From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: "Miller, Mike (OS Dev)" <Mike.Miller@hp.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: Fri, 22 Aug 2008 12:02:17 -0500 [thread overview]
Message-ID: <1219424538.3339.51.camel@localhost.localdomain> (raw)
In-Reply-To: <48AEEE0A.1010900@oracle.com>
On Fri, 2008-08-22 at 09:49 -0700, Randy Dunlap wrote:
> James Bottomley wrote:
> > On Fri, 2008-08-22 at 15:48 +0000, Miller, Mike (OS Dev) wrote:
> >>> -----Original Message-----
> >>> From: Randy Dunlap [mailto:randy.dunlap@oracle.com]
> >>> Sent: Thursday, August 21, 2008 7:27 PM
> >>> To: Miller, Mike (OS Dev)
> >>> Cc: lkml; scsi; akpm
> >>> Subject: Re: in 2.6.23-rc3-git7 in do_cciss_intr
> >>>
> >>> On Thu, 21 Aug 2008 16:25:24 +0000 Miller, Mike (OS Dev) wrote:
> >>>
> >>>>>> Randy,
> >>>>>> We know of a race condition in cciss_init_one. It's fixed
> >>>>> in 2.6.26 I believe. Here's the patch:
> >>>>>>
> >>> http://groups.google.com/group/linux.kernel/browse_thread/thread/7b3
> >>>>> 9f
> >>> 2b77622ab03/4f5f45c008655ca1?hl=en&lnk=gst&q=cciss#4f5f45c008655ca
> >>>>>> 1
> >>>>>
> >>>>> Mike,
> >>>>> Sorry, but my fingers have typoed the $subject. My bad.
> >>>>> Kernel is 2.6.27-rc3-git7 (from above):
> >>>>>
> >>>>>>>>> Modules linked in: cciss(+) ehci_hcd ohci_hcd uhci_hcd
> >>>>>>>>> Pid: 0, comm: swapper Not tainted 2.6.27-rc3-git7 #1
> >>>>>>>>> RIP: 0010:[<ffffffffa001bb68>] [<ffffffffa001bb68>]
> >>>>>>>>> do_cciss_intr+0x627/0xa6c [cciss]
> >>>> Hmmmmm, let me know what happens from your retest. I'll
> >>> look at this
> >>>> as soon as I finish what I'm doing now. We trying to spin
> >>> for our test
> >>>> teams but I have something hopelessly broken. :(
> >>> It didn't BUG in the retest. That just means that it's more
> >>> difficult to find/fix, right?
> >> Yup.
> >
> > Randy,
> >
> > If you can't reproduce it, could you use the debug information or gdb to
> > tell us what line in the source code this:
> >
> > do_cciss_intr+0x627
> >
> > corresponds to? That might help isolating the problem.
>
>
> Sure, here's an attempt at that. Please let me know if you want it
> differently or some other info.
> (gdb) x/20i do_cciss_intr+0x627
> 0x3b68 <do_cciss_intr+1575>: mov %rdx,0x248(%rax)
> 0x3b6f <do_cciss_intr+1582>: mov 0x248(%rbx),%rdx
> 0x3b76 <do_cciss_intr+1589>: mov %rax,0x240(%rdx)
> 0x3b7d <do_cciss_intr+1596>: jmp 0x3b8b <do_cciss_intr+1610>
> 0x3b7f <do_cciss_intr+1598>: movq $0x0,0x100c0(%r12)
> 0x3b8b <do_cciss_intr+1610>: mov 0x234(%rbx),%eax
> 0x3b91 <do_cciss_intr+1616>: test %eax,%eax
> 0x3b93 <do_cciss_intr+1618>: jne 0x3f27 <do_cciss_intr+2534>
> 0x3b99 <do_cciss_intr+1624>: mov 0x250(%rbx),%r14
> 0x3ba0 <do_cciss_intr+1631>: movl $0x0,0xcc(%r14)
> 0x3bab <do_cciss_intr+1642>: mov 0x228(%rbx),%r8
> 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
next prev parent reply other threads:[~2008-08-22 17:02 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 [this message]
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
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=1219424538.3339.51.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=Mike.Miller@hp.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
/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