All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Goldner <robert@au-79.de>
To: Eric Dumazet <eric.dumazet@gmail.com>, linux-kernel@vger.kernel.org
Cc: netdev@vger.kernel.org
Subject: Re: Ooops with 2.6.39
Date: Mon, 30 May 2011 06:50:38 +0200	[thread overview]
Message-ID: <4DE3221E.40508@au-79.de> (raw)
In-Reply-To: <1306722856.30021.28.camel@edumazet-laptop>



Am 30.05.2011 04:34, schrieb Eric Dumazet:
> Le dimanche 29 mai 2011 à 15:45 -0700, Andrew Morton a écrit :
>> (cc netdev)
>>
>> On Sun, 29 May 2011 07:56:35 +0200 Robert Goldner <robert@au-79.de> wrote:
> 
>>> Hi,
>>>
>>> sometimes I got an Ooops while the system is starting:
>>>
>>> [   15.824365] ------------[ cut here ]------------
>>> [   15.824616] WARNING: at net/sched/sch_generic.c:256
>>> dev_watchdog+0x1d6/0x1e0()
>>> [   15.824868] Hardware name:
>>> [   15.825098] NETDEV WATCHDOG: eth0 (sis900): transmit queue 0 timed out
>>> [   15.825333] Modules linked in: coretemp qt1010 af9013 dvb_pll mt2060
>>> dvb_usb_nova_t_usb2 dvb_usb_dibusb_common dib3000mc psmouse
>>> dibx000_common pcspkr dvb_usb_af9015 ohci_hcd
>>> [   15.829066] Pid: 1462, comm: startpar Not tainted 2.6.39-agathe #2
>>> [   15.829301] Call Trace:
>>> [   15.829534]  [<c103c79d>] warn_slowpath_common+0x6d/0xa0
>>> [   15.829948]  [<c13ff216>] ? dev_watchdog+0x1d6/0x1e0
>>> [   15.830183]  [<c13ff216>] ? dev_watchdog+0x1d6/0x1e0
>>> [   15.830417]  [<c103c84e>] warn_slowpath_fmt+0x2e/0x30
>>> [   15.830828]  [<c13ff216>] dev_watchdog+0x1d6/0x1e0
>>> [   15.831241]  [<c104ecc8>] ? __queue_work+0xb8/0x300
>>> [   15.831476]  [<c10048a8>] ? handle_irq+0x18/0x90
>>> [   15.831889]  [<c1041bc7>] ? irq_exit+0x37/0x80
>>> [   15.832127]  [<c10044f6>] ? do_IRQ+0x46/0xb0
>>> [   15.832541]  [<c1080189>] ? rcu_start_gp+0x149/0x1d0
>>> [   15.832954]  [<c1046a24>] run_timer_softirq+0xe4/0x200
>>> [   15.833189]  [<c1041900>] ? local_bh_enable+0x80/0x80
>>> [   15.833426]  [<c151ade9>] ? common_interrupt+0x29/0x30
>>> [   15.833838]  [<c13ff040>] ? qdisc_reset+0x40/0x40
>>> [   15.834250]  [<c1041978>] __do_softirq+0x78/0x100
>>> [   15.834841]  [<c1041900>] ? local_bh_enable+0x80/0x80
>>> [   15.835097]  <IRQ>  [<c1041bfe>] ? irq_exit+0x6e/0x80
>>> [   15.835188]  [<c1019dc6>] ? smp_apic_timer_interrupt+0x56/0x90
>>> [   15.835247]  [<c151a46a>] ? apic_timer_interrupt+0x2a/0x30
>>> [   15.835305]  [<c151a168>] ? resume_userspace+0x14/0x14
>>> [   15.835360] ---[ end trace 519c5412e162986a ]---
>>>
>>>
>>> The level of pain is very low, because the system is still running very
>>> well.
>>>
>>> If somebody needs some more information, please let me know.
>>>
>>
>> Which net device driver is being used?
> 
> Seems to be sis900
> 
> Maybe its TX_TIMEOUT is too low.
> 
> Robert, is your NIC in full or half duplex mode ?
> 
> 
> 

Hello Eric,

the device runs in full duplex mode (as far as I see)

root@agathe:~# ethtool eth0
Settings for eth0:
        Supported ports: [ TP MII ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
        Supports auto-negotiation: Yes
        Advertised link modes:  10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
        Advertised pause frame use: No
        Advertised auto-negotiation: Yes
        Link partner advertised link modes:10baseT/Half 10baseT/Full
                                           100baseT/Half 100baseT/Full
        Link partner advertised pause frame use: Symmetric
        Link partner advertised auto-negotiation: Yes
        Speed: 100Mb/s
        Duplex: Full
        Port: MII
        PHYAD: 1
        Transceiver: internal
        Auto-negotiation: on
        Supports Wake-on: pg
        Wake-on: g
        Current message level: 0x000000c5 (197)
        Link detected: yes


Yes, it's an sis900, lspci:

00:00.0 Host bridge: Silicon Integrated Systems [SiS] 662 Host (rev 01)
00:01.0 PCI bridge: Silicon Integrated Systems [SiS] SiS AGP Port
(virtual PCI-to-PCI bridge)
00:02.0 ISA bridge: Silicon Integrated Systems [SiS] SiS964 [MuTIOL
Media IO] (rev 36)
00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] (rev 01)
00:02.7 Multimedia audio controller: Silicon Integrated Systems [SiS]
AC'97 Sound Controller (rev a0)
00:03.0 USB Controller: Silicon Integrated Systems [SiS] USB 1.1
Controller (rev 0f)
00:03.1 USB Controller: Silicon Integrated Systems [SiS] USB 1.1
Controller (rev 0f)
00:03.2 USB Controller: Silicon Integrated Systems [SiS] USB 1.1
Controller (rev 0f)
00:03.3 USB Controller: Silicon Integrated Systems [SiS] USB 2.0 Controller
00:04.0 Ethernet controller: Silicon Integrated Systems [SiS] SiS900 PCI
Fast Ethernet (rev 91)
00:05.0 IDE interface: Silicon Integrated Systems [SiS] SATA (rev 01)
00:1f.0 PCI bridge: Silicon Integrated Systems [SiS] PCI-to-PCI bridge
01:00.0 VGA compatible controller: Silicon Integrated Systems [SiS]
661/741/760 PCI/AGP or 662/761Gx PCIE VGA Display Adapter (rev 04)

      reply	other threads:[~2011-05-30  4:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-29  5:56 Ooops with 2.6.39 Robert Goldner
2011-05-29 22:45 ` Andrew Morton
2011-05-30  2:34   ` Eric Dumazet
2011-05-30  4:50     ` Robert Goldner [this message]

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=4DE3221E.40508@au-79.de \
    --to=robert@au-79.de \
    --cc=eric.dumazet@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@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.