Problem with network on kernel 2.6.29.6-rt23 (Debian)

Hi Uwe,

we don't reproduce the error with a non-tainted kernel.

We have three computers (same configuration), one with non-tainted kernel and others with tainted kernel (nvidia module). One this get the next error,

Oct  8 21:47:50 tid31 kernel: [38901.704013] ------------[ cut here ]------------
Oct  8 21:47:50 tid31 kernel: [38901.704016] WARNING: at net/sched/sch_generic.c:230 dev_watchdog+0x24c/0x260()
Oct  8 21:47:50 tid31 kernel: [38901.704018] Hardware name: System Product Name
Oct  8 21:47:50 tid31 kernel: [38901.704020] NETDEV WATCHDOG: eth0 (e1000): transmit timed out
Oct  8 21:47:50 tid31 kernel: [38901.704021] Modules linked in: nls_utf8 cifs nls_base nvidia(P) vboxnetadp vboxnetflt vboxdrv autofs4 ipv6 ext4 jbd2 crc16 coretemp it87 hwmon_vid firewire_sbp2 loop snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep snd_pcm_oss snd_mixer_oss snd_pcm snd_seq_dummy snd_seq_oss snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_timer snd_seq_device snd soundcore snd_page_alloc pcspkr evdev i2c_nforce2 i2c_core button ext3 jbd mbcache sd_mod crc_t10dif ide_gd_mod ide_pci_generic amd74xx ide_core usbhid hid firewire_ohci firewire_core sata_nv ahci ata_generic forcedeth crc_itu_t e1000 libata ehci_hcd ohci_hcd scsi_mod thermal processor fan thermal_sys [last unloaded: scsi_wait_scan]
Oct  8 21:47:50 tid31 kernel: [38901.704066] Pid: 5, comm: sirq-timer/0 Tainted: P           2.6.29.6-rt23 #3
Oct  8 21:47:50 tid31 kernel: [38901.704068] Call Trace:
Oct  8 21:47:50 tid31 kernel: [38901.704073]  [<ffffffff8024569a>] ? warn_slowpath+0xea/0x160
Oct  8 21:47:50 tid31 kernel: [38901.704076]  [<ffffffff8047a000>] ? ip_reply_glue_bits+0x50/0x60
Oct  8 21:47:50 tid31 kernel: [38901.704078]  [<ffffffff8047acfa>] ? ip_push_pending_frames+0x3ca/0x490
Oct  8 21:47:50 tid31 kernel: [38901.704081]  [<ffffffff8045568a>] ? __neigh_event_send+0x5a/0x230
Oct  8 21:47:50 tid31 kernel: [38901.704083]  [<ffffffff80457524>] ? neigh_resolve_output+0x1c4/0x360
Oct  8 21:47:50 tid31 kernel: [38901.704085]  [<ffffffff8047b266>] ? ip_queue_xmit+0x246/0x470
Oct  8 21:47:50 tid31 kernel: [38901.704088]  [<ffffffff80475e6e>] ? ip_route_output_flow+0x7e/0x2d0
Oct  8 21:47:50 tid31 kernel: [38901.704090]  [<ffffffff80238d39>] ? pick_next_highest_task_rt+0xb9/0xe0
Oct  8 21:47:50 tid31 kernel: [38901.704093]  [<ffffffff8023a20d>] ? enqueue_task_rt+0x11d/0x2e0
Oct  8 21:47:50 tid31 kernel: [38901.704096]  [<ffffffff802a61b5>] ? perf_counter_task_sched_in+0x65/0x210
Oct  8 21:47:50 tid31 kernel: [38901.704099]  [<ffffffff8037dab1>] ? strlcpy+0x41/0x50
Oct  8 21:47:50 tid31 kernel: [38901.704101]  [<ffffffff8046348c>] ? dev_watchdog+0x24c/0x260
Oct  8 21:47:50 tid31 kernel: [38901.704104]  [<ffffffff804d4d96>] ? thread_return+0x3c/0x6e6
Oct  8 21:47:50 tid31 kernel: [38901.704106]  [<ffffffff80463240>] ? dev_watchdog+0x0/0x260
Oct  8 21:47:50 tid31 kernel: [38901.704109]  [<ffffffff8025058c>] ? run_timer_softirq+0x1ac/0x2f0
Oct  8 21:47:50 tid31 kernel: [38901.704111]  [<ffffffff8024acea>] ? ksoftirqd+0x18a/0x300
Oct  8 21:47:50 tid31 kernel: [38901.704113]  [<ffffffff8024ab60>] ? ksoftirqd+0x0/0x300
Oct  8 21:47:50 tid31 kernel: [38901.704116]  [<ffffffff8024ab60>] ? ksoftirqd+0x0/0x300
Oct  8 21:47:50 tid31 kernel: [38901.704118]  [<ffffffff8025cc17>] ? kthread+0x47/0x90
Oct  8 21:47:50 tid31 kernel: [38901.704121]  [<ffffffff8020d04a>] ? child_rip+0xa/0x20
Oct  8 21:47:50 tid31 kernel: [38901.704123]  [<ffffffff8025cbd0>] ? kthread+0x0/0x90
Oct  8 21:47:50 tid31 kernel: [38901.704125]  [<ffffffff8020d040>] ? child_rip+0x0/0x20
Oct  8 21:47:50 tid31 kernel: [38901.704126] ---[ end trace 8cd1cec32dafbb04 ]---

We come back to 2.6.29.5-rt22.

Thanks.

Regards,

--
jose angel

--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

There is nothing we can do about that. You need to talk to the nvidia folks.

Thanks,

tglx