From: Luiz Capitulino <lcapitulino@prefeitura.sp.gov.br>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: 2.6.0-test3-mm2
Date: 13 Aug 2003 10:35:45 -0300 [thread overview]
Message-ID: <1060781719.449.6.camel@lorien> (raw)
In-Reply-To: <200308132302.26656.kernel@kolivas.org>
Em Qua, 2003-08-13 às 10:02, Con Kolivas escreveu:
> Got this on running lilo (scary but it didn't kill my bootblock).
>
> Aug 13 22:54:58 pc kernel: ------------[ cut here ]------------
> Aug 13 22:54:58 pc kernel: kernel BUG at mm/filemap.c:1930!
> Aug 13 22:54:58 pc kernel: invalid operand: 0000 [#2]
> Aug 13 22:54:58 pc kernel: PREEMPT
> Aug 13 22:54:58 pc kernel: CPU: 0
> Aug 13 22:54:58 pc kernel: EIP: 0060:[<c013b519>] Not tainted VLI
> Aug 13 22:54:58 pc kernel: EFLAGS: 00010282
> Aug 13 22:54:58 pc kernel: EIP is at generic_file_aio_write_nolock+0xe8/0xf5
> Aug 13 22:54:58 pc kernel: eax: 00000000 ebx: 00000000 ecx: df5a4ab0
> edx: df5a4ab0
> Aug 13 22:54:58 pc kernel: esi: 00000000 edi: deecdf6c ebp: deecde84
> esp: deecde40
> Aug 13 22:54:58 pc kernel: ds: 007b es: 007b ss: 0068
> Aug 13 22:54:58 pc kernel: Process lilo (pid: 396, threadinfo=deecc000
> task=c17ac6a0)
> Aug 13 22:54:58 pc kernel: Stack: deecc000 00034001 00000000 00000129 00000138
> c17a7c80 c17a7d10 df909980
> Aug 13 22:54:58 pc kernel: deecde84 df909980 00000000 00000000 c013b682
> deecde84 deecdf6c 00000001
> Aug 13 22:54:58 pc kernel: df9099a0 0806f220 00000200 00000000 00000001
> ffffffff df909980 de86ee68
> Aug 13 22:54:58 pc kernel: Call Trace:
> Aug 13 22:54:58 pc kernel: [<c013b682>] generic_file_write_nolock+0xa2/0xba
> Aug 13 22:54:58 pc kernel: [<c011f126>] autoremove_wake_function+0x0/0x4f
> Aug 13 22:54:58 pc kernel: [<c01a4ba9>] reiserfs_bmap+0x62/0xa6
> Aug 13 22:54:58 pc kernel: [<c01a89ce>] reiserfs_aop_bmap+0x0/0x23
> Aug 13 22:54:58 pc kernel: [<c0158a7b>] generic_block_bmap+0x38/0x40
> Aug 13 22:54:58 pc kernel: [<c01c46e2>] reiserfs_ioctl+0x2b2/0x2b9
> Aug 13 22:54:58 pc kernel: [<c015c939>] blkdev_file_write+0x37/0x3b
> Aug 13 22:54:58 pc kernel: [<c015420c>] vfs_write+0xbc/0x127
> Aug 13 22:54:58 pc kernel: [<c015b7e8>] block_llseek+0x0/0xd5
> Aug 13 22:54:58 pc kernel: [<c015431c>] sys_write+0x42/0x63
> Aug 13 22:54:58 pc kernel: [<c031280f>] syscall_call+0x7/0xb
> Aug 13 22:54:58 pc kernel: [<c031007b>] pfkey_spdflush+0xb8/0xd6
> Aug 13 22:54:58 pc kernel:
> Aug 13 22:54:58 pc kernel: Code: eb f2 8b 54 24 40 89 7c 24 04 c7 44 24 08 01
> 00 00 00 89 54 24 0c 89 2c 24 e8 75 f4 ff ff 8
> 3 7d 10 ff 89 c7 75 ce e9 70 ff ff ff <0f> 0b 8a 07 3f b7 32 c0 e9 54 ff ff ff
> 53 ba 00 e0 ff ff 21 e2
I got the some thing, this happens when fsck will check the
first partition.
PS: my offesets and the call trace is different. Do you need
it ?
--
Luiz Fernando N. Capitulino
<lcapitulino@prefeitura.sp.gov.br>
<http://www.telecentros.sp.gov.br>
WARNING: multiple messages have this Message-ID (diff)
From: Luiz Capitulino <lcapitulino@prefeitura.sp.gov.br>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: 2.6.0-test3-mm2
Date: 13 Aug 2003 10:35:45 -0300 [thread overview]
Message-ID: <1060781719.449.6.camel@lorien> (raw)
In-Reply-To: <200308132302.26656.kernel@kolivas.org>
Em Qua, 2003-08-13 as 10:02, Con Kolivas escreveu:
> Got this on running lilo (scary but it didn't kill my bootblock).
>
> Aug 13 22:54:58 pc kernel: ------------[ cut here ]------------
> Aug 13 22:54:58 pc kernel: kernel BUG at mm/filemap.c:1930!
> Aug 13 22:54:58 pc kernel: invalid operand: 0000 [#2]
> Aug 13 22:54:58 pc kernel: PREEMPT
> Aug 13 22:54:58 pc kernel: CPU: 0
> Aug 13 22:54:58 pc kernel: EIP: 0060:[<c013b519>] Not tainted VLI
> Aug 13 22:54:58 pc kernel: EFLAGS: 00010282
> Aug 13 22:54:58 pc kernel: EIP is at generic_file_aio_write_nolock+0xe8/0xf5
> Aug 13 22:54:58 pc kernel: eax: 00000000 ebx: 00000000 ecx: df5a4ab0
> edx: df5a4ab0
> Aug 13 22:54:58 pc kernel: esi: 00000000 edi: deecdf6c ebp: deecde84
> esp: deecde40
> Aug 13 22:54:58 pc kernel: ds: 007b es: 007b ss: 0068
> Aug 13 22:54:58 pc kernel: Process lilo (pid: 396, threadinfo=deecc000
> task=c17ac6a0)
> Aug 13 22:54:58 pc kernel: Stack: deecc000 00034001 00000000 00000129 00000138
> c17a7c80 c17a7d10 df909980
> Aug 13 22:54:58 pc kernel: deecde84 df909980 00000000 00000000 c013b682
> deecde84 deecdf6c 00000001
> Aug 13 22:54:58 pc kernel: df9099a0 0806f220 00000200 00000000 00000001
> ffffffff df909980 de86ee68
> Aug 13 22:54:58 pc kernel: Call Trace:
> Aug 13 22:54:58 pc kernel: [<c013b682>] generic_file_write_nolock+0xa2/0xba
> Aug 13 22:54:58 pc kernel: [<c011f126>] autoremove_wake_function+0x0/0x4f
> Aug 13 22:54:58 pc kernel: [<c01a4ba9>] reiserfs_bmap+0x62/0xa6
> Aug 13 22:54:58 pc kernel: [<c01a89ce>] reiserfs_aop_bmap+0x0/0x23
> Aug 13 22:54:58 pc kernel: [<c0158a7b>] generic_block_bmap+0x38/0x40
> Aug 13 22:54:58 pc kernel: [<c01c46e2>] reiserfs_ioctl+0x2b2/0x2b9
> Aug 13 22:54:58 pc kernel: [<c015c939>] blkdev_file_write+0x37/0x3b
> Aug 13 22:54:58 pc kernel: [<c015420c>] vfs_write+0xbc/0x127
> Aug 13 22:54:58 pc kernel: [<c015b7e8>] block_llseek+0x0/0xd5
> Aug 13 22:54:58 pc kernel: [<c015431c>] sys_write+0x42/0x63
> Aug 13 22:54:58 pc kernel: [<c031280f>] syscall_call+0x7/0xb
> Aug 13 22:54:58 pc kernel: [<c031007b>] pfkey_spdflush+0xb8/0xd6
> Aug 13 22:54:58 pc kernel:
> Aug 13 22:54:58 pc kernel: Code: eb f2 8b 54 24 40 89 7c 24 04 c7 44 24 08 01
> 00 00 00 89 54 24 0c 89 2c 24 e8 75 f4 ff ff 8
> 3 7d 10 ff 89 c7 75 ce e9 70 ff ff ff <0f> 0b 8a 07 3f b7 32 c0 e9 54 ff ff ff
> 53 ba 00 e0 ff ff 21 e2
I got the some thing, this happens when fsck will check the
first partition.
PS: my offesets and the call trace is different. Do you need
it ?
--
Luiz Fernando N. Capitulino
<lcapitulino@prefeitura.sp.gov.br>
<http://www.telecentros.sp.gov.br>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2003-08-13 13:38 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-13 8:31 2.6.0-test3-mm2 Andrew Morton
2003-08-13 8:31 ` 2.6.0-test3-mm2 Andrew Morton
2003-08-13 9:11 ` How to use hugetlb for the text of a program ? dada1
2003-08-13 9:26 ` Andrew Morton
2003-08-13 12:42 ` dada1
2003-08-13 9:22 ` 2.6.0-test3-mm2 hugang
2003-08-13 10:48 ` 2.6.0-test3-mm2 Andrew Morton
2003-08-13 13:02 ` 2.6.0-test3-mm2 Con Kolivas
2003-08-13 13:02 ` 2.6.0-test3-mm2 Con Kolivas
2003-08-13 13:35 ` Luiz Capitulino [this message]
2003-08-13 13:35 ` 2.6.0-test3-mm2 Luiz Capitulino
2003-08-13 13:36 ` 2.6.0-test3-mm2 Luiz Capitulino
2003-08-13 13:36 ` 2.6.0-test3-mm2 Luiz Capitulino
2003-08-13 14:32 ` 2.6.0-test3-mm2 Hugh Dickins
2003-08-13 14:32 ` 2.6.0-test3-mm2 Hugh Dickins
2003-08-13 16:16 ` 2.6.0-test3-mm2 Martin J. Bligh
2003-08-13 16:16 ` 2.6.0-test3-mm2 Martin J. Bligh
2003-08-13 16:18 ` 2.6.0-test3-mm2 Luiz Capitulino
2003-08-13 16:18 ` 2.6.0-test3-mm2 Luiz Capitulino
2003-08-15 19:38 ` Compile problem with CONFIG_X86_CYCLONE_TIMER 2.6.0-test3-mm2 Mike Fedyk
2003-08-15 19:38 ` Mike Fedyk
2003-08-15 20:23 ` Mike Fedyk
2003-08-15 20:23 ` Mike Fedyk
2003-08-15 20:36 ` Mike Fedyk
2003-08-15 20:36 ` Mike Fedyk
2003-08-16 20:32 ` Dave Hansen
2003-08-27 1:08 ` Compile problem with CONFIG_X86_CYCLONE_TIMER Re: 2.6.0-test4-mm1 Mike Fedyk
2003-08-27 1:08 ` Mike Fedyk
2003-08-27 4:41 ` Dave Hansen
2003-08-27 4:41 ` Dave Hansen
2003-08-27 16:00 ` Mike Fedyk
2003-08-27 16:00 ` Mike Fedyk
2003-08-27 16:15 ` Dave Hansen
2003-08-27 16:15 ` Dave Hansen
2003-08-17 20:37 ` 2.6.0-test3-mm2 Peter Osterlund
-- strict thread matches above, loose matches on Subject: below --
2003-08-13 13:45 2.6.0-test3-mm2 Andreas Mikkelborg
2003-08-14 2:23 ` 2.6.0-test3-mm2 G. Chris Hofmann
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=1060781719.449.6.camel@lorien \
--to=lcapitulino@prefeitura.sp.gov.br \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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.