Re: 2.6.12-rc1-mm4 crash while mounting a reiserfs3 filesystem

2005-04-05 Thread Mathieu Bérard
Bartlomiej Zolnierkiewicz a écrit :
On Apr 3, 2005 11:56 PM, Andrew Morton <[EMAIL PROTECTED]> wrote:
Mathieu Bérard <[EMAIL PROTECTED]> wrote:
Hi,
I get a 100% reproductible oops while booting linux 2.6.12-rc1-mm4.
(Everyting run smoothly using 2.6.11-mm1)
It seems to be related with mounting a reiserfs3 filesystem.
It looks more like an IDE bug.

ReiserFS: hdg1: checking transaction log (hdg1)
Unable to handle kernel paging request at virtual address 0a373138
 printing eip:
df6d1211
*pde = 
Oops: 0002 [#1]
PREEMPT
Modules linked in: ext2 mbcache w83627hf i2c_sensor i2c_isa ppp_generic
slhc w83627hf_wdt msr cpuid
rtc
CPU:0
EIP:0060:[]Not tainted VLI
EFLAGS: 00010202   (2.6.12-rc1-mm4)
EIP is at 0xdf6d1211
eax: c9393266   ebx: df6d1c84   ecx: d84eab1e   edx: c155ccf8
esi: c039242c   edi: c039239c   ebp: 700d580a   esp: df6d1c80
ds: 007b   es: 007b   ss: 0068
Process mount (pid: 1132, threadinfo=df6d1000 task=df711a50)
Stack: c039242c c0229945 c039239c df6d1000 df6d1000 c039242c c155ccf8
c0223051
   0088 1388 c159ae28 df6d1000 c039242c c155ccf8 c039239c
c022333e
   df6d1d1c  c153d6e0 c155bd78  df6d1d1c c14007f0
c0212260
Call Trace:
 [] flagged_taskfile+0x125/0x380
 [] start_request+0x1f1/0x2a0
 [] ide_do_request+0x20e/0x3c0
 [] __generic_unplug_device+0x20/0x30
 [] generic_unplug_device+0x11/0x30
 [] blk_backing_dev_unplug+0xc/0x10
 [] sync_buffer+0x26/0x40
 [] __wait_on_bit+0x42/0x70
 [] sync_buffer+0x0/0x40
 [] sync_buffer+0x0/0x40
 [] out_of_line_wait_on_bit+0x7d/0x90
 [] wake_bit_function+0x0/0x60
 [] __wait_on_buffer+0x29/0x30
 [] _update_journal_header_block+0xf7/0x140
 [] journal_read+0x31d/0x470
 [] journal_init+0x4e1/0x650
 [] printk+0x1b/0x20
 [] reiserfs_fill_super+0x34d/0x770
 [] snprintf+0x20/0x30
 [] disk_name+0x96/0xf0
 [] get_sb_bdev+0xe5/0x130
 [] link_path_walk+0x65/0x140
 [] get_super_block+0x18/0x20
 [] reiserfs_fill_super+0x0/0x770
 [] do_kern_mount+0x44/0xf020 30 20 30 20 30 20 30 20 30 20
30 20 30 20 30 20 <1>general p
It appears that we might have jumped from flagged_taskfile into something
at 0xdf6d1211, which is rather odd.

It is very odd, we shouldn't hit flagged_taskfile() in the first 
place.  This function currently is executed only for special
HDIO_DRIVE_TASKFILE ioctl requests.

Whatever the explanation was, This oops is fixed in 2.6.12-rc2-mm1...
--
Mathieu Bérard
-
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/


Re: 2.6.12-rc1-mm4 crash while mounting a reiserfs3 filesystem

2005-04-05 Thread Bartlomiej Zolnierkiewicz
On Apr 3, 2005 11:56 PM, Andrew Morton <[EMAIL PROTECTED]> wrote:
> Mathieu Bérard <[EMAIL PROTECTED]> wrote:
> >
> > Hi,
> > I get a 100% reproductible oops while booting linux 2.6.12-rc1-mm4.
> > (Everyting run smoothly using 2.6.11-mm1)
> > It seems to be related with mounting a reiserfs3 filesystem.
> 
> It looks more like an IDE bug.
> 
> > ReiserFS: hdg1: checking transaction log (hdg1)
> > Unable to handle kernel paging request at virtual address 0a373138
> >   printing eip:
> > df6d1211
> > *pde = 
> > Oops: 0002 [#1]
> > PREEMPT
> > Modules linked in: ext2 mbcache w83627hf i2c_sensor i2c_isa ppp_generic
> > slhc w83627hf_wdt msr cpuid
> > rtc
> > CPU:0
> > EIP:0060:[]Not tainted VLI
> > EFLAGS: 00010202   (2.6.12-rc1-mm4)
> > EIP is at 0xdf6d1211
> > eax: c9393266   ebx: df6d1c84   ecx: d84eab1e   edx: c155ccf8
> > esi: c039242c   edi: c039239c   ebp: 700d580a   esp: df6d1c80
> > ds: 007b   es: 007b   ss: 0068
> > Process mount (pid: 1132, threadinfo=df6d1000 task=df711a50)
> > Stack: c039242c c0229945 c039239c df6d1000 df6d1000 c039242c c155ccf8
> > c0223051
> > 0088 1388 c159ae28 df6d1000 c039242c c155ccf8 c039239c
> > c022333e
> > df6d1d1c  c153d6e0 c155bd78  df6d1d1c c14007f0
> > c0212260
> > Call Trace:
> >   [] flagged_taskfile+0x125/0x380
> >   [] start_request+0x1f1/0x2a0
> >   [] ide_do_request+0x20e/0x3c0
> >   [] __generic_unplug_device+0x20/0x30
> >   [] generic_unplug_device+0x11/0x30
> >   [] blk_backing_dev_unplug+0xc/0x10
> >   [] sync_buffer+0x26/0x40
> >   [] __wait_on_bit+0x42/0x70
> >   [] sync_buffer+0x0/0x40
> >   [] sync_buffer+0x0/0x40
> >   [] out_of_line_wait_on_bit+0x7d/0x90
> >   [] wake_bit_function+0x0/0x60
> >   [] __wait_on_buffer+0x29/0x30
> >   [] _update_journal_header_block+0xf7/0x140
> >   [] journal_read+0x31d/0x470
> >   [] journal_init+0x4e1/0x650
> >   [] printk+0x1b/0x20
> >   [] reiserfs_fill_super+0x34d/0x770
> >   [] snprintf+0x20/0x30
> >   [] disk_name+0x96/0xf0
> >   [] get_sb_bdev+0xe5/0x130
> >   [] link_path_walk+0x65/0x140
> >   [] get_super_block+0x18/0x20
> >   [] reiserfs_fill_super+0x0/0x770
> >   [] do_kern_mount+0x44/0xf020 30 20 30 20 30 20 30 20 30 20
> > 30 20 30 20 30 20 <1>general p
> 
> It appears that we might have jumped from flagged_taskfile into something
> at 0xdf6d1211, which is rather odd.

It is very odd, we shouldn't hit flagged_taskfile() in the first 
place.  This function currently is executed only for special
HDIO_DRIVE_TASKFILE ioctl requests.
-
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/


Re: 2.6.12-rc1-mm4 crash while mounting a reiserfs3 filesystem

2005-04-05 Thread Mathieu Bérard
Bartlomiej Zolnierkiewicz a écrit :
On Apr 3, 2005 11:56 PM, Andrew Morton [EMAIL PROTECTED] wrote:
Mathieu Bérard [EMAIL PROTECTED] wrote:
Hi,
I get a 100% reproductible oops while booting linux 2.6.12-rc1-mm4.
(Everyting run smoothly using 2.6.11-mm1)
It seems to be related with mounting a reiserfs3 filesystem.
It looks more like an IDE bug.

ReiserFS: hdg1: checking transaction log (hdg1)
Unable to handle kernel paging request at virtual address 0a373138
 printing eip:
df6d1211
*pde = 
Oops: 0002 [#1]
PREEMPT
Modules linked in: ext2 mbcache w83627hf i2c_sensor i2c_isa ppp_generic
slhc w83627hf_wdt msr cpuid
rtc
CPU:0
EIP:0060:[df6d1211]Not tainted VLI
EFLAGS: 00010202   (2.6.12-rc1-mm4)
EIP is at 0xdf6d1211
eax: c9393266   ebx: df6d1c84   ecx: d84eab1e   edx: c155ccf8
esi: c039242c   edi: c039239c   ebp: 700d580a   esp: df6d1c80
ds: 007b   es: 007b   ss: 0068
Process mount (pid: 1132, threadinfo=df6d1000 task=df711a50)
Stack: c039242c c0229945 c039239c df6d1000 df6d1000 c039242c c155ccf8
c0223051
   0088 1388 c159ae28 df6d1000 c039242c c155ccf8 c039239c
c022333e
   df6d1d1c  c153d6e0 c155bd78  df6d1d1c c14007f0
c0212260
Call Trace:
 [c0229945] flagged_taskfile+0x125/0x380
 [c0223051] start_request+0x1f1/0x2a0
 [c022333e] ide_do_request+0x20e/0x3c0
 [c0212260] __generic_unplug_device+0x20/0x30
 [c0212281] generic_unplug_device+0x11/0x30
 [c02122ac] blk_backing_dev_unplug+0xc/0x10
 [c0156336] sync_buffer+0x26/0x40
 [c02a0b22] __wait_on_bit+0x42/0x70
 [c0156310] sync_buffer+0x0/0x40
 [c0156310] sync_buffer+0x0/0x40
 [c02a0bcd] out_of_line_wait_on_bit+0x7d/0x90
 [c012bf80] wake_bit_function+0x0/0x60
 [c01563c9] __wait_on_buffer+0x29/0x30
 [c01b0dd7] _update_journal_header_block+0xf7/0x140
 [c01b290d] journal_read+0x31d/0x470
 [c01b3241] journal_init+0x4e1/0x650
 [c011748b] printk+0x1b/0x20
 [c01a3ced] reiserfs_fill_super+0x34d/0x770
 [c01c9470] snprintf+0x20/0x30
 [c0189ab6] disk_name+0x96/0xf0
 [c015bf75] get_sb_bdev+0xe5/0x130
 [c0163945] link_path_walk+0x65/0x140
 [c01a4168] get_super_block+0x18/0x20
 [c01a39a0] reiserfs_fill_super+0x0/0x770
 [c015c194] do_kern_mount+0x44/0xf020 30 20 30 20 30 20 30 20 30 20
30 20 30 20 30 20 1general p
It appears that we might have jumped from flagged_taskfile into something
at 0xdf6d1211, which is rather odd.

It is very odd, we shouldn't hit flagged_taskfile() in the first 
place.  This function currently is executed only for special
HDIO_DRIVE_TASKFILE ioctl requests.

Whatever the explanation was, This oops is fixed in 2.6.12-rc2-mm1...
--
Mathieu Bérard
-
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/


Re: 2.6.12-rc1-mm4 crash while mounting a reiserfs3 filesystem

2005-04-05 Thread Bartlomiej Zolnierkiewicz
On Apr 3, 2005 11:56 PM, Andrew Morton [EMAIL PROTECTED] wrote:
 Mathieu Bérard [EMAIL PROTECTED] wrote:
 
  Hi,
  I get a 100% reproductible oops while booting linux 2.6.12-rc1-mm4.
  (Everyting run smoothly using 2.6.11-mm1)
  It seems to be related with mounting a reiserfs3 filesystem.
 
 It looks more like an IDE bug.
 
  ReiserFS: hdg1: checking transaction log (hdg1)
  Unable to handle kernel paging request at virtual address 0a373138
printing eip:
  df6d1211
  *pde = 
  Oops: 0002 [#1]
  PREEMPT
  Modules linked in: ext2 mbcache w83627hf i2c_sensor i2c_isa ppp_generic
  slhc w83627hf_wdt msr cpuid
  rtc
  CPU:0
  EIP:0060:[df6d1211]Not tainted VLI
  EFLAGS: 00010202   (2.6.12-rc1-mm4)
  EIP is at 0xdf6d1211
  eax: c9393266   ebx: df6d1c84   ecx: d84eab1e   edx: c155ccf8
  esi: c039242c   edi: c039239c   ebp: 700d580a   esp: df6d1c80
  ds: 007b   es: 007b   ss: 0068
  Process mount (pid: 1132, threadinfo=df6d1000 task=df711a50)
  Stack: c039242c c0229945 c039239c df6d1000 df6d1000 c039242c c155ccf8
  c0223051
  0088 1388 c159ae28 df6d1000 c039242c c155ccf8 c039239c
  c022333e
  df6d1d1c  c153d6e0 c155bd78  df6d1d1c c14007f0
  c0212260
  Call Trace:
[c0229945] flagged_taskfile+0x125/0x380
[c0223051] start_request+0x1f1/0x2a0
[c022333e] ide_do_request+0x20e/0x3c0
[c0212260] __generic_unplug_device+0x20/0x30
[c0212281] generic_unplug_device+0x11/0x30
[c02122ac] blk_backing_dev_unplug+0xc/0x10
[c0156336] sync_buffer+0x26/0x40
[c02a0b22] __wait_on_bit+0x42/0x70
[c0156310] sync_buffer+0x0/0x40
[c0156310] sync_buffer+0x0/0x40
[c02a0bcd] out_of_line_wait_on_bit+0x7d/0x90
[c012bf80] wake_bit_function+0x0/0x60
[c01563c9] __wait_on_buffer+0x29/0x30
[c01b0dd7] _update_journal_header_block+0xf7/0x140
[c01b290d] journal_read+0x31d/0x470
[c01b3241] journal_init+0x4e1/0x650
[c011748b] printk+0x1b/0x20
[c01a3ced] reiserfs_fill_super+0x34d/0x770
[c01c9470] snprintf+0x20/0x30
[c0189ab6] disk_name+0x96/0xf0
[c015bf75] get_sb_bdev+0xe5/0x130
[c0163945] link_path_walk+0x65/0x140
[c01a4168] get_super_block+0x18/0x20
[c01a39a0] reiserfs_fill_super+0x0/0x770
[c015c194] do_kern_mount+0x44/0xf020 30 20 30 20 30 20 30 20 30 20
  30 20 30 20 30 20 1general p
 
 It appears that we might have jumped from flagged_taskfile into something
 at 0xdf6d1211, which is rather odd.

It is very odd, we shouldn't hit flagged_taskfile() in the first 
place.  This function currently is executed only for special
HDIO_DRIVE_TASKFILE ioctl requests.
-
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/


Re: 2.6.12-rc1-mm4 crash while mounting a reiserfs3 filesystem

2005-04-03 Thread Mathieu Bérard
Andrew Morton a écrit :

It appears that we might have jumped from flagged_taskfile into something
at 0xdf6d1211, which is rather odd.
You have two different low-level IDE drivers configured.  Which one is
driving that filesystem?  VIA or Promise?
hdg is connected to my Promise PDC20268 (Ultra100 TX2)
--
Mathieu Bérard
-
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/


Re: 2.6.12-rc1-mm4 crash while mounting a reiserfs3 filesystem

2005-04-03 Thread Andrew Morton
Mathieu Bérard <[EMAIL PROTECTED]> wrote:
>
> Hi,
> I get a 100% reproductible oops while booting linux 2.6.12-rc1-mm4.
> (Everyting run smoothly using 2.6.11-mm1)
> It seems to be related with mounting a reiserfs3 filesystem.

It looks more like an IDE bug.

> ReiserFS: hdg1: checking transaction log (hdg1)
> Unable to handle kernel paging request at virtual address 0a373138
>   printing eip:
> df6d1211
> *pde = 
> Oops: 0002 [#1]
> PREEMPT
> Modules linked in: ext2 mbcache w83627hf i2c_sensor i2c_isa ppp_generic 
> slhc w83627hf_wdt msr cpuid
> rtc
> CPU:0
> EIP:0060:[]Not tainted VLI
> EFLAGS: 00010202   (2.6.12-rc1-mm4)
> EIP is at 0xdf6d1211
> eax: c9393266   ebx: df6d1c84   ecx: d84eab1e   edx: c155ccf8
> esi: c039242c   edi: c039239c   ebp: 700d580a   esp: df6d1c80
> ds: 007b   es: 007b   ss: 0068
> Process mount (pid: 1132, threadinfo=df6d1000 task=df711a50)
> Stack: c039242c c0229945 c039239c df6d1000 df6d1000 c039242c c155ccf8 
> c0223051
> 0088 1388 c159ae28 df6d1000 c039242c c155ccf8 c039239c 
> c022333e
> df6d1d1c  c153d6e0 c155bd78  df6d1d1c c14007f0 
> c0212260
> Call Trace:
>   [] flagged_taskfile+0x125/0x380
>   [] start_request+0x1f1/0x2a0
>   [] ide_do_request+0x20e/0x3c0
>   [] __generic_unplug_device+0x20/0x30
>   [] generic_unplug_device+0x11/0x30
>   [] blk_backing_dev_unplug+0xc/0x10
>   [] sync_buffer+0x26/0x40
>   [] __wait_on_bit+0x42/0x70
>   [] sync_buffer+0x0/0x40
>   [] sync_buffer+0x0/0x40
>   [] out_of_line_wait_on_bit+0x7d/0x90
>   [] wake_bit_function+0x0/0x60
>   [] __wait_on_buffer+0x29/0x30
>   [] _update_journal_header_block+0xf7/0x140
>   [] journal_read+0x31d/0x470
>   [] journal_init+0x4e1/0x650
>   [] printk+0x1b/0x20
>   [] reiserfs_fill_super+0x34d/0x770
>   [] snprintf+0x20/0x30
>   [] disk_name+0x96/0xf0
>   [] get_sb_bdev+0xe5/0x130
>   [] link_path_walk+0x65/0x140
>   [] get_super_block+0x18/0x20
>   [] reiserfs_fill_super+0x0/0x770
>   [] do_kern_mount+0x44/0xf020 30 20 30 20 30 20 30 20 30 20 
> 30 20 30 20 30 20 <1>general p

It appears that we might have jumped from flagged_taskfile into something
at 0xdf6d1211, which is rather odd.

You have two different low-level IDE drivers configured.  Which one is
driving that filesystem?  VIA or Promise?
-
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/


2.6.12-rc1-mm4 crash while mounting a reiserfs3 filesystem

2005-04-03 Thread Mathieu Bérard
Hi,
I get a 100% reproductible oops while booting linux 2.6.12-rc1-mm4.
(Everyting run smoothly using 2.6.11-mm1)
It seems to be related with mounting a reiserfs3 filesystem.
Please also note that this kernel was compiled using gcc-4.0-0pre9
(from Debian)
I'm using mount 2.12p
Please CC: me.
Here the OOPs (netconsole captured):
input: AT Translated Set 2 keyboard on isa0060/serio0
ReiserFS: hda5: using ordered data mode
ReiserFS: hda5: journal params: device hda5, size 8192, journal first 
block 18, max trans len 1024,
max batch 900, max commit age 30, max trans age 30
ReiserFS: hda5: checking transaction log (hda5)
ReiserFS: hda5: Using r5 hash to sort names
VFS: Mounted root (reiserfs filesystem) readonly.
Freeing unused kernel memory: 136k freed
Adding 497972k swap on /dev/hda6.  Priority:-1 extents:1
reiserfs: enabling write barrier flush mode
reiserfs: disabling flush barriers on hda5
Real Time Clock Driver v1.12
WDT driver for the Winbond(TM) W83627HF Super I/O chip initialising.
w83627hf WDT: initialized. timeout=60 sec (nowayout=0)
CSLIP: code copyright 1989 Regents of the University of California
PPP generic driver version 2.4.2
ACPI: No ACPI bus support for 0-0290
ReiserFS: hda7: found reiserfs format "3.6" with standard journal
ReiserFS: hda7: using ordered data mode
reiserfs: using flush barriers
ReiserFS: hda7: journal params: device hda7, size 8192, journal first 
block 18, max trans len 1024,
max batch 900, max commit age 30, max trans age 30
ReiserFS: hda7: checking transaction log (hda7)
reiserfs: disabling flush barriers on hda7
ReiserFS: hda7: Using r5 hash to sort names
ReiserFS: hda8: found reiserfs format "3.6" with standard journal
ReiserFS: hda8: using ordered data mode
reiserfs: using flush barriers
ReiserFS: hda8: journal params: device hda8, size 8192, journal first 
block 18, max trans len 1024,
max batch 900, max commit age 30, max trans age 30
ReiserFS: hda8: checking transaction log (hda8)
reiserfs: disabling flush barriers on hda8
ReiserFS: hda8: Using r5 hash to sort names
ReiserFS: hdg1: found reiserfs format "3.6" with standard journal
ReiserFS: hdg1: using ordered data mode
reiserfs: using flush barriers
ReiserFS: hdg1: journal params: device hdg1, size 8192, journal first 
block 18, max trans len 1024,
max batch 900, max commit age 30, max trans age 30
ReiserFS: hdg1: checking transaction log (hdg1)
Unable to handle kernel paging request at virtual address 0a373138
 printing eip:
df6d1211
*pde = 
Oops: 0002 [#1]
PREEMPT
Modules linked in: ext2 mbcache w83627hf i2c_sensor i2c_isa ppp_generic 
slhc w83627hf_wdt msr cpuid
rtc
CPU:0
EIP:0060:[]Not tainted VLI
EFLAGS: 00010202   (2.6.12-rc1-mm4)
EIP is at 0xdf6d1211
eax: c9393266   ebx: df6d1c84   ecx: d84eab1e   edx: c155ccf8
esi: c039242c   edi: c039239c   ebp: 700d580a   esp: df6d1c80
ds: 007b   es: 007b   ss: 0068
Process mount (pid: 1132, threadinfo=df6d1000 task=df711a50)
Stack: c039242c c0229945 c039239c df6d1000 df6d1000 c039242c c155ccf8 
c0223051
   0088 1388 c159ae28 df6d1000 c039242c c155ccf8 c039239c 
c022333e
   df6d1d1c  c153d6e0 c155bd78  df6d1d1c c14007f0 
c0212260
Call Trace:
 [] flagged_taskfile+0x125/0x380
 [] start_request+0x1f1/0x2a0
 [] ide_do_request+0x20e/0x3c0
 [] __generic_unplug_device+0x20/0x30
 [] generic_unplug_device+0x11/0x30
 [] blk_backing_dev_unplug+0xc/0x10
 [] sync_buffer+0x26/0x40
 [] __wait_on_bit+0x42/0x70
 [] sync_buffer+0x0/0x40
 [] sync_buffer+0x0/0x40
 [] out_of_line_wait_on_bit+0x7d/0x90
 [] wake_bit_function+0x0/0x60
 [] __wait_on_buffer+0x29/0x30
 [] _update_journal_header_block+0xf7/0x140
 [] journal_read+0x31d/0x470
 [] journal_init+0x4e1/0x650
 [] printk+0x1b/0x20
 [] reiserfs_fill_super+0x34d/0x770
 [] snprintf+0x20/0x30
 [] disk_name+0x96/0xf0
 [] get_sb_bdev+0xe5/0x130
 [] link_path_walk+0x65/0x140
 [] get_super_block+0x18/0x20
 [] reiserfs_fill_super+0x0/0x770
 [] do_kern_mount+0x44/0xf020 30 20 30 20 30 20 30 20 30 20 
30 20 30 20 30 20 <1>general p
rotection fault:  [#2]
PREEMPT
Modules linked in: ext2 mbcache w83627hf i2c_sensor i2c_isa ppp_generic 
slhc w83627hf_wdt msr cpuid
rtc
CPU:0
EIP:0060:[]Not tainted VLI
EFLAGS: 00010012   (2.6.12-rc1-mm4)
EIP is at 0xdf6d1dae
eax: df6d1d54   ebx: df6d1d1c   ecx:    edx: 0003
esi: df62190c   edi:    ebp: df7a3e80   esp: df7a3e60
ds: 007b   es: 007b   ss: 0068
Process fsck.reiserfs (pid: 1126, threadinfo=df7a3000 task=df711030)
Stack: c0113849 df7a3ea8 0001 0003 c14007f0 df7a3000 df7a3ea8 
0286
   df7a3e9c c011389f  df7a3ea8 c14007f0 c138be00 dfd36330 
da0db42c
   c012c00a df7a3ea8 c138be00  0001 c0145b47 0054 
000f
Call Trace:
 [] __wake_up_common+0x39/0x60
 [] __wake_up+0x2f/0x60
 [] __wake_up_bit+0x2a/0x30
 [] do_wp_page+0x1e7/0x340
 [] handle_mm_fault+0x184/0x1c0
 [] do_page_fault+0x268/0x657
 [] free_pgtables+0x82/0xb0
 [] unmap_region+0xb2/0x120
 [] unmap_vma_list+0xe/0x20
 [] 

2.6.12-rc1-mm4 crash while mounting a reiserfs3 filesystem

2005-04-03 Thread Mathieu Brard
Hi,
I get a 100% reproductible oops while booting linux 2.6.12-rc1-mm4.
(Everyting run smoothly using 2.6.11-mm1)
It seems to be related with mounting a reiserfs3 filesystem.
Please also note that this kernel was compiled using gcc-4.0-0pre9
(from Debian)
I'm using mount 2.12p
Please CC: me.
Here the OOPs (netconsole captured):
input: AT Translated Set 2 keyboard on isa0060/serio0
ReiserFS: hda5: using ordered data mode
ReiserFS: hda5: journal params: device hda5, size 8192, journal first 
block 18, max trans len 1024,
max batch 900, max commit age 30, max trans age 30
ReiserFS: hda5: checking transaction log (hda5)
ReiserFS: hda5: Using r5 hash to sort names
VFS: Mounted root (reiserfs filesystem) readonly.
Freeing unused kernel memory: 136k freed
Adding 497972k swap on /dev/hda6.  Priority:-1 extents:1
reiserfs: enabling write barrier flush mode
reiserfs: disabling flush barriers on hda5
Real Time Clock Driver v1.12
WDT driver for the Winbond(TM) W83627HF Super I/O chip initialising.
w83627hf WDT: initialized. timeout=60 sec (nowayout=0)
CSLIP: code copyright 1989 Regents of the University of California
PPP generic driver version 2.4.2
ACPI: No ACPI bus support for 0-0290
ReiserFS: hda7: found reiserfs format 3.6 with standard journal
ReiserFS: hda7: using ordered data mode
reiserfs: using flush barriers
ReiserFS: hda7: journal params: device hda7, size 8192, journal first 
block 18, max trans len 1024,
max batch 900, max commit age 30, max trans age 30
ReiserFS: hda7: checking transaction log (hda7)
reiserfs: disabling flush barriers on hda7
ReiserFS: hda7: Using r5 hash to sort names
ReiserFS: hda8: found reiserfs format 3.6 with standard journal
ReiserFS: hda8: using ordered data mode
reiserfs: using flush barriers
ReiserFS: hda8: journal params: device hda8, size 8192, journal first 
block 18, max trans len 1024,
max batch 900, max commit age 30, max trans age 30
ReiserFS: hda8: checking transaction log (hda8)
reiserfs: disabling flush barriers on hda8
ReiserFS: hda8: Using r5 hash to sort names
ReiserFS: hdg1: found reiserfs format 3.6 with standard journal
ReiserFS: hdg1: using ordered data mode
reiserfs: using flush barriers
ReiserFS: hdg1: journal params: device hdg1, size 8192, journal first 
block 18, max trans len 1024,
max batch 900, max commit age 30, max trans age 30
ReiserFS: hdg1: checking transaction log (hdg1)
Unable to handle kernel paging request at virtual address 0a373138
 printing eip:
df6d1211
*pde = 
Oops: 0002 [#1]
PREEMPT
Modules linked in: ext2 mbcache w83627hf i2c_sensor i2c_isa ppp_generic 
slhc w83627hf_wdt msr cpuid
rtc
CPU:0
EIP:0060:[df6d1211]Not tainted VLI
EFLAGS: 00010202   (2.6.12-rc1-mm4)
EIP is at 0xdf6d1211
eax: c9393266   ebx: df6d1c84   ecx: d84eab1e   edx: c155ccf8
esi: c039242c   edi: c039239c   ebp: 700d580a   esp: df6d1c80
ds: 007b   es: 007b   ss: 0068
Process mount (pid: 1132, threadinfo=df6d1000 task=df711a50)
Stack: c039242c c0229945 c039239c df6d1000 df6d1000 c039242c c155ccf8 
c0223051
   0088 1388 c159ae28 df6d1000 c039242c c155ccf8 c039239c 
c022333e
   df6d1d1c  c153d6e0 c155bd78  df6d1d1c c14007f0 
c0212260
Call Trace:
 [c0229945] flagged_taskfile+0x125/0x380
 [c0223051] start_request+0x1f1/0x2a0
 [c022333e] ide_do_request+0x20e/0x3c0
 [c0212260] __generic_unplug_device+0x20/0x30
 [c0212281] generic_unplug_device+0x11/0x30
 [c02122ac] blk_backing_dev_unplug+0xc/0x10
 [c0156336] sync_buffer+0x26/0x40
 [c02a0b22] __wait_on_bit+0x42/0x70
 [c0156310] sync_buffer+0x0/0x40
 [c0156310] sync_buffer+0x0/0x40
 [c02a0bcd] out_of_line_wait_on_bit+0x7d/0x90
 [c012bf80] wake_bit_function+0x0/0x60
 [c01563c9] __wait_on_buffer+0x29/0x30
 [c01b0dd7] _update_journal_header_block+0xf7/0x140
 [c01b290d] journal_read+0x31d/0x470
 [c01b3241] journal_init+0x4e1/0x650
 [c011748b] printk+0x1b/0x20
 [c01a3ced] reiserfs_fill_super+0x34d/0x770
 [c01c9470] snprintf+0x20/0x30
 [c0189ab6] disk_name+0x96/0xf0
 [c015bf75] get_sb_bdev+0xe5/0x130
 [c0163945] link_path_walk+0x65/0x140
 [c01a4168] get_super_block+0x18/0x20
 [c01a39a0] reiserfs_fill_super+0x0/0x770
 [c015c194] do_kern_mount+0x44/0xf020 30 20 30 20 30 20 30 20 30 20 
30 20 30 20 30 20 1general p
rotection fault:  [#2]
PREEMPT
Modules linked in: ext2 mbcache w83627hf i2c_sensor i2c_isa ppp_generic 
slhc w83627hf_wdt msr cpuid
rtc
CPU:0
EIP:0060:[df6d1dae]Not tainted VLI
EFLAGS: 00010012   (2.6.12-rc1-mm4)
EIP is at 0xdf6d1dae
eax: df6d1d54   ebx: df6d1d1c   ecx:    edx: 0003
esi: df62190c   edi:    ebp: df7a3e80   esp: df7a3e60
ds: 007b   es: 007b   ss: 0068
Process fsck.reiserfs (pid: 1126, threadinfo=df7a3000 task=df711030)
Stack: c0113849 df7a3ea8 0001 0003 c14007f0 df7a3000 df7a3ea8 
0286
   df7a3e9c c011389f  df7a3ea8 c14007f0 c138be00 dfd36330 
da0db42c
   c012c00a df7a3ea8 c138be00  0001 c0145b47 0054 
000f
Call Trace:
 [c0113849] __wake_up_common+0x39/0x60
 [c011389f] 

Re: 2.6.12-rc1-mm4 crash while mounting a reiserfs3 filesystem

2005-04-03 Thread Andrew Morton
Mathieu Bérard [EMAIL PROTECTED] wrote:

 Hi,
 I get a 100% reproductible oops while booting linux 2.6.12-rc1-mm4.
 (Everyting run smoothly using 2.6.11-mm1)
 It seems to be related with mounting a reiserfs3 filesystem.

It looks more like an IDE bug.

 ReiserFS: hdg1: checking transaction log (hdg1)
 Unable to handle kernel paging request at virtual address 0a373138
   printing eip:
 df6d1211
 *pde = 
 Oops: 0002 [#1]
 PREEMPT
 Modules linked in: ext2 mbcache w83627hf i2c_sensor i2c_isa ppp_generic 
 slhc w83627hf_wdt msr cpuid
 rtc
 CPU:0
 EIP:0060:[df6d1211]Not tainted VLI
 EFLAGS: 00010202   (2.6.12-rc1-mm4)
 EIP is at 0xdf6d1211
 eax: c9393266   ebx: df6d1c84   ecx: d84eab1e   edx: c155ccf8
 esi: c039242c   edi: c039239c   ebp: 700d580a   esp: df6d1c80
 ds: 007b   es: 007b   ss: 0068
 Process mount (pid: 1132, threadinfo=df6d1000 task=df711a50)
 Stack: c039242c c0229945 c039239c df6d1000 df6d1000 c039242c c155ccf8 
 c0223051
 0088 1388 c159ae28 df6d1000 c039242c c155ccf8 c039239c 
 c022333e
 df6d1d1c  c153d6e0 c155bd78  df6d1d1c c14007f0 
 c0212260
 Call Trace:
   [c0229945] flagged_taskfile+0x125/0x380
   [c0223051] start_request+0x1f1/0x2a0
   [c022333e] ide_do_request+0x20e/0x3c0
   [c0212260] __generic_unplug_device+0x20/0x30
   [c0212281] generic_unplug_device+0x11/0x30
   [c02122ac] blk_backing_dev_unplug+0xc/0x10
   [c0156336] sync_buffer+0x26/0x40
   [c02a0b22] __wait_on_bit+0x42/0x70
   [c0156310] sync_buffer+0x0/0x40
   [c0156310] sync_buffer+0x0/0x40
   [c02a0bcd] out_of_line_wait_on_bit+0x7d/0x90
   [c012bf80] wake_bit_function+0x0/0x60
   [c01563c9] __wait_on_buffer+0x29/0x30
   [c01b0dd7] _update_journal_header_block+0xf7/0x140
   [c01b290d] journal_read+0x31d/0x470
   [c01b3241] journal_init+0x4e1/0x650
   [c011748b] printk+0x1b/0x20
   [c01a3ced] reiserfs_fill_super+0x34d/0x770
   [c01c9470] snprintf+0x20/0x30
   [c0189ab6] disk_name+0x96/0xf0
   [c015bf75] get_sb_bdev+0xe5/0x130
   [c0163945] link_path_walk+0x65/0x140
   [c01a4168] get_super_block+0x18/0x20
   [c01a39a0] reiserfs_fill_super+0x0/0x770
   [c015c194] do_kern_mount+0x44/0xf020 30 20 30 20 30 20 30 20 30 20 
 30 20 30 20 30 20 1general p

It appears that we might have jumped from flagged_taskfile into something
at 0xdf6d1211, which is rather odd.

You have two different low-level IDE drivers configured.  Which one is
driving that filesystem?  VIA or Promise?
-
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/


Re: 2.6.12-rc1-mm4 crash while mounting a reiserfs3 filesystem

2005-04-03 Thread Mathieu Bérard
Andrew Morton a écrit :

It appears that we might have jumped from flagged_taskfile into something
at 0xdf6d1211, which is rather odd.
You have two different low-level IDE drivers configured.  Which one is
driving that filesystem?  VIA or Promise?
hdg is connected to my Promise PDC20268 (Ultra100 TX2)
--
Mathieu Bérard
-
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/