Ubuntu 7.10 having random system failure on Gateway M350WVN (sound issue)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
alsa-driver (Ubuntu) |
Invalid
|
Medium
|
Unassigned |
Bug Description
I've encountered what I believe is an issue with the sound system. I've searched all over for a similar situation, but haven't come up with anything.
In short, Ubuntu 7.10 on my Gateway M350WVN laptop crashes when playing back audio.
In medium, any type of file with an audio elements plays fine (I get sound from speakers, headphones, volume works, etc.) but I'm getting sporadic crashes while the files are playing. I'm not sure exactly where the problem lies, whether in Ubunutu, GNOME, ALSA, the drivers, the kernel, or something combination. I've spent a lot of time testing to replicate the behavior, which is definitely possible. Unfortunately, this is the probably the most annoying kind of bug. It's intermittent, happens under a wide variety of circumstances, and is "fatal" to the system (complete and total lock).
In long, I've been looking over various troubleshooting and bug reporting guides getting a sense of what information is useful/necessary. Hopefully all of this will help nail down the issue and get it resolved. Here goes:
A.) System Specs
1.) machine: Gateway M350WVN laptop (http://
a.) Audio chipset: Sigmatel 174; Soft Audio AC97 rev 2.3 codec (STAC9752)
b.) Sound support: PCI interface audio, Multi-stream Direct Sound and Direct Sound 3D acceleration, SoundBlaster Pro, MIDI, Windows Sound System compatible, MP3, WMA, PCI Power Management Interface (PPMI) 1.1 compliant
c.) Volume controls: Volume control buttons on front of notebook, Volume control keys on keyboard, Software control provided through Windows
d.) Internal speakers: Stereo speakers built into front of notebook, 2 W maximum output
e.) Audio jacks: Stereo headphone output, Monophonic microphone input
2.) distro: Ubuntu 7.10
a.) Installed from LiveCD
b.) "Fresh" install except for enabling wireless, installing restricted-
c.) note that I replicated the crash before and after these changes (see below)
3.) kernel: Linux fd-ubuntu-lap 2.6.22-14-generic #1 SMP Tue Dec 18 08:02:57 UTC 2007 i686 GNU/Linux
4.) See below for files with complete output of commands like lspci, etc.
B.) Symptoms of Crash/Freeze/Lock
1.) sound stops playing, display freezes, no movement of mouse, no response from keyboard
2.) CTRL+ALT+Backspace does nothing
3.) toggling CAPSLOCK does nothing (light doesn't change)
4.) CTRL+ALT+F1 does nothing
5.) ALT+PrntScrn+reisub does nothing
6.) Fn keys, media keys, app buttons do nothing
7.) only way to get system back is to manually power cycle
8.) power cycling results in fsck saying volume not cleanly unmounted, runs a check, repairs, reboots successfully
C.) Replication
1.) crash after random interval during
a.) rhythmbox - streaming m3u over http
b.) rhythmbox - playing mp3 across ntfs partition
c.) rhythmbox - playing mp3 local to ext2 partition
d.) totem - playing DVD
e.) gxine - playing DVD
f.) login screen - entered correct user/pass, froze while playing login sound
g.) gnome-sound-
h.) gnome-sound-
2.) crash does NOT happen during
a.) any of the above cases while having the sound muted (whether from muting at a certain level, or turning volume all the way down)
D.) Testing
1.) memtest - 4.5 passes, 0 errors detected
2.) gdb backtrace - rhythmbox (local mp3s)
a.) first run - music played without crash for over an hour, but unable to generate report because entire system crashed, not just the application, once system rebooted (gdm) stated their was no data to gather into a report
3.) valgrind - rhythmbox (local mp3s)
a.) first run - system ran exceptionally slow, almost no sound actually made it to the speakers, music appeared to play for 45 minutes without crash, ended test, resulting file was so large I deleted it because the text editor choked a couple times trying to open it
b.) second run - system ran exceptionally slow, no sound came out of speakers, only let test run for a few minutes and manually closed rhythmbox, report successfully generated but obviously couldn't capture a crash event
c.) third run - as above, but locked up after about 3 seconds, no report generated because entire system crashed
4.) strace - rhythmbox (local mp3)
a.) first run - app ran for over an hour without crashing, ended test, strace generate 49.5mb file that choked anything that tried to open it
b.) second run - app crashed after about 10 minutes of play, but the file generated was corrupted during the crash such that I can't get it to open in any text editing program.
c.) third run - app ran for length of song, no crash, ended test, large file generated
d.) fourth run - same as third
5.) strace - gnome-sound-
a.) 14 runs w/o crash generated log files ranging from 1.7 to 5 MB
b.) 15th run, generated crash, corrupted file, ubunutu reports that .log file is .xml format and shouldn't be trusted, renamed to .xml and opened, contained some random stuff, but didn't resemble an strace log file at all, suggests file was corrupted similar to the one generated with rhythmbox
6.) /var/crash directory is completely empty
E.) Generated Files in M350WVN-
1.) commands run & their output
a.) uname -a > M350WVN-uname.txt
b.) sudo lspci -vvnn > M350WVN-
c.) lsmod > M350WVN-
d.) dmesg > M350WVN-
e.) tail -2 /proc/asound/
f.) amixer > M350WVN-amixer.txt
g.) asoundconf list > M350WVN-
h.) cat /proc/interrupts > M350WVN-
i.) top -b -n3 > M350WVN-top.log
j.) sudo dmidecode > M350WVN-
2.) script/program output
a.) M350WVN-
b.) M350WVN-
c.) M350WVN-
d.) M350WVN-
e.) **M350WVN-
f.) M350WVN-
g.) **M350WVN-
h.) **M350WVN-
i.) **M350WVN-
j.) M350WVN-
3.) images (hosted by imageshack.us, sorry for poor quality, some were spliced together from cell phone pics)
a.) screen photo of crash with top running (http://
b.) resulting fsck photo (http://
c.) fsck screen photo after test sound crashing without strace running (http://
d.) fsck screen photo after crashing during M350WVN-
F.) Listings (concurrently posted and watched at)
1.) http://
2.) https:/
3.) https:/
4.) http://
Here is the archive mentioned in the initial posting.