multi card reader not working

[Werner Schram]

Alan McKay wrote:
> On Wed, Dec 9, 2009 at 4:59 PM, Alan McKay <alan.mckay at gmail.com> wrote:
>   
>> I should probably boot the LIve CD right now and check again.   MIght do that.
>>     
>
> Nope, still does not work so it looks like I'll be taking it apart to
> try the MoBo trick.
>   
That could be a good idea. In the meantime, I'm still going to post my 
findings about the logs, because I was already typing them, and it would 
be a waste of precious bits to trow it away...

 If the reboot procedure doesn't work, you should have a deeper look at 
the dmesg, because I think you can find some more clues there.
A snip from your last mail:
> root at alan-ubuntu:~# dmesg | grep sd | grep -v sda | grep -v sdb |more
> [    1.333838] sd 1:0:0:0: Attached scsi generic sg0 type 0
> [    6.471418] type=1505 audit(1260320975.995:10):
> operation="profile_load" pid=482 name=/usr/sbin/cupsd
> [    6.593568] sd 8:0:0:0: Attached scsi generic sg2 type 0
> [   12.939735] type=1505 audit(1260320982.454:22):
> operation="profile_replace" pid=914 name=/usr/sbin/cu
> psd
> [  167.973434] sd 8:0:0:0: Device offlined - not ready after error recovery
> [  173.903101] sd 9:0:0:0: Attached scsi generic sg2 type 0
> [  674.443384] sd 10:0:0:0: Attached scsi generic sg2 type 0
>   
The message at 167.x might to be related, "sd 8:0:0:0" is initialized at 
6.x could you look if there is something between those messages that 
shows which error the 167.x line is refering to? After a reboot the 
times will be different, but I suspect you will find the same errors, 
unless of course the reboot with/without the device procedure worked.

>> and the output of the following command, a few seconds after you
>> inserted a card in the reader:
>> dmesg | tail -20
>>     
>
> This does not seem related :
> Dec  9 16:54:18 alan-ubuntu kernel: [74689.105321] sd 147:0:0:0:
> Attached scsi generic sg2 type 0
> Dec  9 16:54:18 alan-ubuntu kernel: [74689.116033] sd 147:0:0:0: [sdb]
> Attached SCSI removable disk
>   
The strange thing about these lines is that they refer to sg2 which is 
the same as the device found at 6.x, 173,x and 674.x. It seems that the 
device is repeatedly detected, fails and is redetected.

Werner