How to kill SuSE 8.0 with 2 commands

Error Log for Thu, 20 Jun 2002 01:54:01 -0400: segfault in module 'flatfish+++' - dump details are as follows...

Wait, you're using it, but it won't stay up long enough to look at the logs?

Isn't that....well....contradictory? Which is it flatty?

That same exact update to alsa for SuSE 8.0 was the perfect thing for my system. I now have all four speakers working. No ill effects, nothing bad at all happened with my install of it. I'd bet there's something completely different that's actually messing up your system, maybe even something hardware related. Perhaps it's just that at that perfect time, a stick of RAM has gone bad? Or maybe something on the MOBO? I've learned from being a repairman for PC's, that those who don't use UPS's, will eventually have all manner of wierd things happen.

John

Error Log for Wed, 19 Jun 2002 23:30:48 -0400: segfault in module 'John B' - dump details are as follows...

Two commands???

Sounds like you've invented Linuxwhacking (see 'Googlewhacking' - in fact, you can Google for it!).

Why would that be so hard to believe? Drivers run in privileged mode and are a part of the kernel address space. Anything goes awry, and you may end up with kernel data structures corruption. Boom, kernel panic is here. I don't see anything that would be hard to believe. As for ALSA, it's still something that requires a lot of work. The only time I've managed to get to work almost properl (volume was extremely low with 7.3) , I had to compile from the source. That is why I am sticking to OSS. Works for me.

There is one bug still open accourding to alsa's bugzilla concerning the midiman 1010. http://sourceforge.net/tracker/?group_id=27464& atid=390601&func=detai...

Try running a non-smp kernel. Although the symptoms are a bit different than the ones you describe.. Have you considered reporting the bug to the alsa-developers/suse-developers? Or do you expect those developers to be reading cola? (although i don't think anyone will believe that installing alsa screwed up KDE/Gnome config... Just not possible.. They are entirely different systems. Alsaconfig won't do anything in $HOME/.kde or .gnome. Check the source)

[snip]

I'll grant you that, really I will. I'm a complete idiot who can install, upgrade, learn and use Linux without constantly destroying my system.

On a flatfish I.Q. scale (ranging from flatfish to idiot) that puts me in the above average range.

flatfish utter moron imbecile dumbass complete idiot idiot

Yeah, I can live with that.

You do know, that it will never get fixed?

Unless offcourse, you file a bugreport/suportrequest at suse/alsa.. and include a bit more information that you did here... What did the logs say, which kernel panic did you get, what filesystem are you using, what if you do a custom-compile of alsa, ... And you can say what you want, but it is very strange that an audio-subsystem was able to screw your filesystem... Even if it *is* inside the kernel... (although I doubt than inside a 2.4 kernel, it's anything more than a module. It will be integrated in the 2.6 kernel, but not yet in the 2.4)

Well either you have oss, or alsa, or alsa with an oss module loaded. Check again if it really is oss, or alsa-with-oss-emulation. Maybe suse shipped xmms with an alsa0.5 output plugin, instead of an alsa0.9? Did you try other programs? mpg321 for example?

If it is a bad output-plugin in xmms, report the bug.. Suse will fix it, and you'll get your fix in the suse-update-agent..