[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/60243
Vassilis Pandis, thank you for reporting this and helping make Ubuntu better.
Gutsy reached EOL on April 18th, 2009.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We were wondering if this is still an issue in a supported release? If
so, could
** Changed in: linux-source-2.6.20 (Ubuntu)
Assignee: Registry Administrators (registry) = (unassigned)
** Changed in: linux-source-2.6.17 (Ubuntu)
Assignee: Registry Administrators (registry) = (unassigned)
** Changed in: linux (Ubuntu)
Assignee: Registry Administrators
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: dirk 1464 F pulseaudio
/dev/snd/pcmC0D0p: dirk 1464 F...m pulseaudio
CRDA: Error: [Errno 2] No such file or directory
There have been no updates or activity on this bug for over a year. Does
the behavior still occur under Karmic (or under the Lucid beta)?
If so, please run the command
apport-collect -p linux 60243
in a terminal window.
If anyone is experiencing a similar problem - but not this exact
** Tags added: suspend
** Tags added: resume
** Tags added: intrepid
** Tags added: jaunty
** Tags added: hardy
--
Does not resume from suspend
https://bugs.launchpad.net/bugs/60243
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Assigned to ubuntu-kernel-acpi as per [1]. Tested against 2.6.28-2; also
affects 2.6.27.
(Importance not set as I do not have that access.)
[1]
https://wiki.ubuntu.com/KernelTeamBugPolicies#Confirmed%20bugs%20are%20assigned%20to%20teams
** Changed in: linux (Ubuntu)
Assignee: (unassigned)
ok i tested it on the new jaunty
** Attachment added: uname.txt
http://launchpadlibrarian.net/20290452/uname.txt
--
Does not resume from suspend
https://bugs.launchpad.net/bugs/60243
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: lspci.txt
http://launchpadlibrarian.net/20290453/lspci.txt
--
Does not resume from suspend
https://bugs.launchpad.net/bugs/60243
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Attachment added: dmidecode.txt
http://launchpadlibrarian.net/20290461/dmidecode.txt
--
Does not resume from suspend
https://bugs.launchpad.net/bugs/60243
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
** Attachment added: kern.log.0
http://launchpadlibrarian.net/20290520/kern.log.0
--
Does not resume from suspend
https://bugs.launchpad.net/bugs/60243
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Attachment added: acpi.tar.bz
http://launchpadlibrarian.net/20290529/acpi.tar.bz
--
Does not resume from suspend
https://bugs.launchpad.net/bugs/60243
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
attached info
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
Does not resume from suspend
https://bugs.launchpad.net/bugs/60243
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Shawn, since you may have a different laptop than the one on which this
problem was originally reported, can you please follow the procedures in
[1] and [2] and attach relevant debugging and diagnostic information?
Thanks!
[1] https://wiki.ubuntu.com/DebuggingACPI
[2]
yes, I just tested it with Intrepid 2.6.27-7 kernel. It is still a bug.
--
Does not resume from suspend
https://bugs.launchpad.net/bugs/60243
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
The 18 month support period for Feisty Fawn 7.04 has reached it's end of
life - http://www.ubuntu.com/news/ubuntu-7.04-end-of-life . As a result
we are closing the linux-source-2.6.20 task.
Shawn, is this still an issue with the final Intrepid release which
contains a 2.6.27-7 kernel? Thanks.
this is still a bug in intrepid using the nv driver it just shows a black
screen after resuming from suspend, but if I use the nvidia driver it works
fine.
intrepid-laptop:~$ uname -a
Linux intrepid-laptop 2.6.27-2-generic #1 SMP Thu Aug 28 17:20:02 UTC 2008 i686
GNU/Linux
--
Does not resume
The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the
upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would
appreciate it if you could please test this newer 2.6.27 Ubuntu kernel.
There are one of two ways you should be able to test:
1) If you are comfortable
The 18 month support period for Edgy Eft 6.10 has reached it's end of
life. As a result, we are closing the linux-source-2.6.17 Edgy Eft
kernel task. However, please note that this report will remain open
against the actively developed kernel. Thank you for your continued
support and help as we
Hardy Heron 8.04 was recently released. It would be helpful if you
could test the new release and verify if this is still an issue -
http://www.ubuntu.com/getubuntu/download . You should be able to test
your bug using the LiveCD. Please let us know your results. Thanks.
** Changed in: linux
Still an issue on gutsy.
--
Does not resume from suspend
https://bugs.launchpad.net/bugs/60243
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Jos:
I guess I was wondering whether the nvidia binary driver might be interfering
with serio_raw thus causing your issue. If the same problem happened with the
nv Xorg driver then that explanation could be completely ruled out.
--
Does not resume from suspend
Even though the serio_raw driver was put in the MODULES list in
/etc/default/acpi-support, yesterday I managed to make the machine
reboot on resume. In the logs was again the serio_raw driver. After the
reboot lsmod showed that the driver was loaded, but nothing was using
it. (what is this driver
Even though the driver is blacklisted in /etc/modprobe.d, the driver is
loaded now. It wasn't loaded immediately after boot. What is loading
this thing?
--
Does not resume from suspend
https://bugs.launchpad.net/bugs/60243
You received this bug notification because you are a member of Ubuntu
Jos:
The open source X nv driver doesn't actually have any code in the kernel. What
you saw was a frame buffer driver for nvidia cards but this is almost never
actually used. It would be interesting to know if you still have problems
suspending and resuming with the vesa driver. If so I suspect
Sitsofe:
I don't understand. I'm not using nv, I use the nvidia driver, but that is
beside the point. I'm having trouble resuming caused by the serio_raw driver.
--
Does not resume from suspend
https://bugs.launchpad.net/bugs/60243
You received this bug notification because you are a member of
I just had a reboot instead of a resume this morning. Now the driver in
question is tty54?? Which device should I blacklist?
[1.331819] Magic number: 0:111:333
[1.331906] hash matches device tty54
--
Does not resume from suspend
https://bugs.launchpad.net/bugs/60243
You received
Reconfirming for 2.6.20 based on Jos' recent testing.
Jos, can you attach the /var/log/kern.log.0 or /var/log/kern.log.1,
whichever covers the failed resume? Thanks.
** Changed in: linux-source-2.6.20 (Ubuntu)
Status: Needs Info = Confirmed
--
Does not resume from suspend
Here is the log.
** Attachment added: kern.log (line with the serio0 is 14652)
http://librarian.launchpad.net/7339305/kern.log.0
--
Does not resume from suspend
https://bugs.launchpad.net/bugs/60243
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
I'm closing this as fix released for the Feisty kernel, based on Jos'
most recent comment; Jos, if you are seeing other errors, please open a
new bug report, we'll keep this going for the suspend/resume problem.
** Changed in: linux-source-2.6.20 (Ubuntu)
Status: Confirmed = Fix Released
It is not fixed (system is current 2007-04-16). I've seen it happen a
few times since. Typically if compiz was running during suspend. I'm
using nvidia driver 9755. It also happens sometimes when running
metacity.
--
Does not resume from suspend
https://bugs.launchpad.net/bugs/60243
You received
Vassilis, you'll note that I marked this as fix released for 2.6.20,
based on other comments. If this doesn't match your experience, please
do change the 2.6.20 status back to confirmed (yes, normally bad form to
confirm one's own bug, but OK in this case, I think!).
If this is fixed in 2.6.20,
Jos, since this is still occurring for you, could you please try the
procedure described in [1]? It might also be worth trying Dennis's
procedure from comment #20. The more we can pin this down, the more
likely we are to being able to find an fix it.
[1]
Just had the problem when I came home from work. Black screen on resume,
can not switch VT, no magic sysrq, only the power button works. This
time it was without any compiz stuff, just plain metacity. I'd say I
get some 80% success rate. I don't have time now, but will try to get
more info using
Ok, I tried the acpi debug procedure. The driver that was the 'likely
culprit' was serio0 in my case. I looked in the lsmod output and found a
driver serio_raw, which I added to the MODULES in acpi-support. This
seems to have fixed it, I have tried to suspend/resume more than 10
times, and it
Pending upstream fixes might help your problem. Try the daily ISO from
http://cdimage.ubuntu.com/daily-live/current on 4/2
** Changed in: linux-source-2.6.20 (Ubuntu)
Status: Needs Info = Confirmed
--
Does not resume from suspend
https://launchpad.net/bugs/60243
--
ubuntu-bugs mailing
Suspend/resume was working fine for me up until a few days ago (dell
latitude d820). Now resume sometimes fails with black screen, or the
machine reboots. I have noticed an oops in the kernel log file (nvidia
module). But with the nv driver, I still can't suspend/resume.
--
Does not resume from
Can you please attach a kernel log containing the oops?
Also, if you try the procedure at
https://wiki.ubuntu.com/DebuggingKernelSuspend, we might learn about the
problem.
Thanks!
** Changed in: linux-source-2.6.20 (Ubuntu)
Status: Confirmed = Needs Info
--
Does not resume from suspend
** Changed in: linux-source-2.6.20 (Ubuntu)
Importance: Undecided = Low
Assignee: Tim Gardner = Ubuntu Kernel ACPI Team
Status: Needs Info = Confirmed
** Changed in: linux-source-2.6.17 (Ubuntu)
Importance: Undecided = Low
Assignee: Tim Gardner = Ubuntu Kernel ACPI Team
I would like you to try something. Log into X using the nvidia driver.
Close any essential applications just in case. Then go into suspend -
wait for approx 2 min then hit a key to resume. Even though you get a
blank screen and hard drive activity, just give it some time. Once the
hard disk light
** Changed in: linux-source-2.6.20 (Ubuntu)
Status: Confirmed = Needs Info
--
Does not resume from suspend
https://launchpad.net/bugs/60243
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Please read and try the suggestions contained in :
https://wiki.ubuntu.com/KernelSuspendDebugging
--
Does not resume from suspend
https://launchpad.net/bugs/60243
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
** Changed in: linux-source-2.6.17 (Ubuntu)
Assignee: Ubuntu Kernel ACPI Team = Tim Gardner
** Changed in: linux-source-2.6.20 (Ubuntu)
Assignee: (unassigned) = Tim Gardner
--
Does not resume from suspend
https://launchpad.net/bugs/60243
--
ubuntu-bugs mailing list
Marking as confirmed based on available logs.
Vassilis, it will also be useful to have the /var/log/kern.log.0 file
from after a crash: Boot, suspend/resume to get the crash, reboot, then
attach /var/log/kern.log.0 to this bug report. Thanks!
** Changed in: linux-source-2.6.20 (Ubuntu)
All my attempts were from GDM.
--
Does not resume from suspend
https://launchpad.net/bugs/60243
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
** Attachment added: dmidecode
http://librarian.launchpad.net/5836596/dmidecode
** Also affects: linux-source-2.6.20 (Ubuntu)
Importance: Undecided
Status: Unconfirmed
--
Does not resume from suspend
https://launchpad.net/bugs/60243
--
ubuntu-bugs mailing list
Oh. Another thing I noticed (with .17 and .20) : I suspend. I resume.
The system resumes temporarily but then crashes. I can tell this because
if I hit caps lock all the time the led goes on and off until the kernel
crashes and there is no response and that (at least under edgy) if I was
playing
Resume from suspend doesn't work with 2.6.20-5-generic #2 SMP on Feisty
either. I turned off all internal devices from the BIOS to make sure
it's not , say the NIC, that causes problems.
** Attachment added: lspci -vv
http://librarian.launchpad.net/5836572/lspci-vv
--
Does not resume from
Thanks this bug report and for attaching command output. Some of these
commands need to be run with root access in order to get full
information required for debugging, so it would it be possible for you
to run the following and attach the output?
uname -a
sudo lspci -vv
sudo lspci -vvn
sudo
I could suspend a few times and resuming without video but with the rest
of the system working. In the logs there were output about nvidia module
exception.
--
Does not resume from suspend
https://launchpad.net/bugs/60243
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Still an issue with -10
--
Does not resume from suspend
https://launchpad.net/bugs/60243
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
** Changed in: linux-source-2.6.17 (Ubuntu)
Status: Needs Info = Unconfirmed
--
Does not resume from suspend
https://launchpad.net/bugs/60243
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Please test 2.6.17-8.22 kernel.
** Changed in: linux-source-2.6.17 (Ubuntu)
Status: Unconfirmed = Needs Info
--
Does not resume from suspend
https://launchpad.net/bugs/60243
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Still an issue. Ironically, hibernate was fixed although I hadn't opened
a bug about it :-) Thanks
--
Does not resume from suspend
https://launchpad.net/bugs/60243
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
** Attachment added: lspci -vv
http://librarian.launchpad.net/4247670/lspci2.txt
--
Does not resume from suspend
https://launchpad.net/bugs/60243
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
** Attachment added: lspci -vvn
http://librarian.launchpad.net/4247676/lspci-vvn.txt
** Changed in: linux-source-2.6.17 (Ubuntu)
Assignee: (unassigned) = Ubuntu Kernel ACPI Team
--
Does not resume from suspend
https://launchpad.net/bugs/60243
--
ubuntu-bugs mailing list
** Attachment added: lspci
http://librarian.launchpad.net/4247669/lspci.txt
--
Does not resume from suspend
https://launchpad.net/bugs/60243
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
** Attachment added: /var/log/messages
http://librarian.launchpad.net/4247686/messages
--
Does not resume from suspend
https://launchpad.net/bugs/60243
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I've attached any information that may be relevant. Please ask for more
if needed. As a side note: when resuming, even though the machine
apparently has hung, the sysrq reboot magic key works.
--
Does not resume from suspend
https://launchpad.net/bugs/60243
--
ubuntu-bugs mailing list
I've attached any information that may be relevant. Please ask for more
if needed. As a side note: when resuming, even though the machine
apparently has hung, the sysrq reboot magic key works.
--
Does not resume from suspend
https://launchpad.net/bugs/60243
--
ubuntu-bugs mailing list
Ahh, sorry, a slip of mind there. I am using the 'nv' driver, not
'nvidia'.
--
Does not resume from suspend
https://launchpad.net/bugs/60243
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
61 matches
Mail list logo
