| Summary: | "modprobe -r snd-intel8x0" loops | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Sisyphus | Reporter: | Ivan Zakharyaschev <imz> | ||||||||
| Component: | module-init-tools | Assignee: | Alexey Gladkov <legion> | ||||||||
| Status: | CLOSED FIXED | QA Contact: | qa-sisyphus | ||||||||
| Severity: | major | ||||||||||
| Priority: | P2 | CC: | ldv, mike, shrek, vsu | ||||||||
| Version: | unstable | ||||||||||
| Hardware: | all | ||||||||||
| OS: | Linux | ||||||||||
| Attachments: |
|
||||||||||
|
Description
Ivan Zakharyaschev
2008-05-17 23:39:13 MSD
Created attachment 2630 [details]
typescript
My attempt to demonstrate the loop by --dry-run.
(In reply to comment #0) > Running "modprobe -r snd-intel8x0" causes something like an exponential forking. Perhaps I'm not right about "exponential" (in my typescript, I haven't explored the other call branches), but anyway it produces an infinitely growing number of modprobe processes. Created attachment 2631 [details]
modprobe-r-snd_intel8x0-v.err
To show what it looks like without --dry-run, the result of: modprobe -r
snd_intel8x0 -v &> modprobe-r-snd_intel8x0-v.err
At some moment, I started killing them.
Created attachment 2632 [details]
modprobe-r-snd-intel8x0.strace.bz2
The more real picture of the loop given by:
strace -fF -e trace=process modprobe -r snd-intel8x0 &>
modprobe-r-snd-intel8x0.strace
Perhaps it's a bug of /etc/modprobe.d/oss. $ rpm -qf /etc/modprobe.d/oss sound-scripts-0.50-alt1 $ sound-scripts-1.0.1-alt1 |