Bug 695618 - Getting "WARNING! errors 0 Skipped probes xx" on resume after shutdown
Summary: Getting "WARNING! errors 0 Skipped probes xx" on resume after shutdown
Status: RESOLVED WONTFIX
Alias: None
Product: openSUSE 11.4
Classification: openSUSE
Component: Kernel (show other bugs)
Version: Final
Hardware: x86 openSUSE 11.4
: P5 - None : Normal with 1 vote (vote)
Target Milestone: ---
Assignee: E-mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-24 08:54 UTC by Kristofer Einarsson
Modified: 2012-08-02 16:01 UTC (History)
2 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kristofer Einarsson 2011-05-24 08:54:00 UTC
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US) AppleWebKit/534.10 (KHTML, like Gecko) Chrome/8.0.552.200 Safari/534.10

Hi

I have have a Lenovo T61 laptop. I also have the NVIDIA driver installed. Sometimes on resume instead of opening X and prompting for password I get the error "WARNING! errors 0 Skipped probes xx" in console and the computer does not accept any input from the keyboard.

I have seen others having similir problems at:
http://forums.opensuse.org/english/get-technical-help-here/applications/459770-warning-errors-0-skipped-probes-xx-2.html

Reproducible: Sometimes

Steps to Reproduce:
1. suspend computer
2. resume computer
3.
Actual Results:  
computer hung

Expected Results:  
computer resumed
Comment 1 Denver D. Robinson 2011-05-24 10:37:50 UTC
at least three 'users' have reported seeing this bewildering WARNING!, and someone posting as 'fche' said (in thread http://forums.opensuse.org/showthread.php?t=459770):

"It's not a systemtap warning that ordinary users should be made to read
or understand.  The OS script that starts up stap should probably just
redirect stderr to /dev/null."

which, on the surface, appears to be logical path to close..
Comment 2 Jeff Mahoney 2012-08-02 16:00:23 UTC
With the coming release of openSUSE 12.2, openSUSE kernel developers are focusing their efforts there. Reports against openSUSE 11.4 and prior will not get the attention needed to resolve them before openSUSE 12.2 is release and openSUSE 11.4 becomes unmaintained.

Please re-test with openSUSE 12.1 or openSUSE RC2+ and re-open with an updated Product if you still encounter your issue.

We apologize for this issue not getting the attention it deserves but we are focusing our resources in the area where they will have the most impact for our users.  We're working hard to make openSUSE 12.2 the best openSUSE release yet!
Comment 3 Jeff Mahoney 2012-08-02 16:01:01 UTC
With the coming release of openSUSE 12.2, openSUSE kernel developers are focusing their efforts there. Reports against openSUSE 11.4 and prior will not get the attention needed to resolve them before openSUSE 12.2 is release and openSUSE 11.4 becomes unmaintained.

Please re-test with openSUSE 12.1 or openSUSE RC2+ and re-open with an updated Product if you still encounter your issue.

We apologize for this issue not getting the attention it deserves but we are focusing our resources in the area where they will have the most impact for our users.  We're working hard to make openSUSE 12.2 the best openSUSE release yet!