Red Hat Bugzilla – Bug 121601
(SND NM256) 2.6.5-1.327 snd-nm256 module hangs Dell Latitidue LS (PP01S)
Last modified: 2007-11-30 17:10:41 EST
using i686 2.6.5-1.327 kernel, anything happening to load the
snd-nm256 module will completely freeze the machine.
Machine is a PIII-500 with NeoMagic MagicMedia256 sound card/GPU.
kernels back to 2.6.5-1.315 also freeze
Arjan - this is almost certainly the Dell audio setup bug that was
fixed in OSS. If you look over the initial setup code in the oss
driver you'll see that over time one I/O was removed because it hangs
There's a handily named flag chip->latitude_workaround which isn't
being activated for all Dell Laptops as it has a rather narrow check:
It seems that if one sets the flag to zero then the workaround works?!
Anyway maybe someone should look into making it a wider check or a
module argument that can be set on loading.
For Latitude LS I have:
Subsystem Vendor: 0x1028
Subsystem Device: 0x0080
Created attachment 101116 [details]
Don't use workaround on PP01S
Rediffed and posted upstream
Bug has been fixed for a bit, but patch is verified upstream and in
Bug still affects Latitude CSx on kernel 2.6.9-1.667
pci bus 0x0001 cardnum 0x00 function 0x00: vendor 0x10c8 device 0x0006
Neomagic Corporation NM2360 [MagicMedia 256ZX]
pci bus 0x0001 cardnum 0x00 function 0x01: vendor 0x10c8 device 0x8006
Neomagic Corporation NM2360 [MagicMedia 256ZX Audio]
Did you find a workaround for the bug on the CSx?
I have the same problem. I am using the kernel 2.6.11 (CSx).
I have tried the patch provided above, but it doesn't apply on my nm256.c file.
Can you try the patch in the next comment instead and see if that seems to fix
the issue? Could you also post the result of:
lspci | grep Neomagic
Created attachment 114912 [details]
Use nm256 workaround on Latitude CSx too
patrick: can you try to apply this and see if that does anything?
Another interesting reference:
The patch could be applied successfuly. I am presently compiling the kernel. I
let you know if that fix the problem.
The result of the command is:
# lspci | grep Neomagic
0000:01:00.0 VGA compatible controller: Neomagic Corporation NM2360 [MagicMedia
0000:01:00.1 Multimedia audio controller: Neomagic Corporation NM2360
[MagicMedia 256ZX Audio]
Could you also now post the output of "lspci -n" as well so I can be sure the
Neomagic device numbers are correct for the patch I posted?
I have since shifted the Latitude CSx mentioned above to RHEL 4 WS with kernel
2.6.9-5.0.5.EL and the problem still exists. With RHEL 4 WS being a flagship
product and Dell being a favoured partner, this does seem a little sad.
As a subscriber I have raised this against RHEL 4 as bug number 158989
Here is the result of the command:
# lspci -n
0000:00:00.0 Class 0600: 8086:7190 (rev 03)
0000:00:01.0 Class 0604: 8086:7191 (rev 03)
0000:00:03.0 Class 0607: 104c:ac1c (rev 01)
0000:00:03.1 Class 0607: 104c:ac1c (rev 01)
0000:00:07.0 Class 0680: 8086:7110 (rev 02)
0000:00:07.1 Class 0101: 8086:7111 (rev 01)
0000:00:07.2 Class 0c03: 8086:7112 (rev 01)
0000:00:07.3 Class 0680: 8086:7113 (rev 03)
0000:01:00.0 Class 0300: 10c8:0006
0000:01:00.1 Class 0401: 10c8:8006
patrick: did this patch end up fixing the issue?
I don't think so. I still get freeze at startup. Did it work for you?
Hmm, I'm kind of out of ideas on this one then... without the specific hardware
its a bit hard to nail down.
One more thing though, can you try setting "vaio_hack=1" as a module parameter.
Does that help at all? The vaios that setting is supposed to be for also have
the ZX chip.