IRQ 11 disabled, no network, desktop / kernel freeze (Averatec laptop) - regression from Breezy

[Fabián Rodríguez]

I am using Dapper FL5, latest upgrades applied, kernel 2.6.15-18 (-k7 or -386) on an Averatec 3250-HX1 laptop with mobile AMD Athlon(tm) XP-M (LV) 2200+ processor.

Problem: Ubuntu desktop does not have network functionality, system hangs completely when attempting dhclient from command line (becomes unresponsive, can't access a console via Ctrl-Alt-F1, can't restart GDM via Ctrl-Alt-Backspace) or trying to reactivate the eth0 interface via System > Amdministration > Networking.

This worked fine in previous Ubuntu version (5.10). Ethernet controller is VIA Technologies, Inc. VT6102 [Rhine-II] (rev 74) as reported by lspci.

When booting in recovery mode, networking works fine, that's how I was able to apt-get update / upgrade.

I tested using -k7 -386 kernels with the same results.

When checking the dmesg output of a normal boot (not recovery), I see this:
[4294703.809000] irq 11: nobody cared (try booting with the "irqpoll" option)

I tried the irqpoll option in the boot options but the system hangs before getting to gdm, with continuous HD activity.

I also found this in dmesg:
[4294703.809000] Disabling IRQ #11

Searching with different terms in Google ("Disabling IRQ #11", "irq 11: nobody cared") this seems to be reported in other distributions and may be related to ACPI. A closer example from the Averatec forums lists a possible workaround which I haven't tried, as I haven't had time to do it:

http://averatecforums.com/showthread.php?t=2166&page=3

I am attaching different commands output for -k7 kernel normal and recovery boot.

[Fabián Rodríguez (magicfab)]

Ouput of dmesg in -k7 kernel

[Fabián Rodríguez (magicfab)]

Ouput of dmesg in -k7 kernel (recovery mode)

[Fabián Rodríguez (magicfab)]

Ouput of lshw in -k7 kernel

[Fabián Rodríguez (magicfab)]

Ouput of lshw in -k7 kernel (recovery mode)

[Fabián Rodríguez (magicfab)]

Ouput of lsmod in -k7 kernel

[Fabián Rodríguez (magicfab)]

Ouput of lsmod in -k7 kernel (recovery mode)

[Fabián Rodríguez (magicfab)]

Ouput of lspci in -k7 kernel

[Fabián Rodríguez (magicfab)]

Ouput of lspci in -k7 kernel (recovery mode)

[Fabián Rodríguez (magicfab)]

Ouput of lsusb in -k7 kernel

[Fabián Rodríguez (magicfab)]

Ouput of lsusb in -k7 kernel (recovery mode)

[Ben Collins (ben-collins)]

Your network card and wireless card are both sharing IRQ-11.

What I need is a complete lspci -vv output, and also "cat /proc/interrupts". No need to do this from both boots (lspci is the same no matter what, and booting to single isn't what I am interested in).

[Matt Zimmerman (mdz)]

Please supply the requested information

[John Simpkins (onerobot)]

I have the exact same machine and can confirm this. I have absolutely no idea how to route irq settings (it seems to be kind of a black art), but this can be worked around by adding the line Option "DisableIRQ" "true"
to the Device section in Xorg.conf.

Output of lspci -vv attached.

[John Simpkins (onerobot)]

Output of "cat /proc/interrupts" attached.

[C. Matt Detzel (cmdetzel)]

I have same laptop. Bug still persists in Beta 1. If I leave both the wireless and the wired unconfigured, and use my cardbus wireless card, all is well. Any attempts to intialize those interfaces creates the same lockups.

[Michael R. Bernstein (webmaven)]

This is the output of 'lspci -vv' on an Averatec 3250HX-01.

[Michael R. Bernstein (webmaven)]

This is a screenshot of the crash output after the following procedure:

1) boot in recovery mode

    Network is up, can access the network and get DHCP lease

2) start X

3) stop X (ctrl-alt-backspace)

    Network now is no longer accessible to pings.

4) Try dhclient (or ifup/ifdown)

    System crashes.

Further investigation shows that the drm and via modules are loaded by X and not unloaded afterwards. However, manually unloading these modules after stopping X is not enough to prevent the crash.

[Fabián Rodríguez (magicfab)]

This seems to be fixed as described in this duplicate bug report:
https://launchpad.net/bugs/48263

I have been using this method with my Averatec model 3250HX-01 without incident for the last week.

However, you need to follow these steps first:
1) edit /boot/grub/menu.lst as root ( sudo nano /boot/grub/menu.lst )
2) Look for the first section similar to:
title Ubuntu, kernel 2.6.xxxxxxx-k7
root (hd0,2)
kernel /boot/vmlinuz-2.6.xxxxxxxxx-k7 root=/dev/hda3 ro quiet splash
initrd /boot/initrd.img-2.6.xxxxxxxx-k7
savedefault
boot
3) At the end of the "kernel" line, add "acpi=noirq" so it looks like this:
kernel /boot/vmlinuz-2.6.xxxxxxxxx-k7 root=/dev/hda3 ro quiet splash acpi=noirq
4) Save the file, reboot the machine

Once you have rebooted, you will have network capabilities. Perform a full system update / upgrade, including kernel. The menu.lst file should update itself accordingly and the new kernel versions from now on will include the equivalente acpi=noirq option.

[Launchpad Janitor (janitor)]

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this linux-source-2.6.15 kernel bug to the new "linux" package. We appreciate your patience and understanding as we make this transition. Also, if you would be interested in testing the upcoming Intrepid Ibex 8.10 release, it is available at http://www.ubuntu.com/testing . Please let us know your results. Thanks!