From: Kasper Dupont <kasperd@cpvhh.24.jul.2011.kasperd.net>
To: "François 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: Mon, 25 Jul 2011 12:36:44 +0200 [thread overview]
Message-ID: <20110725103643.GA11135@colin.search.kasperd.net> (raw)
In-Reply-To: <20110724201626.GB24418@zoreil.com>
On 24/07/11 22.16, François romieu wrote:
> The Sun, Jul 24, 2011 at 09:58:31PM +0200, Kasper Dupont wrote :
> [...]
> > Any idea how to fix this?
>
> Apply 1519e57fe81c14bb8fa4855579f19264d1ef63b4 as well and
> eventually f60ac8e7ab7cbb413a0131d5665b053f9f386526.
>
> Please send r8169 related lines from dmesg, especially the XID
> one and Cc: netdev.
These are the relevant lines from dmesg:
[ 1.045727] pata_sch 0000:00:1f.1: setting latency timer to 64
[ 1.045946] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
[ 1.046061] r8169 0000:02:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 1.046201] r8169 0000:02:00.0: setting latency timer to 64
[ 1.046257] alloc irq_desc for 24 on node -1
[ 1.046263] alloc kstat_irqs on node -1
[ 1.046284] r8169 0000:02:00.0: irq 24 for MSI/MSI-X
[ 1.048097] eth0: RTL8168c/8111c at 0xf8076000, 00:01:c0:09:a1:25, XID 1c4000c0 IRQ 24
[ 1.051517] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
[ 1.051631] r8169 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[ 1.051764] r8169 0000:03:00.0: setting latency timer to 64
[ 1.051820] alloc irq_desc for 25 on node -1
[ 1.051825] alloc kstat_irqs on node -1
[ 1.051847] r8169 0000:03:00.0: irq 25 for MSI/MSI-X
[ 1.053159] usb 1-7: new high speed USB device using ehci_hcd and address 5
[ 1.056574] vga16fb: initializing
[ 1.056584] vga16fb: mapped to 0xc00a0000
[ 1.056819] fb0: VGA16 VGA frame buffer device
[ 1.070138] scsi0 : pata_sch
[ 1.078253] scsi1 : pata_sch
[ 1.079216] ata1: PATA max UDMA/100 cmd 0x1f0 ctl 0x3f6 bmdma 0x1800 irq 14
[ 1.079312] ata2: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0x1808 irq 15
[ 1.082178] eth1: RTL8168c/8111c at 0xf8096000, 00:01:c0:09:a1:26, XID 1c4000c0 IRQ 25
[ 1.205643] usb 1-7: configuration #1 chosen from 1 choice
It works on 2.6.32.32 it crashes on 2.6.32.33. I tried to
take 2.6.32.43 and apply 1519e57fe81c14bb8fa4855579f19264d1ef63b4,
that did not help. 2.6.32.43 crashes with and without that patch.
--
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);
next parent reply other threads:[~2011-07-25 10:46 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 ` Kasper Dupont [this message]
2011-07-28 7:04 ` r8169 driver crashes in 2.6.32.43 Francois Romieu
2011-07-28 8:48 ` Kasper Dupont
2011-07-28 10:58 ` Francois Romieu
2011-07-28 11:43 ` Kasper Dupont
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=20110725103643.GA11135@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).