Re: 3com 3c59x stopped working with 2.6.13-rc[56]
Hello > I assume it worked OK in 2.6.12. Yes, sorry, forgot to mention that. >> 18:27:47: eth1: Setting full-duplex based on MII #24 link partner capability >> of 05e1. >> 18:32:02: NETDEV WATCHDOG: eth1: transmit timed out >> 18:32:02: eth1: transmit timed out, tx_status 00 status e601. >> 18:32:02: diagnostics: net 0cfa media 8880 dma 003a fifo 8800 >> 18:32:02: eth1: Interrupt posted but not delivered -- IRQ blocked by another >> device? > gargh, I have acpi feelings. Could you please It seems you had a good hunch. > a) Compare /proc/interrupts for 2.6.12 and 2.6.13-rc6 /proc/interrputs for 2.6.12: CPU0 0: 76133896 XT-PIC timer 1: 1170 XT-PIC i8042 2: 0 XT-PIC cascade 9: 0 XT-PIC acpi 11:2483056 XT-PIC eth1 14: 603767 XT-PIC ide0 15: 13 XT-PIC ide1 NMI: 0 ERR: 0 /proc/interrputs for 2.6.13: CPU0 0: 851172 XT-PIC timer 1:802 XT-PIC i8042 2: 0 XT-PIC cascade 5: 0 XT-PIC eth1 14: 30180 XT-PIC ide0 15: 13 XT-PIC ide1 NMI: 0 ERR: 0 What is missing is acpi on irq9 > b) Generate the boot-time dmesg output for 2.6.12 and 2.6.13-rc6 >(dmesg -s 100 > foo), then do > diff -u dmesg-2.6.12 dmesg-2.6.13-rc6 > foo >and send foo? Here is foo: --- dmesg-2.6.122005-08-23 12:53:43.0 +0200 +++ dmesg-2.6.132005-08-23 14:26:54.0 +0200 @@ -1,4 +1,4 @@ -Linux version 2.6.12 ([EMAIL PROTECTED]) (gcc version 4.0.1 (Debian 4.0.1-2)) #1 Mon Aug 22 14:49:40 CEST 2005 +Linux version 2.6.13-rc6-git13 ([EMAIL PROTECTED]) (gcc version 4.0.1 (Debian 4.0.1-2)) #2 Mon Aug 22 15:22:10 CEST 2005 BIOS-provided physical RAM map: BIOS-e820: - 000a (usable) BIOS-e820: 000f - 0010 (reserved) @@ -13,25 +13,20 @@ Normal zone: 126956 pages, LIFO batch:31 HighMem zone: 0 pages, LIFO batch:1 DMI 2.3 present. -ACPI: RSDP (v000 ASUS ) @ 0x000f6c20 -ACPI: RSDT (v001 ASUS A7V266-C 0x30303031 MSFT 0x31313031) @ 0x1ffec000 -ACPI: FADT (v001 ASUS A7V266-C 0x30303031 MSFT 0x31313031) @ 0x1ffec080 -ACPI: BOOT (v001 ASUS A7V266-C 0x30303031 MSFT 0x31313031) @ 0x1ffec040 -ACPI: DSDT (v001 ASUS A7V266-C 0x1000 MSFT 0x010b) @ 0x Allocating PCI resources starting at 2000 (gap: 2000:dfff) Built 1 zonelists -Kernel command line: BOOT_IMAGE=Linux.old ro root=301 lapic pci=usepirqmask +Kernel command line: auto BOOT_IMAGE=Linux ro root=301 lapic pci=usepirqmask Initializing CPU#0 -CPU 0 irqstacks, hard=c0442000 soft=c0441000 +CPU 0 irqstacks, hard=c041b000 soft=c041a000 PID hash table entries: 2048 (order: 11, 32768 bytes) Detected 1210.984 MHz processor. Using tsc for high-res timesource Console: colour VGA+ 80x25 Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) -Memory: 515260k/524208k available (2114k kernel code, 8412k reserved, 801k data, 392k init, 0k highmem) +Memory: 515424k/524208k available (2010k kernel code, 8252k reserved, 753k data, 388k init, 0k highmem) Checking if this processor honours the WP bit even in supervisor mode... Ok. -Calibrating delay loop... 2383.87 BogoMIPS (lpj=1191936) +Calibrating delay using timer specific routine.. 2424.59 BogoMIPS (lpj=1212295) Mount-cache hash table entries: 512 CPU: After generic identify, caps: 0383f9ff c1cbf9ff CPU: After vendor identify, caps: 0383f9ff c1cbf9ff @@ -40,65 +35,49 @@ CPU: After all inits, caps: 0383f9ff c1cbf9ff 0020 Intel machine check architecture supported. Intel machine check reporting enabled on CPU#0. +mtrr: v2.0 (20020519) CPU: AMD Duron(TM)Processor stepping 01 Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Checking 'hlt' instruction... OK. -ACPI: setting ELCR to 0200 (from 0400) NET: Registered protocol family 16 PCI: PCI BIOS revision 2.10 entry at 0xf0f00, last bus=1 PCI: Using configuration type 1 -mtrr: v2.0 (20020519) -ACPI: Subsystem revision 20050309 -ACPI: Interpreter enabled -ACPI: Using PIC for interrupt routing -ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled. -ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled. -ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled. -ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 9 *10 11 12 14 15) -ACPI: PCI Root Bridge [PCI0] (:00) +PCI: Probing PCI hardware PCI: Probing PCI hardware (bus 00) Boot video device is :01:00.0 -ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
Re: 3com 3c59x stopped working with 2.6.13-rc[56]
Hello I assume it worked OK in 2.6.12. Yes, sorry, forgot to mention that. 18:27:47: eth1: Setting full-duplex based on MII #24 link partner capability of 05e1. 18:32:02: NETDEV WATCHDOG: eth1: transmit timed out 18:32:02: eth1: transmit timed out, tx_status 00 status e601. 18:32:02: diagnostics: net 0cfa media 8880 dma 003a fifo 8800 18:32:02: eth1: Interrupt posted but not delivered -- IRQ blocked by another device? gargh, I have acpi feelings. Could you please It seems you had a good hunch. a) Compare /proc/interrupts for 2.6.12 and 2.6.13-rc6 /proc/interrputs for 2.6.12: CPU0 0: 76133896 XT-PIC timer 1: 1170 XT-PIC i8042 2: 0 XT-PIC cascade 9: 0 XT-PIC acpi 11:2483056 XT-PIC eth1 14: 603767 XT-PIC ide0 15: 13 XT-PIC ide1 NMI: 0 ERR: 0 /proc/interrputs for 2.6.13: CPU0 0: 851172 XT-PIC timer 1:802 XT-PIC i8042 2: 0 XT-PIC cascade 5: 0 XT-PIC eth1 14: 30180 XT-PIC ide0 15: 13 XT-PIC ide1 NMI: 0 ERR: 0 What is missing is acpi on irq9 b) Generate the boot-time dmesg output for 2.6.12 and 2.6.13-rc6 (dmesg -s 100 foo), then do diff -u dmesg-2.6.12 dmesg-2.6.13-rc6 foo and send foo? Here is foo: --- dmesg-2.6.122005-08-23 12:53:43.0 +0200 +++ dmesg-2.6.132005-08-23 14:26:54.0 +0200 @@ -1,4 +1,4 @@ -Linux version 2.6.12 ([EMAIL PROTECTED]) (gcc version 4.0.1 (Debian 4.0.1-2)) #1 Mon Aug 22 14:49:40 CEST 2005 +Linux version 2.6.13-rc6-git13 ([EMAIL PROTECTED]) (gcc version 4.0.1 (Debian 4.0.1-2)) #2 Mon Aug 22 15:22:10 CEST 2005 BIOS-provided physical RAM map: BIOS-e820: - 000a (usable) BIOS-e820: 000f - 0010 (reserved) @@ -13,25 +13,20 @@ Normal zone: 126956 pages, LIFO batch:31 HighMem zone: 0 pages, LIFO batch:1 DMI 2.3 present. -ACPI: RSDP (v000 ASUS ) @ 0x000f6c20 -ACPI: RSDT (v001 ASUS A7V266-C 0x30303031 MSFT 0x31313031) @ 0x1ffec000 -ACPI: FADT (v001 ASUS A7V266-C 0x30303031 MSFT 0x31313031) @ 0x1ffec080 -ACPI: BOOT (v001 ASUS A7V266-C 0x30303031 MSFT 0x31313031) @ 0x1ffec040 -ACPI: DSDT (v001 ASUS A7V266-C 0x1000 MSFT 0x010b) @ 0x Allocating PCI resources starting at 2000 (gap: 2000:dfff) Built 1 zonelists -Kernel command line: BOOT_IMAGE=Linux.old ro root=301 lapic pci=usepirqmask +Kernel command line: auto BOOT_IMAGE=Linux ro root=301 lapic pci=usepirqmask Initializing CPU#0 -CPU 0 irqstacks, hard=c0442000 soft=c0441000 +CPU 0 irqstacks, hard=c041b000 soft=c041a000 PID hash table entries: 2048 (order: 11, 32768 bytes) Detected 1210.984 MHz processor. Using tsc for high-res timesource Console: colour VGA+ 80x25 Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) -Memory: 515260k/524208k available (2114k kernel code, 8412k reserved, 801k data, 392k init, 0k highmem) +Memory: 515424k/524208k available (2010k kernel code, 8252k reserved, 753k data, 388k init, 0k highmem) Checking if this processor honours the WP bit even in supervisor mode... Ok. -Calibrating delay loop... 2383.87 BogoMIPS (lpj=1191936) +Calibrating delay using timer specific routine.. 2424.59 BogoMIPS (lpj=1212295) Mount-cache hash table entries: 512 CPU: After generic identify, caps: 0383f9ff c1cbf9ff CPU: After vendor identify, caps: 0383f9ff c1cbf9ff @@ -40,65 +35,49 @@ CPU: After all inits, caps: 0383f9ff c1cbf9ff 0020 Intel machine check architecture supported. Intel machine check reporting enabled on CPU#0. +mtrr: v2.0 (20020519) CPU: AMD Duron(TM)Processor stepping 01 Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Checking 'hlt' instruction... OK. -ACPI: setting ELCR to 0200 (from 0400) NET: Registered protocol family 16 PCI: PCI BIOS revision 2.10 entry at 0xf0f00, last bus=1 PCI: Using configuration type 1 -mtrr: v2.0 (20020519) -ACPI: Subsystem revision 20050309 -ACPI: Interpreter enabled -ACPI: Using PIC for interrupt routing -ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled. -ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled. -ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled. -ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 9 *10 11 12 14 15) -ACPI: PCI Root Bridge [PCI0] (:00) +PCI: Probing PCI hardware PCI: Probing PCI hardware (bus 00) Boot video device is :01:00.0 -ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT] -ACPI: PCI Interrupt
Re: 3com 3c59x stopped working with 2.6.13-rc[56]
> i tried to boot 2.6.13-rc5-git4 and 2.6.13-rc6-git13 both with the same > result: my 3com (3c59x driver on 3com 905c) card not working. > Here is what I saw in the logs. > Notice the regularity of the log barfs. They continue the same every 10secs. I'm currently using 2.6.13-rc6-git13 with the 3c95x driver compiled as a module, without any issues. I've tested all of the 2.6.13-* kernels. One noticeable difference, I've been using gcc-3.4.4 and not gcc-4.0.1. Steve - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 3com 3c59x stopped working with 2.6.13-rc[56]
[EMAIL PROTECTED] wrote: > > i tried to boot 2.6.13-rc5-git4 and 2.6.13-rc6-git13 both with the same > result: my 3com (3c59x driver on 3com 905c) card not working. > Here is what I saw in the logs. > Notice the regularity of the log barfs. They continue the same every 10secs. > > The upgrade was committed using: > cd /usr/src/linux > patch -p1 < ../patch-2.6.13-rc5 > patch -p1 < ../patch-2.6.13-rc5-git4 > make oldconfig > make bzImage modules modules_install install > > gcc-4.0.1 from Debian testing. > I assume it worked OK in 2.6.12. There are no changes in the driver which would explain this. > > 18:27:47: eth1: Setting full-duplex based on MII #24 link partner capability > of 05e1. > 18:32:02: NETDEV WATCHDOG: eth1: transmit timed out > 18:32:02: eth1: transmit timed out, tx_status 00 status e601. > 18:32:02: diagnostics: net 0cfa media 8880 dma 003a fifo 8800 > 18:32:02: eth1: Interrupt posted but not delivered -- IRQ blocked by another > device? gargh, I have acpi feelings. Could you please a) Compare /proc/interrupts for 2.6.12 and 2.6.13-rc6 b) Generate the boot-time dmesg output for 2.6.12 and 2.6.13-rc6 (dmesg -s 100 > foo), then do diff -u dmesg-2.6.12 dmesg-2.6.13-rc6 > foo and send foo? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
3com 3c59x stopped working with 2.6.13-rc[56]
Hello, i tried to boot 2.6.13-rc5-git4 and 2.6.13-rc6-git13 both with the same result: my 3com (3c59x driver on 3com 905c) card not working. Here is what I saw in the logs. Notice the regularity of the log barfs. They continue the same every 10secs. The upgrade was committed using: cd /usr/src/linux patch -p1 < ../patch-2.6.13-rc5 patch -p1 < ../patch-2.6.13-rc5-git4 make oldconfig make bzImage modules modules_install install gcc-4.0.1 from Debian testing. Any ideas? Regards, Maciej 18:27:47: eth1: Setting full-duplex based on MII #24 link partner capability of 05e1. 18:32:02: NETDEV WATCHDOG: eth1: transmit timed out 18:32:02: eth1: transmit timed out, tx_status 00 status e601. 18:32:02: diagnostics: net 0cfa media 8880 dma 003a fifo 8800 18:32:02: eth1: Interrupt posted but not delivered -- IRQ blocked by another device? 18:32:02: Flags; bus-master 1, dirty 16(0) current 16(0) 18:32:02: Transmit list vs. dff2c200. 18:32:02: 0: @dff2c200 length 8020 status 00010020 18:32:02: 1: @dff2c2a0 length 802a status 0001002a 18:32:02: 2: @dff2c340 length 802a status 0001002a 18:32:02: 3: @dff2c3e0 length 8076 status 00010076 18:32:02: 4: @dff2c480 length 802a status 0001002a 18:32:02: 5: @dff2c520 length 802a status 0001002a 18:32:02: 6: @dff2c5c0 length 802a status 0001002a 18:32:02: 7: @dff2c660 length 802a status 0001002a 18:32:02: 8: @dff2c700 length 802a status 0001002a 18:32:02: 9: @dff2c7a0 length 802a status 0001002a 18:32:02: 10: @dff2c840 length 802a status 0001002a 18:32:02: 11: @dff2c8e0 length 8020 status 00010020 18:32:02: 12: @dff2c980 length 8020 status 00010020 18:32:02: 13: @dff2ca20 length 8020 status 00010020 18:32:02: 14: @dff2cac0 length 8076 status 80010076 18:32:02: 15: @dff2cb60 length 8020 status 80010020 18:32:02: eth1: Resetting the Tx ring pointer. 18:38:02: NETDEV WATCHDOG: eth1: transmit timed out 18:38:02: eth1: transmit timed out, tx_status 00 status e601. 18:38:02: diagnostics: net 0cfa media 8880 dma 003a fifo 8000 18:38:02: eth1: Interrupt posted but not delivered -- IRQ blocked by another device? 18:38:02: Flags; bus-master 1, dirty 32(0) current 32(0) 18:38:02: Transmit list vs. dff2c200. 18:38:02: 0: @dff2c200 length 8020 status 00010020 18:38:02: 1: @dff2c2a0 length 8020 status 00010020 18:38:02: 2: @dff2c340 length 8020 status 00010020 18:38:02: 3: @dff2c3e0 length 802a status 0001002a 18:38:02: 4: @dff2c480 length 802a status 0001002a 18:38:02: 5: @dff2c520 length 802a status 0001002a 18:38:02: 6: @dff2c5c0 length 802a status 0001002a 18:38:02: 7: @dff2c660 length 802a status 0001002a 18:38:02: 8: @dff2c700 length 802a status 0001002a 18:38:02: 9: @dff2c7a0 length 802a status 0001002a 18:38:02: 10: @dff2c840 length 802a status 0001002a 18:38:02: 11: @dff2c8e0 length 802a status 0001002a 18:38:02: 12: @dff2c980 length 8020 status 00010020 18:38:02: 13: @dff2ca20 length 8076 status 00010076 18:38:02: 14: @dff2cac0 length 8020 status 80010020 18:38:02: 15: @dff2cb60 length 8020 status 80010020 18:38:02: eth1: Resetting the Tx ring pointer. 18:38:12: NETDEV WATCHDOG: eth1: transmit timed out 18:38:12: eth1: transmit timed out, tx_status 00 status e601. 18:38:12: diagnostics: net 0cfa media 8880 dma 003a fifo 18:38:12: eth1: Interrupt posted but not delivered -- IRQ blocked by another device? 18:38:12: Flags; bus-master 1, dirty 48(0) current 48(0) 18:38:12: Transmit list vs. dff2c200. 18:38:12: 0: @dff2c200 length 802a status 0001002a 18:38:12: 1: @dff2c2a0 length 802a status 0001002a 18:38:12: 2: @dff2c340 length 802a status 0001002a 18:38:12: 3: @dff2c3e0 length 802a status 0001002a 18:38:12: 4: @dff2c480 length 802a status 0001002a 18:38:12: 5: @dff2c520 length 802a status 0001002a 18:38:12: 6: @dff2c5c0 length 802a status 0001002a 18:38:12: 7: @dff2c660 length 802a status 0001002a 18:38:12: 8: @dff2c700 length 802a status 0001002a 18:38:12: 9: @dff2c7a0 length 802a status 0001002a 18:38:12: 10: @dff2c840 length 802a status 0001002a 18:38:12: 11: @dff2c8e0 length 802a status 0001002a 18:38:12: 12: @dff2c980 length 802a status 0001002a 18:38:12: 13: @dff2ca20 length 802a status 0001002a 18:38:12: 14: @dff2cac0 length 802a status 8001002a 18:38:12: 15: @dff2cb60 length 802a status 8001002a 18:38:12: eth1: Resetting the Tx ring pointer. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
3com 3c59x stopped working with 2.6.13-rc[56]
Hello, i tried to boot 2.6.13-rc5-git4 and 2.6.13-rc6-git13 both with the same result: my 3com (3c59x driver on 3com 905c) card not working. Here is what I saw in the logs. Notice the regularity of the log barfs. They continue the same every 10secs. The upgrade was committed using: cd /usr/src/linux patch -p1 ../patch-2.6.13-rc5 patch -p1 ../patch-2.6.13-rc5-git4 make oldconfig make bzImage modules modules_install install gcc-4.0.1 from Debian testing. Any ideas? Regards, Maciej 18:27:47: eth1: Setting full-duplex based on MII #24 link partner capability of 05e1. 18:32:02: NETDEV WATCHDOG: eth1: transmit timed out 18:32:02: eth1: transmit timed out, tx_status 00 status e601. 18:32:02: diagnostics: net 0cfa media 8880 dma 003a fifo 8800 18:32:02: eth1: Interrupt posted but not delivered -- IRQ blocked by another device? 18:32:02: Flags; bus-master 1, dirty 16(0) current 16(0) 18:32:02: Transmit list vs. dff2c200. 18:32:02: 0: @dff2c200 length 8020 status 00010020 18:32:02: 1: @dff2c2a0 length 802a status 0001002a 18:32:02: 2: @dff2c340 length 802a status 0001002a 18:32:02: 3: @dff2c3e0 length 8076 status 00010076 18:32:02: 4: @dff2c480 length 802a status 0001002a 18:32:02: 5: @dff2c520 length 802a status 0001002a 18:32:02: 6: @dff2c5c0 length 802a status 0001002a 18:32:02: 7: @dff2c660 length 802a status 0001002a 18:32:02: 8: @dff2c700 length 802a status 0001002a 18:32:02: 9: @dff2c7a0 length 802a status 0001002a 18:32:02: 10: @dff2c840 length 802a status 0001002a 18:32:02: 11: @dff2c8e0 length 8020 status 00010020 18:32:02: 12: @dff2c980 length 8020 status 00010020 18:32:02: 13: @dff2ca20 length 8020 status 00010020 18:32:02: 14: @dff2cac0 length 8076 status 80010076 18:32:02: 15: @dff2cb60 length 8020 status 80010020 18:32:02: eth1: Resetting the Tx ring pointer. 18:38:02: NETDEV WATCHDOG: eth1: transmit timed out 18:38:02: eth1: transmit timed out, tx_status 00 status e601. 18:38:02: diagnostics: net 0cfa media 8880 dma 003a fifo 8000 18:38:02: eth1: Interrupt posted but not delivered -- IRQ blocked by another device? 18:38:02: Flags; bus-master 1, dirty 32(0) current 32(0) 18:38:02: Transmit list vs. dff2c200. 18:38:02: 0: @dff2c200 length 8020 status 00010020 18:38:02: 1: @dff2c2a0 length 8020 status 00010020 18:38:02: 2: @dff2c340 length 8020 status 00010020 18:38:02: 3: @dff2c3e0 length 802a status 0001002a 18:38:02: 4: @dff2c480 length 802a status 0001002a 18:38:02: 5: @dff2c520 length 802a status 0001002a 18:38:02: 6: @dff2c5c0 length 802a status 0001002a 18:38:02: 7: @dff2c660 length 802a status 0001002a 18:38:02: 8: @dff2c700 length 802a status 0001002a 18:38:02: 9: @dff2c7a0 length 802a status 0001002a 18:38:02: 10: @dff2c840 length 802a status 0001002a 18:38:02: 11: @dff2c8e0 length 802a status 0001002a 18:38:02: 12: @dff2c980 length 8020 status 00010020 18:38:02: 13: @dff2ca20 length 8076 status 00010076 18:38:02: 14: @dff2cac0 length 8020 status 80010020 18:38:02: 15: @dff2cb60 length 8020 status 80010020 18:38:02: eth1: Resetting the Tx ring pointer. 18:38:12: NETDEV WATCHDOG: eth1: transmit timed out 18:38:12: eth1: transmit timed out, tx_status 00 status e601. 18:38:12: diagnostics: net 0cfa media 8880 dma 003a fifo 18:38:12: eth1: Interrupt posted but not delivered -- IRQ blocked by another device? 18:38:12: Flags; bus-master 1, dirty 48(0) current 48(0) 18:38:12: Transmit list vs. dff2c200. 18:38:12: 0: @dff2c200 length 802a status 0001002a 18:38:12: 1: @dff2c2a0 length 802a status 0001002a 18:38:12: 2: @dff2c340 length 802a status 0001002a 18:38:12: 3: @dff2c3e0 length 802a status 0001002a 18:38:12: 4: @dff2c480 length 802a status 0001002a 18:38:12: 5: @dff2c520 length 802a status 0001002a 18:38:12: 6: @dff2c5c0 length 802a status 0001002a 18:38:12: 7: @dff2c660 length 802a status 0001002a 18:38:12: 8: @dff2c700 length 802a status 0001002a 18:38:12: 9: @dff2c7a0 length 802a status 0001002a 18:38:12: 10: @dff2c840 length 802a status 0001002a 18:38:12: 11: @dff2c8e0 length 802a status 0001002a 18:38:12: 12: @dff2c980 length 802a status 0001002a 18:38:12: 13: @dff2ca20 length 802a status 0001002a 18:38:12: 14: @dff2cac0 length 802a status 8001002a 18:38:12: 15: @dff2cb60 length 802a status 8001002a 18:38:12: eth1: Resetting the Tx ring pointer. - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 3com 3c59x stopped working with 2.6.13-rc[56]
[EMAIL PROTECTED] wrote: i tried to boot 2.6.13-rc5-git4 and 2.6.13-rc6-git13 both with the same result: my 3com (3c59x driver on 3com 905c) card not working. Here is what I saw in the logs. Notice the regularity of the log barfs. They continue the same every 10secs. The upgrade was committed using: cd /usr/src/linux patch -p1 ../patch-2.6.13-rc5 patch -p1 ../patch-2.6.13-rc5-git4 make oldconfig make bzImage modules modules_install install gcc-4.0.1 from Debian testing. I assume it worked OK in 2.6.12. There are no changes in the driver which would explain this. 18:27:47: eth1: Setting full-duplex based on MII #24 link partner capability of 05e1. 18:32:02: NETDEV WATCHDOG: eth1: transmit timed out 18:32:02: eth1: transmit timed out, tx_status 00 status e601. 18:32:02: diagnostics: net 0cfa media 8880 dma 003a fifo 8800 18:32:02: eth1: Interrupt posted but not delivered -- IRQ blocked by another device? gargh, I have acpi feelings. Could you please a) Compare /proc/interrupts for 2.6.12 and 2.6.13-rc6 b) Generate the boot-time dmesg output for 2.6.12 and 2.6.13-rc6 (dmesg -s 100 foo), then do diff -u dmesg-2.6.12 dmesg-2.6.13-rc6 foo and send foo? - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 3com 3c59x stopped working with 2.6.13-rc[56]
i tried to boot 2.6.13-rc5-git4 and 2.6.13-rc6-git13 both with the same result: my 3com (3c59x driver on 3com 905c) card not working. Here is what I saw in the logs. Notice the regularity of the log barfs. They continue the same every 10secs. I'm currently using 2.6.13-rc6-git13 with the 3c95x driver compiled as a module, without any issues. I've tested all of the 2.6.13-* kernels. One noticeable difference, I've been using gcc-3.4.4 and not gcc-4.0.1. Steve - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
