Fix released! Awesome. Is there a link to anything that will allow me to
verify that it is fixed? Is it in the current 16.04 kernel? 16.10?
17.04? Upstream?
Thanks.
Keith
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Changed in: linux (Ubuntu)
Status: Triaged => Fix Released
--
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/1324935
Title:
[Dell Inspiron 1525] WARNING: CPU: 1 PID: 1154 at
ethany,
I do not really remember. Try 13.04 (and 12.04 if it is still in 13.04).
It was one of those, IIRC, that did not have it. Problem is that so much
has changed in the kernel since then. I went through a huge kernel
bisect project to then be told to report it to the kernel i915 group and
got
see attached Kernel 3.19 dmesg snippet (for comparison).
** Attachment added: "dmesg snippet for 3.19"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1324935/+attachment/4540600/+files/dmesg_3.19.txt
--
You received this bug notification because you are a member of Kernel
Packages,
Adding dmesg for latest mainline kernel at http://kernel.ubuntu.com
/~kernel-ppa/mainline/drm-intel-nightly/current/ -- the error differs
slightly in reporting. Will attach 3.19 snippet as well.
** Attachment added: "Dmesg for
also reported here: https://bugs.freedesktop.org/show_bug.cgi?id=93511
** Bug watch added: freedesktop.org Bugzilla #93511
https://bugs.freedesktop.org/show_bug.cgi?id=93511
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
KeithG,
I have the same problem with my Dell Inspiron 1525. Upgraded from Debian Wheezy
to Debian Jessie, and started getting very similar error messages:
Dec 26 09:57:56 localhost kernel: [ 1017.555709] Pid: 1212, comm: Xorg
Tainted: GW3.8.0 #1
Can you post your kernel .config
attaching additional debug info
** Attachment added: "kernel drm debug parameter enabled"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1324935/+attachment/4540601/+files/dmesg_drm.debug%3D0xe.txt
--
You received this bug notification because you are a member of Kernel
Packages,
https://bugzilla.kernel.org/show_bug.cgi?id=81291 might be related?
--
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/1324935
Title:
[Dell Inspiron 1525] WARNING: CPU: 1 PID: 1154 at
KeithG, the issue you are reporting is an upstream one. Could you please
report this problem following the instructions verbatim at
https://wiki.ubuntu.com/Bugs/Upstream/kernel to the appropriate venue
(TO Daniel Vetter and Jani Nikula CC intel-gfx)?
Please provide a direct URL to your newly made
KeithG, could you please test drm-intel-nightly and advise to the
results?
--
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/1324935
Title:
[Dell Inspiron 1525] WARNING: CPU: 1 PID: 1154
I still get this:
[1.968043] [ cut here ]
[1.968074] WARNING: CPU: 0 PID: 85 at
/home/kernel/COD/linux/drivers/gpu/drm/drm_irq.c:1216
drm_wait_one_vblank+0x1b5/0x1c0 [drm]()
And it is way laggy. 15.10 is unusable for me with any of these kernels
(stock, latest,
Christopher,
I grabbed kernel 4.4.0-040400rc3-generic as it shows as the latest. I
installed it and get the same messages in the dmesg log. I do note that
the fans are not running so fast. I have been having problems where it
will overheat and shut down. Never had that problem with 15.04 or
KeithG:
>"I do not know why it is tainted..."
It's a kernel that has been modified from what was provided upstream.
>" What further information do I need to send?"
It was requested of you in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1324935/comments/76
to test the latest mainline
Just loaded ubuntu 15.10 (kernel 4.2.0-18-generic) and it is still
there.
Interestingly, I have this as well:
CPU: 1 PID: 1276 Comm: Xorg Tainted: GW 4.2.0-18-generic
#22-Ubuntu.
I do not know why it is tainted as I did not install any private
modules. on the 'Software & Updates"
Just upgraded to 15.04. I still get the error and sometimes it will not
shut down and takes a long time to reboot.
Is this just that the i915 driver is not very good or that my hardware
is not well supported?
# lspci
...
00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960
KeithG, to confirm this is a downstream only issue, could you please
test the latest mainline kernel (4.1.1) and advise to the results?
** Tags added: vivid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
As per your instructions, I have submitted bug report. Following is the
link
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1406982
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Hi there, I am also facing the same issue. I have Dell Inspiron 1525 running
14.04.1 LTS and kernel version 3.13.0-39-generic.
System becomes unusable completly and screen goes off as well. Following is
what i have found in dmesg
[ 47.428521] WARNING: CPU: 1 PID: 1146 at
Gurvinder Dadyala, thank you for your comment. So your hardware and problem may
be tracked, could you please file a new report with Ubuntu by executing the
following in a terminal while booted into the default Ubuntu kernel (not a
mainline one) via:
ubuntu-bug linux
For more on this, please
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
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/1324935
Title:
[Dell Inspiron 1525] WARNING: CPU: 1 PID: 1154 at
The report by Keith wasn't invalid. ALL Ubuntu since 14.XX and derivates
of it (like Linux Mint 17) get this issue. The result of this issue is a
total freeze of the computer (all devices when the freeze comes are
disabled).
I got the same log as KeithG. Apparently X.Org was the source of the
According to this, and after execute uname -r to see versions of
kernel that they are, freezes now appear to occur very
frequently/everyday with kernel versions after 3.2.1
Report on Fedora :
https://bugzilla.redhat.com/show_bug.cgi?id=786879
brendan.moyni...@tangotelecom.com 2012-02-03 05:25:08
How can we use an old version of kernel package to test the report of
brendan on Fedora?
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = J.G (jg-imbert)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
J.G, please do not assign yourself to a bug report unless you are going
to release a fix patch imminently, as outlined in
https://wiki.ubuntu.com/Bugs/Status .
Despite this, if you have a problem in Ubuntu, and so your hardware and problem
may be tracked, please file a new report with Ubuntu by
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
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/1324935
Title:
[Dell Inspiron 1525] WARNING: CPU: 1 PID: 1154 at
So why you won't repair this bug ? It's useless to change the status as
incomplete. The status is confirmed by these informations. The bug came
from one of these cases : Kernel, X.Org or the both. The bug is not on
the hardware but on the software.
The bug is confirmed too around the Web in ALL
And it's useless to create a new report. The bug, even if I use a
different video card (here NVIDIA), is the same for all video cards
compagnies (ATI, Intel, NVIDIA, ...) like KeithG had.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
The log file :
Nov 17 16:57:36 jackobo-MS-7616 kernel: [ 41.127845] nvidia :01:00.0: irq
35 for MSI/MSI-X
Nov 17 16:57:37 jackobo-MS-7616 kernel: [ 41.799569] NVRM: Your system is not
currently configured to drive a VGA console
Nov 17 16:57:37 jackobo-MS-7616 kernel: [ 41.799575]
See this :
Nov 17 16:57:37 jackobo-MS-7616 kernel: [ 41.921988] CPU: 1 PID: 1603
Comm: Xorg Tainted: P W OE 3.18.0-031800rc4-generic #201411091835
If you don't see that Xorg or Kernel have an issue, so I don't know how
to prove it to you.
--
You received this bug notification because you
J.G, just to clarify, this report is not scoped to you, your hardware,
or your problem. if you want your bug addressed, please again see
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1324935/comments/67
.
** Changed in: linux (Ubuntu)
Status: Confirmed = Incomplete
--
You received
? I do not fully understand your request. As you said, this was a
failure to resume bug. That bug has been resolved. I am currently
running the current kernel with ubuntu 14.04 and allowing it to update
as time progresses. (apt-get dist-upgrade)
I still have tons of errors in my dmesg. I have
KeithG, just to clarify, if you may now resume in the default trusty
kernel (not upstream) then please feel free to mark this bug report
status Invalid.
Regarding errors in dmesg, this is out of scope for this report. However, if
the errors are correlated to some sort of impact on features,
KeithG, the next step is to fully reverse commit bisect from kernel
3.16-rc6 to 3.16 in order to identify the last bad commit, followed
immediately by the first good one. Once this commit has been identified,
then it may be reviewed as a candidate for backporting into your
release. Could you
3.16.0 - still messages in the log, but it will now suspend and resume
with ubuntu GNOME 14.04 and the 3.16.0 kernel
--
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/1324935
Title:
[Dell
** Tags added: kernel-fixed-upstream-3.16
** Tags added: needs-reverse-bisect
--
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/1324935
Title:
[Dell Inspiron 1525] WARNING: CPU: 1 PID:
I don't think it is 'fixed' as I still get my log filled with the error
message, but I can use hardware acceleration and it will suspend and
resume.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
KeithG, the scope of this report is your ability to suspend/resume.
--
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/1324935
Title:
[Dell Inspiron 1525] WARNING: CPU: 1 PID: 1154 at
I finished the bisect. I am running xubuntu 14.04. I pulled mainline
kernels v3.6 which worked without error and v3.7 which exhibited the
error. I then bisected between the 2. It took 14 steps and concluded
with this which makes more sense:
24929352481f085c5f85d4d4cbc919ddf106d381 is the first
The dmesg from this version of the kernel (different line number in the
*.c file) is attached.
Keith
** Attachment added: dmesg output from the failed commit
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1324935/+attachment/4163777/+files/249293_dmesg.txt
--
You received this bug
KeithG, last check, could you please test the latest mainline kernel via
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.16-rc6-utopic/ and
advise to the results?
** Tags removed: needs-bisect
** Tags added: bisect-done
** Changed in: linux (Ubuntu)
Status: Incomplete = Triaged
--
You
yes, it is still present. dmesg attached.
** Attachment added: dmesg with 3,16-rc6
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1324935/+attachment/4163968/+files/dmesg-3.16_rc6.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is
KeithG, the issue you are reporting is an upstream one. Could you please
report this problem through the appropriate channel by following the
instructions _verbatim_ at https://wiki.ubuntu.com/Bugs/Upstream/kernel
?
Please provide a direct URL to your e-mail to the mailing list once you
have made
Can you explain something to me. Does v3.6.0-rc7 come before v3.6.0? I
thought that release candidates preceeded the release. I am running yet
another bisect, this time good is v3.6 and bad is v3.7. I cannot tell
where bisect is in the tree while it is running, it just reports UUIDs
as it runs,
Now I am at step 8 and the kernel is linux-image-3.5.0-rc4. What am I
doing wrong? I would guess that the first bisect would be 3.6.x
(somewhere between v3.6.0 and v3.7.0).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Since I was unable to successfully use git bisect, I decided to take
another tack. I am running 14.04 no mods or edits, just a simple unstall
of Xubuntu. I installed the b43 driver so the wifi works. If I try to
install and 'install updates', the install crashes. I installed then did
an 'apt-get
fwiw, I grabbed the latest kernel and the bug is still there. I built
v3.16.0-rc5 and still get this filling the log:
l WARNING: CPU: 1 PID: 1143 at drivers/gpu/drm/i915/intel_display.c:10101
intel_modeset_check_state+0x5f3/0x7a0 [i915]()
[ 115.283641] encoder's hw state doesn't match sw
** Tags removed: kernel-bug-exists-upstream-3.15-rc7
** Tags added: kernel-bug-exists-upstream-3.16-rc5
--
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/1324935
Title:
[Dell Inspiron
This is too far out of my league. I need more guidance. This bug appears
to be imtermittent. I have certain kernels which have never exhibited
this error in the dmesg. I have others which sometimes show it. I have
built well over 30 kernels on this laptop and it is like trying to find
a needle in
I kept seeing it and eventually built v3.8.0 and it 'appeared' to not
show the error. I thought I had found it and started another bisect
between the commits for v3.8.0 and v3.8.1, but when I tried to boot back
to v3.8.0, the error in the log showed up. It was not there previously.
Now if I reboot
I have no clue what is going on. I have started building kernels from
v3.8.13 and back. So far all fail. I am at v3.8.7 and still have the
dmesg error. It is not clear from the ubuntu kernel to mainline map as
to which is/should be the version that I have on there which works
without error. The
I rebooted to 14.04 again and built the kernel from that commit,
installed and rebooted 14.04 and the error still shows in the log.
Previously, I was using 13.04 as the base. I guess I will continue to
buils kernels backwards from here until it goes away. Any other
suggestions? I wonder if this is
I started with commit c40e36... and worked back according to the git
log. The last 'good' build was fb72a0... The next commit breaks it.
c40e3641670eb6ebfdb71d4b0c775416ef95f4f0 bad
e651eab0af88aa7a281fe9e8c36c0846552aa7fc bad
7fb476c231bbc551ede5b4afb189d9ca5ab7406d bad
KeithG, did you actually test the commit to verify the proble exists,
and test one commit older to verify it's gone?
--
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/1324935
Title:
[Dell
Yes. Bisecting between commits actually did that for me. My 8th pass
used commit c40e3641670eb6ebfdb71d4b0c775416ef95f4f0 which was 'good'
and was the next older commit. The next newer commit was the 9th pass
which used commit 8164f7af88d9ad3a757bd14f634b23997ee77f6b which was
'bad'. Should I
It seems odd as the diff shows only changes to the arm branch of the
code. the result of the lshw command are attached.
** Attachment added: lshw
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1324935/+attachment/4141378/+files/lshw.txt
--
You received this bug notification because
KeithG, allow me to rephrase my question. Just to be clear, git
bisecting doesn't verify if the problem was in the commit or not. What
verifies it is actually building a kernel against that commit, and then
testing it to verify the git bisect results. So my question is did you
actually build the
Christoper, I am not sure. My second git bisect was done using commits
as the end points and not versions. I tracked the commit numbers as
bisect did its work and it appeared that the 8th run actually built to
that commit. I have done a git pull to the commit right before this
it turned up bad. I am going one back from that.
e651eab0af88aa7a281fe9e8c36c0846552aa7fc. and will test that.
--
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/1324935
Title:
[Dell
Christopher.
I used the commit numbers and did the bisect again. Now it points to one
commit which causes the error:
8164f7af88d9ad3a757bd14f634b23997ee77f6b is the first bad commit
commit 8164f7af88d9ad3a757bd14f634b23997ee77f6b
Author: Stephen Boyd sb...@codeaurora.org
Date: Mon Mar 18
Christopher.
I think know how to do those steps. Is it important that I git clone
again? Should my repository be linux-stable? Mine is currently ~/linux
I was able to build commit ed34add734e33afa33e7bf5ee5826650efdc0fe8 and
that works.
I am confused as to how to go about selecting which
KeithG, following
https://wiki.ubuntu.com/Kernel/KernelBisection#Commit_bisecting_upstream_kernel_versions
it's going to look something like:
sudo apt-get -y install git build-essential kernel-package fakeroot
libncurses5-dev cd $HOME git clone
I guess the bisect has run to its completion. 10 trials between v3.9 and
v3.10. The output of my last 'git bisect bad' is this:
The merge base c1be5a5b1b355d40e6cf79cc979eb66dafa24ad1 is bad.
This means the bug has been fixed between
c1be5a5b1b355d40e6cf79cc979eb66dafa24ad1 and
KeithG, you would actually have to test the fix commit itself in order
to verify these findings.
--
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/1324935
Title:
[Dell Inspiron 1525]
KeithG, you would just build your kernel up to a commit in the middle
and see where you stand specifically.
--
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/1324935
Title:
[Dell Inspiron
Am now getting full builds with modules. Still no 4th decimal. There is
some disconnect, though, between the Ubuntu Kernels and the Mainline
kernels. All V3.8.x kernels build and do not exhibit the error. The V3.9
Kernel does not exhibit the error. The v3.8.15 does, though. I am
building the v3.10
Poked around some more and was able to get other versions in my copy of
the mainline kernel.
this command got me some more kernel versions:
git remote set-url origin
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
now, when I 'tab' to see what is there, I get:
$ git
Ok, Something is going wrong. It stalled at 3.8.0-26.38. It is 'good',
but when I go and do 'git bisect good', it does some stuff and returns
and appears to have a new version to build. WHen I build it, it is the
same version 3.8.0-26.38.
--
You received this bug notification because you are a
Please help! I am trying to follow the instructions to find this bug and am a
bit lost. I have determined that this bug is between 3.8.0-26.38 and
3.8.0-28.42. These do not 'map' to the Mainline kernel map, directly. so I am
guessing near these 2 end points. Following the Mainline instructions,
KeithG, following the mapping as noted in
https://wiki.ubuntu.com/Kernel/KernelBisection#Map_Ubuntu_kernel_to_Mainline_kernel_for_mainline_bisection
you would want to bisect the upstream (not Ubuntu) kernel between
3.8.13.2 and 3.8.13.5 .
--
You received this bug notification because you are a
Christopher,
I Appreciate the help and apologize for being so dense. I think I get it, but
am still a bit lost with the mainline kernel. From the kernel mapping, I see
the 2 kernel versions you are referring to. I have git cloned the kernel. When
I try to tell it that I want 3.8.13.2, though,
I figured it out. I was able to start over. The key is to not edit any
of the files as it bisects. The revision numbers are good enough for me
to keep track of where I am. As it is, I have done 4 or 5 bisects and am
narrowing it down.
--
You received this bug notification because you are a
keith G, you would want to map the Ubuntu kernel to the mainline one via
http://kernel.ubuntu.com/~kernel-ppa/info/kernel-version-map.html and
then switch to bisecting the mainline kernel following
https://wiki.ubuntu.com/Kernel/KernelBisection#How_do_I_bisect_the_upstream_kernel.3F
.
--
You
This is extremely confusing. 1) The kernels I am using do not appear in
that mainline map (version numbers are just not there) 2) I'd rather
just keep going with my first attempt. 3) the example on the
https://wiki.ubuntu.com/Kernel/KernelBisection apparently uses a older
version of git than in
I tried 12.10 and 13.04. 12.10 appears to work. Initial install of 13.04
appears to work. When I dist-upgraded 13.04 after I installed it, I got
the warning in the log. I think I have narrowed it down to this release.
I was going to respond with the kernel versions at beginning and end of
13.04,
KeithG, you were very close. You would want:
git bisect start Ubuntu-3.8.0.19-29 Ubuntu-3.8.0.35-50
--
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/1324935
Title:
[Dell Inspiron 1525]
Ok, I did my first bisect with 3.8.0-28.42 and it came up bad. Now I am
here:
$ git bisect bad
Bisecting: 388 revisions left to test after this (roughly 9 steps)
error: Your local changes to the following files would be overwritten by
checkout:
debian.master/changelog
Please, commit your
Christopher,
I am willing to do this, but need a bit more hand holding to do it. I
have collected the ubuntu-saucy abd ubuntu-precise kernel folders. I am
trying to follow the example, but do not get very far.
What I think I know: linux 3.2.0.63-generic works well. This is the
latest kernel from
Keith G, you could techncially begin git bisecting between 3.2 and 3.11,
you may want to try 12.10/13.04 first to further narrow it down more
quickly.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I loaded 12.04 amd64 on it this morning. This appears to work correctly.
I can suspend and resume with no issues. There is no warning in the log
other than the 'duplicate interface' which does not seem to affect
anything. I have not upgraded anything, just installed xubuntu 12.04
then installed
KeithG, the next step is to fully commit bisect the kernel in order to
identify the offending commit. Could you please do this following
https://wiki.ubuntu.com/Kernel/KernelBisection ?
** Tags removed: regression-potential
** Tags added: needs-bisect regression-release
--
You received this bug
I have started the process. Strange that this bug has crept in and no
one has noticed. It is pretty limiting, actually.
KeithG
--
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/1324935
Just installed it and checked dmesg and this warning was there. I
recently got this computer and have only tried 13.10 and 14.04. THis si
after a cold boot. If I try to suspend, it appears to suspend correctly.
When I resume, it has black screen. I have done a ton of updates, so I
need to try
KeithG, regarding your Dell Inspiron 1525, for regression testing
purposes, could you please test 12.04.0 via http://old-
releases.ubuntu.com/releases/12.04.0/ and advise to the results?
As well, so you have an additional Dell computer, a 1425? If so, please file a
new report about that via a
Actually, that was mis-typed. It is only one and the computer is a Dell
Inspiron 1525.
I will not get to testing with 12.04 today. I did make a couple of
config edits and no longer get that message in the log.
I edited /etc/initramfs-tools/modules I added these parameters after the i915
module
** Description changed:
Dmesg is filled with this:
[32582.450283] [ cut here ]
[32582.450302] WARNING: CPU: 1 PID: 1154 at
/build/buildd/linux-3.13.0/drivers/gpu/drm/i915/intel_display.c:9226
intel_modeset_check_state+0x62d/0x780 [i915]()
[32582.450304] encoder's
If I set modeset=1 or -1, I get the crash on resume. Black screen on all
ttys and no reconnect to network (I cannot ssh back in).
modeset = 0 will allow normal function, but no KMS.
KeithG
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
87 matches
Mail list logo
