[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <000001c72f87$5bd8e520$ce34030a@amr.corp.intel.com>
Date: Wed, 3 Jan 2007 14:34:38 -0800
From: "Chen, Kenneth W" <kenneth.w.chen@...el.com>
To: "'Jens Axboe'" <jens.axboe@...cle.com>
Cc: "Andrew Morton" <akpm@...l.org>, <linux-kernel@...r.kernel.org>,
"Nick Piggin" <nickpiggin@...oo.com.au>,
"Nick Piggin" <npiggin@...e.de>
Subject: RE: [PATCH] 4/4 block: explicit plugging
Jens Axboe wrote on Wednesday, January 03, 2007 2:30 PM
> > We are having some trouble with the patch set that some of our fiber channel
> > host controller doesn't initialize properly anymore and thus lost whole
> > bunch of disks (somewhere around 200 disks out of 900) at boot time.
> > Presumably FC loop initialization command are done through block layer etc.
> > I haven't looked into the problem closely.
> >
> > Jens, I assume the spin lock bug in __blk_run_queue is fixed in this patch
> > set?
>
> It is. Are you still seeing problems after the initial mail exchange we
> had prior to christmas,
Yes. Not the same kernel panic, but a problem with FC loop reset itself.
> or are you referencing that initial problem?
No. we got passed that point thanks for the bug fix patch you give me
prior to Christmas. That fixed a kernel panic on boot up.
> It's not likely to be a block layer issue, more likely the SCSI <->
> block interactions. If you mail me a new dmesg (if your problem is with
> the __blk_run_queue() fixups), I can take a look. Otherwise please do
> test with the __blk_run_queue() fixup, just use the current patchset.
I will just retake the tip of your plug tree and retest.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists