From: bugzilla-daemon@bugzilla.kernel.org
To: backports@vger.kernel.org
Subject: [Bug 51671] New: ALX driver unusable on new kernel
Date: Thu, 13 Dec 2012 05:54:04 +0000 (UTC) [thread overview]
Message-ID: <bug-51671-58281@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=51671
Summary: ALX driver unusable on new kernel
Product: Backports project
Version: unspecified
Kernel Version: 3.7.0
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: Compat-Drivers
AssignedTo: backports@vger.kernel.org
ReportedBy: i@hexchain.org
Regression: No
After upgraded to kernel 3.7, the ALX driver in compat-drivers nolonger
functions. Building is successful, but it is unable to load.
dmesg before kernel update, using compat-wireless 20121003:
Dec 12 12:12:09 lightning.hexchain.org kernel: alx 0000:03:00.0: DMA to 64-BIT
addresses
Dec 12 12:12:09 lightning.hexchain.org kernel: alx 0000:03:00.0: (unregistered
net_device): HW Flags = 0x415
Dec 12 12:12:09 lightning.hexchain.org kernel: alx 0000:03:00.0: (unregistered
net_device): reset PHY, pws = 1, az = 0, ptp = 0
Dec 12 12:12:09 lightning.hexchain.org kernel: alx 0000:03:00.0: (unregistered
net_device): speed = 0x2f, autoneg = 1
Dec 12 12:12:09 lightning.hexchain.org kernel: alx 0000:03:00.0: irq 45 for
MSI/MSI-X
Dec 12 12:12:09 lightning.hexchain.org kernel: alx: Atheros Gigabit Network
Connection
After kernel update, any version of compat-driver before 20121204 fails to
build.
dmesg after kernel update, using the newest compat-driver-u:
Dec 12 22:31:21 lightning.hexchain.org kernel: alx 0000:03:00.0: DMA to 64-BIT
addresses
Dec 12 22:31:21 lightning.hexchain.org kernel: alx 0000:03:00.0: config PHY
speed/duplex failed,err=4
Dec 12 22:31:21 lightning.hexchain.org kernel: alx 0000:03:00.0: error when
probe device, error = -5
Dec 12 22:31:21 lightning.hexchain.org kernel: alx: probe of 0000:03:00.0
failed with error -5
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2012-12-13 5:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-13 5:54 bugzilla-daemon [this message]
2012-12-14 18:53 ` [Bug 51671] ALX driver unusable on new kernel bugzilla-daemon
2012-12-14 20:51 ` bugzilla-daemon
2012-12-16 12:16 ` bugzilla-daemon
2012-12-16 13:49 ` bugzilla-daemon
2012-12-17 3:19 ` bugzilla-daemon
2012-12-19 22:08 ` bugzilla-daemon
2012-12-20 4:48 ` bugzilla-daemon
2012-12-20 6:35 ` bugzilla-daemon
2012-12-20 8:28 ` bugzilla-daemon
2012-12-20 8:36 ` bugzilla-daemon
2012-12-20 8:36 ` bugzilla-daemon
2013-02-21 7:48 ` bugzilla-daemon
2013-03-05 19:53 ` bugzilla-daemon
2013-03-09 22:00 ` bugzilla-daemon
2013-03-09 22:43 ` bugzilla-daemon
2013-03-11 20:12 ` bugzilla-daemon
2013-05-02 16:28 ` bugzilla-daemon
2013-07-30 14:10 ` bugzilla-daemon
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=bug-51671-58281@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=backports@vger.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).