Crash on start with saa7134 and 2.6.24-15-generic

[Kazade]

After upgrading to the 2.6.24-15-generic kernel in Hardy my computer failed to boot. The progress bar would load 2 blocks and then everything would stop.

When I tried recovery mode the same thing happened but I could see a stack trace involving the sound chip on my saa7134 tv card. I fixed it by removing the card from my machine, however after checking the logs I can't see any record of the traceback to report here. I've grep'd /var/log and there is nothing. If you need more information I guess I could put the card back in and write the stack trace down by hand.

[hms113a313 (hms113a313)]

Yes, this happens also to my system with Tevion MD-9717. After rebooting with the old 2.6.24-14 and inspecting the kern.log, I suspect the offending module is saa7134_alsa. Manually blacklist saa7134_alsa seems to solve the problem. I can now boot to 2.6.24-15 and my TV card still works as beautifully as before.

[captive (salvo-schifani)]

Same here, but saa7134_alsa is not modprobed at boot, so I'd blacklist saa7134 itself, loosing my tvcard.
I'm stick with -14 waiting for a fix.

[Rob Martin (robmartin)]

Can also confirm hang on boot and workaround with this device

lshw

 description: Multimedia controller
                product: SAA7133/SAA7135 Video Broadcast Decoder
                vendor: Philips Semiconductors
                physical id: 9
                bus info: pci@0000:07:09.0
                version: d1
                width: 32 bits
                clock: 33MHz
                capabilities: pm bus_master cap_list
                configuration: driver=saa7134 latency=32 maxlatency=32 mingnt=84 module=saa7134

lspci -vv

07:09.0 Multimedia controller: Philips Semiconductors SAA7133/SAA7135 Video Broadcast Decoder (rev d1)
 Subsystem: Creatix Polymedia GmbH Unknown device 000d
 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
 Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
 Latency: 32 (21000ns min, 8000ns max)
 Interrupt: pin A routed to IRQ 24
 Region 0: Memory at df5ff000 (32-bit, non-prefetchable) [size=2K]
 Capabilities: [40] Power Management version 2
  Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
  Status: D0 PME-Enable- DSel=0 DScale=1 PME-

PC is a Medion MD8818 with tevion tri-band (dvb-t, dvb-s, and analogue tuner)

Hope this helps.

[Shaun Orchard (shaun-omghax)]

Same problem with Hauppauge HVR-1100 (also saa7134).

booting -14 fixes it, but that obviously isn't practical.

[jnewton (nevion)]

Also affected.
I believe I have a kworld tv-terminator. Uses saa7134. lspci reports Philips Semiconductors SAA7133/SAA7135 Video Broadcast Decoder.

My work around was to boot with the kernel parameter break=bottom , mount -o remount,rw /root, and to mv /root/lib/modules/2.6.../drivers/media/ to somewhere else (/root/media/media is what I used just so I could get my computer booting).

Quite a nasty little surprise this bug was, had me cut off with no internet since I couldn't get my workstation/router booted. Please find the problem as I cannot play my wii until I can load my tv card drivers again :-)

As I boot with no splash screen,I remember seeing an oops and a call stack. The crash occurred 1 line after the nvidia driver was loaded, which was one line after saa7134 being loaded. It crashed in snd_pcm_* but I don't remember any more specific than that. I believe it had a pointer dereference of 0x0000000000000001.

[Kaivalagi (m-buck)]

Same problem here, just for the record. I have a Compro T750, saa 7134 chipset...

I have reverted back to build 14 of the kernel for now.

 What nevion has mentioned above is correct, it definitely has something to do with the sound part of the tuner card...

[Ari (ari-reads)]

Same problem, saa7134 based card. Originally reported here: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/212342

BTW, hardy also broke the remote control support for saa7334 cards (https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/204960)

[ourasi (ourasi)]

Same problem here with Asus My Cinema-P7131 Hybrid, solved by blacklisting only saa7134_alsa. Thanks hms113a313.

[samuelmello (samuelmello)]

Just another me too.
I have a Encore ENLTV, also reported as Philips Semiconductors SAA7130 Video Broadcast Decoder in lspci.

[Jeffrey Ratcliffe (jeffreyratcliffe)]

Same here. I'll try blacklisting saa7134_alsa.

[Ciso (cisoprogressivo)]

Same problem here with Asus My Cinema-P7131 Hybrid

