Hi
I have a Toshiba m65 notebook running Mandriva 2006. Everything works great. Mandriva supports most all the features that Win does. The problem is that for some unknown reason the system will completely lockup. it seems to be random. last night it ran for hours before it froze. but on reboot it froze loading KDE. then after next reboot it ran for about half hour or so. (The computer actually belongs to my mom, so i have to make it work in KDE.) But its not KDE or X that is locking up. the entire system locks, keyboard, touchpad, sound stops. the wireless network shuts down. (so cant ssh that way.) the only thing that responds is the power switch.

there i don't have any error messages. can't access it through the wireless network. (haven't had it hooked up to wired network when it's locked up.)

I've been thinking its some linux problem. But last night i got to thinking that maybe it wasn't a software problem but something to do with the hardware. i've never had linux lock up on my personal computer. sure X has frozen, but Ctl+Alt+Backspace saves the day. when this system locks, its gone.

PhoenixBIOS v1.10
Intel Pentium 4 M 1.7Ghz
Mobil Intel 915GM Express Chipset
512MB RAM
60GB HD
DVD-+R/RW
Intel Pro/Wireless 2200BG (802.11 b/g)
Intel Graphics Media Accelerator 900
Realtek ALC250 Software Sound
PCMCIA
ExpressCard
Bridge Media Adapter (for SD, MS, and XD memory cards)
1 Firewire port
Integrated v.92 Modem
Intel Pro/100 Network Connection

So if anyone might know whats going on or how to start troubleshooting this i'd apprciate it.
As i said this computer is my moms. she seems to like Mandriva, and i'm hoping she won't have to go back to Win. i'd rather she give linux props then M$ her money.

do a fsck on the partiton on which u have installed the mandriva.

use a live CD/rescue cd

hi

i used a rescue disk after the last crash and saved all the files in /var/log to a different location. i was looking at them but they didn't seem very helpful. of course i don't know which to look at.

the last two minutes of the "messages" file were this:

Dec 22 16:46:27 toshiba drakconf.real[7069]: modified file /etc/mcc.conf
Dec 22 16:46:27 toshiba su(pam_unix)[7063]: session closed for user root
Dec 22 16:47:01 toshiba kde3(pam_unix)[6615]: session closed for user marge
Dec 22 16:47:03 toshiba kernel: mtrr: base(0xc0020000) is not aligned on a size(0x180000) boundary
Dec 22 16:47:06 toshiba kdm_greet[8973]: Can't open default user face
Dec 22 16:47:10 toshiba gconfd (marge-6956): GConf server is not in use, shutting down.
Dec 22 16:47:10 toshiba gconfd (marge-6956): Exiting
Dec 22 16:47:18 toshiba kde3(pam_unix)[8968]: session opened for user jacob by (uid=0)
Dec 22 16:47:18 toshiba net_applet[9058]: ### Program is starting ###
Dec 22 16:47:19 toshiba gconfd (jacob-9110): starting (version 2.10.1), pid 9110 user 'jacob'
Dec 22 16:47:19 toshiba gconfd (jacob-9110): Resolved address "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only configuration source at position 0
Dec 22 16:47:19 toshiba gconfd (jacob-9110): Resolved address "xml:readwrite:/home/jacob/.gconf" to a writable configuration source at position 1
Dec 22 16:47:19 toshiba gconfd (jacob-9110): Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only configuration source at position 2
Dec 22 16:48:20 toshiba nmbd[6159]: [2005/12/22 16:48:20, 0] nmbd/nmbd_incomingdgrams.crocess_local_master_announce(311)
Dec 22 16:48:20 toshiba nmbd[6159]: process_local_master_announce: Server JACOB-P4 at IP 192.168.1.102 is announcing itself as a local master browser for workgroup JACOB and we think we are master. Forcing election.
Dec 22 16:48:20 toshiba nmbd[6159]: [2005/12/22 16:48:20, 0] nmbd/nmbd_become_lmb.c:unbecome_local_master_success(149)
Dec 22 16:48:20 toshiba nmbd[6159]: *****
Dec 22 16:48:20 toshiba nmbd[6159]:
Dec 22 16:48:20 toshiba nmbd[6159]: Samba name server TOSHIBA has stopped being a local master browser for workgroup JACOB on subnet 192.168.1.104
Dec 22 16:48:20 toshiba nmbd[6159]:
Dec 22 16:48:20 toshiba nmbd[6159]: *****
Dec 22 16:48:37 toshiba nmbd[6159]: [2005/12/22 16:48:37, 0] nmbd/nmbd_become_lmb.c:become_local_master_stage2(396)
Dec 22 16:48:37 toshiba nmbd[6159]: *****
Dec 22 16:48:37 toshiba nmbd[6159]:
Dec 22 16:48:37 toshiba nmbd[6159]: Samba name server TOSHIBA is now a local master browser for workgroup JACOB on subnet 192.168.1.104
Dec 22 16:48:37 toshiba nmbd[6159]:
Dec 22 16:48:37 toshiba nmbd[6159]: *****

