I have to apologize twice--first for not including this information previously, and second because on running uname I discovered that I've been booting the 2.6.20 kernel, so I need to see whether this is even relevant for 2.6.22. I'll either update soon or just close the bug if I can't reproduce it.
On Dec 8, 2007 9:16 AM, Che Guevara < [EMAIL PROTECTED]> wrote: > Thank you for taking the time to report this bug and helping to make > Ubuntu better. Unfortunately we can't fix it, because your description > does not yet have enough information. > > Please include the following additional information, if you have not > already done so (pay attention to lspci's additional options), as required > by the Ubuntu Kernel Team: > 1. Please include the output of the command "uname -a" in your next > response. It should be one, long line of text which includes the exact > kernel version you're running, as well as the CPU architecture. > 2. Please run the command "dmesg > dmesg.log" after a fresh boot and > attach the resulting file "dmesg.log" to this bug report. > 3. Please run the command "sudo lspci -vvnn > lspci-vvnn.log " and attach > the resulting file "lspci-vvnn.log" to this bug report. > > For your reference, the full description of procedures for kernel- > related bug reports is available at [WWW] > http://wiki.ubuntu.com/KernelTeamBugPolicies. Thanks in advance! > > -- > e1000 driver causes lockup on suspend > https://bugs.launchpad.net/bugs/174784 > You received this bug notification because you are a direct subscriber > of the bug. > -- e1000 driver causes lockup on suspend https://bugs.launchpad.net/bugs/174784 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
