linux-clk.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Semyon Verchenko <semverchenko@factor-ts.ru>
To: Hans de Goede <hdegoede@redhat.com>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: "David Müller" <dave.mueller@gmx.ch>,
	"Fujinaka, Todd" <todd.fujinaka@intel.com>,
	"Kirsher, Jeffrey T" <jeffrey.t.kirsher@intel.com>,
	"e1000-devel@lists.sf.net" <e1000-devel@lists.sf.net>,
	"Stephen Boyd" <sboyd@kernel.org>,
	linux-clk@vger.kernel.org,
	"Michael Turquette" <mturquette@baylibre.com>,
	"Stephen Boyd" <sboyd@codeaurora.org>
Subject: Re: [E1000-devel] igb driver with Intel Atom Bay Trail issue
Date: Mon, 22 Apr 2019 13:20:13 +0300	[thread overview]
Message-ID: <99a451b4-34cd-b14c-1cef-116829d435f9@factor-ts.ru> (raw)
In-Reply-To: <da634f93-9cbb-f5a8-e7c2-4a20368823e9@redhat.com>


On 18.04.2019 18:12, Hans de Goede wrote:
> Hi Semyon,
>
> On 18-04-19 15:26, Semyon Verchenko wrote:
>>
>> On 18.04.2019 16:09, Hans de Goede wrote:
>>> Hi,
>>>
>>> On 09-04-19 17:31, Andy Shevchenko wrote:
>
> <snip>
>
>>> Ok.
>>>
>>> Семен Верченко, this means that we are going to need DMI info from
>>> the board in question. I thought we already had that, but I now see 
>>> that
>>> you original report did not have that a
>>>
>>> Please run as root:
>>>
>>> dmidecode &> dmidecode.log
>>>
>>> And then reply to this email with the generated dmidecode.log file
>>> attached. Once I have that file I can prepare a patch fixing this.
>
> Thank you for the DMI decode.
>
> Attached are 3 patches, can you please test if adding those 3 patches
> to your kernel fixes the problem?
>
> Thanks & Regards,
>
> Hans
>
Hi Hans,
It seems that these patches fix the problem (at least interfaces are 
visible through ip addr and it's possible to ping something from them).

Thanks for fixing this issue.

  reply	other threads:[~2019-04-22 10:20 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1c433bef-055e-2ac3-990c-325aa2d3899e@factor-ts.ru>
     [not found] ` <9B4A1B1917080E46B64F07F2989DADD69AF4DDE7@ORSMSX115.amr.corp.intel.com>
2019-03-27 16:02   ` [E1000-devel] igb driver with Intel Atom Bay Trail issue Hans de Goede
2019-03-27 16:47     ` Andy Shevchenko
2019-03-27 17:31       ` David Müller
2019-03-27 19:19         ` Andy Shevchenko
2019-03-28 14:35           ` David Müller
2019-03-28 14:58             ` Andy Shevchenko
2019-03-28 15:01               ` Hans de Goede
2019-03-28 15:24                 ` Andy Shevchenko
2019-03-28 15:32                   ` Hans de Goede
2019-03-28 15:49                     ` Andy Shevchenko
2019-03-29  4:46                       ` Hisashi T Fujinaka
2019-03-29 12:32                         ` Hans de Goede
2019-03-29 12:30                       ` Hans de Goede
2019-03-29 13:59                         ` Семен Верченко
2019-03-29 15:53                           ` Hans de Goede
2019-04-04 14:43                             ` Hans de Goede
     [not found]                               ` <20190408172111.GX9224@smile.fi.intel.com>
2019-04-08 18:43                                 ` Hans de Goede
2019-04-09 15:31                                   ` Andy Shevchenko
2019-04-18 13:09                                     ` Hans de Goede
2019-04-18 13:26                                       ` Semyon Verchenko
2019-04-18 15:12                                         ` Hans de Goede
2019-04-22 10:20                                           ` Semyon Verchenko [this message]
2019-04-29 15:02                                             ` Hans de Goede
2019-03-28 14:48       ` Hans de Goede

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=99a451b4-34cd-b14c-1cef-116829d435f9@factor-ts.ru \
    --to=semverchenko@factor-ts.ru \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=dave.mueller@gmx.ch \
    --cc=e1000-devel@lists.sf.net \
    --cc=hdegoede@redhat.com \
    --cc=jeffrey.t.kirsher@intel.com \
    --cc=linux-clk@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=sboyd@codeaurora.org \
    --cc=sboyd@kernel.org \
    --cc=todd.fujinaka@intel.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).