From: Thomas Kleffel <lkml@maintech.de>
To: linux-kernel@vger.kernel.org
Subject: Bug report for linux-2.6.0-test7: System crashes when I try to start my software raid
Date: Sat, 11 Oct 2003 02:24:38 +0200 [thread overview]
Message-ID: <3F874DC6.7090404@maintech.de> (raw)
Hi!
Today I wanted to give 2.6.0 a try on my fileserver. It's got a software
raid (md - no evms) with 11*120GB IDE. When I tried to start it
(raidstart /dev/md0) my system crashed badly. It didnt react to anything
but magic sysreq. The last thing I could see was an (incomplete) stack
trace. Incomplete beacause scrollback didn't work anymore. It looks like
the crashes didn't trash my data or raid headers.
I can reproduce the bug - it happens everytime when I try to start my raid.
I already tried to disable DMA - didn't help. The system worked fine for
over a year with 2.4.x kernels. Currently I run 2.4.22_pre2-gss (a
gentoo flavour).
I am willing to help anyone who wants to fix this as good as I can. This
includes giving informations, testing, etc... just contact me.
If there's a better place than this list for posting this report, please
tell me.
Thanks for helping,
Thomas Kleffel
Some information that might be helpful:
lspci:
00:00.0 Host bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133]
(rev 03)
00:01.0 PCI bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133 AGP]
00:04.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South]
(rev 40)
00:04.1 IDE interface: VIA Technologies, Inc.
VT82C586A/B/VT82C686/A/B/VT8233/A/C/VT8235 PIPC Bus Master IDE (rev 06)
00:04.3 USB Controller: VIA Technologies, Inc. USB (rev 16)
00:04.4 Bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev 40)
00:09.0 Ethernet controller: 3Com Corporation 3c905C-TX/TX-M [Tornado]
(rev 78)
00:0a.0 Unknown mass storage controller: Triones Technologies, Inc.
HPT366/368/370/370A/372 (rev 03)
00:11.0 Unknown mass storage controller: Promise Technology, Inc. 20265
(rev 02)
01:00.0 VGA compatible controller: 3Dfx Interactive, Inc. Voodoo Banshee
(rev 03)
cpuinfo:
processor : 0
vendor_id : AuthenticAMD
cpu family : 6
model : 4
model name : AMD Athlon(tm) Processor
stepping : 2
cpu MHz : 1109.910
cache size : 256 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 sep mtrr pge mca
cmov pat pse36 mmx fxsr syscall mmxext 3dnowext 3dnow
bogomips : 2215.11
reply other threads:[~2003-10-11 0:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3F874DC6.7090404@maintech.de \
--to=lkml@maintech.de \
--cc=linux-kernel@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.