* 2.6.9 + SMT + MPEG transcoding = Hardlock?
@ 2004-10-21 18:43 Troy McFerrron
0 siblings, 0 replies; only message in thread
From: Troy McFerrron @ 2004-10-21 18:43 UTC (permalink / raw)
To: linux-kernel
When 2.6.9-rc1 came around, I tried it and had hardlocks with the SMT
scheduler enabled. 2.6.9-rc2 had the same issue.
2.6.9 rc-3 fixed the issue.
2.6.9 "stable" brought it back.
It mainly manifests itself when using transcode to encode vobs to
MPEG. It doesn't happen with 2.6.8.1, 2.6.9-rc3, but does happen with
everything between and after. (Though I didn't try RC-4. I was happy
with RC3.)
When I say hardlock, I mean hardlock. No reponse from the system at
all. If audio is playing, it loops.
Are there specific changes I could roll back in 2.6.9 to make it
viable and stable on ym system? I'm not willing to give up SMT, but
want to keep my kernel current. Can anyone reproduce these lockups?
--
Troy McFerron
Kernel Ricer and Linux Hobbyist.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2004-10-21 18:52 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-10-21 18:43 2.6.9 + SMT + MPEG transcoding = Hardlock? Troy McFerrron
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.