b44 module not working under Xen

[Stinnux]

It's identical to Redhat's Bug Report here:

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=208242

It's already fixed there, so maybe you can just incorporate their patch.

[Karsten (karsten-redhat-bugs)]

Description of problem:
The b44 module with kernel-2.6.18-1.2693.fc6xen doesn't work:
b44.c:v1.01 (Jun 16, 2006)
ACPI: PCI Interrupt 0000:03:00.0[A] -> GSI 17 (level, low) -> IRQ 17
b44 0000:03:00.0: No usable DMA configuration, aborting.
ACPI: PCI interrupt for device 0000:03:00.0 disabled
b44: probe of 0000:03:00.0 failed with error -5

ifconfig/ifup fails on this device, even though the module is loaded:
# lsmod | grep b44
b44 34133 0
mii 9793 1 b44

The dmesg part with a non-xen kernel kernel-2.6.18-1.2693.fc6:
b44.c:v1.01 (Jun 16, 2006)
ACPI: PCI Interrupt 0000:03:00.0[A] -> GSI 17 (level, low) -> IRQ 177
eth0: Broadcom 4400 10/100BaseT Ethernet 00:14:22:f8:cc:ef

# lspci -v
03:00.0 Ethernet controller: Broadcom Corporation BCM4401-B0 100Base-TX (rev 02)
        Subsystem: Dell Unknown device 01cd
        Flags: bus master, fast devsel, latency 64, IRQ 177
        Memory at dcbfe000 (32-bit, non-prefetchable) [size=8K]
        Capabilities: [40] Power Management version 2

[Mark (mark-redhat-bugs)]

Me too: FC6 (Zod)on Lenovo AMD desktop. Otherwise identical symptoms

[Jindrich (jindrich-redhat-bugs)]

same here:
02:0e.0 Ethernet controller: Broadcom Corporation BCM4401-B0 100Base-TX (rev 02)
        Subsystem: Hewlett-Packard Company NX6110/NC6120
        Flags: bus master, fast devsel, latency 64, IRQ 185
        Memory at d0008000 (32-bit, non-prefetchable) [size=8K]
        Capabilities: [40] Power Management version 2

[Jindrich (jindrich-redhat-bugs)]

doesn't work with 2.6.18-1.2798.fc6xen as well.

[James (james-redhat-bugs)]

I'm having the same issue as well.. on a dual-core AMD here,
2.6.18-1.2849.fc6xen doesn't work with b44.

[Stephen (stephen-redhat-bugs)]

Can you please try the kernel at

http://people.redhat.com/sct/packages/kernel/kernel-xen-2.6.18-1.2857.4.2.fc6.0.2.sct/

and see if that works any better? Thanks.

[Jindrich (jindrich-redhat-bugs)]

Fix confirmed, b44 module now works for me with your kernel. Thanks!

[Felix (felix-redhat-bugs)]

Works for me, too.

[Calvin (calvin-redhat-bugs)]

Insalled the new kernel.

The b44 module loads and eth0 starts up now, but I can't connect to anything and
my logs are filling up with thousands of messages like this:

------------------------------------
printk: 71 messages suppressed.
4gb seg fixup, process beagled-helper (pid 5749), cs:ip 73:0811cb2a
------------------------------------

What else should I be looking at? I've included other relevant info below.

Thanks!

--Cal Webster

top
------------------------------------
top - 14:43:23 up 2:06, 4 users, load average: 1.02, 1.01, 1.03
Tasks: 138 total, 3 running, 135 sleeping, 0 stopped, 0 zombie
Cpu(s): 1.5%us, 0.3%sy, 0.0%ni, 48.1%id, 0.0%wa, 0.3%hi, 49.8%si, 0.0%st
Mem: 1938712k total, 1865236k used, 73476k free, 250936k buffers
Swap: 2031608k total, 0k used, 2031608k free, 1310788k cached

  PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
    3 root 39 19 0 0 0 R 100 0.0 122:58.13 ksoftirqd/0
------------------------------------

ifconfig:
-------------------------------------
eth0 Link encap:Ethernet HWaddr 00:14:22:EF:61:DC
          inet addr:192.168.3.107 Bcast:192.168.3.255 Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2437 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b) TX bytes:104186 (101.7 KiB)

