Kernel panic during install boot in ohci_hcd module

[nenhard]

Kernel panic if I try to boot USB from installer 15.10 image or reboot after dist-upgrade from 15.10 beta to 15.10 release.
This happens in kernel 4.2.0-16, but not in older beta 4.1.0-3-generic kernel.

I have attached picture of kernel panic and 'sudo lspci -vnvn' output.
---
ApportVersion: 2.19.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/pcmC0D0p: nenad 4242 F...m pulseaudio
 /dev/snd/controlC0: nenad 4242 F.... pulseaudio
 /dev/snd/controlC1: nenad 4242 F.... pulseaudio
CurrentDesktop: XFCE
DistroRelease: Ubuntu 15.10
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-08-02 (84 days ago)
InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150726)
MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
NonfreeKernelModules: fglrx
Package: linux (not installed)
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.1.0-3-generic root=UUID=c2eb7374-dd07-45ee-9402-27e3527a60b8 ro amd_iommu=on pci-stub.ids=1002:665d,1002:aac0,13f6:0111
ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
RelatedPackageVersions:
 linux-restricted-modules-4.1.0-3-generic N/A
 linux-backports-modules-4.1.0-3-generic N/A
 linux-firmware 1.149
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
Tags: wily
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
Uname: Linux 4.1.0-3-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 01/25/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: FD
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: 970A-D3
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFD:bd01/25/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rn970A-D3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.: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: Gigabyte Technology Co., 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 1509798

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.

[nenhard (few-find-first)]

apport information

[nenhard (few-find-first)]

apport information

[nenhard (few-find-first)]

apport information

[nenhard (few-find-first)]

apport information

[nenhard (few-find-first)]

apport information

[nenhard (few-find-first)]

apport information

[nenhard (few-find-first)]

apport information

[nenhard (few-find-first)]

apport information

[nenhard (few-find-first)]

apport information

[nenhard (few-find-first)]

apport information

[nenhard (few-find-first)]

apport information

[nenhard (few-find-first)]

apport information

[nenhard (few-find-first)]

apport information

[nenhard (few-find-first)]

apport information

[penalvch (penalvch)]

nenhard, 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 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, Y, and Z are numbers corresponding to the kernel version.

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.

[Stefan Bader (smb)]

When the panic occurs and switches to the text screen, is it possible to use page up/down to capture the upper part of it? Unfortunately that usually is the part that contains the actual location of the crash and as such is more useful.

[nenhard (few-find-first)]

My keyboard is USB, so it does not respond after panic,
But I was able to capture more info after upgrading from beta to release (with radeon module installed).
This time messages are different, but panic is still happening.

I have tried also 4.2.0-040200-generic #201510260713 the same thing.

[penalvch (penalvch)]

nenhard, the latest mainline kernel is 4.3-rc7 (not 4.2.x).

[nenhard (few-find-first)]

Similar thing with 4.3, even after plugging out all USB devices.
I think issue might be with AMD chipset and IOMMU.

[penalvch (penalvch)]

nenhard, 4.3 dot what specifically?

[nenhard (few-find-first)]

There is clearly shown version string in the picture.

linux-image-4.3.0-040300rc7-generic_4.3.0-040300rc7.201510260712_amd64.deb

[penalvch (penalvch)]

nenhard, the next step is to fully commit bisect from kernel 4.1 to 4.2 in order to identify the last good kernel commit, followed immediately by the first bad one. This will allow for a more expedited analysis of the root cause of your issue. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection ?

Please note, finding adjacent kernel versions is not fully commit bisecting.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[Launchpad Janitor (janitor)]

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