2.6.33-rc7 problems
ST
I am currently running the linus main git tree with the last commit beeing:
deb0c98c7f6035d47a247e548384517a955314a5 (2.6.33-rc7)
USB Cardreader:
Since i am now in my third attempt to get my usb flashreader going under this
kernel (damn this must be simple right?). I have my doubts if this is probably
not a .config but a kernel problem. If i plug in the usb card reader i get the
output as attached in the file "usb_problems". The .config will be also
attached. So i thought "ok, no problem i messed up", what about the defconfig.
(arch/x86/configs/x86_64_defconfig).
The defconfig works slightly better by omitting the repeating thread
awake/thread sleeping output but no device is found usable. The distribution
is Debian/Sid. The hardware is working with the standard Debian kernel 2.6.30.
I had a similar error when i had an typo in the default codepage "utf-8" vs.
"utf8". But this error is fixed now and USB Sticks are working fine.
Firmware loading:
Firmware loading seems to hang this machine. It can be worked arround by
embedding the firmware for the device (radeon onboard gfx) into the kernel
CONFIG_PREVENT_FIRMWARE_BUILD=y
CONFIG_FW_LOADER=y
CONFIG_FIRMWARE_IN_KERNEL=y
CONFIG_EXTRA_FIRMWARE="radeon/R600_rlc.bin"
CONFIG_EXTRA_FIRMWARE_DIR="/lib/firmware"
The microcode firmware loading also hangs for quite some time.
Disk access:
This is the most annoying: When dooing a md raid 1 level resync the machine
is barely usable. I haven't testet it with the current configuration but even
when "update-grub" from grub2 is called the slowdown is really still there.
There is a file attached "timeouts" which give a output of such a scenario.
And boy 120s starvation is quite bad, right? Besides it doesn't seem fair to
me either.
I am happy to test any patches you throw at me. Any hints tips are also very
welcome.
Thanks
ST
PS: This is whitebox hw with a ASUS M4A78T-E Mainboard and 8 Gigs of ECC
Memory and two SAMSUNG HD103SI in MD Raid 1 configuration.
PPS: Please CC as im am not subscribed on the list.
ST
Concerning the problems in the non working card reader. The SD Cards are
working but the CF Card is not. (Cardreader: Logitech (Alcor Micro) USB )
So if anybody has a working .config for a recent kernel
where a USB Compact Flash reader is known to work, i would be happy if she/he
could send this config file to me.
I am really out of clues why this is not working. It works under Debian with
Stock kernel but not with my config. It also works with Ubuntu Karmic (2.6.32)
but not with my config and a vanilla 2.6.32 kernel. I also consider it an error
that a "make defconfig" kernel is also not able to read the cf card.
Thanks
ST
Robert Hancock
> Hi
>
> I am currently running the linus main git tree with the last commit beeing:
> deb0c98c7f6035d47a247e548384517a955314a5 (2.6.33-rc7)
>
> USB Cardreader:
> Since i am now in my third attempt to get my usb flashreader going under this
> kernel (damn this must be simple right?). I have my doubts if this is probably
> not a .config but a kernel problem. If i plug in the usb card reader i get the
> output as attached in the file "usb_problems". The .config will be also
> attached. So i thought "ok, no problem i messed up", what about the defconfig.
> (arch/x86/configs/x86_64_defconfig).
> The defconfig works slightly better by omitting the repeating thread
> awake/thread sleeping output but no device is found usable. The distribution
> is Debian/Sid. The hardware is working with the standard Debian kernel 2.6.30.
> I had a similar error when i had an typo in the default codepage "utf-8" vs.
> "utf8". But this error is fixed now and USB Sticks are working fine.
Well, the card reader apparently reports medium not present.. is there
anything in there? how is it not working?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majo...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
ST
Thanks for your reply.
> Well, the card reader apparently reports medium not present.. is there
> anything in there? how is it not working?
Well thats exactly the problem since there is a CF Card plugged into the
reader.
I just checked with Fedora 12 and 2.6.31. The output there looks
like this (and i am 100% sure its not an HW error. Since i plugged out the
USB plug not the CF card an use the same USB port while dualbooting):
usb 1-4.3: SerialNumber: 058F63646476
usb 1-4.3: configuration #1 chosen from 1 choice
scsi9 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 7
usb-storage: waiting for device to settle before scanning
generic-usb: probe of 0003:058F:6364.0004 failed with error -22
usb-storage: device scan complete
scsi 9:0:0:0: Direct-Access Generic- SD/MMC 1.00 PQ: 0 ANSI: 0
scsi 9:0:0:1: Direct-Access Generic- Compact Flash 1.01 PQ: 0 ANSI: 0
scsi 9:0:0:2: Direct-Access Generic- SM/xD-Picture 1.02 PQ: 0 ANSI: 0
scsi 9:0:0:3: Direct-Access Generic- MS/MS-Pro 1.03 PQ: 0 ANSI: 0
CCS
sd 9:0:0:0: Attached scsi generic sg3 type 0
sd 9:0:0:1: Attached scsi generic sg4 type 0
sd 9:0:0:2: Attached scsi generic sg5 type 0
sd 9:0:0:3: Attached scsi generic sg6 type 0
sd 9:0:0:3: [sdf] Attached SCSI removable disk
sd 9:0:0:1: [sdd] 15858864 512-byte logical blocks: (8.11 GB/7.56 GiB)
With my config it stops with :
scsi 8:0:0:0: Direct-Access Generic- SD/MMC 1.00 PQ: 0 ANSI: 0
So either some CF Card stuff is missing (old ata stuff needed?) or there is
some other SCSI stuff going on i don't understand...
Since the device scan with my strange config never completes it never has any
devices to offer...
I also checked with 2.6.32 with my config. Same bad result, so i guess it is
not a regression.
Best regards
ST
ST
> Well, the card reader apparently reports medium not present.. is there
> anything in there? how is it not working?
the reader is detected. This explains why there are only no medium present
results in the calls. There was no SD card plugged into the usb-reader. The
others like CF,Xd,MS are not detected as it seems, while the SD Card component
is indeed working as expected and seen in the log.
ST
Robert Hancock
> Hi
>> Well, the card reader apparently reports medium not present.. is there
>> anything in there? how is it not working?
> Just another information: It seems as if *only* the SD Card component of
> the reader is detected. This explains why there are only no medium present
> results in the calls. There was no SD card plugged into the usb-reader. The
> others like CF,Xd,MS are not detected as it seems, while the SD Card component
> is indeed working as expected and seen in the log.
It looks like this device is like a lot of other multi card-readers in
that it actually is 4 separate logical units (one for SD/MMC, one for
CF, one for SM/xD and one for MS). Each of them operates
independently, which is why you get (or should get) 4 separate drives
showing up. I'm still not sure what you're saying the problem is
though - you're not getting all of the drives detected? Can you post
the full dmesg from 2.6.32 when connecting the drive?
ST
> Can you post
> the full dmesg from 2.6.32 when connecting the drive?
from a Fedora 12 installation. Hopefully this is enough?
Mh, it seems as if the following lines are missing in the failing case?:
Initializing USB Mass Storage driver...
scsi8 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 6
usb-storage: waiting for device to settle before scanning
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usb-storage: device scan complete
Is there probably a wrong driver bound to the wrong driver?
(Didn't find anything suspicious under /sysfs)
Why is "usb_stor_init" not called?
I just tried to get a working kernel by using "make localyesconfig"
under fedora. But it still only detects the the SD card...
Thank you very much for your help.
ST
The Fedora 12 installation with 2.6.31.5-127.fc12.x86_64:
udev: starting version 145
usb 1-4.3: new high speed USB device using ehci_hcd and address 6
usb 1-4.3: New USB device found, idVendor=058f, idProduct=6364
usb 1-4.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 1-4.3: Product: Mass Storage Device
usb 1-4.3: Manufacturer: Generic
usb 1-4.3: SerialNumber: 058F63646476
usb 1-4.3: configuration #1 chosen from 1 choice
generic-usb: probe of 0003:058F:6364.0003 failed with error -22
Initializing USB Mass Storage driver...
scsi8 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 6
usb-storage: waiting for device to settle before scanning
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usb-storage: device scan complete
scsi 8:0:0:0: Direct-Access Generic- SD/MMC 1.00 PQ: 0 ANSI: 0
scsi 8:0:0:1: Direct-Access Generic- Compact Flash 1.01 PQ: 0 ANSI: 0
scsi 8:0:0:2: Direct-Access Generic- SM/xD-Picture 1.02 PQ: 0 ANSI: 0
scsi 8:0:0:3: Direct-Access Generic- MS/MS-Pro 1.03 PQ: 0 ANSI: 0
CCS
sd 8:0:0:0: Attached scsi generic sg3 type 0
sd 8:0:0:1: Attached scsi generic sg4 type 0
sd 8:0:0:2: Attached scsi generic sg5 type 0
sd 8:0:0:3: Attached scsi generic sg6 type 0
sd 8:0:0:2: [sde] Attached SCSI removable disk
sd 8:0:0:0: [sdc] Attached SCSI removable disk
sd 8:0:0:3: [sdf] Attached SCSI removable disk
sd 8:0:0:1: [sdd] 15858864 512-byte logical blocks: (8.11 GB/7.56 GiB)
sd 8:0:0:1: [sdd] Write Protect is off
sd 8:0:0:1: [sdd] Mode Sense: 03 00 00 00
sd 8:0:0:1: [sdd] Assuming drive cache: write through
sd 8:0:0:1: [sdd] Assuming drive cache: write through
sdd: sdd1 sdd2
sd 8:0:0:1: [sdd] Assuming drive cache: write through
sd 8:0:0:1: [sdd] Attached SCSI removable disk
The failure without usb block debug output:
hub 1-4:1.0: state 7 ports 4 chg 0000 evt 0008
hub 1-4:1.0: port 3, status 0101, change 0001, 12 Mb/s
hub 1-4:1.0: debounce: port 3: total 100ms stable 100ms status 0x101
hub 1-4:1.0: port 3 not reset yet, waiting 10ms
usb 1-4.3: new high speed USB device using ehci_hcd and address 6
hub 1-4:1.0: port 3 not reset yet, waiting 10ms
usb 1-4.3: skipped 1 descriptor after interface
usb 1-4.3: default language 0x0409
usb 1-4.3: udev 6, busnum 1, minor = 5
usb 1-4.3: New USB device found, idVendor=058f, idProduct=6364
usb 1-4.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 1-4.3: Product: Mass Storage Device
usb 1-4.3: Manufacturer: Generic
usb 1-4.3: SerialNumber: 058F63646476
usb 1-4.3: uevent
usb 1-4.3: usb_probe_device
usb 1-4.3: configuration #1 chosen from 1 choice
usb 1-4.3: adding 1-4.3:1.0 (config #1, interface 0)
usb 1-4.3:1.0: uevent
usb-storage 1-4.3:1.0: usb_probe_interface
usb-storage 1-4.3:1.0: usb_probe_interface - got id
scsi8 : usb-storage 1-4.3:1.0
usb 1-4.3: adding 1-4.3:1.1 (config #1, interface 1)
usb 1-4.3:1.1: uevent
usbhid 1-4.3:1.1: usb_probe_interface
usbhid 1-4.3:1.1: usb_probe_interface - got id
generic-usb: probe of 0003:058F:6364.0003 failed with error -22
drivers/usb/core/inode.c: creating file '006'
hub 1-4:1.0: state 7 ports 4 chg 0000 evt 0008
usb 1-4.3: uevent
scsi 8:0:0:0: Direct-Access Generic- SD/MMC 1.00 PQ: 0 ANSI: 0
sd 8:0:0:0: [sdc] Attached SCSI removable disk
usb 1-4.3:1.0: uevent
usb 1-4.3: uevent
usb 1-4.3:1.0: uevent
Robert Hancock
> Hi Robert
>> Can you post
>> the full dmesg from 2.6.32 when connecting the drive?
> The dmesg when connecting the drive is attached. This is
> from a Fedora 12 installation. Hopefully this is enough?
>
> Mh, it seems as if the following lines are missing in the failing case?:
> Initializing USB Mass Storage driver...
> scsi8 : SCSI emulation for USB Mass Storage devices
> usb-storage: device found at 6
> usb-storage: waiting for device to settle before scanning
> usbcore: registered new interface driver usb-storage
> USB Mass Storage support registered.
> usb-storage: device scan complete
>
> Is there probably a wrong driver bound to the wrong driver?
> (Didn't find anything suspicious under /sysfs)
> Why is "usb_stor_init" not called?
>
> I just tried to get a working kernel by using "make localyesconfig"
> under fedora. But it still only detects the the SD card...
>
> Thank you very much for your help.
> ST
>
Do you have CONFIG_SCSI_MULTI_LUN=y set in your kernel configuration?
ST
> Do you have CONFIG_SCSI_MULTI_LUN=y set in your kernel configuration?
be close to Darmstadt: I owe you a drink just drop me a mail.
To spare others this torment not to be able to configure their on kernel (well
at least partially) please change the defconfig to have CONFIG_SCSI_MULTI_LUN
enabled. Given the low price of these usb multi card readers this is quite a
common use case?
Best regards
ST
Signed-off-by: ST <s...@iss.tu-darmstadt.de>
diff --git a/arch/x86/configs/i386_defconfig b/arch/x86/configs/i386_defconfig
index d28fad1..053e8bf 100644
--- a/arch/x86/configs/i386_defconfig
+++ b/arch/x86/configs/i386_defconfig
@@ -847,7 +847,7 @@ CONFIG_CHR_DEV_SG=y
#
# Some SCSI devices (e.g. CD jukebox) support multiple LUNs
#
-# CONFIG_SCSI_MULTI_LUN is not set
+CONFIG_SCSI_MULTI_LUN=y
CONFIG_SCSI_CONSTANTS=y
# CONFIG_SCSI_LOGGING is not set
# CONFIG_SCSI_SCAN_ASYNC is not set
diff --git a/arch/x86/configs/x86_64_defconfig b/arch/x86/configs/x86_64_defconfig
index 6c86acd..3f64c27 100644
--- a/arch/x86/configs/x86_64_defconfig
+++ b/arch/x86/configs/x86_64_defconfig
@@ -842,7 +842,7 @@ CONFIG_CHR_DEV_SG=y
#
# Some SCSI devices (e.g. CD jukebox) support multiple LUNs
#
-# CONFIG_SCSI_MULTI_LUN is not set
+CONFIG_SCSI_MULTI_LUN=y
CONFIG_SCSI_CONSTANTS=y
# CONFIG_SCSI_LOGGING is not set
# CONFIG_SCSI_SCAN_ASYNC is not set