On Fri, Sep 21, 2007 at 02:59:42AM -0500, Andrew Deason wrote: > > The only module I had loaded that would taint the kernel would be > fglrx, but that's not loaded until way after resuming. Does that really > make a difference?
well we don't support tainted kernels, as there is no way to fix that code. > In any case, I removed the fglrx module (just to be sure), and the same > thing happens. The dmesg output is even the same, isn't it? Is there > anything besides dmesg output I should be supplying here? yes test against latest linux image 2.6.23-rc5, see trunk snapshot apt lines -> http://wiki.debian.org/DebianKernel if it still ooops please report upstream on bugzilla.kernel.org and let us know the bug nr. thanks -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]