Re: Bug#586967: (no subject)
On Tue, 2010-08-31 at 04:12 +0200, Jens Schüßler wrote: Hi Bob, What is the exact model you have (use lspci -nn -d 10b7:)? 00:0b.0 Ethernet controller [0200]: 3Com Corporation 3c595 100BaseTX [Vortex] [10b7:5950] Also can you try enabling some debug logging: rmmod 3c59x modprobe 3c59x debug=3 Then run dmesg to get the logged messages, and send them back. There are not much, even if I set debug=7 , | [ 72.752091] See Documentation/networking/vortex.txt | [ 72.752098] :00:0b.0: 3Com PCI 3c595 Vortex 100baseTx at 00018800. | [ 72.772890] 00:a0:24:43:dd:fd, IRQ 11 | [ 72.780517] product code 4255 rev 00.0 date 12-02-95 | [ 72.780527] 64K word-wide RAM 1:1 Rx:Tx split, autoselect/10baseT interface. | [ 72.780533] :00:0b.0: scatter/gather disabled. h/w checksums disabledo | ` and thats all. That at least lets me see how it's different from the card I have here. Dialin to a my ISP works (card is connected to a DSL-Modem), but if there are comes traffic I just done a 'links www.google.de' and everything freezes totally, but I saw , | Refresh [ 76.79933] eth0 vortex_error(), status=0xe091 ` on the terminal at this moment. That message is *precisely* what I needed to find the bug, thanks. Booting to my parallel installed Ubuntu, also with kernel 2.6.32, everything is alright. Could I be the only one with this problem, and should I better file a new bug? This is a new bug, introduced by my fix for the previous bug. However, this driver supports a wide range of cards and this new bug only affects some of them. Please do make a new bug report. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Bug#586967: (no subject)
Hi Bob, What is the exact model you have (use lspci -nn -d 10b7:)? 00:0b.0 Ethernet controller [0200]: 3Com Corporation 3c595 100BaseTX [Vortex] [10b7:5950] Also can you try enabling some debug logging: rmmod 3c59x modprobe 3c59x debug=3 Then run dmesg to get the logged messages, and send them back. There are not much, even if I set debug=7 , | [ 72.752091] See Documentation/networking/vortex.txt | [ 72.752098] :00:0b.0: 3Com PCI 3c595 Vortex 100baseTx at 00018800. | [ 72.772890] 00:a0:24:43:dd:fd, IRQ 11 | [ 72.780517] product code 4255 rev 00.0 date 12-02-95 | [ 72.780527] 64K word-wide RAM 1:1 Rx:Tx split, autoselect/10baseT interface. | [ 72.780533] :00:0b.0: scatter/gather disabled. h/w checksums disabledo | ` and thats all. Dialin to a my ISP works (card is connected to a DSL-Modem), but if there are comes traffic I just done a 'links www.google.de' and everything freezes totally, but I saw , | Refresh [ 76.79933] eth0 vortex_error(), status=0xe091 ` on the terminal at this moment. Booting to my parallel installed Ubuntu, also with kernel 2.6.32, everything is alright. Could I be the only one with this problem, and should I better file a new bug? Jens -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (1000, 'testing'), (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686-bigmem (SMP w/1 CPU core) Locale: lang=de...@euro, lc_ctype=de...@euro (charmap=ISO-8859-15) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100831021224.ga5...@sge.kicks-ass.org
Bug#586967: (no subject)
On Fri, 2010-08-06 at 22:24 +0200, Jens Schüßler wrote: I believe that this changes in 3c59x made my squeeze sytem unusuable since yesterdays upgrade from 2.6.32.5-15 to -18. I use a 3com card with this driver for years, and after booting the new kernel my system completely freezed reproducable after seconds online on the net. Unfortunately I wasn't able to find the deb of -15 anymore, and I got the same problen with another 3com card, so I had to change the network card to a DLink model and now everything workes fine. There were absolutely nothing in the logs, machine feezed completely, no keyboard response, so no SysReq worked, only power button saved me. What is the exact model you have (use lspci -nn -d 10b7:)? Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Bug#586967: (no subject)
On Mon, 2010-08-30 at 20:52 +0100, Ben Hutchings wrote: On Fri, 2010-08-06 at 22:24 +0200, Jens Schüßler wrote: I believe that this changes in 3c59x made my squeeze sytem unusuable since yesterdays upgrade from 2.6.32.5-15 to -18. I use a 3com card with this driver for years, and after booting the new kernel my system completely freezed reproducable after seconds online on the net. Unfortunately I wasn't able to find the deb of -15 anymore, and I got the same problen with another 3com card, so I had to change the network card to a DLink model and now everything workes fine. There were absolutely nothing in the logs, machine feezed completely, no keyboard response, so no SysReq worked, only power button saved me. What is the exact model you have (use lspci -nn -d 10b7:)? Also can you try enabling some debug logging: rmmod 3c59x modprobe 3c59x debug=3 Then run dmesg to get the logged messages, and send them back. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Bug#586967: (no subject)
* Ben Hutchings b...@decadent.org.uk wrote: On Mon, 2010-08-30 at 20:52 +0100, Ben Hutchings wrote: On Fri, 2010-08-06 at 22:24 +0200, Jens Schüßler wrote: I believe that this changes in 3c59x made my squeeze sytem unusuable since yesterdays upgrade from 2.6.32.5-15 to -18. I use a 3com card with this driver for years, and after booting the new kernel my system completely freezed reproducable after seconds online on the net. Unfortunately I wasn't able to find the deb of -15 anymore, and I got the same problen with another 3com card, so I had to change the network card to a DLink model and now everything workes fine. There were absolutely nothing in the logs, machine feezed completely, no keyboard response, so no SysReq worked, only power button saved me. What is the exact model you have (use lspci -nn -d 10b7:)? Also can you try enabling some debug logging: rmmod 3c59x modprobe 3c59x debug=3 Then run dmesg to get the logged messages, and send them back. Okay, I can do this tomorrow, have to change the cards back first. I hope that the debug output occurs in the syslog, as I said, the system freezed complete immediately. Jens -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100830230146.gb7...@sge.kicks-ass.org
Bug#586967: (no subject)
On Fri, 2010-08-06 at 22:24 +0200, Jens Schüßler wrote: I believe that this changes in 3c59x made my squeeze sytem unusuable since yesterdays upgrade from 2.6.32.5-15 to -18. I use a 3com card with this driver for years, and after booting the new kernel my system completely freezed reproducable after seconds online on the net. Unfortunately I wasn't able to find the deb of -15 anymore, and I got the same problen with another 3com card, so I had to change the network card to a DLink model and now everything workes fine. There were absolutely nothing in the logs, machine feezed completely, no keyboard response, so no SysReq worked, only power button saved me. Sorry about this. I'm trying to borrow one of these cards so I can debug this. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Bug#586967: (no subject)
I believe that this changes in 3c59x made my squeeze sytem unusuable since yesterdays upgrade from 2.6.32.5-15 to -18. I use a 3com card with this driver for years, and after booting the new kernel my system completely freezed reproducable after seconds online on the net. Unfortunately I wasn't able to find the deb of -15 anymore, and I got the same problen with another 3com card, so I had to change the network card to a DLink model and now everything workes fine. There were absolutely nothing in the logs, machine feezed completely, no keyboard response, so no SysReq worked, only power button saved me. Regards Jens -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100806202400.ga28...@sge.kicks-ass.org
