mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Zhang, Yanmin" <yanmin_zhang@linux.intel.com>
To: LKML <linux-kernel@vger.kernel.org>
Subject: Re: unable to handle kernel NULL pointer dereference in qla2x00_read_nvram_data
Date: Tue, 07 Aug 2007 11:28:59 +0800	[thread overview]
Message-ID: <1186457339.4688.213.camel@ymzhang> (raw)
In-Reply-To: <1186456912.4688.209.camel@ymzhang>

On Tue, 2007-08-07 at 11:21 +0800, Zhang, Yanmin wrote:
> Did someone see the same issue? My machine has a qla fiber card.
> 
> This error is triggered because parameter buf of qla2x00_read_nvram_data
> is 0.
Sorry for missing kernel info. I used kernel 2.6.23-rc2. My machine is
a x86_64, but I installed i386 os on it.

If I disable CONFIG_SCSI_QLOGIC_1280 and CONFIG_SCSI_QLA_FC in kernel config,
kernel could boot.


> 
> --yanmin
> 
> **********************Console log************************
> 
> 
> scsi 0:0:8:0: Processor         SUPER    GEM359 REV001    1.09 PQ: 0
> ANSI: 2
>  target0:0:8: asynchronous
>  target0:0:8: Beginning Domain Validation
>  target0:0:8: Ending Domain Validation
> ACPI: PCI Interrupt 0000:04:02.1[B] -> GSI 17 (level, low) -> IRQ 18
> scsi1 : Adaptec AIC79XX PCI-X SCSI HBA DRIVER, Rev 3.0
>         <Adaptec AIC7902 Ultra320 SCSI adapter>
>         aic7902: Ultra320 Wide Channel B, SCSI Id=7, PCI-X 67-100Mhz,
> 512 SCBs
> Adaptec aacraid driver 1.1-5[2449]-ms
> aic94xx: Adaptec aic94xx SAS/SATA driver version 1.0.3 loaded
> QLogic Fibre Channel HBA Driver
> ACPI: PCI Interrupt 0000:05:01.0[A] -> GSI 16 (level, low) -> IRQ 16
> qla2xxx 0000:05:01.0: Found an ISP2312, irq 16, iobase 0xf8862000
> qla2xxx 0000:05:01.0: Configuring PCI space...
> qla2xxx 0000:05:01.0: Configure NVRAM parameters...
> BUG: unable to handle kernel NULL pointer dereference at virtual address
> 00000000
>  printing eip:
> c04347db
> *pde = 00000000
> Oops: 0002 [#1]
> SMP 
> Modules linked in:
> CPU:    5
> EIP:    0060:[<c04347db>]    Not tainted VLI
> EFLAGS: 00010202   (2.6.23-rc2 #1)
> EIP is at qla2x00_read_nvram_data+0x25/0x56
> eax: 00005349   ebx: 00000000   ecx: 042d8138   edx: 0000007d
> esi: f7d9a34c   edi: 00000001   ebp: 00000001   esp: f7e85d98
> ds: 007b   es: 007b   fs: 00d8  gs: 0000  ss: 0068
> Process swapper (pid: 1, ti=f7e84000 task=f7e82000 task.ti=f7e84000)
> Stack: 00000000 c04347b6 00000000 f7d9a34c 00000000 c0425737 00000100
> 00000008 
>        f7dc0000 00000000 00000000 00000024 f7d9a34c f7d9a34c f7d9a34c
> c39cc000 
>        c398b13c f7d9a34c f7d9a34c f8862000 c0423db8 c06cbd17 c06ca4b9
> c398b13c    
> Call Trace:
> 
>  [<c04347b6>] qla2x00_read_nvram_data+0x0/0x56
> 
>  [<c0425737>] qla2x00_nvram_config+0x7e/0x765
> 
>  [<c0423db8>] qla2x00_initialize_adapter+0x113/0x226
> 
>  [<c04208e1>] qla2x00_probe_one+0x8ea/0xcb9
> 
>  [<c01aa54b>] sysfs_ilookup_test+0x0/0xd
> 
>  [<c0181acf>] ifind+0x8c/0x93
> 
>  [<c01aa54b>] sysfs_ilookup_test+0x0/0xd
> 
>  [<c01aba78>] sysfs_create_link+0xf1/0x149
> 
>  [<c02d7252>] pci_match_device+0x84/0xa4
> 
>  [<c02d72be>] pci_device_probe+0x36/0x57
> 
>  [<c034fc17>] driver_probe_device+0xe1/0x15f
> 
>  [<c034fd3b>] __driver_attach+0x0/0xab
> 
>  [<c034fdae>] __driver_attach+0x73/0xab
> 
>  [<c034f174>] bus_for_each_dev+0x37/0x59
> 
>  [<c034fa6f>] driver_attach+0x16/0x18
> 
>  [<c034fd3b>] __driver_attach+0x0/0xab
> 
>  [<c034f45e>] bus_add_driver+0x6d/0x170
> 
>  [<c02d73fa>] __pci_register_driver+0x53/0x7f
> 
>  [<c07df181>] qla2x00_module_init+0xd4/0xfe
> 
>  [<c07be477>] kernel_init+0x14d/0x2af
> 
>  [<c05a39ad>] _spin_unlock_irq+0x5/0x7
>  [<c0124469>] schedule_tail+0x37/0x91
>  [<c0104d32>] 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

  reply	other threads:[~2007-08-07  3:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-07  3:21 Zhang, Yanmin
2007-08-07  3:28 ` Zhang, Yanmin [this message]
2007-08-07  6:56   ` Dave Young

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1186457339.4688.213.camel@ymzhang \
    --to=yanmin_zhang@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®