public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adam Sampson <azz@us-lot.org>
To: Pete Zaitcev <zaitcev@redhat.com>
Cc: Paulo da Silva <psdasilva@esoterica.pt>, linux-kernel@vger.kernel.org
Subject: Re: k 2.6.9: ub module causes /dev/sda and /dev/sda1 not being created
Date: Sat, 30 Oct 2004 22:39:07 +0100	[thread overview]
Message-ID: <y2a654ryjgk.fsf@cartman.at.fivegeeks.net> (raw)
In-Reply-To: <20041030091522.6f2da605@lembas.zaitcev.lan> (Pete Zaitcev's message of "Sat, 30 Oct 2004 09:15:22 -0700")

Pete Zaitcev <zaitcev@redhat.com> writes:

> This is intentional. The ub takes over certain functions of usb-storage
> when it is configured in. Is it a problem? If yes, why?

This happened to me too.

If you build both ub and usb_storage as modules and only load
usb_storage, then you can't use USB Storage devices any more:
usb_storage doesn't get attached to them (you end up with Driver=none
in /proc/bus/usb/devices). Since ub doesn't appear work with my
unbranded el-cheapo card reader, I wasn't able to use it until I
removed ub from my kernel config and rebuilt.

A friend's got a USB hard disk, and has the same problem with
usb_storage not getting used any more; I don't think he's tried ub
yet, but it's clearly the wrong thing to use for the job anyway.

This is how my card reader appears in /proc/bus/usb/devices with only
usb_storage built as a module:

T:  Bus=01 Lev=01 Prnt=01 Port=01 Cnt=02 Dev#= 35 Spd=12  MxCh= 0
D:  Ver= 1.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1
P:  Vendor=0d7d ProdID=0240 Rev= 1.00
S:  Manufacturer=
S:  Product=USB Reader
S:  SerialNumber=FF0390500928
C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=100mA
I:  If#= 0 Alt= 0 #EPs= 3 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage
E:  Ad=81(I) Atr=02(Bulk) MxPS=  64 Ivl=0ms
E:  Ad=02(O) Atr=02(Bulk) MxPS=  64 Ivl=0ms
E:  Ad=83(I) Atr=03(Int.) MxPS=   2 Ivl=1ms

And these are the errors that I got from ub when trying to mount a
card:

