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.
h
Running 4.4.0-64 in 16.04. This is definitely a flaky wireless driver.
If I turn it off, and back on I cannot browse any ssids. If I suspend
and resume, I cannot browse any ssids. I have recently added the options
to the /etc/modprobe.d/rtl8821ae.conf file "options rtl8821ae ips=0
fwlps=0" It is im
how about 16.04? It does not hang any more, but the message is still
repeated many times in the dmesg log:
[1.940071] [ cut here ]
[1.940109] WARNING: CPU: 1 PID: 6 at
/build/linux-Ay7j_C/linux-4.4.0/drivers/gpu/drm/drm_irq.c:1326
drm_wait_one_vblank+0x1b5/0x1c0 [
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
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
earlie
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
Int
I have an Inspiron 1525 and among its many problems is low volume. Max volume
feels like half volume at best. Running 14.04 with recent kernel:
3.13.0-40-generic
$ cat /proc/asound/card0/codec* | grep Codec
Codec: Conexant ID 2c06
Codec: Silicon Image SiI1392 HDMI
Codec: SigmaTel STAC9228
$ apl
? 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 repo
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.
https://bugs.launchpad.ne
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 I
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 subscrib
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 n
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 bad
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.
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, but
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 di
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 tracki
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 a
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 ver
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
3500ed90b26a9935b943b5e2e4
So far I have tested 5 back and still have the error. Isn't this what git
bisect is supposed to do? At this rate I'll be compiling for a week, one at
a time.
On Jun 28, 2014 2:55 PM, "KeithG" <1324...@bugs.launchpad.net> wrote:
> it turned up bad.
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 Inspiro
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
(c40e3641670eb6ebfdb7
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 y
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 cont
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
Date: Mon Mar 18 19:44:15 2013 +0100
A
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 version
. Penalver <
christopher.m.penal...@gmail.com> wrote:
> 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 subscribed to the bug
> report.
> https://bugs
s again. I do not remember
which kernel version was the last 'good' one.
Keith
On Tue, Jun 17, 2014 at 6:00 PM, Christopher M. Penalver <
christopher.m.penal...@gmail.com> wrote:
> KeithG, you would actually have to test the fix commit itself in order
> to verify these find
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
[2794b5d408c625e1
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 checkou
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, t
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,
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 me
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 member
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 Rar
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
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, bu
know now? If so, I need a bit more help to
do it.
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
Title:
[Dell Inspiron 1525] WARNING: CPU: 1 PID: 1154 at
/build/buildd
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
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 the
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
call
modeset=0 video.allow_duplicates=1
I no longer get the message in the log. The video does not appear to be
as crisp somehow, but I can suspend and wake from the command line (tty
or terminal) I get a black screen on resume when I allow the UI to
timeout and suspend.
KeithG
--
You received
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 suspe
3.15.0-031500rc7-generic kernel has it as well.
** Tags added: bug exists upstream
** Tags removed: bug exists upstream
** Tags added: kernel-bug-exists-upstream
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://b
Tried latest mainline intel kernel I could find (3.15.0-994-generic) and
same issue. This appears to be from, at least, 13.10 to current kernel.
I got this latest kernel here: http://kernel.ubuntu.com/~kernel-
ppa/mainline/ and selected this one: drm-intel-nightly from 5/30/14
I see that the bot
Public bug reported:
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 hw state do
Tried this tonight with 13.04. Installed the DEB and all seems to be
fine so far. I was getting kernel panic and freeze during periods of
high wifi usage.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
https://bugs.launc
53 matches
Mail list logo
