From: David Brownell <david-b@pacbell.net>
To: linux-usb-devel@lists.sourceforge.net
Cc: Andrew Morton <akpm@osdl.org>, Robert Hancock <hancockr@shaw.ca>,
linux-kernel@vger.kernel.org,
Felix von Leitner <felix-linuxkernel@fefe.de>
Subject: Re: [linux-usb-devel] Re: 2.6.11: USB broken on nforce4, ipv6 still broken, centrino speedstep even more broken than in 2.6.10
Date: Sat, 12 Mar 2005 08:34:50 -0800 [thread overview]
Message-ID: <200503120834.50788.david-b@pacbell.net> (raw)
In-Reply-To: <20050311211908.434baba1.akpm@osdl.org>
On Friday 11 March 2005 9:19 pm, Andrew Morton wrote:
>
> (Restoring email headers. Please always use reply-to-all)
>
> Robert Hancock <hancockr@shaw.ca> wrote:
> >
> > Felix von Leitner wrote:
> > > My new nForce 4 mainboard has 10 or so USB 2.0 outlets. In Windows,
> > > they all work. In Linux, two of them work. Putting my USB stick or
> > > anything else in one of the others produces nothing in Linux.
> > > Apparently no IRQ getting through or something?
> >
> > Likely similar to the problem I reported in this thread on
> > linux-usb-devel - the patch that David Brownell posted fixed the problem
> > for me..
> >
> > http://sourceforge.net/mailarchive/message.php?msg_id=10755097
> >
My thoughts exactly. However, 2.6.11 includes that fix. Are you
sure that dmesg output came from 2.6.11?
To repeat what Alan Stern said yesterday: provide full "dmesg"
output, with CONFIG_USB_DEBUG enabled. I think that falls into
the category of "how to provide a usable bug report" ... :)
prev parent reply other threads:[~2005-03-12 16:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3GZyA-16B-17@gated-at.bofh.it>
2005-03-12 5:06 ` 2.6.11: USB broken on nforce4, ipv6 still broken, centrino speedstep even more broken than in 2.6.10 Robert Hancock
2005-03-12 5:19 ` Andrew Morton
2005-03-12 16:34 ` David Brownell [this message]
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=200503120834.50788.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=akpm@osdl.org \
--cc=felix-linuxkernel@fefe.de \
--cc=hancockr@shaw.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
/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