[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKKZj2DZprXcEg1tRDnt9fnFahLnOEMQNno9hS2UJzQ-n13JHA@mail.gmail.com>
Date: Sun, 1 Jul 2012 15:30:12 +0200
From: Michal Zatloukal <myxal.mxl@...il.com>
To: Francois Romieu <romieu@...zoreil.com>
Cc: Stephen Hemminger <shemminger@...tta.com>, netdev@...r.kernel.org
Subject: Re: [BUG, regression, bisected] Marvell 88E8055 NIC (sky2) fails to
detect link after resume from S3
Breaking news:
Fiddling with mmiotrace, I was able to get the "phy I/O error" on
previously-thought-good kernel (non-reliably; it took several
suspend-resume cycles), and also vice versa - in vty, I was able to
suspend and resume the "bad" kernel with the NIC still working (also
not reliably - in GUI, it still flaked out after first
suspend-resume).
Anyway, I've gathered traces of both good and bad behaviour, each from
the respective kernel (not that it seems to matter much). Now, what's
the recommended way of posting them? Each is over 3MB in size and
pastebin won't take them. :-(
MZ
On Sat, Jun 30, 2012 at 10:02 PM, Francois Romieu <romieu@...zoreil.com> wrote:
> Michal Zatloukal <myxal.mxl@...il.com> :
> [...]
>> Is there something I can try?
>
> I have not used it for quite some time but comparing mmiotrace output
> (see Documentation/trace/mmiotrace.txt) before and after the regression
> commit may give some hint.
>
> Otherwise I would ask for help on linux-pm@...r.kernel.org
>
> --
> Ueimor
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists