Hi there,
i got a 'Opss' on my PII (one of my fileservers) just changing the
kernel version from 2.5.5 to .6
The problem is got just in the first fsck (of a ReiserFS fs) on boot-time.
This fsck is done to /dev/sda1 so raid1->ReiserFS is not the problem (its
just on the second place of the partitions to mount).
Any ideas?
Thanks by advance and sorry by the pour english.
THE BOOT Oops! ---------------------------------------- (just a
segmentation fault)
----------------------------------------------------------------------------------------------------------------
found reiserfs format "3.6" with standard journal
Unable to handle kernel NULL pointer dereference at virtual address 00000010
printing eip:
c012c79e
*pde = 00000000
Oops: 0000
CPU: 0
EIP: 0010:[<c012c79e>] Not tainted
EFLAGS: 00010286
eax: 00001000 ebx: 0000000d ecx: 00000007 edx: 00002012
esi: 00000007 edi: 00002012 ebp: 00000000 esp: c7a9bd90
ds: 0018 es: 0018 ss: 0018
Process mount (pid: 88, threadinfo=c7a9a000 task=c7bd0bc0)
Stack: 00001000 00002012 00000000 c7a1f000 c0123bdb c012cc8b 00000000 00002012
00001000 c7a1f000 c8852000 c88633ec c012ce5f 00000000 00002012
00001000
c7a1f000 c0178e86 00000000 00002012 00001000 00000301 00000000
c7a1f154
Call Trace: [<c0123bdb>] [<c012cc8b>] [<c012ce5f>] [<c0178e86>] [<c012c130>]
[<c016b568>] [<c016be2c>] [<c0181c6c>] [<c013006a>] [<c011d7a7>]
[<c016c20f>]
[<c016bd08>] [<c0130220>] [<c013eb09>] [<c013ede0>] [<c013ec24>]
[<c013f164>]
[<c0106cff>]
Code: 0f b7 45 10 b0 00 66 0f b6 55 10 01 d0 0f b7 c0 89 44 24 10
<6>
--------------------------------------------------------------------------------------
[email protected] wrote:
>
> Hi there,
>
> i got a 'Opss' on my PII (one of my fileservers) just changing the
> kernel version from 2.5.5 to .6
Reiserfs in linux >= 2.5.6-pre3 does have broken stuff in journal area due to vfs cleanups.
Please wait, or apply this:
--- linux-2.5.6-pre3/fs/reiserfs/journal.c.orig Thu Mar 7 12:44:43 2002
+++ linux-2.5.6-pre3/fs/reiserfs/journal.c Thu Mar 7 13:53:36 2002
@@ -1960,8 +1960,7 @@
SB_ONDISK_JOURNAL_DEVICE( super ) ?
to_kdev_t(SB_ONDISK_JOURNAL_DEVICE( super )) : super -> s_dev;
/* there is no "jdev" option and journal is on separate device */
- if( ( !jdev_name || !jdev_name[ 0 ] ) &&
- SB_ONDISK_JOURNAL_DEVICE( super ) ) {
+ if( ( !jdev_name || !jdev_name[ 0 ] ) ) {
journal -> j_dev_bd = bdget( kdev_t_to_nr( jdev ) );
if( journal -> j_dev_bd )
result = blkdev_get( journal -> j_dev_bd,
@@ -1976,9 +1975,6 @@
return result;
}
- /* no "jdev" option and journal is on the host device */
- if( !jdev_name || !jdev_name[ 0 ] )
- return 0;
journal -> j_dev_file = filp_open( jdev_name, 0, 0 );
if( !IS_ERR( journal -> j_dev_file ) ) {
struct inode *jdev_inode;
Thanks,
Edward
Thanks Edward.
I'll apply and let me inform u about result ( just like a beta-tester )
At 21:22 10/03/2002 +0000, Edward Shushkin wrote:
>[email protected] wrote:
> >
> > Hi there,
> >
> > i got a 'Opss' on my PII (one of my fileservers) just changing the
> > kernel version from 2.5.5 to .6
>
>Reiserfs in linux >= 2.5.6-pre3 does have broken stuff in journal area due
>to vfs cleanups.
>Please wait, or apply this:
>
>--- linux-2.5.6-pre3/fs/reiserfs/journal.c.orig Thu Mar 7 12:44:43 2002
>+++ linux-2.5.6-pre3/fs/reiserfs/journal.c Thu Mar 7 13:53:36 2002
>@@ -1960,8 +1960,7 @@
> SB_ONDISK_JOURNAL_DEVICE( super ) ?
> to_kdev_t(SB_ONDISK_JOURNAL_DEVICE( super )) : super ->
> s_dev;
> /* there is no "jdev" option and journal is on separate device */
>- if( ( !jdev_name || !jdev_name[ 0 ] ) &&
>- SB_ONDISK_JOURNAL_DEVICE( super ) ) {
>+ if( ( !jdev_name || !jdev_name[ 0 ] ) ) {
> journal -> j_dev_bd = bdget( kdev_t_to_nr( jdev ) );
> if( journal -> j_dev_bd )
> result = blkdev_get( journal -> j_dev_bd,
>@@ -1976,9 +1975,6 @@
> return result;
> }
>
>- /* no "jdev" option and journal is on the host device */
>- if( !jdev_name || !jdev_name[ 0 ] )
>- return 0;
> journal -> j_dev_file = filp_open( jdev_name, 0, 0 );
> if( !IS_ERR( journal -> j_dev_file ) ) {
> struct inode *jdev_inode;
>
>
>Thanks,
>Edward
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to [email protected]
>More majordomo info at http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at http://www.tux.org/lkml/
Hello!
On Sun, Mar 10, 2002 at 07:37:22PM +0100, [email protected] wrote:
> I'll apply and let me inform u about result ( just like a beta-tester )
Can we also ask you to decode your oopses
(as described in /usr/src/linux/Documentation/oops-tracing.txt)
This is absolute requirement if you want unknown bugs you are hitting to
be resolved.
Luckily this bug was already known, so we was able to provide a patch
without the decoded oops, but this is not always the case.
Bye,
Oleg