On Tuesday 03 February 2004 02:44 am, Ian Freislich wrote: > John Baldwin wrote: > > On Saturday 31 January 2004 09:29 am, Ian Freislich wrote: > > > John Baldwin wrote: > > > > On Thursday 29 January 2004 12:42 pm, Ian Freislich wrote: > > > > > Hi > > > > > > > > > > I've been getting this panic at boot time for last few weeks. The > > > > > last kernel that works is of around Wed Jan 7 15:23:38 SAST 2004. > > > > > > > > > > Random datapoints: > > > > > Gigabyte 686DLX motherboard with 2 PentiumII CPUs > > > > > I've noticed that ACPI has been working more and more poorly > > > > > with this motherboard. > > > > > I think this is related to ACPI brokenness because the working > > > > > kernel panics in exactly the same way if I set > > > > > hint.acpi.0.disabled="1". > > > > > > > > That means your working kernel doesn't work if ACPI is disabled > > > > which is what you are seeing here. Can you try kernels without > > > > SMP and see if ACPI and !ACPI both work? > > > > > > Yes, UP kernels work with and without ACPI. So ACPI is broken for > > > SMP (on this particular board)? > > > > No, you get the panic when you don't use ACPI when using SMP. See if > > your system has an MADT table via 'acpidump -t'. If it doesn't, see > > if there is a BIOS update for your BIOS. > > My machine is running the latest BIOS, well, the very latest image > from Gigabyte was a Beta version that required a univeral programmer > to recover the motherboard. I don't have access to a universal > programmer any more, so I'm a bit reluctant to try this image again. > > Is there anything else that can be done to fix this (appart from > downgrading to 4.9). If you use ACPI, disable device apic via 'hint.apic.0.disabled=1' -- John Baldwin <jhb_at_FreeBSD.org> <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.orgReceived on Tue Feb 03 2004 - 06:22:53 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:41 UTC