Keyboard, mouse and network all unusable with v 3.13.0-45

[Campbell Boyd]

On booting for first time with 3.13.0-45-generic following update yesterday, keyboard, mouse totally unresponsive and message saying network disconnected.

On booting and using GRUB to select previous version, 3.13.0-43-generic, everything back ok.

Novatech Life NTI114

Running ubuntu 14.04
Memory: 7.7 GiB
Processor: Intel® Core™ i5-4460 CPU @ 3.20GHz × 4
Graphics: Intel® Haswell Desktop
OS type: 64-bit

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: ubuntu-release-upgrader-core 1:0.220.5
ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
Uname: Linux 3.13.0-43-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: Unity
Date: Tue Feb 3 12:20:29 2015
InstallationDate: Installed on 2014-09-17 (139 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
Symptom: release-upgrade
UpgradeStatus: No upgrade log present (probably fresh install)
---
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: campbell 2710 F.... pulseaudio
 /dev/snd/pcmC1D0p: campbell 2710 F...m pulseaudio
 /dev/snd/controlC0: campbell 2710 F.... pulseaudio
DistroRelease: Ubuntu 14.04
HibernationDevice: RESUME=UUID=b7290e2f-642a-414d-988b-cac7bac6530e
InstallationDate: Installed on 2014-09-17 (142 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
IwConfig:
 eth0 no wireless extensions.

 lo no wireless extensions.
MachineType: NOVATECH LTD PERSONAL COMPUTER
Package: linux (not installed)
ProcEnviron:
 LANGUAGE=en_GB:en
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-45-generic root=UUID=fc6ea265-b75c-458a-b5d2-2950ebad0828 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied
 No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-45-generic N/A
 linux-backports-modules-3.13.0-45-generic N/A
 linux-firmware 1.127.11
RfKill:

Tags: trusty
Uname: Linux 3.13.0-45-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

_MarkForUpload: True
dmi.bios.date: 06/19/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F5
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H81M-DS2V
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: To be filled by O.E.M.
dmi.chassis.asset.tag: xxxxxxx-xxx
dmi.chassis.type: 3
dmi.chassis.vendor: NOVATECH LTD
dmi.chassis.version: V1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnPERSONALCOMPUTER:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0:
dmi.product.name: PERSONAL COMPUTER
dmi.product.version: V1.0
dmi.sys.vendor: NOVATECH LTD

[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 1417548

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.

[Campbell Boyd (campbell-boyd-gmail)]

apport information

[Campbell Boyd (campbell-boyd-gmail)]

apport information

[Campbell Boyd (campbell-boyd-gmail)]

apport information

[Campbell Boyd (campbell-boyd-gmail)]

apport information

[Campbell Boyd (campbell-boyd-gmail)]

apport information

[Campbell Boyd (campbell-boyd-gmail)]

apport information

[Campbell Boyd (campbell-boyd-gmail)]

apport information

[Campbell Boyd (campbell-boyd-gmail)]

apport information

[Campbell Boyd (campbell-boyd-gmail)]

apport information

[Campbell Boyd (campbell-boyd-gmail)]

apport information

[Campbell Boyd (campbell-boyd-gmail)]

apport information

[Campbell Boyd (campbell-boyd-gmail)]

apport information

[penalvch (penalvch)]

Campbell Boyd, thank you for reporting this and helping make Ubuntu better. Could you please test the latest upstream kernel available from the very top line at the top of the page (the release names are irrelevant for testing, and please do not test the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue.

If the test 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 bug 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-3.XY-rcZ

Where XY and Z are numbers corresponding to the kernel version.

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-3.XY-rcZ

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

Thank you for your understanding.

[Campbell Boyd (campbell-boyd-gmail)]

Hi Christoher

I want to check I'm doing the right thing.

So far I've tested:

3.19.0-031900rc7-generic
3.19.0-031900rc6-generic
3.19.0-031900rc5-generic
3.19.0-031900rc4-generic
3.19.0-031900rc3-generic
3.19.0-031900rc2-generic

and all have passed - i.e failed to reproduce the problem.

Should I just continue?

Regards

Campbell Boyd
01324 714582

On Sun, Feb 8, 2015 at 5:17 PM, Christopher M. Penalver <
<email address hidden>> wrote:

> Campbell Boyd, thank you for reporting this and helping make Ubuntu
> better. Could you please test the latest upstream kernel available from
> the very top line at the top of the page (the release names are
> irrelevant for testing, and please do not test the daily folder)
> following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow
> additional upstream developers to examine the issue.
>
> If the test 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 bug 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-3.XY-rcZ
>
> Where XY and Z are numbers corresponding to the kernel version.
>
> If the mainline kernel does not fix this bug, please add the following
> tags:
> kernel-bug-exists-upstream
> kernel-bug-exists-upstream-3.XY-rcZ
>
> Once testing of the upstream kernel is complete, please mark this bug's
> Status as Confirmed. Please let us know your results.
>
> Thank you for your understanding.
>
> ** Tags added: latest-bios-f5
>
> ** Changed in: linux (Ubuntu)
> Importance: Undecided => High
>
> ** Changed in: linux (Ubuntu)
> Status: Confirmed => Incomplete
>
> ** Tags added: regression-update
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1417548
>
> Title:
> Keyboard, mouse and network all unusable with v 3.13.0-45
>
> Status in linux package in Ubuntu:
> Incomplete
>
> Bug description:
> On booting for first time with 3.13.0-45-generic following update
> yesterday, keyboard, mouse totally unresponsive and message saying
> network disconnected.
>
> On booting and using GRUB to select previous version,
> 3.13.0-43-generic, everything back ok.
>
> Novatech Life NTI114
>
> Running ubuntu 14.04
> Memory: 7.7 GiB
> Processor: Intel® Core™ i5-4460 CPU @ 3.20GHz × 4
> Graphics: Intel® Haswell Desktop
> OS type: 64-bit
>
> ProblemType: Bug
> DistroRelease: Ubuntu 14.04
> Package: ubuntu-release-upgrader-core 1:0.220.5
> ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
> Uname: Linux 3.13.0-43-generic x86_64
> ApportVersion: 2.14.1-0ubuntu3.6
> Architecture: amd64
> CrashDB: ubuntu
> CurrentDesktop: Unity
> Date: Tue Feb 3 12:20:29 2015
> InstallationDate: Installed ...

[penalvch (penalvch)]

Campbell Boyd, it wouldn't hurt to continue testing earlier releases until you find the earliest one that works.

[Bill Knight (bill-knight)]

For what it's worth, I had this problem upon letting Software Updater upgrade my system to 3.13.0-45.

I rebooted into 3.13.0-44 and I noticed the /boot/initrd.img-3.13.0-45-generic file was about half the size of previous versions (at about 17MB) so I tried using Synaptic Package Manager to reinstall 3.13.0-45 (IIRC it was linux-generic that I installed), and everything was fine aftwerwards.

So maybe the problem is just with Software Updater not performing a full installation update rather than with the kernel itself.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

[penalvch (penalvch)]

Campbell Boyd, to see if this is fixed in Ubuntu already, could you please test for this via http://cdimage.ubuntu.com/daily-live/current/ and advise to the results?

[Campbell Boyd (campbell-boyd-gmail)]

I downloaded vivid-desktop-amd64.iso ( 21-Apr-2015 08:34 1.1G Desktop image for 64-bit PC (AMD64) computers (standard download)) , burnt it to a USB then booted to it.

No problems occurred and the original problems that caused me to raise this bug did not occur.

[penalvch (penalvch)]

Campbell Boyd, would you need a backport to a release prior to Vivid, or may this be closed as Status Invalid?

[Campbell Boyd (campbell-boyd-gmail)]

I'm currently running 3.13.0-45-generic with no problems so I assume problem is fixed.

[penalvch (penalvch)]

Campbell Boyd, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1417548/comments/23 regarding this being fixed with an update. 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.