https://bugzilla.novell.com/show_bug.cgi?id=406832 Robert Vojcik changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.provo.novell.com |kernel-maintainers@forge.provo.novell.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=406832 User nfbrown@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=406832#c1 Neil Brown changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |petersed@uwosh.edu --- Comment #1 from Neil Brown 2008-08-11 19:44:02 MDT --- That does look like a strange bug. Given how repeatable it appears to be, I would expect someone else to have found and even fixed it, but I cannot find and evidence of that. Would you be able to get an 'strace' of the two 'rpc.gssd's ? i.e. killall rpc.gssd strace -o /tmp/trace1 -s 200 rpc.gssd -f # in other window mount ... # back to first window Interrupt strace -o /tmp/trace1 -s 200 rpc.gssd -f .. wait for mount to succeed Interrupt and attach the two traces. Thanks. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=406832 User petersed@uwosh.edu added comment https://bugzilla.novell.com/show_bug.cgi?id=406832#c3 --- Comment #3 from Dan Petersen 2008-08-12 07:56:31 MDT --- Created an attachment (id=232963) --> (https://bugzilla.novell.com/attachment.cgi?id=232963) Trace #2 - rpc.gssd started after mount -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=406832 User petersed@uwosh.edu added comment https://bugzilla.novell.com/show_bug.cgi?id=406832#c5 Dan Petersen changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|petersed@uwosh.edu | --- Comment #5 from Dan Petersen 2008-11-10 08:09:40 MST --- I started the mount, found the PID of rpc.gssd, and sent it a kill -37. The mount still wouldn't complete. Killing it off and restarting it still does complete as per the original report, so the latest software updates haven't changed the behavior. Here is a "cat /proc/self/status": Name: cat State: R (running) Tgid: 3343 Pid: 3343 PPid: 3222 TracerPid: 0 Uid: 0 0 0 0 Gid: 0 0 0 0 FDSize: 256 Groups: 0 VmPeak: 1940 kB VmSize: 1940 kB VmLck: 0 kB VmHWM: 504 kB VmRSS: 504 kB VmData: 152 kB VmStk: 84 kB VmExe: 20 kB VmLib: 1376 kB VmPTE: 16 kB Threads: 1 SigQ: 0/8192 SigPnd: 0000000000000000 ShdPnd: 0000000000000000 SigBlk: fffffffe00000000 SigIgn: 0000000000000000 SigCgt: 0000000000000000 CapInh: 0000000000000000 CapPrm: ffffffffffffffff CapEff: ffffffffffffffff voluntary_ctxt_switches: 2 nonvoluntary_ctxt_switches: 1 Did you mean "cat /proc//status"? Here's that, in case: Name: cat State: R (running) Tgid: 3343 Pid: 3343 PPid: 3222 TracerPid: 0 Uid: 0 0 0 0 Gid: 0 0 0 0 FDSize: 256 Groups: 0 VmPeak: 1940 kB VmSize: 1940 kB VmLck: 0 kB VmHWM: 504 kB VmRSS: 504 kB VmData: 152 kB VmStk: 84 kB VmExe: 20 kB VmLib: 1376 kB VmPTE: 16 kB Threads: 1 SigQ: 0/8192 SigPnd: 0000000000000000 ShdPnd: 0000000000000000 SigBlk: fffffffe00000000 SigIgn: 0000000000000000 SigCgt: 0000000000000000 CapInh: 0000000000000000 CapPrm: ffffffffffffffff CapEff: ffffffffffffffff voluntary_ctxt_switches: 2 nonvoluntary_ctxt_switches: 1 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=406832 User petersed@uwosh.edu added comment https://bugzilla.novell.com/show_bug.cgi?id=406832#c7 Dan Petersen changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|petersed@uwosh.edu | --- Comment #7 from Dan Petersen 2008-11-11 08:24:42 MST --- This is interesting. In looking through /proc/*/status, the first PID with that signal mask is startkde. The terminal I open within KDE (KDE 3) then has that mask, and anything run inside it. I've always been starting NFS by hand within the terminal rather than automatically on boot. If I enable it for automatic startup, it works as expected. Obviously under normal conditions it would be started automatically anyway. I installed and tested the other GUI options to see how they behave. I'm logging in directly as "root" for each test: Gnome: NOT blocked IceWM: Blocked KDE3: Blocked KDE4: Blocked Metacity: Couldn't get a UI TWM: Blocked XFCE: Blocked Failsafe: NOT blocked No GUI (runlevel 3): NOT blocked SSH: NOT blocked If I log in to the text console in runlevel 3, then "startx" and get KDE3, it's not blocked. If I run "gdm" or "xdm" as the GUI login manager (instead of kdm) KDE still has the signals blocked when I log in. So it looks like this isn't a problem specific to rpc.gssd or NFS, it is a more generic problem with GUI logins. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=406832 User nfbrown@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=406832#c9 Neil Brown changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED --- Comment #9 from Neil Brown 2008-11-19 19:24:28 MST --- I have discussed this upstream and we will probably just unblock the signal just-in-case. I have applied this patch to the suse-11 package and it should be in factory in a day or two. Thanks. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.