Hi all, I just moved my old hard-drive to a new box, so I put it on /dev/hdb Trying to boot the 2.6.22 kernel seems to upset yaird AFAICT
As well as this: Probing IDE interface ide1... BUG: sleeping function called from invalid context kpnpbiosd(92) at kernel/rtmutex.c:636 in_atomic():1 [00000001], irqs_disabled():0 [<c02b8b06>] __rt_spin_lock+0x20/0x3a [<c021811b>] pnp_bios_dock_station_info+0x64/0x149 [<c0216f9d>] pnp_dock_thread+0x0/0x1a0 [<c0217119>] pnp_dock_thread+0x17c/0x1a0 [<c0216f9d>] pnp_dock_thread+0x0/0x1a0 [<c02b7996>] schedule+0xed/0x110 [<c0216f9d>] pnp_dock_thread+0x0/0x1a0 [<c012ca3e>] kthread+0x36/0x5c [<c012ca08>] kthread+0x0/0x5c [<c0105017>] kernel_thread_helper+0x7/0x10 ======================= --------------------------- | preempt count: 00000001 ] | 1-level deep critical section nesting: ---------------------------------------- .. [<c02180ea>] .... pnp_bios_dock_station_info+0x33/0x149 .....[<00000000>] .. ( <= _stext+0x3feff000/0x14) Which was there before and didn't prevent booting I get lots of waiting for /sys/block/dev/hdb/ to show up messages ending in a kernel panic Having googled a bit, this bug is present in the 2.6.14 kernels as well as the 2.6.22 specifically and appears to be some conflict with yaird. This is admittedly a corner case, but I can easily test future kernels against this. It just strengthens the case for getting a new version ready for testing. ;) Anyway, I'm running 2.6.21 for now & I'll check out 2.6.23 as soon as I have the rest of my hardware running happily on the old kernel. cheers, tim _______________________________________________ 64studio-devel mailing list [email protected] http://lists.64studio.com/mailman/listinfo/64studio-devel
