Description of problem: ssh'ing into a machine running 2.6.19-1.2891.fc7 produces the log messages attached to this bug. selinux is configured as permissive,targetted The ssh connection works afterwards. Version-Release number of selected component (if applicable): kernel-2.6.19-1.2891.fc7 How reproducible: Always Steps to Reproduce: 1. boot kernel 2. ssh into machine 3. Actual results: Expected results: Additional info:
Created attachment 144345 [details] dmesg output
I'm seeing exactly the same message when I logged into 2.6.19-1.2904.fc7 on x86_64, except its Xorg instead of ssh in dmesg output of comment#1. The system still boot and logon on to the desktop though, only that usb drives don't automount. Same usb drive automounts when booted into the 2.6.20rc3-rt kernel.
Created attachment 145073 [details] 2905 /var/log/messages 2905 /var/log/messages
today I caught same error as comment #1 with sendmail can also confirm with ssh also & kernel 2.6.19-1.2905. also all kernels since 2.6.18-1.2849.fc6 crash on exit only got 2 screenshots no logs may be related! full dmesg is included. hardware: athlon-xp 2500 NVidia nforce2 chipset.
Created attachment 145075 [details] kernel panic on shutdown
Created attachment 145076 [details] the other part of panic shot
dex, the 2 panics from comment 5 and 6 appear to be unrelated to this particular issues. would you mind filing them as a new BZ? As for the issues discovered by the lock dependancy code in comments 1 and 3 this should be resolved upstream. Until you get a fixed kernel it is possible your machine will deadlock. Test fedora kernels with a fix can be found at http://people.redhat.com/eparis/BZ220966 I am going to mark this bug as a dup of 220966 *** This bug has been marked as a duplicate of 220966 ***
2.6.19-1.2906.fc7 sorted the panic on shutdown from #5 #6(whoohoo!) testing kernel from comment #7 2.6.19-1.2906.fc7 didnt help lock dependancy still there. watching & reporting @ #220966 now.