How to debug daily freezes?

alphazo · 2010-01-12 10:25:57

Since few weeks I'm getting more and more "daily freezes" of the ArchLinux machine (Dell D430). I don't know if it is related to 2.6.32 or recent Xorg upgrades. It happens when the system does pretty much nothing (Firefox and Thunderbird opened) with CPU usage close to 0%. When it hits, it freezes the mouse/keyboard and even the CPU activity panel in XFCE and most of the time I get the CAPS and NUM lock LEDs blinking.

I looked at the following post but I don't use GDM (Slim + Xfce), however I do have an Intel graphic card.
http://bbs.archlinux.org/viewtopic.php?id=87786
http://bbs.archlinux.org/viewtopic.php?pid=675909

I don't know if that can help but here is the content of some of the key log files. I would appreciate your assistance on analyzing this problem.
Alphazo

lspci

00:00.0 Host bridge: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT Express Memory Controller Hub (rev 03)
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller (rev 03)
00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03)
00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 01)
00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 01)
00:1c.1 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 2 (rev 01)
00:1c.2 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 3 (rev 01)
00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #1 (rev 01)
00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #2 (rev 01)
00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #3 (rev 01)
00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #4 (rev 01)
00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 01)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e1)
00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 01)
00:1f.1 IDE interface: Intel Corporation 82801G (ICH7 Family) IDE Controller (rev 01)
00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev 01)
02:01.0 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev b4)
02:01.1 FireWire (IEEE 1394): Ricoh Co Ltd R5C552 IEEE 1394 Controller (rev 09)
02:01.2 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 18)
09:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5752 Gigabit Ethernet PCI Express (rev 02)
0c:00.0 Network controller: Intel Corporation PRO/Wireless 4965 AG or AGN [Kedron] Network Connection (rev 61)

/var/log/messages

...
Jan 12 09:58:14 ARCH-DN kernel: ACPI: \_SB_.PCI0.PCIE.GDCK - undocking
Jan 12 09:58:17 ARCH-DN kernel: tg3: eth0: Link is down.
Jan 12 09:58:17 ARCH-DN kernel: usb 1-8: USB disconnect, address 7
Jan 12 09:58:17 ARCH-DN kernel: usb 1-8.1: USB disconnect, address 8
Jan 12 09:58:17 ARCH-DN kernel: usb 1-8.1.1: USB disconnect, address 9
Jan 12 09:58:17 ARCH-DN dhcpcd: eth0: carrier lost
Jan 12 09:58:17 ARCH-DN kernel: usb 1-8.1.2: USB disconnect, address 10
Jan 12 09:58:19 ARCH-DN kernel: ACPI: \_SB_.PCI0.PCIE.GDCK - undocking
Jan 12 09:58:21 ARCH-DN kernel: [drm] LVDS-8: set mode  25
Jan 12 09:58:22 ARCH-DN kernel: [drm] TV-16: set mode NTSC 480i 0
Jan 12 09:58:22 ARCH-DN kernel: [drm] TV-16: set mode NTSC 480i 0
Jan 12 09:58:22 ARCH-DN dhcpcd: sending signal 1 to pid 15172
Jan 12 09:58:22 ARCH-DN dhcpcd: received SIGHUP, releasing lease
Jan 12 09:58:22 ARCH-DN dhcpcd: eth0: removing interface
Jan 12 09:58:22 ARCH-DN dhcpcd: waiting for pid 15172 to exit
Jan 12 09:58:22 ARCH-DN kernel: [drm] TV-16: set mode NTSC 480i 0
Jan 12 09:58:23 ARCH-DN kernel: [drm] TV-16: set mode NTSC 480i 0
Jan 12 09:58:23 ARCH-DN kernel: tg3 0000:09:00.0: PME# enabled
Jan 12 09:58:23 ARCH-DN kernel: tg3 0000:09:00.0: wake-up capability enabled by ACPI
Jan 12 09:58:23 ARCH-DN kernel: tg3 0000:09:00.0: wake-up capability disabled by ACPI
Jan 12 09:58:23 ARCH-DN kernel: tg3 0000:09:00.0: PME# disabled
Jan 12 09:58:23 ARCH-DN kernel: [drm] TV-16: set mode NTSC 480i 0
Jan 12 09:58:23 ARCH-DN kernel: [drm] TV-16: set mode NTSC 480i 0
Jan 12 09:58:23 ARCH-DN kernel: Registered led device: iwl-phy1::radio
Jan 12 09:58:23 ARCH-DN kernel: Registered led device: iwl-phy1::assoc
Jan 12 09:58:23 ARCH-DN kernel: Registered led device: iwl-phy1::RX
Jan 12 09:58:23 ARCH-DN kernel: Registered led device: iwl-phy1::TX
Jan 12 09:58:24 ARCH-DN kernel: [drm] TV-16: set mode NTSC 480i 0
Jan 12 09:58:24 ARCH-DN kernel: [drm] TV-16: set mode NTSC 480i 0
Jan 12 09:58:25 ARCH-DN kernel: [drm] TV-16: set mode NTSC 480i 0
Jan 12 09:58:25 ARCH-DN kernel: [drm] TV-16: set mode NTSC 480i 0
Jan 12 09:58:25 ARCH-DN kernel: [drm] TV-16: set mode NTSC 480i 0
Jan 12 09:58:25 ARCH-DN kernel: [drm] TV-16: set mode NTSC 480i 0
Jan 12 09:58:27 ARCH-DN dhcpcd: version 5.1.3 starting
Jan 12 09:58:27 ARCH-DN dhcpcd: wlan0: broadcasting for a lease
Jan 12 09:58:28 ARCH-DN dhcpcd: wlan0: offered 172.31.0.85 from 172.31.0.254
Jan 12 09:58:28 ARCH-DN dhcpcd: wlan0: acknowledged 172.31.0.85 from 172.31.0.254
Jan 12 09:58:28 ARCH-DN dhcpcd: wlan0: checking for 172.31.0.85
Jan 12 09:58:33 ARCH-DN dhcpcd: wlan0: leased 172.31.0.85 for 259200 seconds
Jan 12 09:58:33 ARCH-DN dhcpcd: forking to background
Jan 12 09:58:53 ARCH-DN kernel: [drm] TV-16: set mode NTSC 480i 0
Jan 12 09:58:53 ARCH-DN kernel: [drm] TV-16: set mode NTSC 480i 0
Jan 12 09:58:54 ARCH-DN kernel: [drm] LVDS-8: set mode  25
Jan 12 09:58:54 ARCH-DN kernel: [drm] TV-16: set mode NTSC 480i 0
Jan 12 09:58:55 ARCH-DN kernel: [drm] TV-16: set mode NTSC 480i 0
Jan 12 10:18:55 ARCH-DN -- MARK --
Jan 12 10:21:18 ARCH-DN kernel: psmouse.c: DualPoint TouchPad at isa0060/serio1/input0 lost sync at byte 1
Jan 12 10:21:18 ARCH-DN kernel: psmouse.c: DualPoint TouchPad at isa0060/serio1/input0 lost sync at byte 1
Jan 12 10:21:18 ARCH-DN kernel: psmouse.c: DualPoint TouchPad at isa0060/serio1/input0 lost sync at byte 1
Jan 12 10:21:19 ARCH-DN kernel: psmouse.c: DualPoint TouchPad at isa0060/serio1/input0 - driver resynched.
Jan 12 10:21:21 ARCH-DN kernel: psmouse.c: DualPoint TouchPad at isa0060/serio1/input0 lost sync at byte 1
Jan 12 10:21:21 ARCH-DN kernel: psmouse.c: DualPoint TouchPad at isa0060/serio1/input0 lost sync at byte 1
Jan 12 10:21:21 ARCH-DN kernel: psmouse.c: DualPoint TouchPad at isa0060/serio1/input0 lost sync at byte 1
Jan 12 10:21:22 ARCH-DN kernel: psmouse.c: DualPoint TouchPad at isa0060/serio1/input0 - driver resynched.
..........................
... HARD RESET ...
..........................
Jan 12 10:28:16 ARCH-DN kernel: Linux version 2.6.32-ARCH (tobias@T-POWA-LX) (gcc version 4.4.2 20091208 (prerelease) (GCC) ) #1 SMP PREEMPT Thu Jan 7 22:19:56 UTC 2010
Jan 12 10:28:16 ARCH-DN kernel: KERNEL supported cpus:
Jan 12 10:28:16 ARCH-DN kernel: Intel GenuineIntel
Jan 12 10:28:16 ARCH-DN kernel: AMD AuthenticAMD
Jan 12 10:28:16 ARCH-DN kernel: NSC Geode by NSC
Jan 12 10:28:16 ARCH-DN kernel: Cyrix CyrixInstead
Jan 12 10:28:16 ARCH-DN kernel: Centaur CentaurHauls
Jan 12 10:28:16 ARCH-DN kernel: Transmeta GenuineTMx86
Jan 12 10:28:16 ARCH-DN kernel: Transmeta TransmetaCPU
Jan 12 10:28:16 ARCH-DN kernel: UMC UMC UMC UMC

