[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#2351: Re: xdm doesn't detect gpm mouse lock

On Sun, 18 Feb 1996, Stephen Early wrote:

> On Sun, 18 Feb 1996, Kevin M Bealer wrote:
> > When I run gpm (from init.d in my case) then run xdm, xdm either:
> > 	a) general protection faults listed as 0000
> This is a kernel bug.
> > 	b) repeatedly runs and lets die the X server (at least it looks like
> > 		this is what is happening.  I needed to reboot to stop it,
> > 		then it gives a gp fault.
> This is a bit of bad design in xdm. I don't know how easy it would be to
> fix it; I'll have a look at the source when I have some time.
> > I recommend that xdm detect fatal conditions such as unavailable resources,
> > or that the X servers be given a way to communicate to xdm that they will
> > not recover from whatever error by reloading.  Perhaps there are some
> > considerations of a user creating such a condition in order to terminate xdm
> > and thus breach security, esp. if xdm is started manually by the root user.
> I think the ideal situation would be that an X server that couldn't start
> properly would exit with a particular exit code, which xdm would notice
> and wouldn't attempt to start the server again, possibly putting a message
> in the syslog or its own log file.
> I'm sure that xdm does this already in some cases, but I haven't had time
> to look at the source so I'll shut up for now and post more when I know
> what I'm talking about.
> > When xdm is cycling X, hitting the cntrl-alt-del allows me to view a general
> > protection fault before reboot:
> >
> > general protection: 0000
> > EIP: 0010:0014a115
> > EFLAGS: 00010206
> > eax: 6e6f632d ebx: 00215910 ecx: 007c1dd0 edx: 002c5000
> > esi: 00330f54 edi: 00330f54 ebp: 007c1e8c esp: 007c1e00
> > ds: 0018 es: 0018 fs: 002b gs: 002b ss: 0018
> >
> > Process xdm (pid: 621, process nr 6, stackpage=007c10000
> >                                       or is it 007c|0000?
> Definitely a kernel problem of some sort.
> > I hit scroll-lock during reboot and the system just sat there until I was
> > done... should it listen for scroll lock while it's rebooting?
> This is a question for somebody else. If you're worried about it, I
> suggest you post a separate message. Presumably the shutdown script is
> blocking on output to the console.
> Steve Early
> sde1000@cam.ac.uk

As far as kernel bugs go, let me add then that this happened with 1.2.13-7
after I added a whole mess of stuff from the develoment tree.  I'm not
concerned about the scroll lock, just curious.


So you think you know the real meaning of fear?       |
Yeah, you think you do know, but I doubt it.          |  kmb203@psu.edu
When you sit in a shelter with bombs falling all over.|  running debian
And the houses around you are burning like torches.   |  Linux 1.2.13
I agree that you experience horror and fright         |
For such moments are dreadful, for as long as they last,
But the all-clear sounds--then it's okay--          |  -- Ilya Selvinskiy
You take a deep breath, the stress has passed by.   | (Taken from "The Sum
But real fear is a stone deep down in your chest.   |   of All Fears" by
You hear me?  A stone.  That's what it is, no more. | Tom Clancy pg. 182.)

Reply to: