[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#424239: marked as done (linux-image-2.6.18-4-486: linux freeze sometimes on my laptop)

Your message dated Fri, 14 Dec 2007 18:46:58 +0100
with message-id <20071214174658.GA13736@universal.soleil>
and subject line Not Found in linux-image-2.6.18-5-k7
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message --- 
Package: linux-image-2.6.18-4-486
Version: 2.6.18.dfsg.1-12
Severity: critical
Justification: breaks the whole system


I have regularly freezes on my laptop computer. I do not see nothing
when I am in an X session (my screen stay in the exact same state but
nothing works nor keyboard, nor network...) and I have no way but to 
push the power-off button.

I think this bug is the same which occured some time in console mode
with this informations :

    <0>Kernel panic - not syncing: Attempted to kill the idle task!

and 

    CPU: 0
    EIP: 0060:[<de826310>] Not Tainted VLI
    EFLAGS: 00010286 (2.6.18-4-486 #1)
    acpi_processor_idle+0x292/0x2fa

    Stack Trace
    cpu_idle+0x37/0x4c
    start_kernel+0x270/0x272

I have no more information now and I do not know how to reproduce this
bug which raises at random times (the presence of an USB mouse plugged
seems to decrease the probability of such bug)

-- System Information:
Debian Release: 4.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-4-486
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)

Versions of packages linux-image-2.6.18-4-486 depends on:
ii  coreutils                     5.97-5.3   The GNU core utilities
ii  debconf [debconf-2.0]         1.5.11     Debian configuration management sy
ii  initramfs-tools [linux-initra 0.85g      tools for generating an initramfs
ii  module-init-tools             3.3-pre4-2 tools for managing Linux kernel mo

linux-image-2.6.18-4-486 recommends no packages.

-- debconf information:
  shared/kernel-image/really-run-bootloader: true
  linux-image-2.6.18-4-486/preinst/abort-overwrite-2.6.18-4-486:
  linux-image-2.6.18-4-486/preinst/abort-install-2.6.18-4-486:
  linux-image-2.6.18-4-486/postinst/old-initrd-link-2.6.18-4-486: true
  linux-image-2.6.18-4-486/preinst/bootloader-initrd-2.6.18-4-486: true
  linux-image-2.6.18-4-486/postinst/kimage-is-a-directory:
  linux-image-2.6.18-4-486/preinst/failed-to-move-modules-2.6.18-4-486:
  linux-image-2.6.18-4-486/postinst/bootloader-test-error-2.6.18-4-486:
  linux-image-2.6.18-4-486/preinst/overwriting-modules-2.6.18-4-486: true
  linux-image-2.6.18-4-486/postinst/old-system-map-link-2.6.18-4-486: true
  linux-image-2.6.18-4-486/preinst/lilo-initrd-2.6.18-4-486: true
  linux-image-2.6.18-4-486/preinst/lilo-has-ramdisk:
  linux-image-2.6.18-4-486/postinst/depmod-error-2.6.18-4-486: false
  linux-image-2.6.18-4-486/postinst/old-dir-initrd-link-2.6.18-4-486: true
  linux-image-2.6.18-4-486/preinst/already-running-this-2.6.18-4-486:
  linux-image-2.6.18-4-486/postinst/create-kimage-link-2.6.18-4-486: true
  linux-image-2.6.18-4-486/postinst/depmod-error-initrd-2.6.18-4-486: false
  linux-image-2.6.18-4-486/prerm/removing-running-kernel-2.6.18-4-486: true
  linux-image-2.6.18-4-486/preinst/initrd-2.6.18-4-486:
  linux-image-2.6.18-4-486/postinst/bootloader-error-2.6.18-4-486:
  linux-image-2.6.18-4-486/preinst/elilo-initrd-2.6.18-4-486: true
  linux-image-2.6.18-4-486/prerm/would-invalidate-boot-loader-2.6.18-4-486: true

--- End Message ---
--- Begin Message --- 
Sorry for the late reply. Since the upgrade of my kernel (more than
two month ago) I had no occurence of this bug. 

Due to the nature of the bug I cannot be completely sure it is
resolved but the probability is very high.

francois

--- End Message ---
Reply to: