Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 4 Nov 2003 19:43:46 +0100
From:      Harald Schmalzbauer <h@schmalzbauer.de>
To:        John Baldwin <jhb@FreeBSD.org>
Cc:        Lukas Ertl <l.ertl@univie.ac.at>
Subject:   Re: new interrupt code: panic when going multiuser
Message-ID:  <200311041943.53890@harrymail>
In-Reply-To: <XFMail.20031104133801.jhb@FreeBSD.org>
References:  <XFMail.20031104133801.jhb@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help

--Boundary-02=_pN/p/0x01ieZI3k
Content-Type: text/plain;
  charset="iso-8859-15"
Content-Transfer-Encoding: quoted-printable
Content-Description: signed data
Content-Disposition: inline

On Tuesday 04 November 2003 19:38, John Baldwin wrote:
> On 04-Nov-2003 Harald Schmalzbauer wrote:
> > On Tuesday 04 November 2003 18:19, John Baldwin wrote:
> >> On 04-Nov-2003 Lukas Ertl wrote:
> >> > On Tue, 4 Nov 2003, John Baldwin wrote:
> >> >> On 04-Nov-2003 Lukas Ertl wrote:
> >> >> > On Tue, 4 Nov 2003, Lukas Ertl wrote:
> >> >> >> I somehow can't get at a good vmcore :-(.  But I found out that
> >> >> >> the machine boots fine in "Safe Mode", where DMA and hw.ata.wc is
> >> >> >> turned off.
> >> >> >
> >> >> > Ok, if I set hw.ata.ata_dma=3D0 in loader.conf, it boots fine.  C=
ould
> >> >> > there be some issue with ATAng + new interrupt code?
> >> >>
> >> >> Can you provide a dmesg please?  There may be a weird issue with
> >> >> some PPro's for example that I haven't been able to test.
> >> >
> >> > Sorry for the noise, I think I found the problem: I had to put
> >> > "options SMP" and "device apic" into the kernel, now everythings see=
ms
> >> > to run fine. I thought they were only needed for SMP kernels, that's
> >> > at least what the comment in GENERIC says...  If you still want the
> >> > dmesg, I can send it to you.
> >>
> >> Well, a kernel without SMP and just 'device apic' should work fine, and
> >> a kernel with both SMP and 'device apic' should also work fine.
> >
> > Hmm, I think this answer should be for "New <PNP0303> and aPic question=
"?
> >
> > Well I tired to build one (with -curr some weeks ago) with device apic
> > only which didn't work, I had to add options smp arrrgghhh. Had a look =
in
> > my file and saw I did the following:
> >#options         SMP
> >#options         APIC_IO
> >
> > Seems I didn't use "device apic" (perhaps I didn't recognize)
> >
> > But regardless, when I built a SMP kernel it didn't run on my UP machin=
e.
> >
> > Thanks a lot,
>
> I just committed a bunch of changes to the interrupt and SMP code.
> When you update to those changes, you should be able to build a UP
> kernel with 'device apic' and have it work, and you should be able
> to build an SMP kernel and have it run on your machine.

Oh, great! Thanks a lot and sorry for the former nonses-reply. I read your=
=20
first answer which was correct for my subject but I hadn't carefully read=20
this thread.
After jdk14 is finished I'll recvsup and build a new kernel. I already buil=
t=20
world today so I hope kernel only is okay.

Best regards,

=2DHarry

--Boundary-02=_pN/p/0x01ieZI3k
Content-Type: application/pgp-signature
Content-Description: signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (FreeBSD)

iD8DBQA/p/NpBylq0S4AzzwRAoNRAKCGfjdN+LK/wAoRxol8JGxLtYOHiQCfXeS+
sadW2X/zJMlggUDgO9gnitc=
=Z1tw
-----END PGP SIGNATURE-----

--Boundary-02=_pN/p/0x01ieZI3k--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200311041943.53890>