Launchpad has imported 25 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=208242.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2006-09-27T10:32:32+00:00 Karsten wrote: 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 Reply at: https://bugs.launchpad.net/ubuntu/+source/xen- meta/+bug/116267/comments/0 ------------------------------------------------------------------------ On 2006-11-01T14:46:17+00:00 Mark wrote: Me too: FC6 (Zod)on Lenovo AMD desktop. Otherwise identical symptoms Reply at: https://bugs.launchpad.net/ubuntu/+source/xen- meta/+bug/116267/comments/1 ------------------------------------------------------------------------ On 2006-11-03T15:08:33+00:00 Jindrich wrote: 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 Reply at: https://bugs.launchpad.net/ubuntu/+source/xen-meta/+bug/116267/comments/2 ------------------------------------------------------------------------ On 2006-11-03T15:23:25+00:00 Jindrich wrote: doesn't work with 2.6.18-1.2798.fc6xen as well. Reply at: https://bugs.launchpad.net/ubuntu/+source/xen- meta/+bug/116267/comments/3 ------------------------------------------------------------------------ On 2006-11-20T17:07:32+00:00 James wrote: 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. Reply at: https://bugs.launchpad.net/ubuntu/+source/xen- meta/+bug/116267/comments/4 ------------------------------------------------------------------------ On 2006-11-27T12:27:35+00:00 Stephen wrote: 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. Reply at: https://bugs.launchpad.net/ubuntu/+source/xen-meta/+bug/116267/comments/5 ------------------------------------------------------------------------ On 2006-11-28T06:59:09+00:00 Jindrich wrote: Fix confirmed, b44 module now works for me with your kernel. Thanks! Reply at: https://bugs.launchpad.net/ubuntu/+source/xen- meta/+bug/116267/comments/6 ------------------------------------------------------------------------ On 2006-11-28T15:21:42+00:00 Felix wrote: Works for me, too. Reply at: https://bugs.launchpad.net/ubuntu/+source/xen- meta/+bug/116267/comments/7 ------------------------------------------------------------------------ On 2006-11-28T20:30:24+00:00 Calvin wrote: 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 0 0 0 4749 0 0 0 LRU peth0 1500 0 0 0 0 0 0 0 0 0 BOU vif0.0 1500 0 2718 0 0 0 0 0 0 0 BORU xenbr0 1500 0 2718 0 0 0 0 0 0 0 BORU ------------------------------------- route ------------------------------------- Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.3.0 * 255.255.255.0 U 0 0 0 eth0 default kc130ssa 0.0.0.0 UG 0 0 0 eth0 ------------------------------------- ping -c 2 kc130ssa ------------------------------------- PING kc130ssa (192.168.3.254) 56(84) bytes of data. >From 192.168.3.107 icmp_seq=1 Destination Host Unreachable >From 192.168.3.107 icmp_seq=2 Destination Host Unreachable ------------------------------------- dmesg | tail ------------------------------------- printk: 104495 messages suppressed. 4gb seg fixup, process beagled-helper (pid 5749), cs:ip 73:0811cbff printk: 109 messages suppressed. 4gb seg fixup, process beagled-helper (pid 5749), cs:ip 73:0811cb2a printk: 69 messages suppressed. 4gb seg fixup, process beagled-helper (pid 5749), cs:ip 73:0811cb2a printk: 63 messages suppressed. 4gb seg fixup, process beagled-helper (pid 5749), cs:ip 73:0811cbff printk: 71 messages suppressed. 4gb seg fixup, process beagled-helper (pid 5749), cs:ip 73:0811cb2a ------------------------------------- dmesg | egrep '^printk|^4gb' | wc -l ------------------------------------- 2580 ------------------------------------- Network Manager messages eth0: ------------------------------------- Nov 28 12:47:59 wizard NetworkManager: <information> eth0: Device is fully-su pported using driver 'b44'. Nov 28 12:47:59 wizard NetworkManager: <information> nm_device_init(): waitin g for device's worker thread to start Nov 28 12:47:59 wizard NetworkManager: <information> nm_device_init(): device 's worker thread started, continuing. ... Nov 28 12:48:00 wizard NetworkManager: <information> Activation (eth0) Stage 5 of 5 (IP Configure Commit) complete. ------------------------------------- Reply at: https://bugs.launchpad.net/ubuntu/+source/xen- meta/+bug/116267/comments/8 ------------------------------------------------------------------------ On 2006-11-28T22:29:51+00:00 Stephen wrote: 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. Reply at: https://bugs.launchpad.net/ubuntu/+source/xen-meta/+bug/116267/comments/9 ------------------------------------------------------------------------ On 2006-12-04T16:12:43+00:00 Randy wrote: 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. Reply at: https://bugs.launchpad.net/ubuntu/+source/xen- meta/+bug/116267/comments/10 ------------------------------------------------------------------------ On 2006-12-11T22:26:27+00:00 Calvin wrote: 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. Reply at: https://bugs.launchpad.net/ubuntu/+source/xen-meta/+bug/116267/comments/11 ------------------------------------------------------------------------ On 2006-12-12T11:22:21+00:00 Stephen wrote: 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. Reply at: https://bugs.launchpad.net/ubuntu/+source/xen- meta/+bug/116267/comments/12 ------------------------------------------------------------------------ On 2006-12-12T11:55:40+00:00 Karsten wrote: 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. Reply at: https://bugs.launchpad.net/ubuntu/+source/xen- meta/+bug/116267/comments/13 ------------------------------------------------------------------------ On 2006-12-12T15:49:08+00:00 Calvin wrote: I've submitted a new Bug #219309 Summary: No networking: IRQ nrs appear truncated Thank you! Reply at: https://bugs.launchpad.net/ubuntu/+source/xen- meta/+bug/116267/comments/14 ------------------------------------------------------------------------ On 2006-12-13T13:54:18+00:00 Stephen wrote: Patch available, tested, and merged upstream; reassigning for merge/rebase into rawhide. Reply at: https://bugs.launchpad.net/ubuntu/+source/xen- meta/+bug/116267/comments/15 ------------------------------------------------------------------------ On 2006-12-21T12:43:55+00:00 Felix wrote: Will this patch be included into FC6 kernels? 2.6.18-1.2868 does not work for me. Reply at: https://bugs.launchpad.net/ubuntu/+source/xen- meta/+bug/116267/comments/16 ------------------------------------------------------------------------ On 2006-12-23T20:21:09+00:00 Xiaodong wrote: My Dell inspiron640m works after install new kernel and add localhost 127.0.0.1 to /etc/hosts, everything is fine now Reply at: https://bugs.launchpad.net/ubuntu/+source/xen- meta/+bug/116267/comments/17 ------------------------------------------------------------------------ On 2007-01-02T20:33:52+00:00 Julian wrote: 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> Reply at: https://bugs.launchpad.net/ubuntu/+source/xen-meta/+bug/116267/comments/18 ------------------------------------------------------------------------ On 2007-01-11T00:17:01+00:00 William wrote: 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 Reply at: https://bugs.launchpad.net/ubuntu/+source/xen- meta/+bug/116267/comments/19 ------------------------------------------------------------------------ On 2007-01-22T11:05:07+00:00 Andrei wrote: Still does not work on an Acer Aspire 5630, kernel-xen-2.6.19-1.2895.fc6, BCM4401-B0 (rev. 02). Reply at: https://bugs.launchpad.net/ubuntu/+source/xen- meta/+bug/116267/comments/20 ------------------------------------------------------------------------ On 2007-02-28T19:54:36+00:00 Daniel wrote: 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 Reply at: https://bugs.launchpad.net/ubuntu/+source/xen- meta/+bug/116267/comments/21 ------------------------------------------------------------------------ On 2007-03-01T14:42:07+00:00 Calvin wrote: dito Reply at: https://bugs.launchpad.net/ubuntu/+source/xen- meta/+bug/116267/comments/22 ------------------------------------------------------------------------ On 2007-07-02T16:37:10+00:00 Calvin wrote: b44 in latest FC6 Xen kernels work fine now for me. See Bug #219277. Reply at: https://bugs.launchpad.net/ubuntu/+source/xen- meta/+bug/116267/comments/24 ------------------------------------------------------------------------ On 2007-07-03T10:44:18+00:00 Karsten wrote: confirmed, latest Xen kernel works for me as well. I'll close this report. Reply at: https://bugs.launchpad.net/ubuntu/+source/xen- meta/+bug/116267/comments/25 ** Changed in: xen-meta (Fedora) Importance: Unknown => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/116267 Title: b44 module not working under Xen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xen-meta/+bug/116267/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
