Unable to boot
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | linux (Ubuntu) |
Undecided
|
Unassigned | ||
Bug Description
System: Kubuntu (adm64) 14.10.
Last update: 4-Jan-2015
No proprietary drivers.
No 3rd party software.
The last kernel I was able to run on my Utopic system is 3.16.0-17-generic. Every update thereafter failed. The last one I tried is -28.
From syslog for -28 kernel:
Jan 4 14:22:41 aldebaran kernel: [ 1.712424] [drm] Initialized drm 1.1.0 20060810
Jan 4 14:22:41 aldebaran kernel: [ 1.736322] [drm] VGACON disable radeon kernel modesetting.
Jan 4 14:22:41 aldebaran kernel: [ 1.736375] [drm:radeon_init] *ERROR* No UMS support in radeon module!
Jan 4 14:22:41 aldebaran kernel: [ 10.340446] [drm] VGACON disable radeon kernel modesetting.
Jan 4 14:22:41 aldebaran kernel: [ 10.340448] [drm:radeon_init] *ERROR* No UMS support in radeon module!
Jan 4 14:22:41 aldebaran kernel: [ 101.573768] [drm] VGACON disable radeon kernel modesetting.
Jan 4 14:22:41 aldebaran kernel: [ 101.573771] [drm:radeon_init] *ERROR* No UMS support in radeon module!
From syslog for -17 kernel:
Jan 4 14:27:56 aldebaran kernel: [ 1.676277] [drm] Initialized drm 1.1.0 20060810
Jan 4 14:27:56 aldebaran kernel: [ 1.698850] [drm] radeon kernel modesetting enabled.
Jan 4 14:27:56 aldebaran kernel: [ 1.698924] fb: switching to radeondrmfb from VESA VGA
Jan 4 14:27:56 aldebaran kernel: [ 1.699341] [drm] initializing kernel modesetting (TURKS 0x1002:0x6758 0x1043:0x03EA).
Jan 4 14:27:56 aldebaran kernel: [ 1.699351] [drm] register mmio base: 0xFDDC0000
Jan 4 14:27:56 aldebaran kernel: [ 1.699352] [drm] register mmio size: 131072
Jan 4 14:27:56 aldebaran kernel: [ 1.699877] [drm] Detected VRAM RAM=1024M, BAR=256M
Jan 4 14:27:56 aldebaran kernel: [ 1.699878] [drm] RAM width 128bits DDR
Jan 4 14:27:56 aldebaran kernel: [ 1.700079] [drm] radeon: 1024M of VRAM memory ready
Jan 4 14:27:56 aldebaran kernel: [ 1.700081] [drm] radeon: 1024M of GTT memory ready.
Jan 4 14:27:56 aldebaran kernel: [ 1.700092] [drm] Loading TURKS Microcode
Jan 4 14:27:56 aldebaran kernel: [ 1.700180] [drm] Internal thermal controller with fan control
Jan 4 14:27:56 aldebaran kernel: [ 1.700714] [drm] radeon: power management initialized
Jan 4 14:27:56 aldebaran kernel: [ 1.700815] [drm] GART: num cpu pages 262144, num gpu pages 262144
Jan 4 14:27:56 aldebaran kernel: [ 1.701896] [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0
Jan 4 14:27:56 aldebaran kernel: [ 1.711628] [drm] PCIE GART of 1024M enabled (table at 0x0000000000273
Jan 4 14:27:56 aldebaran kernel: [ 1.713260] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
Jan 4 14:27:56 aldebaran kernel: [ 1.713262] [drm] Driver supports precise vblank timestamp query.
Jan 4 14:27:56 aldebaran kernel: [ 1.713314] [drm] radeon: irq initialized.
Jan 4 14:27:56 aldebaran kernel: [ 1.729572] [drm] ring test on 0 succeeded in 1 usecs
Jan 4 14:27:56 aldebaran kernel: [ 1.729629] [drm] ring test on 3 succeeded in 1 usecs
Jan 4 14:27:56 aldebaran kernel: [ 1.934934] [drm] ring test on 5 succeeded in 1 usecs
Jan 4 14:27:56 aldebaran kernel: [ 1.934938] [drm] UVD initialized successfully.
Jan 4 14:27:56 aldebaran kernel: [ 1.935061] [drm] ib test on ring 0 succeeded in 0 usecs
Jan 4 14:27:56 aldebaran kernel: [ 1.935081] [drm] ib test on ring 3 succeeded in 0 usecs
Jan 4 14:27:56 aldebaran kernel: [ 2.105144] [drm] ib test on ring 5 succeeded
Jan 4 14:27:56 aldebaran kernel: [ 2.105738] [drm] Radeon Display Connectors
Jan 4 14:27:56 aldebaran kernel: [ 2.105740] [drm] Connector 0:
Jan 4 14:27:56 aldebaran kernel: [ 2.105741] [drm] DP-1
Jan 4 14:27:56 aldebaran kernel: [ 2.105742] [drm] HPD4
Jan 4 14:27:56 aldebaran kernel: [ 2.105743] [drm] DDC: 0x6480 0x6480 0x6484 0x6484 0x6488 0x6488 0x648c 0x648c
Jan 4 14:27:56 aldebaran kernel: [ 2.105744] [drm] Encoders:
Jan 4 14:27:56 aldebaran kernel: [ 2.105745] [drm] DFP1: INTERNAL_UNIPHY2
Jan 4 14:27:56 aldebaran kernel: [ 2.105745] [drm] Connector 1:
Jan 4 14:27:56 aldebaran kernel: [ 2.105746] [drm] HDMI-A-1
Jan 4 14:27:56 aldebaran kernel: [ 2.105747] [drm] HPD2
Jan 4 14:27:56 aldebaran kernel: [ 2.105748] [drm] DDC: 0x6470 0x6470 0x6474 0x6474 0x6478 0x6478 0x647c 0x647c
Jan 4 14:27:56 aldebaran kernel: [ 2.105748] [drm] Encoders:
Jan 4 14:27:56 aldebaran kernel: [ 2.105749] [drm] DFP2: INTERNAL_UNIPHY2
Jan 4 14:27:56 aldebaran kernel: [ 2.105750] [drm] Connector 2:
Jan 4 14:27:56 aldebaran kernel: [ 2.105751] [drm] DVI-I-1
Jan 4 14:27:56 aldebaran kernel: [ 2.105751] [drm] HPD1
Jan 4 14:27:56 aldebaran kernel: [ 2.105752] [drm] DDC: 0x6460 0x6460 0x6464 0x6464 0x6468 0x6468 0x646c 0x646c
Jan 4 14:27:56 aldebaran kernel: [ 2.105753] [drm] Encoders:
Jan 4 14:27:56 aldebaran kernel: [ 2.105754] [drm] DFP3: INTERNAL_UNIPHY
Jan 4 14:27:56 aldebaran kernel: [ 2.105754] [drm] CRT1: INTERNAL_
Jan 4 14:27:56 aldebaran kernel: [ 2.154011] [drm] fb mappable at 0xD0474000
Jan 4 14:27:56 aldebaran kernel: [ 2.154013] [drm] vram apper at 0xD0000000
Jan 4 14:27:56 aldebaran kernel: [ 2.154014] [drm] size 9216000
Jan 4 14:27:56 aldebaran kernel: [ 2.154014] [drm] fb depth is 24
Jan 4 14:27:56 aldebaran kernel: [ 2.154015] [drm] pitch is 7680
Jan 4 14:27:56 aldebaran kernel: [ 2.154154] fbcon: radeondrmfb (fb0) is primary device
Jan 4 14:27:56 aldebaran kernel: [ 2.154213] radeon 0000:01:00.0: fb0: radeondrmfb frame buffer device
Jan 4 14:27:56 aldebaran kernel: [ 2.160162] [drm] Initialized radeon 2.39.0 20080528 for 0000:01:00.0 on minor 0
- I've tried regenerating /boot/grub/grub.cfg but there are no differences with previous file.
- The kernel command line is the same for both kernels.
Regards
Philippe
| Changed in linux (Ubuntu): | |
| status: | New → Incomplete |
| tags: | added: utopic |
Would it be possible for you to test the latest upstream kernel? Refer to https:/
If this bug is fixed in the mainline kernel, please add the following tag 'kernel-
If the mainline kernel does not fix this bug, please add the tag: 'kernel-
If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".
Thanks in advance.
[0] http://
| tags: | added: kernel-key |
| Changed in linux (Ubuntu): | |
| importance: | Undecided → Medium |
| Philippe Clérié (pclerie) wrote : | #3 |
Tried v3.19-rc2-vivid as requested. It failed in the same manner. No change.
Philippe
| tags: | added: kernel-bug-exists-upstream |
| tags: |
added: kernel-da-key removed: kernel-key |
| Joseph Salisbury (jsalisbury) wrote : | #4 |
I'd like to perform a bisect to figure out what commit caused this regression. We need to identify the earliest kernel where the issue started happening as well as the latest kernel that did not have this issue.
Can you test the following kernels and post back? We are looking for the first kernel version that exhibits this bug:
v3.16.3: http://
v3.16.4: http://
v3.16.5: http://
You don't have to test every kernel, just up until the kernel that first has this bug.
Thanks in advance!
| tags: | added: performing-bisect |
| Philippe Clérié (pclerie) wrote : | #5 |
Looks like 3.16.4 is your baby.
Thanks for the speed! :-)
| Changed in linux (Ubuntu Utopic): | |
| status: | New → Confirmed |
| Changed in linux (Ubuntu Vivid): | |
| status: | Incomplete → Confirmed |
| Changed in linux (Ubuntu Utopic): | |
| importance: | Undecided → Medium |
| Joseph Salisbury (jsalisbury) wrote : | #6 |
I see the CONFIG_
I think our best bet is to bisect between v3.16.3 and v3.16.4. It will require testing about 8 - 10 kernels. I'll build the first test kernel and post a link to it shortly.
| Philippe Clérié (pclerie) wrote : | #7 |
The only thing I hate more than bugs is reporting them. :-)
OK! You build, I test.
But give me more than one kernel at a time.
--
Philippe
| Joseph Salisbury (jsalisbury) wrote : | #8 |
I started a kernel bisect between v3.16.3 and v3.16.4. The kernel bisect will require testing of about 7-10 test kernels.
I built the first test kernel, up to the following commit:
be35ff0f45bf85f
The test kernel can be downloaded from:
http://
Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results.
Thanks in advance
| Philippe Clérié (pclerie) wrote : | #9 |
OK! I'll check that one out this evening.
I don't know what the constraints are, but if you must build kernels based on my tests, then this is going to take a few days.
On the other hand, if I have a bunch of kernels, I can install them all at once, boot one then boot the next until we find the culprit. That's at most one hour, not counting download time, which for me would be around 15-30 min per kernel, but that can be automated.
Whatever the method, as I said, you build them, I test them.
| Philippe Clérié (pclerie) wrote : | #10 |
First kernel fails!
| Philippe Clérié (pclerie) wrote : | #11 |
Side note:
I have been getting an error at boot since Trusty:
Error: Diskfilter writes are not supported.
I work around it by doing something else while the thing boots. Anyway, I don't get that error with the kernel builds you had me testing.
| Joseph Salisbury (jsalisbury) wrote : | #12 |
Unfortunately we can't build more that one kernel at a time during a bisect. The bisect needs to be told whether the last kernel was 'good' or 'bad', so it knows what commit to build up to next.
I built the first test kernel, up to the following commit:
907ed7ee43a3fee
The test kernel can be downloaded from:
http://
Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results.
Thanks in advance
| Philippe Clérié (pclerie) wrote : | #13 |
Second kernel fails.
| Joseph Salisbury (jsalisbury) wrote : | #14 |
I built the next test kernel, up to the following commit:
1423ca3aa4335d5
The test kernel can be downloaded from:
http://
Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results.
Thanks in advance
| Philippe Clérié (pclerie) wrote : | #15 |
Third kernel fails.
| Joseph Salisbury (jsalisbury) wrote : | #16 |
I built the next test kernel, up to the following commit:
d528dcb9cac01b5
The test kernel can be downloaded from:
http://
Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results.
| Philippe Clérié (pclerie) wrote : | #17 |
Fourth kernel fails.
| Joseph Salisbury (jsalisbury) wrote : | #18 |
I built the next test kernel, up to the following commit:
fc065a4cecb9d49
The test kernel can be downloaded from:
http://
Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results.
| Philippe Clérié (pclerie) wrote : | #19 |
Kernel #5 works. :-)
| Joseph Salisbury (jsalisbury) wrote : | #20 |
I built the next test kernel, up to the following commit:
d5a1560b20bff6a
The test kernel can be downloaded from:
http://
Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results.
| Philippe Clérié (pclerie) wrote : | #21 |
Kernel #6 works.
| Philippe Clérié (pclerie) wrote : | #22 |
Anything new?
| Rolf Leggewie (r0lf) wrote : | #23 |
utopic has seen the end of its life and is no longer receiving any updates. Marking the utopic task for this ticket as "Won't Fix".
| Changed in linux (Ubuntu Utopic): | |
| status: | Confirmed → Won't Fix |
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
/dev/snd/
/dev/snd/
/dev/snd/
CurrentDesktop: Unity
DistroRelease: Ubuntu 16.04
InstallationDate: Installed on 2016-04-22 (5 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
IwConfig:
enp9s0 no wireless extensions.
enp7s0 no wireless extensions.
lo no wireless extensions.
MachineType: System manufacturer System Product Name
Package: linux (not installed)
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=
ProcVersionSign
RelatedPackageV
linux-
linux-
linux-firmware 1.157
RfKill:
Tags: xenial xenial
Uname: Linux 4.4.0-21-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 09/03/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0610
dmi.board.
dmi.board.name: P6T DELUXE V2
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: System Product Name
dmi.product.
dmi.sys.vendor: System manufacturer
| tags: | added: apport-collected xenial |
apport information
apport information
apport information
apport information
apport information
apport information
apport information
apport information
apport information
apport information
apport information
apport information
apport information
I'm was running: "apport-collect 1407505", all of my comments up there are autogenerated by apport-collect, I'm sorry for the quantities.
I have updated from Ubuntu 15.10 to Ubuntu 16.04 LTS and now I'm affected from this bug.
The kernel version is: 4.4.0-21-generic
Running: dmesg | egrep 'drm|radeon' I'm getting this error:
[ 1.127347] [drm] Initialized drm 1.1.0 20060810
[ 1.159659] [drm] VGACON disable radeon kernel modesetting.
[ 1.159734] [drm:radeon_init [radeon]] *ERROR* No UMS support in radeon module!
[ 1.196474] [drm] VGACON disable radeon kernel modesetting.
[ 1.196549] [drm:radeon_init [radeon]] *ERROR* No UMS support in radeon module!
[ 18.569430] [drm] VGACON disable radeon kernel modesetting.
[ 18.569467] [drm:radeon_init [radeon]] *ERROR* No UMS support in radeon module!
I'm tried to edit the /etc/default/grub from
GRUB_CMDLINE_
to
GRUB_CMDLINE_
without success.
| Cgiraud (cgiraud) wrote : | #39 |
Same problem for me upgrading from 15.10 to 16.04:
$ dmesg | egrep 'drm|radeon'
[ 1.293303] [drm] Initialized drm 1.1.0 20060810
[ 1.328085] [drm] VGACON disable radeon kernel modesetting.
[ 1.328109] [drm:radeon_init [radeon]] *ERROR* No UMS support in radeon module!
[ 12.801460] [drm] VGACON disable radeon kernel modesetting.
[ 12.801484] [drm:radeon_init [radeon]] *ERROR* No UMS support in radeon module!
$ lspci -nn | grep VGA
00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Sumo [Radeon HD 6410D] [1002:9644]
baobab:~/sw/amd$ uname -r
4.4.0-21-lowlatency
$ apport-collect 1407505
/usr/share/
from gi.repository import GLib, Wnck, GdkX11, Gdk
Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
$
| Marco Graziotti (graziottimarco) wrote : | #40 |
It's necessary to open a new bug report?
Because this report it's for Ubuntu Utopic (no longer supported) and Ubuntu Vivid (that it's supported yet).
| Cgiraud (cgiraud) wrote : | #41 |
Xenial also impacted.
| no longer affects: | linux (Ubuntu Vivid) |
| no longer affects: | linux (Ubuntu Utopic) |
| summary: |
- No UMS support in radeon module + Unable to boot |
Philippe Clérié, given the originally reported issue was resolved when you upgraded from Utopic to WIly, this report is considered closed.
For any new issue afterwards, please file a new report.
Thank you for your understanding.
| Changed in linux (Ubuntu): | |
| importance: | Medium → Undecided |
| status: | Confirmed → Invalid |
| Cgiraud (cgiraud) wrote : | #43 |
See new bug created here:
https:/


This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
apport-collect 1407505
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.