Skip to contentSkip to conversation

Kernel Oops with 2.6.23

Suspend-devel Ritesh Raj Sarraf 2 participants 2 messages Dec 17, 2007 – Dec 26, 2007 3 messages not in the archive

lore
Share & tools
lore
#3 lore raw
In reply to a message not in the archive
Quoted 27 lines · Pavel Machek
Quoted 26 lines · Ritesh Raj Sarraf
Quoted 3 lines · Pavel Machek

killall -9 pulseaudio. If pulseaudio is not dead within 60 seconds, you hit a kernel bug. If it needs suspend to be reproduced, you probably have a suspend bug.

Hi Pavel,

Something similar to this are multiple cases where the kernel is not able to kill a process at all.

A good example is an application pumping IO to a multipathed device. When all the paths to the multipathed devices go down, and you'd like to kill the process, there is no way left to do it. In fact, a reboot also doesn't work in such cases. Reboot gets hung in midway trying to kill the process. The user is left to do a hard reset of the machine.

In situations like these, the processes go into D state.

Here's what the manpage of ps says:

PROCESS STATE CODES
Here are the different values that the s, stat and state output
specifiers (header "STAT" or "S")
will display to describe the state of a process.
D Uninterruptible sleep (usually IO)

Quoted 5 lines
Quoted 2 lines

Does it mean that processes in D state are excluded by the kernel from being killed ? Or is it still a kernel bug ?

Still a kernel bug. Processes should not stay in D state for long.
Pavel

Hi Pavel,

Sometime back we discussed about 'D' state processes which are not killed by the kernel by any signal.

Here's a bugzilla detailing the symptom.
https://bugzilla.redhat.com/show_bug.cgi?id=419581
[I/O Processes don't get killed when all the paths to the LUN are down]

It is still being assumed as working as designed.

Ritesh

Signature · 3 lines
Ritesh Raj Sarraf
RESEARCHUT - http://www.researchut.com
"Necessity is the mother of invention."
#4 lore raw
Quoted 36 lines · Ritesh Raj Sarraf
Quoted 27 lines · Pavel Machek
Quoted 26 lines · Ritesh Raj Sarraf
Quoted 3 lines · Pavel Machek

killall -9 pulseaudio. If pulseaudio is not dead within 60 seconds, you hit a kernel bug. If it needs suspend to be reproduced, you probably have a suspend bug.

Hi Pavel,

Something similar to this are multiple cases where the kernel is not able to kill a process at all.

A good example is an application pumping IO to a multipathed device. When all the paths to the multipathed devices go down, and you'd like to kill the process, there is no way left to do it. In fact, a reboot also doesn't work in such cases. Reboot gets hung in midway trying to kill the process. The user is left to do a hard reset of the machine.

In situations like these, the processes go into D state.

Here's what the manpage of ps says:

PROCESS STATE CODES
Here are the different values that the s, stat and state output
specifiers (header "STAT" or "S")
will display to describe the state of a process.
D Uninterruptible sleep (usually IO)

Quoted 5 lines
Quoted 2 lines

Does it mean that processes in D state are excluded by the kernel from being killed ? Or is it still a kernel bug ?

Still a kernel bug. Processes should not stay in D state for long.
Pavel

Hi Pavel,

Quoted 8 lines

Sometime back we discussed about 'D' state processes which are not killed by the kernel by any signal.

Here's a bugzilla detailing the symptom.
https://bugzilla.redhat.com/show_bug.cgi?id=419581
[I/O Processes don't get killed when all the paths to the LUN are down]

It is still being assumed as working as designed.

This is borderline.

I guess multipath should use new TASK_KILLABLE infrastructure, but I do not expect RedHat to backport that.

Feel free to implement that yourself, it should be quite easy.
Pavel

Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html