Reboot instead of debugger/dump from X11? (Re: an accidental way to pull the plug)

From: Robert Watson (rwatson_at_FreeBSD.org)
Date: 12/25/04

  • Next message: Eric Anholt: "Re: Reboot instead of debugger/dump from X11? (Re: an accidental way to pull the plug)" 
    Date: Sat, 25 Dec 2004 21:40:17 +0000 (GMT)
To: Chuck Robey <chuckr@chuckr.org>

    On Sat, 25 Dec 2004, Chuck Robey wrote:

    > I got a little too fast just now, and did something that I shouldn't
    > have done, but what's interesting is, FreeBSD decided to pull the plug
    > and instantly reboot, which is usually something to be regarded as
    > pathological, so I am letting you folks know. I haven't analyzed
    > exactly what happened to cause it, actually.

    With the recent 802.11 panic I posted about a bit earlier, I saw something
    rather odd: when the panic took place on the normal text console, the
    system dropped to the debugger. However, when it took place with X11
    running, I got an "instant reboot" -- no dump, etc. So something odd is
    happening during even normal failure modes when X11 is running for me. I
    wonder if anyone else is seeing this?

    Robert N M Watson FreeBSD Core Team, TrustedBSD Projects
    robert@fledge.watson.org Principal Research Scientist, McAfee Research

    >
    > Anyhow, I have been using FreeBSD as a fine platform for a Free database I
    > am constructing for a buddy of mine who has a video rental store. The
    > database, which was active at the time (the app is nearly complete) is
    > made with Python, gtk, pygtk (obviously) and the Sleepycat database. I
    > called those folks up and got the opinion that, as long as I didn't try to
    > distribute the software, the way I'm handling it (for free) it generally
    > falls under their free license, so I'm ok on that.
    >
    > Anyhow, I was talking screen dump pictures of the 6 data entry screens, in
    > X11, using xv to grab the windows. I got a bit confused with mouse
    > clicks, and actually asked it to do a grab while another grab was in delay
    > wait (it has a timer delay, which I set to 5 seconds). Result: reboot,
    > instant.
    >
    > I think that's it, although I will try to answer any questions. If you
    > folks are all too tied up with your own projects, it won't bother me, I'm
    > only trying to be conscientious about things.
    >
    > ----------------------------------------------------------------------------
    > Chuck Robey | Interests include C & Java programming, FreeBSD,
    > chuckr@chuckr.org | electronics, communications, and SF/Fantasy.
    >
    > New Year's Resolution: I will not sphroxify gullible people into looking up
    > fictitious words in the dictionary (on the wall at my old fraternity,
    > Signa Phi Nothing).
    > ----------------------------------------------------------------------------
    > _______________________________________________
    > freebsd-current@freebsd.org mailing list
    > http://lists.freebsd.org/mailman/listinfo/freebsd-current
    > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
    >

    _______________________________________________
    freebsd-current@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-current
    To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"

  • Next message: Eric Anholt: "Re: Reboot instead of debugger/dump from X11? (Re: an accidental way to pull the plug)"

    Relevant Pages

    • Re: Reboot instead of debugger/dump from X11? (Re: an accidental way to pull the plug)
      ... when it took place with X11 ... on startup and switch back to the text console. ... I have been using FreeBSD as a fine platform for a Free database I ... using xv to grab the windows. ...
      (freebsd-current)
    • vfs_mountroot panic on tru64 v5.1A
      ... When I tried to reboot, bcheckrc hung, stating that there was a ... On contacting Compaq, they decided that the hardware database was the ... This is when the major problem kicked in - the machine hung, ...
      (comp.unix.tru64)
    • Problem after 49.71 Days
      ... We have a SQL Server 7 machine running under Windows 2000 on a HP Compaq ... couple of seconds) and continue until we reboot the database machine. ... we **MUST** reboot the actual SQL Server machine. ... steps to ensure that connections are not held open this long. ...
      (microsoft.public.sqlserver.server)
    • Re: Windows 2003: 10g doesnt start automatically after reboot
      ... The OracleServiceORCL service is set to "automatic" and to ... There's nothing in the alert log: its last entry is "Completed: ... ALTER DATABASE OPEN" but the date is way before the last reboot. ...
      (comp.databases.oracle.server)
    • Re: Windows 2003: 10g doesnt start automatically after reboot
      ... There's nothing in the alert log: its last entry is "Completed: ... ALTER DATABASE OPEN" but the date is way before the last reboot. ... Make sure you are logged on as local administrator, ...
      (comp.databases.oracle.server)