netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kasper Dupont <kasperd@cpvhh.24.jul.2011.kasperd.net>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: ivecera@redhat.com, hayeswang@realtek.com, gregkh@suse.de,
	netdev@vger.kernel.org
Subject: Re: r8169 driver crashes in 2.6.32.43
Date: Thu, 28 Jul 2011 13:43:05 +0200	[thread overview]
Message-ID: <20110728114305.GA24549@colin.search.kasperd.net> (raw)
In-Reply-To: <20110728105831.GA11385@electric-eye.fr.zoreil.com>

On 28/07/11 12.58, Francois Romieu wrote:
> Kasper Dupont <kasperd@cpvhh.24.jul.2011.kasperd.net> :
> [...]
> > I tried to apply both 1519e57fe81c14bb8fa4855579f19264d1ef63b4
> > and f60ac8e7ab7cbb413a0131d5665b053f9f386526. It still crashes,
> > the first two times I booted that exact build it printed out a
> > stackdump just before crashing. I have pictures of the two
> > stack dumps in case that is any help, but unfortunately they
> > were too deep to fit on 25 lines.
> 
> It will probably not help but I can hardly tell without seeing them. :o)
> It will be ok if you publish them somewhere.

http://kasperd.net/~kasperd/r8169/

> 
> Does something prevent you to enable a different video mode ?

I got some problems with getting the video drivers to behave
properly. I managed to get X to use the correct screen
resolution, but I haven't figured out to get the text console
to do so.

Netconsole over the network interface we are trying to debug
probably isn't the way to go. Do you think it would be feasible
to run netconsole over wifi?

> 
> [...]
> > I tried applying this one as well (in addition to the previous
> > two). It no longer crashes, but now the network stops working
> > after the first few packets have been transmitted.
> 
> Thanks for testing.
> 
> > What exactly was 649f25c389e9498923b459bbffff41a2fd1d7a64
> > trying to fix in the first place?
> >
> > Before that patch the network on this machine was running fast and stable.
> 
> It's frustrating.
> 
> Either the hardware did not experience Rx FIFO overflow internally or it
> was able to recover from it without driver intervention. Ivan's hardware
> seems to behave differently so blindly revert 
> 649f25c389e9498923b459bbffff41a2fd1d7a64 is not an option.
> 
> Can you add the crap below on top of the pre "no longer crashes, no network"
> one (it will work on top of plain -git driver as well) ?

I'll give it a try.

-- 
Kasper Dupont -- Rigtige mænd skriver deres egne backupprogrammer
#define _(_)"d.%.4s%."_"2s" /* This is my email address */
char*_="@2kaspner"_()"%03"_("4s%.")"t\n";printf(_+11,_+6,_,11,_+2,_+7,_+6);

  reply	other threads:[~2011-07-28 11:43 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20110724195831.GA8718@colin.search.kasperd.net>
     [not found] ` <20110724201626.GB24418@zoreil.com>
2011-07-25 10:36   ` r8169 driver crashes in 2.6.32.43 Kasper Dupont
2011-07-28  7:04     ` Francois Romieu
2011-07-28  8:48       ` Kasper Dupont
2011-07-28 10:58         ` Francois Romieu
2011-07-28 11:43           ` Kasper Dupont [this message]
2011-07-28 11:59             ` Kasper Dupont
2011-07-28 12:23               ` Francois Romieu
2011-07-28 12:45                 ` Kasper Dupont
2011-07-28 12:54                   ` Kasper Dupont
2011-07-28 14:47                     ` Francois Romieu
2011-07-28 21:01                       ` Kasper Dupont
2011-08-05 14:08                         ` Kasper Dupont
2011-08-05 14:40                           ` Kasper Dupont

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=20110728114305.GA24549@colin.search.kasperd.net \
    --to=kasperd@cpvhh.24.jul.2011.kasperd.net \
    --cc=gregkh@suse.de \
    --cc=hayeswang@realtek.com \
    --cc=ivecera@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=romieu@fr.zoreil.com \
    /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).