On Tue, 13 Sep 2011, maximilian attems wrote:
tags 628444 moreinfo
stop
This bug actually applies to all Debian kernels I have tried including
2.6.36, 2.6.37, 2.6.38, and 2.6,39
Did you try since newer 3.0 images, how are they performing?
thank you
I wasn't aware that the 3.0 kernels were out until you sent this message.
Unfortunately, since this bug takes time to manifest, it will require that
I run with 3.0 as my default kernel, this means I have to get vmware to
run with it (since I use it heavily), and that is usually a problem for
bleeding edge kernels. I will look into it, but it may be a week or so
before I can even try running a 3.0 kernel.
Shannon C. Dealy | DeaTech Research Inc.
de...@deatech.com | - Custom Software Development -
Phone: (800) 467-5820 | - Natural Building Instruction -
or: (541) 929-4089 | www.deatech.com
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/alpine.deb.2.00.1109142348290.19...@nashapur.deatech.com
