Re: Complete system freeze from virtual terminals / terminal emulators
[ If you want to make sure that your messages show up in the correct thread then you have to provide In-Reply-To headers. With your webmail interface it is probably best to use Reply-To-All and then to remove the email address of the original poster and to shift the list address from Cc: to To:. ] Thanks for the tips Florian :) I'm more used to forums than mailing lists :P I would also go to K-Menu Control Center Sound Multimedia System Bell and check the settings there. I don't know which other parts of KDE might want to use the system bell but it cannot hurt to make sure it is deactivated for all of KDE. I checked the system bell settings in the control center, and fortunately It was not enabled, so it shouldn't be a problem in any other applications. It looks like your X setup is OK as far as the graphics card is concerned (see my remarks below). Maybe the problem is in some weird way related to the pcspkr module which controls the system bell. You could try to (un)load the module and see if that makes any difference. The whole thing might be a very rare coincidence of several factors; tracking it down might be difficult and not really worth it. [...] Brilliant Florian, the problem does seem to be the pcspkr module. I modprobe -r pcspkr and the terminal works fine, then I modprobe pcspkr and everything freezes again. So I suppose all I have to do is blacklist the pcspkr module or something like that and my problems should be over. Should I file a bug report for this with the kernel team then?? Thanks again for all your help, Pat -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Complete system freeze from virtual terminals / terminal emulators
On Sat, Apr 14, 2007 at 21:09:16 -0700, Pat Primate wrote: Florian Kulzer wrote earlier: [...] It looks like your X setup is OK as far as the graphics card is concerned (see my remarks below). Maybe the problem is in some weird way related to the pcspkr module which controls the system bell. You could try to (un)load the module and see if that makes any difference. The whole thing might be a very rare coincidence of several factors; tracking it down might be difficult and not really worth it. [...] Brilliant Florian, the problem does seem to be the pcspkr module. I modprobe -r pcspkr and the terminal works fine, then I modprobe pcspkr and everything freezes again. So I suppose all I have to do is blacklist the pcspkr module or something like that and my problems should be over. Should I file a bug report for this with the kernel team then?? I would first test if the pcspkr module works (beeps) on the TTYs. This bug could very well be somewhere in KDE (or X) and the absence of the pcspkr module might fix things only because it leads to KDE/X skipping some buggy code. You can check dmesg | grep -i speaker for clues while playing around with the module. It would be especially interesting to see if the magic switch X-TTY-X changes anything in /dev/input. (Don't ask me why the device node of the speaker is generated in input.) Anyway, if all else fails you can simply use echo blacklist pcspkr /etc/modprobe.d/pcspkr to blacklist the pcspkr module during boot. -- Regards, Florian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Complete system freeze from virtual terminals / terminal emulators
Thank you Florian and Kamaraju, I am impressed by the speed and helpfulness of the Debian-Users mailing list :) As for my system, I am completely up to date (clean install of 4.0r0) and the crash doesn't happen in the tty1 terminals, Only inside KDE/X11. I checked the bell settings in Konsole (settings --- bell) and it was set to System bell and not visual bell, BUT (the good news) I tried setting the bell settings to 'system notification', 'visual bell', and 'none' and all three of those settings allow me to use konsole with NO CRASHES :D So it seems that the crashes only happen when the bell setting is set to 'system bell', but the funny thing is that I don't actually hear the bell beep, the crash happens first (even though my sound SEEMS to work fine for other things). So here are the attachments you wanted me to add, if you could help me figure out where to file a bug report and what info to include I would be very grateful :) Thank you both so much Pat 1) lspci | egrep -i 'vga|display|video|graphics 00:02.0 VGA compatible controller: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller (rev 04) 00:02.1 Display controller: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller (rev 04) -- 2) awk '/Section (Device|Module)/,/EndSection/' /etc/X11/xorg.conf Section Module Loadi2c Loadbitmap Loadddc Loaddri Loadextmod Loadfreetype Loadglx Loadint10 Loadvbe EndSection Section Device Identifier Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller Driver i810 BusID PCI:0:2:0 EndSection -- 3) patop:/home/pat# egrep '^\((EE|WW)\)' /var/log/Xorg.0.log (WW) The directory /usr/X11R6/lib/X11/fonts/misc does not exist. (WW) The directory /usr/share/fonts/X11/cyrillic does not exist. (WW) The directory /usr/X11R6/lib/X11/fonts/cyrillic does not exist. (WW) The directory /usr/X11R6/lib/X11/fonts/100dpi/ does not exist. (WW) The directory /usr/X11R6/lib/X11/fonts/75dpi/ does not exist. (WW) The directory /usr/X11R6/lib/X11/fonts/Type1 does not exist. (WW) The directory /usr/X11R6/lib/X11/fonts/100dpi does not exist. (WW) The directory /usr/X11R6/lib/X11/fonts/75dpi does not exist. (WW) The directory /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType does not exist. (WW) I810: No matching Device section for instance (BusID PCI:0:2:1) found (WW) I810(0): Bad V_BIOS checksum (WW) I810(0): Bad V_BIOS checksum (WW) I810(0): config file hsync range 43.8857-48.5053kHz not within DDC hsync ranges. (WW) I810(0): Bad V_BIOS checksum (WW) I810(0): Extended BIOS function 0x5f05 failed. (WW) AIGLX: 3D driver claims to not support visual 0x23 (WW) AIGLX: 3D driver claims to not support visual 0x24 (WW) AIGLX: 3D driver claims to not support visual 0x25 (WW) AIGLX: 3D driver claims to not support visual 0x26 (WW) AIGLX: 3D driver claims to not support visual 0x27 (WW) AIGLX: 3D driver claims to not support visual 0x28 (WW) AIGLX: 3D driver claims to not support visual 0x29 (WW) AIGLX: 3D driver claims to not support visual 0x2a (WW) AIGLX: 3D driver claims to not support visual 0x2b (WW) AIGLX: 3D driver claims to not support visual 0x2c (WW) AIGLX: 3D driver claims to not support visual 0x2d (WW) AIGLX: 3D driver claims to not support visual 0x2e (WW) AIGLX: 3D driver claims to not support visual 0x2f (WW) AIGLX: 3D driver claims to not support visual 0x30 (WW) AIGLX: 3D driver claims to not support visual 0x31 (WW) AIGLX: 3D driver claims to not support visual 0x32 -- h, bad v_bios checksum eh.. I had 915Resolution installed on a previous operating system - would that cause that??? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Complete system freeze from virtual terminals / terminal emulators
[ If you want to make sure that your messages show up in the correct thread then you have to provide In-Reply-To headers. With your webmail interface it is probably best to use Reply-To-All and then to remove the email address of the original poster and to shift the list address from Cc: to To:. ] On Fri, Apr 13, 2007 at 10:08:58 -0700, Pat Primate wrote: Thank you Florian and Kamaraju, I am impressed by the speed and helpfulness of the Debian-Users mailing list :) As for my system, I am completely up to date (clean install of 4.0r0) and the crash doesn't happen in the tty1 terminals, Only inside KDE/X11. I checked the bell settings in Konsole (settings --- bell) and it was set to System bell and not visual bell, BUT (the good news) I tried setting the bell settings to 'system notification', 'visual bell', and 'none' and all three of those settings allow me to use konsole with NO CRASHES :D So it seems that the crashes only happen when the bell setting is set to 'system bell', but the funny thing is that I don't actually hear the bell beep, the crash happens first (even though my sound SEEMS to work fine for other things). I would also go to K-Menu Control Center Sound Multimedia System Bell and check the settings there. I don't know which other parts of KDE might want to use the system bell but it cannot hurt to make sure it is deactivated for all of KDE. So here are the attachments you wanted me to add, if you could help me figure out where to file a bug report and what info to include I would be very grateful :) It looks like your X setup is OK as far as the graphics card is concerned (see my remarks below). Maybe the problem is in some weird way related to the pcspkr module which controls the system bell. You could try to (un)load the module and see if that makes any difference. The whole thing might be a very rare coincidence of several factors; tracking it down might be difficult and not really worth it. [...] 1) lspci | egrep -i 'vga|display|video|graphics 00:02.0 VGA compatible controller: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller (rev 04) 00:02.1 Display controller: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller (rev 04) -- 2) awk '/Section (Device|Module)/,/EndSection/' /etc/X11/xorg.conf Section Module Loadi2c Loadbitmap Loadddc Loaddri Loadextmod Loadfreetype Loadglx Loadint10 Loadvbe EndSection Section Device Identifier Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller Driver i810 BusID PCI:0:2:0 EndSection All is fine as far as I can tell. -- 3) patop:/home/pat# egrep '^\((EE|WW)\)' /var/log/Xorg.0.log (WW) The directory /usr/X11R6/lib/X11/fonts/misc does not exist. [ snip: similar errors for other font directories ] You can comment out these paths in the Files section of your xorg.conf to make these (harmless) warnings go away. (WW) I810: No matching Device section for instance (BusID PCI:0:2:1) found I see the same here (Intel Q965 chipset) and I never noticed any problem arising from it. (WW) I810(0): Bad V_BIOS checksum (WW) I810(0): Bad V_BIOS checksum (WW) I810(0): config file hsync range 43.8857-48.5053kHz not within DDC hsync ranges. (WW) I810(0): Bad V_BIOS checksum (WW) I810(0): Extended BIOS function 0x5f05 failed. My laptop (Intel 855GM chipset) works without trouble in spite of similar Bad V_BIOS and Extended BIOS function ... warnings. I think these are symptoms of minor glitches of the driver. You have to adjust the values in the Monitor section of xorg.conf if you want to get rid of the hsync range message. (WW) AIGLX: 3D driver claims to not support visual 0x23 [ snip: the same for other visuals ] Same story: I get these warnings too and I never had problems. I guess these messages will go away once AIGLX support for the Intel chipsets has matured a bit more. -- Regards, Florian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Complete system freeze from virtual terminals / terminal emulators
I have an LG LW40-S3MU1 laptop and I'm new to Debian and I would love to give her a good run, but I have run into a persistant problem. With a fresh install (all software is original Etch 4.0r0 versions) if I open up a virtual terminal / terminal emulator (like konsole) and press one of the arrow keys on my keyboard (e.g., the left arrow key) my entire system will freeze solid I have to hold the power button down for 4 or 5 seconds to shut it down. The freeze is easily replicated (every single time I try). To make this more clear, If I open up Konsole, Yakuake, Xterm, or Eterm (those were the 4 terminal emulators I tried it on) and I press the left arrow key - my entire system freezes completely The same thing happens if I press the right arrow key, or the down arrow key or the up arrow key. To make matters weirder, if I pres ctrl+alt+F1 to enter one of the tty1 sessions (I don't even have to log in) and then press ctrl+alt+F7 to get back to the KDE desktop I can suddenly go into any of the terminal emulation programs and press the arrow keys to my hearts content, without any freezes I would of course like to fix this, but I would also like to file a bug report for this. I unfortunately do not know which application to file the bug for, and I do not what/how to dig for more useful debug information. A post on the Debian-help forums suggested I access my Dmesg log from a live cd after the freeze - I will do that as soon as I have a live cd downloaded. Any advice or feedback would be appreciated Thank you very much Pat -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Complete system freeze from virtual terminals / terminal emulators
Pat Primate wrote: I have an LG LW40-S3MU1 laptop and I'm new to Debian and I would love to give her a good run, but I have run into a persistant problem. With a fresh install (all software is original Etch 4.0r0 versions) if I open up a virtual terminal / terminal emulator (like konsole) and press one of the arrow keys on my keyboard (e.g., the left arrow key) my entire system will freeze solid I have to hold the power button down for 4 or 5 seconds to shut it down. The freeze is easily replicated (every single time I try). When the freeze happens, are you able to ssh into that machine? If so, then you can check /var/log/Xorg.0.log and see if you find any errors. Another workaround is to completely disable the graphical environments (KDM etc.,) and see if you can reproduce the crash in a pure console based environment. If the console based system does not hang, run startx and see what errors you are receiving. BTW, are all your packages up to date? Sometimes when the KDE packages from different versions are mixed together, strange things can happen. hth raju -- Kamaraju S Kusumanchi http://www.people.cornell.edu/pages/kk288/ http://malayamaarutham.blogspot.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Complete system freeze from virtual terminals / terminal emulators
On Thu, Apr 12, 2007 at 11:39:20 -0700, Pat Primate wrote: I have an LG LW40-S3MU1 laptop and I'm new to Debian and I would love to give her a good run, but I have run into a persistant problem. With a fresh install (all software is original Etch 4.0r0 versions) if I open up a virtual terminal / terminal emulator (like konsole) and press one of the arrow keys on my keyboard (e.g., the left arrow key) my entire system will freeze solid I have to hold the power button down for 4 or 5 seconds to shut it down. The freeze is easily replicated (every single time I try). To make this more clear, If I open up Konsole, Yakuake, Xterm, or Eterm (those were the 4 terminal emulators I tried it on) and I press the left arrow key - my entire system freezes completely The same thing happens if I press the right arrow key, or the down arrow key or the up arrow key. It seems that the (visual) bell hangs your system. (???) To make matters weirder, if I pres ctrl+alt+F1 to enter one of the tty1 sessions (I don't even have to log in) and then press ctrl+alt+F7 to get back to the KDE desktop I can suddenly go into any of the terminal emulation programs and press the arrow keys to my hearts content, without any freezes Do you see the terminal window flash or do you hear a beep if you press one of the arrow keys in this situation? That would at least tell us if the bell could really be responsible for the hard lock. I think the main effect of your magic fix (X-tty-X) is that the video mode of your graphics card gets changed twice. Your initial problem might therefore be related to an initialization error of the video hardware, so maybe we should have a closer look at that. Please post the output of the following three commands: lspci | egrep -i 'vga|display|video|graphics' awk '/Section (Device|Module)/,/EndSection/' /etc/X11/xorg.conf egrep '^\((EE|WW)\)' /var/log/Xorg.0.log -- Regards, Florian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Subject: Re: Complete system freeze from virtual terminals / terminal emulators
Ooops, sorry everyone, I accidently forgot to put the subject in my previous post. So if Florian or Kamaraju did not read my 'no subject' post (sent 2 minutes ago) please do so, I have responses to your questions :) Thanx pat -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
