Just wanted to add here that I think I've found an even simpler
workaround. It looks like passing "pci=bios" as a kernel parameter
consistently allows the GPU to load, regardless of kernel version or
power source. I haven't tested it a whole lot, but so far it has worked
100%.
--
You received thi
It's been a while, but I've found the time to dig much deeper into this
and familiarize myself with the kernel code some. Actually, I feel
comfortable with the idea of directly contacting the appropriate mailing
list now so this is more to keep the record up-to-date than a request
for more triage.
Hmm... so I've just finished a first set of tests with reverting that commit,
and I definitely have results, though they aren't as cut-and-dry as I hoped.
When I reverted the commit, there were merge conflicts in:
drivers/acpi/scan.c
drivers/dma/acpi-dma.c
Since I really have no clue how these f
So after another couple of months, I've managed to do more testing, and
I may have found something useful. First off, two fresh, stable versions
of the Ubuntu kernel have shown the bug: v3.2.0-56 (64-bit) and
v3.5.0-44 (32-bit). Also, the most recent package from the Ubuntu
mainline kernel PPA, v3.
I was a little confused about exactly which version of the kernel you
wanted to test, but it's a moot point because all of the ones I tried
had the bug still.
I'm still using Ubuntu 12.04 so sudo apt-get dist-upgrade just keeps me
on v3.5.0-40, which definitely has the bug. I also tested v3.11-rc1
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 th
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 yet
** 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
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 comm
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, ever
** 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.
https://
apport information
** Attachment added: "UdevLog.txt"
https://bugs.launchpad.net/bugs/1009312/+attachment/3693033/+files/UdevLog.txt
--
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:
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1009312/+attachment/3693034/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1009312
Ti
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1009312/+attachment/3693030/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/100
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1009312/+attachment/3693026/+files/IwConfig.txt
--
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:
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1009312/+attachment/3693025/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1009312
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1009312/+attachment/3693031/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1009312
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1009312/+attachment/3693028/+files/Lsusb.txt
--
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
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1009312/+attachment/3693032/+files/UdevDb.txt
--
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:
GP
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
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1009312/+attachment/3693024/+files/CRDA.txt
--
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 lo
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1009312/+attachment/3693027/+files/Lspci.txt
--
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
apport information
** Attachment added: "BootDmesg.txt"
https://bugs.launchpad.net/bugs/1009312/+attachment/3693023/+files/BootDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1009312
Titl
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1009312/+attachment/3693029/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1009312
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
v
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 drivers
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
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 ha
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 list
** 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/100931
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 aw
** 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.
https://bugs.launchpad.net/bugs
** 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.
https://bugs.launchpad.net/bugs/10093
** 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
Titl
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 test
I just came across this report, and while I'm not having problems with
black screens or failed shut-downs so much, I have a similar set-up to
the original reporter: Nvidia 8400M GT, Core 2 Duo, and I've been having
problems with the GPU failing to activate (see Bug #1009312). It seems
to be happeni
*** This bug is a duplicate of bug 1009312 ***
https://bugs.launchpad.net/bugs/1009312
** This bug has been marked a duplicate of bug 1009312
GPU loads unreliably, possible kernel timeout
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** 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 notificatio
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 on
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 and
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, I
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" wor
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1009312/+attachment/3289861/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1009312
Ti
apport information
** Attachment added: "UdevLog.txt"
https://bugs.launchpad.net/bugs/1009312/+attachment/3289860/+files/UdevLog.txt
--
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:
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1009312/+attachment/3289859/+files/UdevDb.txt
--
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:
GP
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1009312/+attachment/3289858/+files/PulseList.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1009312
Titl
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1009312/+attachment/3289857/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1009312
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1009312/+attachment/3289856/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/100
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1009312/+attachment/3289855/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1009312
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1009312/+attachment/3289854/+files/Lsusb.txt
--
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
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1009312/+attachment/3289853/+files/Lspci.txt
--
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
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1009312/+attachment/3289852/+files/IwConfig.txt
--
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:
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1009312/+attachment/3289851/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1009312
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1009312/+attachment/3289850/+files/CRDA.txt
--
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 lo
apport information
** Attachment added: "BootDmesg.txt"
https://bugs.launchpad.net/bugs/1009312/+attachment/3289849/+files/BootDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1009312
Titl
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 it
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
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 beca
Before using Ubuntu 12.04, I was running Xubuntu 11.10. Although,
I didn't use Unity, the computer would detect my GPU, load the
nvidia driver module, and I was able to use higher resolutions.
However, I didn't have the newest version of the kernel because
starting around version 3.2.0-15 my comput
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 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 th
** 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 notificatio
** 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 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 manag
** 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.
https://bugs.la
** 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.
https://bugs.launchp
** 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
Public bug reported:
I've been running Ubuntu 12.04 for a few weeks now, I really like it,
but from the beginning, I had the issue where the proprietary nvidia
driver installs but fails to load (confirmed from the commandline,
jockey, and the nvidia-dashboard). Over time, I've noticed that
sometim
69 matches
Mail list logo
