So I've been busy, but I have some more useful info. I've confirmed the
bug's still in both version 3.5.0-40 (32 bit) and 3.2.0-53 (64 bit) of
the Ubuntu kernel.
However, while I've been busy, I had the idea of just splicing the
changes from Xiao's patch (which we found in the last bisect) into
Hello again, I just thought I would make a quick update. I noticed that
the commit that fixed the mainstream build has been backported into
recent stable kernels. Unfortunately, I'm still seeing the bug on my
32-bit kernel (v3.5.0-37), and while it hasn't popped up for the current
64-bit kernel
** Tags added: bisect-done
** Tags added: cherry-pick
** Description changed:
+ Reverse upstream kernel commit bisecting revealed a fix via commit
+ d34883d4e35c0a994e91dd847a82b4c9e0c31d83 by Xiao Guangrong.
+
WORKAROUND: If I boot my computer from battery power alone without AC,
my GPU
Just finished the reverse bisection (managed to remember that bisect
bad is good and vice versa). It looks like the commit that fixes the
problem is something to do with memory mapping:
d34883d4e35c0a994e91dd847a82b4c9e0c31d83 by Xiao Guangrong
To be safe, I tested the kernel built at that
** Attachment added: Reverse Bisection Log
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1009312/+attachment/3710622/+files/bisect-log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1009312
Kyle Auble, thank you for performing the requested tests. The next step
would be to perform a reverse mainline kernel commit bisect in order to
find the earliest mainline kernel commit that fixed your problem. Could
you please do this following
https://wiki.ubuntu.com/Kernel/KernelBisection ?
**
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
** Tags removed: needs-upstream-testing
** Tags added: kernel-fixed-upstream kernel-fixed-upstream-v3.10-rc4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Huzzah, I think you all got it! I finally found the time to do a
separate install of i386 Ubuntu on the end of my harddisk for testing
the 32bit version of the mainline kernel.
When I boot the 32bit version with the default kernel (v3.5), the GPU
still doesn't load, but with kernel v3.10-rc4,
Sure, can do.
Because the bug seems to lie dormant most of the time in the 64-bit
build, I've tried both the 32 64 bit versions of Saucy Salamander. I
tried the 64 bit version 4 times without seeing the bug, but it popped
right up with the 32 bit version. I'll run apport from within the 32 bit
apport information
** Tags added: saucy
** Description changed:
WORKAROUND: If I boot my computer from battery power alone without AC,
my GPU the Ubuntu splash screen load on startup.
I've been running Ubuntu 12.04 for a few weeks now, I really like it,
but from the beginning, I had
Kyle Auble, could you please confirm this issue exists with the latest
development release of Ubuntu Saucy Salamander? ISO images are available
from http://cdimage.ubuntu.com/daily-live/current/ . If the issue
remains, could you please run the following command in the development
release from a
I know it's been a while, but I thought I should report that I've still
been seeing this bug. I recently installed a fresh mainline kernel
(3.9.0-999-generic, built on 4/21), and it runs fine except I'm still
seeing the bug. I want to try some of the ACPI options again when
booting, but my problem
Hello, I've been away from a while, but I just wanted to see if there
was anything I could still do to help with this bug. I haven't had a
problem with it for a few weeks, but I did have one weird startup this
morning when my monitor simply didn't come on.
I moved to one of the beta Nvidia
** Tags added: regression-release
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1009312
Title:
GPU loads unreliably, possible kernel timeout
To manage notifications about this bug go to:
Kyle Auble, thank you for providing the requested attachments.
Regarding your comments
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1009312/comments/41 :
Kernel log of a failed suspend attempt (123.2 KiB, text/plain)
Let us not introduce suspend problems, and accompanying attachments,
I finally had another bad reboot and remembered to run the ACPI
debugging steps. However a diff on the output of `sudo dmidecode` showed
no differences from the one in a good session, and the only difference
in the /proc/acpi files was that in battery/BAT0/info, my battery's
design voltage was
Also, there were several differences in the output of `sudo lspci -vvnn`
between the good and the bad sessions. For several of the devices, there
seems to be a consistent change in the MAbort flag between the good and
bad session, although PresDet switched for the Root Port, the Audio
Controller
I have been busy lately, but I've searched Launchpad a little and found
one other expired bug that I felt confident enough to label a duplicate.
I also came across Bug #940564, which while I don't think it's an exact
duplicate, seems to have a lot of similarities to this one. That one is
currently
It's strange, but the bug hasn't appeared again yet. I've tried a few
more random things, but nothing seems to make it come up again. I
suppose it's always possible that one bad session was a complete
outlier, but since I can't consistently replicate the bug now in 64bit
Ubuntu, I can't really
Kyle Auble, please provide the attachments requested in
https://wiki.ubuntu.com/DebuggingACPI#Filing_a_Bug_Report without any of
the suggested kernel parameters in place and from a session where the
bug does not appear.
--
You received this bug notification because you are a member of Ubuntu
** Attachment added: Output of `uname -a`
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1009312/+attachment/3314917/+files/uname
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1009312
** Attachment added: Output of `sudo lspci -vvnn`
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1009312/+attachment/3314918/+files/lspci
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: Output of `sudo dmidecode`
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1009312/+attachment/3314919/+files/dmidecode.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I wasn't able to follow the exact instructions on the wiki page because
my system is just appending different sessions to the main kernel log,
instead of archiving old log files. I've cut out all of the earlier
sessions so it should just be of the most recent one, including a test
of suspend and
** Attachment added: Tarball of /proc/acpi
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1009312/+attachment/3314921/+files/acpi.tar.bz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1009312
Arrrgh, spoke too soon. After several reboots that went fine, I just
booted up the computer, the splash screen failed to show, and I'm now in
Unity 2D without my GPU. I'm really out of ideas as to what could be
going on.
I diffed the dmesg logs again, and after the times have been stripped,
the
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1009312
Title:
GPU loads unreliably, possible kernel timeout
To manage
** Tags added: amd64
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1009312
Title:
GPU loads unreliably, possible kernel timeout
To manage notifications about this bug go to:
Kyle Auble, thank you for testing for this in Quantal.
Could you please provide the information following
https://wiki.ubuntu.com/DebuggingACPI ?
** Changed in: linux (Ubuntu)
Status: Confirmed = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I'm now running the AMD64 version of Precise from the hard-disk, and
over several reboots, the GPU has been loading without any problems. It
looks like dropping the PAE version of the kernel fixed things for me. I
don't know if whatever was happening was due to the mismatch between the
32bit OS
What do you know? I tried booting the 64bit version of Quantal from a
Live USB multiple times, and the splash screen consistently appeared.
Now I wasn't able to check the logs because the screen would then freeze
(as I mentioned in my last post, that may be a bug in Quantal's
graphics).
However,
apport information
** Tags added: apport-collected quantal running-unity
** Description changed:
WORKAROUND: If I boot my computer from battery power alone without AC,
my GPU the Ubuntu splash screen load on startup.
I've been running Ubuntu 12.04 for a few weeks now, I really like
I finally picked up a spare USB thumb drive and set it up as a Live USB
with the Aug 31 build of Quantal. Just to be sure, I went back and
checked with my old Precise Live CD, and the bug appears for both
versions in a live boot too. While both live-boots also respond to the
boot-from-battery
I've been busy recently, and probably won't be able to test the Ubuntu
build right away. I only have spare CD-Rs right now, but the download
page says that the daily build of Quetzal is currently too large to burn
to CD.
I'll keep checking, and once I have a spare USB drive or some DVD-Rs, or
the
Kyle Auble, thank you for testing the newest mainline.
Could you please confirm this issue exists with the latest development
release of Ubuntu? ISO CD images are available from
http://cdimage.ubuntu.com/daily/current/ . If the issue remains, could
you please run the following command in the
Sorry about the tags, I guess I did something wrong or don't have access
to the email interface
** Tags removed: kernel-unable-to-test-upstream needs-upstream-testing
** Tags added: kernel-bug-exists-upstream
kernel-bug-exists-upstream-v3.5-rc7-quantal
--
You received this bug notification
Kyle Auble, this bug was reported a while ago and there hasn't been any
activity in it recently. We were wondering if this is still an issue? If so, :
+ Did this issue not occur in prior Ubuntu releases?
+ As well, could you please test upstream kernel
After paying attention to how my computer boots, I've finally found a
consistent relationship. If I boot my computer from battery power alone
without AC, my GPU the Ubuntu splash screen load on startup. However,
if I start my laptop on AC power, with or without the battery connected,
it seems to
I can now also confirm that suspend works perfectly with the nvidia
driver loaded
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1009312
Title:
GPU loads unreliably, possible kernel timeout
To
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.5kernel[0] (Not a kernel in the daily directory) and install both the
linux-image and linux-image-extra .deb packages.
Once you've tested the
** Tags added: kernel-unable-to-test-upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1009312
Title:
GPU loads unreliably, possible kernel timeout
To manage notifications about this bug go
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1009312
Title:
GPU loads unreliably, possible kernel timeout
To manage
I just tried booting into the newest 3.5 release candidate (dated from
June 2nd), and it choked somewhere between starting up my wireless card
and reaching a login screen. While installing the mainline kernel, dpkg
actually printed an error about not being able to build the nvidia
module against
** Attachment added: A dmesg log showing a fallback onto VESA
https://bugs.launchpad.net/bugs/1009312/+attachment/3177035/+files/baddmesg.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1009312
** Attachment added: A Xorg log showing a fallback onto VESA
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1009312/+attachment/3177057/+files/badxorg.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: A jockey error log from a fallback to VESA
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1009312/+attachment/3177058/+files/badjockey.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: linux (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1009312
Title:
GPU loads unreliably, possible kernel timeout
To manage notifications
47 matches
Mail list logo
