[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200803311704.37256.oliver@neukum.org>
Date: Mon, 31 Mar 2008 17:04:36 +0200
From: Oliver Neukum <oliver@...kum.org>
To: Mark Lord <lkml@....ca>
Cc: Pavel Machek <pavel@...e.cz>,
Linux Kernel <linux-kernel@...r.kernel.org>,
Greg KH <gregkh@...e.de>,
Andrew Morton <akpm@...ux-foundation.org>, jikos@...e.cz
Subject: Re: 2.6.25-rc7: Ugh.
Am Montag, 31. März 2008 16:39:33 schrieb Mark Lord:
> Oliver Neukum wrote:
> > Am Sonntag, 30. März 2008 23:04:25 schrieb Mark Lord:
> >>>> Correction there: 3GB of RAM, not 2.
> >>> 3GB of RAM can be a problem. Try iommu=soft. .. but in such case
> >>> rmmod/insmod of usbhid would not help...
> >> ..
> >>
> >> Booted with mem=2GB, and USB hung again on the first suspend/resume cycle.
> >
> > Are you running with CONFIG_USB_SUSPEND? If so, please try without it.
> ..
>
> Funny. One of the first posts in this thread told me to make sure
> that I do use CONFIG_USB_SUSPEND (which I have been for many kernels now).
>
> One thing I just tried, was to unload all USB stuff before suspend,
> and reload on resume -- just stuck the commands into my suspend/resume script.
>
> The machine has been 100% rock solid since then.
> So I think that definitely implicates USB.
Yes. What happens if you unload only usbhid at that time?
> Still want USB_SUSPEND=n ? Please explain.
It looks like you are hanging in the kthread for autosuspending. Compiling
that out should confirm it.
Regards
Oliver
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists