so it's confirmed this affects gm45, and possibly only that.. thanks
** Summary changed:
- 3.19.0-17 freeze
+ [gm45] 3.19.0-17 freeze
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1453593
Title:
[
As requested in Post #12 above
** Attachment added: "terminal output"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1453593/+attachment/4398007/+files/sudo%20lspci%20-vvvnn
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
h
nope, all were with some 4.0 based mainline, could you try again?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1453593
Title:
3.19.0-17 freeze
To manage notifications about this bug go to:
https:/
although it's also possible that it didn't get far enough to start
logging to the disk.. boot the bad one without drm.debug, quiet and
splash, hoping that you'll get something on the screen instead.. take a
picture if you do
--
You received this bug notification because you are a member of Ubuntu
at #15:
one time boot with 3.19.0-17:
added 'drm.debug=0xe' to the boot options, removed "quiet no splash".
Boot attempt with 3.19.0-17 was made at 10:56, I suppose.
Later, successfully booted was with 4.0.
Included /var/log/kern.log.
** Attachment added: "boot attempt with 3.19.0-17"
ht
please attach the kern.log after booting the bad kernel once with
'drm.debug=0xe'
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1453593
Title:
3.19.0-17 freeze
To manage notifications about this bu
at #13:
v4.0-rc7 mainline boots okay on dell e6500.
Startup time under systemd is about 5.7sec (kernel)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1453593
Title:
3.19.0-17 freeze
To manage not
** Changed in: linux (Ubuntu Vivid)
Assignee: (unassigned) => Timo Aaltonen (tjaalton)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1453593
Title:
3.19.0-17 freeze
To manage notifications abo
also, test v4.0-rc7 mainline
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1453593
Title:
3.19.0-17 freeze
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/li
@Alan Fry and @taiebot65
Can you post the output of : 'sudo lspci -vvvnn'
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1453593
Title:
3.19.0-17 freeze
To manage notifications about this bug go to
** Changed in: linux (Ubuntu)
Importance: Medium => High
** Changed in: linux (Ubuntu)
Status: Incomplete => Triaged
** Tags added: kernel-key
** Also affects: linux (Ubuntu Vivid)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Vivid)
Importance: Undecided
Mainline kernel 4.0.3 also boots OK.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1453593
Title:
3.19.0-17 freeze
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+s
HP Elitebook 6930p, Intel graphics, with fully updated Ubuntu Wily and
kernel 3.19.0-17 also freezes early in the boot. It appears to happen
just as the low resolution display changes to higher resolution.
Booting in recovery mode results in low resolution display.
Kernel 3.19.0-16 is OK as is ma
By the way on my computer with kernel 3.19.0-17 my computer fails to
start
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1453593
Title:
3.19.0-17 freeze
To manage notifications about this bug go to
I am having the same problem but i will not be able to upgrade my bios.
I have an old gateway computer.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1453593
Title:
3.19.0-17 freeze
To manage notif
at #6:
3.19.6-vivid boots normally. Startup time (kernel) under systemd is 4.8s (about
what is found for other recent kernels).
For completeness, I tested also 3.19.8-vivid: boots also normally. However,
startup time (kernel) is considerably longer, about 8s!
--
You received this bug notificat
Can you also test the upstream stable 3.19.6 kernel ,which Ubuntu
3.19.0-17 is based on? This will tell us if this is an Ubuntu specific
issue.
The 3.19.6 kernel can be downloaded from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.19.6-vivid/
Thanks in advance!
** Changed in: linux (Ubuntu)
at #3 - bios upgrade:
i just discover that sudo dmidecode -s bios-version && sudo dmidecode -s
bios-release-date do not work with kernel 4.0, but still work under 3.19.0-16.
I get the response: "/dev/mem: no such file"
Is this a bug or a new feature?
--
You received this bug notification beca
at #3 - bios upgrade:
considering the fact that such an upgrade is a sensitive matter, I feel
that the suggested procedures are somewhat risky because not being
really transparent to me.
On the other hand, I have a virtual win7 machine (32bit install) (under
virtualbox) at my disposal.
Maybe, y
volker kempter, thank you for reporting this and helping make Ubuntu
better. As per http://www.dell.com/support/home/us/en/19/product-
support/product/latitude-e6500/drivers an update to your computer's
buggy and outdated BIOS is available (A29). If you update to this
following https://help.ubuntu.
20 matches
Mail list logo
