← Back to team overview

kernel-packages team mailing list archive

[Bug 1132129] Re: USB3 ports cause kernel crash and oops since 3.5.0-24-generic (3.5.0-23 ok), USB2 OK.

 

Still happens on 3.5.0-41-generic.

I have recently observed a variant (and the symptoms are active now on the laptop I'm writing with).
When bug happens, plugging a device on one of the two USB3 ports powers the device but Linux does not detect anything (nothing in dmesg).
Plugging the same device on one of the two USB2 ports (which never suffered the problem) works normally as it always did.

Heres the output of lsusb when all 4 USB ports are free (nothing
plugged) :

Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 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:0003 Linux Foundation 3.0 root hub
Bus 001 Device 044: ID 0cf3:3005 Atheros Communications, Inc. AR3011 Bluetooth
Bus 001 Device 004: ID 1bcf:2883 Sunplus Innovation Technology Inc. 

Regards

** Changed in: linux (Ubuntu)
       Status: Expired => New

** Changed in: linux (Ubuntu)
       Status: New => Incomplete

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1132129

Title:
  USB3 ports cause kernel crash and oops since 3.5.0-24-generic
  (3.5.0-23 ok), USB2 OK.

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Summary: upgrading from 3.5.0-23 to 3.5.0-24 appears to reduce kernel
  stability suddenly from weeks/months to day or so.

  Context: Hardware Asus n55sf laptop. Plugging Galaxy Nexus phone via USB daily or so. Observed for months that sometimes USB breaks (e.g. optical mouse literally off, un/plug does nothing, reboot fixes), but no oops.
  Using suspend to ram regularly (~ daily). Typical uptime : weeks to 1-2 months.
  Using Ubuntu upgrades regularly.
  On 2013-02-01, upgraded to 3.5.0-23, no problem.
  On 2013-02-21, upgraded to 3.5.0-24.

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or
  System -> About Ubuntu

  12.10 AMD64

  2) The version of the package you are using, via 'apt-cache policy
  pkgname' or by checking in Software Center

  LC_ALL=C apt-cache policy linux-image

  linux-image:
    Installed: (none)
    Candidate: 3.5.0.25.31
    Version table:
       3.5.0.25.31 0
          500 http://fr.archive.ubuntu.com/ubuntu/ quantal-updates/main amd64 Packages
          500 http://security.ubuntu.com/ubuntu/ quantal-security/main amd64 Packages
       3.5.0.17.19 0
          500 http://fr.archive.ubuntu.com/ubuntu/ quantal/main amd64 Packages

  3) What you expected to happen

  No oops, no crash.

  4) What happened instead

  On 2013-02-22 (that is kernel update + 1 day), observed kernel panic: switch to text mode with panic report (but X mouse cursor still visible), led blinking. Text says : fatal exception interrupt.
  Action : taken photograph of screen (can join if useful), power cycle machine.

  On 2013-02-23 (that is kernel update + 2 days), observed kernel oops: switch to text mode with oops report, but X mouse cursor still visible and music still playing.
  Action : taken photograph on screen (can join if useful, but you have dmesg attached so probably not useful). Observed that vt-switching key combinations could restore display. Not rebooted system (using it to write this very report) but several features disabled (laptop-integrated card reader, USB mouse). Lsusb still reports in-laptop bluetooth device as present but bluetooth-sendto cannot detect Galaxy Nexus nearby when doing proper steps.

  Considered actions:
  * continue normal use to confirm / narrow oops circumstances
  * downgrade to 3.5.0-23 to confirm symptom disappear

  Thank you for your attention.


  $ lsusb

  Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 003 Device 002: ID 0b05:17a9 ASUSTek Computer, Inc.
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 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:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 007: ID 0cf3:3005 Atheros Communications, Inc. AR3011 Bluetooth
  Bus 001 Device 004: ID 1bcf:2883 Sunplus Innovation Technology Inc.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: linux-image (not installed)
  ProcVersionSignature: Ubuntu 3.5.0-24.37-generic 3.5.7.4
  Uname: Linux 3.5.0-24-generic x86_64
  ApportVersion: 2.6.1-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USER        PID ACCESS COMMAND
   /dev/snd/controlC0:  stephane   2793 F.... xfce4-volumed
                        stephane   2797 F.... pulseaudio
                        stephane   2876 F.... xfce4-mixer-plu
   /dev/snd/pcmC0D0p:   stephane   2797 F...m pulseaudio
  Date: Sat Feb 23 15:03:04 2013
  HibernationDevice: RESUME=UUID=d05e8def-662d-4d3a-b3b3-4d9d2997966d
  InstallationDate: Installed on 2012-12-27 (58 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MachineType: ASUSTeK Computer Inc. N55SF
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-24-generic root=UUID=0ac65d3d-9ad8-4b02-8650-5df01d16640a ro quiet splash
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory /home/stephane not ours.
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.5.0-24-generic N/A
   linux-backports-modules-3.5.0-24-generic  N/A
   linux-firmware                            1.95
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/29/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N55SF.207
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N55SF
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN55SF.207:bd08/29/2011:svnASUSTeKComputerInc.:pnN55SF:pvr1.0:rvnASUSTeKComputerInc.:rnN55SF:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: N55SF
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1132129/+subscriptions