*** This bug is a duplicate of bug 353122 ***
https://bugs.launchpad.net/bugs/353122
Seems to be a periodic problem like the other bug. I'm going to mark
this one as a duplicate report and the other as confirmed.
** This bug has been marked a duplicate of bug 353122
eee pc 1000he -- Kerne
** Attachment added: "dmesg.log"
http://launchpadlibrarian.net/25254461/dmesg.log
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/25254462/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/25254463/CurrentDmesg.txt
** Attachment adde
Is this error reproducible? Does it always fail to suspend properly, or
only sometimes, such as with this previous bug report
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/353122)?
--
kernel problem on suspend - EEE PC 1000HE
https://bugs.launchpad.net/bugs/359646
You received this bug n
** Attachment added: "dmesg.log"
http://launchpadlibrarian.net/25254461/dmesg.log
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/25254462/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/25254463/CurrentDmesg.txt
** Attachment adde
Is this error reproducible? Does it always fail to suspend properly, or
only sometimes, such as with this previous bug report
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/353122)?
--
kernel problem on suspend - EEE PC 1000HE
https://bugs.launchpad.net/bugs/359646
You received this bug n
*** This bug is a duplicate of bug 353122 ***
https://bugs.launchpad.net/bugs/353122
Seems to be a periodic problem like the other bug. I'm going to mark
this one as a duplicate report and the other as confirmed.
** This bug has been marked a duplicate of bug 353122
eee pc 1000he -- Kerne
** Attachment added: "dmesg.log"
http://launchpadlibrarian.net/25254461/dmesg.log
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/25254462/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/25254463/CurrentDmesg.txt
** Attachment adde
Is this error reproducible? Does it always fail to suspend properly, or
only sometimes, such as with this previous bug report
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/353122)?
--
kernel problem on suspend - EEE PC 1000HE
https://bugs.launchpad.net/bugs/359646
You received this bug n
*** This bug is a duplicate of bug 353122 ***
https://bugs.launchpad.net/bugs/353122
Seems to be a periodic problem like the other bug. I'm going to mark
this one as a duplicate report and the other as confirmed.
** This bug has been marked a duplicate of bug 353122
eee pc 1000he -- Kerne
** Attachment added: "dmesg.log"
http://launchpadlibrarian.net/25254461/dmesg.log
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/25254462/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/25254463/CurrentDmesg.txt
** Attachment adde
Is this error reproducible? Does it always fail to suspend properly, or
only sometimes, such as with this previous bug report
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/353122)?
--
kernel problem on suspend - EEE PC 1000HE
https://bugs.launchpad.net/bugs/359646
You received this bug n
*** This bug is a duplicate of bug 353122 ***
https://bugs.launchpad.net/bugs/353122
Seems to be a periodic problem like the other bug. I'm going to mark
this one as a duplicate report and the other as confirmed.
** This bug has been marked a duplicate of bug 353122
eee pc 1000he -- Kerne
** Attachment added: "dmesg.log"
http://launchpadlibrarian.net/25254461/dmesg.log
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/25254462/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/25254463/CurrentDmesg.txt
** Attachment adde
Is this error reproducible? Does it always fail to suspend properly, or
only sometimes, such as with this previous bug report
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/353122)?
--
kernel problem on suspend - EEE PC 1000HE
https://bugs.launchpad.net/bugs/359646
You received this bug n
*** This bug is a duplicate of bug 353122 ***
https://bugs.launchpad.net/bugs/353122
Seems to be a periodic problem like the other bug. I'm going to mark
this one as a duplicate report and the other as confirmed.
** This bug has been marked a duplicate of bug 353122
eee pc 1000he -- Kerne
** Attachment added: "dmesg.log"
http://launchpadlibrarian.net/25254461/dmesg.log
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/25254462/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/25254463/CurrentDmesg.txt
** Attachment adde
Is this error reproducible? Does it always fail to suspend properly, or
only sometimes, such as with this previous bug report
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/353122)?
--
kernel problem on suspend - EEE PC 1000HE
https://bugs.launchpad.net/bugs/359646
You received this bug n
*** This bug is a duplicate of bug 353122 ***
https://bugs.launchpad.net/bugs/353122
Seems to be a periodic problem like the other bug. I'm going to mark
this one as a duplicate report and the other as confirmed.
** This bug has been marked a duplicate of bug 353122
eee pc 1000he -- Kerne
This is a question I should have asked myself before filing the bug
report.
I set the lid close event to "suspend to disk" reboooted, closed lid,
resumed, suspended, and resumed. Repeated this 5 times:
no problems with resume. WLAN reconnect was hit and miss.
I did the same thing with "suspend to
This is a question I should have asked myself before filing the bug
report.
I set the lid close event to "suspend to disk" reboooted, closed lid,
resumed, suspended, and resumed. Repeated this 5 times:
no problems with resume. WLAN reconnect was hit and miss.
I did the same thing with "suspend to
This is a question I should have asked myself before filing the bug
report.
I set the lid close event to "suspend to disk" reboooted, closed lid,
resumed, suspended, and resumed. Repeated this 5 times:
no problems with resume. WLAN reconnect was hit and miss.
I did the same thing with "suspend to
This is a question I should have asked myself before filing the bug
report.
I set the lid close event to "suspend to disk" reboooted, closed lid,
resumed, suspended, and resumed. Repeated this 5 times:
no problems with resume. WLAN reconnect was hit and miss.
I did the same thing with "suspend to
This is a question I should have asked myself before filing the bug
report.
I set the lid close event to "suspend to disk" reboooted, closed lid,
resumed, suspended, and resumed. Repeated this 5 times:
no problems with resume. WLAN reconnect was hit and miss.
I did the same thing with "suspend to
This is a question I should have asked myself before filing the bug
report.
I set the lid close event to "suspend to disk" reboooted, closed lid,
resumed, suspended, and resumed. Repeated this 5 times:
no problems with resume. WLAN reconnect was hit and miss.
I did the same thing with "suspend to
24 matches
Mail list logo
