From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 53281] megaraid_mbox kernel panic during boot
Date: Mon, 18 Mar 2013 11:52:34 +0000 (UTC) [thread overview]
Message-ID: <20130318115234.243B311FB85@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-53281-11613@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=53281
justgivemeafkenaccountplx@yahoo.co.uk changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |justgivemeafkenaccountplx@y
| |ahoo.co.uk
--- Comment #10 from justgivemeafkenaccountplx@yahoo.co.uk 2013-03-18 11:52:33 ---
I'm getting a very similar kernel dump on an LSI MegaRaid SATA 300-8X card.
(1000:0409) This card also uses the megaraid_mbox driver. Boots fine, but
crashes consistently when running badblocks -wsv over an array, usually within
an hour. Sometimes it will dump to console and flash the keyboard lights,
sometimes it just hangs.
Server is running nothing else at the moment beyond the basics, and the LSI
currently has no filesystems. I have no reason to suspect the card or the
server as both were running Win2003 server for the last 5 - 6 years without any
issues beyond the fact Windows was running on it :)
Ubuntu 12.04 i386 server, same results with Ubuntu kernel 3.5.0-25 and latest
compiled kernel 3.8.3. If there is any interest here I can post the kernel
dump, hardware details, etc. In a nutshell it's a single hyperthread P4 Xeon
2.4GHz on an Intel PCI-X server board with one jigglybyte of DDR1 ECC. LSI card
is running four 200GB SATA drives in a RAID5, configured with Write Through
caching and DirectIO, 128MB of cache, no backup battery.
I have tried various kernel flags to no avail but seemed to have some success
when I turned off all the performance enhancing settings in the LSI BIOS.
(Multiple PCI delayed transactions, command queuing, HDD write caching) It got
4 - 5 hours through badblocks without crashing but I stopped it as it was
taking forever. Could well have been just a result of decreased load though.
Turning hyperthread on/off makes no difference.
Currently testing various different settings in the LSI BIOS but it's slow
going. Any help would be appreciated here.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
prev parent reply other threads:[~2013-03-18 11:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-31 13:00 [Bug 53281] New: megaraid_mbox kernel panic during boot bugzilla-daemon
2013-01-31 13:05 ` [Bug 53281] " bugzilla-daemon
2013-01-31 13:05 ` bugzilla-daemon
2013-01-31 13:06 ` bugzilla-daemon
2013-01-31 13:07 ` bugzilla-daemon
2013-01-31 13:07 ` bugzilla-daemon
2013-01-31 13:07 ` bugzilla-daemon
2013-01-31 13:08 ` bugzilla-daemon
2013-01-31 13:19 ` bugzilla-daemon
2013-01-31 13:28 ` bugzilla-daemon
2013-03-18 11:52 ` bugzilla-daemon [this message]
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=20130318115234.243B311FB85@bugzilla.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 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).