From: "Miles Lane" <miles.lane@gmail.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Christoph Lameter" <cl@linux-foundation.org>,
"Ingo Molnar" <mingo@elte.hu>, "Tejun Heo" <htejun@gmail.com>
Subject: Re: 2.6.28-rc6-git1 -- BUG: unable to handle kernel paging request at ffff8800be8b0019
Date: Thu, 27 Nov 2008 11:14:37 -0500 [thread overview]
Message-ID: <a44ae5cd0811270814m380f1439k93a7eadd6726e811@mail.gmail.com> (raw)
In-Reply-To: <200811270026.37941.rjw@sisk.pl>
I don't recall doing a suspend/resume. I have tried to reproduce this
BUG, but haven't managed it thus far. I will keep trying. I can't spend
too much time on it, as I have a work project to complete.
Thanks,
Miles
On Wed, Nov 26, 2008 at 6:26 PM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> On Tuesday, 25 of November 2008, Miles Lane wrote:
>> # find /sys -name "*" | xargs tail
>>
>> [ 3866.840809] BUG: unable to handle kernel paging request at ffff8800be8b0019
>> [ 3866.840819] IP: [<ffffffff80262f07>] kallsyms_lookup+0x20/0x120
>> [ 3866.840828] PGD 202063 PUD 117f067 PMD 1374067 PTE 80000000be8b0160
>> [ 3866.840835] Oops: 0002 [#1] PREEMPT SMP DEBUG_PAGEALLOC
>> [ 3866.840842] last sysfs file: /sys/kernel/slab/kmalloc-64/alloc_calls
>> [ 3866.840846] CPU 1
>> [ 3866.840849] Modules linked in: hci_uart serport ipv6 af_packet
>> binfmt_misc sco bridge stp llc rfcomm bnep l2cap bluetooth
>> acpi_cpufreq cpufreq_performance cpufreq_powersave iptable_filter
>> ip_tables sbp2 parport_pc lp parport snd_hda_intel pcmcia snd_pcm_oss
>> snd_mixer_oss snd_pcm snd_page_alloc snd_hwdep snd_seq_dummy
>> snd_seq_oss snd_seq_midi tifm_7xx1 iwl3945 evdev snd_rawmidi tifm_core
>> psmouse rfkill rng_core yenta_socket rsrc_nonstatic iTCO_wdt
>> iTCO_vendor_support mac80211 snd_seq_midi_event snd_seq snd_timer
>> snd_seq_device snd battery ac shpchp button soundcore loop sd_mod
>> sr_mod cdrom sg ohci1394 ieee1394 ehci_hcd uhci_hcd sky2 usbcore
>> thermal processor fan unix
>> [ 3866.840943] Pid: 7717, comm: tail Not tainted 2.6.28-rc6-git1 #6
>> [ 3866.840946] RIP: 0010:[<ffffffff80262f07>] [<ffffffff80262f07>]
>> kallsyms_lookup+0x20/0x120
>> [ 3866.840953] RSP: 0018:ffff880073d63da8 EFLAGS: 00010292
>> [ 3866.840956] RAX: 0000000000000f9a RBX: ffffffff80695c45 RCX: ffff880073d63e00
>> [ 3866.840959] RDX: ffff880073d63df8 RSI: ffff880073d63df0 RDI: ffffffff80695c45
>> [ 3866.840962] RBP: ffff880073d63dd8 R08: ffff8800be8aff9a R09: 0000000000000000
>> [ 3866.840965] R10: ffff88013e8aff91 R11: 000000000000000a R12: ffff8800be8aff9a
>> [ 3866.840968] R13: ffff880073d63df8 R14: ffff880073d63df0 R15: ffff880073d63e00
>> [ 3866.840972] FS: 00007f707c7996e0(0000) GS:ffff8800bf002898(0000)
>> knlGS:0000000000000000
>> [ 3866.840975] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
>> [ 3866.840978] CR2: ffff8800be8b0019 CR3: 0000000090844000 CR4: 00000000000006e0
>> [ 3866.840982] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
>> [ 3866.840985] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
>> [ 3866.840989] Process tail (pid: 7717, threadinfo ffff880073d62000,
>> task ffff880088e3dd00)
>> [ 3866.840992] Stack:
>> [ 3866.840994] ffffffff806638f8 ffff8800be8aff9a ffffffff80695c45
>> ffff8800be8af000
>> [ 3866.841000] 0000000000000037 0000000000000fce ffff880073d63e18
>> ffffffff8026302f
>> [ 3866.841008] 0000000000000002 0000000000000f90 ffff880052574f30
>> ffff8800be8af000
>> [ 3866.841017] Call Trace:
>> [ 3866.841020] [<ffffffff8026302f>] sprint_symbol+0x28/0xaa
>> [ 3866.841025] [<ffffffff8029e972>] list_locations+0x170/0x2ef
>> [ 3866.841031] [<ffffffff8029eb34>] alloc_calls_show+0x1c/0x24
>> [ 3866.841036] [<ffffffff8029cbbc>] slab_attr_show+0x23/0x27
>> [ 3866.841041] [<ffffffff802efdff>] sysfs_read_file+0xba/0x13c
>> [ 3866.841046] [<ffffffff802a4795>] vfs_read+0xa4/0xde
>> [ 3866.841052] [<ffffffff802a4893>] sys_read+0x47/0x6e
>> [ 3866.841056] [<ffffffff8020b6fb>] system_call_fastpath+0x16/0x1b
>> [ 3866.841062] Code: df e8 39 d2 ff ff 5b 41 5c c9 c3 55 48 89 e5 41
>> 57 49 89 cf 41 56 49 89 f6 41 55 49 89 d5 41 54 4d 89 c4 53 48 89 fb
>> 48 83 ec 08 <41> c6 40 7f 00 41 c6 00 00 48 81 ff 00 90 20 80 72 09 48
>> 81 ff
>> [ 3866.841128] RIP [<ffffffff80262f07>] kallsyms_lookup+0x20/0x120
>> [ 3866.841134] RSP <ffff880073d63da8>
>> [ 3866.841136] CR2: ffff8800be8b0019
>> [ 3866.841140] ---[ end trace ebccc2f1a2509fb0 ]---
>
> Did that happen after a resume from suspend to RAM, by chance?
>
> Rafael
>
prev parent reply other threads:[~2008-11-27 16:14 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-25 16:50 Miles Lane
2008-11-26 23:26 ` Rafael J. Wysocki
2008-11-27 13:37 ` Pekka Enberg
2008-11-27 13:50 ` Vegard Nossum
2008-11-27 13:54 ` Hugh Dickins
2008-11-27 14:13 ` Pekka Enberg
2008-11-27 17:34 ` Hugh Dickins
2008-11-27 21:23 ` Pekka Enberg
2008-11-27 21:56 ` Hugh Dickins
2008-11-27 22:51 ` Christoph Lameter
2008-11-28 7:57 ` Pekka Enberg
2008-11-27 23:27 ` Steven Rostedt
2008-11-27 23:31 ` Steven Rostedt
2008-11-28 0:16 ` Frederic Weisbecker
2008-11-29 6:40 ` Andrew Morton
2008-11-28 7:56 ` Pekka Enberg
2008-12-01 20:51 ` Andrew Morton
2008-12-01 22:47 ` Hugh Dickins
2008-12-02 0:57 ` Rusty Russell
2008-11-27 16:14 ` Miles Lane [this message]
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=a44ae5cd0811270814m380f1439k93a7eadd6726e811@mail.gmail.com \
--to=miles.lane@gmail.com \
--cc=cl@linux-foundation.org \
--cc=htejun@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rjw@sisk.pl \
/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
all inboxes | Powered by JetHome®