/var/log/errors.log

Jan 12 09:37:19 ARCH-DN dhcpcd: timed out
Jan 12 09:37:24 ARCH-DN dhcpcd: dhcpcd not running
Jan 12 09:37:24 ARCH-DN dhcpcd: dhcpcd not running
Jan 12 09:58:23 ARCH-DN dhcpcd: dhcpcd not running
Jan 12 10:28:16 ARCH-DN kernel: fb: conflicting fb hw usage inteldrmfb vs VESA VGA - removing generic driver
Jan 12 10:28:35 ARCH-DN dhcpcd: dhcpcd not running
Jan 12 10:28:35 ARCH-DN dhcpcd: dhcpcd not running

/var/log/kernel.log

Jan 12 09:58:26 ARCH-DN kernel: wlan0: associated
Jan 12 09:58:53 ARCH-DN kernel: [drm] TV-16: set mode NTSC 480i 0
Jan 12 09:58:53 ARCH-DN kernel: [drm] TV-16: set mode NTSC 480i 0
Jan 12 09:58:54 ARCH-DN kernel: [drm] LVDS-8: set mode  25
Jan 12 09:58:54 ARCH-DN kernel: [drm] TV-16: set mode NTSC 480i 0
Jan 12 09:58:55 ARCH-DN kernel: [drm] TV-16: set mode NTSC 480i 0
Jan 12 10:21:18 ARCH-DN kernel: psmouse.c: DualPoint TouchPad at isa0060/serio1/input0 lost sync at byte 1
Jan 12 10:21:18 ARCH-DN kernel: psmouse.c: DualPoint TouchPad at isa0060/serio1/input0 lost sync at byte 1
Jan 12 10:21:18 ARCH-DN kernel: psmouse.c: DualPoint TouchPad at isa0060/serio1/input0 lost sync at byte 1
Jan 12 10:21:19 ARCH-DN kernel: psmouse.c: DualPoint TouchPad at isa0060/serio1/input0 - driver resynched.
Jan 12 10:21:21 ARCH-DN kernel: psmouse.c: DualPoint TouchPad at isa0060/serio1/input0 lost sync at byte 1
Jan 12 10:21:21 ARCH-DN kernel: psmouse.c: DualPoint TouchPad at isa0060/serio1/input0 lost sync at byte 1
Jan 12 10:21:21 ARCH-DN kernel: psmouse.c: DualPoint TouchPad at isa0060/serio1/input0 lost sync at byte 1
Jan 12 10:21:22 ARCH-DN kernel: psmouse.c: DualPoint TouchPad at isa0060/serio1/input0 - driver resynched.
Jan 12 10:28:16 ARCH-DN kernel: Linux version 2.6.32-ARCH (tobias@T-POWA-LX) (gcc version 4.4.2 20091208 (prerelease) (GCC) ) #1 SMP PREEMPT Thu Jan 7 22:19:
56 UTC 2010
Jan 12 10:28:16 ARCH-DN kernel: KERNEL supported cpus:
Jan 12 10:28:16 ARCH-DN kernel: Intel GenuineIntel
Jan 12 10:28:16 ARCH-DN kernel: AMD AuthenticAMD
Jan 12 10:28:16 ARCH-DN kernel: NSC Geode by NSC

