From: John Rigg <lk@sound-man.co.uk>
To: linux-kernel@vger.kernel.org
Subject: 2.6.13-rt13 SMP crashes on boot
Date: Mon, 19 Sep 2005 19:54:26 +0100 [thread overview]
Message-ID: <E1EHQmY-0001MS-8L@localhost.localdomain> (raw)
I've been trying to get 2.6.13 with RT-preempt patch to run on my
dual Opteron with debugging code (with CONFIG_PREEMPT_RT=y).
It crashes on boot if I enable latency tracing in .config. This happens
with -rt13, -rt12, and -rt4 versions of the patch. Unfortunately it
occurs before any logging, so I can't provide any log data.
The crash appears to happen just after drive hda is
detected, while it's trying to mount my ext3 / filesystem (on hda7).
The mount fails then the screen fills with a segfault message in an
infinite loop:
segfault at ffffffff8010f20c rip ffffffff8010f20c rsp 00007fffffacdc88
A hard reboot is then required.
Without latency tracing it boots and runs fine with the following:
Kernel debug
MagicSysRq
Detect soft lockups
Wakeup latency timing
Compile with debug info
Collect scheduler stats
Debug preemptible kernel
With latency tracing the crash occurs even if I disable all other
kernel hacking except for
Magic SysRq, Wakeup latency timing, and Compile w. debug info.
Hardware is 2 x Opteron 240, MSI K8T Master2-FAR (VIA K8T 800) m/board,
1GB ECC RAM. System is Debian amd64 unstable (gcc-4.0_4.0.1-7,
binutils_2.16.1cvs20050902-1).
Copy of .config and lspci output are here:
http://www.sound-man.co.uk/crash
Regards,
John
next reply other threads:[~2005-09-19 18:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-19 18:54 John Rigg [this message]
2005-09-19 20:49 ` Steven Rostedt
2005-09-19 20:54 ` Thomas Gleixner
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=E1EHQmY-0001MS-8L@localhost.localdomain \
--to=lk@sound-man.co.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®