[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-users] bcm43xx module fails loading on domU


  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: albert mohortiso <albert_morthi11@xxxxxxxxx>
  • Date: Sat, 11 Aug 2007 12:32:06 -0700 (PDT)
  • Delivery-date: Fri, 17 Aug 2007 09:42:23 -0700
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=NX8ZXlDlFdMrCgK0USnsVU+Be9CsL4ulKXFJrJ0hxD2fSzvLpcGroA/PaNYWetSLLGBeCJsESTKpA/MeAYUcLCIPI3gRRlYSZgP3bsrwCk3fFgxu9pY5gZ1ZFOckhcD8xxDwwHXXYGY3TI5fskl1R6Rq+Cuu1yY11KVsbpEq/mQ=;
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Hello 
        I'm trying to get a Broadcom BMC4306 wireless pci nic
to work on domU. I manage to get the nic working on
dom0  using the bcm43xx module and firmware extracted
with the bcm43xx-fwcutter tool. once pci hiding is
applied the nic shows on domU but modprob'ing the
module gives the following error : 

ieee80211: 802.11 data/management/control stack,
git-1.1.13
        ieee80211: Copyright (C) 2004-2005 Intel
Corporation 
        bcm43xx driver
        PCI: Enabling device 0000:00:00.0 (0000 ->
0002)
            bcm43xx: Failed to switch to core 0       
            
