public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: "Alex Villacís Lasso" <a_villacis@palosanto.com>
To: Marek Szyprowski <m.szyprowski@samsung.com>,
	Francois Romieu <romieu@fr.zoreil.com>,
	netdev@vger.kernel.org
Subject: Re: BISECTED: Re: REGRESSION: 3.4.0->3.5.0-rc2 kernel WARNING on cable plug on Acer Aspire One, no network
Date: Wed, 04 Jul 2012 23:14:42 -0500	[thread overview]
Message-ID: <4FF514B2.4050000@palosanto.com> (raw)
In-Reply-To: <000901cd59b2$f2a542e0$d7efc8a0$%szyprowski@samsung.com>

El 04/07/12 02:02, Marek Szyprowski escribió:
> Hello,
>
> On Tuesday, July 03, 2012 4:27 PM Alex Villací¬s Lasso wrote:
>
>> El 03/07/12 00:40, Marek Szyprowski escribió:
>>> Hi Alex,
>>>
>>> On Tuesday, July 03, 2012 4:45 AM Alex Villacís Lasso wrote:
>>>
>>>> -------- Mensaje original --------
>>>> Asunto:  BISECTED: Re: REGRESSION: 3.4.0->3.5.0-rc2 kernel WARNING on cable
>>>> plug on Acer Aspire One, no network Fecha:  Mon, 02 Jul 2012 21:33:41 -0500 De:
>>>>    Alex Villacís Lasso <a_villacis@palosanto.com> Para:  Francois Romieu
>>>> <romieu@fr.zoreil.com> CC:  netdev@vger.kernel.org
>>>> El 01/07/12 08:50, Alex Villacís Lasso escribió:
>>>>> El 11/06/12 16:38, Francois Romieu escribió:
>>>>>> 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 ?
>>>>>>
>>>>> Still present in 3.5-rc5. Bisection still in progress.
>>>>>
>>>>> --
>>>>> To unsubscribe from this list: send the line "unsubscribe netdev" in
>>>>> the body of a message to majordomo@vger.kernel.org
>>>>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>>> My full bisection points to this commit:
>>>>
>>>> commit 0a2b9a6ea93650b8a00f9fd5ee8fdd25671e2df6
>>>> Author: Marek Szyprowski <m.szyprowski@samsung.com>
>>>> Date:   Thu Dec 29 13:09:51 2011 +0100
>>>>
>>>>       X86: integrate CMA with DMA-mapping subsystem
>>>>
>>>>       This patch adds support for CMA to dma-mapping subsystem for x86
>>>>       architecture that uses common pci-dma/pci-nommu implementation. This
>>>>       allows to test CMA on KVM/QEMU and a lot of common x86 boxes.
>>>>
>>>>       Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
>>>>       Signed-off-by: Kyungmin Park <kyungmin.park@samsung.com>
>>>>       CC: Michal Nazarewicz <mina86@mina86.com>
>>>>       Acked-by: Arnd Bergmann <arnd@arndb.de>
>>>>
>>>> Is this commit somehow messing with the network card DMA?
>>> This commit in fact touches DMA-mapping subsystem and introduces a bug,
>>> which has been finally fixed by commit c080e26edc3a2a3 merged to v3.5-rc3.
>>> After applying it the DMA-mapping subsystem should work exactly the same was
>>> as in v3.4. Could you please check if it fixes this issue?
>>>
>>> Best regards
>> No. It still fails in 3.5-rc5, as mentioned before.
> Hmm. I was a bit confused, because both the subject and git bisect log pointed to v3.5-rc2,
> which had that bug. Maybe there is one some other issue present in v3.5-rc5 not related to
> my patches?
>
> Could you check with v3.5-rc5 if reverting patch c080e26edc3a2a3cdfa4c430c663ee1c3bbd8fae
> and 0a2b9a6ea93650b8a00f9fd5ee8fdd25671e2df6 fixes the problems with rtl driver?
>
> Best regards
Reverting the two patches indeed fixes the bug on -rc5.

  parent reply	other threads:[~2012-07-05  4:14 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
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 [this message]
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=4FF514B2.4050000@palosanto.com \
    --to=a_villacis@palosanto.com \
    --cc=m.szyprowski@samsung.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