From: Igor Russkikh <irusskikh@marvell.com>
To: Stephen Hemminger <stephen@networkplumber.org>, <netdev@vger.kernel.org>
Subject: Re: Fw: [Bug 214619] New: Aquantia / Atlantic driver not loading post 5.14.RC7
Date: Fri, 19 Nov 2021 09:58:25 +0100 [thread overview]
Message-ID: <ea15681a-01b8-c6c5-a2c6-d1c255a03d4e@marvell.com> (raw)
In-Reply-To: <20211004141418.1b4bd7bb@hermes.local>
Hello community,
> Bug ID: 214619
> Summary: Aquantia / Atlantic driver not loading post 5.14.RC7
> Product: Networking
> Version: 2.5
> Kernel Version: 514.rc7
> Hardware: x86-64
> OS: Linux
> Tree: Mainline
> Status: NEW
> Severity: high
> Priority: P1
> Component: Other
> Assignee: stephen@networkplumber.org
> Reporter: Miles.Rumppe@gmail.com
> Regression: No
>
https://bugzilla.kernel.org/show_bug.cgi?id=214619
Quite a strange issue, we are looking for advice/assistance.
After looking into disassembly, I see the failure is AFTER the end of the function:
272d: b8 01 00 00 00 mov $0x1,%eax
2732: d3 e0 shl %cl,%eax
2734: 41 09 85 f8 05 00 00 or %eax,0x5f8(%r13)
273b: eb 84 jmp 26c1 <aq_nic_start+0x301>
>> 273d: 0f 0b ud2
273f: 90 nop
On undefined instruction.
We had similar report in past from another user, but were unable to find out how execution could reach that point.
I suspect this is something related to compiler optimization or some other coincidence.
We also were not successful in trying to bisect this driver specific changes. Looks like some side kernel change could have triggered that.
Any clue?
Regards,
Igor
prev parent reply other threads:[~2021-11-19 8:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-04 21:14 Fw: [Bug 214619] New: Aquantia / Atlantic driver not loading post 5.14.RC7 Stephen Hemminger
2021-11-19 8:58 ` Igor Russkikh [this message]
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=ea15681a-01b8-c6c5-a2c6-d1c255a03d4e@marvell.com \
--to=irusskikh@marvell.com \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.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.