Subject: Re: amd64 reboot when using acpi
To: Brett Lymn <email@example.com>
From: Chavdar Ivanov <firstname.lastname@example.org>
Date: 06/20/2007 12:24:54
On 20/06/07, Chavdar Ivanov <email@example.com> wrote:
> On 20/06/07, Brett Lymn <firstname.lastname@example.org> wrote:
> > On Wed, Jun 20, 2007 at 11:30:55AM +0100, Chavdar Ivanov wrote:
> > >
> > > Disabling ehci fixes the problem; ACPI seems to work.
> > >
> > That actually makes sense - it seems to be IRQ 7 that is causing an
> > interrupt storm. I am thinking perhaps it has something to do with
> > the message about forcing the bios to give up possession of the
> > device. I did try checking for and ack'ing interrupts on the ehci
> > device when forcing it out of the BIOS's clutches but that didn't seem
> > to help any. The other thing I was going to try was tweaking the bios
> > to reserve IRQ 7 just to see of the problem persisted.
Reserving IRQ7 in the BIOS did not help.
In the mean time I got another panic - this time in OHCI while copying
large ~ 4GB - directory from an external USB disk, after copying some
panic: ohci_softintr: addr 0x868395d0 not found
db itself gives page fault trap, code=0; Faulted in DDB; continuing...
No dump could be taken.
> I'll try the latter.
> In the mean time, the diagnostic kernel panics as follows:
> root file system type: ffs
> init: copying out path '/sbin/init' 11
> kernel: double fault trap code=0
> Stopped in pid 1.1 (init) at netbsd:Xintr_legacy7+0x48: movq %r9, 0x28(%rsp)
> so you guess about interrupt 7 is probably right.
> If I disable acpi (but not ehci), it boots, but the nfe driver emits
> 'watchdog timeout' and there is no network.
> Hope that helps.
> > --
> > Brett Lymn