Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#9810 - Kernel 2.6.24, Arch64 - buggy

Attached to Project: Arch Linux
Opened by Vladimir (vlstefanovic) - Tuesday, 11 March 2008, 01:12 GMT
Last edited by Tobias Powalowski (tpowa) - Wednesday, 12 March 2008, 18:22 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To No-one
Architecture x86_64
Severity Critical
Priority Normal
Reported Version 2007.08-2
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
I've just updated kernel (I'm using Arch64), and it appeared to work all normal. After about an hour, I noticed that 'mercury' is not working (msn program in Java). Then I opened 'ksysguardd' to view processes, and the list was empty. Then tried 'ps ax' and neither do 'ps' worked correctly. 'ps' lists most of the processes, but not all and doesn't exits, just stays hanging in the middle of the list. vt1 shows some kernel messages.
Generally, system is not frozen, but "buggy".

Additional info:
* package version(s)
* config and/or log files etc.
2.6.24-ARCH

Steps to reproduce:
Boot system. Start 'mercury'
   kernel.log (128.5 KiB)
This task depends upon

Closed by  Tobias Powalowski (tpowa)
Wednesday, 12 March 2008, 18:22 GMT
Reason for closing:  Not a bug
Comment by Vladimir (vlstefanovic) - Tuesday, 11 March 2008, 01:26 GMT
No, I've tried again, and just started KDE and kernel says oops.
Comment by Pierre Schmitz (Pierre) - Tuesday, 11 March 2008, 09:54 GMT
Try using a non-tainted kernel (e.g. use vesa instead of fglrx).
Comment by Jan de Groot (JGC) - Tuesday, 11 March 2008, 17:03 GMT
Not actually a 2.6.24 issue, but just another snd-hda-intel ALSA driver bug. I don't think a tainted kernel has anything to do with it.
Comment by Pierre Schmitz (Pierre) - Tuesday, 11 March 2008, 22:02 GMT
Ah, I think you are right. I just saw the fglrx errors.
Comment by Vladimir (vlstefanovic) - Wednesday, 12 March 2008, 18:08 GMT
Yes, it appears to be snd-hda-intel related. I just removed all snd* modules and everything seems to be ok.
Comment by Tobias Powalowski (tpowa) - Wednesday, 12 March 2008, 18:09 GMT
you could try to use special parameter with this module to get it working, it's a trial and error thing.
Comment by Vladimir (vlstefanovic) - Wednesday, 12 March 2008, 18:21 GMT
It's working now, I forgot that I compiled driver for my sound card. My fault, sorry for disturbing. Thanks.

Loading...