From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Jose Angel Martinez Conde <joseangel@taller-id.com>
Cc: RT <linux-rt-users@vger.kernel.org>
Subject: Re: Problem with network on kernel 2.6.29.6-rt23 (Debian)
Date: Tue, 6 Oct 2009 08:41:21 +0200 [thread overview]
Message-ID: <20091006064121.GA22242@pengutronix.de> (raw)
In-Reply-To: <369171892.211254768721569.JavaMail.root@groupware>
Hello,
On Mon, Oct 05, 2009 at 08:52:01PM +0200, Jose Angel Martinez Conde wrote:
>
> Sep 27 13:22:11 tid31 kernel: [ 1905.704018] ------------[ cut here ]------------
> Sep 27 13:22:11 tid31 kernel: [ 1905.704023] WARNING: at net/sched/sch_generic.c:230 dev_watchdog+0x24c/0x260()
> Sep 27 13:22:11 tid31 kernel: [ 1905.704025] Hardware name: System Product Name
> Sep 27 13:22:11 tid31 kernel: [ 1905.704026] NETDEV WATCHDOG: eth1 (e1000): transmit timed out
> Sep 27 13:22:11 tid31 kernel: [ 1905.704027] Modules linked in: nls_utf8 sg sr_mod cdrom usb_storage isofs udf nls_base i2c_dev nvidia(P) ipv6 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 pcspkr soundcore snd_page_alloc i2c_nforce2 evdev 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 crc_itu_t e1000 libata ohci_hcd ehci_hcd scsi_mod thermal processor fan thermal_sys [last unloaded: nvidia]
> Sep 27 13:22:11 tid31 kernel: [ 1905.704074] Pid: 5, comm: sirq-timer/0 Tainted: P 2.6.29.6-rt23 #1
> Sep 27 13:22:11 tid31 kernel: [ 1905.704076] Call Trace:
> Sep 27 13:22:11 tid31 kernel: [ 1905.704081] [<ffffffff8024587a>] ? warn_slowpath+0xea/0x160
> Sep 27 13:22:11 tid31 kernel: [ 1905.704258] [<ffffffffa109cd77>] ? _nv005972rm+0x1f/0x27 [nvidia]
> Sep 27 13:22:11 tid31 kernel: [ 1905.704378] [<ffffffffa105eda4>] ? _nv012325rm+0x3f/0x54 [nvidia]
> Sep 27 13:22:11 tid31 kernel: [ 1905.704490] [<ffffffffa109cd77>] ? _nv005972rm+0x1f/0x27 [nvidia]
> Sep 27 13:22:11 tid31 kernel: [ 1905.704499] [<ffffffff80238bf9>] ? pick_next_highest_task_rt+0xb9/0xe0
> Sep 27 13:22:11 tid31 kernel: [ 1905.704501] [<ffffffff8023a0bf>] ? enqueue_task_rt+0x11f/0x2e0
> Sep 27 13:22:11 tid31 kernel: [ 1905.704504] [<ffffffff8037f9f1>] ? strlcpy+0x41/0x50
> Sep 27 13:22:11 tid31 kernel: [ 1905.704506] [<ffffffff8046712c>] ? dev_watchdog+0x24c/0x260
> Sep 27 13:22:11 tid31 kernel: [ 1905.704508] [<ffffffff80238210>] ? activate_task+0x20/0x30
> Sep 27 13:22:11 tid31 kernel: [ 1905.704511] [<ffffffff80240a16>] ? try_to_wake_up+0x186/0x2b0
> Sep 27 13:22:11 tid31 kernel: [ 1905.704515] [<ffffffff8025044b>] ? cascade+0x7b/0xa0
> Sep 27 13:22:11 tid31 kernel: [ 1905.704517] [<ffffffff80466ee0>] ? dev_watchdog+0x0/0x260
> Sep 27 13:22:11 tid31 kernel: [ 1905.704519] [<ffffffff8025094c>] ? run_timer_softirq+0x1ac/0x2f0
> Sep 27 13:22:11 tid31 kernel: [ 1905.704522] [<ffffffff8024b0aa>] ? ksoftirqd+0x18a/0x300
> Sep 27 13:22:11 tid31 kernel: [ 1905.704524] [<ffffffff8024af20>] ? ksoftirqd+0x0/0x300
> Sep 27 13:22:11 tid31 kernel: [ 1905.704526] [<ffffffff8024af20>] ? ksoftirqd+0x0/0x300
> Sep 27 13:22:11 tid31 kernel: [ 1905.704529] [<ffffffff8025d017>] ? kthread+0x47/0x90
> Sep 27 13:22:11 tid31 kernel: [ 1905.704531] [<ffffffff8020d04a>] ? child_rip+0xa/0x20
> Sep 27 13:22:11 tid31 kernel: [ 1905.704533] [<ffffffff8025cfd0>] ? kthread+0x0/0x90
> Sep 27 13:22:11 tid31 kernel: [ 1905.704535] [<ffffffff8020d040>] ? child_rip+0x0/0x20
> Sep 27 13:22:11 tid31 kernel: [ 1905.704537] ---[ end trace c3aee9954334308d ]---
Can you please reproduce with a non-tainted kernel? I.e. don't load the
nvidia module.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-10-06 6:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1804966706.191254768514851.JavaMail.root@groupware>
2009-10-05 18:52 ` Problem with network on kernel 2.6.29.6-rt23 (Debian) Jose Angel Martinez Conde
2009-10-06 6:41 ` Uwe Kleine-König [this message]
2009-10-06 9:12 ` Jose Angel Martinez Conde
2009-10-06 6:47 ` Hans-Peter Bock
2009-10-06 9:15 ` Uwe Kleine-König
2009-10-06 9:22 ` Jose Angel Martinez Conde
2009-10-06 9:27 ` Hans-Peter Bock
[not found] <1609492146.281254820627823.JavaMail.root@groupware>
2009-10-06 9:18 ` Jose Angel Martinez Conde
[not found] <658461008.621255079453937.JavaMail.root@groupware>
2009-10-09 9:11 ` Jose Angel Martinez Conde
2009-10-09 15:43 ` Thomas Gleixner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20091006064121.GA22242@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=joseangel@taller-id.com \
--cc=linux-rt-users@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.