On Mon, Oct 12, 2009 at 09:41:07PM +0100, Ben Hutchings wrote:
> On Mon, 2009-10-12 at 21:47 +0300, George Tellalov wrote:
> > On Sun, Oct 11, 2009 at 11:23:42PM +0100, Ben Hutchings wrote:
> > > Can you test whether the newer kernel versions in unstable (2.6.30) or
> > > experimental (2.6.31) still have this bug? You can install kernel
> > > packages from unstable/experimental without upgrading the rest of a
> > > stable system.
> > >
> >
> > I don't have an easy way to upgrade this pc to unstable.
>
> You should only need to install a single additional package,
> linux-image-2.6.30-2-amd64 or linux-image-2.6.31-trunk-amd64.

George, did you try a more recent kernel?

Cheers,
Moritz



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

> George, did you try a more recent kernel?
>

I did a while ago but I couldn't spend enough time to reproduce the problem. I
think I'll have to attach a lot of usb devices and put the pc to a high load.
Hopefully I'll be able to do that in the coming days with 2.6.32



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

It seems that the problem is gone with 2.6.32-6. I've tested for over an hour
today and I couldn't crash it. I'll leave the on-board usb controller on with
all the devices attached and if the problem appears again, I'll reopen the
bug. Right now I think it's safe to close it.

Thanks!



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org