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-devel

RE: [Xen-devel] qla2xxx driver failed in dom0 - invalid opcode: 0000[1]

To: "Brancato, Mike" <mike.brancato@xxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] qla2xxx driver failed in dom0 - invalid opcode: 0000[1] SMP
From: "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
Date: Fri, 14 Jul 2006 10:52:29 +0100
Delivery-date: Fri, 14 Jul 2006 02:55:36 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcanHiYTPRhzTIHmSgWzBOJtjCzEsQADMO/w
Thread-topic: [Xen-devel] qla2xxx driver failed in dom0 - invalid opcode: 0000[1] SMP
> I wanted to post this in case there is a real bug here.
> 
> The system this is on is running Debian Etch with the Xen packages
from
> Debian Unstable (currently 3.0.2+hg9697-1).  I am running all packaged
> software so this is probably slightly out of date.

It would be interesting to see if this can be repro'ed on a tree built
from a recent xen-unstable.hg. There's been changes to the fault
handling code that could well have fixed this.

Thanks,
Ian

 
> This is on an HP DL320 G4 with a Pentium D 930 processor.  I tried
unloading
> and reloading the qla2xxx module, but rmmod reported it in use,
however it
> did not seem to be used by any other module.
> 
> dmesg output below:
> 
> QLogic Fibre Channel HBA Driver
> qla2xxx 0000:06:01.0: Found an ISP2312, irq 16, iobase
0xffffc2000001e000
> qla2xxx 0000:06:01.0: Configuring PCI space...
> qla2xxx 0000:06:01.0: Configure NVRAM parameters...
> ----------- [cut here ] --------- [please bite here ] ---------
> Kernel BUG at arch/x86_64/mm/fault-xen.c:292
> invalid opcode: 0000 [1] SMP
> CPU 1
> Modules linked in: qla2xxx libata firmware_class tg3 scsi_transport_fc
> psmouse serio_raw serial_core ext3 jbd mbcache cciss scsi_mod
> Pid: 2163, comm: modprobe Not tainted 2.6.16-2-xen-em64t-p4 #1
> RIP: e030:[<ffffffff801166f7>] <ffffffff801166f7>{do_page_fault+1656}
> RSP: e02b:ffff88000ec1daf8  EFLAGS: 00010287
> RAX: ffff800000000000 RBX: ffff880000c6a000 RCX: 00003ffffffff000
> RDX: 00000000000fdff0 RSI: ffff880000c690f0 RDI: 0000000000010800
> RBP: ffff880000000000 R08: 0000000000010800 R09: 0000000000000000
> R10: 0000000003c69067 R11: ffff880001000000 R12: ffffc2000001e00e
> R13: ffff88000ec1dbe8 R14: ffff88000e2cf140 R15: 0000000000000002
> FS:  00002ad5ad5566d0(0000) GS:ffffffff80407080(0000)
knlGS:0000000000000000
> CS:  e033 DS: 0000 ES: 0000
> Process modprobe (pid: 2163, threadinfo ffff88000ec1c000, task
> ffff88000e2cf140)
> Stack: ffffffffffffd028 ffff880000c6b000 0000000000002fd8
0000000000030001
>        0000000000000246 ffffffff801e7166 000000000000001e
0000000000000034
>        0000000000030000 ffffffff8010722a
> Call Trace: <ffffffff801e7166>{vgacon_cursor+0}
> <ffffffff8010722a>{hypercall_page+554}
>        <ffffffff8010722a>{hypercall_page+554}
> <ffffffff8023729f>{force_evtchn_callback+10}
>        <ffffffff8010b403>{error_exit+0}
> <ffffffff801e03d4>{__pci_find_next_cap+100}
>        <ffffffff801e03d4>{__pci_find_next_cap+100}
> <ffffffff880d7a5f>{:qla2xxx:qla2x00_get_nvram_word+72}
>        <ffffffff880d7a97>{:qla2xxx:qla2x00_get_nvram_word+128}
>        <ffffffff801e03d4>{__pci_find_next_cap+100}
> <ffffffff880d7ae5>{:qla2xxx:qla2x00_read_nvram_data+41}
>        <ffffffff880ca5e3>{:qla2xxx:qla2x00_nvram_config+137}
>        <ffffffff880cd48f>{:qla2xxx:qla2x00_initialize_adapter+243}
>        <ffffffff880c83cd>{:qla2xxx:qla2x00_probe_one+3594}
>        <ffffffff80121dc0>{__wake_up+54}
> <ffffffff801e2220>{pci_device_probe+74}
>        <ffffffff802334a1>{driver_probe_device+82}
> <ffffffff80233550>{__driver_attach+0}
>        <ffffffff802335a6>{__driver_attach+86}
> <ffffffff80232ae4>{bus_for_each_dev+67}
>        <ffffffff80232ddd>{bus_add_driver+110}
> <ffffffff801e7166>{vgacon_cursor+0}
>        <ffffffff801e1e2a>{__pci_register_driver+128}
> <ffffffff88078e5b>{:scsi_transport_fc:fc_attach_transport+216}
>        <ffffffff880e908f>{:qla2xxx:qla2x00_module_init+143}
>        <ffffffff80142b2e>{sys_init_module+240}
> <ffffffff8010acea>{system_call+134}
>        <ffffffff8010ac64>{system_call+0}
> 
> Code: 0f 0b 68 aa 8f 2e 80 c2 24 01 e9 59 04 00 00 41 f6 c7 08 74
> RIP <ffffffff801166f7>{do_page_fault+1656} RSP <ffff88000ec1daf8>
> 
> A soft reboot from the dom0 produced a successful load the second
time:
> 
> QLogic Fibre Channel HBA Driver
> qla2xxx 0000:06:01.0: Found an ISP2312, irq 16, iobase
0xffffc2000001e000
> qla2xxx 0000:06:01.0: Configuring PCI space...
> qla2xxx 0000:06:01.0: Configure NVRAM parameters...
> qla2xxx 0000:06:01.0: Verifying loaded RISC code...
> qla2xxx 0000:06:01.0: Waiting for LIP to complete...
> qla2xxx 0000:06:01.0: LIP reset occured (f700).
> qla2xxx 0000:06:01.0: LOOP UP detected (2 Gbps).
> qla2xxx 0000:06:01.0: Topology - (F_Port), Host Loop address 0xffff
> scsi0 : qla2xxx
> qla2xxx 0000:06:01.0:
>  QLogic Fibre Channel HBA Driver: 8.01.04-k
>   QLogic QLA2340 -
>   ISP2312: PCI-X (133 MHz) @ 0000:06:01.0 hdma-, host#=0, fw=3.03.20
IPX
> scsi: unknown device type 12
>   Vendor: COMPAQ    Model: MSA1000           Rev: 5.02
>   Type:   RAID                               ANSI SCSI revision: 04
>   Vendor: COMPAQ    Model: MSA1000 VOLUME    Rev: 5.02
>   Type:   Direct-Access                      ANSI SCSI revision: 04
>   Vendor: COMPAQ    Model: MSA1000 VOLUME    Rev: 5.02
>   Type:   Direct-Access                      ANSI SCSI revision: 04
> 
> --
> Michael Brancato, CISSP, CCNA
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel

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

<Prev in Thread] Current Thread [Next in Thread>
  • RE: [Xen-devel] qla2xxx driver failed in dom0 - invalid opcode: 0000[1] SMP, Ian Pratt <=