All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Zdenek Kabelac" <zdenek.kabelac@gmail.com>
To: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: BUG: unable to handle kernel paging request - scsi_bus_uevent
Date: Wed, 14 May 2008 11:23:02 +0200	[thread overview]
Message-ID: <c4e36d110805140223w640a4e1erf613ce27284e78ff@mail.gmail.com> (raw)

Hello


With kernel 2.6.26-rc2 - commit 093e2bb3cb5fcc37e3d02a193a3435ba64e9eb7b
(2 days old) I've got oops during boot (my setup T61, C2D, 2GB)

Zdenek

This oops is not deterministic

BUG: unable to handle kernel paging request at ffff81007ca27f78
IP: [<ffffffff81218497>] scsi_bus_uevent+0x7/0x30
PGD 8063 PUD a063 PMD 7ceb8163 PTE 800000007ca27160
Oops: 0000 [1] PREEMPT SMP DEBUG_PAGEALLOC
CPU 0
Modules linked in: uhci_hcd ohci_hcd ehci_hcd usbcore
Pid: 612, comm: udevtrigger Not tainted 2.6.26-rc2 #1
RIP: 0010:[<ffffffff81218497>]  [<ffffffff81218497>] scsi_bus_uevent+0x7/0x30
RSP: 0018:ffff81007c9ffdb8  EFLAGS: 00010286
RAX: ffff81007e152090 RBX: ffff81007ca28028 RCX: 0000000000000003
RDX: ffff81007e1521e9 RSI: ffff81007e152090 RDI: ffff81007ca28028
RBP: ffff81007c9ffdb8 R08: 00000000fffffffe R09: 000000000000000b
R10: ffffffff8140d3d1 R11: ffff81007c9ffcd8 R12: ffff81007e152090
R13: 0000000000000000 R14: ffffffff8147c8e0 R15: 0000000000000000
FS:  00007f57ce88a780(0000) GS:ffffffff81493000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: ffff81007ca27f78 CR3: 000000007cefb000 CR4: 00000000000006e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Process udevtrigger (pid: 612, threadinfo ffff81007c9fe000, task
ffff81007c910000)
Stack:  ffff81007c9ffdd8 ffffffff81202bf4 ffff81007e02d738 ffff81007ca281d8
 ffff81007c9ffe68 ffffffff81177cd5 ffffffff813e5dff 0000000000000000
 ffff81007ca88cc0 ffff81007e152090 ffffffff8142831e 0000000000000000
Call Trace:
 [<ffffffff81202bf4>] dev_uevent+0x84/0x120
 [<ffffffff81177cd5>] kobject_uevent_env+0x1d5/0x3f0
 [<ffffffff81177efb>] kobject_uevent+0xb/0x10
 [<ffffffff81202eb8>] store_uevent+0x38/0xa0
 [<ffffffff8120244e>] dev_attr_store+0x1e/0x20
 [<ffffffff8111032a>] sysfs_write_file+0xca/0x140
 [<ffffffff810b98eb>] vfs_write+0xcb/0x170
 [<ffffffff810b9a80>] sys_write+0x50/0x90
 [<ffffffff8100c50b>] system_call_after_swapgs+0x7b/0x80


Code: f5 ff 4d 85 e4 74 0f 49 8b 44 24 28 48 85 c0 74 05 48 89 df ff
d0 31 c0 48 8b 1c 24 4c 8b 64 24 08 c9 c3 90 55 48 89 f0 48 89 e5 <0f>
be 97 50 ff ff ff 48 c7 c6 43 d4 40 81 48 89 c7 31 c0 e8 21
RIP  [<ffffffff81218497>] scsi_bus_uevent+0x7/0x30
 RSP <ffff81007c9ffdb8>
CR2: ffff81007ca27f78
---[ end trace 30e85c42da63b92f ]---
BUG: sleeping function called from invalid context at kernel/rwsem.c:21
in_atomic():0, irqs_disabled():1
INFO: lockdep is turned off.
irq event stamp: 129392
hardirqs last  enabled at (129391): [<ffffffff810b525d>] __kmalloc+0x7d/0x120
hardirqs last disabled at (129392): [<ffffffff812f7de5>]
do_page_fault+0x35/0xaf0
softirqs last  enabled at (129304): [<ffffffff812802dd>] sk_filter+0x9d/0xe0
softirqs last disabled at (129302): [<ffffffff8128028a>] sk_filter+0x4a/0xe0
Pid: 612, comm: udevtrigger Tainted: G      D   2.6.26-rc2 #1

Call Trace:
 [<ffffffff8105ffa0>] ? print_irqtrace_events+0x110/0x120
 [<ffffffff81032bcc>] __might_sleep+0xec/0x130
 [<ffffffff812f33e0>] down_read+0x20/0x70
 [<ffffffff81075af4>] acct_collect+0x44/0x1f0
 [<ffffffff8103fb4c>] do_exit+0x19c/0x8a0
 [<ffffffff811f06cf>] ? do_unblank_screen+0x1f/0x170
 [<ffffffff812f5ee8>] oops_end+0x88/0x90
 [<ffffffff812f8030>] do_page_fault+0x280/0xaf0
 [<ffffffff81063724>] ? __lock_acquire+0x364/0x11d0
 [<ffffffff8117c7b2>] ? vsnprintf+0x472/0x7e0
 [<ffffffff812f575d>] error_exit+0x0/0xa9
 [<ffffffff81218497>] ? scsi_bus_uevent+0x7/0x30
 [<ffffffff81202bf4>] ? dev_uevent+0x84/0x120
 [<ffffffff81177cd5>] ? kobject_uevent_env+0x1d5/0x3f0
 [<ffffffff81177efb>] ? kobject_uevent+0xb/0x10
 [<ffffffff81202eb8>] ? store_uevent+0x38/0xa0
 [<ffffffff8120244e>] ? dev_attr_store+0x1e/0x20
 [<ffffffff8111032a>] ? sysfs_write_file+0xca/0x140
 [<ffffffff810b98eb>] ? vfs_write+0xcb/0x170
 [<ffffffff810b9a80>] ? sys_write+0x50/0x90
 [<ffffffff8100c50b>] ? system_call_after_swapgs+0x7b/0x80

agpgart: Detected an Intel 965GM Chipset.
agpgart: Detected 7676K stolen memory.
agpgart: AGP aperture is 256M @ 0xe0000000

             reply	other threads:[~2008-05-14  9:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-14  9:23 Zdenek Kabelac [this message]
2008-05-15  2:48 ` BUG: unable to handle kernel paging request - scsi_bus_uevent Andrew Morton

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=c4e36d110805140223w640a4e1erf613ce27284e78ff@mail.gmail.com \
    --to=zdenek.kabelac@gmail.com \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.