Created attachment 59362 [details] dmesg for hotplugged case The 2.6.39 debian standard kernel recognized the Silicon Image based Delock ExpressCard eSATA controller 34mm when inserted upon boot. When I remove it then, I see 05:00.0 Mass storage controller [0180]: Silicon Image, Inc. SiI 3531 [SATALink/SATARaid] Serial ATA Controller [1095:3531] (rev ff) (prog-if ff) !!! Unknown header type 7f Kernel driver in use: sata_sil24 00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 10: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 20: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff as traces from the card. I do not see any trace of the card when I insert it after boot. I am running martin@merkaba:~> cat /proc/version Linux version 2.6.39-1-amd64 (Debian 2.6.39-1) (buildd_amd64-brahms@buildd.debian.org) (gcc version 4.4.6 (Debian 4.4.6-3) ) #1 SMP Tue May 24 14:34:19 UTC 2011 I can try with a vanilla upstream kernel, but I doubt it will make any difference. I will attach lspci -nnnvvvxxx and dmesg for hotplugged, coldplug and coldplug and removed case. Well the dmesg for coldplug and coldplug and removed case is the same except an additional: [ 299.280535] [Hardware Error]: Machine check events logged I do not know whether that is really related to the removal of the card. After I removed it once more I didn´t see another one of these error messages.
Created attachment 59372 [details] lspci -nnnvvvxxx for hotplugged case
Created attachment 59382 [details] dmesg for coldplugged case
Created attachment 59392 [details] lspci -nnnvvvxxx for coldplugged case
Created attachment 59402 [details] lspci -nnnvvvxxx for coldplugged and then removed case dmesg is the same as for coldplugged case, except for an additional: [ 299.280535] [Hardware Error]: Machine check events logged I am not 100% sure whether this message is related to the Express Card removal.
Created attachment 59432 [details] dmesg of cold plug with drive attached to Express Card eSATA adapter The controller also does not work after a hibernation cycle with in-kernel-suspend. When I plug in a 2,5 inch eSATA drive there is nothing in dmesg. When I reboot, then the drive is properly recognized. I can open an extra bug for that if needed.
Created attachment 59442 [details] dmidecode for coldplug case I guess it doesn´t change for the hotplug case, the ExpressCard slot is shown in the hotplug case as well. If you wonder about that internal eSATA/USB combo port: Lenovo model managers decided it would be a good idea to only enable it with a suitable socket when one pays for the NVidia Optimus model. So currently it only works via the Minidock. Without that IMHO stupid decision I wouldn´t be trying that ExpressCard stuff at all.
The message May 25 19:21:18 merkaba kernel: [ 1047.585158] [Hardware Error]: Machine check events logged is unrelated to this bug. I had it another time while the card was still inserted and it didn´t occur when I remove it.
Well it works when I load acpiphp module as an reader of the Linux ThinkPad mailing list tolds me. So its not a kernel issue but maybe an udev issue for not autoloading that module on this hardware. martin@merkaba:~> lsmod | grep acpiphp martin@merkaba:~> su - Passwort: merkaba:~> modprobe acpiphp merkaba:~> lsmod | grep acpiphp acpiphp 22422 0 pci_hotplug 26711 1 acpiphp merkaba:~> tail -fn0 /var/log/syslog May 26 19:21:09 merkaba kernel: [27232.929058] pci 0000:05:00.0: [1095:3531] type 0 class 0x000180 May 26 19:21:09 merkaba kernel: [27232.929124] pci 0000:05:00.0: reg 10: [mem 0x00000000-0x0000007f 64bit] May 26 19:21:09 merkaba kernel: [27232.929173] pci 0000:05:00.0: reg 18: [mem 0x00000000-0x00001fff 64bit] May 26 19:21:09 merkaba kernel: [27232.929206] pci 0000:05:00.0: reg 20: [io 0x0000-0x007f] May 26 19:21:09 merkaba kernel: [27232.929338] pci 0000:05:00.0: supports D1 D2 May 26 19:21:09 merkaba kernel: [27232.929729] pci 0000:05:00.0: BAR 2: assigned [mem 0xd1d00000-0xd1d01fff 64bit] May 26 19:21:09 merkaba kernel: [27232.929759] pci 0000:05:00.0: BAR 2: set to [mem 0xd1d00000-0xd1d01fff 64bit] (PCI address [0xd1d00000-0xd1d01fff]) May 26 19:21:09 merkaba kernel: [27232.929773] pci 0000:05:00.0: BAR 0: assigned [mem 0xd1d02000-0xd1d0207f 64bit] May 26 19:21:09 merkaba kernel: [27232.929798] pci 0000:05:00.0: BAR 0: set to [mem 0xd1d02000-0xd1d0207f 64bit] (PCI address [0xd1d02000-0xd1d0207f]) May 26 19:21:09 merkaba kernel: [27232.929808] pci 0000:05:00.0: BAR 4: assigned [io 0x4000-0x407f] May 26 19:21:09 merkaba kernel: [27232.929824] pci 0000:05:00.0: BAR 4: set to [io 0x4000-0x407f] (PCI address [0x4000-0x407f]) May 26 19:21:09 merkaba kernel: [27232.929850] pci 0000:05:00.0: no hotplug settings from platform May 26 19:21:09 merkaba kernel: [27232.960711] sata_sil24 0000:05:00.0: version 1.1 May 26 19:21:09 merkaba kernel: [27232.960741] sata_sil24 0000:05:00.0: enabling device (0000 -> 0003) May 26 19:21:09 merkaba kernel: [27232.960763] sata_sil24 0000:05:00.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19 May 26 19:21:09 merkaba kernel: [27232.960898] sata_sil24 0000:05:00.0: setting latency timer to 64 May 26 19:21:09 merkaba kernel: [27232.961640] scsi6 : sata_sil24 May 26 19:21:09 merkaba kernel: [27232.961849] ata7: SATA max UDMA/100 host m128@0xd1d02000 port 0xd1d00000 irq 19 May 26 19:21:11 merkaba kernel: [27235.036080] ata7: SATA link down (SStatus 0 SControl 0) May 26 19:21:17 merkaba kernel: [27240.876027] sata_sil24 0000:05:00.0: PCI INT A disabled ---------- Weitergeleitete Nachricht ---------- Subject: [ltp] Re: eSATA controller Express Card in ThinkPad T520 not working Date: Donnerstag, 26. Mai 2011 From: Bjørn Mork [...] To: linux-thinkpad [...] Martin Steigerwald [...] writes: > So indeed hotplug does not seem to work. Anyway, I want to have it > permanently installed, so this will do for now. Do you have acpiphp loaded? Bjørn -- The linux-thinkpad mailing list home page is at: http://mailman.linux-thinkpad.org/mailman/listinfo/linux-thinkpad ------------------------------------------------------- http://mailman.linux-thinkpad.org/pipermail/linux-thinkpad/2011-May/049768.html Thus closing. Should it continue not to work after a resume I will open a new bug for that. Thanks.