From: Anisse Astier <anisse@astier.eu>
To: linux-fsdevel@vger.kernel.org
Subject: [BUG] Oops while mkfs.ext3 in block/writeback
Date: Mon, 20 Sep 2010 17:49:42 +0200 [thread overview]
Message-ID: <20100920174942.46b3ffc7@destiny.ordissimo> (raw)
Hi,
(Please Cc: me since I'm not subscribed to fsdevel)
I had this oops on a Toshiba L670D laptop; I was able to reproduce with
version 2.6.33.3 and 2.6.31.6 (I know these aren't up-to-date).
This happened while running "mkfs.ext3 -O dir_index -L home /dev/sda9".
Oops:
[ 71.731461] BUG: unable to handle kernel NULL pointer dereference at (null)
[ 71.732128] IP: [<c108df53>] __block_write_full_page+0x10f/0x2e0
[ 71.732128] *pde = 00000000
[ 71.732128] Oops: 0000 [#1] SMP
[ 71.732128] last sysfs file: /sys/devices/pci0000:00/0000:00:11.0/host0/target0:0:0/0:0:0:0/block/sda/sda9/size
[ 71.732128] Modules linked in: ipv6 fuse snd_hda_codec_atihdmi uvcvideo videodev snd_hda_codec_realtek usb_storage video v4l1_compat snd_hda_intel output snd_hda_codec battery ac rtc_cmos snd_hwdep rtc_core snd_pcm rtc_lib snd_timer r8192se_pci snd i2c_piix4 snd_page_alloc i2c_core button processor nfs lockd nfs_acl auth_rpcgss sunrpc smsc95xx usbnet ohci_hcd ehci_hcd usbcore thermal thermal_sys
[ 71.732128]
[ 71.732128] Pid: 2642, comm: flush-8:0 Not tainted 2.6.35.4 #30 NALAE/Satellite L670D
[ 71.732128] EIP: 0060:[<c108df53>] EFLAGS: 00010297 CPU: 1
[ 71.732128] EIP is at __block_write_full_page+0x10f/0x2e0
[ 71.732128] EAX: 00003a9d EBX: 03080313 ECX: 00000002 EDX: 0000000a
[ 71.732128] ESI: 00000000 EDI: 00000000 EBP: c145e5e0 ESP: f6ab7dc0
[ 71.732128] DS: 007b ES: 007b FS: 00d8 GS: 0000 SS: 0068
[ 71.732128] Process flush-8:0 (pid: 2642, ti=f6ab6000 task=f59c63b0 task.ti=f6ab6000)
[ 71.790021] Stack:
[ 71.790021] c009c1d0 00000001 f05aa2bc 00000400 0d2742e8 00000000 c10900bf c145e5e0
[ 71.790021] <0> f05aa2bc 9d0ba400 00000034 c108e1ca f6ab7f10 c108ccdb c10900bf f6ab7f10
[ 71.790021] <0> f05aa36c f6ab7f10 00000000 00000000 c108e1dd c108ccdb c1056a67 c145e5e0
[ 71.790021] Call Trace:
[ 71.790021] [<c10900bf>] ? blkdev_get_block+0x0/0xc9
[ 71.790021] [<c108e1ca>] ? block_write_full_page_endio+0xa6/0xaf
[ 71.790021] [<c108ccdb>] ? end_buffer_async_write+0x0/0xd1
[ 71.790021] [<c10900bf>] ? blkdev_get_block+0x0/0xc9
[ 71.790021] [<c108e1dd>] ? block_write_full_page+0xa/0xc
[ 71.790021] [<c108ccdb>] ? end_buffer_async_write+0x0/0xd1
[ 71.790021] [<c1056a67>] ? __writepage+0x8/0x1f
[ 71.790021] [<c1056fdb>] ? write_cache_pages+0x1af/0x267
[ 71.790021] [<c1056a5f>] ? __writepage+0x0/0x1f
[ 71.790021] [<c10570a9>] ? generic_writepages+0x16/0x1d
[ 71.790021] [<c10570c4>] ? do_writepages+0x14/0x20
[ 71.790021] [<c1087593>] ? writeback_single_inode+0xb0/0x272
[ 71.790021] [<c1087b51>] ? writeback_sb_inodes+0x128/0x1da
[ 71.790021] [<c1087fab>] ? writeback_inodes_wb+0xfa/0x10a
[ 71.790021] [<c1088127>] ? wb_writeback+0x16c/0x1d2
[ 71.790021] [<c10881cd>] ? wb_do_writeback+0x40/0x117
[ 71.790021] [<c102c42f>] ? process_timeout+0x0/0x5
[ 71.790021] [<c10882d3>] ? bdi_writeback_task+0x2f/0xe8
[ 71.790021] [<c105f754>] ? bdi_start_fn+0x52/0x9e
[ 71.790021] [<c105f702>] ? bdi_start_fn+0x0/0x9e
[ 71.790021] [<c10337df>] ? kthread+0x5f/0x64
[ 71.790021] [<c1033780>] ? kthread+0x0/0x64
[ 71.790021] [<c1002b76>] ? kernel_thread_helper+0x6/0x10
[ 71.790021] Code: d3 e3 f6 c1 20 74 04 89 de 31 db 8b 45 0c 89 04 24 89 c7 3b 74 24 14 72 12 77 06 3b 5c 24 10 76 0a f0 80 27 fd f0 80 0f 01 eb 5c <8b> 07 a8 20 74 05 f6 c4 02 74 51 a8 02 74 4d 8b 54 24 0c 39 57
[ 71.790021] EIP: [<c108df53>] __block_write_full_page+0x10f/0x2e0 SS:ESP 0068:f6ab7dc0
[ 71.790021] CR2: 0000000000000000
[ 71.791599] ---[ end trace ce00a6c6f84b6ee8 ]---
Regards,
Anisse
next reply other threads:[~2010-09-20 15:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-20 15:49 Anisse Astier [this message]
2010-09-24 9:24 ` [BUG] Oops while mkfs.ext3 in block/writeback Anisse Astier
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=20100920174942.46b3ffc7@destiny.ordissimo \
--to=anisse@astier.eu \
--cc=linux-fsdevel@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;
as well as URLs for NNTP newsgroup(s).