/var/log/Xorg.0.log

This is a pre-release version of the X server from The X.Org Foundation.
It is not supported in any way.
Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/.
Select the "xorg" product for bugs you find in this release.
Before reporting bugs in pre-release versions please check the
latest version in the X.Org Foundation git repository.
See http://wiki.x.org/wiki/GitPage for git access instructions.

X.Org X Server 1.7.3.902 (1.7.4 RC 2)
Release Date: 2009-12-26
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.32-ARCH i686 
Current Operating System: Linux ARCH-DN 2.6.32-ARCH #1 SMP PREEMPT Thu Jan 7 22:19:56 UTC 2010 i686
Kernel command line: root=/dev/disk/by-uuid/046d7122-21a4-47df-8f19-3fb5ebec9192 ro vga=773
Build Date: 26 December 2009  11:37:45AM
 
Current version of pixman: 0.16.4
    Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Tue Jan 12 10:28:22 2010
(II) Loader magic: 0x81e4c60
(II) Module ABI versions:
    X.Org ANSI C Emulation: 0.4
    X.Org Video Driver: 6.0
    X.Org XInput driver : 7.0
    X.Org Server Extension : 2.0
(++) using VT number 7

(--) PCI:*(0:0:2:0) 8086:27a2:1028:0201 Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller rev 3, Mem @ 0xeff00000/524288,
 0xd0000000/268435456, 0xefec0000/262144, I/O @ 0x0000eff8/8
(--) PCI: (0:0:2:1) 8086:27a6:1028:0201 Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller rev 3, Mem @ 0xeff80000/524
288
(==) Using default built-in configuration (30 lines)
(==) --- Start of built-in configuration ---
    Section "Device"
        Identifier    "Builtin Default intel Device 0"
        Driver    "intel"
    EndSection
    Section "Screen"
        Identifier    "Builtin Default intel Screen 0"
        Device    "Builtin Default intel Device 0"
    EndSection
    Section "Device"
        Identifier    "Builtin Default vesa Device 0"
        Driver    "vesa"
    EndSection
    Section "Screen"
        Identifier    "Builtin Default vesa Screen 0"
        Device    "Builtin Default vesa Device 0"
    EndSection
    Section "Device"
        Identifier    "Builtin Default fbdev Device 0"
        Driver    "fbdev"
    EndSection
    Section "Screen"
        Identifier    "Builtin Default fbdev Screen 0"
        Device    "Builtin Default fbdev Device 0"
    EndSection
    Section "ServerLayout"
        Identifier    "Builtin Default Layout"
        Screen    "Builtin Default intel Screen 0"
        Screen    "Builtin Default vesa Screen 0"
        Screen    "Builtin Default fbdev Screen 0"
    EndSection
(==) --- End of built-in configuration ---
(==) ServerLayout "Builtin Default Layout"
(**) |-->Screen "Builtin Default intel Screen 0" (0)
(**) |   |-->Monitor "<default monitor>"
(**) |   |-->Device "Builtin Default intel Device 0"
(==) No monitor specified for screen "Builtin Default intel Screen 0".
    Using a default monitor configuration.
(**) |-->Screen "Builtin Default vesa Screen 0" (1)
(**) |   |-->Monitor "<default monitor>"
(**) |   |-->Device "Builtin Default vesa Device 0"
(==) No monitor specified for screen "Builtin Default vesa Screen 0".
    Using a default monitor configuration.
(**) |-->Screen "Builtin Default fbdev Screen 0" (2)
(**) |   |-->Monitor "<default monitor>"
(**) |   |-->Device "Builtin Default fbdev Device 0"
(==) No monitor specified for screen "Builtin Default fbdev Screen 0".
    Using a default monitor configuration.
(==) Automatically adding devices
(==) Automatically enabling devices
(==) FontPath set to:
    /usr/share/fonts/misc,
    /usr/share/fonts/100dpi:unscaled,
    /usr/share/fonts/75dpi:unscaled,
    /usr/share/fonts/TTF,
    /usr/share/fonts/Type1
(==) ModulePath set to "/usr/lib/xorg/modules"
(II) Cannot locate a core pointer device.
(II) Cannot locate a core keyboard device.
(II) The server relies on HAL to provide the list of input devices.
    If no devices become available, reconfigure HAL or disable AutoAddDevices.
(WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
(II) LoadModule: "extmod"
(II) Loading /usr/lib/xorg/modules/extensions/libextmod.so
(II) Module extmod: vendor="X.Org Foundation"
    compiled for 1.7.3.902, module version = 1.0.0
    Module class: X.Org Server Extension
    ABI class: X.Org Server Extension, version 2.0
(II) Loading extension MIT-SCREEN-SAVER
(II) Loading extension XFree86-VidModeExtension
(II) Loading extension XFree86-DGA
(II) Loading extension DPMS
(II) Loading extension XVideo
(II) Loading extension XVideo-MotionCompensation
(II) Loading extension X-Resource
(II) LoadModule: "dbe"
(II) Loading /usr/lib/xorg/modules/extensions/libdbe.so
(II) Module dbe: vendor="X.Org Foundation"
    compiled for 1.7.3.902, module version = 1.0.0
    Module class: X.Org Server Extension
    ABI class: X.Org Server Extension, version 2.0
(II) Loading extension DOUBLE-BUFFER
(II) LoadModule: "glx"
(II) Loading /usr/lib/xorg/modules/extensions/libglx.so
(II) Module glx: vendor="X.Org Foundation"
    compiled for 1.7.3.902, module version = 1.0.0
    ABI class: X.Org Server Extension, version 2.0
(==) AIGLX enabled
(II) Loading extension GLX
(II) LoadModule: "dri"
(II) Loading /usr/lib/xorg/modules/extensions/libdri.so
(II) Module dri: vendor="X.Org Foundation"
    compiled for 1.7.3.902, module version = 1.0.0
    ABI class: X.Org Server Extension, version 2.0
(II) Loading extension XFree86-DRI
(II) LoadModule: "dri2"
(II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
(II) Module dri2: vendor="X.Org Foundation"
    compiled for 1.7.3.902, module version = 1.1.0
    ABI class: X.Org Server Extension, version 2.0
(II) Loading extension DRI2
(II) LoadModule: "intel"
(II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
(II) Module intel: vendor="X.Org Foundation"
    compiled for 1.7.1, module version = 2.9.1
    Module class: X.Org Video Driver
    ABI class: X.Org Video Driver, version 6.0
(II) LoadModule: "vesa"
(II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
(II) Module vesa: vendor="X.Org Foundation"
    compiled for 1.7.0.901, module version = 2.2.1
    Module class: X.Org Video Driver
    ABI class: X.Org Video Driver, version 6.0
(II) LoadModule: "fbdev"
(WW) Warning, couldn't open module fbdev
(II) UnloadModule: "fbdev"
(EE) Failed to load module "fbdev" (module does not exist, 0)
(II) intel: Driver for Intel Integrated Graphics Chipsets: i810,
    i810-dc100, i810e, i815, i830M, 845G, 852GM/855GM, 865G, 915G,
    E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM, Pineview G,
    965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33, GM45,
    4 Series, G45/G43, Q45/Q43, G41, B43, Clarkdale, Arrandale
(II) VESA: driver for VESA chipsets: vesa
(II) Primary Device is: PCI 00@00:02:0
(WW) Falling back to old probe method for vesa
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 8, (OK)
drmOpenByBusid: Searching for BusID pci:0000:00:02.0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 8, (OK)
drmOpenByBusid: drmOpenMinor returns 8
drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0
(II) intel(0): Creating default Display subsection in Screen section
    "Builtin Default intel Screen 0" for depth/fbbpp 24/32
(==) intel(0): Depth 24, (--) framebuffer bpp 32
(==) intel(0): RGB weight 888
(==) intel(0): Default visual is TrueColor
(II) intel(0): Integrated Graphics Chipset: Intel(R) 945GM
(--) intel(0): Chipset: "945GM"
(II) intel(0): Output VGA1 has no monitor section
(II) intel(0): Output LVDS1 has no monitor section
(II) intel(0): Output DVI1 has no monitor section
(II) intel(0): Output TV1 has no monitor section
(II) intel(0): Output VGA1 disconnected
(II) intel(0): Output LVDS1 connected
(II) intel(0): Output DVI1 disconnected
(II) intel(0): Output TV1 disconnected
(II) intel(0): Using exact sizes for initial modes
(II) intel(0): Output LVDS1 using initial mode 1280x800
(II) intel(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
(==) intel(0): video overlay key set to 0x101fe
(==) intel(0): DPI set to (96, 96)
(II) Loading sub module "fb"
(II) LoadModule: "fb"
(II) Loading /usr/lib/xorg/modules/libfb.so
(II) Module fb: vendor="X.Org Foundation"
    compiled for 1.7.3.902, module version = 1.0.0
    ABI class: X.Org ANSI C Emulation, version 0.4
(II) UnloadModule: "vesa"
(II) Unloading /usr/lib/xorg/modules/drivers/vesa_drv.so
(==) Depth 24 pixmap format is 32 bpp
(II) intel(0): [DRI2] Setup complete
(**) intel(0): Kernel mode setting active, disabling FBC.
(**) intel(0): Framebuffer compression disabled
(**) intel(0): Tiling enabled
(**) intel(0): SwapBuffers wait enabled
(==) intel(0): VideoRam: 262144 KB
(II) intel(0): Attempting memory allocation with tiled buffers.
(II) intel(0): Tiled allocation successful.
(II) UXA(0): Driver registered support for the following operations:
(II)         solid
(II)         copy
(II)         composite (RENDER acceleration)
(==) intel(0): Backing store disabled
(==) intel(0): Silken mouse enabled
(II) intel(0): Initializing HW Cursor
(II) intel(0): No memory allocations
(II) intel(0): RandR 1.2 enabled, ignore the following RandR disabled message.
(==) intel(0): DPMS enabled
(==) intel(0): Intel XvMC decoder disabled
(II) intel(0): Set up textured video
(II) intel(0): direct rendering: DRI2 Enabled
(--) RandR disabled
(II) Initializing built-in extension Generic Event Extension
(II) Initializing built-in extension SHAPE
(II) Initializing built-in extension MIT-SHM
(II) Initializing built-in extension XInputExtension
(II) Initializing built-in extension XTEST
(II) Initializing built-in extension BIG-REQUESTS
(II) Initializing built-in extension SYNC
(II) Initializing built-in extension XKEYBOARD
(II) Initializing built-in extension XC-MISC
(II) Initializing built-in extension SECURITY
(II) Initializing built-in extension XINERAMA
(II) Initializing built-in extension XFIXES
(II) Initializing built-in extension RENDER
(II) Initializing built-in extension RANDR
(II) Initializing built-in extension COMPOSITE
(II) Initializing built-in extension DAMAGE
(II) AIGLX: enabled GLX_MESA_copy_sub_buffer
(II) AIGLX: enabled GLX_SGI_make_current_read
(II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control
(II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
(II) AIGLX: Loaded and initialized /usr/lib/xorg/modules/dri/i915_dri.so
(II) GLX: Initialized DRI2 GL provider for screen 0
(II) intel(0): Setting screen physical size to 338 x 211
(II) config/hal: Adding input device AT Translated Set 2 keyboard
(II) LoadModule: "evdev"
(II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
(II) Module evdev: vendor="X.Org Foundation"
    compiled for 1.7.3, module version = 2.3.2
    Module class: X.Org XInput Driver
    ABI class: X.Org XInput driver, version 7.0
(**) AT Translated Set 2 keyboard: always reports core events
(**) AT Translated Set 2 keyboard: Device: "/dev/input/event1"
(II) AT Translated Set 2 keyboard: Found keys
(II) AT Translated Set 2 keyboard: Configuring as keyboard
(II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "evdev"
(**) Option "xkb_layout" "fr"
(II) config/hal: Adding input device Macintosh mouse button emulation
(**) Macintosh mouse button emulation: always reports core events
(**) Macintosh mouse button emulation: Device: "/dev/input/event0"
(II) Macintosh mouse button emulation: Found 3 mouse buttons
(II) Macintosh mouse button emulation: Found relative axes
(II) Macintosh mouse button emulation: Found x and y relative axes
(II) Macintosh mouse button emulation: Configuring as mouse
(**) Macintosh mouse button emulation: YAxisMapping: buttons 4 and 5
(**) Macintosh mouse button emulation: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
(II) XINPUT: Adding extended input device "Macintosh mouse button emulation" (type: MOUSE)
(**) Macintosh mouse button emulation: (accel) keeping acceleration scheme 1
(**) Macintosh mouse button emulation: (accel) acceleration profile 0
(II) Macintosh mouse button emulation: initialized for relative axes.
(II) config/hal: Adding input device AlpsPS/2 ALPS DualPoint TouchPad
(II) LoadModule: "synaptics"
(II) Loading /usr/lib/xorg/modules/input/synaptics_drv.so
(II) Module synaptics: vendor="X.Org Foundation"
    compiled for 1.7.3, module version = 1.2.1
    Module class: X.Org XInput Driver
    ABI class: X.Org XInput driver, version 7.0
(II) Synaptics touchpad driver version 1.2.1
(**) Option "Device" "/dev/input/event8"
(II) AlpsPS/2 ALPS DualPoint TouchPad: x-axis range 0 - 1023
(II) AlpsPS/2 ALPS DualPoint TouchPad: y-axis range 0 - 767
(II) AlpsPS/2 ALPS DualPoint TouchPad: pressure range 0 - 127
(II) AlpsPS/2 ALPS DualPoint TouchPad: finger width range 0 - 0
(II) AlpsPS/2 ALPS DualPoint TouchPad: buttons: left right middle
(**) Option "TapButton1" "1"
(**) Option "TapButton2" "2"
(**) Option "TapButton3" "3"
(--) AlpsPS/2 ALPS DualPoint TouchPad: touchpad found
(**) AlpsPS/2 ALPS DualPoint TouchPad: always reports core events
(II) XINPUT: Adding extended input device "AlpsPS/2 ALPS DualPoint TouchPad" (type: TOUCHPAD)
(**) AlpsPS/2 ALPS DualPoint TouchPad: (accel) keeping acceleration scheme 1
(**) AlpsPS/2 ALPS DualPoint TouchPad: (accel) acceleration profile 0
(--) AlpsPS/2 ALPS DualPoint TouchPad: touchpad found
(II) config/hal: Adding input device DualPoint Stick
(**) DualPoint Stick: always reports core events
(**) DualPoint Stick: Device: "/dev/input/event7"
(II) DualPoint Stick: Found 3 mouse buttons
(II) DualPoint Stick: Found relative axes
(II) DualPoint Stick: Found x and y relative axes
(II) DualPoint Stick: Configuring as mouse
(**) DualPoint Stick: YAxisMapping: buttons 4 and 5
(**) DualPoint Stick: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
(II) XINPUT: Adding extended input device "DualPoint Stick" (type: MOUSE)
(**) DualPoint Stick: (accel) keeping acceleration scheme 1
(**) DualPoint Stick: (accel) acceleration profile 0
(II) DualPoint Stick: initialized for relative axes.
(II) config/hal: Adding input device Sleep Button
(**) Sleep Button: always reports core events
(**) Sleep Button: Device: "/dev/input/event6"
(II) Sleep Button: Found keys
(II) Sleep Button: Configuring as keyboard
(II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "evdev"
(**) Option "xkb_layout" "fr"
(II) config/hal: Adding input device Power Button
(**) Power Button: always reports core events
(**) Power Button: Device: "/dev/input/event5"
(II) Power Button: Found keys
(II) Power Button: Configuring as keyboard
(II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "evdev"
(**) Option "xkb_layout" "fr"
(II) config/hal: Adding input device Video Bus
(**) Video Bus: always reports core events
(**) Video Bus: Device: "/dev/input/event3"
(II) Video Bus: Found keys
(II) Video Bus: Configuring as keyboard
(II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "evdev"
(**) Option "xkb_layout" "fr"
(II) config/hal: Adding input device Video Bus
(**) Video Bus: always reports core events
(**) Video Bus: Device: "/dev/input/event2"
(II) Video Bus: Found keys
(II) Video Bus: Configuring as keyboard
(II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "evdev"
(**) Option "xkb_layout" "fr"
(II) intel(0): EDID vendor "LCD", prod id 14086
(II) intel(0): Printing DDC gathered Modelines:
(II) intel(0): Modeline "1280x800"x0.0   68.50  1280 1296 1344 1410  800 802 804 810 -hsync -vsync (48.6 kHz)
(II) intel(0): EDID vendor "LCD", prod id 14086
(II) intel(0): Printing DDC gathered Modelines:
(II) intel(0): Modeline "1280x800"x0.0   68.50  1280 1296 1344 1410  800 802 804 810 -hsync -vsync (48.6 kHz)

alphazo · 2010-01-15 09:28:37

RIP... After those daily crashes and power cycles I've lost my entire filesystem on Wednesday (bad superblocks and unable to use any of the alternative ones)! The fsck did recover some of the files with or without names but most of my stuff is gone.

Good news is I had a backup from last Friday (in fact I also have the past 6 weeks with rsnapshot). So it is not that bad but still as I use it for work I had to grab a spare laptop with Win XP on it... and that I'm not very proud of

I'm not blaming Arch, 2.6.32 nor EXT4. Although this is the first time I use this not-so-old EXT4 filesystem so that makes me think that it is not that robust. That combined with 2.6.32 makes me believe there is something wrong. Could be related to Intel video driver as well. I went through lengthy hard drive surface tests and 24 hours burn-in tests (100% CPU usage). I'm now in a middle in a long Memtest session to also verify the memory. If that passes I don't really know what to do. I think I'm gonna re-install Arch on EXT3 with
- full journal enabled (data=journal vs default data=ordered)
- barriers enabled
- write-cache disable (that sounds excessive but as the hard drive is dead slow anyway it should be ok )

...but still I don't believe I'll get any better stability (but at least I won't have data corruption).

Alphazo

Last edited by alphazo (2010-01-15 10:01:13)

barzam · 2010-01-15 10:05:08

I had the same problem, I solved it (haven't seen a single lockup in more than a week now) by installing Slim and setting up inittab to start it. See the wiki on how to achieve this, and please report if it works.

My lockups always happened when I was typing, that is also when I wasn't doing anything demanding in any way (writing mails, doing stuff i OO etc). Eeepc 1005HA with mostly Intel stuff inside.

alphazo · 2010-01-15 10:07:12

Unfortunately, this the configuration I've been using since the first install - slim launched via inittab.

barzam · 2010-01-15 11:11:00

Can you see if X indeed is on TTY7 and not somewhere else?

Do you have the same lockups with the .31 kernel as well? I believe mine started occuring when I installed the first .32 version.

alphazo · 2010-01-15 11:17:06

I need to re-install arch before I see TTY7 However during the different crashes I could not switch to console by using CTLR+ALT keys. I would get blinking CAPS and NUM LOCKS sometimes.

I would say that I experienced some lockups with 2.6.31 and much more with 2.6.32. But keep in mind that Xorg also upgraded in the meantime so it's hard to find the guilty component.

Alphazo

eldragon · 2010-01-15 11:55:34

describe your hard locks.... do they look anything like http://bugzilla.kernel.org/show_bug.cgi?id=15004

one thoughts on hard powering down your system

THINGS TO TRY OUT FIRST:

- install openssh and setup the daemon. when it hardlocks, a good test is to try and log in through another machine.. there is a big chance you can, and issue a reboot command from there. you can check logs there too and see why it failed

- enable the magic sysrq commands. if the system freezes, but the kernel is still awake. you can issue some commands that will reboot the system but not before flushing caches and making it 'safeish'.

Ashren · 2010-01-15 12:38:21

Are you using KMS?

alphazo · 2010-01-15 12:45:14

Thank you for looking at my problem.

eldragon wrote:

describe your hard locks.... do they look anything like http://bugzilla.kernel.org/show_bug.cgi?id=15004

I described it in my original post (see above) with logs. I'm not sure it is related to the posted bug. In my case keyboard and mouse pointer are frozen too , CAPS and NUMLOCK blinking.

- install openssh and setup the daemon. when it hardlocks, a good test is to try and log in through another machine.. there is a big chance you can, and issue a reboot command from there. you can check logs there too and see why it failed

That wouldn't have worked in the case that killed my laptop as the access point I'm connected too doesn't accept individual clients to see each others. But still a good way to debug it in the future. If that happens what should I be looking at, only logs in /var/logs or more?

- enable the magic sysrq commands. if the system freezes, but the kernel is still awake. you can issue some commands that will reboot the system but not before flushing caches and making it 'safeish'.

Discovered that one today, pretty sleek. However would it work with an unresponsive keyboard with blinking LEDs?

alphazo · 2010-01-15 12:47:03

Ashren wrote:

Are you using KMS?

I use the stock 2.6.32 kernel and didn't explicitly enable it so I guess the answer is no. As a side note I don't use compiz at all on this tiny machine.

Looking at archlinux news page regarding 2.6.32
http://www.archlinux.org/news/477/

[EDIT] I noticed on archlinux news page: http://www.archlinux.org/news/477/

KMS changes:
- changed intel kms enabled by default

Do I need KMS and is there a way to disable it?

[EDIT2] There is one sentence in the wiki regarding Intel/KMS that worries me:

KMS is supported by Intel chipsets that use the i915 DRM driver and is now enabled by default as of kernel v2.6.32.
Important: When using KMS, you must remove any references to "vga=" or "video=" from the kernel commandline in /boot/grub/menu.lst

I had vga=773 in my kernel command line option and installed xf86-video-intel package (no module loaded on startup). Is that a probelm and could have generated conflicts?

Does that mean that now KMS is enable by default one must change its options to :

kernel /boot/vmlinuz26 root=/dev/... i915.modeset=1

and load "intel_agp i915" modules.

So in the end, would you recommend KMS on intel cards for stability?

Thanks
Alphazo

Last edited by alphazo (2010-01-15 15:24:31)

Minishark · 2010-01-15 15:27:33

Have you tried running MemTest86? I was having random freezes a few weeks ago, turns out I had a bad stick of memory. No problems since removing it.

alphazo · 2010-01-15 15:30:16

Minishark wrote:

Have you tried running MemTest86? I was having random freezes a few weeks ago, turns out I had a bad stick of memory. No problems since removing it.

I have Memtest86+ running at the moment (It has been around 7 hours without errors) and plan to keep it running over the week-end before deciding what to do.

Ashren · 2010-01-15 15:40:12

You can disable KMS by appending i915.modeset=0 to the kernel line in /boot/grub/menu.lst:

kernel /boot/vmlinuz26 root=/dev/... i915.modeset=0

This might cause X not to start, but try it out.

Last edited by Ashren (2010-01-15 15:40:46)

ninian · 2010-01-15 20:13:32

@alphazo:

I have a not-so-new laptop with a Via C3 processor which exhibits behaviour very similar to that which you described. The crashes happened with at least the 2.6.32 and 2.6.31 kernels, and maybe earlier. Seems absolutely random, and I tried changed X drivers - vesa, openchrome, etc - to no obvious avail. RAM also checked out okay.

Ran Ubuntu 9.10 from a live DVD and it works fine until you try glxgears => crash and blinking lights.

@eldragon:

install openssh and setup the daemon. when it hardlocks, a good test is to try and log in through another machine.. there is a big chance you can, and issue a reboot command from there. you can check logs there too and see why it failed

Seems like a sensible idea and will try, but as far as I recall nothing gets reported in the logs and the magic SysRq keys don't work either.

Very frustrating.

eldragon · 2010-01-15 20:42:17

you need to enable sysrq in the kernel. this is setup in /etc/sysctl.conf

the safe reboot code is
alt-prnscr+ R E I S U B (one at a time).

ninian · 2010-01-15 20:43:56

eldragon wrote:

you need to enable sysrq in the kernel. this is setup in /etc/sysctl.conf
the safe reboot code is
alt-prnscr+ R E I S U B (one at a time).

Yup - knew about that and had done it.
Have never encountered such a random but severe problem on any other of the dozen or so machines I have installed Arch on.

eldragon · 2010-01-15 20:53:39

have you considered hardware problems?

alphazo · 2010-01-15 20:59:25

ninian wrote:

eldragon wrote:
you need to enable sysrq in the kernel. this is setup in /etc/sysctl.conf
the safe reboot code is
alt-prnscr+ R E I S U B (one at a time).
Yup - knew about that and had done it.
Have never encountered such a random but severe problem on any other of the dozen or so machines I have installed Arch on.

Can you confirm the default journaling scheme on Arch (data=ordered)? I have noticed some differences with the wiki here:
http://bbs.archlinux.org/viewtopic.php? … 48#p689048

ninian · 2010-01-15 21:02:28

Hardware problem: can't discount that, but no other signs evident so far.
I'm using ext3, but never knew about the journaling 'data=ordered/writeback' stuff ... interesting.

eldragon · 2010-01-15 21:04:11

ninian wrote:

Hardware problem: can't discount that, but no other signs evident so far.
I'm using ext3, but never knew about the journaling 'data=ordered/writeback' stuff ... interesting.

check for flashing caps + scroll lock leds on the keyboard..

ninian · 2010-01-15 21:07:30

eldragon wrote:

check for flashing caps + scroll lock leds on the keyboard..

Don't have immediate access to this laptop at the moment, but a couple of lights do flash - and it could well be these ones you mention.

eldragon · 2010-01-15 21:23:59

well, they are called kernel panic. and it means the kernel ... just panicked..

check temps, ram, cpu fan, and hdd for failure.... you are likely facing a hardware failure.

ninian · 2010-01-15 21:25:12

eldragon wrote:

well, they are called kernel panic. and it means the kernel ... just panicked..
check temps, ram, cpu fan, and hdd for failure.... you are likely facing a hardware failure.

Will try and check the blessed thing out again over the weekend - thanks for the pointers.

rusty99 · 2010-01-16 09:45:41

I had a very similar problem of completely random reboots when browsing the net. Dropping back to 2.6.31 made things more stable but certainly didn't get rid of the problem.
Quite often after a crash I'd check bios and temps would be ~32C so no problem there. I stripped the machine and rebuilt it after cleaning everything and it still kept happening. I decided to install FreeBSD to try a different OS approach and lo and behold as soon as I visted bbc.co.uk the browser crashed and the machine also rebooted.

What's hard to determine here is where and what causes the crash, FreeBSD had a USB rewrite for v8.0 so was there a bug in the code somewhere? I had noticed that my keyboard would sometimes not get detected when booting, switching to an old keyboard got rid of that issue and removed any crashes. I got a new keyboard 2 days ago and no crashes yet.

However the chances that both OS' have an issue with my keyboard (when Arch worked fine with it for nearly 9mths) and there are no reports of incompatability anywhere just go to make the situation even more confusing.

Good luck with finding the cause, I knpw exactly how fustrating this is

Last edited by rusty99 (2010-01-16 09:48:32)

naguz · 2010-01-16 11:43:07

I have a htpc and have a similar problem. It will stop responding
The ssh-session i have open does not die immediatly, but it stops responding (cant type or anything in it), and if I leave the htpc on, it dies eventually. Trying to open a new ssh-session results in:
"ssh: connect to host 192.168.0.102 port 22: No route to host"

The Wiimote I have connected using cwiid says it is still connected, but pressing something doesnt wake it up. The TV will say "no signal" on the HDMI input.

It runs xbmc-standalone launched from .xinitrc. X is launched from inittab
Inittab:

x:5:respawn:/bin/su tv -l -c "/bin/bash --login -c startx >/dev/null 2>&1"

.xinitrc:

exec /usr/bin/ck-launch-session /usr/bin/dbus-launch --exit-with-session /usr/bin/xbmc-standalone

I have a nvidia on board graphics card, and nvidia drivers from repo.

The strange thing is, there is no errors in xorg.log, an nothing in any of the other log files I have looked at in /var/log. Not just no errors, but no nothing. They're empty. I just can't understand what's going on. oO

I have had errors in xorg.log one time, suggesting it is the nvodoa driver as far as I can understand, but usually there are no erors at all.

(EE) Jan 13 21:41:27 NVIDIA(0): Failed to determine display capabilities
(EE) NVIDIA(0):  *** Aborting ***
(II) Jan 13 21:41:27 NVIDIA(0): Setting mode "nvidia-auto-select"
(EE) Jan 13 21:41:27 NVIDIA(0): Failed to initiate mode change

Backtrace:
0: /usr/bin/X (xorg_backtrace+0x28) [0x4b04e8]
1: /usr/bin/X (0x400000+0x66209) [0x466209]
2: /lib/libpthread.so.0 (0x7f52462c8000+0xee80) [0x7f52462d6e80]
3: /usr/lib/xorg/modules/drivers/nvidia_drv.so (0x7f5242405000+0x4f4c6) [0x7f52424544c6]
4: /usr/lib/xorg/modules/drivers/nvidia_drv.so (0x7f5242405000+0x55932) [0x7f524245a932]
5: /usr/lib/xorg/modules/drivers/nvidia_drv.so (0x7f5242405000+0x322538) [0x7f5242727538]
6: /usr/lib/xorg/modules/drivers/nvidia_drv.so (0x7f5242405000+0x322cee) [0x7f5242727cee]
7: /usr/lib/xorg/modules/drivers/nvidia_drv.so (0x7f5242405000+0x313f5c) [0x7f5242718f5c]
8: /usr/bin/X (0x400000+0x124fe2) [0x524fe2]
9: /usr/bin/X (0x400000+0x129d89) [0x529d89]
10: /usr/bin/X (xf86Wakeup+0x3f2) [0x472612]
11: /usr/bin/X (WakeupHandler+0x4b) [0x435cdb]
12: /usr/bin/X (WaitForSomething+0x1d7) [0x45a797]
13: /usr/bin/X (0x400000+0x41472) [0x441472]
14: /usr/bin/X (0x400000+0x219ec) [0x4219ec]
15: /lib/libc.so.6 (__libc_start_main+0xfd) [0x7f5245573b6d]
16: /usr/bin/X (0x400000+0x21599) [0x421599]
Segmentation fault at address 0x9c

But thats just one time.

I don't know if this is at all related, but it won't shut down properly either. shutdown -P now just makes it go into single user mode (press ctrl+d screen), but it dowsn't turn off.

Arch Linux

#1 2010-01-12 10:25:57

How to debug daily freezes?

#2 2010-01-15 09:28:37

Re: How to debug daily freezes?

#3 2010-01-15 10:05:08

Re: How to debug daily freezes?

#4 2010-01-15 10:07:12

Re: How to debug daily freezes?

#5 2010-01-15 11:11:00

Re: How to debug daily freezes?

#6 2010-01-15 11:17:06

Re: How to debug daily freezes?

#7 2010-01-15 11:55:34

Re: How to debug daily freezes?

#8 2010-01-15 12:38:21

Re: How to debug daily freezes?

#9 2010-01-15 12:45:14

Re: How to debug daily freezes?

#10 2010-01-15 12:47:03

Re: How to debug daily freezes?

#11 2010-01-15 15:27:33

Re: How to debug daily freezes?

#12 2010-01-15 15:30:16

Re: How to debug daily freezes?

#13 2010-01-15 15:40:12

Re: How to debug daily freezes?

#14 2010-01-15 20:13:32

Re: How to debug daily freezes?

#15 2010-01-15 20:42:17

Re: How to debug daily freezes?

#16 2010-01-15 20:43:56

Re: How to debug daily freezes?

#17 2010-01-15 20:53:39

Re: How to debug daily freezes?

#18 2010-01-15 20:59:25

Re: How to debug daily freezes?

#19 2010-01-15 21:02:28

Re: How to debug daily freezes?

#20 2010-01-15 21:04:11

Re: How to debug daily freezes?

#21 2010-01-15 21:07:30

Re: How to debug daily freezes?

#22 2010-01-15 21:23:59

Re: How to debug daily freezes?

#23 2010-01-15 21:25:12

Re: How to debug daily freezes?

#24 2010-01-16 09:45:41

Re: How to debug daily freezes?

#25 2010-01-16 11:43:07

Re: How to debug daily freezes?

Board footer