[Bug 129226] Re: kernel oops after resuming from suspend to RAM
Hi All, For those of you experiencing new or slightly different issues, please open a new bug report. It is helpful to the kernel team if bug reports target a specific issue against a specific set of hardware. The original kernel Oops issue appears to have been resolved so I am flipping back to Fix Released. Also, please be sure to test with the latest Hardy Alpha release. The Hardy Heron Alpha series contains an updated version of the kernel. You can download and try the new Hardy Heron Alpha release from http://cdimage.ubuntu.com/releases/hardy/ . You should be able to then test the new kernel via the LiveCD. General information regarding the release can also be found here: http://www.ubuntu.com/testing/ . Thanks. ** Changed in: linux-source-2.6.22 (Ubuntu) Status: Confirmed = Fix Released -- kernel oops after resuming from suspend to RAM https://bugs.launchpad.net/bugs/129226 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129226] Re: kernel oops after resuming from suspend to RAM
Hi all. My notebook dell 1420 produces the same logs as tk23 $ modprobe -rv acpi_cpufreq $ modprobe -v acpi_cpufreq solves the problem. the 2nd core doesnt die after resume. it's running without frequency scaling. btw I'm using opensuse 10.3. only suspend to ram produces the problem. suspend to disk does not. -- kernel oops after resuming from suspend to RAM https://bugs.launchpad.net/bugs/129226 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129226] Re: kernel oops after resuming from suspend to RAM
It's not really fixed. Speedstepping the second core fails after suspend, but it does not crash. The log shows: [ 4754.68] CPU: Processor Core ID: 1 [ 4754.68] CPU1: Intel(R) Core(TM)2 Duo CPU T7300 @ 2.00GHz stepping 0a [ 4754.68] ACPI Error (psloop-0136): Found unknown opcode FE at AML address f88523ca offset 3, ignoring [20070126] [ 4754.68] ACPI Error (psargs-0355): [C\376\377\376.D\376\377] Namespace lookup failure, AE_NOT_FOUND [ 4754.68] ACPI Error (psparse-0551): Method parse/execution failed [\_PR_.CPU1._PCT] (Node df816870), AE_NOT_FOUND [ 4754.68] ACPI Exception (processor_perflib-0170): AE_NOT_FOUND, Evaluating _PCT [20070126] [ 4754.68] CPU1 is up [ 4754.684000] Switched to high resolution mode on CPU 1 [ 4754.724000] ACPI: PCI Interrupt :00:02.0[A] - GSI 16 (level, low) - IRQ 16 $ cat /proc/cpuinfo |grep ... cpu family : 6 model : 15 model name : Intel(R) Core(TM)2 Duo CPU T7300 @ 2.00GHz cpu MHz : 800.000 cpu family : 6 model : 15 model name : Intel(R) Core(TM)2 Duo CPU T7300 @ 2.00GHz cpu MHz : 1995.106 $ sudo cpufreq-info cpufrequtils 002: cpufreq-info (C) Dominik Brodowski 2004-2006 Report errors and bugs to [EMAIL PROTECTED], please. analyzing CPU 0: driver: acpi-cpufreq CPUs which need to switch frequency at the same time: 0 hardware limits: 800 MHz - 2.00 GHz available frequency steps: 2.00 GHz, 2.00 GHz, 1.60 GHz, 1.20 GHz, 800 MHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance current policy: frequency should be within 800 MHz and 2.00 GHz. The governor ondemand may decide which speed to use within this range. current CPU frequency is 800 MHz (asserted by call to hardware). analyzing CPU 1: no or unknown cpufreq driver is active on this CPU I repeat: The second core does *not* crash - it is available with full speed, only frequency scaling fails. If you need some more information, please let me know. -- kernel oops after resuming from suspend to RAM https://bugs.launchpad.net/bugs/129226 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 129226] Re: kernel oops after resuming from suspend to RAM
On Wednesday 21 November 2007 16:10:56 tk23 wrote: I repeat: The second core does *not* crash - it is available with full speed, only frequency scaling fails. This seems to be case in 2.6.23.8 from kernel.org, too. -- kernel oops after resuming from suspend to RAM https://bugs.launchpad.net/bugs/129226 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129226] Re: kernel oops after resuming from suspend to RAM
I'm seeing the same issue on my Latitude D830 with a stock 2.6.23 kernel I compiled myself. This may be a bug in the kernel itself? -- kernel oops after resuming from suspend to RAM https://bugs.launchpad.net/bugs/129226 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129226] Re: kernel oops after resuming from suspend to RAM
Also I don't think it's truly fixed in 2.6.22-14, I had still disappear Core1 after resume. -- kernel oops after resuming from suspend to RAM https://bugs.launchpad.net/bugs/129226 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129226] Re: kernel oops after resuming from suspend to RAM
I don't think it's truly fixed. ** Changed in: linux-source-2.6.22 (Ubuntu) Status: Fix Released = Confirmed -- kernel oops after resuming from suspend to RAM https://bugs.launchpad.net/bugs/129226 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129226] Re: kernel oops after resuming from suspend to RAM
i get a kernel panic on 2.6.22-13-generic if resuming from hibernation unfortunately nothing is logged -- kernel oops after resuming from suspend to RAM https://bugs.launchpad.net/bugs/129226 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129226] Re: kernel oops after resuming from suspend to RAM
My Dell XPS M1330 enables also one core after suspend. I've got an uptodate Gutsy with Kernel 2.6.22-12 Here my /var/log/messages Sep 27 02:40:06 kingslanding kernel: [0.458656] Enabling non-boot CPUs ... Sep 27 02:40:06 kingslanding kernel: [0.459285] atkbd.c: Unknown key pressed (translated set 2, code 0x88 on isa0060/serio0). Sep 27 02:40:06 kingslanding kernel: [0.459291] atkbd.c: Use 'setkeycodes e008 keycode' to make it known. Sep 27 02:40:06 kingslanding kernel: [0.459634] atkbd.c: Unknown key pressed (translated set 2, code 0x88 on isa0060/serio0). Sep 27 02:40:06 kingslanding kernel: [0.459640] atkbd.c: Use 'setkeycodes e008 keycode' to make it known. Sep 27 02:40:06 kingslanding kernel: [0.459934] SMP alternatives: switching to SMP code Sep 27 02:40:06 kingslanding kernel: [0.460182] Booting processor 1/2 APIC 0x1 Sep 27 02:40:06 kingslanding kernel: [0.471233] Initializing CPU#1 Sep 27 02:40:06 kingslanding kernel: [0.547518] Calibrating delay using timer specific routine.. 4387.96 BogoMIPS (lpj=8775936) Sep 27 02:40:06 kingslanding kernel: [0.547532] CPU: L1 I cache: 32K, L1 D cache: 32K Sep 27 02:40:06 kingslanding kernel: [0.547537] CPU: L2 cache: 4096K Sep 27 02:40:06 kingslanding kernel: [0.547542] CPU 1/1 - Node 0 Sep 27 02:40:06 kingslanding kernel: [0.547546] CPU: Physical Processor ID: 0 Sep 27 02:40:06 kingslanding kernel: [0.547549] CPU: Processor Core ID: 1 Sep 27 02:40:06 kingslanding kernel: [0.548720] Intel(R) Core(TM)2 Duo CPU T7500 @ 2.20GHz stepping 0a Sep 27 02:40:06 kingslanding kernel: [0.551845] ACPI Error (psloop-0136): Found unknown opcode FE at AML address c2ab23ca offset 7, ignoring [20070126] Sep 27 02:40:06 kingslanding kernel: [0.551857] ACPI Error (psloop-0136): Found unknown opcode 16 at AML address c2ab23cc offset 9, ignoring [20070126] Sep 27 02:40:06 kingslanding kernel: [0.551871] ACPI Error (psloop-0136): Found unknown opcode 19 at AML address c2ab23d0 offset D, ignoring [20070126] Sep 27 02:40:06 kingslanding kernel: [0.551888] ACPI Error (psargs-0355): [C\376\377^I] Namespace lookup failure, AE_NOT_FOUND Sep 27 02:40:06 kingslanding kernel: [0.551899] ACPI Error (psparse-0551): Method parse/execution failed [\_PR_.CPU1._PCT] (Node 81007cfa3d60), AE_NOT_FOUND Sep 27 02:40:06 kingslanding kernel: [0.551983] ACPI Exception (processor_perflib-0170): AE_NOT_FOUND, Evaluating _PCT [20070126] Sep 27 02:40:06 kingslanding kernel: [0.551989] CPU1 is up Sep 27 02:40:06 kingslanding kernel: [0.562877] PCI: Enabling device :00:1a.0 ( - 0001) Sep 27 02:40:06 kingslanding kernel: [0.562881] ACPI: PCI Interrupt :00:1a.0[A] - GSI 20 (level, low) - IRQ 20 -- kernel oops after resuming from suspend to RAM https://bugs.launchpad.net/bugs/129226 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129226] Re: kernel oops after resuming from suspend to RAM
For me it looks like the fix fixed it, I will reopen a bug in case of troubles. Thanks! (ThinkPad X61s) -- kernel oops after resuming from suspend to RAM https://bugs.launchpad.net/bugs/129226 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129226] Re: kernel oops after resuming from suspend to RAM
With the new kernel I do not get the oops but it still dies the exact same way as with the oops error message and now I get the sound error too... Should I start a new bug report? -- kernel oops after resuming from suspend to RAM https://bugs.launchpad.net/bugs/129226 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129226] Re: kernel oops after resuming from suspend to RAM
New kernel (2.6.22-10-generic) fixed it for me on a Dell Inspiron 1420 (Core 2 Duo). No flashing keyboard lights, cat /proc/cpuinfo shows both cores, and they both also appear in System Monitor. -- kernel oops after resuming from suspend to RAM https://bugs.launchpad.net/bugs/129226 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129226] Re: kernel oops after resuming from suspend to RAM
The new version of the kernel is now available in most repositories. This fixed it for me also so I am marking this bug as Fix Released. In the event that any one still has any issues feel free to reopen the bug. ** Changed in: linux-source-2.6.22 (Ubuntu) Status: Fix Committed = Fix Released -- kernel oops after resuming from suspend to RAM https://bugs.launchpad.net/bugs/129226 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129226] Re: kernel oops after resuming from suspend to RAM
This fixed the resume problem of 1 core not resuming, but created a different problem with the sound not resuming. If anyone else now has sound not resuming after upgrading to this kernel, I've started a new bug at 134167. -- kernel oops after resuming from suspend to RAM https://bugs.launchpad.net/bugs/129226 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129226] Re: kernel oops after resuming from suspend to RAM
Is the fix already released? Because I have a fully up-to-date Gutsy and I got an oops just 10 minutes ago when going out of suspend. -- kernel oops after resuming from suspend to RAM https://bugs.launchpad.net/bugs/129226 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129226] Re: kernel oops after resuming from suspend to RAM
It's still happening for me with a fully uptodate gutsy. The only kernel update happened 3-4 days ago and didn't contain the fix, it seems. -- kernel oops after resuming from suspend to RAM https://bugs.launchpad.net/bugs/129226 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129226] Re: kernel oops after resuming from suspend to RAM
Make sure you are running 2.6.22-10.26. It has just finished building @ https://launchpad.net/ubuntu/+source/linux-source-2.6.22/ uname -a will show your current version. -- kernel oops after resuming from suspend to RAM https://bugs.launchpad.net/bugs/129226 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129226] Re: kernel oops after resuming from suspend to RAM
It hasn't finished building yet. Hold on for a day or so. -- kernel oops after resuming from suspend to RAM https://bugs.launchpad.net/bugs/129226 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129226] Re: kernel oops after resuming from suspend to RAM
A new kernel has been released as source, but there's no binary yet. At the moment I'm still on 2.6.22-9.25 (and everyone else would be too at this point), which doesn't contain the fixes. I believe the kernel with the fix is version 2.6.22-10.26. It'll be available soon. Keep in mind I've never tracked the Ubuntu kernel before so I may be completely wrong :) -- kernel oops after resuming from suspend to RAM https://bugs.launchpad.net/bugs/129226 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129226] Re: kernel oops after resuming from suspend to RAM
Shouldn't the status of this get changed from Fix Committed since the patch was reverted? I just want to make sure this doesn't get forgotten, but I'm not entirely sure how the procedures are supposed to work... -- kernel oops after resuming from suspend to RAM https://bugs.launchpad.net/bugs/129226 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129226] Re: kernel oops after resuming from suspend to RAM
I have a Dell E1505 and have Ubuntu 7.04 with the Gutsy kernel compiled via script. I can confirm this bug as well. -- kernel oops after resuming from suspend to RAM https://bugs.launchpad.net/bugs/129226 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129226] Re: kernel oops after resuming from suspend to RAM
@Peter - In most cases users don't want to know the 'underlying stuff' - they just want their HW to work. :) OTOH, interested users always ask, and in most cases I dare say, receive somewhat satisfactory answers. In this case, the post after yours answers your question. But I agree, that some more details wouldn't do any harm - I will try to do that in the future. -- kernel oops after resuming from suspend to RAM https://bugs.launchpad.net/bugs/129226 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129226] Re: kernel oops after resuming from suspend to RAM
Hi! I have run into a pretty similar problem after suspend with Gutsy Tribe 4 AMD64, I have a Dual CPU Xeon system and after the error messages: -Kernel panic - not syncing: Attempted to kill the idel task -Oops: SMP -CR2:805ac78 my system dies. I have to switch it off and on to get it run again. -- kernel oops after resuming from suspend to RAM https://bugs.launchpad.net/bugs/129226 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129226] Re: kernel oops after resuming from suspend to RAM
I can confirm this behaviour with Asus V6J too. -- kernel oops after resuming from suspend to RAM https://bugs.launchpad.net/bugs/129226 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 129226] Re: kernel oops after resuming from suspend to RAM
You could download the kernel tree and compile it yourself. $ git clone git://kernel.ubuntu.com/ubuntu/ubuntu-gutsy.git $ cd ubuntu-gutsy $ fakeroot debian/rules binary-generic ^^^ Change this to the correct architecture - this one is for i386 $ cd ..; dpkg -i *.deb On 8/9/07, vlowther [EMAIL PROTECTED] wrote: For the benefit of those of us who would like to be able to use both cores of their dual-core processor and have (suspend|hibernate) and resume functionality at the same time, could a pointer to the patch which fixes this issue be provided? for me, at least, it is either that or run with the Feisty kernel until Tribe 5. -- kernel oops after resuming from suspend to RAM https://bugs.launchpad.net/bugs/129226 You received this bug notification because you are a direct subscriber of the bug. -- kernel oops after resuming from suspend to RAM https://bugs.launchpad.net/bugs/129226 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129226] Re: kernel oops after resuming from suspend to RAM
Thanks for the pointer to the git repo. Whilst I can happily track changes to source packages in Ubuntu, rebuild them etc..., check launchpad - its often a bit of a mystery where the cutting edge work goes on behind the scenes. As the developers bugzilla posts are probably trying to be user-friendly, thereI never seems to be a lot of linking to the underlying technical stuff. For the curious like me, could you point me to which commit you reverte to fix the issue? I only see: http://kernel.ubuntu.com/git?p=zul/ubuntu- gutsy.git;a=commitdiff;h=8444584e11e4c80a1bde56152db8bb615c242bc1 There didn't appear to be an explanation in the log why it was reverted though. Was that the one, just config changes? If so, doesn't this mean there is still some underlying kernel bug which is just set off by a particular config? -- kernel oops after resuming from suspend to RAM https://bugs.launchpad.net/bugs/129226 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129226] Re: kernel oops after resuming from suspend to RAM
It is actually http://kernel.ubuntu.com/git?p=ubuntu/ubuntu- gutsy.git;a=commit;h=98f537ca1bc7218f299831c31224027892093ab6 which is causing the glitch. Based on what the patch reverts it (according to my WAG), it would come as no surprise that the DMI information is not precisely sane after a suspend/hibernate event in certain BIOSes and there is some odd poking that has to be done to get it back and/or you may have to wait for the information to stabilize. -- kernel oops after resuming from suspend to RAM https://bugs.launchpad.net/bugs/129226 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129226] Re: kernel oops after resuming from suspend to RAM
For the benefit of those of us who would like to be able to use both cores of their dual-core processor and have (suspend|hibernate) and resume functionality at the same time, could a pointer to the patch which fixes this issue be provided? for me, at least, it is either that or run with the Feisty kernel until Tribe 5. -- kernel oops after resuming from suspend to RAM https://bugs.launchpad.net/bugs/129226 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129226] Re: kernel oops after resuming from suspend to RAM
Reverted a patch that was responsible for this. David confirmed that this works for him. -- kernel oops after resuming from suspend to RAM https://bugs.launchpad.net/bugs/129226 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129226] Re: kernel oops after resuming from suspend to RAM
Patch reverted ** Changed in: linux-source-2.6.22 (Ubuntu) Status: Confirmed = Fix Committed -- kernel oops after resuming from suspend to RAM https://bugs.launchpad.net/bugs/129226 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129226] Re: kernel oops after resuming from suspend to RAM
Too late for a full kernel upload now, unless this is an unintrusive one and does not break ABI. ** Changed in: linux-source-2.6.22 (Ubuntu) Target: tribe-4 = tribe-5 -- kernel oops after resuming from suspend to RAM https://bugs.launchpad.net/bugs/129226 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129226] Re: kernel oops after resuming from suspend to RAM
** Changed in: linux-source-2.6.22 (Ubuntu) Target: None = tribe-4 -- kernel oops after resuming from suspend to RAM https://bugs.launchpad.net/bugs/129226 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
