Bug 249048

I would like to see dmesg taken after the insertion.

this is shortly after boot:

audit(1185041526.584:2): audit_pid=2017 old=0 by auid=4294967295
Bluetooth: Core ver 2.11
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Bluetooth: L2CAP ver 2.8
Bluetooth: L2CAP socket layer initialized
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: RFCOMM ver 1.8
Bluetooth: HIDP (Human Interface Emulation) ver 1.2
i2c_adapter i2c-2: SMBus Quick command not supported, can't probe for chips
w83627ehf: unsupported chip ID: 0xffff
eth0: no IPv6 routers present
NET: Registered protocol family 4
NET: Registered protocol family 5


so nothing to work on I guess.

Anyway since then I upgraded to kernel-2.6.22.1-27.fc7 and it work well again.

And this is what I get in 2.6.22.1, dmesg, messages

NET: Registered protocol family 5
sd 6:0:0:0: [sdc] 31488 512-byte hardware sectors (16 MB)
sd 6:0:0:0: [sdc] Write Protect is off
sd 6:0:0:0: [sdc] Mode Sense: 02 00 00 00
sd 6:0:0:0: [sdc] Assuming drive cache: write through
sd 6:0:0:0: [sdc] 31488 512-byte hardware sectors (16 MB)
sd 6:0:0:0: [sdc] Write Protect is off
sd 6:0:0:0: [sdc] Mode Sense: 02 00 00 00
sd 6:0:0:0: [sdc] Assuming drive cache: write through
 sdc: sdc1




Jul 21 20:27:02 hal9000 kernel: sd 6:0:0:0: [sdc] 31488 512-byte hardware
sectors (16 MB)
Jul 21 20:27:02 hal9000 kernel: sd 6:0:0:0: [sdc] Write Protect is off
Jul 21 20:27:02 hal9000 kernel: sd 6:0:0:0: [sdc] Assuming drive cache: write
through
Jul 21 20:27:02 hal9000 kernel: sd 6:0:0:0: [sdc] 31488 512-byte hardware
sectors (16 MB)
Jul 21 20:27:02 hal9000 kernel: sd 6:0:0:0: [sdc] Write Protect is off
Jul 21 20:27:02 hal9000 kernel: sd 6:0:0:0: [sdc] Assuming drive cache: write
through
Jul 21 20:27:02 hal9000 kernel:  sdc: sdc1
Jul 21 20:27:15 hal9000 automount[2373]: lookup_mount: >> /usr/sbin/showmount:
can't get address for .directory
Jul 21 20:27:16 hal9000 hald: mounted /dev/sdc1 on behalf of uid 500

Please attach the COMPLETE dmesg. I'd like to see if we enabled ub by accident.
Please do not drop it into comments box.

Created attachment 159736 [details]
dmesg output

output from dmesg after boot and inserting of a cf card

Hello,

I'm reviewing this bug as part of the kernel bug triage project, an attempt to
isolate current bugs in the fedora kernel.

http://fedoraproject.org/wiki/KernelBugTriage

I am CC'ing myself to this bug and will try and assist you in resolving it if I can.

There hasn't been much activity on this bug for a while. Could you tell me if
you are still having problems with the latest kernel?

If the problem no longer exists then please close this bug or I'll do so in a
few days if there is no additional information lodged.

Cheers
Chris

Latest 2.6.22.x kernels are working fine. I thought no new information is needed
after I attached full dmesg output. Feel free to close the bug. However I have
no idea what went wrong with the particular kernel release.

I can't shed any light on it - I also had the same problem with previous
kernels. Please re-open if you experience a regression of course. Thanks for the
update.

Cheers
Chris