this is relevent lines from acpid file:

[Thu Dec 22 16:45:22 2005] received event "ac_adapter ACAD 00000080 00000000"
[Thu Dec 22 16:45:22 2005] notifying client 5543[0:0]
[Thu Dec 22 16:45:22 2005] executing action "/etc/acpi/actions/lm_ac_adapter.sh ac_adapter ACAD 00000080 00000000"
[Thu Dec 22 16:45:22 2005] BEGIN HANDLER MESSAGES
Laptop mode enabled, activesed: can't read /var/run/laptop-mode-nolm-mountopts: No such file or directory
.
HDIO_DRIVE_CMD(identify) failed: Inappropriate ioctl for device
HDIO_DRIVE_CMD(identify) failed: Inappropriate ioctl for device
HDIO_DRIVE_CMD(identify) failed: Inappropriate ioctl for device
[Thu Dec 22 16:45:22 2005] END HANDLER MESSAGES
[Thu Dec 22 16:45:22 2005] action exited with status 0
[Thu Dec 22 16:45:22 2005] completed event "ac_adapter ACAD 00000080 00000000"
[Thu Dec 22 16:45:22 2005] received event "battery BAT1 00000080 00000001"
[Thu Dec 22 16:45:22 2005] notifying client 5543[0:0]
[Thu Dec 22 16:45:22 2005] executing action "/etc/acpi/actions/lm_battery.sh battery BAT1 00000080 00000001"
[Thu Dec 22 16:45:22 2005] BEGIN HANDLER MESSAGES
remaining capacity: 4400 mAh
[Thu Dec 22 16:45:23 2005] END HANDLER MESSAGES
[Thu Dec 22 16:45:23 2005] action exited with status 0
[Thu Dec 22 16:45:23 2005] completed event "battery BAT1 00000080 00000001"
[Thu Dec 22 16:45:43 2005] received event "button/lid LID0 00000080 00000004"
[Thu Dec 22 16:45:43 2005] notifying client 5543[0:0]
[Thu Dec 22 16:45:43 2005] executing action "/etc/acpi/actions/lm_lid.sh button/lid LID0 00000080 00000004"
[Thu Dec 22 16:45:43 2005] BEGIN HANDLER MESSAGES
Laptop mode enabled, active.
HDIO_DRIVE_CMD(identify) failed: Inappropriate ioctl for device
HDIO_DRIVE_CMD(identify) failed: Inappropriate ioctl for device
HDIO_DRIVE_CMD(identify) failed: Inappropriate ioctl for device
[Thu Dec 22 16:45:43 2005] END HANDLER MESSAGES
[Thu Dec 22 16:45:43 2005] action exited with status 0
[Thu Dec 22 16:45:43 2005] completed event "button/lid LID0 00000080 00000004"
[Thu Dec 22 16:47:03 2005] client connected from 5543[0:0]
[Thu Dec 22 16:47:03 2005] 1 client rule loaded


don't know what it all means. but i those were things that i thought might be important.

hello
heres a note.
after some fooling around and setting up system monitors on the KDE task panel i think i might have narrowed down the problem. i noticed that the cpu load meter was spiking. i checked the kde process watcher program and found that kded was using at one point 75% or more cpu. i did some googling and found that other people have had the same problem. kded will over load the cpu causing the KDE and the system lockup. it seems that kded has some kinda bug in the KDE version i got with mandriva. havent read the answer yet. still looking around. but i thought i'd post my progress in case anyone is interested.

which kde are u using

is it 3.4

Oh, cool. Did any of you think about the fact, that the default fstab for MDK does not have the noatime option?? That could be the problem, not KDE.

the problem seems to be kded. i kill it every time i enter kde, and as long as its gone, no freeze-ups. i have been opening KDE process viewer and killing the daemon each time i use KDE. it would be nice to prevent it from loading in the first place. until i can spend time on a proper fix. it controls the battery monitor for the laptop, and the cookies for konqueror, among other things. so i need to find a sure fix. but until then... any ideas?
...
i was just surfing and was noticing that kded may not be the root of the problem. i read of one bug that was related to klaptop and qt. but i don't know if that applies. never noticed klaptop running. but kded is just a daemon that makes some other things work, e.g. Kat, Kwallet, battery monitor, etc.
so it could be one of those that is causing problems.
this is the bug id about qt:
67929
kde bug site (i couldn't post url, too new of a user)
it offers a patch at the end. but i'm using binaries, from RPMs.
and i don't know how to patch.
i guess i'll just keep working on it.

I am trying to resolve simular issues on multiple Suse 9.3 IBM devices. I am however, not running KDE. I am running Windowsmaker.

I have just set the runlevel to 3 to see if that makes any difference by not starting any windows or desktop manager.

I am trying to check the driver versions for my hardware now. Last thing I did was upgrade my BIOS to latest & greatest & still have the problem.

I will post any finding I have if they may help.

Steve

Lol. WINDOWSMAKER.