Re: fxp0: device timeout with 5.1BETA2
Hi, On Fri, Jun 13, 2003 at 10:37:26AM +0200, Markus Wennrich wrote: UPDATE: If I make an SMP-kernel this issue is completely solved for me. Everythings works as before, both fxp's share the same irq (together with uhci), both are working, with sio, usb, etc ... like as before the evil cvsup :-) Did you investigate it a little more? I updated -current today and fxp0 is at the moment unusable. But anyway I will try to build the kernel with SMP. -Kirill pgp0.pgp Description: PGP signature
Re: fxp0: device timeout with 5.1BETA2
UPDATE: If I make an SMP-kernel this issue is completely solved for me. Everythings works as before, both fxp's share the same irq (together with uhci), both are working, with sio, usb, etc ... like as before the evil cvsup :-) Markus On Wed, Jun 11, 2003 at 10:34:15AM +0200, Markus Wennrich wrote: On Tue, Jun 10, 2003 at 02:08:54PM +0200, Markus Wennrich wrote: fxp0: device timeout I get these as well. Is it on irq9 by any chance, along with acpi0 ? No. It's on irc 11 device 8 (as dmesg states). All irqs in bios are set to 11 (factory default). ACPI is disabled. Ok, well that's a useful data point (for me anyway) since it means there's a problem with fxp losing interrupts that's not related to some other ACPI problems I've experienced, suggesting that it's therefore a fxp driver problem. I have the same problem here with a freshly cvsupped 5.1-CURRENT. The machine has two fxp-NICs and I get device timeouts with both of them (with acpi enabled or disabled, both the same, no change). See attached dmesg. Well, I got a little further: Until yesterday, my fxp's both hat irq 10, shared with the uhci-usb-controller. Everything worked fine. Since the cvsup, fxp0 uses irq 3 (shared with sio0) and fxp1 irq 10 (shared with uhci0), which didn't work. If I remove sio from my kernel-config, fxp0 works fine. But if I use the fxp1-device (dhclient or ifconfig) the machine freezes immediatly. Then I tried to also remove the usb-support, so the fxp1 has irq 10 soley for itself ... doesn't work. The machine still freezes. (I tried to pinpoint both irq's to irq 3 via device.hints (hint.fxp.1.irq=3) ... didn't worked.) Well ... at least I can use fxp0 if it has its irq soley for itself. But the machine still freezes, if I try to use fxp1. Any ideas what else I could try? I volunteer for debugging ;-) Bye, Markus -- Unix IS user friendly ... it's just selective about who its friends are. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] -- Gibt es irgendwelche Regeln? - Ja. Wer zuerst stirbt, verliert. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: fxp0: device timeout with 5.1BETA2
On Tue, Jun 10, 2003 at 02:08:54PM +0200, Markus Wennrich wrote: fxp0: device timeout I get these as well. Is it on irq9 by any chance, along with acpi0 ? No. It's on irc 11 device 8 (as dmesg states). All irqs in bios are set to 11 (factory default). ACPI is disabled. Ok, well that's a useful data point (for me anyway) since it means there's a problem with fxp losing interrupts that's not related to some other ACPI problems I've experienced, suggesting that it's therefore a fxp driver problem. I have the same problem here with a freshly cvsupped 5.1-CURRENT. The machine has two fxp-NICs and I get device timeouts with both of them (with acpi enabled or disabled, both the same, no change). See attached dmesg. Well, I got a little further: Until yesterday, my fxp's both hat irq 10, shared with the uhci-usb-controller. Everything worked fine. Since the cvsup, fxp0 uses irq 3 (shared with sio0) and fxp1 irq 10 (shared with uhci0), which didn't work. If I remove sio from my kernel-config, fxp0 works fine. But if I use the fxp1-device (dhclient or ifconfig) the machine freezes immediatly. Then I tried to also remove the usb-support, so the fxp1 has irq 10 soley for itself ... doesn't work. The machine still freezes. (I tried to pinpoint both irq's to irq 3 via device.hints (hint.fxp.1.irq=3) ... didn't worked.) Well ... at least I can use fxp0 if it has its irq soley for itself. But the machine still freezes, if I try to use fxp1. Any ideas what else I could try? I volunteer for debugging ;-) Bye, Markus -- Unix IS user friendly ... it's just selective about who its friends are. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: fxp0: device timeout with 5.1BETA2
On Tue, Jun 03, 2003 at 12:02:20AM +0100, Paul Richards wrote: fxp0: device timeout I get these as well. Is it on irq9 by any chance, along with acpi0 ? No. It's on irc 11 device 8 (as dmesg states). All irqs in bios are set to 11 (factory default). ACPI is disabled. Ok, well that's a useful data point (for me anyway) since it means there's a problem with fxp losing interrupts that's not related to some other ACPI problems I've experienced, suggesting that it's therefore a fxp driver problem. I have the same problem here with a freshly cvsupped 5.1-CURRENT. The machine has two fxp-NICs and I get device timeouts with both of them (with acpi enabled or disabled, both the same, no change). See attached dmesg. Markus -- Why are they called buildings, when they're already finished? Shouldn't they be called builts? Copyright (c) 1992-2003 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.1-CURRENT #4: Tue Jun 10 12:55:22 CEST 2003 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/MYKERNEL Preloaded elf kernel /boot/kernel/kernel at 0xc04ae000. Timecounter i8254 frequency 1193182 Hz Timecounter TSC frequency 547179019 Hz CPU: Pentium III/Pentium III Xeon/Celeron (547.18-MHz 686-class CPU) Origin = GenuineIntel Id = 0x673 Stepping = 3 Features=0x387fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,PN,MMX,FXSR,SSE real memory = 1610612736 (1536 MB) avail memory = 1561681920 (1489 MB) Pentium Pro MTRR support enabled npx0: math processor on motherboard npx0: INT 16 interface pcibios: BIOS version 2.10 Using $PIR table, 12 entries at 0xc00fdf00 pcib0: Intel 82443GX host to PCI bridge at pcibus 0 on motherboard pci0: PCI bus on pcib0 pci_cfgintr: 0:12 INTA BIOS irq 11 pci_cfgintr: 0:12 INTA BIOS irq 11 pci_cfgintr: 0:14 INTA BIOS irq 10 pci_cfgintr: 0:18 INTD BIOS irq 10 agp0: Intel 82443GX host to PCI bridge mem 0xf800-0xfbff at device 0.0 on pci0 pcib1: PCI-PCI bridge at device 1.0 on pci0 pci1: PCI bus on pcib1 pcib2: PCI-PCI bridge at device 15.0 on pci1 pci2: PCI bus on pcib2 pcib3: PCI-PCI bridge at device 4.0 on pci2 pci3: PCI bus on pcib3 pci_cfgintr: 0:1 INTA routed to irq 3 pcib1: slot 15 INTB is routed to irq 3 pcib2: slot 4 INTB is routed to irq 3 pcib3: slot 5 INTA is routed to irq 3 fxp0: Intel 82557/8/9 EtherExpress Pro/100(B) Ethernet port 0x3000-0x303f mem 0xf420-0xf42f,0xf430-0xf4300fff irq 3 at device 5.0 on pci3 fxp0: Ethernet address 00:d0:b7:20:97:72 miibus0: MII bus on fxp0 inphy0: i82555 10/100 media interface on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto ahc0: Adaptec aic7896/97 Ultra2 SCSI adapter port 0x2000-0x20ff mem 0xf410-0xf4100fff irq 11 at device 12.0 on pci0 aic7896/97: Ultra2 Wide Channel A, SCSI Id=7, 32/253 SCBs ahc1: Adaptec aic7896/97 Ultra2 SCSI adapter port 0x2400-0x24ff mem 0xf4101000-0xf4101fff irq 11 at device 12.1 on pci0 aic7896/97: Ultra2 Wide Channel B, SCSI Id=7, 32/253 SCBs fxp1: Intel 82557/8/9 EtherExpress Pro/100(B) Ethernet port 0x2800-0x283f mem 0xf400-0xf40f,0xf4102000-0xf4102fff irq 10 at device 14.0 on pci0 fxp1: Ethernet address 00:90:27:6a:51:54 miibus1: MII bus on fxp1 inphy1: i82555 10/100 media interface on miibus1 inphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto isab0: PCI-ISA bridge at device 18.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel PIIX4 UDMA33 controller port 0x2860-0x286f at device 18.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: Intel 82371AB/EB (PIIX4) USB controller port 0x2840-0x285f irq 10 at device 18.2 on pci0 usb0: Intel 82371AB/EB (PIIX4) USB controller 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 pci0: bridge, PCI-unknown at device 18.3 (no driver attached) pci0: display, VGA at device 20.0 (no driver attached) orm0: Option ROMs at iomem 0xce000-0xcefff,0xcd800-0xcdfff,0xc8000-0xcd7ff,0xc-0xc7fff on isa0 pmtimer0 on isa0 atkbdc0: Keyboard controller (i8042) at port 0x64,0x60 on isa0 atkbd0: AT Keyboard flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: model IntelliMouse, device ID 3 fdc0: Enhanced floppy controller (i82077, NE72065 or clone) at port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: 1440-KB 3.5 drive on fdc0 drive 0 ppc0: Parallel port at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold ppbus0: Parallel port bus on ppc0 lpt0: Printer on ppbus0 lpt0: Interrupt-driven port ppi0: Parallel I/O on ppbus0 plip0: PLIP network interface on ppbus0 sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x300 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0:
fxp0: device timeout with 5.1BETA2
Hi I still get a fxp0: device timeout on my Thinkpad T30 with a newly installed 5.1BETA2. Browsing the archives showed that people had success with hint.fxp.0.prefer_iomap=1 on a T30 and 5.1BETA1. Any ideas why this doesn't help in my case? thx, t. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: fxp0: device timeout with 5.1BETA2
On Tue, 2003-06-03 at 22:00, Tobias Roth wrote: Hi I still get a fxp0: device timeout I get these as well. Is it on irq9 by any chance, along with acpi0 ? -- Tis a wise thing to know what is wanted, wiser still to know when it has been achieved and wisest of all to know when it is unachievable for then striving is folly. [Magician] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: fxp0: device timeout with 5.1BETA2
On Mon, Jun 02, 2003 at 10:59:22PM +0100, Paul Richards wrote: On Tue, 2003-06-03 at 22:00, Tobias Roth wrote: fxp0: device timeout I get these as well. Is it on irq9 by any chance, along with acpi0 ? No. It's on irc 11 device 8 (as dmesg states). All irqs in bios are set to 11 (factory default). ACPI is disabled. It's a fresh 5.1-BETA2 system with the following modifications: hint.apm.0.disabled=0 hint.acpi.0.disabled=1 hint.fxp.0.prefer_iomap=1 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: fxp0: device timeout with 5.1BETA2
On Tue, 2003-06-03 at 23:17, Tobias Roth wrote: On Mon, Jun 02, 2003 at 10:59:22PM +0100, Paul Richards wrote: On Tue, 2003-06-03 at 22:00, Tobias Roth wrote: fxp0: device timeout I get these as well. Is it on irq9 by any chance, along with acpi0 ? No. It's on irc 11 device 8 (as dmesg states). All irqs in bios are set to 11 (factory default). ACPI is disabled. Ok, well that's a useful data point (for me anyway) since it means there's a problem with fxp losing interrupts that's not related to some other ACPI problems I've experienced, suggesting that it's therefore a fxp driver problem. -- Tis a wise thing to know what is wanted, wiser still to know when it has been achieved and wisest of all to know when it is unachievable for then striving is folly. [Magician] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: fxp0: device timeout with 5.1BETA2
Date: Tue, 3 Jun 2003 23:00:21 +0200 From: Tobias Roth [EMAIL PROTECTED] Sender: [EMAIL PROTECTED] Hi I still get a fxp0: device timeout on my Thinkpad T30 with a newly installed 5.1BETA2. Browsing the archives showed that people had success with hint.fxp.0.prefer_iomap=1 on a T30 and 5.1BETA1. Any ideas why this doesn't help in my case? Odd. I have not seen this on my T30 running a CURRENT from May 29 (or almost Beta2). I do not have any hint like you suggest, either. My fxp0 has been working very well. R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]