mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Badari Pulavarty <pbadari@us.ibm.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Andrew Vasquez <andrew.vasquez@qlogic.com>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.16-rc3 qlogic panic ?
Date: Thu, 16 Feb 2006 09:19:08 -0800	[thread overview]
Message-ID: <1140110348.29800.12.camel@dyn9047017100.beaverton.ibm.com> (raw)
In-Reply-To: <1140108765.4117.89.camel@laptopd505.fenrus.org>

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


  reply	other threads:[~2006-02-16 17:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-16 16:49 Badari Pulavarty
2006-02-16 16:52 ` Arjan van de Ven
2006-02-16 17:19   ` Badari Pulavarty [this message]
2006-02-16 17:19 ` Andrew Vasquez
2006-02-16 17:28   ` Badari Pulavarty

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=1140110348.29800.12.camel@dyn9047017100.beaverton.ibm.com \
    --to=pbadari@us.ibm.com \
    --cc=andrew.vasquez@qlogic.com \
    --cc=arjan@infradead.org \
    --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®