9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
* [9fans] Bogus shared IRQ on Dell D610
@ 2006-02-13  2:56 Lyndon Nerenberg
  2006-02-13  7:57 ` Lyndon Nerenberg
                   ` (2 more replies)
  0 siblings, 3 replies; 5+ messages in thread
From: Lyndon Nerenberg @ 2006-02-13  2:56 UTC (permalink / raw)
  To: Fans of the OS Plan 9 from Bell Labs

A bit more info on the 3C589 problems I'm having on my D610 laptop.   
During boot the kernel says:

...
ELCR: 0E80
#y0: 2 slot Intel 82365SL: port 0x3E0 IRQ 5
#y1: 2 slot Intel 82365SL: port 0x3E0 IRQ 5
8259enable: irq 5 shared but not level
intrenable: couldn't enable irq 5, tbdf 0xFFFFFFFF for i82365.1
#I0: xcvr10BaseT 3C589
I0: 3C589: 10 Mbps port 0x240 irq 10: 00104bdf06a8
...

The kernel is getting confused about #y1, which makes sense, because  
there is no #y1.  This laptop only has a single card slot.  The 589  
card is visible, and both /net/ether0/stats and ifstats are reporting  
traffic in both directions (provoked by trying the DHCP dance with ip/ 
ipconfig), it just seems as though the received data isn't being  
handed up to the user mode process.

I'm puzzled whether this is because of the irq 5 confusion. The card  
claims it's interrupting on irq 10, and the driver claims to be  
receiving (good) frames.  Should irq 5 even matter after the kernel  
finds the device and (apparently successfully) maps it's memory and  
sets up the interrupt routing?

--lyndon


^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [9fans] Bogus shared IRQ on Dell D610
  2006-02-13  2:56 [9fans] Bogus shared IRQ on Dell D610 Lyndon Nerenberg