lo Link encap:Local Loopback
          inet addr:127.0.0.1 Mask:255.0.0.0
          UP LOOPBACK RUNNING MTU:16436 Metric:1
          RX packets:4736 errors:0 dropped:0 overruns:0 frame:0
          TX packets:4736 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:3433226 (3.2 MiB) TX bytes:3433226 (3.2 MiB)

peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
          UP BROADCAST NOARP MTU:1500 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
          Interrupt:17

vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
          UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
          RX packets:2681 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:116361 (113.6 KiB) TX bytes:0 (0.0 b)

xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
          UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
          RX packets:2681 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:78827 (76.9 KiB) TX bytes:0 (0.0 b)
-------------------------------------

netstat -i
-------------------------------------
Kernel Interface table
Iface MTU Met RX-OK RX-ERR RX-DRP RX-OVR TX-OK TX-ERR TX-DRP TX-OVR Flg
eth0 1500 0 0 0 0 0 2474 0 0 0 BMRU
lo 16436 0 4749 ...

[Stephen (stephen-redhat-bugs)]

The
  4gb seg fixup, process beagled-helper (pid 5749), cs:ip 73:0811cb2a
messages are nothing to do with networking --- they are notifications of mono
applications using segment accesses which cannot be efficiently supported under Xen.

NetworkManager is unlikely to work well with Xen's default bridging network
setup: you probably want to configure routed networking for Xen if you have
NetworkManager running at all.

[Randy (randy-redhat-bugs)]

Stephen's kernel works for me too on a Dell Inspiron 5150 (with 1GB real
memory and the same ethernet interface). It had the exact same symptoms as
noted above.

[Calvin (calvin-redhat-bugs)]

I'm still not getting any networking in the Xen kernel. I can't even ping the
local gateway.

I've disabled NetworkManager and left the other network settings as they were.

The IRQ assignments still don't look right to me. Here's how they differ in
"dmesg" between non-Xen (<) and Xen (>) kernel boots. At a glance, it looks like
the IRQ numbers are being truncated.

191c163
< ACPI: PCI Interrupt 0000:00:01.0[A] -> GSI 16 (level, low) -> IRQ 169
---
> ACPI: PCI Interrupt 0000:00:01.0[A] -> GSI 16 (level, low) -> IRQ 16
193c165
< ACPI: PCI Interrupt 0000:00:1c.0[A] -> GSI 16 (level, low) -> IRQ 169
---
> ACPI: PCI Interrupt 0000:00:1c.0[A] -> GSI 16 (level, low) -> IRQ 16
195c167
< ACPI: PCI Interrupt 0000:00:1c.1[B] -> GSI 17 (level, low) -> IRQ 177
---
> ACPI: PCI Interrupt 0000:00:1c.1[B] -> GSI 17 (level, low) -> IRQ 17
197c169
< ACPI: PCI Interrupt 0000:00:1c.3[D] -> GSI 19 (level, low) -> IRQ 185
---
> ACPI: PCI Interrupt 0000:00:1c.3[D] -> GSI 19 (level, low) -> IRQ 18

Is there some special procedure to make the virtual interfaces and bridge come
up correctly?

This was what I had to do to get QEMU bridging to work:

Rename a copy of ifcfg-eth0 to ifcfg-br0
Remove all the IP related entries from original ifcfg-eth0 but leave the HWADDR.
Set "dev.rtc.max-user-freq = 1024" in /etc/sysctl.conf
Load the "tun" module
Run this sequence of commands:

    ifdown eth0
    ifdown br0
    modprobe bridge
    brctl addbr br0
    brctl stp br0 off
    brctl setfd br0 1
    ifup eth0
    brctl addif br0 eth0

Do I need to do this same thing to get Xen kernel networking running?
It sure seems like it should be simpler than that.

I'd be grateful for some pointers. Maybe this is all covered somewhere in Xen
docs. I'm certainly not getting the "out-of-the-box" experience that the on-line
docs say "most" people are supposed to get.

[Stephen (stephen-redhat-bugs)]

re comment #11:

Can you please open a separate bug for this? From your report

The b44 module loads and eth0 starts up now, but I can't connect to anything and
my logs are filling up with thousands of messages like this:

and the fact that eth0 *has* now got an IP address, your eth0 interface is up
and running. Any other problems are separate, and need to be reported as such,
otherwise we can't properly track them independently of the original b44 problem.

[Karsten (karsten-redhat-bugs)]

