10de:03ef [ASRock N68-GS4/USB3 FX] Networking and ACPI conflicts

[mike]

My on-board networking doesn't work, and trying to restart or shutdown the computer freezes the system.

With an older 12.04 kernel, 3.2.0-23.36, there were two workarounds.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1003297

WORKAROUND: Boot into rescue mode, drop to the terminal, run "rmmod forcedeth" then "modprobe forcedeth msi=0 msix=0" then resume a normal boot. This enabled both networking and regular ACPI functions. This needs to be repeated at every start up and several graphics drivers do not function well until the next normal boot.

---
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: taff 2383 F.... pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 14.04
HibernationDevice: RESUME=UUID=3707218c-3355-4bdb-a631-69aee3520e51
InstallationDate: Installed on 2015-11-25 (5 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
Package: linux (not installed)
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic root=UUID=c6fdfec8-75cf-427c-813d-c6b9dbff9919 ro recovery nomodeset
ProcVersionSignature: Ubuntu 3.19.0-25.26~14.04.1-generic 3.19.8-ckt2
RelatedPackageVersions:
 linux-restricted-modules-3.19.0-25-generic N/A
 linux-backports-modules-3.19.0-25-generic N/A
 linux-firmware 1.127.18
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
Tags: trusty
Uname: Linux 3.19.0-25-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 10/02/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.10
dmi.board.asset.tag: D050997CF5D0
dmi.board.name: N68-GS4/USB3 FX
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd10/02/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN68-GS4/USB3FX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1520651

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[mike (taffod)]

apport information

[mike (taffod)]

apport information

[mike (taffod)]

apport information

[mike (taffod)]

apport information

[mike (taffod)]

apport information

[mike (taffod)]

apport information

[mike (taffod)]

apport information

[mike (taffod)]

apport information

[mike (taffod)]

apport information

[mike (taffod)]

apport information

[mike (taffod)]

apport information

[mike (taffod)]

apport information

[mike (taffod)]

apport information

[mike (taffod)]

apport information

[penalvch (penalvch)]

mike, could you please test the latest upstream kernel available from the very top line at the top of the page from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D (the release names are irrelevant for testing, and please do not test the daily folder)? Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds . This will allow additional upstream developers to examine the issue.

If the latest kernel did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this issue is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, and Y are the first two numbers of the kernel version, and Z is the release candidate number if it exists.

If the mainline kernel does not fix the issue, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream.

Once testing of the latest upstream kernel is complete, please mark this report's Status as Confirmed. Please let us know your results.

Thank you for your understanding.

[mike (taffod)]

Kernel bug exists upstream.

using v4.4-rc3-wily/ did not fix the issue.

[penalvch (penalvch)]

mike, the issue you are reporting is an upstream one. Could you please report this problem following the instructions verbatim at https://wiki.ubuntu.com/Bugs/Upstream/kernel to the appropriate venue (netdev mailinglist)?

Please provide a direct URL to your newly made report when it becomes available so that it may be tracked.

Thank you for your understanding.

[mike (taffod)]

Christopher,

I'm a bit confused here. Didn't I do the upstream testing as you requested? Following your instructions exactly?

Now, are you suggesting that "the issue you are reporting is an upstream one", well of course it is. You asked me to do it that way, and I obliged.

As much fun as it has been getting involved in this testing and bug reports, the real reason, I made my initial report was that I have an unusable PC.

I was hoping someone could suggest a practical work-around. Someone with knowledge of the new kernels who can tell me how to adapt the old work-arounds that I referenced to the current system?

Is there anyone out there that can help me with that?

I can see that no-one is able or willing to help me with that, so: I will unable to do any further testing on this issue as the PC is now packaged up and ready to dispatch back to the supplier, who has generously agreed to replace the motherboard for me.

I note that this is an increasing problem with newer motherboards especially USB 3 ready ones. I hope that this issue is addressed soon or UBUNTU may seriously loose popularity as it will be unusable to an increasing number of new motherboard owners.

Thank you for your help to date.

What shall I do with this thread now? Close it down?

Mike

[penalvch (penalvch)]

mike, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1520651/comments/19 regarding you no longer have the original hardware. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.