Feisty 20070222 shows two USB icons
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
linux-source-2.6.20 (Ubuntu) |
Won't Fix
|
Low
|
Kyle McMartin |
Bug Description
Feisty 20070222 (md5sums check) CD Live Desktop shows two identical casper-rw USB drive icons.
Should not be two icons, there is only one USB drive plugged in.
/var/log/syslog shows this:
Feb 22 13:39:01 ubuntu kernel: [ 55.397911] loop: loaded (max 8 devices)
Feb 22 13:39:01 ubuntu kernel: [ 55.513297] SCSI device sda: 2012160 512-byte hdwr sectors (1030 MB)
Feb 22 13:39:01 ubuntu kernel: [ 55.518267] sda: Write Protect is off
Feb 22 13:39:01 ubuntu kernel: [ 55.518276] sda: Mode Sense: 03 00 00 00
Feb 22 13:39:01 ubuntu kernel: [ 55.518281] sda: assuming drive cache: write through
Feb 22 13:39:01 ubuntu kernel: [ 55.530257] SCSI device sda: 2012160 512-byte hdwr sectors (1030 MB)
Feb 22 13:39:01 ubuntu kernel: [ 55.535345] sda: Write Protect is off
Feb 22 13:39:01 ubuntu kernel: [ 55.535350] sda: Mode Sense: 03 00 00 00
Feb 22 13:39:01 ubuntu kernel: [ 55.535354] sda: assuming drive cache: write through
Feb 22 13:39:01 ubuntu kernel: [ 55.535365] sda: sda1
Feb 22 13:39:01 ubuntu kernel: [ 55.542648] sd 0:0:0:0: Attached scsi removable disk sda
Feb 22 13:39:01 ubuntu kernel: [ 55.555582] sd 0:0:0:0: Attached scsi generic sg0 type 0
which looks like some sort of loop gone through when booting up, and it does seem to think it finds two devices. They are really the same device.
Bug is, why is the loop detecting the same device twice? Same UUID, same capacity, ...
Cheers, Jerry
Changed in linux-source-2.6.20: | |
status: | Unconfirmed → Needs Info |
Changed in linux-source-2.6.20: | |
status: | Needs Info → Unconfirmed |
Thanks for taking the time to report this bug. Unfortunately we can't fix it, because your description doesn't yet have enough information.
Please include the following additional information, if you have not already done so (please pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command "dmesg > dmesg.log" and attach the resulting file "dmesg.log" to this bug report.
3. Please run the command "lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.
For your reference, the full description of procedures for kernel-related bug reports is available at http:// wiki.ubuntu. com/DebuggingKe rnelProblems . Thanks in advance!