Re: PRoblem with pcnet32 under 2.4.0 , was :Drivers under 2.4
I experimented some further today. using some printk i found out is was setting Fullduplex, hardcoded that to half-duplex (mine is connected to a hub and not a switch) , and it's configuration was 100Mbit as it was supposed to. Then i started looking at the start_xmit code and got lost :-))) Hope this helpes to pin-point the problem. Danny - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: PRoblem with pcnet32 under 2.4.0 , was :Drivers under 2.4
I experimented some further today. using some printk i found out is was setting Fullduplex, hardcoded that to half-duplex (mine is connected to a hub and not a switch) , and it's configuration was 100Mbit as it was supposed to. Then i started looking at the start_xmit code and got lost :-))) Hope this helpes to pin-point the problem. Danny - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: PRoblem with pcnet32 under 2.4.0 , was :Drivers under 2.4
On Fri, Jan 12, 2001 at 12:50:10PM +0100, Danny ter Haar wrote: > eth0: PCnet/FAST III 79C973 at 0xfce0, 00 00 e2 24 41 1d > pcnet32: pcnet32_private lp=c3c42000 lp_dma_addr=0x3c42000 assigned IRQ 9. > pcnet32.c:v1.25kf 26.9.1999 [EMAIL PROTECTED] same chip works for me von my P5 SMP box. > irq 0: 16840 timer irq 9: 0 acpi, PCnet/FAST III no interrupts for PCnet driver sounds more like interrupt routing problem to me. Thomas. -- Crap can work. Given enough thrust pigs will fly, but it's not necessary a good idea. [ Alexander Viro on linux-kernel ] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: PRoblem with pcnet32 under 2.4.0 , was :Drivers under 2.4
Hans Grobler <[EMAIL PROTECTED]> wrote: >> lspci -vx output: >What about the other devices? ok, here's the full listing : 00:00.0 Host bridge: Cyrix Corporation PCI Master Flags: bus master, medium devsel, latency 0 00: 78 10 01 00 07 00 80 02 00 00 00 06 00 00 00 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:0e.0 VGA compatible controller: Intergraphics Systems CyberPro 5000 (rev 02) (prog-if 00 [VGA]) Subsystem: Unknown device 0280:7000 Flags: medium devsel, IRQ 11 Memory at fd00 (32-bit, non-prefetchable) [size=16M] Expansion ROM at [disabled] [size=64K] 00: ea 10 00 50 03 00 00 02 02 00 00 03 04 40 00 00 10: 00 00 00 fd 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 80 02 00 70 30: 00 00 00 00 00 00 00 00 00 00 00 00 0b 01 00 00 00:0f.0 Ethernet controller: Advanced Micro Devices [AMD] 79c970 [PCnet LANCE] ( rev 42) Subsystem: Advanced Micro Devices [AMD]: Unknown device 2000 Flags: bus master, medium devsel, latency 64, IRQ 9 I/O ports at fce0 [size=32] Memory at fedffc00 (32-bit, non-prefetchable) [size=32] Expansion ROM at [disabled] [size=1M] Capabilities: [40] Power Management version 1 00: 22 10 00 20 07 00 90 02 42 00 00 02 00 40 00 00 10: e1 fc 00 00 00 fc df fe 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 22 10 00 20 30: 00 00 00 00 40 00 00 00 00 00 00 00 09 01 18 18 00:12.1 Bridge: Cyrix Corporation 5530 SMI [Kahlua] Flags: medium devsel Memory at 40012000 (32-bit, non-prefetchable) [size=256] 00: 78 10 01 01 02 00 80 02 00 00 80 06 00 00 00 00 10: 00 20 01 40 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:12.2 IDE interface: Cyrix Corporation 5530 IDE [Kahlua] (prog-if 00 []) Flags: medium devsel I/O ports at fc00 [size=16] 00: 78 10 02 01 01 00 80 02 00 00 01 01 00 00 00 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 01 fc 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:12.3 Multimedia audio controller: Cyrix Corporation 5530 Audio [Kahlua] Flags: bus master, medium devsel, latency 0 Memory at 40011000 (32-bit, non-prefetchable) [size=128] 00: 78 10 03 01 06 00 80 02 00 00 01 04 00 00 00 00 10: 00 10 01 40 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:13.0 USB Controller: Compaq Computer Corporation: Unknown device a0f8 (rev 06 ) (prog-if 10 [OHCI]) Subsystem: Compaq Computer Corporation: Unknown device a0f8 Flags: medium devsel, IRQ 10 Memory at fedfe000 (32-bit, non-prefetchable) [size=4K] 00: 11 0e f8 a0 13 00 80 02 06 10 03 0c 00 40 00 00 10: 00 e0 df fe 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 11 0e f8 a0 30: 00 00 00 00 00 00 00 00 00 00 00 00 0a 01 00 50 00:14.0 Multimedia video controller: Zoran
Re: PRoblem with pcnet32 under 2.4.0 , was :Drivers under 2.4
On Fri, 12 Jan 2001, Danny ter Haar wrote: > According to Hans Grobler: > > If you're willing, would you please follow "REPORTING-BUGS" and send some > > more info. Also cat /proc/interrupts. This one's intriging... Thanks for the report (still studying it). > lspci -vx output: > > 00:0f.0 Ethernet controller: Advanced Micro Devices [AMD] 79c970 [PCnet LANCE] ( What about the other devices? > irq 0: 16840 timer irq 9: 0 acpi, PCnet/FAST III Ok, this may not mean much, but have you tried compiling without acpi? Just to remove some variables... -- Hans - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
PRoblem with pcnet32 under 2.4.0 , was :Drivers under 2.4
According to Hans Grobler: > If you're willing, would you please follow "REPORTING-BUGS" and send some > more info. Also cat /proc/interrupts. This one's intriging... In short: Cyrix Multimedia box Everything onboard, including ethernet. Works as supposed to under 2.2.x (including 2.2.19pre7) installing 2.4.0 kernel recognises the driver but no byte is passed over the ethernet. Kernel: Linux version 2.4.0-ac7 (root@multimedia) (gcc version 2.95.3 20001229 (prerelea se)) #2 Fri Jan 12 11:17:47 CET 2001 Distribution: Debian unstable (sid) Output of loading the pcnet32 module: pcnet32_probe_pci: found device 0x001022.0x002000 ioaddr=0x00fce0 resource_flags=0x000101 PCI: Found IRQ 9 for device 00:0f.0 eth0: PCnet/FAST III 79C973 at 0xfce0, 00 00 e2 24 41 1d pcnet32: pcnet32_private lp=c3c42000 lp_dma_addr=0x3c42000 assigned IRQ 9. pcnet32.c:v1.25kf 26.9.1999 [EMAIL PROTECTED] lspci -vx output: 00:0f.0 Ethernet controller: Advanced Micro Devices [AMD] 79c970 [PCnet LANCE] ( rev 42) Subsystem: Advanced Micro Devices [AMD]: Unknown device 2000 Flags: bus master, medium devsel, latency 64, IRQ 9 I/O ports at fce0 [size=32] Memory at fedffc00 (32-bit, non-prefetchable) [size=32] Expansion ROM at [disabled] [size=1M] Capabilities: [40] Power Management version 1 00: 22 10 00 20 07 00 90 02 42 00 00 02 00 40 00 00 10: e1 fc 00 00 00 fc df fe 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 22 10 00 20 30: 00 00 00 00 40 00 00 00 00 00 00 00 09 01 18 18 The machine is connected to a 3com 8ports 100Mbit hub no additional parameters when the module is loaded, except i tried debug=7 which gave verbose output After bootup this is the situation: multimedia:~# ifconfig eth0 Link encap:Ethernet HWaddr 00:00:E2:24:41:1D inet addr:192.168.1.51 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 Interrupt:9 Base address:0xfce0 procinfo: multimedia:~# procinfo Linux 2.4.0-ac7 (root@multimedia) (gcc 2.95.3 20001229 ) #2 Fri Jan 12 11:17:47 CET 2001 1CPU [multimedia.(none)] Memory: TotalUsedFree Shared Buffers Cached Mem: 62308 12596 49712 0 6366636 Swap: 184708 0 184708 Bootup: Fri Jan 12 12:30:22 2001Load average: 0.02 0.03 0.01 1/28 229 user : 0:00:05.32 3.2% page in : 5744 nice : 0:00:00.00 0.0% page out: 354 system: 0:00:09.31 5.5% swap in :1 idle : 0:02:33.77 91.3% swap out:0 uptime: 0:02:48.38 context : 2940 irq 0: 16840 timer irq 9: 0 acpi, PCnet/FAST III irq 1: 3 keyboard irq 12: 0 PS/2 Mouse irq 2: 0 cascade [4] irq 14: 1640 ide0 irq 4: 127 serialirq 15: 3 ide1 irq 8: 1 rtc after trying to ping -c10 a host in it's own range (default gw in fact): Jan 12 12:30:36 multimedia kernel: eth0: pcnet32_open() irq 9 tx/rx rings 0x3c41 200/0x3c41000 init 0x3c41300. Jan 12 12:30:36 multimedia kernel: eth0: pcnet32 open after 5 ticks, init block 0x3c41300 csr0 01f3. Jan 12 12:30:38 multimedia kernel: eth0: pcnet32_start_xmit()
PRoblem with pcnet32 under 2.4.0 , was :Drivers under 2.4
According to Hans Grobler: If you're willing, would you please follow "REPORTING-BUGS" and send some more info. Also cat /proc/interrupts. This one's intriging... In short: Cyrix Multimedia box Everything onboard, including ethernet. Works as supposed to under 2.2.x (including 2.2.19pre7) installing 2.4.0 kernel recognises the driver but no byte is passed over the ethernet. Kernel: Linux version 2.4.0-ac7 (root@multimedia) (gcc version 2.95.3 20001229 (prerelea se)) #2 Fri Jan 12 11:17:47 CET 2001 Distribution: Debian unstable (sid) Output of loading the pcnet32 module: pcnet32_probe_pci: found device 0x001022.0x002000 ioaddr=0x00fce0 resource_flags=0x000101 PCI: Found IRQ 9 for device 00:0f.0 eth0: PCnet/FAST III 79C973 at 0xfce0, 00 00 e2 24 41 1d pcnet32: pcnet32_private lp=c3c42000 lp_dma_addr=0x3c42000 assigned IRQ 9. pcnet32.c:v1.25kf 26.9.1999 [EMAIL PROTECTED] lspci -vx output: 00:0f.0 Ethernet controller: Advanced Micro Devices [AMD] 79c970 [PCnet LANCE] ( rev 42) Subsystem: Advanced Micro Devices [AMD]: Unknown device 2000 Flags: bus master, medium devsel, latency 64, IRQ 9 I/O ports at fce0 [size=32] Memory at fedffc00 (32-bit, non-prefetchable) [size=32] Expansion ROM at unassigned [disabled] [size=1M] Capabilities: [40] Power Management version 1 00: 22 10 00 20 07 00 90 02 42 00 00 02 00 40 00 00 10: e1 fc 00 00 00 fc df fe 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 22 10 00 20 30: 00 00 00 00 40 00 00 00 00 00 00 00 09 01 18 18 The machine is connected to a 3com 8ports 100Mbit hub no additional parameters when the module is loaded, except i tried debug=7 which gave verbose output After bootup this is the situation: multimedia:~# ifconfig eth0 Link encap:Ethernet HWaddr 00:00:E2:24:41:1D inet addr:192.168.1.51 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 Interrupt:9 Base address:0xfce0 procinfo: multimedia:~# procinfo Linux 2.4.0-ac7 (root@multimedia) (gcc 2.95.3 20001229 ) #2 Fri Jan 12 11:17:47 CET 2001 1CPU [multimedia.(none)] Memory: TotalUsedFree Shared Buffers Cached Mem: 62308 12596 49712 0 6366636 Swap: 184708 0 184708 Bootup: Fri Jan 12 12:30:22 2001Load average: 0.02 0.03 0.01 1/28 229 user : 0:00:05.32 3.2% page in : 5744 nice : 0:00:00.00 0.0% page out: 354 system: 0:00:09.31 5.5% swap in :1 idle : 0:02:33.77 91.3% swap out:0 uptime: 0:02:48.38 context : 2940 irq 0: 16840 timer irq 9: 0 acpi, PCnet/FAST III irq 1: 3 keyboard irq 12: 0 PS/2 Mouse irq 2: 0 cascade [4] irq 14: 1640 ide0 irq 4: 127 serialirq 15: 3 ide1 irq 8: 1 rtc after trying to ping -c10 a host in it's own range (default gw in fact): Jan 12 12:30:36 multimedia kernel: eth0: pcnet32_open() irq 9 tx/rx rings 0x3c41 200/0x3c41000 init 0x3c41300. Jan 12 12:30:36 multimedia kernel: eth0: pcnet32 open after 5 ticks, init block 0x3c41300 csr0 01f3. Jan 12 12:30:38 multimedia kernel: eth0:
Re: PRoblem with pcnet32 under 2.4.0 , was :Drivers under 2.4
On Fri, 12 Jan 2001, Danny ter Haar wrote: According to Hans Grobler: If you're willing, would you please follow "REPORTING-BUGS" and send some more info. Also cat /proc/interrupts. This one's intriging... Thanks for the report (still studying it). lspci -vx output: 00:0f.0 Ethernet controller: Advanced Micro Devices [AMD] 79c970 [PCnet LANCE] ( What about the other devices? irq 0: 16840 timer irq 9: 0 acpi, PCnet/FAST III Ok, this may not mean much, but have you tried compiling without acpi? Just to remove some variables... -- Hans - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: PRoblem with pcnet32 under 2.4.0 , was :Drivers under 2.4
Hans Grobler [EMAIL PROTECTED] wrote: lspci -vx output: What about the other devices? ok, here's the full listing : 00:00.0 Host bridge: Cyrix Corporation PCI Master Flags: bus master, medium devsel, latency 0 00: 78 10 01 00 07 00 80 02 00 00 00 06 00 00 00 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:0e.0 VGA compatible controller: Intergraphics Systems CyberPro 5000 (rev 02) (prog-if 00 [VGA]) Subsystem: Unknown device 0280:7000 Flags: medium devsel, IRQ 11 Memory at fd00 (32-bit, non-prefetchable) [size=16M] Expansion ROM at unassigned [disabled] [size=64K] 00: ea 10 00 50 03 00 00 02 02 00 00 03 04 40 00 00 10: 00 00 00 fd 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 80 02 00 70 30: 00 00 00 00 00 00 00 00 00 00 00 00 0b 01 00 00 00:0f.0 Ethernet controller: Advanced Micro Devices [AMD] 79c970 [PCnet LANCE] ( rev 42) Subsystem: Advanced Micro Devices [AMD]: Unknown device 2000 Flags: bus master, medium devsel, latency 64, IRQ 9 I/O ports at fce0 [size=32] Memory at fedffc00 (32-bit, non-prefetchable) [size=32] Expansion ROM at unassigned [disabled] [size=1M] Capabilities: [40] Power Management version 1 00: 22 10 00 20 07 00 90 02 42 00 00 02 00 40 00 00 10: e1 fc 00 00 00 fc df fe 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 22 10 00 20 30: 00 00 00 00 40 00 00 00 00 00 00 00 09 01 18 18 00:12.1 Bridge: Cyrix Corporation 5530 SMI [Kahlua] Flags: medium devsel Memory at 40012000 (32-bit, non-prefetchable) [size=256] 00: 78 10 01 01 02 00 80 02 00 00 80 06 00 00 00 00 10: 00 20 01 40 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:12.2 IDE interface: Cyrix Corporation 5530 IDE [Kahlua] (prog-if 00 []) Flags: medium devsel I/O ports at fc00 [size=16] 00: 78 10 02 01 01 00 80 02 00 00 01 01 00 00 00 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 01 fc 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:12.3 Multimedia audio controller: Cyrix Corporation 5530 Audio [Kahlua] Flags: bus master, medium devsel, latency 0 Memory at 40011000 (32-bit, non-prefetchable) [size=128] 00: 78 10 03 01 06 00 80 02 00 00 01 04 00 00 00 00 10: 00 10 01 40 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:13.0 USB Controller: Compaq Computer Corporation: Unknown device a0f8 (rev 06 ) (prog-if 10 [OHCI]) Subsystem: Compaq Computer Corporation: Unknown device a0f8 Flags: medium devsel, IRQ 10 Memory at fedfe000 (32-bit, non-prefetchable) [size=4K] 00: 11 0e f8 a0 13 00 80 02 06 10 03 0c 00 40 00 00 10: 00 e0 df fe 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 11 0e f8 a0 30: 00 00 00 00 00 00 00 00 00 00 00 00 0a 01 00 50 00:14.0 Multimedia video
Re: PRoblem with pcnet32 under 2.4.0 , was :Drivers under 2.4
On Fri, Jan 12, 2001 at 12:50:10PM +0100, Danny ter Haar wrote: eth0: PCnet/FAST III 79C973 at 0xfce0, 00 00 e2 24 41 1d pcnet32: pcnet32_private lp=c3c42000 lp_dma_addr=0x3c42000 assigned IRQ 9. pcnet32.c:v1.25kf 26.9.1999 [EMAIL PROTECTED] same chip works for me von my P5 SMP box. irq 0: 16840 timer irq 9: 0 acpi, PCnet/FAST III no interrupts for PCnet driver sounds more like interrupt routing problem to me. Thomas. -- Crap can work. Given enough thrust pigs will fly, but it's not necessary a good idea. [ Alexander Viro on linux-kernel ] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Drivers under 2.4
Hi Danny, If you're willing, would you please follow "REPORTING-BUGS" and send some more info. Also cat /proc/interrupts. This one's intriging... -- Hans - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Drivers under 2.4
Jeff Garzik <[EMAIL PROTECTED]> wrote: >Does this patch help at all? Nope, unfortunatly it didn't > filename="pcnet32.patch" pcnet32_probe_pci: found device 0x001022.0x002000 ioaddr=0x00fce0 resource_flags=0x000101 PCI: Found IRQ 9 for device 00:0f.0 PCnet chip version is 0x22625003. eth0: PCnet/FAST III 79C973 at 0xfce0, 00 00 e2 24 41 1d<6>pcnet32: pcnet32_priv ate lp=c3fb8d40 lp_dma_addr=0x3bf1000 assigned IRQ 9. pcnet32.c:v1.25smp Nov 11, 2000 [EMAIL PROTECTED] eth0: pcnet32_open() irq 9 tx/rx rings 0x3bf1200/0x3bf1000 init 0x3bf1300. eth0: pcnet32 open after 5 ticks, init block 0x3bf1300 csr0 01f3. eth0: pcnet32_start_xmit() called, csr0 01f3. multimedia:~# ping -c5 192.168.1.1 PING 192.168.1.1 (192.168.1.1): 56 data bytes --- 192.168.1.1 ping statistics --- 5 packets transmitted, 0 packets received, 100% packet loss multimedia:~# arp -an ? (192.168.1.2) at on eth0 ? (192.168.1.1) at on eth0 multimedia:~# ifconfig eth0 eth0 Link encap:Ethernet HWaddr 00:00:E2:24:41:1D inet addr:192.168.1.51 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 Interrupt:9 Base address:0xfce0 Danny - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Drivers under 2.4
Danny ter Haar wrote:
>
> >Jan 11 12:45:49 multimedia kernel: eth0: pcnet32_start_xmit() called, csr0 07f3.
> >Jan 11 12:46:01 multimedia last message repeated 12 times
>
> hot from the ethernet wire: more info just arrived:
>
> NETDEV WATCHDOG: eth0: transmit timed out
> eth0: transmit timed out, status 07f3, resetting.
> Ring data dump: dirty_tx 0 cur_tx 16 (full) cur_rx 0.
> 03b2f012 0608 0040 0310 03b2f812 0608 0040 0310
> 03b2e012 0608 0040 0310 03b2e812 0608 0040 0310
> 03b2d012 0608 0040 0310 03b2d812 0608 0040 0310
> 03b2c012 0608 0040 0310 03b2c812 0608 0040 0310
> 03b2b012 0608 0040 0310 03b2b812 0608 0040 0310
> 03b2a012 0608 0040 0310 03b2a812 0608 0040 0310
> 03b29012 0608 0040 0310 03b29812 0608 0040 0310
> 03b28012 0608 0040 0310 03b28812 0608 0111 0310
> 03b3f012 0608 00fc 0310 03b3f812 0608 006a 0310
> 03b3e012 0608 0040 0310 03b3e812 0608 0040 0310
> 03b3d012 0608 0040 0310 03b3d812 0608 0040 0310
> 03b3c012 0608 0040 0310 03b3c812 0608 0040 0310
> 03b3a012 0608 0040 0310 03b3a812 0608 0040 0310
> 03b39012 0608 0040 0310 03b39812 0608 0040 0340
> 03b38012 0608 0040 0340 03b38812 0608 0040 0340
> 03b4f012 0608 0040 0340 03b4f812 0608 0040 0340
> 03f9a782 0066 0300 03b4e222 002a 0300
> 03b4e2a2 002a 0300 03b4e322 002a 0300
> 03b4e3a2 002a 0300 03b4e422 002a 0300
> 03b4e4a2 002a 0300 03b4e522 002a 0300
> 03b4e5a2 002a 0300 03b4e622 002a 0300
> 03b4e6a2 002a 0300 03b4eea2 002a 0300
> 03b4ef22 002a 0300 03f9a882 007e 0300
> 03f9a982 007e 0300 03f9aa82 007e 0300
> eth0: pcnet32_start_xmit() called, csr0 05f3.
> eth0: pcnet32_start_xmit() called, csr0 07f3.
>
> etc...
Does this patch help at all?
Jeff
--
Jeff Garzik | "You see, in this world there's two kinds of
Building 1024 | people, my friend: Those with loaded guns
MandrakeSoft | and those who dig. You dig." --Blondie
Index: drivers/net/pcnet32.c
===
RCS file: /cvsroot/gkernel/linux_2_4/drivers/net/pcnet32.c,v
retrieving revision 1.1.1.7
retrieving revision 1.1.1.7.10.1
diff -u -r1.1.1.7 -r1.1.1.7.10.1
--- drivers/net/pcnet32.c 2000/12/12 03:23:16 1.1.1.7
+++ drivers/net/pcnet32.c 2001/01/11 13:38:07 1.1.1.7.10.1
@@ -1,19 +1,22 @@
/* pcnet32.c: An AMD PCnet32 ethernet driver for linux. */
/*
* Copyright 1996-1999 Thomas Bogendoerfer
- *
+ *
* Derived from the lance driver written 1993,1994,1995 by Donald Becker.
- *
+ *
* Copyright 1993 United States Government as represented by the
* Director, National Security Agency.
- *
+ *
* This software may be used and distributed according to the terms
* of the GNU Public License, incorporated herein by reference.
*
* This driver is for PCnet32 and PCnetPCI based ethercards
+ *
+ * Nov 2000 (jgarzik): SMP, endian, PCI DMA, other fixes.
+ * Removed VLB support (use CONFIG_LANCE instead).
*/
-static const char *version = "pcnet32.c:v1.25kf 26.9.1999
[EMAIL PROTECTED]\n";
+static const char *version = "pcnet32.c:v1.25smp Nov 11, 2000
[EMAIL PROTECTED]\n";
#include
@@ -37,13 +40,9 @@
#include
#include
-static unsigned int pcnet32_portlist[] __initdata = {0x300, 0x320, 0x340, 0x360, 0};
-
static int pcnet32_debug = 1;
static int tx_start = 1; /* Mapping -- 0:20, 1:64, 2:128, 3:~220 (depends on chip
vers) */
-static struct net_device *pcnet32_dev;
-
static const int max_interrupt_work = 80;
static const int rx_copybreak = 200;
@@ -63,10 +62,10 @@
* table to translate option values from tulip
* to internal options
*/
-static unsigned char options_mapping[] = {
+static unsigned char options_mapping[] __initdata = {
PORT_ASEL,/* 0 Auto-select */
PORT_AUI, /* 1 BNC/AUI */
-PORT_AUI, /* 2 AUI/BNC */
+PORT_AUI, /* 2 AUI/BNC */
PORT_ASEL,/* 3 not supported*/
PORT_10BT | PORT_FD, /* 4 10baseT-FD */
PORT_ASEL,/* 5 not supported*/
@@ -88,14 +87,14 @@
/*
* Theory of Operation
- *
+ *
* This driver uses the same software structure as the normal lance
* driver. So look for a verbose description in lance.c. The differences
* to the normal lance driver is the use of the 32bit mode of PCnet32
* and PCnetPCI chips. Because these chips are 32bit chips, there is no
* 16MB limitation and we don't need bounce buffers.
*/
-
+
/*
* History:
* v0.01: Initial version
@@ -149,7 +148,7 @@
* v1.22: changed pci scanning code
Re: Drivers under 2.4
>Jan 11 12:45:49 multimedia kernel: eth0: pcnet32_start_xmit() called, csr0 07f3. >Jan 11 12:46:01 multimedia last message repeated 12 times hot from the ethernet wire: more info just arrived: NETDEV WATCHDOG: eth0: transmit timed out eth0: transmit timed out, status 07f3, resetting. Ring data dump: dirty_tx 0 cur_tx 16 (full) cur_rx 0. 03b2f012 0608 0040 0310 03b2f812 0608 0040 0310 03b2e012 0608 0040 0310 03b2e812 0608 0040 0310 03b2d012 0608 0040 0310 03b2d812 0608 0040 0310 03b2c012 0608 0040 0310 03b2c812 0608 0040 0310 03b2b012 0608 0040 0310 03b2b812 0608 0040 0310 03b2a012 0608 0040 0310 03b2a812 0608 0040 0310 03b29012 0608 0040 0310 03b29812 0608 0040 0310 03b28012 0608 0040 0310 03b28812 0608 0111 0310 03b3f012 0608 00fc 0310 03b3f812 0608 006a 0310 03b3e012 0608 0040 0310 03b3e812 0608 0040 0310 03b3d012 0608 0040 0310 03b3d812 0608 0040 0310 03b3c012 0608 0040 0310 03b3c812 0608 0040 0310 03b3a012 0608 0040 0310 03b3a812 0608 0040 0310 03b39012 0608 0040 0310 03b39812 0608 0040 0340 03b38012 0608 0040 0340 03b38812 0608 0040 0340 03b4f012 0608 0040 0340 03b4f812 0608 0040 0340 03f9a782 0066 0300 03b4e222 002a 0300 03b4e2a2 002a 0300 03b4e322 002a 0300 03b4e3a2 002a 0300 03b4e422 002a 0300 03b4e4a2 002a 0300 03b4e522 002a 0300 03b4e5a2 002a 0300 03b4e622 002a 0300 03b4e6a2 002a 0300 03b4eea2 002a 0300 03b4ef22 002a 0300 03f9a882 007e 0300 03f9a982 007e 0300 03f9aa82 007e 0300 eth0: pcnet32_start_xmit() called, csr0 05f3. eth0: pcnet32_start_xmit() called, csr0 07f3. etc... Danny - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Drivers under 2.4
> cyrix processor, chipset and amd/lance ethernet chipset onboard. > It' working fine with 2.2.x but not with 2.4.x kernels with > the same driver version of the pcnet32 networkdriver. What problems do you see - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Drivers under 2.4
Andrew Morton <[EMAIL PROTECTED]> wrote: >There's a "reporting problems" section at the end >of Documentation/networking/vortex.txt. Should help. okidoki, have read it, thanks >Probably the most important thing is inserting the driver >module with `debug=7', opening the device, sending some >traffic and then sending us the logs. pcnet32_probe_pci: found device 0x001022.0x002000 ioaddr=0x00fce0 resource_flags=0x000101 PCI: Found IRQ 9 for device 00:0f.0 PCnet chip version is 0x22625003. eth0: PCnet/FAST III 79C973 at 0xfce0, 00 00 e2 24 41 1d pcnet32: pcnet32_private lp=c3bf6000 lp_dma_addr=0x3bf6000 assigned IRQ 9. pcnet32.c:v1.25kf 26.9.1999 [EMAIL PROTECTED] eth0: pcnet32_open() irq 9 tx/rx rings 0x3bf6200/0x3bf6000 init 0x3bf6300. eth0: pcnet32 open after 5 ticks, init block 0x3bf6300 csr0 01f3. eth0: pcnet32_start_xmit() called, csr0 01f3. this after bootup, static ip adress multimedia:~# ifconfig eth0 eth0 Link encap:Ethernet HWaddr 00:00:E2:24:41:1D inet addr:192.168.1.51 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 Interrupt:9 Base address:0xfce0 multimedia:~# ping -c10 192.168.1.1 PING 192.168.1.1 (192.168.1.1): 56 data bytes --- 192.168.1.1 ping statistics --- 10 packets transmitted, 0 packets received, 100% packet loss after this the following messages in dmesg: Jan 11 12:45:49 multimedia kernel: eth0: pcnet32_start_xmit() called, csr0 07f3. Jan 11 12:46:01 multimedia last message repeated 12 times Danny - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Drivers under 2.4
Danny ter Haar wrote: > > According to Andi Kleen: > > "Doesn't work" isn't a very useful bug report. What happens exactly? > > Do the RX/TX/error counters increase when you try to send packets? > > no, the counters you see with ifconfig eth0 are set to zero > for rx and to 1 for tx. > > So it's trying to send out data but somehow it doesn't work. > Since the driver version is the same (althoud the output is > slihtly different which seems odd) i suspect the PCI > probing to be folded somewhere. > > How could i provide people with more info ? There's a "reporting problems" section at the end of Documentation/networking/vortex.txt. Should help. Probably the most important thing is inserting the driver module with `debug=7', opening the device, sending some traffic and then sending us the logs. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Drivers under 2.4
According to Andi Kleen: > "Doesn't work" isn't a very useful bug report. What happens exactly? > Do the RX/TX/error counters increase when you try to send packets? no, the counters you see with ifconfig eth0 are set to zero for rx and to 1 for tx. So it's trying to send out data but somehow it doesn't work. Since the driver version is the same (althoud the output is slihtly different which seems odd) i suspect the PCI probing to be folded somewhere. How could i provide people with more info ? Thanks, Danny - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Drivers under 2.4
On Thu, Jan 11, 2001 at 10:24:01AM +, Danny ter Haar wrote: > Version number of the driver is the same but it doesn't work. > > Any thoughts anyone ? "Doesn't work" isn't a very useful bug report. What happens exactly? Do the RX/TX/error counters increase when you try to send packets? -Andi - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Drivers under 2.4
Hans Grobler <[EMAIL PROTECTED]> wrote: >The softnet changes are most likely the primary source of breakage (for >network drivers). I happen to have a multimedia box from siemens/fujitsu with a cyrix processor, chipset and amd/lance ethernet chipset onboard. It' working fine with 2.2.x but not with 2.4.x kernels with the same driver version of the pcnet32 networkdriver. 2.4.0-ac4 Jan 9 17:09:53 multimedia kernel: Linux version 2.4.0-ac4 (root@ws1) (gcc version 2.95.3 20001229 (prerelease)) #2 Tue Jan 9 16:22:08 CET 2001 Jan 9 17:09:53 multimedia kernel: PCI: Found IRQ 9 for device 00:0f.0 Jan 9 17:09:53 multimedia kernel: eth0: PCnet/FAST III 79C973 at 0xfce0, 00 00 e2 24 41 1d Jan 9 17:09:53 multimedia kernel: pcnet32: pcnet32_private lp=c3c8 lp_dma_addr=0x3c8 assigned IRQ 9. Jan 9 17:09:53 multimedia kernel: pcnet32.c:v1.25kf 26.9.1999 [EMAIL PROTECTED] and 2.2.19pre7 Jan 10 20:46:15 multimedia kernel: Linux version 2.2.19pre7 (root@multimedia) (gcc version 2.95.3 20001229 (prerelease)) #2 Wed Jan 10 20:13:57 CET 2001 Jan 10 20:46:15 multimedia kernel: pcnet32.c: PCI bios is present, checking for devices... Jan 10 20:46:15 multimedia kernel: Found PCnet/PCI at 0xfce0, irq 9. Jan 10 20:46:15 multimedia kernel: eth0: PCnet/FAST III 79C973 at 0xfce0, 00 00 e2 24 41 1d assigned IRQ 9. Jan 10 20:46:15 multimedia kernel: pcnet32.c:v1.25kf 26.9.1999 [EMAIL PROTECTED] Version number of the driver is the same but it doesn't work. Any thoughts anyone ? Danny - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Drivers under 2.4
Hans Grobler [EMAIL PROTECTED] wrote: The softnet changes are most likely the primary source of breakage (for network drivers). I happen to have a multimedia box from siemens/fujitsu with a cyrix processor, chipset and amd/lance ethernet chipset onboard. It' working fine with 2.2.x but not with 2.4.x kernels with the same driver version of the pcnet32 networkdriver. 2.4.0-ac4 Jan 9 17:09:53 multimedia kernel: Linux version 2.4.0-ac4 (root@ws1) (gcc version 2.95.3 20001229 (prerelease)) #2 Tue Jan 9 16:22:08 CET 2001 Jan 9 17:09:53 multimedia kernel: PCI: Found IRQ 9 for device 00:0f.0 Jan 9 17:09:53 multimedia kernel: eth0: PCnet/FAST III 79C973 at 0xfce0, 00 00 e2 24 41 1d Jan 9 17:09:53 multimedia kernel: pcnet32: pcnet32_private lp=c3c8 lp_dma_addr=0x3c8 assigned IRQ 9. Jan 9 17:09:53 multimedia kernel: pcnet32.c:v1.25kf 26.9.1999 [EMAIL PROTECTED] and 2.2.19pre7 Jan 10 20:46:15 multimedia kernel: Linux version 2.2.19pre7 (root@multimedia) (gcc version 2.95.3 20001229 (prerelease)) #2 Wed Jan 10 20:13:57 CET 2001 Jan 10 20:46:15 multimedia kernel: pcnet32.c: PCI bios is present, checking for devices... Jan 10 20:46:15 multimedia kernel: Found PCnet/PCI at 0xfce0, irq 9. Jan 10 20:46:15 multimedia kernel: eth0: PCnet/FAST III 79C973 at 0xfce0, 00 00 e2 24 41 1d assigned IRQ 9. Jan 10 20:46:15 multimedia kernel: pcnet32.c:v1.25kf 26.9.1999 [EMAIL PROTECTED] Version number of the driver is the same but it doesn't work. Any thoughts anyone ? Danny - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Drivers under 2.4
On Thu, Jan 11, 2001 at 10:24:01AM +, Danny ter Haar wrote: Version number of the driver is the same but it doesn't work. Any thoughts anyone ? "Doesn't work" isn't a very useful bug report. What happens exactly? Do the RX/TX/error counters increase when you try to send packets? -Andi - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Drivers under 2.4
According to Andi Kleen: "Doesn't work" isn't a very useful bug report. What happens exactly? Do the RX/TX/error counters increase when you try to send packets? no, the counters you see with ifconfig eth0 are set to zero for rx and to 1 for tx. So it's trying to send out data but somehow it doesn't work. Since the driver version is the same (althoud the output is slihtly different which seems odd) i suspect the PCI probing to be folded somewhere. How could i provide people with more info ? Thanks, Danny - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Drivers under 2.4
Danny ter Haar wrote: According to Andi Kleen: "Doesn't work" isn't a very useful bug report. What happens exactly? Do the RX/TX/error counters increase when you try to send packets? no, the counters you see with ifconfig eth0 are set to zero for rx and to 1 for tx. So it's trying to send out data but somehow it doesn't work. Since the driver version is the same (althoud the output is slihtly different which seems odd) i suspect the PCI probing to be folded somewhere. How could i provide people with more info ? There's a "reporting problems" section at the end of Documentation/networking/vortex.txt. Should help. Probably the most important thing is inserting the driver module with `debug=7', opening the device, sending some traffic and then sending us the logs. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Drivers under 2.4
Andrew Morton [EMAIL PROTECTED] wrote: There's a "reporting problems" section at the end of Documentation/networking/vortex.txt. Should help. okidoki, have read it, thanks Probably the most important thing is inserting the driver module with `debug=7', opening the device, sending some traffic and then sending us the logs. pcnet32_probe_pci: found device 0x001022.0x002000 ioaddr=0x00fce0 resource_flags=0x000101 PCI: Found IRQ 9 for device 00:0f.0 PCnet chip version is 0x22625003. eth0: PCnet/FAST III 79C973 at 0xfce0, 00 00 e2 24 41 1d pcnet32: pcnet32_private lp=c3bf6000 lp_dma_addr=0x3bf6000 assigned IRQ 9. pcnet32.c:v1.25kf 26.9.1999 [EMAIL PROTECTED] eth0: pcnet32_open() irq 9 tx/rx rings 0x3bf6200/0x3bf6000 init 0x3bf6300. eth0: pcnet32 open after 5 ticks, init block 0x3bf6300 csr0 01f3. eth0: pcnet32_start_xmit() called, csr0 01f3. this after bootup, static ip adress multimedia:~# ifconfig eth0 eth0 Link encap:Ethernet HWaddr 00:00:E2:24:41:1D inet addr:192.168.1.51 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 Interrupt:9 Base address:0xfce0 multimedia:~# ping -c10 192.168.1.1 PING 192.168.1.1 (192.168.1.1): 56 data bytes --- 192.168.1.1 ping statistics --- 10 packets transmitted, 0 packets received, 100% packet loss after this the following messages in dmesg: Jan 11 12:45:49 multimedia kernel: eth0: pcnet32_start_xmit() called, csr0 07f3. Jan 11 12:46:01 multimedia last message repeated 12 times Danny - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Drivers under 2.4
cyrix processor, chipset and amd/lance ethernet chipset onboard. It' working fine with 2.2.x but not with 2.4.x kernels with the same driver version of the pcnet32 networkdriver. What problems do you see - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Drivers under 2.4
Jan 11 12:45:49 multimedia kernel: eth0: pcnet32_start_xmit() called, csr0 07f3. Jan 11 12:46:01 multimedia last message repeated 12 times hot from the ethernet wire: more info just arrived: NETDEV WATCHDOG: eth0: transmit timed out eth0: transmit timed out, status 07f3, resetting. Ring data dump: dirty_tx 0 cur_tx 16 (full) cur_rx 0. 03b2f012 0608 0040 0310 03b2f812 0608 0040 0310 03b2e012 0608 0040 0310 03b2e812 0608 0040 0310 03b2d012 0608 0040 0310 03b2d812 0608 0040 0310 03b2c012 0608 0040 0310 03b2c812 0608 0040 0310 03b2b012 0608 0040 0310 03b2b812 0608 0040 0310 03b2a012 0608 0040 0310 03b2a812 0608 0040 0310 03b29012 0608 0040 0310 03b29812 0608 0040 0310 03b28012 0608 0040 0310 03b28812 0608 0111 0310 03b3f012 0608 00fc 0310 03b3f812 0608 006a 0310 03b3e012 0608 0040 0310 03b3e812 0608 0040 0310 03b3d012 0608 0040 0310 03b3d812 0608 0040 0310 03b3c012 0608 0040 0310 03b3c812 0608 0040 0310 03b3a012 0608 0040 0310 03b3a812 0608 0040 0310 03b39012 0608 0040 0310 03b39812 0608 0040 0340 03b38012 0608 0040 0340 03b38812 0608 0040 0340 03b4f012 0608 0040 0340 03b4f812 0608 0040 0340 03f9a782 0066 0300 03b4e222 002a 0300 03b4e2a2 002a 0300 03b4e322 002a 0300 03b4e3a2 002a 0300 03b4e422 002a 0300 03b4e4a2 002a 0300 03b4e522 002a 0300 03b4e5a2 002a 0300 03b4e622 002a 0300 03b4e6a2 002a 0300 03b4eea2 002a 0300 03b4ef22 002a 0300 03f9a882 007e 0300 03f9a982 007e 0300 03f9aa82 007e 0300 eth0: pcnet32_start_xmit() called, csr0 05f3. eth0: pcnet32_start_xmit() called, csr0 07f3. etc... Danny - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Drivers under 2.4
Danny ter Haar wrote:
Jan 11 12:45:49 multimedia kernel: eth0: pcnet32_start_xmit() called, csr0 07f3.
Jan 11 12:46:01 multimedia last message repeated 12 times
hot from the ethernet wire: more info just arrived:
NETDEV WATCHDOG: eth0: transmit timed out
eth0: transmit timed out, status 07f3, resetting.
Ring data dump: dirty_tx 0 cur_tx 16 (full) cur_rx 0.
03b2f012 0608 0040 0310 03b2f812 0608 0040 0310
03b2e012 0608 0040 0310 03b2e812 0608 0040 0310
03b2d012 0608 0040 0310 03b2d812 0608 0040 0310
03b2c012 0608 0040 0310 03b2c812 0608 0040 0310
03b2b012 0608 0040 0310 03b2b812 0608 0040 0310
03b2a012 0608 0040 0310 03b2a812 0608 0040 0310
03b29012 0608 0040 0310 03b29812 0608 0040 0310
03b28012 0608 0040 0310 03b28812 0608 0111 0310
03b3f012 0608 00fc 0310 03b3f812 0608 006a 0310
03b3e012 0608 0040 0310 03b3e812 0608 0040 0310
03b3d012 0608 0040 0310 03b3d812 0608 0040 0310
03b3c012 0608 0040 0310 03b3c812 0608 0040 0310
03b3a012 0608 0040 0310 03b3a812 0608 0040 0310
03b39012 0608 0040 0310 03b39812 0608 0040 0340
03b38012 0608 0040 0340 03b38812 0608 0040 0340
03b4f012 0608 0040 0340 03b4f812 0608 0040 0340
03f9a782 0066 0300 03b4e222 002a 0300
03b4e2a2 002a 0300 03b4e322 002a 0300
03b4e3a2 002a 0300 03b4e422 002a 0300
03b4e4a2 002a 0300 03b4e522 002a 0300
03b4e5a2 002a 0300 03b4e622 002a 0300
03b4e6a2 002a 0300 03b4eea2 002a 0300
03b4ef22 002a 0300 03f9a882 007e 0300
03f9a982 007e 0300 03f9aa82 007e 0300
eth0: pcnet32_start_xmit() called, csr0 05f3.
eth0: pcnet32_start_xmit() called, csr0 07f3.
etc...
Does this patch help at all?
Jeff
--
Jeff Garzik | "You see, in this world there's two kinds of
Building 1024 | people, my friend: Those with loaded guns
MandrakeSoft | and those who dig. You dig." --Blondie
Index: drivers/net/pcnet32.c
===
RCS file: /cvsroot/gkernel/linux_2_4/drivers/net/pcnet32.c,v
retrieving revision 1.1.1.7
retrieving revision 1.1.1.7.10.1
diff -u -r1.1.1.7 -r1.1.1.7.10.1
--- drivers/net/pcnet32.c 2000/12/12 03:23:16 1.1.1.7
+++ drivers/net/pcnet32.c 2001/01/11 13:38:07 1.1.1.7.10.1
@@ -1,19 +1,22 @@
/* pcnet32.c: An AMD PCnet32 ethernet driver for linux. */
/*
* Copyright 1996-1999 Thomas Bogendoerfer
- *
+ *
* Derived from the lance driver written 1993,1994,1995 by Donald Becker.
- *
+ *
* Copyright 1993 United States Government as represented by the
* Director, National Security Agency.
- *
+ *
* This software may be used and distributed according to the terms
* of the GNU Public License, incorporated herein by reference.
*
* This driver is for PCnet32 and PCnetPCI based ethercards
+ *
+ * Nov 2000 (jgarzik): SMP, endian, PCI DMA, other fixes.
+ * Removed VLB support (use CONFIG_LANCE instead).
*/
-static const char *version = "pcnet32.c:v1.25kf 26.9.1999
[EMAIL PROTECTED]\n";
+static const char *version = "pcnet32.c:v1.25smp Nov 11, 2000
[EMAIL PROTECTED]\n";
#include linux/module.h
@@ -37,13 +40,9 @@
#include linux/skbuff.h
#include linux/spinlock.h
-static unsigned int pcnet32_portlist[] __initdata = {0x300, 0x320, 0x340, 0x360, 0};
-
static int pcnet32_debug = 1;
static int tx_start = 1; /* Mapping -- 0:20, 1:64, 2:128, 3:~220 (depends on chip
vers) */
-static struct net_device *pcnet32_dev;
-
static const int max_interrupt_work = 80;
static const int rx_copybreak = 200;
@@ -63,10 +62,10 @@
* table to translate option values from tulip
* to internal options
*/
-static unsigned char options_mapping[] = {
+static unsigned char options_mapping[] __initdata = {
PORT_ASEL,/* 0 Auto-select */
PORT_AUI, /* 1 BNC/AUI */
-PORT_AUI, /* 2 AUI/BNC */
+PORT_AUI, /* 2 AUI/BNC */
PORT_ASEL,/* 3 not supported*/
PORT_10BT | PORT_FD, /* 4 10baseT-FD */
PORT_ASEL,/* 5 not supported*/
@@ -88,14 +87,14 @@
/*
* Theory of Operation
- *
+ *
* This driver uses the same software structure as the normal lance
* driver. So look for a verbose description in lance.c. The differences
* to the normal lance driver is the use of the 32bit mode of PCnet32
* and PCnetPCI chips. Because these chips are 32bit chips, there is no
* 16MB limitation and we don't need bounce buffers.
*/
-
+
/*
* History:
* v0.01: Initial version
@@ -149,7 +148,7 @@
* v1.22: changed pci scanning
Re: Drivers under 2.4
Jeff Garzik [EMAIL PROTECTED] wrote: Does this patch help at all? Nope, unfortunatly it didn't filename="pcnet32.patch" pcnet32_probe_pci: found device 0x001022.0x002000 ioaddr=0x00fce0 resource_flags=0x000101 PCI: Found IRQ 9 for device 00:0f.0 PCnet chip version is 0x22625003. eth0: PCnet/FAST III 79C973 at 0xfce0, 00 00 e2 24 41 1d6pcnet32: pcnet32_priv ate lp=c3fb8d40 lp_dma_addr=0x3bf1000 assigned IRQ 9. pcnet32.c:v1.25smp Nov 11, 2000 [EMAIL PROTECTED] eth0: pcnet32_open() irq 9 tx/rx rings 0x3bf1200/0x3bf1000 init 0x3bf1300. eth0: pcnet32 open after 5 ticks, init block 0x3bf1300 csr0 01f3. eth0: pcnet32_start_xmit() called, csr0 01f3. multimedia:~# ping -c5 192.168.1.1 PING 192.168.1.1 (192.168.1.1): 56 data bytes --- 192.168.1.1 ping statistics --- 5 packets transmitted, 0 packets received, 100% packet loss multimedia:~# arp -an ? (192.168.1.2) at incomplete on eth0 ? (192.168.1.1) at incomplete on eth0 multimedia:~# ifconfig eth0 eth0 Link encap:Ethernet HWaddr 00:00:E2:24:41:1D inet addr:192.168.1.51 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 Interrupt:9 Base address:0xfce0 Danny - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Drivers under 2.4
Hi Danny, If you're willing, would you please follow "REPORTING-BUGS" and send some more info. Also cat /proc/interrupts. This one's intriging... -- Hans - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Drivers under 2.4
On Wed, 10 Jan 2001, Andi Kleen wrote: > On Wed, Jan 10, 2001 at 04:37:06PM -0500, Dennis wrote: > > > > Aren't you supposed to design the spec BEFORE you implement it? > > Try http://www.firstfloor.org/~andi/softnet (minor details outdated) The softnet changes are most likely the primary source of breakage (for network drivers). You should also read the kernel-* docs under Documentation/DocBook (see Documentation/kernel-doc-nano-HOWTO.txt). -- Hans - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Drivers under 2.4
On Wed, Jan 10, 2001 at 04:37:06PM -0500, Dennis wrote: > At 03:01 PM 01/10/2001, Hans Grobler wrote: > >On Wed, 10 Jan 2001, Dennis wrote: > > > At 02:57 PM 01/09/2001, Dennis wrote: > > > >Where might one find the definitive document on porting device drivers to > > > >2.4 kernels? > > > > > > should I assume that there are none? > > > >I don't think anyone has had the time yet. I'm sure someone will get > >around to this soon. If you ask specific questions here, the answers may > >well form the basis for such a document. > > > Aren't you supposed to design the spec BEFORE you implement it? Try http://www.firstfloor.org/~andi/softnet (minor details outdated) -Andi - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Drivers under 2.4
At 03:01 PM 01/10/2001, Hans Grobler wrote: >On Wed, 10 Jan 2001, Dennis wrote: > > At 02:57 PM 01/09/2001, Dennis wrote: > > >Where might one find the definitive document on porting device drivers to > > >2.4 kernels? > > > > should I assume that there are none? > >I don't think anyone has had the time yet. I'm sure someone will get >around to this soon. If you ask specific questions here, the answers may >well form the basis for such a document. Aren't you supposed to design the spec BEFORE you implement it? >-- Hans > > >- >To unsubscribe from this list: send the line "unsubscribe linux-kernel" in >the body of a message to [EMAIL PROTECTED] >Please read the FAQ at http://www.tux.org/lkml/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Drivers under 2.4
On Wed, 10 Jan 2001, Dennis wrote: > At 02:57 PM 01/09/2001, Dennis wrote: > >Where might one find the definitive document on porting device drivers to > >2.4 kernels? > > should I assume that there are none? I don't think anyone has had the time yet. I'm sure someone will get around to this soon. If you ask specific questions here, the answers may well form the basis for such a document. -- Hans - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Drivers under 2.4
At 02:57 PM 01/09/2001, Dennis wrote: >Where might one find the definitive document on porting device drivers to >2.4 kernels? > >DB should I assume that there are none? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Drivers under 2.4
At 02:57 PM 01/09/2001, Dennis wrote: Where might one find the definitive document on porting device drivers to 2.4 kernels? DB should I assume that there are none? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Drivers under 2.4
On Wed, 10 Jan 2001, Dennis wrote: At 02:57 PM 01/09/2001, Dennis wrote: Where might one find the definitive document on porting device drivers to 2.4 kernels? should I assume that there are none? I don't think anyone has had the time yet. I'm sure someone will get around to this soon. If you ask specific questions here, the answers may well form the basis for such a document. -- Hans - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Drivers under 2.4
At 03:01 PM 01/10/2001, Hans Grobler wrote: On Wed, 10 Jan 2001, Dennis wrote: At 02:57 PM 01/09/2001, Dennis wrote: Where might one find the definitive document on porting device drivers to 2.4 kernels? should I assume that there are none? I don't think anyone has had the time yet. I'm sure someone will get around to this soon. If you ask specific questions here, the answers may well form the basis for such a document. Aren't you supposed to design the spec BEFORE you implement it? -- Hans - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Drivers under 2.4
On Wed, Jan 10, 2001 at 04:37:06PM -0500, Dennis wrote: At 03:01 PM 01/10/2001, Hans Grobler wrote: On Wed, 10 Jan 2001, Dennis wrote: At 02:57 PM 01/09/2001, Dennis wrote: Where might one find the definitive document on porting device drivers to 2.4 kernels? should I assume that there are none? I don't think anyone has had the time yet. I'm sure someone will get around to this soon. If you ask specific questions here, the answers may well form the basis for such a document. Aren't you supposed to design the spec BEFORE you implement it? Try http://www.firstfloor.org/~andi/softnet (minor details outdated) -Andi - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Drivers under 2.4
On Wed, 10 Jan 2001, Andi Kleen wrote: On Wed, Jan 10, 2001 at 04:37:06PM -0500, Dennis wrote: Aren't you supposed to design the spec BEFORE you implement it? Try http://www.firstfloor.org/~andi/softnet (minor details outdated) The softnet changes are most likely the primary source of breakage (for network drivers). You should also read the kernel-* docs under Documentation/DocBook (see Documentation/kernel-doc-nano-HOWTO.txt). -- Hans - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Drivers under 2.4
Where might one find the definitive document on porting device drivers to 2.4 kernels? DB - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Drivers under 2.4
Where might one find the definitive document on porting device drivers to 2.4 kernels? DB - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
