From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 13311] mptsas: ioc0: removing ssp device, kernel oops
Date: Tue, 9 Jun 2009 21:27:08 GMT [thread overview]
Message-ID: <200906092127.n59LR8i6015475@demeter.kernel.org> (raw)
In-Reply-To: <bug-13311-11613@http.bugzilla.kernel.org/>
http://bugzilla.kernel.org/show_bug.cgi?id=13311
--- Comment #3 from Mike Loseke <mike.tummy@gmail.com> 2009-06-09 21:27:07 ---
On Thu, May 28, 2009 at 2:00 AM, Andrew Morton
<akpm@linux-foundation.org> wrote:
>
> (switched to email. Please respond via emailed reply-to-all, not via the
> bugzilla web interface).
>
> On Thu, 14 May 2009 18:17:10 GMT bugzilla-daemon@bugzilla.kernel.org wrote:
>
> > http://bugzilla.kernel.org/show_bug.cgi?id=13311
> >
> > Summary: mptsas: ioc0: removing ssp device, kernel oops
>
> I'd have thought that the severity of this problem is not matched by
> the response.
>
> > Product: SCSI Drivers
> > Version: 2.5
> > Kernel Version: 2.6.27.21
>
> Is it reproducible? If so, is there any change that it can be retested
> under a 2.6.29-based kernel?
We've put a 2.6.29 kernel on these two systems and experienced another
kernel oops yesterday. So far, we haven't been able to reproduce it
on demand, but it has occurred under a heavier system load each time
(load average of 16 with 2,000 blocks/sec every 5 seconds writes to
the devices attached using the mptsas driver.
The oops from yesterday isn't identical to the previous oops, but the
end result is the same where the system has to be rebooted. I've
attached that the log capture of the oops.
The system is identical to the original specs, just the kernel has changed:
# cat /proc/version
Linux version 2.6.29.4-0.1-default (root@tile01-primary) (gcc version
4.3.2 [gcc-4_3-branch revision 141291] (SUSE Linux) ) #1 SMP Tue May
26 22:50:58 CDT 2009
Hopefully this is helpful.
Mike
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-06-09 21:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-14 18:17 [Bug 13311] New: mptsas: ioc0: removing ssp device, kernel oops bugzilla-daemon
2009-05-28 8:00 ` Andrew Morton
2009-05-28 11:54 ` Kay Sievers
2009-06-09 21:27 ` Mike Loseke
2009-06-09 21:52 ` Andrew Morton
2009-05-28 8:01 ` [Bug 13311] " bugzilla-daemon
2009-05-28 11:54 ` bugzilla-daemon
2009-06-09 21:27 ` bugzilla-daemon [this message]
2009-06-09 21:30 ` bugzilla-daemon
2009-06-09 21:53 ` bugzilla-daemon
2009-07-16 21:41 ` bugzilla-daemon
[not found] <bug-13311-11613@https.bugzilla.kernel.org/>
2012-06-07 10:49 ` bugzilla-daemon
2012-06-07 10:49 ` bugzilla-daemon
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=200906092127.n59LR8i6015475@demeter.kernel.org \
--to=bugzilla-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.