From: Mark Lord <lkml@rtr.ca>
To: Pavel Machek <pavel@ucw.cz>
Cc: bugme-daemon@bugzilla.kernel.org, rjw@sisk.pl, bunk@kernel.org,
Linux Kernel <linux-kernel@vger.kernel.org>,
linux-usb@vger.kernel.org
Subject: Re: [Bug 10345] USB HID problems after resume
Date: Sun, 30 Mar 2008 16:15:50 -0400 [thread overview]
Message-ID: <47EFF4F6.1050302@rtr.ca> (raw)
In-Reply-To: <20080330182243.GA11839@elf.ucw.cz>
Pavel Machek wrote:
> On Sun 2008-03-30 13:46:25, Mark Lord wrote:
>> Pavel Machek wrote:
>>> On Sat 2008-03-29 13:15:40, Mark Lord wrote:
>>> ..
>>>> Just happened again. The machine resumed from RAM with no functioning USB.
>>>> Still running the exact same 2.6.25-rc7 kernel as before, with the RTC conflict fixed.
>>>>
>>>> WTF?
>>>> 3GB of RAM? Try iommu=soft.
>> ..
>>
>> What does that option do (it is not in Documentation/kernel-parameters.txt),
>> and why do you suspect it may make a difference here?
>
> See x86_64/boot-options.txt . Yes, that should be fixed.
>
> I had strange problems, and it looks like iommu does not have proper
> suspend/resume support. > 3GB machines hit that. Do you have one?
..
This is a 32-bit system / kernel, so I'm guessing that this option is not applicable.
Right? (it does have 3GB of RAM, though).
Cheers
next prev parent reply other threads:[~2008-03-30 20:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080328223544.A61F711D10C@picon.linux-foundation.org>
[not found] ` <47EE78C9.5090006@rtr.ca>
2008-03-29 17:15 ` [Bug 10345] USB HID problems after resume Mark Lord
2008-03-29 22:02 ` Alan Stern
2008-03-30 9:30 ` Oliver Neukum
2008-03-30 11:48 ` Pavel Machek
2008-03-30 17:46 ` Mark Lord
2008-03-30 18:22 ` Pavel Machek
2008-03-30 20:15 ` Mark Lord [this message]
2008-03-30 20:20 ` Pavel Machek
2008-03-30 20:22 ` Mark Lord
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=47EFF4F6.1050302@rtr.ca \
--to=lkml@rtr.ca \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=bunk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rjw@sisk.pl \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.