@ 2006-02-13  7:57 ` Lyndon Nerenberg
  2006-02-13  8:14 ` Lyndon Nerenberg
  2006-02-13 17:40 ` Dave Eckhardt
  2 siblings, 0 replies; 5+ messages in thread
From: Lyndon Nerenberg @ 2006-02-13  7:57 UTC (permalink / raw)
  To: Fans of the OS Plan 9 from Bell Labs

[-- Attachment #1: Type: text/plain, Size: 267 bytes --]


> #y0: 2 slot Intel 82365SL: port 0x3E0 IRQ 5
> #y1: 2 slot Intel 82365SL: port 0x3E0 IRQ 5
> 8259enable: irq 5 shared but not level

FWIW, here's what FreeBSD has to say about the hardware.  It fires up  
on the wire fine, so the HW and cabling is okay.



[-- Attachment #2: dmesg-ep0.txt --]
[-- Type: text/plain, Size: 6168 bytes --]

Copyright (c) 1992-2005 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 6.0-STABLE #1: Fri Feb  3 17:27:42 PST 2006
    lnerenberg@gollum.gmi-mr.com:/usr/src/sys/i386/compile/GOLLUM
ACPI APIC Table: <DELL   CPi R  >
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: Intel(R) Pentium(R) M processor 1.73GHz (1728.97-MHz 686-class CPU)
  Origin = "GenuineIntel"  Id = 0x6d8  Stepping = 8
  Features=0xafe9fbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,TM,PBE>
  Features2=0x180<EST,TM2>
  AMD Features=0x100000<NX>
real memory  = 536678400 (511 MB)
avail memory = 515817472 (491 MB)
ioapic0: Changing APIC ID to 1
ioapic0 <Version 2.0> irqs 0-23 on motherboard
netsmb_dev: loaded
ath_hal: 0.9.14.9 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413)
npx0: [FAST]
npx0: <math processor> on motherboard
npx0: INT 16 interface
acpi0: <DELL CPi R  > on motherboard
Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0
cpu0: <ACPI CPU> on acpi0
acpi_throttle0: <ACPI CPU Throttling> on cpu0
acpi_acad0: <AC Adapter> on acpi0
battery0: <ACPI Control Method Battery> on acpi0
battery1: <ACPI Control Method Battery> on acpi0
acpi_lid0: <Control Method Lid Switch> on acpi0
acpi_button0: <Power Button> on acpi0
acpi_button1: <Sleep Button> on acpi0
pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
pci0: <ACPI PCI bus> on pcib0
pcib1: <ACPI PCI-PCI bridge> at device 1.0 on pci0
pci1: <ACPI PCI bus> on pcib1
pci1: <display, VGA> at device 0.0 (no driver attached)
pcib2: <ACPI PCI-PCI bridge> at device 28.0 on pci0
pci2: <ACPI PCI bus> on pcib2
bge0: <Broadcom BCM5751 Gigabit Ethernet, ASIC rev. 0x4001> mem 0xdfcf0000-0xdfcfffff irq 16 at device 0.0 on pci2
miibus0: <MII bus> on bge0
brgphy0: <BCM5750 10/100/1000baseTX PHY> on miibus0
brgphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto
bge0: Ethernet address: 00:12:3f:f3:4d:8e
uhci0: <Intel 82801FB/FR/FW/FRW (ICH6) USB controller USB-A> port 0xbf80-0xbf9f irq 16 at device 29.0 on pci0
uhci0: [GIANT-LOCKED]
usb0: <Intel 82801FB/FR/FW/FRW (ICH6) USB controller USB-A> on uhci0
usb0: USB revision 1.0
uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
uhci1: <Intel 82801FB/FR/FW/FRW (ICH6) USB controller USB-B> port 0xbf60-0xbf7f irq 17 at device 29.1 on pci0
uhci1: [GIANT-LOCKED]
usb1: <Intel 82801FB/FR/FW/FRW (ICH6) USB controller USB-B> on uhci1
usb1: USB revision 1.0
uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub1: 2 ports with 2 removable, self powered
uhci2: <Intel 82801FB/FR/FW/FRW (ICH6) USB controller USB-C> port 0xbf40-0xbf5f irq 18 at device 29.2 on pci0
uhci2: [GIANT-LOCKED]
usb2: <Intel 82801FB/FR/FW/FRW (ICH6) USB controller USB-C> on uhci2
usb2: USB revision 1.0
uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub2: 2 ports with 2 removable, self powered
uhci3: <Intel 82801FB/FR/FW/FRW (ICH6) USB controller USB-D> port 0xbf20-0xbf3f irq 19 at device 29.3 on pci0
uhci3: [GIANT-LOCKED]
usb3: <Intel 82801FB/FR/FW/FRW (ICH6) USB controller USB-D> on uhci3
usb3: USB revision 1.0
uhub3: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub3: 2 ports with 2 removable, self powered
ehci0: <Intel 82801FB (ICH6) USB 2.0 controller> mem 0xffa80800-0xffa80bff irq 16 at device 29.7 on pci0
ehci0: [GIANT-LOCKED]
usb4: EHCI version 1.0
usb4: companion controllers, 2 ports each: usb0 usb1 usb2 usb3
usb4: <Intel 82801FB (ICH6) USB 2.0 controller> on ehci0
usb4: USB revision 2.0
uhub4: Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1
uhub4: 8 ports with 8 removable, self powered
pcib3: <ACPI PCI-PCI bridge> at device 30.0 on pci0
pci3: <ACPI PCI bus> on pcib3
cbb0: <PCI-CardBus Bridge> at device 1.0 on pci3
cardbus0: <CardBus bus> on cbb0
pccard0: <16-bit PCCard bus> on cbb0
pci3: <simple comms> at device 1.5 (no driver attached)
pci3: <network> at device 3.0 (no driver attached)
pcm0: <Intel ICH6 (82801FB)> port 0xed00-0xedff,0xec40-0xec7f mem 0xdffffe00-0xdfffffff,0xdffffd00-0xdffffdff irq 16 at device 30.2 on pci0
pcm0: <SigmaTel STAC9750/51 AC97 Codec>
pci0: <simple comms, generic modem> at device 30.3 (no driver attached)
isab0: <PCI-ISA bridge> at device 31.0 on pci0
isa0: <ISA bus> on isab0
atapci0: <Intel ICH6 SATA150 controller> port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xbfa0-0xbfaf irq 17 at device 31.2 on pci0
atapci0: failed to enable memory mapping!
ata0: <ATA channel 0> on atapci0
ata1: <ATA channel 1> on atapci0
pci0: <serial bus, SMBus> at device 31.3 (no driver attached)
acpi_tz0: <Thermal Zone> on acpi0
atkbdc0: <Keyboard controller (i8042)> port 0x60,0x64,0x62,0x66 irq 1 on acpi0
atkbd0: <AT Keyboard> irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
psm0: <PS/2 Mouse> irq 12 on atkbdc0
psm0: [GIANT-LOCKED]
psm0: model GlidePoint, device ID 0
sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
sio0: type 16550A
sio1 port 0x2f8-0x2ff,0x280-0x287 irq 3 drq 3 on acpi0
sio1: type 16550A
pmtimer0 on isa0
orm0: <ISA Option ROM> at iomem 0xc0000-0xcffff on isa0
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
Timecounter "TSC" frequency 1728972416 Hz quality 800
Timecounters tick every 1.000 msec
pccard0: <unknown card> (manufacturer=0x0101, product=0x0589, function_type=6) at function 0
pccard0:    CIS info: 3Com Corporation, 3C589D, TP/BNC LAN Card Ver. 2a, 000002
ad0: 38154MB <Hitachi HTS541040G9AT00 MB2OA61A> at ata0-master UDMA100
acd0: CDRW <TSSTcorpCD-RW/DVD-ROM TSL462C/DE01> at ata1-master UDMA33
Trying to mount root from ufs:/dev/ad0s1a
ep0: <3Com Corporation 3C589D> at port 0x100-0x10f irq 19 function 0 config 1 on pccard0
ep0: Ethernet address: 00:10:4b:df:06:a8

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [9fans] Bogus shared IRQ on Dell D610
  2006-02-13  2:56 [9fans] Bogus shared IRQ on Dell D610 Lyndon Nerenberg
  2006-02-13  7:57 ` Lyndon Nerenberg
