Re: 2.6.9 suspend-to-disk bug (during resume)

[Alan Jenkins]

On Thu, 2005-01-20 at 10:19 +0100, Rafael J. Wysocki wrote: 
> On Thursday, 20 of January 2005 09:49, Alan Jenkins wrote:
> > On 20/01/05 08:48:02, Alan Jenkins wrote:
> > I have noticed a similar message, and so has someone else on the list:
> > 
> > http://groups-beta.google.com/group/fa.linux.kernel/browse_thread/thread/1bfcbbca2d508bb3/cb69d674510d215a?q=%22bad:+scheduling+while+atomic!%22+suspend&_done=%2Fgroup%2Ffa.linux.kernel%2Fsearch%3Fgroup%3Dfa.linux.kernel%26q%3D%22bad:+scheduling+while+atomic!%22+suspend%26qt_g%3D1%26searchnow%3DSearch+this+group%26&_doneTitle=Back+to+Search&&d#cb69d674510d215a
> > 
> > I have an asrock motherboard with an sis chipset.
> > SiS seems to be the common factor.  I think its something general about
> > the chipset.  My messages seem to involve the network card, the sound
> > card and the i8042 (ps/2 port) controller:
> 
> Have you tried to boot with "pci=routeirq" or/and "noapic"?
> 
> Greets,
> RJW
> 

To no avail.  Pavels workaround (disable preempt) works though.

With regard to the ps/2 controller, the keyboard stops working after a
suspend/resume cycle at the console (as opposed to from X).  This does
not occur if I first boot to runlevel 1 and then switch to the desired
runlevel - perhaps it is some sort of timing issue?  Very puzzling.

Thanks
Alan

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/