All of lore.kernel.org
 help / color / mirror / Atom feed
From: Francois Romieu <romieu@fr.zoreil.com>
To: "Alex Villacís Lasso" <a_villacis@palosanto.com>
Cc: netdev@vger.kernel.org
Subject: Re: REGRESSION: 3.4.0->3.5.0-rc2 kernel WARNING on cable plug on Acer Aspire One, no network
Date: Mon, 11 Jun 2012 23:38:15 +0200	[thread overview]
Message-ID: <20120611213815.GA8517@electric-eye.fr.zoreil.com> (raw)
In-Reply-To: <4FD504DA.3000500@palosanto.com>

Alex Villacís Lasso <a_villacis@palosanto.com> :
[...]
> $ grep XID dmesg-3.5.0-rc2.txt
> [   15.873858] r8169 0000:02:00.0: eth0: RTL8102e at 0xf7c0e000,
> 00:1e:68:e5:5d:b1, XID 04a00000 IRQ 44

The 8102e has not been touched by that many suspect patches but I do
not see where the problem is :o(

Can you peel off the r8169 patches between 3.4.0 and 3.5-rc ?

-- 
Ueimor

  reply	other threads:[~2012-06-11 21:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-10 19:16 REGRESSION: 3.4.0->3.5.0-rc2 kernel WARNING on cable plug on Acer Aspire One, no network Alex Villacís Lasso
2012-06-10 19:59 ` Francois Romieu
2012-06-10 20:34   ` Alex Villacís Lasso
2012-06-11 21:38     ` Francois Romieu [this message]
2012-07-01 13:50       ` Alex Villacís Lasso
2012-07-03  2:33         ` BISECTED: " Alex Villacís Lasso
     [not found]           ` <4FF25CC2.3050101@palosanto.com>
     [not found]             ` <03be01cd58de$6c2a06d0$447e1470$%szyprowski@samsung.com>
     [not found]               ` <4FF30129.5000702@palosanto.com>
     [not found]                 ` <000901cd59b2$f2a542e0$d7efc8a0$%szyprowski@samsung.com>
2012-07-05  4:14                   ` Alex Villacís Lasso
2012-07-05  6:58                     ` Marek Szyprowski
2012-07-06  0:35                       ` Alex Villacís Lasso
2012-07-08 17:14                       ` Alex Villacís Lasso

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=20120611213815.GA8517@electric-eye.fr.zoreil.com \
    --to=romieu@fr.zoreil.com \
    --cc=a_villacis@palosanto.com \
    --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.