[ManuPeng (mvieuxmaire)]

Also new here, 2.6.24-12 boots just great but the new kernel 2.6.24.15 freezes at bootup.
The line that hangs says:
hda_codec: Unknown model for ALC882, trying auto-probe from BIOS.

ALC882 is my sound chip, this takes place somewhere around the initialization of my Hauppage with a cx88 something chip.

[ManuPeng (mvieuxmaire)]

It's me again, yeah, it's a cx8800 chip on my Hauppage, lshw returns:
 configuration: driver=cx8800 latency=64 maxlatency=55 mingnt=20 module=cx8800

[Jeffrey Ratcliffe (jeffreyratcliffe)]

Blacklisting saa7134_alsa fixed things.

[samuelmello (samuelmello)]

I've just tested with 2.6.24-16 and the problem persist.
Anyone got a patch for this?

[ourasi (ourasi)]

For me same problem with 2.6.24-16-generic and same solution: blacklisting of saa7134_alsa helps still. But how can I start Live-CD with blacklisting?

[samuelmello (samuelmello)]

As indicated in https://wiki.ubuntu.com/KernelTeamBugPolicies, i'm posting lspci -vvnn.
The kern.log is already attached in the first post.
The other information required (uname and version_signature) are not acessible as system does not complete boot, but I don't think they are going to be really needed.

Up to the last working version (2.6.24-14-generic), the module saa7134-alsa were not shipped:
root@samuel-desktop:/lib/modules# find 2.6.24-14-generic/ -name "*7134*"
2.6.24-14-generic/kernel/drivers/media/video/saa7134
2.6.24-14-generic/kernel/drivers/media/video/saa7134/saa7134-dvb.ko
2.6.24-14-generic/kernel/drivers/media/video/saa7134/saa7134.ko
2.6.24-14-generic/kernel/drivers/media/video/saa7134/saa7134-empress.ko
root@samuel-desktop:/lib/modules#

Starting at 2.6.24-15-generic, there are some more modules in a 'ubuntu' directory, and it seems that one of those modules are causing the system crash.

root@samuel-desktop:/lib/modules# find 2.6.24-15-generic/ -name "*7134*"
2.6.24-15-generic/kernel/drivers/media/video/saa7134
2.6.24-15-generic/kernel/drivers/media/video/saa7134/saa7134-dvb.ko
2.6.24-15-generic/kernel/drivers/media/video/saa7134/saa7134.ko
2.6.24-15-generic/kernel/drivers/media/video/saa7134/saa7134-empress.ko
2.6.24-15-generic/ubuntu/media/saa7134
2.6.24-15-generic/ubuntu/media/saa7134/saa7134-oss.ko
2.6.24-15-generic/ubuntu/media/saa7134/saa7134-alsa.ko
2.6.24-15-generic/ubuntu/media/saa7134/saa7134-dvb.ko
2.6.24-15-generic/ubuntu/media/saa7134/saa7134.ko
2.6.24-15-generic/ubuntu/media/saa7134/saa7134-empress.ko
root@samuel-desktop:/lib/modules#

Does anyone know why and how this 'ubuntu' directory appeared in 2.6.24-15?

BTW, have somebody at kernel-team taken a look on this bug?

[Jeffrey Ratcliffe (jeffreyratcliffe)]

This also affects 2.6.24-16.

[ourasi (ourasi)]

"BTW, have somebody at kernel-team taken a look on this bug?"

Is this #212143 a duplicate of bug #212271 or vice versa?
https://bugs.launchpad.net/ubuntu/+source/linux-ubuntu-modules-2.6.24/+bug/212271

[Oleksiy Lukin (alukin)]

The same thing with Philips Semiconductors SAA7134/SAA7135HL Video Broadcast Decoder (rev 01)
not only with Ubuntu kernels. On my Fedora 2.6.24, 2.6.25 tv card works but freezes system randomly.
I think it is bug of saa7134 module.

[jacobS (jacsalomon)]

I don't have this bug I take a Encore ENLTV-FM whith Saa7134, but don't have this issue. I used the kernel:

2.6.24-19-generic

I don't believe that is a module saa7134 or Kernel

[Jeffrey Ratcliffe (jeffreyratcliffe)]

For me, this is fixed in 2.6.24-19-generic.

[captive (salvo-schifani)]

Same here