Messages in this thread | | | Date | Thu, 17 Jul 2008 16:35:16 +0200 | From | "Vegard Nossum" <> | Subject | Re: ext3 on latest -git: BUG: unable to handle kernel NULL pointer dereference at 0000000c |
| |
On Thu, Jul 17, 2008 at 4:13 PM, Josef Bacik <jbacik@redhat.com> wrote: > On Thu, Jul 17, 2008 at 04:25:49PM +0200, Vegard Nossum wrote: >> On Thu, Jul 17, 2008 at 3:57 PM, Josef Bacik <jbacik@redhat.com> wrote: >> > Can you try this patch out and see if it fixes the problem? I didn't compile >> > test it, so you may need to tweak somethings, but it should work. Thanks, >> > >> > Signed-off-by: Josef Bacik <jbacik@redhat.com> >> >> Nope, seems to be the same problem: >> >> kjournald starting. Commit interval 5 seconds >> EXT3-fs warning: mounting fs with errors, running e2fsck is recommended >> EXT3 FS on loop0, internal journal >> EXT3-fs: mounted filesystem with ordered data mode. >> EXT3-fs error (device loop0): ext3_free_blocks: Freeing blocks in >> system zones - Block = 16, count = 1 >> EXT3-fs error (device loop0): ext3_free_blocks: Freeing blocks in >> system zones - Block = 32, count = 1 >> EXT3-fs error (device loop0): ext3_free_blocks: Freeing blocks not in >> datazone - block = 262144, count = 1 >> BUG: unable to handle kernel NULL pointer dereference at 0000000c >> IP: [<c01fd210>] journal_dirty_metadata+0xa0/0x160 >> >> Full log at http://folk.uio.no/vegardno/linux/log-1216304953.txt >> >> > > Ok, this should do it then. Thanks,
Hm, it doesn't apply. Should I revert the previous patch?
Vegard
-- "The animistic metaphor of the bug that maliciously sneaked in while the programmer was not looking is intellectually dishonest as it disguises that the error is the programmer's own creation." -- E. W. Dijkstra, EWD1036
| |