Re: panic: inthand_add: Can't initialize ICU

2001-09-27 Thread Mathias . Picker

I stumbled across this just now. I got the error after usb detection, so
I switched off everything usb in my bios, and amazingly it boots again.
Strange but true :)

On 27 Sep, 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: NE2000 PCI Ethernet (RealTek 8029) 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.
 
 Please fix.
 
 -Maxim

-- 
virtual earth
 Mathias Picker
 Geschäftsführer  Gesellschaft für Wissens re/prä sentation mbH

[EMAIL PROTECTED] 
Fon +49 89  / 540 7425-1
Fax +49 89  / 540 7425-9



To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: panic: inthand_add: Can't initialize ICU

2001-09-27 Thread Matthew N. Dodd

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: NE2000 PCI Ethernet (RealTek 8029) 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.

Revision 1.59 of sys/i386/isa/intr_machdep.c added the return to the
following block of code (in icu_setup()).

#if defined(APIC_IO)
if ((u_int)intr = ICU_LEN) /* no 8259 SLAVE to ignore */
#else
if ((u_int)intr = ICU_LEN || intr == ICU_SLAVEID)
#endif /* APIC_IO */
+return (EINVAL);
if (intr_handler[intr] != isa_strayintr)
return (EBUSY);

I'm not sure if the above change is correct but I'd be interested to see
if the problem goes away if you prevent IRQ 9 from being assigned.

-- 
| Matthew N. Dodd  | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD  |
| [EMAIL PROTECTED] |   2 x '84 Volvo 245DL| ix86,sparc,pmax |
| http://www.jurai.net/~winter |  For Great Justice!  | ISO8802.5 4ever |


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



RE: panic: inthand_add: Can't initialize ICU

2001-09-27 Thread John Baldwin


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: NE2000 PCI Ethernet (RealTek 8029) 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.
 
 Please fix.

Could you, say, add a printf to icu_set() to print out the passed in interrupt
number before it returns EINVAL?  Also, adding a call to debugger
(Debugger(foo);) and getting a stack trace would be very helpful.

 -Maxim

-- 

John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/
PGP Key: http://www.baldwin.cx/~john/pgpkey.asc
Power Users Use the Power to Serve!  -  http://www.FreeBSD.org/


Copyright (c) 1992-2001 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD 5.0-CURRENT #26: Wed Sep 19 10:04:40 EEST 2001
root@big_brother:/usr/src/sys/i386/compile/MBSD
Calibrating clock(s) ... TSC clock: 501070587 Hz, i8254 clock: 1193026 Hz
Timecounter i8254  frequency 1193026 Hz
Timecounter TSC  frequency 501070587 Hz
CPU: AMD-K6(tm) 3D processor (501.07-MHz 586-class CPU)
  Origin = AuthenticAMD  Id = 0x58c  Stepping = 12
  Features=0x8021bfFPU,VME,DE,PSE,TSC,MSR,MCE,CX8,PGE,MMX
  AMD Features=0x8800SYSCALL,3DNow!
