| Autor |
Nachricht |
|
|
|
Titel: floating point exceptions
 Verfasst am: 02.10.2006, 06:15 Uhr
|
|
Anmeldung: 24. Jun 2006
Beiträge: 90
Wohnort: Muppet Theater
|
|
So, I press alt-f2, type in konqueror, press return, and get a box that says kdeinit can't launch my app. I happen to have yakuake running, lucky me, so I press f12, that terminal drops down and I type in konqueror, and terminal returns 'floating point exception'. Same thing when I try as user or root. I can't launch anything new. Everything from the K menu fails silently. I can only post this because I had left firefox open. Other info-
running easter rc4, last d-u was 2 weeks ago w/ h2's script. The computer has been running for 8 hrs, same session of firefox open the whole time, evolution open the whole time, and playing a live music feed on xmms from streamtuner for the last 6 hrs. Oh, and this happened yesterday after I had my laptop on for a long time, too. |
|
|
| |
|
|
|
 |
|
|
|
Titel: RE: floating point exceptions
Verfasst am: 27.10.2006, 04:19 Uhr
|
|
Anmeldung: 24. Jun 2006
Beiträge: 90
Wohnort: Muppet Theater
|
|
Update: the floating point exception is back. This time, I was using openoffice to work on slideshow for a talk I had to give today. Openoffice crashed I think, because it suddenly went away and I didn't think I had closed it. clicked on the openoffice icon again, chose impress, and the mouse bounced up and down like always. However, openoffice never came up. I pressed ctr-esc to bring up the process table, but nothing happened. I tried alt-f2 to bring up the run command box, typed in 'konsole' and got back the message 'kdeinit can't launch the application'. I pulled down the yakuake terminal that I always have running and tried to launch openoffice from there, and got an error message: floating point exception. Tried konqueror, got back 'floating point exception'. Tried firefox, and it opened up. Tried kmail, got floating point exception. Tried konsole, got floating point exception. Tried korganizer, got floating point exception.
So, I rebooted the machine. Tried to run openoffice, and got the floating point exception again. Power down, left machine off for 30 minutes, power back up, try to run openoffice, and got floating point exception.
The persistence of the problem made me think it was something software related, so I got a new kernel. 2.6.18.1-slh-smp2 using h2's script and didn't install the fglrx driver this time, because I saw a thread in a forum somplace where fglrx was supposedly making qt based apps crash. Maybe that explain why I couldn't get kde apps to open but firefox would? Doesn't kde rely pretty heavily on qt? By this time, I was happy to just be able to get OO.o up so I could give my talk.
After the talk, I booted back to the stock Easter RC4 kernel, ran removed kernels by script (remove-kernels-completely.sh) and then used h2 script to install 2.6.18-kanotix-1 kernel, madwifi drivers, fglrx driver, and do a d-u. Openoffice is currently opening just fine.
I am not really sure what the problem was or if I really fixed anything. It may have just 'gone away' for all I know. In IRC some one suggested that RAM might be bad. I'll run memtest tonight and see, but I have been using the same two sticks without issue for nearly two years. |
|
|
| |
|
|
|
|
|
|
|
Titel: RE: floating point exceptions
Verfasst am: 28.10.2006, 17:19 Uhr
|
|
Anmeldung: 24. Jun 2006
Beiträge: 90
Wohnort: Muppet Theater
|
|
| Sure enough, one stick of ram has an error. Can one bad spot on the ram cause all this grief? Who knows, but Kingston is willing to take it back. So, I'll get that swapped out and see if the problem stays away. |
|
|
| |
|
|
|
|
|
|
|
Titel: RE: floating point exceptions
Verfasst am: 28.10.2006, 17:29 Uhr
|
|
Team Member
Anmeldung: 03. Mai 2005
Beiträge: 1544
Wohnort: out there somewhere
|
|
Besides the ram problem (probably main problem and the cause) what does
Code:
xdpyinfo | grep -A1 dimen
give you ?
Kind of reminds me of Bug#384325 from which I have read is not only related to QPaintDevice but opening any app (especially qt and kde apps) |
_________________
h2's d-u script
h2's rdiff-backup script
Zuletzt bearbeitet von piper am 28.10.2006, 17:30 Uhr, insgesamt ein Mal bearbeitet
|
| |
|
|
|
|
|
|
|
Titel: RE: floating point exceptions
Verfasst am: 28.10.2006, 17:30 Uhr
|
|
Anmeldung: 05. Okt 2004
Beiträge: 2069
Wohnort: w3
|
|
^^^^^ welcome back, piper! ^^^^^
Greetings,
Chris |
_________________
"An operating system must operate."
|
| |
|
|
|
|
|
|
|
Titel: RE: floating point exceptions
Verfasst am: 28.10.2006, 17:31 Uhr
|
|
Team Member
Anmeldung: 03. Mai 2005
Beiträge: 1544
Wohnort: out there somewhere
|
|
|
|
|
|
|
|
|
Titel: Re: RE: floating point exceptions
Verfasst am: 29.10.2006, 18:56 Uhr
|
|
Anmeldung: 24. Jun 2006
Beiträge: 90
Wohnort: Muppet Theater
|
|
|
piper hat folgendes geschrieben::
Besides the ram problem (probably main problem and the cause) what does
Code:
xdpyinfo | grep -A1 dimen
give you ?
Kind of reminds me of Bug#384325 from which I have read is not only related to QPaintDevice but opening any app (especially qt and kde apps)
I get
Code:
noahsark@Rodan:~$ xdpyinfo | grep -A1 dimen
dimensions: 1400x1050 pixels (494x370 millimeters)
resolution: 72x72 dots per inch
I'll look into that bug you mentioned when I get a chance.
Oh, and this halloween theme is GREAT!! My avatar fits in perfectly! |
|
|
| |
|
|
|
|
|
|
|
Titel: RE: Re: RE: floating point exceptions
Verfasst am: 02.11.2006, 17:24 Uhr
|
|
Anmeldung: 24. Jun 2006
Beiträge: 90
Wohnort: Muppet Theater
|
|
OK. Haven't gotten to looking at the bug yet, but I do have a new stick of RAM. Kingston was great about swapping the faulty stick for a new one. It was a nice warm fuzzy experience, although I would rather not have had the bad RAM in the first place. I guess I'll find out in another month or so if the problem was something besides the RAM  |
|
|
| |
|
|
|
|
|
|
|
Titel: RE: Re: RE: floating point exceptions
Verfasst am: 02.11.2006, 18:04 Uhr
|
|
Team Member
Anmeldung: 03. Mai 2005
Beiträge: 1544
Wohnort: out there somewhere
|
|
|
|
|
|
|
|
|
Titel: RE: Re: RE: floating point exceptions
Verfasst am: 03.11.2006, 19:40 Uhr
|
|
Anmeldung: 24. Jun 2006
Beiträge: 90
Wohnort: Muppet Theater
|
|
Ok. It happened again- the floating point exception. I have amarok running to listen to mp3s off HDD while I work on a large slide show presentation in Impress. I also have konqueror open with several tabs open. I use one of the tabs to start going through a folder full of pictures looking for one to put into the slide show. I have gwenview installed so that I get a window pane with thumbnails and a large view of the selected thumbnail. After going through about 30 pictures or so Konqueror suddenly closes. No warning messages or anything. I try to open it upgain only to be told that KDEinit can't open it. I try it via terminal using yakuake which was also running and get a floating point exception. I also ran the code you suggested earlier, Piper. It spit out some weird stuff this time.
Code:
# konqueror
Floating point exception
# xdpyinfo | grep -A1 dimen
dimensions: 1400x1050 pixels (0x0 millimeters)
resolution: -2147483648x-2147483648 dots per inch
~$ xdpyinfo | grep -A1 dimen
dimensions: 1400x1050 pixels (0x0 millimeters)
resolution: -2147483648x-2147483648 dots per inch
I did change my resolution once this morning, to 1024x768 and then back again to 1400x1050. I wonder if that had anything to do with it. |
|
|
| |
|
|
|
|
|
|
|
Titel: RE: Re: RE: floating point exceptions
Verfasst am: 03.11.2006, 20:01 Uhr
|
|
Anmeldung: 24. Jun 2006
Beiträge: 90
Wohnort: Muppet Theater
|
|
|
|
|
|
|
|
|
Titel: RE: Re: RE: floating point exceptions
Verfasst am: 03.11.2006, 20:21 Uhr
|
|
Anmeldung: 12. Mar 2005
Beiträge: 1005
|
|
uncledeadley, do a new memtest scan, let it loop over and over for a few hours, then look at the results.
A new stick of memory can be bad, just like an old one, and some errors only show up after running the test several times, which takes some hours.
After that, you can fairly safely assume it's not ram, but not before doing these tests again. |
_________________
Read more on dist-upgrades using du-fixes-h2.sh script.
New: rdiff-backup script
|
| |
|
|
|
|
|
|
|
Titel: RE: Re: RE: floating point exceptions
Verfasst am: 03.11.2006, 21:47 Uhr
|
|
Anmeldung: 24. Jun 2006
Beiträge: 90
Wohnort: Muppet Theater
|
|
| I did check the new ram right after I got it. I installed it, minus the known good stick, and let memtest run 4 or 5 hours. I forget how many times it completed tests 1-10. I think it was around 8 or more times. No errors. Then I added the known good stick and tested both of them together and let them run overnight. No problems in the morning. |
|
|
| |
|
|
|
|
|
|
|
Titel: RE: Re: RE: floating point exceptions
Verfasst am: 03.11.2006, 23:51 Uhr
|
|
Team Member
Anmeldung: 03. Mai 2005
Beiträge: 1544
Wohnort: out there somewhere
|
|
I think what I would do (first) is drop down to init 3, do
fix-fonts -e then do fix-dpi-kdm then init 5 and see how things are
If that don't work, go back to init 3, type knxcc remove modelines, switch to ati not fglrx, go back to desktop (init 5) and see how things work, if all goes well, try installing fglrx again. Not sure if any of this will work but is worth a try |
_________________
h2's d-u script
h2's rdiff-backup script
|
| |
|
|
|
|
|
|
|
Titel: RE: Re: RE: floating point exceptions
Verfasst am: 03.11.2006, 23:58 Uhr
|
|
Anmeldung: 12. Mar 2005
Beiträge: 1005
|
|
|
|
|
|
|
|
|
Titel: RE: Re: RE: floating point exceptions
Verfasst am: 06.11.2006, 18:10 Uhr
|
|
Anmeldung: 24. Jun 2006
Beiträge: 90
Wohnort: Muppet Theater
|
|
Ok. I have a little more info. The problem arises when I change resolution. I have to change down to 1024x768 to hook up to a projector to give slide shows. That's when the dpi goes goofy.
Going to init 3 and then back to init 5 gets me back to a working gui. I removed the modelines, as suggested above, and the problem still persists. I also have the problem even when using vesa driver instead of fglrx (tested using a kernel that has no fglrx installed).
So, what I think I need to do is edit xorg.conf, but I'm not sure what to change. |
|
|
| |
|
|
|
|
|
|
