Andrew,
I am not sure if its already reported. I get following panic
while using qla2200 on 2.6.16-rc3.
Thanks,
Badari
Unable to handle kernel NULL pointer dereference at 0000000000000000
RIP:
<ffffffff88042690>{:qla2xxx:qla2x00_mem_free+648}
PGD 1bddac067 PUD 1be314067 PMD 0
Oops: 0000 [1] SMP
CPU 0
Modules linked in: thermal processor fan button battery ac parport_pc lp
parport ipv6 sg qlogicfc qla2200 qla2300 qla2xxx ohci_hcd hw_random
usbcore dm_mod
Pid: 4601, comm: modprobe Tainted: GF 2.6.16-rc3 #1
RIP: 0010:[<ffffffff88042690>]
<ffffffff88042690>{:qla2xxx:qla2x00_mem_free+648}RSP:
0018:ffff8101be8b9d58 EFLAGS: 00010207
RAX: ffff81017df566a0 RBX: ffff81017df544b0 RCX: 0000000000000003
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffff81017df544b0 R08: 00000000ffffffff R09: 0000000000000003
R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000002400
R13: ffff81017df54000 R14: 0000000000000100 R15: ffffffffffffffff
FS: 00002b544141b6e0(0000) GS:ffffffff80575000(0000)
knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 0000000000000000 CR3: 00000001bdf1a000 CR4: 00000000000006e0
Process modprobe (pid: 4601, threadinfo ffff8101be8b8000, task
ffff8101beeaf100)Stack: 00000000ffffffff ffff81017df544b0
ffff81017df544b0 ffffffff880427fd
00000000fffffff4 ffffffff880445f0 ffff8101c13d3a00
ffff8101dfc2c000
0000000000000292 ffffffff80125c73
Call Trace: <ffffffff880427fd>{:qla2xxx:qla2x00_free_device+193}
<ffffffff880445f0>{:qla2xxx:qla2x00_probe_one+3860}
<ffffffff80125c73>{set_cpus_allowed+318}
<ffffffff803a3827>{__down+237}
<ffffffff80278910>{pci_device_probe+230}
<ffffffff80278978>{pci_bus_match+0}
<ffffffff802ca53e>{driver_probe_device+84}
<ffffffff802ca596>{__driver_attach+0}
<ffffffff802ca5ec>{__driver_attach+86}
<ffffffff802c9f86>{bus_for_each_dev+67}
<ffffffff802c9a5a>{bus_add_driver+114}
<ffffffff80278b2c>{__pci_register_driver+118}
<ffffffff801444e7>{sys_init_module+241}
<ffffffff8010a762>{system_call+126}
Code: 48 8b 2f 74 2d 48 8b 07 48 8b 57 08 48 89 50 08 48 89 02 48
RIP <ffffffff88042690>{:qla2xxx:qla2x00_mem_free+648} RSP
<ffff8101be8b9d58>
On Thu, 2006-02-16 at 08:49 -0800, Badari Pulavarty wrote:
> Andrew,
>
> I am not sure if its already reported. I get following panic
> while using qla2200 on 2.6.16-rc3.
>
> Thanks,
> Badari
>
> Unable to handle kernel NULL pointer dereference at 0000000000000000
> RIP:
> <ffffffff88042690>{:qla2xxx:qla2x00_mem_free+648}
> PGD 1bddac067 PUD 1be314067 PMD 0
> Oops: 0000 [1] SMP
> CPU 0
> Modules linked in: thermal processor fan button battery ac parport_pc lp
> parport ipv6 sg qlogicfc qla2200 qla2300 qla2xxx ohci_hcd hw_random
> usbcore dm_mod
> Pid: 4601, comm: modprobe Tainted: GF 2.6.16-rc3 #1
why are you using insmod -f ? are you sure that that wasn't an
incompatible module ?
(also loading BOTH qlogicfc and qla2200 is BAD)
On Thu, 2006-02-16 at 17:52 +0100, Arjan van de Ven wrote:
> On Thu, 2006-02-16 at 08:49 -0800, Badari Pulavarty wrote:
> > Andrew,
> >
> > I am not sure if its already reported. I get following panic
> > while using qla2200 on 2.6.16-rc3.
> >
> > Thanks,
> > Badari
> >
> > Unable to handle kernel NULL pointer dereference at 0000000000000000
> > RIP:
> > <ffffffff88042690>{:qla2xxx:qla2x00_mem_free+648}
> > PGD 1bddac067 PUD 1be314067 PMD 0
> > Oops: 0000 [1] SMP
> > CPU 0
> > Modules linked in: thermal processor fan button battery ac parport_pc lp
> > parport ipv6 sg qlogicfc qla2200 qla2300 qla2xxx ohci_hcd hw_random
> > usbcore dm_mod
> > Pid: 4601, comm: modprobe Tainted: GF 2.6.16-rc3 #1
>
> why are you using insmod -f ? are you sure that that wasn't an
> incompatible module ?
I am not using "insmod -f" intentionally. It happend on the boot.
> (also loading BOTH qlogicfc and qla2200 is BAD)
Okay. I built qlogicfc and qla2200 as modules. I removed qlogicfc module
completely, I don't the panic any more.
Thanks,
Badari
On Thu, 16 Feb 2006, Badari Pulavarty wrote:
> I am not sure if its already reported. I get following panic
> while using qla2200 on 2.6.16-rc3.
>
The qlogicfc driver attaches to 2100 and 2200 devices:
> Unable to handle kernel NULL pointer dereference at 0000000000000000
> RIP:
> <ffffffff88042690>{:qla2xxx:qla2x00_mem_free+648}
> PGD 1bddac067 PUD 1be314067 PMD 0
> Oops: 0000 [1] SMP
> CPU 0
> Modules linked in: thermal processor fan button battery ac parport_pc lp
> parport ipv6 sg qlogicfc qla2200 qla2300 qla2xxx ohci_hcd hw_random
> usbcore dm_mod
Choose either qlogicfc or qla2xxx to manage the 2200, not both.
> Pid: 4601, comm: modprobe Tainted: GF 2.6.16-rc3 #1
> RIP: 0010:[<ffffffff88042690>]
> <ffffffff88042690>{:qla2xxx:qla2x00_mem_free+648}RSP:
The crash is occuring due to PCI resources being held by qlogicfc and
qla2xxx bailing-out into it's cleanup routines.
The attached patch should handle the cleanup issues during resource
contention -- I'll workup a larger one for 2.6.17 to address the
clean-up-everything-in-one-function mess.
Thanks,
AV
---
diff --git a/drivers/scsi/qla2xxx/qla_os.c b/drivers/scsi/qla2xxx/qla_os.c
index 9f91f1a..df9c434 100644
--- a/drivers/scsi/qla2xxx/qla_os.c
+++ b/drivers/scsi/qla2xxx/qla_os.c
@@ -1311,8 +1311,11 @@ int qla2x00_probe_one(struct pci_dev *pd
/* Configure PCI I/O space */
ret = qla2x00_iospace_config(ha);
- if (ret)
- goto probe_failed;
+ if (ret) {
+ scsi_host_put(host);
+ pci_release_regions(pdev);
+ goto probe_disable_device;
+ }
qla_printk(KERN_INFO, ha,
"Found an ISP%04X, irq %d, iobase 0x%p\n", pdev->device, pdev->irq,
On Thu, 2006-02-16 at 09:19 -0800, Andrew Vasquez wrote:
> On Thu, 16 Feb 2006, Badari Pulavarty wrote:
>
> > I am not sure if its already reported. I get following panic
> > while using qla2200 on 2.6.16-rc3.
> >
>
> The qlogicfc driver attaches to 2100 and 2200 devices:
>
> > Unable to handle kernel NULL pointer dereference at 0000000000000000
> > RIP:
> > <ffffffff88042690>{:qla2xxx:qla2x00_mem_free+648}
> > PGD 1bddac067 PUD 1be314067 PMD 0
> > Oops: 0000 [1] SMP
> > CPU 0
> > Modules linked in: thermal processor fan button battery ac parport_pc lp
> > parport ipv6 sg qlogicfc qla2200 qla2300 qla2xxx ohci_hcd hw_random
> > usbcore dm_mod
>
> Choose either qlogicfc or qla2xxx to manage the 2200, not both.
Yep. I had built both qlogicfc and qla2200 as modules. I took out
qlogicfc module out, things are fine now.
Thanks,
Badari