From: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
To: kernel list <linux-kernel@vger.kernel.org>
Cc: stable@kernel.org, npiggin@suse.de,
Andy Whitcroft <apw@shadowen.org>,
Balbir Singh <balbir@linux.vnet.ibm.com>
Subject: [BUG] 2.6.24.4 kernel bug while running ftest03
Date: Thu, 03 Apr 2008 13:27:07 +0530 [thread overview]
Message-ID: <47F48DD3.8070103@linux.vnet.ibm.com> (raw)
Hi,
The kernel panic's, while running the LTP ftest03 on the 2.6.24.4 kernel
compiled with the gcov patches from LTP.
(http://ltp.cvs.sourceforge.net/ltp/utils/analysis/gcov-kernel/linux-2.6.24-gcov.patch?view=markup)
BUG: unable to handle kernel paging request at virtual address f8000004
printing eip: c01c2836 *pdpt = 0000000000004001 *pde = 0000000000000000
Oops: 0000 [#1] SMP
Modules linked in: hidp rfcomm l2cap bluetooth dm_multipath nvram via686a hwmon i2c_viapro pcspkr mptsas scsi_transport_sas floppy tg3 parport_pc ac battery button dm_mirror dm_mod joydev sunrpc i2c_dev i2c_core autofs4 lp parport ipv6 md5 sg mptspi mptscsih mptbase scsi_transport_spi sd_mod scsi_mod ehci_hcd ohci_hcd uhci_hcdPid: 24160, comm: ftest03 Not tainted (2.6.24.4-gcov-autokern1 #1)
EIP: 0060:[<c01c2836>] EFLAGS: 00010246 CPU: 1
EIP is at iov_iter_advance+0xe9/0x155
EAX: 00000000 EBX: f3457d98 ECX: 00000080 EDX: 00000000
ESI: 00000000 EDI: f8000000 EBP: f33f6d30 ESP: f3457d24
DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068
Process ftest03 (pid: 24160, ti=f3457000 task=f6544590 task.ti=f3457000)
Stack: 00000800 0006b800 00000000 c01c5e79 0006b800 00000000 00000800 00000800
c7209030 c015cdea f3457e8c f7fb9180 f33f6d30 c07b1600 f33f6c68 00000000
00000800 00000800 00000000 c07b1600 00000000 0000006b f3457da8 c02f11cd
Call Trace:
[<c01c5e79>] generic_file_buffered_write+0x29f/0xc05
[<c015cdea>] current_fs_time+0x4e/0x6f
[<c02f11cd>] ext3_readpages+0x0/0x35
[<c02f11cd>] ext3_readpages+0x0/0x35
[<c01d1da4>] __do_page_cache_readahead+0x268/0x386
[<c015cdea>] current_fs_time+0x4e/0x6f
[<c01c6f97>] __generic_file_aio_write_nolock+0x7b8/0x852
[<c01c70be>] generic_file_aio_write+0x8d/0x162
[<c01c7bfd>] generic_file_aio_read+0x292/0x31a
[<c02ecfc2>] ext3_file_write+0x32/0x17c
[<c020b830>] do_sync_readv_writev+0xcf/0x152
[<c01c5163>] wait_on_page_writeback_range+0x153/0x1e7
[<c017d0f7>] autoremove_wake_function+0x0/0x5f
[<c04f21b9>] copy_from_user+0xb1/0x135
[<c020b602>] rw_copy_check_uvector+0xd2/0x19f
[<c020c4f6>] do_readv_writev+0x152/0x328
[<c02ecf90>] ext3_file_write+0x0/0x17c
[<c079c11d>] _spin_unlock+0x13/0x22
[<c01b427e>] audit_syscall_entry+0x2eb/0x323
[<c020c758>] vfs_writev+0x8c/0x9e
[<c020cf6c>] sys_writev+0x8b/0x1a5
[<c0108a76>] syscall_call+0x7/0xb
=======================
Code: c0 00 29 c8 01 ce 89 43 0c 39 77 04 75 13 83 c7 08 83 05 98 63 a6 c0 01 83 15 9c 63 a6 c0 00 31 f6 29 ca 85 d2 0f 85 78 ff ff ff <83> 7f 04 00 75 29 83 05 a0 63 a6 c0 01 83 15 a4 63 a6 c0 00 83 EIP: [<c01c2836>] iov_iter_advance+0xe9/0x155 SS:ESP 0068:f3457d24---[ end trace af3ae442124c3d18 ]---
--
Thanks & Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
next reply other threads:[~2008-04-03 7:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-03 7:57 Kamalesh Babulal [this message]
2008-04-03 12:46 ` Jan Kara
2008-04-03 12:53 ` Jan Kara
2008-04-03 13:18 ` Nick Piggin
2008-04-03 17:00 ` Kamalesh Babulal
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=47F48DD3.8070103@linux.vnet.ibm.com \
--to=kamalesh@linux.vnet.ibm.com \
--cc=apw@shadowen.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=npiggin@suse.de \
--cc=stable@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
Powered by JetHome