All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugme-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 12195] "dd" make kernel panic
Date: Thu, 11 Dec 2008 07:17:26 -0800 (PST)	[thread overview]
Message-ID: <20081211151726.EF777108042@picon.linux-foundation.org> (raw)
In-Reply-To: <bug-12195-11613@http.bugzilla.kernel.org/>

http://bugzilla.kernel.org/show_bug.cgi?id=12195





------- Comment #5 from anonymous@kernel-bugs.osdl.org  2008-12-11 07:17 -------
Reply-To: James.Bottomley@HansenPartnership.com

On Thu, 2008-12-11 at 01:05 -0800, bugme-daemon@bugzilla.kernel.org
wrote:
> I instrumented kernel. below is some finding.
> 1) The disk isn't stable. If we run dd in a loop, sometimes the disk doesn't
> work, so block request will expire to start a scsi error handling;
> 2) fussion driver has its own periodic (1 sec) checking in
> mpt_fault_reset_work. If something is wrong, it will do a hardware reset and
> flush all pending requests;
> 3) Step 1) and 2) have a race that a request might be flushed in step 2), but
> step 1) releases the request firstly. Later on, when SOFTIRQ tries to release
> the scsi_cmnd, kernel panic.

OK, so to rule out the block timer problems which we think are fixed,
could you reproduce on 2.6.28-rc8.

Also, the routine 

> [<a000000100391cf0>] scsi_softirq_done+0x50/0x2e0
>                                 sp=e000000008a97e10 bsp=e000000008a90d70

Is hard to diagnose. Could you ask gdb or addr2line which actual source
line this is?

Thanks,

James


-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

  parent reply	other threads:[~2008-12-11 15:18 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-11  2:07 [Bug 12195] New: "dd" make kernel panic bugme-daemon
2008-12-11  2:09 ` [Bug 12195] " bugme-daemon
2008-12-11  2:15 ` bugme-daemon
2008-12-11  3:12 ` bugme-daemon
2008-12-11  9:05 ` bugme-daemon
2008-12-11 15:17   ` James Bottomley
2008-12-11  9:26 ` bugme-daemon
2008-12-11 15:17 ` bugme-daemon [this message]
2008-12-11 19:45 ` bugme-daemon
2008-12-12  2:27 ` bugme-daemon
2008-12-12 10:22   ` Mike Anderson
2008-12-12 15:09     ` James Bottomley
2008-12-12 19:28       ` James Bottomley
2008-12-12 10:22 ` bugme-daemon
2008-12-12 15:09 ` bugme-daemon
2008-12-12 19:28 ` bugme-daemon
2008-12-13 17:58 ` bugme-daemon
2008-12-15  9:52 ` bugme-daemon
2008-12-15 10:39 ` bugme-daemon
2008-12-15 20:13   ` James Bottomley
2008-12-15 20:13 ` bugme-daemon
2008-12-16  5:12 ` bugme-daemon
2008-12-21 19:52 ` bugme-daemon
2008-12-13 16:29 2.6.28-rc8-git1: Reported regressions from 2.6.27 Rafael J. Wysocki
2008-12-13 16:33 ` [Bug #12195] "dd" make kernel panic Rafael J. Wysocki
2008-12-13 16:33   ` Rafael J. Wysocki
2008-12-20 21:56 2.6.28-rc9-git1: Reported regressions from 2.6.27 Rafael J. Wysocki
2008-12-20 22:00 ` [Bug #12195] "dd" make kernel panic Rafael J. Wysocki
2008-12-20 22:00   ` Rafael J. Wysocki
2008-12-21 13:52   ` James Bottomley
2008-12-21 13:52     ` James Bottomley
2008-12-21 19:52     ` Rafael J. Wysocki
2008-12-21 19:52       ` Rafael J. Wysocki

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=20081211151726.EF777108042@picon.linux-foundation.org \
    --to=bugme-daemon@bugzilla.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 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.