linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: landwer@free.fr
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	linux-acpi@vger.kernel.org,
	"linux-pm@lists.linux-foundation.org"
	<linux-pm@lists.linux-foundation.org>
Subject: Re: Macbook bug after suspend to disk
Date: Wed, 5 Sep 2007 08:35:35 -0700	[thread overview]
Message-ID: <20070905083535.d9e8373a.akpm@linux-foundation.org> (raw)
In-Reply-To: <1187650790.5194.2.camel@cocoduo.atr>

> On Tue, 21 Aug 2007 00:59:50 +0200 Lionel Landwerlin <landwer@free.fr> wrote:

Three weeks, no responses.

> I'm using 2.6.22.1 on my macbook (32bits). I had got this trace a few
> hours after a suspend to disk. I never got this kind of trace without
> suspend. I will try to reproduce with 2.6.22.3.

And was it reproducible?

> Here is the trace :
> 
> Aug 20 14:14:23 cocoduo kernel: kernel BUG at mm/slab.c:2980!

That's here:


               /*
                 * The slab was either on partial or free list so
                 * there must be at least one object available for
                 * allocation.
                 */
                BUG_ON(slabp->inuse < 0 || slabp->inuse >= cachep->num);


> Aug 20 14:14:23 cocoduo kernel: invalid opcode: 0000 [#1]
> Aug 20 14:14:23 cocoduo kernel: SMP 
> Aug 20 14:14:23 cocoduo kernel: Modules linked in: wlan_tkip wlan_ccmp usbkbd ath_pci button nfs lockd nfs_acl sunrpc ac battery cpufreq_ondemand cpufreq_powersave i915 drm binfmt_misc hci_usb rfcomm l2cap bluetooth ppdev lp parport ipv6 dm_snapshot dm_mirror dm_mod cpufreq_userspace acpi_cpufreq freq_table firewire_sbp2 loop joydev usbmouse appletouch snd_hda_intel tsdev sky2 rtc_cmos rtc_core intelfb i2c_i801 wlan_scan_sta iTCO_wdt snd_pcm snd_timer snd soundcore rtc_lib i2c_algo_bit ath_rate_sample intel_agp agpgart i2c_core snd_page_alloc wlan ath_hal(P) evdev ext3 jbd mbcache usbhid hid sd_mod ide_cd cdrom ata_piix ata_generic libata scsi_mod piix firewire_ohci firewire_core crc_itu_t ehci_hcd generic ide_core uhci_hcd usbcore thermal processor fan
> Aug 20 14:14:23 cocoduo kernel: CPU:    0
> Aug 20 14:14:23 cocoduo kernel: EIP:    0060:[<c016706a>]    Tainted: P       VLI

People might want to see this reproduced on an untainted kernel.  Did you
try disabling ath_hal?


> Aug 20 14:14:23 cocoduo kernel: EFLAGS: 00210092   (2.6.22-1-686 #1)
> Aug 20 14:14:23 cocoduo kernel: EIP is at cache_alloc_refill+0xe9/0x451
> Aug 20 14:14:23 cocoduo kernel: eax: 0000007f   ebx: c20bf800   ecx: df9e8d40   edx: 00000000
> Aug 20 14:14:23 cocoduo kernel: esi: db91c000   edi: 00000010   ebp: dfff1600   esp: eecdddbc
> Aug 20 14:14:23 cocoduo kernel: ds: 007b   es: 007b   fs: 00d8  gs: 0033  ss: 0068
> Aug 20 14:14:23 cocoduo kernel: Process hald (pid: 5167, ti=eecdc000 task=ef3a8a50 task.ti=eecdc000)
> Aug 20 14:14:23 cocoduo kernel: Stack: 00000000 00000000 000000d0 df9e8d40 df9e0c00 00000000 c0152f3b 00000044 
> Aug 20 14:14:23 cocoduo kernel:        000000d0 c0327ff4 ef3a8a50 00000000 000000a4 df9e8d40 00200202 c210ac24 
> Aug 20 14:14:23 cocoduo kernel:        c0167553 000000a4 00000001 000000a4 c02017f4 00000004 c210ac00 00000000 
> Aug 20 14:14:23 cocoduo kernel: Call Trace:
> Aug 20 14:14:23 cocoduo kernel:  [<c0152f3b>] __alloc_pages+0x52/0x294
> Aug 20 14:14:23 cocoduo kernel:  [<c0167553>] kmem_cache_zalloc+0x42/0x79
> Aug 20 14:14:23 cocoduo kernel:  [<c02017f4>] acpi_ps_alloc_op+0x5d/0x9e
> Aug 20 14:14:23 cocoduo kernel:  [<c02014a7>] acpi_ps_parse_loop+0x6f6/0x737
> Aug 20 14:14:23 cocoduo kernel:  [<c02007b2>] acpi_ps_parse_aml+0x60/0x237
> Aug 20 14:14:23 cocoduo kernel:  [<c01f444c>] acpi_ds_init_aml_walk+0xb4/0xfe
> Aug 20 14:14:23 cocoduo kernel:  [<c02019f0>] acpi_ps_execute_method+0x11b/0x1bb
> Aug 20 14:14:23 cocoduo kernel:  [<c01fed59>] acpi_ns_evaluate+0x99/0xf0
> Aug 20 14:14:23 cocoduo kernel:  [<c01fe9c1>] acpi_evaluate_object+0x139/0x1dc
> Aug 20 14:14:23 cocoduo kernel:  [<c01f0a6d>] acpi_evaluate_integer+0x80/0xb3
> Aug 20 14:14:23 cocoduo kernel:  [<f8e01096>] acpi_ac_get_state+0x26/0x61 [ac]
> Aug 20 14:14:23 cocoduo kernel:  [<c015d3ed>] vma_link+0x54/0xc9
> Aug 20 14:14:23 cocoduo kernel:  [<f8e01130>] acpi_ac_seq_show+0x12/0x4e [ac]
> Aug 20 14:14:23 cocoduo kernel:  [<c017fc87>] seq_read+0xe7/0x274
> Aug 20 14:14:23 cocoduo kernel:  [<c017fba0>] seq_read+0x0/0x274
> Aug 20 14:14:23 cocoduo kernel:  [<c016a5b9>] vfs_read+0xa6/0x128
> Aug 20 14:14:23 cocoduo kernel:  [<c016a9b5>] sys_read+0x41/0x67
> Aug 20 14:14:23 cocoduo kernel:  [<c0103d0e>] sysenter_past_esp+0x6b/0xa1
> Aug 20 14:14:23 cocoduo kernel:  =======================
> Aug 20 14:14:23 cocoduo kernel: Code: 00 00 00 8b 75 00 39 ee 75 15 8b 75 10 8d 45 10 c7 45 34 01 00 00 00 39 c6 0f 84 9c 00 00 00 8b 4c 24 0c 8b 41 38 39 46 10 72 34 <0f> 0b eb fe 8b 44 24 10 8b 5e 14 8b 08 8b 44 24 0c 8b 50 2c 8b 
> Aug 20 14:14:23 cocoduo kernel: EIP: [<c016706a>] cache_alloc_refill+0xe9/0x451 SS:ESP 0068:eecdddbc

Well it seems to think that some ACPI slab cache is wrecked.

It would be interesting to see if the same happens with CONFIG_SLUB=n,
CONFIG_SLAB=y.

Is this a regression?  Was 2.6.21 OK?  2.6.20?

If you didn't have all slab debug options enabled, please do so.

If this is repeatable and if nobody fixes it (likely) then please raise a
reports against acpi at bugzilla.kernel.org, thanks.

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

           reply	other threads:[~2007-09-05 15:35 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <1187650790.5194.2.camel@cocoduo.atr>]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070905083535.d9e8373a.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=landwer@free.fr \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-pm@lists.linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox