Re: What is this kernel error?

On Sun, Mar 25, 2007 at 11:23:15PM -0400, Greg Folkert wrote:
On Sun, 2007-03-25 at 23:12 -0400, Kevin Mark wrote:
On Sun, Mar 25, 2007 at 08:56:21PM -0400, Rick Pasotto wrote:
<snip>
My machine (desktop) was last booted 7 days ago. I rebooted because of
the new kernel. That's why I pointed out the specific kernel.
<snip>
that is at least SOMETHING useful. If you have an issue after you
changed the kernel, then the 1st logical step is to try to boot with the
last kernel, assuming that it is possible and see if the issue still
happens.

It is *X* and his screensaver. It took three seconds of typing in a
Google search widget and reading a few things.

*What* did you search for? *Where* did you search? When I searched for
the error on Google all I got was a single result that related it to
mplayer, which clearly was *not* relevant.

He was not able to even give us context *UNTIL* he said he left and
*MAYBE* the screensaver kicked in and of all things, in a rant back to
me.

Maybe it was the phase of the moon! That comment about the screensaver
was meant to be satirical.

Again, the screensaver has come on *many*, *many* times since the last
reboot. What is different about this time? Is it a particular
screensaver module? (I have it set to random so I never know which one
will fire up next.) If it is a particular module, has a bug report been
filed?

I guess we can't trust people to even look for themselves anymore.

Don't make unfounded assumptions.

Rick Pasotto has been round filed in my book.

*You* started the nastiness with your snide comment in response to a
simple question.

"Well, you know more than we do. We don't even have the machine at our
disposal."

Maybe we should all post our boot.logs and syslogs and 'ps ax' (of
course it kinda hard to do that for x minutes ago) and who knows what
else for every little question we have. Would *that* be sufficient
context?

A little bit of *friendly* Q&A to zero in on the *relevant* context
might be more productive.

--
"If I devote myself to other pursuits and contemplations, I must
first see, at least, that I do not pursue them sitting upon
another man's shoulders. I must get off him first, that he may
pursue his contemplations too." -- Henry David Thoreau
Rick Pasotto rick@xxxxxxxx http://www.niof.net


--
To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx
with a subject of "unsubscribe". Trouble? Contact listmaster@xxxxxxxxxxxxxxxx

Relevant Pages

  • Re: ... Tiny Personal Firewall ...
    ... Winlogin and GINA interact via several command sequences (WlxIsLockOk, ... - Screensaver desktop (insecure, but designed to 'flip' to the winlogin ... > because Tiny Personal Firewall most likely operates at the kernel level. ... > the kernel when prompting the console ...
    (Bugtraq)
  • Re: What is this kernel error?
    ... That's why I pointed out the specific kernel. ... It is *X* and his screensaver. ... It is related to your video card, your motherboard chipset, opengl, xorg ...
    (Debian-User)
  • Re: Kernel 2.6.15-1.1830 lock-up issues
    ... ntfs, plus the vmwareplayer). ... password to exit screensaver. ... I've booted into the previous kernel. ... kernel-modules, fglrx and NTFS, plus the vmwareplayer, all of which i updated ...
    (Fedora)
  • Re: Kernel 2.6.15-1.1830 lock-up issues
    ... require a password to exit screensaver. ... I did a hard reset and came back up, ... the previous kernel. ... to boot up the system, but my hard drives are not found with the live CD. ...
    (Fedora)
  • Re: Kernel 2.6.15-1.1830 lock-up issues
    ... password to exit screensaver. ... nothing - did another hard reset. ... into the previous kernel. ... After a night of searching out stuff on the web, and trying to find the answer in a linux book here at home, I finally figured out how to boot into the the previous kernel and am getting the same messages. ...
    (Fedora)