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

Bug#473644: marked as done (linux-image-2.6.24-1-686: S3 suspend oops once in a while)

Your message dated Wed, 5 Aug 2009 19:45:06 +0200
with message-id <20090805174506.GC10306@inutil.org>
and subject line Re: linux-image-2.6.24-1-686: S3 suspend oops once in a while
has caused the Debian Bug report #473644,
regarding linux-image-2.6.24-1-686: S3 suspend oops once in a while
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
473644: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=473644
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-image-2.6.24-1-686
Version: 2.6.24-4
Severity: normal

I've seen this oops a couple times now, though it doesn't happen
often.  I try to put the machine to sleep (S3) with Fn-F4, whose
action I've set to "/etc/acpi/sleepbtn.sh && /etc/acpi/sleep.sh", and
I see an oops in the dmesg (with no S3 sleep).  

The machine is a Thinkpad T60 with Intel video, wireless.  I had
installed the 2.6.24-5 version of the kernel package but had not
rebooted into it, so I was still running the 2.6.24-4 Debian kernel.
It's uname:

  Linux approx 2.6.24-1-686 #1 SMP Mon Feb 11 14:37:45 UTC 2008 i686 GNU/Linux

The oops:

BUG: unable to handle kernel NULL pointer dereference at virtual address 00000000
printing eip: 00000000 *pde = 00000000 
Oops: 0000 [#1] SMP 
Modules linked in: sbs sbshc battery ac thinkpad_acpi nvram thermal fan button iwl3945 mac80211 cfg80211 e1000 usb_storage snd_pcm_oss snd_mixer_oss snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device fuse i915 drm ipt_LOG xt_state iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack iptable_filter ip_tables x_tables ppdev parport_pc lp parport ipv6 dm_snapshot dm_mirror dm_mod loop pcmcia hci_usb bluetooth arc4 ecb blkcipher video output firmware_class psmouse serio_raw yenta_socket rsrc_nonstatic pcmcia_core irtty_sir sir_dev nsc_ircc snd_hda_intel irda snd_pcm snd_timer snd soundcore intel_agp agpgart i2c_i801 crc_ccitt snd_page_alloc i2c_core iTCO_wdt rtc pcspkr evdev ext3 jbd mbcache ide_cd cdrom sd_mod generic piix ide_core ata_generic ahci uhci_hcd libata ehci_hcd scsi_mod usbcore processor

Pid: 48, comm: kacpi_notify Not tainted (2.6.24-1-686 #1)
EIP: 0060:[<00000000>] EFLAGS: 00010282 CPU: 0
EIP is at _stext+0x3feff000/0x14
EAX: f7c36e14 EBX: f74fdaec ECX: 00000000 EDX: 00000080
ESI: f777d878 EDI: c020263d EBP: 00000000 ESP: f7d35f80
 DS: 007b ES: 007b FS: 00d8 GS: 0000 SS: 0068
Process kacpi_notify (pid: 48, ti=f7d34000 task=f7c940b0 task.ti=f7d34000)
Stack: c0207cc2 cab76940 cab76948 c020265f f31867a8 f7c5bdc0 c0132225 00000000 
       00000246 c0135554 f7c5bdc0 f7c5bdc0 c0132a9b f7d35fd0 c0132b55 00000000 
       f7c940b0 c0135441 f7d35fc8 f7d35fc8 f7c5bdc0 00000000 c013537a c0135342 
Call Trace:
 [<c0207cc2>] acpi_ev_notify_dispatch+0x4c/0x55
 [<c020265f>] acpi_os_execute_notify+0x22/0x2b
 [<c0132225>] run_workqueue+0x7d/0x109
 [<c0135554>] prepare_to_wait+0x12/0x49
 [<c0132a9b>] worker_thread+0x0/0xc5
 [<c0132b55>] worker_thread+0xba/0xc5
 [<c0135441>] autoremove_wake_function+0x0/0x35
 [<c013537a>] kthread+0x38/0x5e
 [<c0135342>] kthread+0x0/0x5e
 [<c0104b0f>] kernel_thread_helper+0x7/0x10
 =======================
Code:  Bad EIP value.
EIP: [<00000000>] _stext+0x3feff000/0x14 SS:ESP 0068:f7d35f80
---[ end trace 45643a917ff2a1b6 ]---


-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.24-1-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages linux-image-2.6.24-1-686 depends on:
ii  debconf [debconf-2.0]        1.5.20      Debian configuration management sy
ii  initramfs-tools [linux-initr 0.91e       tools for generating an initramfs
ii  module-init-tools            3.3-pre11-4 tools for managing Linux kernel mo

Versions of packages linux-image-2.6.24-1-686 recommends:
ii  libc6-i686                    2.7-10     GNU C Library: Shared libraries [i

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

--- End Message ---
--- Begin Message --- 
Version: 2.6.28-1

On Thu, Jan 01, 2009 at 10:52:07AM -0500, Sanjoy Mahajan wrote:
> >> I've seen this oops a couple times now, though it doesn't happen
> >> often.  I try to put the machine to sleep (S3) with Fn-F4, whose
> >> action I've set to "/etc/acpi/sleepbtn.sh && /etc/acpi/sleep.sh", and
> >> I see an oops in the dmesg (with no S3 sleep).
> 
> > Does this error still occur with more recent kernel versions?
> 
> I haven't seen it with vanilla 2.6.27.4.

Thanks for the feedback, marking as closed.

Cheers,
        Moritz

--- End Message ---
Reply to: