Bug#514131: [linux-image-2.6.26-1-686]: network card 3ccfem656b (3c59x.ko) doesn't work
On Sun, 2010-04-04 at 10:12 +0200, Klaus Klein wrote: > I guess it's now on me to apologize for a late response. ;-) > > I today installed and tested 2.6.32 and the problem seems not to exist with > this version. > > Unfortunately not all installed software works with this kernel as it comes > out of the box (e.g. NFS, nVidia, etc.) > > Is there a chance to get a fix for 2.6.26 ? I looked through the changes to the driver and the PCMCIA/CardBus code between 2.6.26 and 2.6.27 (as you said this was also fixed in Ubuntu's 2.6.27) and cannot see any changes that look like they could have fixed this. I also looked through driver changes between 2.6.18 and 2.6.26 and did not see anything that looked like it could have caused the bug. If we cannot identify a specific change that fixes this then there is no way we can fix 2.6.26. If you're comfortable with rebuilding the kernel and have the time to spare, you could try to identify at what point the driver broke between 2.6.18 and 2.6.26, using git's bisect facility: sudo apt-get install git-core (read the git-bisect manual page) git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git cd linux-2.6 git bisect start v2.6.26 v2.6.18 cp /boot/config-2.6.26-2-686 .config make oldconfig signature.asc Description: This is a digitally signed message part
Bug#514131: [linux-image-2.6.26-1-686]: network card 3ccfem656b (3c59x.ko) doesn't work
I guess it's now on me to apologize for a late response. ;-) I today installed and tested 2.6.32 and the problem seems not to exist with this version. Unfortunately not all installed software works with this kernel as it comes out of the box (e.g. NFS, nVidia, etc.) Is there a chance to get a fix for 2.6.26 ? Regards, Klaus Moritz Muehlenhoff wrote: > The next release of Debian (6.0, code name Squeeze) will be based on 2.6.32. Please test the current 2.6.32 from unstable/testing and tell us whether the problem persists. If so, we should report it upstream to the kernel.org developers. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#514131: [linux-image-2.6.26-1-686]: network card 3ccfem656b (3c59x.ko) doesn't work
On Wed, Feb 04, 2009 at 05:46:37PM +0100, Klaus Klein wrote: > Package: linux-image-2.6.26-1-686 > Version: 2.6.26-12 > > Environment: - Dell Latitude 8100 > - 3Com 3CCFEM656B > - Debian 2.6 (Lenny) > > After inserting the network card (3CCFEM656B) the module 3c59x.ko is loaded. > > Nevertheless, the following entries in /var/log/syslog appear: Sorry for the late response :-/ The next release of Debian (6.0, code name Squeeze) will be based on 2.6.32. Please test the current 2.6.32 from unstable/testing and tell us whether the problem persists. If so, we should report it upstream to the kernel.org developers. The 2.6.32 kernel is available from packages.debian.org and can be installed in both Debian stable, testing and unstable installations. Thanks, Moritz -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#514131: [linux-image-2.6.26-1-686]: network card 3ccfem656b (3c59x.ko) doesn't work
Package: linux-image-2.6.26-1-686 Version: 2.6.26-12 Environment: - Dell Latitude 8100 - 3Com 3CCFEM656B - Debian 2.6 (Lenny) After inserting the network card (3CCFEM656B) the module 3c59x.ko is loaded. Nevertheless, the following entries in /var/log/syslog appear: Feb 4 17:09:24 p933 last message repeated 2 times Feb 4 17:09:26 p933 kernel: [ 3213.560057] pccard: CardBus card inserted into slot 0 Feb 4 17:09:27 p933 kernel: [ 3214.515283] 3c59x :09:00.0: enabling device ( -> 0003) Feb 4 17:09:27 p933 kernel: [ 3214.515313] ACPI: PCI Interrupt :09:00.0[A] -> Link [LNKD] -> GSI 10 (level, low) -> IRQ 10 Feb 4 17:09:27 p933 kernel: [ 3214.515338] 3c59x: Donald Becker and others. Feb 4 17:09:27 p933 kernel: [ 3214.515351] :09:00.0: 3Com PCI 3CCFEM656B Cyclone+Winmodem CardBus at e0ad6000. Feb 4 17:09:27 p933 kernel: [ 3214.515367] PCI: Setting latency timer of device :09:00.0 to 64 Feb 4 17:09:27 p933 kernel: [ 3214.525943] ***INVALID CHECKSUM 0094*** <6>eth1: setting half-duplex. Feb 4 17:09:27 p933 avahi-daemon[2423]: Joining mDNS multicast group on interface eth1.IPv4 with address 192.168.20.69. Feb 4 17:09:27 p933 avahi-daemon[2423]: New relevant interface eth1.IPv4 for mDNS. Feb 4 17:09:27 p933 avahi-daemon[2423]: Registering new address record for 192.168.20.69 on eth1.IPv4. Feb 4 17:09:27 p933 modprobe: WARNING: Not loading blacklisted module ipv6 Feb 4 17:09:28 p933 last message repeated 2 times Feb 4 17:10:05 p933 kernel: [ 3252.748965] eth1: setting full-duplex. Feb 4 17:11:16 p933 kernel: [ 3322.592054] irq 10: nobody cared (try booting with the "irqpoll" option) Feb 4 17:11:16 p933 kernel: [ 3322.592054] Pid: 0, comm: swapper Tainted: P 2.6.26-1-686 #1 Feb 4 17:11:16 p933 kernel: [ 3322.592054] [] __report_bad_irq+0x24/0x69 Feb 4 17:11:16 p933 kernel: [ 3322.592054] [] __report_bad_irq+0x2b/0x69 Feb 4 17:11:16 p933 kernel: [ 3322.592054] [] note_interrupt+0x1d4/0x208 Feb 4 17:11:16 p933 kernel: [ 3322.592054] [] handle_IRQ_event+0x23/0x51 Feb 4 17:11:16 p933 kernel: [ 3322.592054] [] handle_level_irq+0x87/0xb6 Feb 4 17:11:16 p933 kernel: [ 3322.592054] [] do_IRQ+0x4d/0x63 Feb 4 17:11:16 p933 kernel: [ 3322.592054] [] common_interrupt+0x23/0x28 Feb 4 17:11:16 p933 kernel: [ 3322.592054] [] __do_softirq+0x57/0xd3 Feb 4 17:11:16 p933 kernel: [ 3322.592054] [] do_softirq+0x45/0x53 Feb 4 17:11:16 p933 kernel: [ 3322.592054] [] irq_exit+0x35/0x67 Feb 4 17:11:16 p933 kernel: [ 3322.592054] [] do_IRQ+0x52/0x63 Feb 4 17:11:16 p933 kernel: [ 3322.592054] [] common_interrupt+0x23/0x28 Feb 4 17:11:16 p933 kernel: [ 3322.592054] [] param_set_charp+0x8/0x48 Feb 4 17:11:16 p933 kernel: [ 3322.592054] [] acpi_idle_enter_simple+0x196/0x203 [processor] Feb 4 17:11:16 p933 kernel: [ 3322.592054] [] cpuidle_idle_call+0x5b/0x86 Feb 4 17:11:16 p933 kernel: [ 3322.592054] [] cpuidle_idle_call+0x0/0x86 Feb 4 17:11:16 p933 kernel: [ 3322.592054] [] cpu_idle+0xab/0xcb Feb 4 17:11:16 p933 kernel: [ 3322.592054] === Feb 4 17:11:16 p933 kernel: [ 3322.592054] handlers: Feb 4 17:11:16 p933 kernel: [ 3322.592054] [] (usb_hcd_irq+0x0/0x73 [usbcore]) Feb 4 17:11:16 p933 kernel: [ 3322.592054] [] (ohci_irq_handler+0x0/0x6be [ohci1394]) Feb 4 17:11:16 p933 kernel: [ 3322.592054] [] (yenta_interrupt+0x0/0xb3 [yenta_socket]) Feb 4 17:11:16 p933 kernel: [ 3322.592054] [] (yenta_interrupt+0x0/0xb3 [yenta_socket]) Feb 4 17:11:16 p933 kernel: [ 3322.592054] [] (e100_intr+0x0/0x85 [e100]) Feb 4 17:11:16 p933 kernel: [ 3322.592054] [] (vortex_interrupt+0x0/0x2a8 [3c59x]) Feb 4 17:11:16 p933 kernel: [ 3322.592054] Disabling IRQ #10 Also, while the real mac address starts with 00:50:DA:... the mac address reported by udev and ifconfig is usually one out of the following: 00:0a:00:50:16:3f 00:0a:00:50:2c:7f 00:14:00:50:16:3f 00:14:00:50:2c:7f 00:09:76:ab:da:ad (only seen once) The according interface looks ok (e.g. ifconfig eth1) but an attempt to ping a node on the network will either result in a system lookup or the appearance of the following entries in /var/log/syslog: Feb 4 17:15:11 p933 kernel: [ 3559.31] NETDEV WATCHDOG: eth1: transmit timed out Feb 4 17:15:11 p933 kernel: [ 3559.51] eth1: transmit timed out, tx_status 00 status 0604. Feb 4 17:15:11 p933 kernel: [ 3559.65] diagnostics: net media 0003 dma fifo Feb 4 17:15:11 p933 kernel: [ 3559.91] [ cut here ] Feb 4 17:15:11 p933 kernel: [ 3559.99] WARNING: at net/sched/sch_generic.c:222 dev_watchdog+0x8f/0xdc() Feb 4 17:15:11 p933 kernel: [ 3559.000106] Modules linked in: 3c59x nvidia(P) i2c_core rfcomm l2cap bluetooth ppdev lp speedstep_smi speedstep_lib cpufreq_userspace cpufreq_stats cpufreq_powersave cpufreq_ondemand freq_table cpufreq_conservative nfsd auth_rpcgss exportfs nfs lockd nfs_acl sunrpc ext2 dm_snapshot dm_mirror dm_log dm_mod ide_generic