BUG: unable to handle kernel NULL pointer dereference
at virtual address 00000001
         printing eip:
        e124188f
        20650000 -> *pde = 00000000:28b5e001
        1fd56000 -> *pme = 00000000:00000000
        Oops: 0000 [#1]
        SMP 
        Modules linked in: bcm43xx firmware_class
ieee80211softmac ieee80211 ieee80211_crypt ipv6
dm_snapshot dm_mirror dm_mod 8250 serial_core ext3 jbd
mbcache processor
        CPU:    0
        EIP:    0061:[<e124188f>]    Not tainted VLI
        EFLAGS: 00010246   (2.6.18-4-xen-686 #1) 
        EIP is at bcm43xx_pctl_set_crystal+0x110/0x18e
[bcm43xx]
        eax: 00000000   ebx: 00000000   ecx: c0477d9c 
 edx: c0476000
        esi: c0660da0   edi: 00000000   ebp: ffffffed 
 esp: c0477d9c
        ds: 007b   es: 007b   ss: 0069
        Process modprobe (pid: 1136, ti=c0476000
task=c0822550 task.ti=c0476000)
        Stack: 000000c0 00000000 000000ff c0660000
c0660da0 c0661154 e1233f68 c02d5320 
               c0d67c00 c0155f99 00000001 c0de7fa8
c14ef218 00000001 c0477df8 c0114479 
               00000000 00000003 c14ef214 00000000
c14ef214 00000000 00000001 c0477e1c 
        Call Trace:
         [<e1233f68>] bcm43xx_attach_board+0xea2/0xf0a
[bcm43xx]
         [<c0155f99>] kmem_cache_alloc+0x4a/0x54
         [<c0114479>] __wake_up_common+0x2f/0x53
         [<c011489e>] __wake_up+0x2a/0x3d
         [<c0208370>] __driver_attach+0x0/0x5d
         [<c01289d9>] __queue_work+0x3c/0x49
         [<c0128a31>] queue_work+0x4b/0x50
         [<e12354af>] bcm43xx_init_one+0x1f4/0x238
[bcm43xx]
         [<c0208370>] __driver_attach+0x0/0x5d
         [<c01c312c>] pci_device_probe+0x36/0x57
         [<c02082d1>] driver_probe_device+0x42/0x8b
         [<c02083a8>] __driver_attach+0x38/0x5d
         [<c0207df2>] bus_for_each_dev+0x33/0x55
         [<c020823b>] driver_attach+0x11/0x13
         [<c0208370>] __driver_attach+0x0/0x5d
         [<c0207b0b>] bus_add_driver+0x64/0xfd
         [<c01c3268>] __pci_register_driver+0x47/0x63
         [<c01337a1>] sys_init_module+0x16c3/0x1846
         [<c0104883>] syscall_call+0x7/0xb
        Code: 0c 8b 50 20 8b 40 10 51 b9 b4 00 00 00
e8 40 de f7 de 5e 85 c0 89 c3 75 77 b8 b8 ae 47 01 e8
22 99 f7 de eb 7b 8b 86 34 01 00 00 <80> 78 01 04 76
6f f6 86 98 00 00 00 20 75 66 ba 01 00 00 00 89 
        EIP: [<e124188f>]
bcm43xx_pctl_set_crystal+0x110/0x18e [bcm43xx] SS:ESP
0069:c0477d9c
         
        Message from syslogd@(none) at Sat Aug 11
19:45:29 2007 ...
        (none) kernel: Oops: 0000 [#1]
        
        Message from syslogd@(none) at Sat Aug 11
19:45:29 2007 ...
        (none) kernel: SMP 
        
        Message from syslogd@(none) at Sat Aug 11
19:45:29 2007 ...
        (none) kernel: CPU:    0
        
        Message from syslogd@(none) at Sat Aug 11
19:45:29 2007 ...
        (none) kernel: EIP is at
bcm43xx_pctl_set_crystal+0x110/0x18e [bcm43xx]
        
        Message from syslogd@(none) at Sat Aug 11
19:45:29 2007 ...
        (none) kernel: eax: 00000000   ebx: 00000000  
ecx: c0477d9c   edx: c0476000
        
        Message from syslogd@(none) at Sat Aug 11
19:45:29 2007 ...
        (none) kernel: esi: c0660da0   edi: 00000000  
ebp: ffffffed   esp: c0477d9c
        
        Message from syslogd@(none) at Sat Aug 11
19:45:29 2007 ...
        (none) kernel: ds: 007b   es: 007b   ss: 0069
        
        Message from syslogd@(none) at Sat Aug 11
19:45:29 2007 ...
        (none) kernel: Process modprobe (pid: 1136,
ti=c0476000 task=c0822550 task.ti=c0476000)
        
        Message from syslogd@(none) at Sat Aug 11
19:45:29 2007 ...
        (none) kernel: Stack: 000000c0 00000000
000000ff c0660000 c0660da0 c0661154 e1233f68 c02d5320 
        
        Message from syslogd@(none) at Sat Aug 11
19:45:29 2007 ...
        (none) kernel:        c0d67c00 c0155f99
00000001 c0de7fa8 c14ef218 00000001 c0477df8 c0114479 
        
        Message from syslogd@(none) at Sat Aug 11
19:45:29 2007 ...
        (none) kernel:        00000000 00000003
c14ef214 00000000 c14ef214 00000000 00000001 c0477e1c 
        
        Message from syslogd@(none) at Sat Aug 11
19:45:29 2007 ...
        (none) kernel: Call Trace:
        
        Message from syslogd@(none) at Sat Aug 11
19:45:29 2007 ...
        (none) kernel: Code: 0c 8b 50 20 8b 40 10 51
b9 b4 00 00 00 e8 40 de f7 de 5e 85 c0 89 c3 75 77 b8
b8 ae 47 01 e8 22 99 f7 de eb 7b 8b 86 34 01 00 00
<80> 78 01 04 76 6f f6 86 98 00 00 00 20 75 66 ba 01
00 00 00 89 
        
        Message from syslogd@(none) at Sat Aug 11
19:45:29 2007 ...
        (none) kernel: EIP: [<e124188f>]
bcm43xx_pctl_set_crystal+0x110/0x18e [bcm43xx] SS:ESP
0069:c0477d9c
        Segmentation fault
        

I suspect the fact that the card appears on 00:00.0
instead of it's original location might have something
to do with it. Is there any way to set the 'mounting'
location of pci devices in domU ? 
any help would be appreciated 

dom0 runs debian etch with a 2.6.18-4-xen-686 kernel.
l"=0m)L6 albert_morthi11

domU's config file:
        kernel = "/boot/vmlinuz-2.6.18-4-xen-686"
        ramdisk = "/boot/xen-initrd-18-4.gz"
        memory = '512'
        disk = [ 'phy:hdc1,sda1,w','phy:hdc2,sda2,w' ]
        root = '/dev/sda1 ro'
        dhcp = 'no'
        pci = [ '02:00.0' ]
        vif = [ 'ip=192.168.3.100, vifname=vif1.0' ]
        name = 'node1'
        on_poweroff = 'destroy'
        on_reboot   = 'restart'
        on_crash    = 'restart'


       
____________________________________________________________________________________
Take the Internet to Go: Yahoo!Go puts the Internet in your pocket: mail, news, 
photos & more. 
http://mobile.yahoo.com/go?refer=1GNXIC

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.