@ 2006-02-13  8:14 ` Lyndon Nerenberg
  2006-02-13 17:40 ` Dave Eckhardt
  2 siblings, 0 replies; 5+ messages in thread
From: Lyndon Nerenberg @ 2006-02-13  8:14 UTC (permalink / raw)
  To: Fans of the OS Plan 9 from Bell Labs


On Feb 12, 2006, at 6:56 PM, Lyndon Nerenberg wrote:

> The 589 card is visible, and both /net/ether0/stats and ifstats are  
> reporting traffic in both directions (provoked by trying the DHCP  
> dance with ip/ipconfig), it just seems as though the received data  
> isn't being handed up to the user mode process.

I have also confirmed the 589 is sending packets.  Sniffing on  
another box I can see the DHCP requests being sent, as well as the  
responses from the DHCP server. /net/log doesn't have anything to say  
with ip debugging turned on.

--lyndon


^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [9fans] Bogus shared IRQ on Dell D610
  2006-02-13  2:56 [9fans] Bogus shared IRQ on Dell D610 Lyndon Nerenberg
  2006-02-13  7:57 ` Lyndon Nerenberg
  2006-02-13  8:14 ` Lyndon Nerenberg
@ 2006-02-13 17:40 ` Dave Eckhardt
  2006-02-13 18:47   ` Lyndon Nerenberg
  2 siblings, 1 reply; 5+ messages in thread
From: Dave Eckhardt @ 2006-02-13 17:40 UTC (permalink / raw)
  To: Fans of the OS Plan 9 from Bell Labs

> The kernel is getting confused about #y1, which makes sense,
> because there is no #y1.

I think there's some plan9.ini foo which says "no matter how
many PCI devices this machine claims to have, it has only N",
which if you're lucky might clip out the second #y.

Dave Eckhardt


^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [9fans] Bogus shared IRQ on Dell D610
  2006-02-13 17:40 ` Dave Eckhardt
@ 2006-02-13 18:47   ` Lyndon Nerenberg
  0 siblings, 0 replies; 5+ messages in thread
From: Lyndon Nerenberg @ 2006-02-13 18:47 UTC (permalink / raw)
  To: Fans of the OS Plan 9 from Bell Labs

> I think there's some plan9.ini foo which says "no matter how
> many PCI devices this machine claims to have, it has only N",
> which if you're lucky might clip out the second #y.

The only thing I could find in the driver was "pcmcia0=disabled" (I 
forget the exact value) that disables all PCMCIA configuration attempts. 
  There's nothing to override the number of card slots.

I'm not sure changing the PCI probe limits is going to help here.  I 
think for now I'm going to start adding prints to the 589 driver to see 
exactly where the push of the received data up to userland is falling 
over.  I still don't know if this is related to the IRQ5 confusion or 
what.  I also need to examine the FreeBSD driver for the cardbus bridge 
to see if they're doing anything special.


--lyndon


^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2006-02-13 18:47 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2006-02-13  2:56 [9fans] Bogus shared IRQ on Dell D610 Lyndon Nerenberg
2006-02-13  7:57 ` Lyndon Nerenberg
2006-02-13  8:14 ` Lyndon Nerenberg
2006-02-13 17:40 ` Dave Eckhardt
2006-02-13 18:47   ` Lyndon Nerenberg

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).