From: Randy Dunlap <randy.dunlap@oracle.com>
To: Jens Axboe <jens.axboe@oracle.com>
Cc: "Miller, Mike (OS Dev)" <Mike.Miller@hp.com>,
James Bottomley <James.Bottomley@hansenpartnership.com>,
lkml <linux-kernel@vger.kernel.org>,
scsi <linux-scsi@vger.kernel.org>,
akpm <akpm@linux-foundation.org>
Subject: Re: in 2.6.23-rc3-git7 in do_cciss_intr
Date: Thu, 25 Sep 2008 13:33:07 -0700 [thread overview]
Message-ID: <48DBF583.3050307@oracle.com> (raw)
In-Reply-To: <20080905092838.GS20055@kernel.dk>
Jens Axboe wrote:
> On Thu, Sep 04 2008, Miller, Mike (OS Dev) wrote:
>>>>>> 0x3bb2 <do_cciss_intr+1649>: mov 0x2(%r8),%dx
>>>>>> 0x3bb7 <do_cciss_intr+1654>: test %dx,%dx
>>>>>> 0x3bba <do_cciss_intr+1657>: je 0x3f0e <do_cciss_intr+2509>
>>>>>>
>>>>>>
>>>>>> $ addr2line -e cciss.o -f do_cciss_intr+0x627 SA5_fifo_full
>>>>>>
>>> /home/rdunlap/linsrc/linux-2.6.27-rc3-git7/drivers/block/cciss.h:206
>>>>> OK ...that's confusing. It seems to be saying that ctrlr_info_t *
>>>>> was NULL. However, I can't see a way of getting into the
>>> fifo_full
>>>>> callback from do_cciss_intr ..
>>>>> especially not with an NULL host.
>>>>>
>>>>> James
>>>> That is weird. Even if we could get there fifo_full doesn't
>>> do anything but wait for a bit.
>>>
>>> Hi,
>>>
>>> This just happened again. This time it's on 2.6.27-rc5-git3.
>>>
>>> ~Randy
>> Thanks Randy. I think. :)
>>
>> I'll try to recreate in my lab.
>
> This looks somewhat strange, mostly like 'c' is NULL and it's oopsing in
> in removeQ (I don't think Randy's analysis is correct in assuming it's
> 'h' and it's in fifo_full). Given that 'c' cannot be NULL, it's c->prev
> or c->next that are NULL.
Yes, correct IMO. I checked my daily test logs and I have had this problem
in do_cciss_intr() 3 times, all at the same location, which appears to be
in removeQ(), as Jens says.
--
~Randy
next prev parent reply other threads:[~2008-09-25 20:33 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-21 5:52 BUG: in 2.6.23-rc3-git7 in do_cciss_intr rdunlap
2008-08-21 7:16 ` Andrew Morton
2008-08-21 14:26 ` Miller, Mike (OS Dev)
2008-08-21 15:43 ` Randy Dunlap
2008-08-21 15:48 ` Miller, Mike (OS Dev)
2008-08-21 16:15 ` Randy Dunlap
2008-08-21 16:25 ` Miller, Mike (OS Dev)
2008-08-22 0:26 ` Randy Dunlap
2008-08-22 15:48 ` Miller, Mike (OS Dev)
2008-08-22 15:54 ` James Bottomley
2008-08-22 16:49 ` Randy Dunlap
2008-08-22 17:02 ` James Bottomley
2008-08-22 18:25 ` Miller, Mike (OS Dev)
2008-09-04 16:59 ` Randy Dunlap
2008-09-04 18:00 ` Miller, Mike (OS Dev)
2008-09-05 9:28 ` Jens Axboe
2008-09-25 20:33 ` Randy Dunlap [this message]
2008-09-25 20:40 ` Randy Dunlap
2008-09-25 20:56 ` Miller, Mike (OS Dev)
2008-11-18 20:14 ` Randy Dunlap
2008-11-18 20:20 ` Randy Dunlap
2008-11-18 21:32 ` Randy Dunlap
2008-11-19 8:52 ` Jens Axboe
2008-11-19 17:00 ` Miller, Mike (OS Dev)
2008-11-19 17:22 ` Randy Dunlap
2008-11-19 17:27 ` Miller, Mike (OS Dev)
2008-11-19 17:29 ` Jens Axboe
2008-11-19 19:15 ` Miller, Mike (OS Dev)
2008-11-19 20:46 ` Jens Axboe
2008-11-20 9:13 ` Jens Axboe
2008-11-20 16:41 ` Miller, Mike (OS Dev)
2008-11-20 17:50 ` Jens Axboe
2008-11-20 19:12 ` Miller, Mike (OS Dev)
2008-11-19 17:18 ` Randy Dunlap
2008-11-18 21:32 ` Miller, Mike (OS Dev)
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=48DBF583.3050307@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=Mike.Miller@hp.com \
--cc=akpm@linux-foundation.org \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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