From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: "Matwey V. Kornilov" <matwey.kornilov@gmail.com>, hdegoede@redhat.com
Cc: andriy.shevchenko@linux.intel.com, carlo@endlessm.com,
davem@davemloft.net, hkallweit1@gmail.com, js@sig21.net,
linux-clk@vger.kernel.org, linux-wireless@vger.kernel.org,
mturquette@baylibre.com, netdev@vger.kernel.org,
sboyd@kernel.org
Subject: Re: [BISECTED] igb initialization failure on Bay Trail
Date: Mon, 25 Jul 2022 10:32:27 -0500 [thread overview]
Message-ID: <148f6cb9-aafc-4fd5-9e30-24078866d3fd@linux.intel.com> (raw)
In-Reply-To: <20220724210037.3906-1-matwey.kornilov@gmail.com>
On 7/24/22 16:00, Matwey V. Kornilov wrote:
> Hello,
>
> I've just found that the following commit
>
> 648e921888ad ("clk: x86: Stop marking clocks as CLK_IS_CRITICAL")
>
> breaks the ethernet on my Lex 3I380CW (Atom E3845) motherboard. The board is
> equipped with dual Intel I211 based 1Gbps copper ethernet.
It's not going to be simple, it's 4 yr old commit that fixes other
issues with S0i3...
>
> Before the commit I see the following:
>
> igb 0000:01:00.0: added PHC on eth0
> igb 0000:01:00.0: Intel(R) Gigabit Ethernet Network Connection
> igb 0000:01:00.0: eth0: (PCIe:2.5Gb/s:Width x1) 4c:02:89:10:02:e4
> igb 0000:01:00.0: eth0: PBA No: FFFFFF-0FF
> igb 0000:01:00.0: Using MSI-X interrupts. 2 rx queue(s), 2 tx queue(s)
> igb 0000:02:00.0: added PHC on eth1
> igb 0000:02:00.0: Intel(R) Gigabit Ethernet Network Connection
> igb 0000:02:00.0: eth1: (PCIe:2.5Gb/s:Width x1) 4c:02:89:10:02:e5
> igb 0000:02:00.0: eth1: PBA No: FFFFFF-0FF
> igb 0000:02:00.0: Using MSI-X interrupts. 2 rx queue(s), 2 tx queue(s)
>
> while when the commit is applied I see the following:
>
> igb 0000:01:00.0: added PHC on eth0
> igb 0000:01:00.0: Intel(R) Gigabit Ethernet Network Connection
> igb 0000:01:00.0: eth0: (PCIe:2.5Gb/s:Width x1) 4c:02:89:10:02:e4
> igb 0000:01:00.0: eth0: PBA No: FFFFFF-0FF
> igb 0000:01:00.0: Using MSI-X interrupts. 2 rx queue(s), 2 tx queue(s)
> igb: probe of 0000:02:00.0 failed with error -2
>
> Please note, that the second ethernet initialization is failed.
>
>
> See also: http://www.lex.com.tw/products/pdf/3I380A&3I380CW.pdf
next prev parent reply other threads:[~2022-07-25 17:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-12 9:34 [PATCH v2 0/3] r8169 (x86) clk fixes to fix S0ix not being reached Hans de Goede
2018-09-12 9:34 ` [PATCH v2 1/3] clk: x86: add "ether_clk" alias for Bay Trail / Cherry Trail Hans de Goede
[not found] ` <20180912093456.23400-1-hdegoede-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2018-09-12 9:34 ` [PATCH v2 2/3] r8169: Get and enable optional ether_clk clock Hans de Goede
2018-09-12 9:34 ` [PATCH v2 3/3] clk: x86: Stop marking clocks as CLK_IS_CRITICAL Hans de Goede
2022-07-24 21:00 ` [BISECTED] igb initialization failure on Bay Trail Matwey V. Kornilov
2022-07-25 15:32 ` Pierre-Louis Bossart [this message]
2022-07-26 9:15 ` Matwey V. Kornilov
2022-07-27 12:18 ` Hans de Goede
2018-09-18 1:48 ` [PATCH v2 0/3] r8169 (x86) clk fixes to fix S0ix not being reached David Miller
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=148f6cb9-aafc-4fd5-9e30-24078866d3fd@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=carlo@endlessm.com \
--cc=davem@davemloft.net \
--cc=hdegoede@redhat.com \
--cc=hkallweit1@gmail.com \
--cc=js@sig21.net \
--cc=linux-clk@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=matwey.kornilov@gmail.com \
--cc=mturquette@baylibre.com \
--cc=netdev@vger.kernel.org \
--cc=sboyd@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 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).