From: Greg KH <greg@kroah.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: kernel list <linux-kernel@vger.kernel.org>,
stern@rowland.harvard.edu, linux-usb@vger.kernel.org,
oliver@neukum.name
Subject: Re: 2.6.25 -- long standing bug with usb after resume with 4GB ram
Date: Thu, 13 Mar 2008 14:58:42 -0700 [thread overview]
Message-ID: <20080313215842.GB15029@kroah.com> (raw)
In-Reply-To: <20080313110141.GA4329@elf.ucw.cz>
On Thu, Mar 13, 2008 at 12:01:41PM +0100, Pavel Machek wrote:
> Hi!
>
> There are problems with usb after suspend/resume... it works as long
> as memory is limited to 3G -- probably because iommu/agpgart/something
> is not used in such case.
>
> rmmod/insmod of ehci_hcd & ohci_hcd fixes that.
>
> For testing with 2.6.25, you'll need aperture_64.c patch that makes
> iommu as nosave (or it oopses).
Any pointer to where this patch is?
Can it go into 2.6.25?
thanks,
greg k-h
next prev parent reply other threads:[~2008-03-13 22:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-13 11:01 2.6.25 -- long standing bug with usb after resume with 4GB ram Pavel Machek
2008-03-13 20:27 ` Rafael J. Wysocki
2008-03-13 21:58 ` Greg KH [this message]
2008-03-13 22:05 ` Pavel Machek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080313215842.GB15029@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=oliver@neukum.name \
--cc=pavel@ucw.cz \
--cc=stern@rowland.harvard.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox