[Bug 694077] New: after random time NIC crashes with kernel errors
https://bugzilla.novell.com/show_bug.cgi?id=694077 https://bugzilla.novell.com/show_bug.cgi?id=694077#c0 Summary: after random time NIC crashes with kernel errors Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: x86-64 OS/Version: openSUSE 11.4 Status: NEW Severity: Minor Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers@forge.provo.novell.com ReportedBy: jonas.rottmann@web.de QAContact: qa@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.3 (KHTML, like Gecko) Chrome/6.0.472.63 Safari/534.3 My NIC crashed after random time every boot with various kernels I tried, with always similiar Kernel errors: May 9 08:53:26 server kernel: [ 292.704044] ------------[ cut here ]------------ May 9 08:53:26 server kernel: [ 292.704054] WARNING: at /usr/src/packages/BUILD/kernel-desktop-2.6.37.6/linux-2.6.37/net/sched/sch_generic.c:258 dev_watchdog+0x233/0x240() May 9 08:53:26 server kernel: [ 292.704056] Hardware name: System Product Name May 9 08:53:26 server kernel: [ 292.704058] NETDEV WATCHDOG: eth1 (e1000): transmit queue 0 timed out May 9 08:53:26 server kernel: [ 292.704060] Modules linked in: loop ip6t_LOG xt_TCPMSS ipt_MASQUERADE iptable_nat nf_nat ipt_LOG xt_tcpudp xt_limit xt_pkttype af_packet edd ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_raw xt_NOTRACK ipt_REJECT iptable_raw iptable_filter ip6table_mangle nf_conntrack_netbios_ns nf_conntrack_ipv4 nf_defrag_ipv4 ip_tables xt_conntrack nf_conntrack ip6table_filter ip6_tables x_tables cpufreq_conservative snd_pcm_oss cpufreq_userspace cpufreq_powersave snd_mixer_oss acpi_cpufreq mperf snd_seq snd_seq_device dm_mod snd_hda_codec_hdmi ata_generic snd_hda_codec_realtek sg sr_mod r8169 pata_marvell snd_hda_intel cdrom ppdev e1000 iTCO_wdt iTCO_vendor_support i2c_i801 pcspkr shpchp parport_pc pci_hotplug parport snd_hda_codec snd_hwdep snd_pcm snd_timer snd soundcore snd_page_alloc asus_atk0110 serio_raw raid456 async_raid6_recov async_pq raid6_pq async_xor xor async_memcpy async_tx raid10 raid1 raid0 i915 drm_kms_helper drm i2c_algo_bit button video fan thermal processor therma May 9 08:53:26 server kernel: l_sys May 9 08:53:26 server kernel: [ 292.704124] Pid: 0, comm: kworker/0:0 Not tainted 2.6.37.6-0.5-desktop #1 May 9 08:53:26 server kernel: [ 292.704126] Call Trace: May 9 08:53:26 server kernel: [ 292.704138] [<ffffffff810059b9>] dump_trace+0x79/0x340 May 9 08:53:26 server kernel: [ 292.704143] [<ffffffff81521752>] dump_stack+0x69/0x6f May 9 08:53:26 server kernel: [ 292.704149] [<ffffffff8105815b>] warn_slowpath_common+0x7b/0xc0 May 9 08:53:26 server kernel: [ 292.704154] [<ffffffff81058255>] warn_slowpath_fmt+0x45/0x50 May 9 08:53:26 server kernel: [ 292.704158] [<ffffffff81442463>] dev_watchdog+0x233/0x240 May 9 08:53:26 server kernel: [ 292.704164] [<ffffffff8106819e>] call_timer_fn+0x3e/0x190 May 9 08:53:26 server kernel: [ 292.704169] [<ffffffff81068534>] run_timer_softirq+0x144/0x2a0 May 9 08:53:26 server kernel: [ 292.704173] [<ffffffff8105f98a>] __do_softirq+0xda/0x2a0 May 9 08:53:26 server kernel: [ 292.704178] [<ffffffff81003e6c>] call_softirq+0x1c/0x30 May 9 08:53:26 server kernel: [ 292.704182] [<ffffffff8100590d>] do_softirq+0x4d/0x80 May 9 08:53:26 server kernel: [ 292.704186] [<ffffffff8105fc45>] irq_exit+0x95/0xa0 May 9 08:53:26 server kernel: [ 292.704191] [<ffffffff810204fa>] smp_apic_timer_interrupt+0x6a/0xa0 May 9 08:53:26 server kernel: [ 292.704195] [<ffffffff81003933>] apic_timer_interrupt+0x13/0x20 May 9 08:53:26 server kernel: [ 292.704201] [<ffffffff8100bb17>] mwait_idle+0x97/0x290 May 9 08:53:26 server kernel: [ 292.704206] [<ffffffff8100125c>] cpu_idle+0x4c/0xa0 May 9 08:53:26 server kernel: [ 292.704209] ---[ end trace bd81b6d65023f91b ]--- May 9 08:53:29 server kernel: [ 295.419835] e1000: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX Crashed means it was responsive in system ifconfig up and down worked, but couldn't be pinged or ping anything else in the network... I think it was because of dust, I cleaned the chasis and put the NIC out and in again, and didn't got the failures anymore Reproducible: Always Steps to Reproduce: 1. 2. 3. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=694077
https://bugzilla.novell.com/show_bug.cgi?id=694077#c
Jiri Slaby
https://bugzilla.novell.com/show_bug.cgi?id=694077
https://bugzilla.novell.com/show_bug.cgi?id=694077#c1
Heiko Nardmann
https://bugzilla.novell.com/show_bug.cgi?id=694077
https://bugzilla.novell.com/show_bug.cgi?id=694077#c2
Jeff Mahoney
participants (1)
-
bugzilla_noreply＠novell.com