From: Aurelien Jarno <aurelien@aurel32.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] sparc32: kernel crash while writing to disk
Date: Sun, 24 Sep 2006 14:52:40 +0200 [thread overview]
Message-ID: <20060924125239.GA3117@sparc.aurel32.net> (raw)
Hi,
I have successfully installed a Debian instable on an emulated
SparcStation 5 by QEMU. Globally it works correctly, but I have
experienced a few kernel crashes, due to a problem with the ESP
controller. It seems to occur while writing a high volume of data to
disk, although that not always crash the kernel. Note that I am using
the CVS version of QEMU.
You will find the kernel log below. Does somebody have an idea? I don't
know how to debug such a thing, but I can make some tests if needed.
Thanks,
Aurelien
esp0: !BSERV after data, probably to msgout
esp0: !BSERV after data, probably to msgout
esp0: Aborting command
esp0: dumping state
esp0: dma -- cond_reg<a4000211> addr<f077d000>
esp0: SW [sreg<00> sstep<04> ireg<18>]
esp0: HW reread [sreg<83> sstep<00> ireg<10>]
esp0: current command [tgt<00> lun<00> pphase<DATAOUT> cphase<DATAOUT>]
esp0: disconnected
esp0: Aborting command
esp0: dumping state
esp0: dma -- cond_reg<a4000210> addr<f077d000>
esp0: SW [sreg<00> sstep<04> ireg<18>]
esp0: HW reread [sreg<03> sstep<00> ireg<10>]
esp0: current command [tgt<00> lun<00> pphase<UNISSUED> cphase<UNISSUED>]
esp0: disconnected
esp0: Resetting scsi bus
esp0: SCSI bus reset interrupt
Unable to handle kernel NULL pointer dereference
tsk->{mm,active_mm}->context = 00000023
tsk->{mm,active_mm}->pgd = fc019400
\|/ ____ \|/
"@'/ ,. \`@"
/_| \__/ |_\
\__U_/
klogd(2895): Oops [#1]
PSR: 04400fc7 PC: fe61f618 NPC: fe61f61c Y: 00000000 Not tainted
PC: <esp_do_data_finale+0x36c/0x3b8 [esp]>
%G: 00000000 ffffffff 00000014 fd01a000 00000000 00000040 f1a82000 00000001
%O: fe620c00 00000000 00000000 00000000 00000000 fff00000 f1a83b38 fe61f300
RPC: <esp_do_data_finale+0x54/0x3b8 [esp]>
%L: f38f98a0 00000000 00000000 f01f7500 00000000 00000000 f390c000 0000000c
%I: f3904a84 000c0000 00000001 00000000 00000000 0eebb3c0 f1a83ba0 fe61ee28
Caller[fe61ee28]: esp_work_bus+0x5c/0x6c [esp]
Caller[fe61fd3c]: esp_intr+0x1d8/0x310 [esp]
Caller[f0013154]: handler_irq+0x8c/0xd4
Caller[f0010bd0]: patch_handler_irq+0x0/0x24
Caller[f0190eb4]: here+0x10/0x90
Caller[f002fc08]: do_syslog+0x110/0x3e8
Caller[f0069900]: vfs_read+0xa0/0x15c
Caller[f0069e28]: sys_read+0x30/0x64
Caller[f001162c]: syscall_is_too_hard+0x34/0x40
Caller[000119b0]: 0x119b0
Instruction DUMP: c2242118 8400a014 c4242114 <c200a010> c2242110 c200a00c c224210c c20e203a 82086007
Kernel panic - not syncing: Aiee, killing interrupt handler!
<0>Press Stop-A (L1-A) to return to the boot prom
--
.''`. Aurelien Jarno | GPG: 1024D/F1BCDB73
: :' : Debian developer | Electrical Engineer
`. `' aurel32@debian.org | aurelien@aurel32.net
`- people.debian.org/~aurel32 | www.aurel32.net
reply other threads:[~2006-09-24 12:45 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=20060924125239.GA3117@sparc.aurel32.net \
--to=aurelien@aurel32.net \
--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).