[SOLVED] Dual boot: Win7/HD Ok, LXDE/SSD froze.

[Just17]

Do you ever get the system freezing when using PCLOS without a VM running?

How many VMs do you have running normally?

You reported this

Memory 7.4GB/16GB,

Does that mean nearly half the memory (8GB) was in use at the time?

Is this a normal situation?

What kernel is in use in PCLOS?  Have you tried an alternate kernel?  If so did you have any different results?

get the results from the following commands please ...

dmesg | grep -i error

dmesg | grep -i fail

dmesg | grep -i warn

There *might* be something relevant ......


I would suggest a memory test .......  in case some of the memory around the 8GB mark is causing the problem .....

[joejac]

Hello Just18,
1.- Yes, today it got freeze with no VM.
2.- I normally run 2 VMs so I am always around 8 to 9 GB.
3.- My host uses kernel: 3.2.18-pclos1.pae.bfs
4.- dmesg | grep -i error

pci0000:00: ACPI _OSC request failed (AE_ERROR), returned control mask: 0x1d
ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20110623/psargs-359)
ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT1._GTF] (Node e602f588), AE_NOT_FOUND (20110623/psparse-536)
ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20110623/psargs-359)
ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT0._GTF] (Node e602f540), AE_NOT_FOUND (20110623/psparse-536)
ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20110623/psargs-359)
ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT4._GTF] (Node e602f660), AE_NOT_FOUND (20110623/psparse-536)
ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20110623/psargs-359)
ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT0._GTF] (Node e602f540), AE_NOT_FOUND (20110623/psparse-536)
ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20110623/psargs-359)
ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT4._GTF] (Node e602f660), AE_NOT_FOUND (20110623/psparse-536)
ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20110623/psargs-359)
ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT1._GTF] (Node e602f588), AE_NOT_FOUND (20110623/psparse-536)

5.- dmesg | grep -i fail

pci0000:00: ACPI _OSC request failed (AE_ERROR), returned control mask: 0x1d
ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20110623/psargs-359)
ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT1._GTF] (Node e602f588), AE_NOT_FOUND (20110623/psparse-536)
ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20110623/psargs-359)
ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT0._GTF] (Node e602f540), AE_NOT_FOUND (20110623/psparse-536)
ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20110623/psargs-359)
ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT4._GTF] (Node e602f660), AE_NOT_FOUND (20110623/psparse-536)
ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20110623/psargs-359)
ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT0._GTF] (Node e602f540), AE_NOT_FOUND (20110623/psparse-536)
ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20110623/psargs-359)
ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT4._GTF] (Node e602f660), AE_NOT_FOUND (20110623/psparse-536)
ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20110623/psargs-359)
ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT1._GTF] (Node e602f588), AE_NOT_FOUND (20110623/psparse-536)
xhci_hcd 0000:00:14.0: Failed to enable MSI-X

6.- dmesg | grep -i warn