Wed Oct 27 19:54:27 2004 warning: ub: sizeof ub_scsi_cmd 60 ub_dev 924
Wed Oct 27 19:54:27 2004 info: uba: device 3 capacity nsec 50 bsize 512
Wed Oct 27 19:54:27 2004 warning: uba: made changed
Wed Oct 27 19:54:27 2004 info: uba: device 3 capacity nsec 50 bsize 512
Wed Oct 27 19:54:27 2004 info: uba: device 3 capacity nsec 50 bsize 512
Wed Oct 27 19:54:27 2004 info:  uba:end_request: I/O error, dev uba, sector 0
Wed Oct 27 19:54:27 2004 err: Buffer I/O error on device uba, logical block 0
Wed Oct 27 19:54:27 2004 warning: end_request: I/O error, dev uba, sector 2
Wed Oct 27 19:54:27 2004 err: Buffer I/O error on device uba, logical block 1
Wed Oct 27 19:54:27 2004 warning: end_request: I/O error, dev uba, sector 4
Wed Oct 27 19:54:27 2004 err: Buffer I/O error on device uba, logical block 2
Wed Oct 27 19:54:27 2004 warning: end_request: I/O error, dev uba, sector 6
Wed Oct 27 19:54:27 2004 err: Buffer I/O error on device uba, logical block 3
Wed Oct 27 19:54:27 2004 warning: end_request: I/O error, dev uba, sector 6
Wed Oct 27 19:54:27 2004 err: Buffer I/O error on device uba, logical block 3
Wed Oct 27 19:54:27 2004 warning: end_request: I/O error, dev uba, sector 4
Wed Oct 27 19:54:27 2004 err: Buffer I/O error on device uba, logical block 2
Wed Oct 27 19:54:27 2004 warning: end_request: I/O error, dev uba, sector 2
Wed Oct 27 19:54:27 2004 err: Buffer I/O error on device uba, logical block 1
Wed Oct 27 19:54:27 2004 warning: end_request: I/O error, dev uba, sector 0
Wed Oct 27 19:54:27 2004 err: Buffer I/O error on device uba, logical block 0
Wed Oct 27 19:54:27 2004 warning:  unable to read partition table
Wed Oct 27 19:54:27 2004 info:  uba:end_request: I/O error, dev uba, sector 2
Wed Oct 27 19:54:27 2004 err: Buffer I/O error on device uba, logical block 1
Wed Oct 27 19:54:27 2004 warning: end_request: I/O error, dev uba, sector 4
Wed Oct 27 19:54:27 2004 err: Buffer I/O error on device uba, logical block 2
Wed Oct 27 19:54:27 2004 warning: end_request: I/O error, dev uba, sector 6
Wed Oct 27 19:54:27 2004 err: Buffer I/O error on device uba, logical block 3
Wed Oct 27 19:54:27 2004 warning: end_request: I/O error, dev uba, sector 0
Wed Oct 27 19:54:27 2004 err: Buffer I/O error on device uba, logical block 0
Wed Oct 27 19:54:27 2004 warning:  unable to read partition table
Wed Oct 27 19:54:27 2004 info: usbcore: registered new driver ub
Wed Oct 27 19:55:27 2004 warning: uba: made changed
Wed Oct 27 19:55:27 2004 info: uba: device 3 capacity nsec 50 bsize 512
Wed Oct 27 19:55:27 2004 info: uba: device 3 capacity nsec 50 bsize 512
Wed Oct 27 19:55:27 2004 info:  uba:end_request: I/O error, dev uba, sector 2
Wed Oct 27 19:55:27 2004 err: Buffer I/O error on device uba, logical block 1
Wed Oct 27 19:55:27 2004 warning: end_request: I/O error, dev uba, sector 4
Wed Oct 27 19:55:27 2004 err: Buffer I/O error on device uba, logical block 2
Wed Oct 27 19:55:27 2004 warning: end_request: I/O error, dev uba, sector 6
Wed Oct 27 19:55:27 2004 err: Buffer I/O error on device uba, logical block 3
Wed Oct 27 19:55:27 2004 warning: end_request: I/O error, dev uba, sector 0
Wed Oct 27 19:55:27 2004 err: Buffer I/O error on device uba, logical block 0
Wed Oct 27 19:55:27 2004 warning: end_request: I/O error, dev uba, sector 2
Wed Oct 27 19:55:27 2004 err: Buffer I/O error on device uba, logical block 1
Wed Oct 27 19:55:27 2004 warning: end_request: I/O error, dev uba, sector 4
Wed Oct 27 19:55:27 2004 err: Buffer I/O error on device uba, logical block 2
(etc.; lots more "Buffer I/O error" lines)

-- 
Adam Sampson <azz@us-lot.org>                        <http://offog.org/>

  reply	other threads:[~2004-10-30 21:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.1099103401.11097.linux-kernel2news@redhat.com>
2004-10-30 16:15 ` k 2.6.9: ub module causes /dev/sda and /dev/sda1 not being created Pete Zaitcev
2004-10-30 21:39   ` Adam Sampson [this message]
2004-10-31 22:10   ` Fabio Coatti
2004-10-31 22:57     ` Pete Zaitcev
2004-10-30  2:19 Paulo da Silva
2004-10-30 10:23 ` Pasi Savolainen
     [not found] ` <mailman.1099132081.20925.linux-kernel2news@redhat.com>
2004-11-23 17:50   ` Pete Zaitcev

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=y2a654ryjgk.fsf@cartman.at.fivegeeks.net \
    --to=azz@us-lot.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=psdasilva@esoterica.pt \
    --cc=zaitcev@redhat.com \
    /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