fedora death on eee

i installed those 460 updates and (about 8 hours later) rebooted.  this time we got another filesystem error but fsck reported a lot more problems and now when i boot i just get:

VFS: Can't find ext3 filesystem on dev dm-0.

now i think i got that before when i tried to install F9 and i just re-installed and it was okay the second time round.  so i’m going to try re-installing F10 and we’ll see what we get.

———-

booting to f10 beta livecd was painless again but the system reported many disk errors on the system disks (presumably because of whatever stopped it booting before) and throttled them back to their slowest settings (PIO0) so when the ‘install to system’ got to the ‘copying image to disk’ stage it went very slowly and the system got very slow too.  so i gave up and rebooted.  i guess the re-format and reboot cheered it up because those errors went away and i’m now typing this from f10 beta proper again.

i’ve tried rebooting with this default kernel but haven’t been able to reproduce the disk corruption yet so i’ve kicked off the system update again.  480 updates this time.

oh, i’ve taken a copy of the dmesg errors i mentioned earlier:

=================================
[ INFO: inconsistent lock state ]
2.6.27-0.352.rc7.git1.fc10.i686 #1
———————————
inconsistent {hardirq-on-W} -> {in-hardirq-W} usage.
NetworkManager/2490 [HC1[1]:SC0[1]:HE0:SE0] takes:
(&adapter->mdio_lock){+-..}, at: [<f88ee54e>] atl1e_intr+0x22d/0x3f7 [atl1e]
{hardirq-on-W} state was registered at:
[<c044ca1a>] __lock_acquire+0x2ad/0xae6
[<c044d2ae>] lock_acquire+0x5b/0x81
[<c06e5150>] _spin_lock+0x23/0x50
[<f88f1fdc>] atl1e_probe+0x50b/0x6bc [atl1e]
[<c054164e>] pci_device_probe+0x3e/0x5e
[<c05aeb0e>] driver_probe_device+0xa5/0x141
[<c05aebec>] __driver_attach+0x42/0x64
[<c05ae4c1>] bus_for_each_dev+0x43/0x6d
[<c05ae996>] driver_attach+0x19/0x1b
[<c05aded6>] bus_add_driver+0xa8/0x1c8
[<c05aeda1>] driver_register+0x89/0xe9
[<c0541840>] __pci_register_driver+0x58/0x84
[<f881601c>] 0xf881601c
[<c0401139>] do_one_initcall+0x42/0x133
[<c045500e>] sys_init_module+0x8e/0x183
[<c0404d0a>] syscall_call+0x7/0xb
[<ffffffff>] 0xffffffff
irq event stamp: 8897
hardirqs last  enabled at (8895): [<c044c160>] trace_hardirqs_on+0xb/0xd
hardirqs last disabled at (8897): [<c0535c24>] trace_hardirqs_off_thunk+0xc/0x10
softirqs last  enabled at (8818): [<c0432781>] __do_softirq+0x104/0x10f
softirqs last disabled at (8896): [<c06e518e>] _spin_lock_bh+0x11/0x55

other info that might help us debug this:
2 locks held by NetworkManager/2490:
#0:  (rtnl_mutex){–..}, at: [<c065955d>] rtnetlink_rcv+0x17/0x2b
#1:  (_xmit_ETHER){-…}, at: [<c06504ea>] dev_set_rx_mode+0x19/0x2b

stack backtrace:
Pid: 2490, comm: NetworkManager Not tainted 2.6.27-0.352.rc7.git1.fc10.i686 #1
[<c06e2d1a>] ? printk+0x14/0x1a
[<c044b8fa>] valid_state+0x12a/0x13d
[<c044bcf7>] mark_lock+0xde/0x331
[<c044c99d>] __lock_acquire+0x230/0xae6
[<c044b392>] ? trace_hardirqs_off_caller+0x15/0x91
[<c044b419>] ? trace_hardirqs_off+0xb/0xd
[<c04097a2>] ? native_sched_clock+0xb3/0xd3
[<c044bc37>] ? mark_lock+0x1e/0x331
[<c044d2ae>] lock_acquire+0x5b/0x81
[<f88ee54e>] ? atl1e_intr+0x22d/0x3f7 [atl1e]
[<c06e5150>] _spin_lock+0x23/0x50
[<f88ee54e>] ? atl1e_intr+0x22d/0x3f7 [atl1e]
[<f88ee54e>] atl1e_intr+0x22d/0x3f7 [atl1e]
[<c044a9b0>] ? lock_release_holdtime+0x30/0x125
[<c046d192>] handle_IRQ_event+0x1f/0x54
[<c046e290>] handle_fasteoi_irq+0x82/0xbb
[<c046e20e>] ? handle_fasteoi_irq+0x0/0xbb
[<c0406fad>] do_IRQ+0x9f/0xc9
[<c0405700>] common_interrupt+0x28/0x30
[<c06502a5>] ? __dev_set_rx_mode+0x2b/0x8c
[<c06504f1>] dev_set_rx_mode+0x20/0x2b
[<c06520c0>] dev_open+0x96/0xb9
[<c0651ae0>] dev_change_flags+0xa1/0x154
[<c0658883>] ? rtnl_setlink+0x0/0xdb
[<c06587d1>] do_setlink+0x26d/0x31f
[<c06e4f3c>] ? _read_unlock+0x22/0x25
[<c0658883>] ? rtnl_setlink+0x0/0xdb
[<c065895a>] rtnl_setlink+0xd7/0xdb
[<c065970e>] rtnetlink_rcv_msg+0x19d/0x1b7
[<c0659571>] ? rtnetlink_rcv_msg+0x0/0x1b7
[<c066730b>] netlink_rcv_skb+0x35/0x7a
[<c0659569>] rtnetlink_rcv+0x23/0x2b
[<c0666f05>] netlink_unicast+0xf6/0x14c
[<c0667192>] netlink_sendmsg+0x237/0x244
[<c0645b4f>] __sock_sendmsg+0x4a/0x53
[<c0646379>] sock_sendmsg+0xbd/0xd3
[<c043f922>] ? autoremove_wake_function+0x0/0x38
[<c043f922>] ? autoremove_wake_function+0x0/0x38
[<c041f2ae>] ? need_resched+0x18/0x22
[<c05360db>] ? copy_from_user+0x3e/0x125
[<c064cbae>] ? verify_iovec+0x45/0x73
[<c06464d3>] sys_sendmsg+0x144/0x197
[<c0646fb5>] ? sys_recvmsg+0x11b/0x180
[<c044b392>] ? trace_hardirqs_off_caller+0x15/0x91
[<c044b419>] ? trace_hardirqs_off+0xb/0xd
[<c04097a2>] ? native_sched_clock+0xb3/0xd3
[<c040961f>] ? sched_clock+0x8/0xb
[<c044a9b0>] ? lock_release_holdtime+0x30/0x125
[<c044c160>] ? trace_hardirqs_on+0xb/0xd
[<c044c134>] ? trace_hardirqs_on_caller+0xf9/0x11a
[<c044c160>] ? trace_hardirqs_on+0xb/0xd
[<c042abf1>] ? finish_task_switch+0x49/0xc5
[<c042aba8>] ? finish_task_switch+0x0/0xc5
[<c06e3549>] ? schedule+0x6d9/0x6f8
[<c0647530>] sys_socketcall+0x16d/0x1a3
[<c040b403>] ? syscall_trace_enter+0xba/0xce
[<c0404d0a>] syscall_call+0x7/0xb
=======================

