From: John David Anglin <dave.anglin@bell.net>
To: John David Anglin <dave.anglin@bell.net>
Cc: linux-parisc List <linux-parisc@vger.kernel.org>
Subject: Re: SCSI bug
Date: Sat, 20 Feb 2016 15:43:59 -0500 [thread overview]
Message-ID: <E2C8DBC2-F0AD-4C78-BD63-9C85B387E284@bell.net> (raw)
In-Reply-To: <82D4BF6F-05CF-4441-9530-79475BFF84F3@bell.net>
On 2016-02-20, at 3:13 PM, John David Anglin wrote:
> On 2016-01-23, at 1:00 PM, John David Anglin wrote:
>
>> WARNING: at block/blk-merge.c:454
>
> With linux-image-4.4.0-1-parisc64-smp on c3740, the above warning is the last message I see.
> Kernel seems to hang at that point. This is warning code:
>
> /*
> * Something must have been wrong if the figured number of
> * segment is bigger than number of req's physical segments
> */
> WARN_ON(nsegs > rq->nr_phys_segments);
On Sep. 12, 2015, I reported the following problem:
http://www.spinics.net/lists/linux-parisc/msg06327.html
Dave
--
John David Anglin dave.anglin@bell.net
next prev parent reply other threads:[~2016-02-20 20:43 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-23 18:00 SCSI bug John David Anglin
2016-02-20 20:13 ` John David Anglin
2016-02-20 20:43 ` John David Anglin [this message]
2016-02-20 21:59 ` Helge Deller
2016-02-20 22:52 ` John David Anglin
2016-02-21 2:52 ` John David Anglin
2016-02-21 3:47 ` James Bottomley
2016-02-21 14:45 ` John David Anglin
2016-02-21 18:10 ` James Bottomley
2016-02-21 18:09 ` John David Anglin
2016-02-21 18:13 ` James Bottomley
2016-02-21 18:43 ` John David Anglin
2016-02-21 19:07 ` James Bottomley
2016-02-21 19:36 ` Helge Deller
2016-02-21 20:28 ` James Bottomley
2016-02-21 21:09 ` John David Anglin
2016-02-21 21:17 ` Helge Deller
2016-02-21 21:49 ` James Bottomley
2016-02-21 22:08 ` John David Anglin
2016-02-22 0:53 ` John David Anglin
2016-02-22 3:24 ` John David Anglin
2016-02-23 3:04 ` John David Anglin
2016-02-23 18:06 ` Helge Deller
2016-02-23 19:10 ` John David Anglin
2016-02-21 20:42 ` John David Anglin
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=E2C8DBC2-F0AD-4C78-BD63-9C85B387E284@bell.net \
--to=dave.anglin@bell.net \
--cc=linux-parisc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.