public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Lieverdink <peter@cc.com.au>
To: linux-kernel@vger.kernel.org
Cc: lk@rekl.yi.org
Subject: Re: KM266/VT8235, USB2.0 and problems
Date: Tue, 06 Jan 2004 15:36:38 +1100	[thread overview]
Message-ID: <1073363798.7647.7.camel@kahlua> (raw)
In-Reply-To: <Pine.LNX.4.58.0401052145520.32347@rekl.yi.org>

[-- Attachment #1: Type: text/plain, Size: 895 bytes --]

On Tue, 2004-01-06 at 14:52, lk@rekl.yi.org wrote:
> > > > Do the errors go away if you stop using devfs?
> > > 
> 
> Ok, I removed devfs support from the kernel, and installed udev on the 
> machine.  I get the same error:
> 
> SCSI error : <0 0 0 0> return code = 0x70000
> end_request: I/O error, dev sda, sector 7552
> Buffer I/O error on device sda, logical block 944

I get the same thing using USB2 on a KT400/VT8235 mobo. I have a 20Gb
USB2 HDD (fat32), which produces this when accessed:

SCSI error : <1 0 0 0> return code = 0x8000000
Current sdb: sense key No Sense
end_request: I/O error, dev sdb, sector 19159735
Buffer I/O error on device sdb1, logical block 19159672

The drive works flawlessly with Windows and MacOS. A 128Mb USB key via
USB1.1 causes no problems. Not using udev, not using devfs. The USB2
drive works fine under 2.4.X as well.

- Peter.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-01-06  4:37 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
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 [this message]
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=1073363798.7647.7.camel@kahlua \
    --to=peter@cc.com.au \
    --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