fedora 9 on the eee pc 901

i need to make a note of all the behaviours of fedora 9 on my eee pc 901 before installing fedora 10 beta on it.

main points are:

  • have to build wireless drivers from source from here – currently version 1.8.0 – which is, hopefully, the same as the 1.7.0 i used plus the patches i had to apply!
  • the wireless driver doesn’t appear to have a monitor mode
  • without a usb dvd drive you have to boot from the SD slot or an external usb hard drive. this works with livecd (if you’ve got the livecd creator tools) but not with the DVD image.
  • after a suspend/resume the brightness control doesn’t work
  • suspend by closing the lid works fine but suspend on idle does a hibernate instead
  • there’s noise from the speakers if they’re not muted – which is a shame on an utterly silent system
  • occasionally the back-light switches off (possibly only after screensaver and screen blank when on AC) and it doesn’t come back on until you use a Fn brightness key. it’s still possible it’s actually any key and it’s just gone to sleep
  • 3D works pretty well for compiz but it goes a bit wrong when you try running a 3D or Xv (video) app at the same time – particularly troublesome when that app defaults to fullscreen mode – e.g. blender or miro. watching DVDs or using stellarium or blender is fine with compiz disabled
  • no middle mouse button (big problem in blender) and we’ve moved to xinput driver so it’s a bit of a pain enabling support again – i created /etc/hal/fdi/policy/3button.fdi with
    <match key="info.product" string="ImPS/2 Logitech Wheel Mouse">
     <merge key="input.x11_options.Emulate3Buttons" type="string">true</merge>
    </match>

    in it.  can’t remember where i read that – i think it’s the sum of several hints and previous hal experience.

  • sometimes if you type too fast keystrokes (especially shift keys) are missed
  • when compiz is enabled you get a brief flash of the desktop before the password prompt is displayed when the system has been locked or suspended
  • sometimes networkmanager disables networking entirely – not sure why.  i think it only happens after a suspend/resume – but only occasionally.
  • 3D does have its limits – flightgear manages only a couple of frames per second (might not have anything to do with the 3D and might be fixable in the settings) – celestia doesn’t work at all and google-earth runs a several seconds per frame.  also i’ve switched off the compiz cube as there’s a little bit of tearing when it spins.  the left/right slide is much more understated anyway.
  • many bad apps assume you’ll have 600 vertical pixels to play with.  i think there might be a compiz plugin to run the entire screen like a virtual display scaled down – i’ll see if i can find that.
  • everything looks sooo pretty on it that  a) i’ve forgotten how hideous the ‘pearl white’ plastic is and b) i really don’t want to do a clean re-install.

on the plus side:

  • the screen is very nice
  • it plays DVDs – we’ll see how it copes with HD content soon
  • desktop effects, google gadgets and cairo-dock look great
  • it’s completely silent
  • battery life is good – 4-6 hours
  • i’ve installed all the good office, internet and graphics apps without problems
  • it fits in a small bag
  • i can afford it
  • it certainly runs F10 to some extent
  • you can jam a custom touch screen and 3G slot inside it!

happy days.

well, that’s as much as i can remember for now.  on with the show – let’s trash it and stick F10 beta on instead.

oh yes, the 901 actually has two SSDs – 4G + 16G for linux, 4G + 8G for windows.  nice.  so i tried partitioning them with some RAID stuff.  here’s some hdparm numbers for F9:

cached reads (memory speed) are around 550MB/s

the 4G disk goes at around 26-28MB/s

the 16G at around 24-27MB/s

RAID1 at around 24-26MB/s

RAID0 at around 30MB/s

with O_DIRECT (unbuffered):

4G 31MB/s

16G 28.5MB/s

RAID1 31MB/s

RAID0 30MB/s

STYG