From: David Brownell <david-b@pacbell.net>
To: linux-usb-devel@lists.sourceforge.net
Cc: Norbert Preining <preining@logic.at>,
linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>,
Dmitry Torokhov <dtor_core@ameritech.net>
Subject: Re: [linux-usb-devel] 2.6.8-rc2-mm2 with usb and input problems
Date: Mon, 2 Aug 2004 10:03:42 -0700 [thread overview]
Message-ID: <200408021003.42090.david-b@pacbell.net> (raw)
In-Reply-To: <20040802162845.GA24725@gamma.logic.tuwien.ac.at>
On Monday 02 August 2004 09:28, Norbert Preining wrote:
> - USB deadlocking
> USB is still deadlocky, quite often process hang in D+ state.
So what does alt-sysrq-t show you about those processes?
How do you reproduce these hangs? I'm guesssing that
And does 2.6.8-rc (without the MM patch) acts the same.
> - psmouse/synaptics
> If I have usb as module, I cannot get synaptics to be recognized.
Odd. BIOS settings maybe?
> (or is a modular USB not necessary for S2R now that
> we have CONFIG_USB_SUSPEND?)
The S2R issue is caused by delivering bogus PCI
device power states to PCI drivers. See if the patch
in http://bugme.osdl.org/show_bug.cgi?id=2886
helps at all. (It might be better to map STANDBY
to D0 state, so long as nobody's actually checking
PCI config space there to see if D1 or D2 works.)
If you don't actually have code trying to suspend
USB devices, don't enable it. Until some other
issues in the PM core get resolved (notably its
eagerness to self-deadlock) that's purely for use
by developers.
- Dave
next prev parent reply other threads:[~2004-08-02 17:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-02 16:28 2.6.8-rc2-mm2 with usb and input problems Norbert Preining
2004-08-02 17:03 ` David Brownell [this message]
2004-08-02 17:13 ` [linux-usb-devel] " Norbert Preining
2004-08-03 8:11 ` Norbert Preining
2004-08-05 2:26 ` David Brownell
2004-08-05 6:51 ` Norbert Preining
2004-08-05 15:37 ` David Brownell
2004-08-10 17:18 ` Norbert Preining
2004-08-10 18:46 ` Alan Stern
2004-08-11 5:20 ` Norbert Preining
2004-08-03 0:08 ` Dmitry Torokhov
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=200408021003.42090.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=akpm@osdl.org \
--cc=dtor_core@ameritech.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=preining@logic.at \
/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.