linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Laurent Dufour <ldufour@linux.vnet.ibm.com>
To: Michael Ellerman <mpe@ellerman.id.au>, linuxppc-dev@lists.ozlabs.org
Subject: Re: kernel BUG at drivers/scsi/scsi_lib.c:1096!
Date: Wed, 18 Nov 2015 12:17:05 +0100	[thread overview]
Message-ID: <564C5E31.70200@linux.vnet.ibm.com> (raw)
In-Reply-To: <1447845043.7303.1.camel@ellerman.id.au>

On 18/11/2015 12:10, Michael Ellerman wrote:
> On Wed, 2015-11-18 at 12:06 +0100, Laurent Dufour wrote:
>> On 18/11/2015 10:18, Michael Ellerman wrote:
>>> Hi folks,
>>>
>>> I'm intermittently seeing the following oops on at least one powerpc box.
>>>
>>> The BUG_ON() is from:
>>>
>>> static int scsi_init_sgtable(struct request *req, struct scsi_data_buffer *sdb)
>>> {
>>> 	...
>>> 	count = blk_rq_map_sg(req->q, req, sdb->table.sgl);
>>> 	BUG_ON(count > sdb->table.nents);
>>>
>>> Looking at the dump it looks like count was 2, I can't work out what nents was.
>>>
>>> The machine's just a fairly boring bare metal setup, with a single IPR adapter:
>>>
>>> 0001:08:00.0 RAID bus controller: IBM PCI-E IPR SAS Adapter (ASIC) (rev 02)
>>> 	Subsystem: IBM PCIe3 x8 SAS RAID Internal Adapter 6Gb (57D7)
>>> 	Flags: bus master, fast devsel, latency 0
>>> 	Kernel driver in use: ipr
>>>
>>>
>>> Anyone seen it before or have any ideas?
>>
>> Hi Michael,
>>
>> I'm facing the same panic on my bare metal system.
>>
>> Sounds to be raised by the latest update to 4.4-rc1
> 
> Yeah I think it's new since 4.3.
> 
> Do you see it regularly, or just every now and then?

I got it almost every time I'm stressing the system's memory, but I
can't state if it's tied or not.

I can't remember having seeing it with 4.3, I'll double check that and
getting back to you.

Laurent.

  reply	other threads:[~2015-11-18 11:17 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-18  9:18 kernel BUG at drivers/scsi/scsi_lib.c:1096! Michael Ellerman
2015-11-18 11:06 ` Laurent Dufour
2015-11-18 11:10   ` Michael Ellerman
2015-11-18 11:17     ` Laurent Dufour [this message]
2015-11-18 14:03 ` Mark Salter
2015-11-19  1:02   ` Michael Ellerman
2015-11-19  8:23     ` Christoph Hellwig
2015-11-19 15:35       ` Hannes Reinecke
2015-11-20 14:38         ` Ewan Milne
2015-11-20 14:55           ` Hannes Reinecke
2015-11-20 15:28             ` Ewan Milne
2015-11-23  6:55               ` Hannes Reinecke
2015-11-25  9:04               ` Hannes Reinecke
2015-11-25 17:56                 ` Jens Axboe
2015-11-25 19:10                   ` Hannes Reinecke
2015-11-25 19:24                     ` Jens Axboe
2015-11-25 20:23                       ` Mike Snitzer
2015-11-25 21:20                         ` Mike Snitzer
2015-11-25 18:01                 ` Mike Snitzer
2015-11-25 19:01                   ` Hannes Reinecke
2015-12-04 16:59                     ` Takashi Iwai
2015-12-04 17:02                       ` Jens Axboe
2015-12-04 17:09                         ` Takashi Iwai
2015-11-20 12:10       ` Michael Ellerman
2015-11-20 12:56         ` Laurent Dufour
2015-11-20 13:37           ` Mark Salter
2015-11-21 11:30         ` Laurent Dufour
2015-11-21 16:56           ` Ming Lei
2015-11-22 23:20             ` Mark Salter
2015-11-23  0:36               ` Ming Lei
2015-11-23  1:50                 ` Mark Salter
2015-11-23  2:46                   ` Ming Lei
2015-11-23 15:21                     ` Ming Lei
2015-11-24 18:59                       ` Alan Ott
2015-11-23 13:57               ` Laurent Dufour
2015-11-23 15:13                 ` Pratyush Anand
2015-11-23 15:20                   ` Laurent Dufour
2015-11-23 15:27                     ` Ming Lei
2015-11-23 16:24                       ` Laurent Dufour
2015-11-24  1:30                       ` Mark Salter

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=564C5E31.70200@linux.vnet.ibm.com \
    --to=ldufour@linux.vnet.ibm.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mpe@ellerman.id.au \
    /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;
as well as URLs for NNTP newsgroup(s).