SCT: I've installed your kernel and get a slightly different message when the
module loads:
b44.c:v1.01 (Jun 16, 2006)
ACPI: PCI Interrupt 0000:03:00.0[A] -> GSI 17 (level, low) -> IRQ 17
eth0: Broadcom 4400 10/100BaseT Ethernet 00:xx:xx:xx:xx:xx

So this looks fine (apart from the low IRQ).

Network still doesn't work, but that's another issue. I'll open a new bug for that.

[Calvin (calvin-redhat-bugs)]

I've submitted a new Bug #219309
Summary: No networking: IRQ nrs appear truncated

Thank you!

[Stephen (stephen-redhat-bugs)]

Patch available, tested, and merged upstream; reassigning for merge/rebase into
rawhide.

[Felix (felix-redhat-bugs)]

Will this patch be included into FC6 kernels? 2.6.18-1.2868 does not work for me.

[Xiaodong (xiaodong-redhat-bugs)]

My Dell inspiron640m works after install new kernel and add localhost 127.0.0.1
to /etc/hosts, everything is fine now

[Julian (julian-redhat-bugs)]

Identical issues for me.

Running latest kernel 2.6.18-1.2869.fc6xen.

Relevant 'lspci -v' output:
03:00.0 Ethernet controller: Broadcom Corporation BCM4401-B0 100Base-TX (rev 02)
 Subsystem: Dell Inspiron 6000 laptop
 Flags: bus master, fast devsel, latency 64, IRQ 193
 Memory at dfdfe000 (32-bit, non-prefetchable) [size=8K]
 Capabilities: <access denied>

[William (william-redhat-bugs)]

re comment #13
I have a dell inspiron 6000 b44 module tried kernel 2.6.18-1.2869 xen.
With ifconfig bCM4401-b0 gets set to IRQ 19.

Networking still does not work for me same as comment#13.

What can I do?

Thanks for any help

[Andrei (andrei-redhat-bugs)]

Still does not work on an Acer Aspire 5630, kernel-xen-2.6.19-1.2895.fc6,
BCM4401-B0 (rev. 02).

[Daniel (daniel-redhat-bugs)]

need to update the kernel package that supposedly fixed this issue. the new
kernel is 2.6.19-1.2911 and the problem is still evident, so i'd be nice to have
an updated kernel fix for xen

[Calvin (calvin-redhat-bugs)]

dito

[Calvin (calvin-redhat-bugs)]

b44 in latest FC6 Xen kernels work fine now for me. See Bug #219277.

[Karsten (karsten-redhat-bugs)]

confirmed, latest Xen kernel works for me as well. I'll close this report.

[Nystagmus (jamesbrummer)]

I can confirm this bug. Lately I've been working with a fully up-to-date install of Feisty 7.04. I've been trying to get the ubuntu-xen-desktop package to work. Working with a Dell Inspiron 5100 series laptop. The b44 driver works just fine under the standard ubuntu kernel but fails under both the xen desktop and server kernels.

Here are some other websites detailing this same issue in other distros, particularly Red Hat / Fedora as mentioned above.

http://www.felix-schwarz.name/Linux_on_Dell_E521_(en)#Ethernet_.28solved.29
http://www.linuxquestions.org/questions/showthread.php?t=550084

This is the par

[root@localhost ~]# dmesg |grep b44
b44.c:v1.01 (Jun 16, 2006)
b44 0000:03:00.0: No usable DMA configuration, aborting.
b44: probe of 0000:03:00.0 failed with error -5

Attention to this would be greatly appreciated since this leaves pretty much all Dell users (especially laptops) at a loss for being able to use Xen.

[Jeff Anderson (jander99)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance.

[rusivi2 (rusivi2-deactivatedaccount)]

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

[Nystagmus (jamesbrummer)]

My apologies. You can probably close this bug report. The system I
encountered it on is long since dead so I can't test it further.

On Wed, Sep 15, 2010 at 10:25 PM, rusivi1 <email address hidden> wrote:

> We'd like to figure out what's causing this bug for you, but we haven't
> heard back from you in a while. Could you please provide the requested
> information? Thanks!
>
> --
> b44 module not working under Xen
> https://bugs.launchpad.net/bugs/116267
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
"He felt that his whole life was some kind of dream and he sometimes
wondered whose it was and whether they were enjoying it." - Douglas Adams