From: "Blue Swirl" <blauwirbel@gmail.com>
To: qemu-devel@nongnu.org, andreas.faerber@web.de
Subject: Re: [Qemu-devel] Sparc32 network problems
Date: Wed, 6 Jun 2007 21:27:45 +0300 [thread overview]
Message-ID: <f43fc5580706061127l1625f6abi9f2cd6a54a5f3811@mail.gmail.com> (raw)
In-Reply-To: <5C0D359E-F154-4E86-8BCF-72EBF9A27EEA@web.de>
On 6/6/07, Andreas Färber <andreas.faerber@web.de> wrote:
>
> > Using Q 0.9.0d88 on a Mac OS X i386 host I was able to boot into
> > debian-40r0-sparc-netinst.iso with qemu-system-sparc, have the NIC
> > configured through DHCP and install to about 73% where I repeatedly
> > got a kernel panic "Aiee".
>
> I should add that when I tried the interrupt checking patch proposed
> on this list (http://lists.gnu.org/archive/html/qemu-devel/2007-03/
> msg00153.html) then instead of the kernel panic I got a qemu crash.
Would this happen to be the same bug as in this report:
http://marc.info/?l=qemu-devel&m=117768736212439&w=2
next prev parent reply other threads:[~2007-06-06 18:27 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-05 22:17 [Qemu-devel] Sparc32 network problems Andreas Färber
2007-06-06 7:42 ` Nigel Horne
2007-06-06 12:51 ` Andreas Färber
2007-06-06 18:27 ` Blue Swirl [this message]
2007-06-06 18:35 ` Aurelien Jarno
2007-06-06 18:52 ` Blue Swirl
2007-06-06 20:45 ` Andreas Färber
2007-06-07 11:47 ` Andreas Färber
2007-06-09 12:13 ` Andreas Färber
2007-06-10 15:49 ` Blue Swirl
2007-06-10 16:26 ` Andreas Färber
2007-06-10 16:44 ` Blue Swirl
2007-06-07 19:59 ` Blue Swirl
2007-06-07 21:04 ` Thiemo Seufer
2007-06-07 21:41 ` Andreas Färber
2007-06-08 16:25 ` Blue Swirl
2007-06-08 18:35 ` Thiemo Seufer
2007-06-08 19:04 ` Blue Swirl
2007-06-09 14:48 ` Thiemo Seufer
2007-06-08 20:44 ` Andreas Färber
2007-06-09 7:05 ` Blue Swirl
2007-06-09 8:05 ` Blue Swirl
2007-06-09 10:30 ` Andreas Färber
2007-06-10 15:40 ` Blue Swirl
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=f43fc5580706061127l1625f6abi9f2cd6a54a5f3811@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=andreas.faerber@web.de \
--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).