From: Rob Landley <rob@landley.net>
To: qemu-devel@nongnu.org
Cc: Quentin Barnes <qbarnes@urbana.css.mot.com>
Subject: Re: [Qemu-devel] Intermittant linux kernel panic on arm
Date: Fri, 9 Mar 2007 19:05:27 -0500 [thread overview]
Message-ID: <200703091905.28445.rob@landley.net> (raw)
In-Reply-To: <20070307181433.GA2911@urbana.css.mot.com>
On Wednesday 07 March 2007 1:14 pm, Quentin Barnes wrote:
> This is my first post to the list. Hopefully, it will go well.
>
> I've been using the ARM qemu for Linux development for some basic
> work, but wanted to expand and do more with it. I outgrew the
> initrd limitation and needed a disk. Since I've been using a disk,
> I've been getting intermittant panics during the udevd phase of
> boot. Once the system is up though, it's been stable.
>
> The panic occurs about 50%-75% the time. I've had this problem on both
> 0.9.0 and the 2007-03-07_05 snapshot. I've had this problem using both
> my own 2.6.19-1 ARM kernel made directly from kernel.org as well as
> Aurelien Jarno's 2.6.18 Debian ARM kernel at
> http://people.debian.org/~aurel32/arm-versatile/vmlinuz-2.6.18-4-versatile
The first thing I'd do is try to figure out what's udev doing to trigger this
panic?
> r7 = 00000036 r6 = 00002285 r5 = FFFFFFF7 r4 = C0BA0D20
> [<c0089334>] (sys_ioctl+0x0/0x64) from [<c00228c0>]
(ret_fast_syscall+0x0/0x2c)
Is there any way you can figure out which ioctl this is? Presumably udev read
something from /sys that told it to mknod something in /dev. I'm not quite
sure where an ioctl comes into this...
If you could get a small C program that triggers the panic, and a
kernel .config you built your kernel with, that would be helpful.
Rob
--
Vista: Windows Millenium Second Edition
next prev parent reply other threads:[~2007-03-10 0:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-07 18:14 [Qemu-devel] Intermittant linux kernel panic on arm Quentin Barnes
2007-03-10 0:05 ` Rob Landley [this message]
2007-03-12 5:33 ` Quentin Barnes
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=200703091905.28445.rob@landley.net \
--to=rob@landley.net \
--cc=qbarnes@urbana.css.mot.com \
--cc=qemu-devel@nongnu.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).