I get a hard lockup when trying to play a mp3 with XMMS;
Sound Blaster Live card. The first second loops, and I lose all
connectivity to the machine; I can't ping it, can't to a an Alt-Sysq,
nothing.
Details:
running RedHat 7.0
using kernel 2.4.0-test11pre4
emu10k1 compiled as a module
system is a Dell Dimension 4100 (815e based, 512mb ram, 3com 3c905c cardA)
I'll try to compile in soundcore and emu10k1 into the kernel, foregoing
any modules and see if that helps. I will also revert back to
2.4.0-test10 as well just to test. If anyone needs further information,
let me know.
Thanks,
Will Sarka
--
---------------------------------------------
Those, who would give up essential liberty to
purchase a little temporary safety, deserve
neither liberty nor safety.
-Ben Franklin
Historical Review of Constitution and
Government of Pennsylvania
---------------------------------------------
On Mon, 13 Nov 2000, Willis L. Sarka wrote:
> I get a hard lockup when trying to play a mp3 with XMMS;
> Sound Blaster Live card. The first second loops, and I lose all
> connectivity to the machine; I can't ping it, can't to a an Alt-Sysq,
> nothing.
Just for reference, I've been use the ALSA drivers for most of the
2.4.0-testX kernels without any problems (provided you use the driver
version that matches the kernel version). Even under high memory
preasure, swapping, NFS traffic, etc. the worst that happens is sporadic
skipping. XMMS and mpg123 in use. I've tried the kernel emu10k1 a few
times but also got similar lockup's. I haven't tried the kernel emu10k1
since the NMI watchdog was added. This should show something? ... but
I guess you can't see anything because you're in X. I wonder if you'd see
anything if you were using mpg123 and working on the console?
My system:
RedHat 7.0
kernel 2.4.0-test11pre3 SMP (soundcore as modules)
ALSA drivers 0.5.9d
Gigabyte 440BX SMP (Dual Pentium II 450), 256MB,
Intel Ethernet Pro 100, Adaptec AIC-7895 Ultra SCSI
--
Hans Grobler <[email protected]>
Department Electronic & Electrical Engineering
University of Stellenbosch, South Africa
On Mon, 13 Nov 2000, Hans Grobler wrote:
> On Mon, 13 Nov 2000, Willis L. Sarka wrote:
> > I get a hard lockup when trying to play a mp3 with XMMS;
> > Sound Blaster Live card. The first second loops, and I lose all
> > connectivity to the machine; I can't ping it, can't to a an Alt-Sysq,
> > nothing.
>
> Just for reference, I've been use the ALSA drivers for most of the
> 2.4.0-testX kernels without any problems (provided you use the driver
> version that matches the kernel version). Even under high memory
> preasure, swapping, NFS traffic, etc. the worst that happens is sporadic
> skipping. XMMS and mpg123 in use. I've tried the kernel emu10k1 a few
> times but also got similar lockup's.
Which was the latest kernel you tried? A (easy to trigger) deadlock was
fixed around 2.4.0-test...
Rui Sousa
On Mon, 13 Nov 2000, Willis L. Sarka wrote:
> I get a hard lockup when trying to play a mp3 with XMMS;
> Sound Blaster Live card. The first second loops, and I lose all
> connectivity to the machine; I can't ping it, can't to a an Alt-Sysq,
> nothing.
Is this when you try to play something for the first time or
it just happens sometimes?
> Details:
>
> running RedHat 7.0
> using kernel 2.4.0-test11pre4
> emu10k1 compiled as a module
> system is a Dell Dimension 4100 (815e based, 512mb ram, 3com 3c905c cardA)
>
> I'll try to compile in soundcore and emu10k1 into the kernel, foregoing
> any modules and see if that helps. I will also revert back to
> 2.4.0-test10 as well just to test.
Yes, it would be good to know when the problems started.
> If anyone needs further information,
> let me know.
What is the output of:
/sbin/lspci -v
Rui Sousa
Rui Sousa wrote:
>
> On Mon, 13 Nov 2000, Willis L. Sarka wrote:
>
> > I get a hard lockup when trying to play a mp3 with XMMS;
> > Sound Blaster Live card. The first second loops, and I lose all
> > connectivity to the machine; I can't ping it, can't to a an Alt-Sysq,
> > nothing.
>
> Is this when you try to play something for the first time or
> it just happens sometimes?
>
> > Details:
> >
> > running RedHat 7.0
> > using kernel 2.4.0-test11pre4
> > emu10k1 compiled as a module
> > system is a Dell Dimension 4100 (815e based, 512mb ram, 3com 3c905c cardA)
> >
> > I'll try to compile in soundcore and emu10k1 into the kernel, foregoing
> > any modules and see if that helps. I will also revert back to
> > 2.4.0-test10 as well just to test.
>
> Yes, it would be good to know when the problems started.
>
> > If anyone needs further information,
> > let me know.
Well, just as a note:
I'm using the same (software-) setup as above, only difference is that
the emu10k1 driver is compiled into the kernel and I have no problems
with xmms whatsoever.
Juri
On Tue, 14 Nov 2000, Rui Sousa wrote:
> Which was the latest kernel you tried? A (easy to trigger) deadlock was
> fixed around 2.4.0-test...
It was around test7... I think. I remember seeing changes to emu10k1 in
the patch and I tried that version. It still crashed. I work almost
exclusively command line and saw no kernel error messages. The system
simply locked up and did not respond to SysRq etc.
I'll try test11-pre5 today.
-- Hans
Just as another data point, I, too, had trouble with lockups with the
emu10k1 (with the 2.4.0-test driver and ALSA both). I noticed that it was
sharing an interrupt with ACPI. As soon as I rebuilt the kernel with the
ACPI Interpreter option turned off, the problem went away.
It's not the first time I've gotten burned with the "turn on some option
because I might want to mess with it someday" approach to kernel
configuration...
jon
On Wed, 15 Nov 2000, Jonathan Corbet wrote:
> Just as another data point, I, too, had trouble with lockups with the
> emu10k1 (with the 2.4.0-test driver and ALSA both). I noticed that it was
> sharing an interrupt with ACPI. As soon as I rebuilt the kernel with the
> ACPI Interpreter option turned off, the problem went away.
In my case, the emu10k1 has an IRQ all to itself... (and I don't have
ACPI enabled).
Been running the kernel emu10k1 on test11-pre5 since this morning.
I've only had one lockup (older testX emu10k1's locked up more
frequently). So there still appears to be a problem with (or triggered by)
test11-pre5 emu10k1. As I was under X at that stage (XMMS & two xterms), I
did not see any panic()'s or BUG()'s.
Next I'm going to compile with serial console & see if I can see any
panic() or BUG()s.
-- Hans.