port 0xe800-0xe81f irq 9 at
>> > device
>> > 9.0 on pci0
>> > panic: inthand_add: can't initialize ICU
>> >
>> > Attached please find verbose kernel bootup messages obtained from the last
>> > good kernel from about a week ago.
>> >
It seems John Baldwin wrote:
> > I found that I am no longer able to boot -current kernel on my machine. The
> > system panices right after initialising ed0 driver:
> >
> > [...]
> > ed0: port 0xe800-0xe81f irq 9 at device
> > 9.0 on pci0
> >
On 27-Sep-01 Maxim Sobolev wrote:
> Hi,
>
> I found that I am no longer able to boot -current kernel on my machine. The
> system panices right after initialising ed0 driver:
>
> [...]
> ed0: port 0xe800-0xe81f irq 9 at device
> 9.0 on pci0
> panic: inthan
On Thu, 27 Sep 2001, Maxim Sobolev wrote:
> I found that I am no longer able to boot -current kernel on my machine. The
> system panices right after initialising ed0 driver:
>
> [...]
> ed0: port 0xe800-0xe81f irq 9 at device 9.0 on
>pci0
> panic: inthand_add:
. The system panices right after initialising ed0 driver:
>
> [...]
> ed0: port 0xe800-0xe81f irq 9 at
> device 9.0 on pci0 panic: inthand_add: can't initialize ICU
>
> Attached please find verbose kernel bootup messages obtained from the
> last good kernel from about a
Hi,
I found that I am no longer able to boot -current kernel on my machine. The
system panices right after initialising ed0 driver:
[...]
ed0: port 0xe800-0xe81f irq 9 at device 9.0 on
pci0
panic: inthand_add: can't initialize ICU
Attached please find verbose kernel bootup messages obt