Date: Fri, 4 Feb 2005 16:24:10 -0500 From: John Baldwin <jhb@FreeBSD.org> To: Ian FREISLICH <if@hetzner.co.za> Cc: current@FreeBSD.org Subject: Re: sys/1386/i386/mptable.c rev 1.239 breaks boot. Message-ID: <200502041624.10668.jhb@FreeBSD.org> In-Reply-To: <E1CwzvC-00014A-00@hetzner.co.za> References: <E1CwzvC-00014A-00@hetzner.co.za>
next in thread | previous in thread | raw e-mail | index | archive | help
On Friday 04 February 2005 04:38 am, Ian FREISLICH wrote: > John Baldwin wrote: > > On Monday 31 January 2005 07:01 am, Ian FREISLICH wrote: > > > Hi > > > > > > I have a dual pII machine that doesn't boot with 1.239 of > > > sys/1386/i386/mptable.c. It boots with this patch backed out. > > > Does anyone have any ideas beyond backing out this patch? > > > > > > revision 1.239 > > > date: 2005/01/18 20:27:24; author: jhb; state: Exp; lines: +7 -1 > > > If a valid ELCR was found, consult it for the trigger mode of ISA > > > interrupts that have a trigger mode of conforming. This fixes problems > > > on some older machines that still route PCI devices via ISA interrupts > > > when using an I/O APIC. > > > > > > This seems to be a case of breaking, rather than fixing older > > > machines. It's highly reproduceable. I mailed the author of this > > > commit over a week ago, but have not had a response yet :(. This > > > is definitely a show-stopper, for me at least. > > > > It did fix other boxes. :( Can you provide a verbose dmesg? > > I've included both a working and broken kernel verbose boot. Ok, short answer is you have a busted MP Table as it is incomplete. You can try disabling USB as a hack for one to test if that fixes your problem. I would be interested in seeing your mptable output. > pcib0: unable to route slot 7 INTD > found-> vendor=0x8086, dev=0x7112, revid=0x01 > bus=0, slot=7, func=2 > class=0c-03-00, hdrtype=0x00, mfdev=0 > cmdreg=0x0005, statreg=0x0280, cachelnsz=0 (dwords) > lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) > intpin=d, irq=11 > map[90]: type 4, range 32, base 00005000, size 4, enabled This is your USB controller and is what has the problem FWIW. Note the message from pcib0 about being unable to route an interrupt. Let me know if just disabling USB is enough to fix the problem for now. If it is we can go from there. -- John Baldwin <jhb@FreeBSD.org> <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200502041624.10668.jhb>