From: Alexander Hoogerhuis <alexh@ihatent.com>
To: linux-kernel@vger.kernel.org
Subject: SUB memeory stick and kobject oops
Date: 21 Feb 2004 11:44:09 +0100 [thread overview]
Message-ID: <87n07cbtl2.fsf@lapper.ihatent.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2012 bytes --]
Caught this one in my log when inserting my shiny new 512Mb Verbatim
USB memory stick:
usb 3-1: new high speed USB device using address 2
SCSI subsystem initialized
Initializing USB Mass Storage driver...
scsi0 : SCSI emulation for USB Mass Storage devices
Vendor: Verbatim Model: USB Drive Rev: 2.00
Type: Direct-Access ANSI SCSI revision: 02
WARNING: USB Mass Storage data integrity not assured
USB Mass Storage device found at 2
drivers/usb/core/usb.c: registered new driver usb-storage
USB Mass Storage support registered.
sda: Unit Not Ready, sense:
Current : sense key Unit Attention
Additional sense: Not ready to ready change, medium may have changed
sda : READ CAPACITY failed.
sda : status=1, message=00, host=0, driver=08
Current sd: sense key Unit Attention
Additional sense: Not ready to ready change, medium may have changed
sda: assuming Write Enabled
sda: assuming drive cache: write through
SCSI device sda: 1024000 512-byte hdwr sectors (524 MB)
sda: assuming Write Enabled
sda: assuming drive cache: write through
SCSI device sda: 1024000 512-byte hdwr sectors (524 MB)
sda: assuming Write Enabled
sda: assuming drive cache: write through
sda: sda1
sda: sda1
kobject_register failed for sda1 (-17)
Call Trace:
[<c01b5e83>] kobject_register+0x50/0x52
[<c01840f0>] add_partition+0xb4/0xde
[<c018426a>] register_disk+0xf8/0x103
[<c0202351>] add_disk+0x3b/0x48
[<c02022f4>] exact_match+0x0/0xb
[<c02022ff>] exact_lock+0x0/0x17
[<f09b5730>] sd_probe+0x1ff/0x36a [sd_mod]
[<c01853ab>] create_dir+0xa4/0xa6
[<c01fb493>] bus_match+0x35/0x5e
[<c01fb5a0>] driver_attach+0x55/0x7f
[<c01b5e56>] kobject_register+0x23/0x52
[<c01fb81a>] bus_add_driver+0x8d/0x9f
[<c01fbba0>] driver_register+0x2b/0x2f
[<f096c02d>] init_sd+0x2d/0x6b [sd_mod]
[<c0136fc3>] sys_init_module+0x107/0x23d
[<c027b736>] sysenter_past_esp+0x43/0x65
Attached scsi removable disk sda at scsi0, channel 0, id 0, lun 0
Gentoo 1.4 (unstable), kernel 2.6.3-mm2 and config is here:
[-- Attachment #2: config.gz --]
[-- Type: application/octet-stream, Size: 8613 bytes --]
[-- Attachment #3: Type: text/plain, Size: 286 bytes --]
Device seems to work after this though, it can be mounted as
/dev/sda1.
mvh,
A
--
Alexander Hoogerhuis | alexh@ihatent.com
CCNP - CCDP - MCNE - CCSE | +47 908 21 485
"You have zero privacy anyway. Get over it." --Scott McNealy
next reply other threads:[~2004-02-21 10:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-21 10:44 Alexander Hoogerhuis [this message]
2004-02-21 11:55 ` SUB memeory stick and kobject oops Alexander Hoogerhuis
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=87n07cbtl2.fsf@lapper.ihatent.com \
--to=alexh@ihatent.com \
--cc=linux-kernel@vger.kernel.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