From: Fabrice Bellard <fabrice@bellard.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] FreeBSD status
Date: Wed, 26 May 2004 00:34:36 +0200 [thread overview]
Message-ID: <40B3C9FC.2010105@bellard.org> (raw)
In-Reply-To: <20040524232328.A69576@saturn.kn-bremen.de>
Juergen Lock wrote:
> As mentioned on irc I was having some success with FreeBSD:
>
> 4.10RC3 install cd: boots, but kernel doesnt see any disks
> (error message when trying to partition, -hda with empty image)
>
> 5.2.1 install cd and boot.flp: boot now with the fixes in cvs,
> but panic when trying to write to disk (same empty image).
> to repeat: at the mountroot prompt type:
> ufs:md0
> then in sysinstall select custom install, partition, `c',
> enter slice (partition) size, hit `w' to write immediately,
> confirm, select mbr -> panic writing to disk
I found the problem : it seems that FreeBSD expects the IDE READY status
bit just after the IDE WRITE command. It is weird as it is not
mentionned in the IDE specs. I would like to be sure it is a standard
IDE behaviour.
> I also get: npx0: WARNING: no FPU! from the kernel (kernel
> messages can be viewed with scroll-lock and then page-up/down,
> cursur-up/down), Fabrice says that the FPU error comes from the fact
> that FreeBSD uses FPU interrupts to test the FPU exception reporting.
I made a fix (not commited yet).
> Fabrice also said the FreeBSD host patches are not in yet,
> is that just lack of time or do they have some problems?
Still no time.
> Also, would it help if i try to make a debug version of the 5.2.1
> GENERIC kernel to see where the panic is? It is always trying to
> read from 0x2c, supervisor read, page not present. (I guess a NULL
> pointer to a struct, unfortunately i won't be able to take crashdumps
> and get a full backtrace as that requires writing to disk...)
Fabrice.
next prev parent reply other threads:[~2004-05-25 23:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-24 21:23 [Qemu-devel] FreeBSD status Juergen Lock
2004-05-25 22:34 ` Fabrice Bellard [this message]
2004-05-27 22:17 ` Juergen Lock
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=40B3C9FC.2010105@bellard.org \
--to=fabrice@bellard.org \
--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 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.