| Author |
Logout very strange??
|
|
| prezbedard 2003-02-01, 1:35 pm |
| OK this is bit weird. I know I still have a LOT to learn about linux but listen to this. Just several minutes ago I'm sitting here using my redhat when the screen blanks so get a fury thinking it is my rebooting problem again which by the way is much better. So it so doesn't reboot(I checked the system log to be sure) but goes right to the log in screen and it did this twice in about a minute.
Any of you linux experts every seen this before?
Thanks
just happened again twice | |
| Boulware5 2003-02-01, 6:02 pm |
| If you are in a console session and type 'exit' it would take you to a login screen. Could you have down that? There's a few ways to reboot...
[as root]
shutdown -r now
typing "reboot"
hitting ctrl-alt-del
telinit 6 | |
| prezbedard 2003-02-01, 6:10 pm |
| quote:
Originally posted by Boulware5
If you are in a console session and type 'exit' it would take you to a login screen. Could you have down that? There's a few ways to reboot...
[as root]
shutdown -r now
typing "reboot"
hitting ctrl-alt-del
telinit 6
Nope I was in the gui and had a terminal window open one of the times. It seem to doing logout on its own
Thanks
It just did it again while I was using evolution.
Here are some syslog entries that appear at the time the logout happened these other similar if not the same as when it logged out before:
Feb 1 19:04:35 localhost gdm(pam_unix)[2587]: session closed for user Greg
Feb 1 19:04:37 localhost gdm[2587]: gdm_slave_xioerror_handler: Fatal X error - Restarting :0
Feb 1 19:04:49 localhost gdm(pam_unix)[2916]: session opened for user Greg by (uid=0)
Feb 1 19:04:54 localhost kernel: Assertion failed! buffer != NULL,via82cxxx_audio.c,via_dsp_write,line=2308
Feb 1 19:05:00 localhost kernel: cdrom: This disc doesn't have any tracks I recognize!
Feb 1 19:09:13 localhost kernel: cdrom: This disc doesn't have any tracks I recognize!
Feb 1 19:09:55 localhost last message repeated 2 times
Feb 1 19:12:37 localhost userhelper: pam_timestamp: timestamp file `/var/run/sudo/Greg/unknown:root' is only 147 seconds old, allowing access to redhat-logviewer for UID 500
Happened yet again just now | |
| Boulware5 2003-02-01, 6:19 pm |
| Then you must have only logged out of X. There's ways in X to reboot while in GUI. Also there are ways to log out and return to a console login. | |
| prezbedard 2003-02-01, 6:24 pm |
| quote:
Originally posted by Boulware5
Then you must have only logged out of X. There's ways in X to reboot while in GUI. Also there are ways to log out and return to a console login.
It didn't reboot just logged out.
Here is the log of what just happened
I just noticed that in the log it says
Fatal X error. What could be causing that?
Feb 1 19:14:23 localhost gdm(pam_unix)[2916]: session closed for user Greg
Feb 1 19:14:24 localhost gdm[2916]: gdm_slave_xioerror_handler: Fatal X error - Restarting :0
Feb 1 19:14:36 localhost gdm(pam_unix)[3170]: session opened for user Greg by (uid=0)
Feb 1 19:14:40 localhost kernel: Assertion failed! buffer != NULL,via82cxxx_audio.c,via_dsp_write,line=2308
Feb 1 19:14:44 localhost kernel: cdrom: This disc doesn't have any tracks I recognize!
Feb 1 19:15:18 localhost modprobe: modprobe: Can't locate module sound-slot-1
Feb 1 19:15:18 localhost modprobe: modprobe: Can't locate module sound-service-1-0
Feb 1 19:15:19 localhost modprobe: modprobe: Can't locate module sound-slot-1
Feb 1 19:15:19 localhost modprobe: modprobe: Can't locate module sound-service-1-0 | |
| prezbedard 2003-02-01, 6:31 pm |
| quote:
Originally posted by prezbedard
It didn't reboot just logged out.
just didn't twice while I was editing this post
Here is the log of what just happened
I just noticed that in the log it says
Fatal X error. What could be causing that?
Feb 1 19:14:23 localhost gdm(pam_unix)[2916]: session closed for user Greg
Feb 1 19:14:24 localhost gdm[2916]: gdm_slave_xioerror_handler: Fatal X error - Restarting :0
Feb 1 19:14:36 localhost gdm(pam_unix)[3170]: session opened for user Greg by (uid=0)
Feb 1 19:14:40 localhost kernel: Assertion failed! buffer != NULL,via82cxxx_audio.c,via_dsp_write,line=2308
Feb 1 19:14:44 localhost kernel: cdrom: This disc doesn't have any tracks I recognize!
Feb 1 19:15:18 localhost modprobe: modprobe: Can't locate module sound-slot-1
Feb 1 19:15:18 localhost modprobe: modprobe: Can't locate module sound-service-1-0
Feb 1 19:15:19 localhost modprobe: modprobe: Can't locate module sound-slot-1
Feb 1 19:15:19 localhost modprobe: modprobe: Can't locate module sound-service-1-0
| |
| Boulware5 2003-02-01, 6:34 pm |
| It happen that one time or keeps doing it? Looks like something with your sound card and CD. But you could have probably come to that conclusion.  I have sometimes also got X errors while logging out. It wasn't harmful and didn't seem like a big deal so I ignored them. | |
| prezbedard 2003-02-01, 6:43 pm |
| quote:
Originally posted by Boulware5
It happen that one time or keeps doing it? Looks like something with your sound card and CD. But you could have probably come to that conclusion. I have sometimes also got X errors while logging out. It wasn't harmful and didn't seem like a big deal so I ignored them.
but it is logging out automacticlly.
I am not telling it to log off
Keeps doing it
just did it again
I have had the sound card error for quite a while the cd one is new though.
It also only seems to happen when I am actively using the system
This has started today I have never seen this before today
and it just did it again when I went to check this thread agin but seemed dandy when I was sittimg odley by | |
| Boulware5 2003-02-01, 8:01 pm |
| Hm, um, have you checked youe xfree86 log file and see what that says? See if you can find it in /var/log/XFree86.n.log where n is the display number of your X server. | |
| prezbedard 2003-02-02, 5:11 pm |
| This line was repeated quite a few times.
GetModeLine - scrn: 0 clock: 78800
GetModeLine - hdsp: 1024 hbeg: 1040 hend: 1136 httl: 1312
vdsp: 768 vbeg: 769 vend: 772 vttl: 800 flags: 5
While I was posting this it logged out again and I looked at the log and all of the above repeated entries were gone and I had this with just the above posted once.
(**) Option "dpms"
(**) TRIDENT(0): DPMS enabled
(II) TRIDENT(0): XvFlags: VID_ZOOM_INV VID_ZOOM_MINI
(II) Initializing built-in extension MIT-SHM
(II) Initializing built-in extension XInputExtension
(II) Initializing built-in extension XTEST
(II) Initializing built-in extension XKEYBOARD
(II) Initializing built-in extension LBX
(II) Initializing built-in extension XC-APPGROUP
(II) Initializing built-in extension SECURITY
(II) Initializing built-in extension XINERAMA
(II) Initializing built-in extension XFree86-Bigfont
(II) Initializing built-in extension RENDER
(**) Option "Protocol" "PS/2"
(**) Mouse0: Protocol: "PS/2"
(**) Option "CorePointer"
(**) Mouse0: Core Pointer
(**) Option "Device" "/dev/psaux"
(**) Option "Emulate3Buttons" "no"
(**) Option "ZAxisMapping" "4 5"
(**) Mouse0: ZAxisMapping: buttons 4 and 5
(**) Mouse0: Buttons: 5
(**) Option "Protocol" "IMPS/2"
(**) Mouse1: Protocol: "IMPS/2"
(**) Option "SendCoreEvents"
(**) Mouse1: always reports core events
(**) Option "Device" "/dev/input/mice"
(**) Option "Emulate3Buttons" "no"
(**) Option "ZAxisMapping" "4 5"
(**) Mouse1: ZAxisMapping: buttons 4 and 5
(**) Mouse1: Buttons: 5
(II) Keyboard "Keyboard0" handled by legacy driver
(II) XINPUT: Adding extended input device "Mouse1" (type: MOUSE)
(II) XINPUT: Adding extended input device "Mouse0" (type: MOUSE)
GetModeLine - scrn: 0 clock: 78800
Should I try rebooting?
This only happens when I'm using it. I had the screen locked all night and it was fine until I went to this post again.
Also I just noticed that the cdrom light is blinking and there is no cd in it.
That could be the reason for the cdrom error in the system log. I'm wondering what could be causing the light to contune to blink? The system might be attempting to read form the drive. What could be causing it to do that? | |
| Boulware5 2003-02-02, 6:22 pm |
| Not sure...maybe one of the experts (MrLinuxGuy) can chime in. | |
| prezbedard 2003-02-02, 6:31 pm |
| Now the trick is to get him to read this. | |
| Boulware5 2003-02-02, 7:15 pm |
| He will.
RANDY! YOU OUT THERE?!?!
Shouting usually works  | |
| prezbedard 2003-02-02, 8:08 pm |
| I would think if he had seen this he would of offered his insight so I guess he hasn't looked at it.
I'm going to do I quick search on google to see if I get any results. | |
| prezbedard 2003-02-02, 9:14 pm |
| I just found something that talks about this issue in search on RedHat's site
redhat source 1
It talks about killing network connectively but I don't seem to have that in mine. | |
| prezbedard 2003-02-02, 9:36 pm |
| I have had it happen with different combinitions of the following
Evolution
Mozilla
Terminal Window
emacs
System log veiwer
a weather program.
However I did npt seen my system using
100% cpu but with nothing else running I was looking at system monitor and it was fluctuating between 3&-10%
Also we have very similar specs
CPU: AMD 1700+ XP
Mobo: Soyo Kvem pro - VIA KLE133 chipset
Memory: 1292160KB
OS: Redhat Linux 8.0
I am going to try and reboot which seems to have worked for this guy but I will wait a little longer for your input
This person seems to have very similar symptons
"I was running several applications on top an X Windows session, I
noticed the CPU usage at a 100%. Running top to see what was hogging
all of the CPU showed X windows running at ~50% and top the other %50.
However top was extremely slow to return and rest of the machine started
crawling to a halt. X windows then exited killing all of the apps.
Apps running:
Gnome2
Evolution
Galeon
ArgoUML (Java based UML program)
Eclipse
CD Player
Logging back in I looked at the logs and noticed a number of Oops
messages (logs and output from ksymoops below).
Opening evolution to send an E. mail the problem occurred again, this
time the log only seemed to show a partial oops trace and running it
through ksymoops caused a segmenation fault.
This problem occurred 3 more times before I rebooted, which seemed to
alleviate the problem. I did notice that any program that tried to
access current process information (eg. ps and top) ran extremely slow
(30 secs to 1 min to return) and would use 100% CPU.
I have had a number of problems with this system from kernel versions
2.4.8 to 2.4.19. Faults such as this where X windows or various other
programs will exit through to hard lockups of the system. The problem
most commonly seems to occur when the memory usage is very high (around
100%) when the system would start to swap.
I have heard that there have been various problems with AMD CPUs on VIA
chipsets. I saw a patch available that is intended to improve general
stability of AMD CPUs however it looked like the patch was only for
2.5.x kernels.
Any help, suggestions (even if it is buy an different motherboard and/or
CPU) would be appreciated.
Kind regards,
Mike.
System Info:
CPU: AMD 1600XP
Mobo: Asus A7V333 - VIA KT333 chipset
Memory: 1292160KB
OS: Redhat Linux 8.0" | |
| prezbedard 2003-02-04, 1:16 pm |
| Well I rebooted and shortly after it logged itself out again while using evolution.
Howver after I logged back in I went back into evolution and mozilla and it did not reboot. I even opened up system log and it didn't log out. I am still quite suspicious. I do not want to have to reinstall again. | |
| Mr. Linux Guy 2003-02-05, 6:41 am |
| Check your environment variables. I remember setting up some machines where I had to put:
set autologout=60
in the .cshrc file so that after a period of inacitivity, the user would automatically get logged off. Also check your log files to see if this is what might be happening. There is probably a default setting that was included that you weren't aware of that does this for security purposes. | |
| prezbedard 2003-02-05, 9:23 am |
| quote:
Originally posted by Mr. Linux Guy
Check your environment variables. I remember setting up some machines where I had to put:
set autologout=60
in the .cshrc file so that after a period of inacitivity, the user would automatically get logged off. Also check your log files to see if this is what might be happening. There is probably a default setting that was included that you weren't aware of that does this for security purposes.
One of my log files has this which seems to indicate a X windows crash:
Feb 1 19:14:23 localhost gdm(pam_unix)[2916]: session closed for user Greg
Feb 1 19:14:24 localhost gdm[2916]: gdm_slave_xioerror_handler: Fatal X error - Restarting :0
This error is in each instance of the automatic logout.
You mentioned above that it logs out do to inactivity. This only happens though when I'm activily using it. I leave it alone(screen locked) all night and it is fine.
Thanks | |
| prezbedard 2003-02-05, 9:56 am |
| I just checked that file.
This is what it said
csh configuration for all shell invocations. The contents were for configuring a shell. At least that is what it looked like. I didn't see any automatic logout setting or something pertaining to that. | |
| Mr. Linux Guy 2003-02-05, 12:33 pm |
| Looks like gdm is encountering some error that it is unable to recover from. You might want to try rerunning the configuration program. It might be looking for some fonts or screens that it is unable to find. Can you post more of your config file, like maybe 50 lines or so before the crash occurs? I have heard of this happening a number of times and it is usually because the gui has a conmfiguration problem or the partiocular version of gdm is not fully supported on a certain distro. I am assuming that you installed from a CD-ROM, so that shouldn't be a problem. before you start over, make sure to save your current configuration files just in case the reconfiguration makes things worse (or doesn't help at all).
It's not an environment variable problem. That wouldn't cause a fatal X error. I was just thinking that it was possible that a default logout time was set without you being aware of it.
Another thing occurs to me . . . it could be a permissions problem if this only occurs when you are using it. Does this occur when you are logged in as root ? (Yeah, yeah, you should never do that, but sometimes when debugging . . . ) | |
| prezbedard 2003-02-06, 9:27 am |
| Actually since this has been happening I haven't logged in as root. I can I determine if it is indeed a permissions problem? I am just using the standard apps
email, mozilla. It has happened when I've had the systen log view open too. For config file do you mean the XFree log?
I'm going to log in as root and get the log files and run the X config.
Thanks again | |
| prezbedard 2003-02-06, 9:47 am |
| It just happened while I was logged in as root. I was checking the log files and found something interesting of note but it logged out on me when I was trying to post.
Had to to do with the video card default innvocation then that repeated with a higher resoltion each time yxx i.e 800x600
Though this is the second time I installed linux on the same machine and this did not happen before. Is there anyway to use the CD roms to do a 'repair' installation?
I'm going to check to see what the log entry says when it logged out while I was in as root.
Ok
same error when root was logged out.
gdm_slave_xioerror_handler:
Fatal X error restarting:0 | |
| Mr. Linux Guy 2003-02-13, 12:55 pm |
| Did you try reconfiguring X? | |
| prezbedard 2003-02-13, 6:18 pm |
| quote:
Originally posted by Mr. Linux Guy
Did you try reconfiguring X?
How can I get to a text login to run the X configuration? I am going to set up a second linux test box.
I dedcided to reload rh8 | |
| Mr. Linux Guy 2003-02-13, 6:40 pm |
| Install xf86config when you install RH. That and XF86Setup should allow you to configure X using only text mode or 16 bit VGA mode which any monitor should be able to handle. "Fatal Error" makes it seem like you have some configuration problem with X. This rarely happens to RH nowadays, but it is occasionally a prob. Might need to get your video card specs and hand configure as much as possible. | |
| prezbedard 2003-02-13, 7:16 pm |
| Thats strange because Red Hat was working fine one the system for a while then it started doing that. The video card is pretty generic Trident Cyberblade on board.
The other system I'm going to use is an 2 year old emachine so everything on that is nothing fancy.
thanks |
|
|
|