WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

[Xen-users] madwifi and Xen

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] madwifi and Xen
From: Luke <secureboot@xxxxxxxxx>
Date: Sun, 12 Feb 2006 16:58:49 -0500
Delivery-date: Sun, 12 Feb 2006 22:11:34 +0000
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:mime-version:content-transfer-encoding:message-id:content-type:to:from:subject:date:x-mailer; b=uqZ+p+bSOkXDD1nQSOyABbjXZhJDGzk6sao8iZnXcIPg7ConaWJ96I1+zTkop7MAHfxS2Jg9Jo4nvA++uobfHXdiop1d1RMh+BBeVItr4yKuZZk3FIDPX+JO4VksleHT5xTo283cmfgd8RQsvbgSky2+E5dtqGaGOzzDeUMJx5s=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Is it possible to get madwifi working in a dom0? When I try, both with and without the noacpi on the kernel line in menu.lst, the machine crashes all the time, but in different ways (different parts of the bootup segfault, and create different sorts of errors).

I built the old madwifi codebase, linked to the Xen kernel source via make KERNELPATH=/path_to_xen_kernel

At the very least, i'd love to know if such a thing is possible.

Here's the output from one such bootup that failed on a DLink (dwl- g520, well supported under madwifi):

Modules linked in: ip_tables wlan_wep uhci_hcd ath_pci ath_rate_sample wlan athtCPU: 0
EIP:    0061:[<c9140527>]    Tainted: P      VLI
EFLAGS: 00010206   (2.6.12.6-xen0)
EIP is at ath_chan_set+0xc7/0x230 [ath_pci]
eax: c0523eb0   ebx: 00000001   ecx: 4aec73ae   edx: 00000006
esi: 000000e2   edi: c760c000   ebp: c7112000   esp: c0523e8c
ds: 007b   es: 007b   ss: 0069
Process swapper (pid: 0, threadinfo=c0522000 task=c0495040)
Stack: c760c000 00000006 c0523eb0 00000001 c0523eac c7557a20 c0495040 c7112620 00000007 00a0097b 00000001 000000e2 c7112000 c760c000 c9140947 c7112000 c711284e c0523f9c c0523f9c c010c0f2 00000001 c01040c7 c760c000 c7113ce4
Call Trace:
[<c9140947>] ath_newstate+0x157/0x490 [ath_pci]
[<c010c0f2>] timer_interrupt+0x132/0x270
[<c9179822>] ieee80211_next_scan+0x132/0x190 [wlan]
[<c9140690>] ath_next_scan+0x0/0x20 [ath_pci]
[<c0126a89>] run_timer_softirq+0xa9/0x1f0
[<c0122632>] __do_softirq+0x52/0xc0
[<c01226ea>] do_softirq+0x4a/0x50
[<c010dcd2>] do_IRQ+0x22/0x30
[<c0105873>] evtchn_do_upcall+0x63/0x90
[<c0109a1c>] hypervisor_callback+0x2c/0x34
[<c0107605>] xen_idle+0x35/0x70
[<c0107667>] cpu_idle+0x27/0x40
[<c05247ea>] start_kernel+0x17a/0x1e0
[<c0524360>] unknown_bootoption+0x0/0x1e0
Code: 3c 07 00 00 31 d2 c7 44 24 0c 01 00 00 00 89 3c 24 83 f8 03 0f 45 d0 8d 4 <0>Kernel panic - not syncing: Fatal exception in interrupt
(XEN) Domain 0 shutdown: rebooting machine.

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

<Prev in Thread] Current Thread [Next in Thread>