netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@osdl.org>
To: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
Cc: maximilian attems <maks@sternwelten.at>,
	396185@bugs.debian.org, netdev@vger.kernel.org
Subject: Re: Bug#396185: sky2 freezes in 2.6.17-2-686. Maintainer confirms that it should be fixed in 2.6.19-git tree.
Date: Thu, 16 Nov 2006 09:38:21 -0800	[thread overview]
Message-ID: <20061116093821.318efbe6@freekitty> (raw)
In-Reply-To: <20061116173532.GA10653@2ka.mipt.ru>

On Thu, 16 Nov 2006 20:35:32 +0300
Evgeniy Polyakov <johnpol@2ka.mipt.ru> wrote:

> On Tue, Oct 31, 2006 at 12:44:25PM +0300, Evgeniy Polyakov (johnpol@2ka.mipt.ru) wrote:
> > > > > > Bug was filled against 2.6.17-9, but was fixed in recent git (2.6.19-rc3), probably also
> > > > > > fixed in 2.6.18.1
> > > > > > 
> > > > > > Here is link to discussion:
> > > > > > http://marc.theaimsgroup.com/?l=linux-netdev&m=116227512815783&w=2
> > > > > > 
> > > > > 
> > > > > can you try the linux-image 2.6.18, they are in unstable
> > > > > and the etch release images.
> 
> 2.6.18-1-686 kernel still allows to freeze sky2.

Fix didn't go in until 2.6.18.2

> There is nothing in dmesg and card just stops transmitting and
> receiving.
> rmmod/modproble helps in this situation though, so it is probably 
> not 100% the same bug as described in above link.
> 
> It looks like it happens when device is in promiscuous mode some traffic
> is started, at least I did not see such freezes when device operates in 
> usual mode, but it can be unrelated though.
> 
> I would say it is 100% reproducible, but only in current state - I do
> not know what will happen when I reboot. With tcpdump -n host 224.0.0.123
> and scp of the big file from sky2 to via_rhine 100mbit I'm able to
> reproduce that bug 100%, without tcpdump it seems to work correct.
> 
> Here is rmmod/modprobe dmesg:
> 
> ACPI: PCI interrupt for device 0000:05:00.0 disabled
> PCI: Enabling device 0000:05:00.0 (0000 -> 0003)
> ACPI: PCI Interrupt 0000:05:00.0[A] -> Link [LNKD] -> GSI 17 (level,low) -> IRQ 106
> PCI: Setting latency timer of device 0000:05:00.0 to 64
> sky2 v1.5 addr 0xfbefc000 irq 106 Yukon-EC (0xb6) rev 2
> sky2 eth0: addr 00:17:31:9a:e5:be
> sky2 eth0: enabling interface
> ADDRCONF(NETDEV_UP): eth0: link is not ready
> sky2 eth0: Link is up at 1000 Mbps, full duplex, flow control both
> ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
> eth0: no IPv6 routers present
> 
> Here is line from /proc/interrupts when device was frozen again:
> 114:    3257078          0         PCI-MSI  sky2
> 
> Above number does not change when card is frozen and starts increasing
> after rmmod/modprobe.
> 
> Attached statistic and register dumps for working and frozen states.
> 

Please retest with 2.76.18.2 or 2.6.19-rc6, there were some fixes
already there.

-- 
Stephen Hemminger <shemminger@osdl.org>

       reply	other threads:[~2006-11-16 17:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20061031073030.6658.11274.reportbug@kano.factory.vocord.ru>
     [not found] ` <20061031085716.GW13178@baikonur.stro.at>
     [not found]   ` <20061031093051.GA3323@2ka.mipt.ru>
     [not found]     ` <20061031093455.GX13178@baikonur.stro.at>
     [not found]       ` <20061031094424.GA19052@2ka.mipt.ru>
     [not found]         ` <20061116173532.GA10653@2ka.mipt.ru>
2006-11-16 17:38           ` Stephen Hemminger [this message]
2006-11-16 17:48             ` Bug#396185: sky2 freezes in 2.6.17-2-686. Maintainer confirms that it should be fixed in 2.6.19-git tree Evgeniy Polyakov
2006-11-18 11:21             ` maximilian attems
2006-11-18 11:25               ` Evgeniy Polyakov
2006-11-29  5:29                 ` Evgeniy Polyakov
2006-12-17 14:15                   ` Evgeniy Polyakov
2006-12-18 17:17                     ` Stephen Hemminger
2006-12-19  5:38                       ` Evgeniy Polyakov

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=20061116093821.318efbe6@freekitty \
    --to=shemminger@osdl.org \
    --cc=396185@bugs.debian.org \
    --cc=johnpol@2ka.mipt.ru \
    --cc=maks@sternwelten.at \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).