[Kernel-packages] [Bug 1547204] Re: i915 several 'call traces' in dmesg

2017-03-12 Thread David Dombrowsky
New bug created: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1672200 -- 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/1547204 Title: i915 several 'call traces' in dmesg Status in

[Kernel-packages] [Bug 1547204] Re: i915 several 'call traces' in dmesg

2017-03-11 Thread Christopher M. Penalver
David Dombrowsky, it will help immensely if you filed a new report with Ubuntu, using the default repository kernel (not mainline/upstream/3rd party) via a terminal: ubuntu-bug linux Please feel free to subscribe me to it. For more on why this is helpful, please see https://wiki.ubuntu.com/Repo

[Kernel-packages] [Bug 1547204] Re: i915 several 'call traces' in dmesg

2017-03-11 Thread David Dombrowsky
This bug shows up every time I boot linux on this laptop. $ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date 68YGU Ver. F.07 07/28/2006 Text of the error, from dmesg: Mar 11 16:46:13 lappy kernel: [3.260587] WARNING: CPU: 0 PID: 170 at /build/linux-Nasqxe/linux-4.4.0/dr

[Kernel-packages] [Bug 1547204] Re: i915 several 'call traces' in dmesg

2016-07-06 Thread Christopher M. Penalver
Aapo Rantalainen: 1) You don't need to apport-collect any further unless specifically requested to do so. 2) Please provide the output of the following terminal command: sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date 3) To keep this relevant to upstream, could you please tes

[Kernel-packages] [Bug 1547204] Re: i915 several 'call traces' in dmesg

2016-02-29 Thread Aapo Rantalainen
I haven't run older Ubuntu on this machine. Warnings don't happen with mainline kernel 4.2.0-040200-generic. Upgrading BIOS (from 1.13 to 1.15) didn't help. With mainline kernel 4.5: only two warnings: dmesg | grep "cut here" -A 1 [8.852365] [ cut here ] [8.85247

[Kernel-packages] [Bug 1547204] Re: i915 several 'call traces' in dmesg

2016-02-22 Thread Joseph Salisbury
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.5 kernel[0

[Kernel-packages] [Bug 1547204] Re: i915 several 'call traces' in dmesg

2016-02-22 Thread Christopher M. Penalver
** Tags added: bios-outdated-1.15 -- 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/1547204 Title: i915 several 'call traces' in dmesg Status in linux package in Ubuntu: Incomplete Statu

[Kernel-packages] [Bug 1547204] Re: i915 several 'call traces' in dmesg

2016-02-18 Thread Aapo Rantalainen
** Attachment added: "dmesg_4.2.0" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1547204/+attachment/4574908/+files/dmesg_4.2.0 ** Tags added: kernel-bug-exists-upstream ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because

[Kernel-packages] [Bug 1547204] Re: i915 several 'call traces' in dmesg

2016-02-18 Thread Aapo Rantalainen
apport information ** Tags added: apport-collected xenial ** Description changed: Ubuntu 16.04 Kernel: Ubuntu 4.4.0-4.19-generic 4.4.1 There are seven WARNINGS in dmesg during boot. dmesg | grep "cut here" -A 1 [5.916356] [ cut here ] [5.916450] WAR

[Kernel-packages] [Bug 1547204] Re: i915 several 'call traces' in dmesg

2016-02-18 Thread Aapo Rantalainen
** Attachment added: "dmesg_4.4.1" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1547204/+attachment/4574907/+files/dmesg_4.4.1 -- 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/154