From: Greg KH <greg@kroah.com>
To: lk@rekl.yi.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: KM266/VT8235, USB2.0 and problems
Date: Mon, 5 Jan 2004 00:12:26 -0800 [thread overview]
Message-ID: <20040105081226.GA14177@kroah.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0401042314160.18200@rekl.yi.org>
On Sun, Jan 04, 2004 at 11:30:51PM -0600, lk@rekl.yi.org wrote:
> Hi. I've noticed that intermittently in the past with some devices, and
> now every time with my new USB2.0 thumb drive (aka pen drive, aka flash
> memory thing) that there are errors with the USB on my motherboard. It's
> a M7VIG-PRO, which has a KM266/VT8235 chipset.
>
> Using kernel 2.6.0, I can only access my flash drive several times before
> getting an error about not being able to access the device. The dmesg
> output is below. When I try on my laptop, which has an EHCI USB2.0
> controller, the device works flawlessly. There are no errors, etc.
>
> I am using a USB keyboard and a USB mouse. Both work fine.
>
> I've tried several combinations of connecting the device, with and without
> the "noapic" kernel option while booting. I've connected the device to
> the motherboard's USB sockets (ie the ones soldered to the board, not via
> wires to the case), through a USB2.0 hub, etc. I get the same result
> every time.
>
> I've included the relevant parts of "dmesg" and "dmidecode". Please cc:
> me on responses, since I'm not subscribed, and let me know what to try
> next.
Do the errors go away if you stop using devfs?
thanks,
greg k-h
next prev parent reply other threads:[~2004-01-05 8:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-05 5:30 KM266/VT8235, USB2.0 and problems lk
2004-01-05 8:12 ` Greg KH [this message]
2004-01-05 16:48 ` lk
2004-01-05 17:23 ` Greg KH
2004-01-05 17:44 ` lk
2004-01-06 3:52 ` lk
2004-01-06 4:36 ` Peter Lieverdink
2004-01-06 19:25 ` Greg KH
2004-01-07 17:02 ` lk
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=20040105081226.GA14177@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lk@rekl.yi.org \
/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