xhci_hcd 0000:00:14.0: WARN: short transfer on control ep
xhci_hcd 0000:00:14.0: WARN: short transfer on control ep
xhci_hcd 0000:00:14.0: WARN: short transfer on control ep
xhci_hcd 0000:00:14.0: WARN: short transfer on control ep
warning: `VirtualBox' uses 32-bit capabilities (legacy support in use)

7.- I also found this that points to kernel 3.3.6 as a possible solution, can I get a test kernel 3.3.6 for LXDE?
7.1 http://forums.linuxmint.com/viewtopic.php?f=49&t=107636#p608722
7.2 https://bugs.launchpad.net/another distro/+source/xserver-xorg-video-intel/+bug/993187
NOTE: Please enter in link 7.2 from within link 7.1 because it do not work if clicked directly on the link.

Thank you for your help.
Best regards
joejac

[Just17]

I would be inclined to try some acpi boot options as that appears to be causing problems .....

acpi=force
acpi=off
acpi=strict
acpi=noirq

.....  also

http://www.pclinuxos.com/forum/index.php/topic,102974.0.html

[joejac]

Thanks Just18,

I do not know, I do not want to disable something that might damage the hardware, can I safely replace my acpi=on by acpi=off in my /boot/grub/menu.lst file?

Now I have:

Code: [Select]

timeout 10
color black/cyan yellow/cyan
gfxmenu (hd0,0)/boot/gfxmenu
default 0

title linux
kernel (hd0,0)/boot/vmlinuz BOOT_IMAGE=linux root=UUID=b283d097-75b4-4877-b281-ae82dcc5d79a quiet nokmsboot vmalloc=256M acpi=on resume=UUID=17a2212a-8f9b-43fd-b787-f8fb753af4a5 splash=silent vga=788
initrd (hd0,0)/boot/initrd.img

title linux-nonfb
kernel (hd0,0)/boot/vmlinuz BOOT_IMAGE=linux-nonfb root=UUID=b283d097-75b4-4877-b281-ae82dcc5d79a quiet nokmsboot vmalloc=256M acpi=on resume=UUID=17a2212a-8f9b-43fd-b787-f8fb753af4a5
initrd (hd0,0)/boot/initrd.img

title failsafe
kernel (hd0,0)/boot/vmlinuz BOOT_IMAGE=failsafe root=UUID=b283d097-75b4-4877-b281-ae82dcc5d79a quiet failsafe vmalloc=256M acpi=on
initrd (hd0,0)/boot/initrd.img

title windows
root (hd1,0)
map (0x81) (0x80)
map (0x80) (0x81)
makeactive
chainloader +1

title 2.6.38.8-pclos3.bfs
kernel (hd0,0)/boot/vmlinuz-2.6.38.8-pclos3.bfs BOOT_IMAGE=2.6.38.8-pclos3.bfs root=UUID=b283d097-75b4-4877-b281-ae82dcc5d79a quiet nokmsboot vmalloc=256M acpi=on resume=UUID=17a2212a-8f9b-43fd-b787-f8fb753af4a5 splash=silent vga=788
initrd (hd0,0)/boot/initrd-2.6.38.8-pclos3.bfs.img

title 3.2.18-pclos1.pae.bfs
kernel (hd0,0)/boot/vmlinuz-3.2.18-pclos1.pae.bfs BOOT_IMAGE=3.2.18-pclos1.pae.bfs root=UUID=b283d097-75b4-4877-b281-ae82dcc5d79a quiet nokmsboot vmalloc=256M acpi=on resume=UUID=17a2212a-8f9b-43fd-b787-f8fb753af4a5 splash=silent vga=788
initrd (hd0,0)/boot/initrd-3.2.18-pclos1.pae.bfs.img
Thanks a lot
joejac

[Just17]

Yes you can, but some functions which it controls may not operate .....  but if it is not operating properly now that would not seem to be a concern ......  worth trying for a while to see if it makes any difference .......  and do check the errors/failures/warnings with dmesg when using 'off' and some of the other options.

[Mike]

Why did I hope Windows driver info would be helpful? Not even close to the versioning system nVidia uses. But, at least it shows the nVidia driver being used.

The user was almost looking in the right place - he should look here:

Windows Control Panel>Nvidia Control Panel

Then when the Nvidia panel is open he should go to the Help menu and choose System Information. This will reveal the driver version as well as a whole pile of other nvidia stuff.

Hope this helps,

Hugh

To add to what macemm said, try this: Windows Control Panel> Hardware>Nvidia Control Panel 

[joejac]

Hello,

1.- Thanks Just18, I set acpi=off and I will monitor for a few days how it works.
2.- Thanks Mikeh, but my Windows 7 Control Panel has a System option and inside it has "Device Manager" and under "Display adapters" is NVIDIA GeFORCE GTX 570 with same information I reported on a previous post:
Driver Version:  8.17.12.9573
3.- It looks like  Nvidia Control Panel is not installed. But with the Windows 7 in a WD Caviar Black HD, in same Desktop, everything works fine until now.
Best regards
joejac

[kjpetrie]

After any kind of hard reset it is important to boot from a livecd and run fsck -f /dev/sdxn (where x and n are the drive letter and partition number of the partition) on your unmounted linux partitions. Failure to do so will result in all sorts of potential damage to system and data producing unpredictable effects.

Secondly, the assumption is being made this is a video issue. It could be, but it could also be something else. As you say it has increased in frequency since you started using new equipment, have you run memtest (search for it in Synaptic if it's not installed and then reboot into it after installation)? Let it run for several hours. If you get errors you have a hardware problem in memory, north bridge, CPU or PSU. If not, those devices are in the clear. It is also possible you could have other problems, but as Windows runs reliably most hardware errors other than memory can be ruled out.

I also note temperature sensors don't seem to be detected properly. This could result in fans not running properly and overheating which, on a well-designed system would trigger emergency shutdown by the BIOS. If you can open the case without voiding the warranty do so and watch. If not listen and feel the box to see whether it runs warmer in pclos.

[joejac]

Hello and thanks kjpetrie,

1.- I set acpi=off and the temperature applet displayed -273, Gkrellm not detecting the 8 CPUs only the 4 Cores, not measuring the CPU and motherboard temperature only the GPU. At boot I was barely able to see the first of various errors, I guess a BIOS error, it happens too fast. Fans were working I noticed air flow in all 3 of them.

2.- I did not want to take the risk, so I went back to acpi=on.

3.- Looking for some tutorials, I was not able to see the -f, what is -f for in: fsck -f /dev/sdxn ?

3.1 I checked the SSD with the Intel Tools via Windows 7 and it says 100% for both Life and Health.

I insist, in the bugg reported in another distro:"another distro 12.04 completely freezes frequently"

Bug Description

Update: 6/12/2012
This bug is about a complete system lock-up. No other TTYs can be started. Mouse doesn't move. Keyboard doesn't react. The only solution is hard reset.

Seems to happen on a variety of configurations, including nVidia, ATI and Intel graphics.

If you are still able to TTY or SSH into other sessions, move the mouse or use the keyboard, file another bug.

Thx. Joris V. (brains).

Update: 5/21/2012
Updating the kernel to 3.3.6 as suggested by Michael in #91, the system seems stable, no freezes yet in 5-6 hrs of using and watching videos for couple of hrs.

Original description:
I recently installed newly released another distro 12.04 LTS 64 bit version on my desktop. And it is frequently freezing, for the first few hours it ran smoothly and when I started watching videos it started freezing randomly.
I have to use hard restart every time.
Initially it was only during videos but now even during normal browsing it is freezing.

I am using on board graphics and do not have any graphics card installed.

Can someone please help me here, I really love the new looks of 12.04 and it bugs me not being able to use

Below is my hardware configuration:
Processor: Intel CORE i3 processor (2nd generation)
Board: Intel® Desktop Board DH67BL
Ram: 4GB
Graphics: On board
HDD: 500 GB

Please let me know if you need more information, or any specific logs I can capture (and how).

Thanks,
Ketan Patil

4.- "the kernel to 3.3.6 as suggested by Michael in #91, the system seems stable,"
4.1 So I wonder if it is possible to get a test kernel 3.3.6 for LXDE?

Best regards
joejac

[kjpetrie]

fsck -f means force a full check, not just a quick journal check.

There's no 3.3 kernel in testing yet, but if you know how to compile one there's nothing to stop you downloading the source and compiling it - provided you have a system stable enough to stay up long enough! Compiling is a matter for the Advanced Users' section though, and not supported here, and you won't be able to do some pclos special things like remastering, but if the problem is that the pclos kernel is too old for your hardware it could be the only option you have.

[joejac]

Hello and thanks kjpetrie,

1.- I did the memtest for 8 hours 45 minutes, 4 tests, 0 errors, please see this link for a screen capture: http://tinypic.com/view.php?pic=1hpcn5&s=6
1.1 I booted normally and the Host lost the task bar with the menu. This happens not very often but happens some times.

2.- I will do fsck -f, hope it works fine with my SSD and do not damage any data.

3.-  I have a very new hardware. As you can see from my questions I do not know how to compile. This compilation process is different for each distro? I found these links but I am not sure which to follow, I do not speak that language    can you provide a hint on which to use, or if there is another more easy to understand?
3.1 http://pclinuxos2007.blogspot.com/2010/02/why-should-you-compile-your-kernel-and.html
3.2 http://www.pclinuxos.com/forum/index.php?topic=63319.0
3.3 http://www.pclinuxos.com/forum/index.php/topic,61257.msg494248.html#msg494248

4.- When you said I won't be able to remastering with the compiled kernel, you mean to create a Live CD of the installation?

Thanks a lot for your time to answer.
Best regards
joejac

[kjpetrie]

1. That's good. We've eliminated the obvious hardware faults (New equipment shouldn't have faults but never assume anything!)

2. fsck shouldn't hurt an SSD and will not harm data, but hard resets can lose data and that is why fsck is needed.

3. Compiling itself is not difficult, and it's not really distro specific unless you're building a package, which you won't be. The first hurdle you have will be finding a machine to compile on, as it takes some hours to do and a machine that's likely to crash before it's finished is no good. If you haven't got another machine that runs pclos, you might be able to get a stable pclos by installing Virtualbox in Win7 and creating a VM there! The next will be dealing with the complexities of configuration.

4. What is distro-specific are the patches. Whether these would apply to a new generic kernel would be a matter for experiment and probably best avoided for a first try. Once you have a working stable kernel you can experiment with compiling alternative versions at your leisure. Because it wouldn't have the pclos patches it won't do pclos-specific things like remastering (making a new livecd for re-installing, as you rightly understood).

Compiling falls into the Advanced Users' section of the forum, so if you want to learn about that I suggest you head over there and start a new thread.

Of course, if pclos is stable in Win 7 VB, depending on your needs you might be able to copy your other VMs into that environment and live with running the other way round for a few months while waiting for the devs to produces a newer pclos kernel.

[joejac]

Hello and thanks a lot kjpetrie

This is the result for:
1.- Show File Systems:

=====================>>> fsarchiver probe simple <<<=====================
[======DISK======] [=============NAME==============] [====SIZE====] [MAJ] [MIN]
[sda             ] [WDC WD1002FAEX-0               ] [   931.51 GB] [  8] [  0]
[sdb             ] [INTEL SSDSC2CW24               ] [   223.57 GB] [  8] [ 16]

[=====DEVICE=====] [==FILESYS==] [======LABEL======] [====SIZE====] [MAJ] [MIN]
[loop0           ] [squashfs   ] [<unknown>        ] [   294.58 MB] [  7] [  0]
[sda1            ] [ntfs       ] [<unknown>        ] [   931.51 GB] [  8] [  1]
[sdb1            ] [ext4       ] [<unknown>        ] [    12.01 GB] [  8] [ 17]
[sdb5            ] [swap       ] [<unknown>        ] [     3.90 GB] [  8] [ 21]
[sdb6            ] [ext4       ] [<unknown>        ] [   207.66 GB] [  8] [ 22]
 
Press a key to continue

2.- fsck -f /dev/sdb1

root@sysresccd /root % fsck -f /dev/sdb1
fsck from util-linux 2.20.1
e2fsck 1.42.4 (12-June-2012)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/sdb1: 130603/788416 files (0.1% non-contiguous), 801203/3148732 blocks
root@sysresccd /root %

3.- fsck -f /dev/sdb5

root@sysresccd /root % fsck -f /dev/sdb5
fsck from util-linux 2.20.1
fsck: fsck.swap: not found
fsck: error 2 while executing fsck.swap for /dev/sdb5
root@sysresccd /root %

4.- fsck -f /dev/sdb6

root@sysresccd /root % fsck -f /dev/sdb6
fsck from util-linux 2.20.1
e2fsck 1.42.4 (12-June-2012)
Superblock last write time is in the future.
   (by less than a day, probably due to the hardware clock being incorrectly set).  Fix<y>? no
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/sdb6: 1177/13615104 files (4.8% non-contiguous), 36374540/54436244 blocks
root@sysresccd /root %

kjpetrie, I appreciate if you can orient me if the above results are fine or no. Do you see errors?. And what else do I have to do?.
I appreciate your help.
Best regards
joejac

[kjpetrie]

All is fine with your partitions. The error on swap is to be expected as swap is new on every new boot and therefore doesn't need repair if improperly shutdown, so there is no utility to do it. We old Linux hands forget to tell people they don't need to use fsck on swap because we forget it's not obvious. Sorry.

We're running out of options, I'm afraid.

[joejac]

Thanks a lot kjpetrie,
There are always options, I will find the way.
Best regards
joejac