From: Olaf Hering <olaf@aepfle.de>
To: linux-kernel@vger.kernel.org
Subject: oops in __delayacct_blkio_ticks with 2.6.18-rc4
Date: Mon, 21 Aug 2006 13:24:05 +0200 [thread overview]
Message-ID: <20060821112405.GA28356@aepfle.de> (raw)
https://bugzilla.novell.com/show_bug.cgi?id=200526
tsk->delays became 0 after or during the call to spinlock. _spin_lock cant be
called with 0.
pear login: Oops: Kernel access of bad area, sig: 11 [#1]
SMP NR_CPUS=128 NUMA
Modules linked in: pppoe pppox ppp_generic slhc joydev st ide_cd nfs lockd
nfs_acl sunrpc autofs ipv6 sg pdc202xx_new e1000 dm_mod raid0 ipr
firmware_class sr_mod cd
rom sd_mod scsi_mod
NIP: C00000000009D614 LR: C00000000009D604 CTR: 0000000000000000
REGS: c0000000bb307630 TRAP: 0300 Not tainted (2.6.18-rc4-20060810162421-ppc64)
MSR: 8000000000009032 <EE,ME,IR,DR> CR: 24042422 XER: 20000001
DAR: 0000000000000028, DSISR: 0000000040000000
TASK = c0000002e0542ae0[24051] 'w' THREAD: c0000000bb304000 CPU: 5
GPR00: C00000000009D604 C0000000BB3078B0 C000000000620130 C0000002E308EAA0
GPR04: C0000000BB307AD0 C0000000BB307AD8 C0000000BB307AEF C0000002D2A29480
GPR08: C00000011A482380 0000000000989680 0000000000000000 0000000000000000
GPR12: 0000000000000000 C000000000476B80 0000000000000000 0000000000000000
GPR16: 0000000000000000 0000000000000000 0000000000000011 0000000000400044
GPR20: 0000000000000000 0000000000005DED 0000000029B33DD2 000000000000FF15
GPR24: C00000013B42D500 0000000000000007 0000000000010002 0000000000000000
GPR28: 0000000000000000 C0000002D2A29480 C0000000004CAC98 C0000002D2A29480
NIP [C00000000009D614] .__delayacct_blkio_ticks+0x34/0x6c
LR [C00000000009D604] .__delayacct_blkio_ticks+0x24/0x6c
Call Trace:
[C0000000BB3078B0] [C00000000009D604] .__delayacct_blkio_ticks+0x24/0x6c (unreliable)
[C0000000BB307940] [C000000000128320] .do_task_stat+0x4b0/0x6fc
[C0000000BB307C40] [C000000000124F4C] .proc_info_read+0x9c/0x144
[C0000000BB307CF0] [C0000000000D394C] .vfs_read+0x118/0x200
[C0000000BB307D90] [C0000000000D3E30] .sys_read+0x4c/0x8c
[C0000000BB307E30] [C00000000000871C] syscall_exit+0x0/0x40
Instruction dump:
fba1ffe8 7c7d1b78 f8010010 f821ff71 60000000 60000000 e8630818 482e2c49
60000000 e97d0818 3d200098 61299680 <e86b0028> e80b0030 7c630214 7c634b92
next reply other threads:[~2006-08-21 11:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-21 11:24 Olaf Hering [this message]
2006-08-22 19:09 ` oops in __delayacct_blkio_ticks with 2.6.18-rc4 Shailabh Nagar
2006-08-23 11:18 ` Olaf Hering
2006-08-24 19:05 ` Shailabh Nagar
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=20060821112405.GA28356@aepfle.de \
--to=olaf@aepfle.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox