Morning ...

        I'm having a bugger of a time getting anywhere with the KTR stuff,
for, as soon as I enable it, the system slows down so badly that I can't
get into X to hang it ...

        Figure that I'd try killing off *everything* not required (named,
ethernet interfaces, etc), so that there was less happening, I started up
X ... wouldn't hang.

        Rebooted the machine, so that everything was running 'as per
normal', and started X ... dead in no time.

        Looking at the IRQs that my machine is running with, according to
dmesg, I notice a few 'overlaps', and wonder if that could be the cause?

> dmesg | grep irq
IOAPIC #0 intpin 2 -> irq 0
IOAPIC #0 intpin 19 -> irq 2
IOAPIC #0 intpin 18 -> irq 10
IOAPIC #0 intpin 17 -> irq 11
IOAPIC #0 intpin 16 -> irq 12
ata0: at 0x1f0 irq 14 on atapci0
ahc0: <Adaptec 2940 Ultra SCSI adapter> port 0xcc00-0xccff mem 0xf0200000-0xf0200fff 
irq 11 at device 13.0 on pci0
pcm0: <AudioPCI ES1370> port 0xd000-0xd03f irq 2 at device 17.0 on pci0
atapci1: <HighPoint HPT366 ATA66 controller> port 
0xdc00-0xdcff,0xd800-0xd803,0xd400-0xd407 irq 10 at device 19.0 on pci0
atapci2: <HighPoint HPT366 ATA66 controller> port 
0xe800-0xe8ff,0xe400-0xe403,0xe000-0xe007 irq 10 at device 19.1 on pci0
atkbd0: <AT Keyboard> flags 0x1 irq 1 on atkbdc0
sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
sio1 at port 0x2f8-0x2ff irq 3 on isa0
fxp0: <Intel Pro 10/100B/100+ Ethernet> port 0xc400-0xc43f mem 
0xf0100000-0xf01fffff,0xf0201000-0xf0201fff irq 2 at device 9.0 on pci0
fxp1: <Intel Pro 10/100B/100+ Ethernet> port 0xc800-0xc83f mem 
0xf0000000-0xf00fffff,0xf0202000-0xf0202fff irq 10 at device 11.0 on pci0

        My sound card overlaps with fxp0, and fxp1 overlaps with the
HighPoint controller ...

        Grasping at straws here ...

Marc G. Fournier                   ICQ#7615664               IRC Nick: Scrappy
Systems Administrator @
primary: [EMAIL PROTECTED]           secondary: scrappy@{freebsd|postgresql}.org

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

Reply via email to