Lombard Sleep Crash (Was: 2.2.18pre17 again)

[Michael Schmitz]

> PC=c00d11f4 		 -> c00d11dc t idepmac_wake_device

Can you disassemble the kernel and look up where approximately in
idepmac_wake_device the panic happens?

> I recompiled with CONFIG_ALL_PPC=y in .config, but this did not change anything.
> Was there a change of the major device number for /dev/adb? In
> /var/log/messages, the startup of results in the following:
>
> pmud[333]: pmud [treshold = 420, margin = 15] started
> modprobe: modprobe: Can't locate module char-major-56
> pmud[333]: Couldn't open /dev/adb
> pmud[333]: daemon stopped (Couldn't open /dev/adb)

Nope, /dev/adb remains unchanged, just ADB mice aren't necessarily read
via the adbmouse device anymore (but that was misc minor 10, the patch to
handle keyboard and mouse data as separate ADB devices in the ADB major
range never made it in).

Make sure you the core adb support is compiled in. It currently is, unless
CONFIG_MBX is set ... if CONFIG_ALL_PPC=y implies CONFIG_MBX=y, someone
better fix this.

Did all your kernels that crash lack ADB support, or just the latest you
built with CONFIG_ALL_PPC=y ?

	Michael


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/