Data TLB: 128 entries, 2-way associative
Instruction TLB: 64 entries, 1-way associative
L1 data cache: 32 kbytes, 32 bytes/line, 2 lines/tag, 2-way associative
L1 instruction cache: 32 kbytes, 32 bytes/line, 2 lines/tag, 2-way associative
Write Allocate Enable Limit: 384M bytes
Write Allocate 15-16M bytes: Enable
real memory  = 402587648 (393152K bytes)
Physical memory chunk(s):
0x1000 - 0x0009efff, 647168 bytes (158 pages)
0x00352000 - 0x17fe7fff, 399073280 bytes (97430 pages)
avail memory = 388304896 (379204K bytes)
bios32: Found BIOS32 Service Directory header at 0xc00fafd0
bios32: Entry = 0xfb450 (c00fb450)  Rev = 0  Len = 1
pcibios: PCI BIOS entry at 0xf+0xb480
pnpbios: Found PnP BIOS data at 0xc00fc0a0
pnpbios: Entry = f:c0c8  Rev = 1.0
Other BIOS signatures found:
Preloaded elf kernel /boot/kernel.old/kernel at 0xc032b000.
Preloaded elf module /boot/kernel.old/acpi.ko at 0xc032b0b8.
null: null device, zero device
mem: memory  I/O
K6-family MTRR support enabled (2 registers)
random: entropy source
pci_open(1):mode 1 addr port (0x0cf8) is 0x80003840
pci_open(1a):   mode1res=0x8000 (0x8000)
pci_cfgcheck:   device 0 [class=06] [hdr=00] is there (id=05971106)
Using $PIR table, 6 entries at 0xc00fddf0
npx0: math processor on motherboard
npx0: INT 16 interface
acpi0: AWARD  AWRDACPI on motherboard
acpi0: power button is handled as a fixed feature programming model.
Timecounter ACPI  frequency 3579545 Hz
can't fetch resources for \\_SB_.PCI0.ISA_.FDC0 - AE_AML_BUFFER_LIMIT
acpi_timer0: 24-bit timer at 3.579545MHz port 0x5008-0x500b on acpi0
acpi_cpu0: CPU on acpi0
acpi_button0: Power Button on acpi0
acpi_pcib0: Host-PCI bridge port 0x5080-0x50ff,0x5000-0x507f,0xcf8-0xcff on acpi0
pci0: physical bus=0
map[10]: type 3, range 32, base d800, size 26, enabled
found- vendor=0x1106, dev=0x0597, revid=0x04
bus=0, slot=0, func=0
class=06-00-00, hdrtype=0x00, mfdev=0
found- vendor=0x1106, dev=0x8598, revid=0x00
bus=0, slot=1, func=0
class=06-04-00, hdrtype=0x01, mfdev=0
found- vendor=0x1106, dev=0x0586, revid=0x41
bus=0, slot=7, func=0
class=06-01-00, hdrtype=0x00, mfdev=1
map[20]: type 4, range 32, base e000, size  4, enabled
found- vendor=0x1106, dev=0x0571, revid=0x06
bus=0, slot=7, func=1
class=01-01-8a, hdrtype=0x00, mfdev=0
map[20]: type 4, range 32, base e400, size  5, enabled
found- vendor=0x1106, dev=0x3038, revid=0x02
bus=0, slot=7, func=2
class=0c-03-00, hdrtype=0x00, mfdev=0
intpin=d, irq=9
found- vendor=0x1106, dev=0x3040, revid=0x10
bus=0, slot=7, func=3
class=06-00-00, hdrtype=0x00, mfdev=0
map[10]: type 4, range 32, base e800, size  5, enabled
found- vendor=0x10ec, dev=0x8029, revid=0x00
bus=0, slot=9, func=0
class=02-00-00, hdrtype=0x00, mfdev=0
intpin=a, irq=9
pci0: PCI bus on acpi_pcib0
pcib1: PCI-PCI bridge at device 1.0 on pci0
pcib1:   secondary bus 1
pcib1:   subordinate bus   1
pcib1:   I/O decode0xd000-0xdfff
pcib1:   memory decode 0xdc00-0xddff
pcib1:   prefetched decode 0xde00-0xdeff
pci1: physical bus=1
map[10]: type 3, range 32, base de00, size 24, enabled
map[14]: type 4, range 32, base d000, size  8, enabled
map[18]: type 1, range 32, base dd00, size 12, enabled
found- vendor=0x1002, dev=0x4742, revid=0x5c
bus=1, slot=0, func=0

Re: panic: inthand_add: Can't initialize ICU

2001-09-27 Thread Søren Schmidt

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: NE2000 PCI Ethernet (RealTek 8029) 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.
  
  Please fix.
 
 Could you, say, add a printf to icu_set() to print out the passed in interrupt
 number before it returns EINVAL?  Also, adding a call to debugger
 (Debugger(foo);) and getting a stack trace would be very helpful.


I see the same thing here on my latitude, the passed irq is 0xb, I dont 
have the stack trace written down (too damn long) but its when it attaches
the pcic controller..

-Søren

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: panic: inthand_add: Can't initialize ICU

2001-09-27 Thread John Baldwin


On 27-Sep-01 SXren Schmidt wrote:
 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: NE2000 PCI Ethernet (RealTek 8029) 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.
  
  Please fix.
 
 Could you, say, add a printf to icu_set() to print out the passed in
 interrupt
 number before it returns EINVAL?  Also, adding a call to debugger
 (Debugger(foo);) and getting a stack trace would be very helpful.
 
 
 I see the same thing here on my latitude, the passed irq is 0xb, I dont 
 have the stack trace written down (too damn long) but its when it attaches
 the pcic controller..

I've just committed a workaround.  It had to do with shared interrupts.

 -Søren

-- 

John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/
PGP Key: http://www.baldwin.cx/~john/pgpkey.asc
Power Users Use the Power to Serve!  -  http://www.FreeBSD.org/

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message