* kernel BUG() hit during PCI testing
@ 2005-05-09 22:23 Linas Vepstas
2005-05-10 16:25 ` Jeff Mahoney
0 siblings, 1 reply; 4+ messages in thread
From: Linas Vepstas @ 2005-05-09 22:23 UTC (permalink / raw)
To: reiserfs-dev, reiserfs-list
Hi,
I just hit a kernel BUG() during pci testing of 2.6.11.8. The goal of
the testing was to temporarily disable a PCI slot containing a SCSI controller.
I think I permanently killed the PCI slot; i/o died, and shortly after
I hit the BUG(). See below.
The goal is, of course, to have the kernel keep on trooping even if
the SCSI controller dies out from under it; returning -EIO to user apps
accessing the failed file system is acceptable.
--linas
io-falcons:~ # dmesg
-bash: /bin/dmesg: Input/output error
(Above is the "normal" message when a file system returns -EIO to user space;
I expect to see these kinds of messages if the block device under the
file system fails. Then, a second later I got the crash:
io-falcons:~ #
io-falcons:~ #
io-falcons:~ # cpu 0x0: Vector: 700 (Program Check) at [c0000001ffe73740]
pc: c000000000138b48: .write_ordered_chunk+0xa4/0x100
lr: c0000000001392f4: .write_ordered_buffers+0x348/0x364
sp: c0000001ffe739c0
msr: 9000000000029032
current = 0xc0000003fe6d5030
paca = 0xc000000000547000
pid = 942, comm = reiserfs/0
kernel BUG in submit_ordered_buffer at fs/reiserfs/journal.c:616!
enter ? for help
0:mon>
0:mon> t
[c0000001ffe73a60] c0000000001392f4 .write_ordered_buffers+0x348/0x364
[c0000001ffe73c30] c000000000139b70 .flush_commit_list+0x80c/0x8cc
[c0000001ffe73d10] c00000000013eb40 .flush_async_commits+0xf0/0xf4
[c0000001ffe73db0] c00000000006f5dc .worker_thread+0x258/0x32c
[c0000001ffe73ee0] c000000000076060 .kthread+0x174/0x1c8
[c0000001ffe73f90] c000000000014388 .kernel_thread+0x4c/0x6c
0:mon> r
R00 = 000000000000001c R16 = 0000000000000000
R01 = c0000001ffe739c0 R17 = 0000000000000000
R02 = c0000000007017e8 R18 = 0000000003a10000
R03 = c0000001ffe73ad0 R19 = 0000000003edf020
R04 = c0000001f4031a78 R20 = 0000000000000000
R05 = d000000000080168 R21 = d000000000080000
R06 = c0000000006cf2a8 R22 = c0000003f8ca3aa8
R07 = 0000000000000000 R23 = 00000000000982f1
R08 = c0000003f8ca3b28 R24 = fffffffffffffffb
R09 = 0000000000000000 R25 = c0000001ffe73be0
R10 = c0000003f8ca3b28 R26 = c0000000006cf218
R11 = 0000000000000000 R27 = c0000001ffe73ad0
R12 = 0000000044044022 R28 = 0000000000000000
R13 = c000000000547000 R29 = 0000000000000002
R14 = 0000000000000000 R30 = c000000000594018
R15 = 0000000000000000 R31 = c0000001ffe739c0
pc = c000000000138b48 .write_ordered_chunk+0xa4/0x100
lr = c0000000001392f4 .write_ordered_buffers+0x348/0x364
msr = 9000000000029032 cr = 24044024
ctr = c00000000013ea50 xer = 000000000000ff7f trap = 700
0:mon>
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: kernel BUG() hit during PCI testing
2005-05-09 22:23 kernel BUG() hit during PCI testing Linas Vepstas
@ 2005-05-10 16:25 ` Jeff Mahoney
2005-05-10 17:34 ` Linas Vepstas
0 siblings, 1 reply; 4+ messages in thread
From: Jeff Mahoney @ 2005-05-10 16:25 UTC (permalink / raw)
To: Linas Vepstas; +Cc: reiserfs-dev, reiserfs-list
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Linas Vepstas wrote:
>
>
> Hi,
>
> I just hit a kernel BUG() during pci testing of 2.6.11.8. The goal of
> the testing was to temporarily disable a PCI slot containing a SCSI controller.
> I think I permanently killed the PCI slot; i/o died, and shortly after
> I hit the BUG(). See below.
>
> The goal is, of course, to have the kernel keep on trooping even if
> the SCSI controller dies out from under it; returning -EIO to user apps
> accessing the failed file system is acceptable.
>
> --linas
>
> io-falcons:~ # dmesg
>
>
> -bash: /bin/dmesg: Input/output error
>
> (Above is the "normal" message when a file system returns -EIO to user space;
> I expect to see these kinds of messages if the block device under the
> file system fails. Then, a second later I got the crash:
>
> io-falcons:~ #
> io-falcons:~ #
> io-falcons:~ # cpu 0x0: Vector: 700 (Program Check) at [c0000001ffe73740]
> pc: c000000000138b48: .write_ordered_chunk+0xa4/0x100
> lr: c0000000001392f4: .write_ordered_buffers+0x348/0x364
> sp: c0000001ffe739c0
> msr: 9000000000029032
> current = 0xc0000003fe6d5030
> paca = 0xc000000000547000
> pid = 942, comm = reiserfs/0
> kernel BUG in submit_ordered_buffer at fs/reiserfs/journal.c:616!
Hi Linas -
This one is on my radar among several others of the same type. What's
happening is that somehow buffers are getting dirtied despite not being
uptodate. They're getting allowed to be put back into the write cycle
which is totally invalid, so they're getting caught rather than being
written to disk. ext3 has similar problems, but tends to handle them as
buffer errors rather than BUGs. I'm investigating whether or not these
errors could occur outside individual filesystems.
- -Jeff
- --
Jeff Mahoney
SuSE Labs
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)
iD8DBQFCgOBdLPWxlyuTD7IRAqyHAJ9CNKvE0R8eNZZYb6KbTQ4uKoHNHACfa/kL
CRuuI9esIf10Xr2PGN/O77Y=
=eEwG
-----END PGP SIGNATURE-----
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: kernel BUG() hit during PCI testing
2005-05-10 16:25 ` Jeff Mahoney
@ 2005-05-10 17:34 ` Linas Vepstas
2005-05-10 18:25 ` Jeff Mahoney
0 siblings, 1 reply; 4+ messages in thread
From: Linas Vepstas @ 2005-05-10 17:34 UTC (permalink / raw)
To: Jeff Mahoney; +Cc: reiserfs-dev, reiserfs-list
HI,
On Tue, May 10, 2005 at 12:25:01PM -0400, Jeff Mahoney was heard to remark:
> Linas Vepstas wrote:
> >
> > Hi,
> >
> > I just hit a kernel BUG() during pci testing of 2.6.11.8. The goal of
> > the testing was to temporarily disable a PCI slot containing a SCSI controller.
> > I think I permanently killed the PCI slot; i/o died, and shortly after
> > I hit the BUG(). See below.
> >
> > The goal is, of course, to have the kernel keep on trooping even if
> > the SCSI controller dies out from under it; returning -EIO to user apps
> > accessing the failed file system is acceptable.
> >
> > --linas
> >
> > io-falcons:~ # dmesg
> >
> >
> > -bash: /bin/dmesg: Input/output error
> >
> > (Above is the "normal" message when a file system returns -EIO to user space;
> > I expect to see these kinds of messages if the block device under the
> > file system fails. Then, a second later I got the crash:
> >
> > io-falcons:~ #
> > io-falcons:~ #
> > io-falcons:~ # cpu 0x0: Vector: 700 (Program Check) at [c0000001ffe73740]
> > pc: c000000000138b48: .write_ordered_chunk+0xa4/0x100
> > lr: c0000000001392f4: .write_ordered_buffers+0x348/0x364
> > sp: c0000001ffe739c0
> > msr: 9000000000029032
> > current = 0xc0000003fe6d5030
> > paca = 0xc000000000547000
> > pid = 942, comm = reiserfs/0
> > kernel BUG in submit_ordered_buffer at fs/reiserfs/journal.c:616!
>
> Hi Linas -
>
> This one is on my radar among several others of the same type. What's
> happening is that somehow buffers are getting dirtied despite not being
> uptodate. They're getting allowed to be put back into the write cycle
> which is totally invalid, so they're getting caught rather than being
> written to disk. ext3 has similar problems, but tends to handle them as
> buffer errors rather than BUGs. I'm investigating whether or not these
> errors could occur outside individual filesystems.
OK, if I don't get busy with other things, I'll look more closely at
this as well. Maybe :-/ Meanwhile here's the dmesg output between
the pci outage and the crash. Don't know if this will be useful.
If you want any kind of tracing turned on, let me know.
--linas
<4>sym0: suspicious SCSI data while resetting the BUS.
<4>sym0: dp1,d15-8,dp0,d7-0,rst,req,ack,bsy,sel,atn,msg,c/d,i/o =
0x7ffffff, expecting 0x100
<5>sym0: SCSI BUS has been reset.
<4>sym0:8:0: HOST RESET operation timed-out.
(Yes, that's because the PCI bus is down at this point ... this
message is "normal".)
<6>scsi: Device offlined - not ready after error recovery: host 0
channel 0 id 8 lun 0
<6>scsi: Device offlined - not ready after error recovery: host 0
channel 0 id 8 lun 0
<6>scsi: Device offlined - not ready after error recovery: host 0
channel 0 id 8 lun 0
<3>scsi0 (8:0): rejecting I/O to offline device
<3>scsi0 (8:0): rejecting I/O to offline device
<3>scsi0 (8:0): rejecting I/O to offline device
<3>scsi0 (8:0): rejecting I/O to offline device
<3>Buffer I/O error on device sda4, logical block 743
<4>lost page write due to I/O error on sda4
<3>scsi0 (8:0): rejecting I/O to offline device
<3>Buffer I/O error on device sda4, logical block 744
<4>lost page write due to I/O error on sda4
<3>scsi0 (8:0): rejecting I/O to offline device
<3>Buffer I/O error on device sda4, logical block 745
<4>lost page write due to I/O error on sda4
<3>Buffer I/O error on device sda4, logical block 746
<4>lost page write due to I/O error on sda4
<3>Buffer I/O error on device sda4, logical block 747
<4>lost page write due to I/O error on sda4
<3>Buffer I/O error on device sda4, logical block 748
<4>lost page write due to I/O error on sda4
<3>Buffer I/O error on device sda4, logical block 749
<4>lost page write due to I/O error on sda4
<3>Buffer I/O error on device sda4, logical block 750
<4>lost page write due to I/O error on sda4
<3>Buffer I/O error on device sda4, logical block 751
<4>lost page write due to I/O error on sda4
<3>Buffer I/O error on device sda4, logical block 752
<4>lost page write due to I/O error on sda4
<4>ReiserFS: sda4: warning: vs-13070: reiserfs_read_locked_inode: i/o
failure occurred trying to find stat data of [20588 360606 0x0 SD]
<3>scsi0 (8:0): rejecting I/O to offline device
<2>REISERFS: abort (device sda4): Journal write error in
flush_commit_list
<2>REISERFS: Aborting journal for filesystem on sda4
<2>kernel BUG in submit_ordered_buffer at fs/reiserfs/journal.c:616!
<3>scsi0 (8:0): rejecting I/O to offline device
<4>ReiserFS: sda4: warning: vs-13070: reiserfs_read_locked_inode: i/o
failure occurred trying to find stat data of [20588 88143 0x0 SD]
<3>scsi0 (8:0): rejecting I/O to offline device
<4>ReiserFS: sda4: warning: vs-13070: reiserfs_read_locked_inode: i/o
failure occurred trying to find stat data of [20588 243569 0x0 SD]
<3>scsi0 (8:0): rejecting I/O to offline device
<4>ReiserFS: sda4: warning: vs-13070: reiserfs_read_locked_inode: i/o
failure occurred trying to find stat data of [20588 287908 0x0 SD]
<3>scsi0 (8:0): rejecting I/O to offline device
<4>ReiserFS: sda4: warning: vs-13070: reiserfs_read_locked_inode: i/o
failure occurred trying to find stat data of [20588 294525 0x0 SD]
<3>scsi0 (8:0): rejecting I/O to offline device
<4>ReiserFS: sda4: warning: vs-13070: reiserfs_read_locked_inode: i/o
failure occurred trying to find stat data of [20588 347520 0x0 SD]
<3>scsi0 (8:0): rejecting I/O to offline device
<4>ReiserFS: sda4: warning: vs-13070: reiserfs_read_locked_inode: i/o
failure occurred trying to find stat data of [20588 358764 0x0 SD]
<3>scsi0 (8:0): rejecting I/O to offline device
<4>ReiserFS: sda4: warning: vs-13070: reiserfs_read_locked_inode: i/o
failure occurred trying to find stat data of [20588 353053 0x0 SD]
<3>scsi0 (8:0): rejecting I/O to offline device
<4>ReiserFS: sda4: warning: vs-13070: reiserfs_read_locked_inode: i/o
failure occurred trying to find stat data of [20588 297565 0x0 SD]
<4>ReiserFS: sda4: warning: clm-6006: writing inode 155380 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 155380 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 155380 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 155380 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 155380 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 155380 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<3>scsi0 (8:0): rejecting I/O to offline device
<4>ReiserFS: sda4: warning: vs-13070: reiserfs_read_locked_inode: i/o
failure occurred trying to find stat data of [20588 271252 0x0 SD]
<3>scsi0 (8:0): rejecting I/O to offline device
<4>ReiserFS: sda4: warning: vs-13070: reiserfs_read_locked_inode: i/o
failure occurred trying to find stat data of [20588 294526 0x0 SD]
<3>scsi0 (8:0): rejecting I/O to offline device
<4>ReiserFS: sda4: warning: vs-13070: reiserfs_read_locked_inode: i/o
failure occurred trying to find stat data of [20588 275030 0x0 SD]
<3>scsi0 (8:0): rejecting I/O to offline device
<4>ReiserFS: sda4: warning: vs-13070: reiserfs_read_locked_inode: i/o
failure occurred trying to find stat data of [20588 269330 0x0 SD]
<3>scsi0 (8:0): rejecting I/O to offline device
<4>ReiserFS: sda4: warning: vs-13070: reiserfs_read_locked_inode: i/o
failure occurred trying to find stat data of [20595 269318 0x0 SD]
<3>scsi0 (8:0): rejecting I/O to offline device
<4>ReiserFS: sda4: warning: vs-13070: reiserfs_read_locked_inode: i/o
failure occurred trying to find stat data of [20588 364350 0x0 SD]
<3>scsi0 (8:0): rejecting I/O to offline device
<4>ReiserFS: sda4: warning: vs-13070: reiserfs_read_locked_inode: i/o
failure occurred trying to find stat data of [20588 271245 0x0 SD]
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<3>scsi0 (8:0): rejecting I/O to offline device
<4>ReiserFS: sda4: warning: vs-13070: reiserfs_read_locked_inode: i/o
failure occurred trying to find stat data of [20588 271354 0x0 SD]
<3>scsi0 (8:0): rejecting I/O to offline device
<4>ReiserFS: sda4: warning: vs-13070: reiserfs_read_locked_inode: i/o
failure occurred trying to find stat data of [2 157094 0x0 SD]
<3>scsi0 (8:0): rejecting I/O to offline device
<4>ReiserFS: sda4: warning: vs-13070: reiserfs_read_locked_inode: i/o
failure occurred trying to find stat data of [20588 275029 0x0 SD]
<3>scsi0 (8:0): rejecting I/O to offline device
<4>ReiserFS: sda4: warning: vs-13070: reiserfs_read_locked_inode: i/o
failure occurred trying to find stat data of [20588 263497 0x0 SD]
<3>scsi0 (8:0): rejecting I/O to offline device
<4>ReiserFS: sda4: warning: vs-13070: reiserfs_read_locked_inode: i/o
failure occurred trying to find stat data of [20588 100739 0x0 SD]
<4>ReiserFS: sda4: warning: clm-6006: writing inode 155380 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 155380 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 155380 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 155380 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 155380 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 155380 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 155380 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 155380 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 155380 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 155380 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 155380 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 155380 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 155380 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 155380 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 155380 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 155380 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
<4>ReiserFS: sda4: warning: clm-6006: writing inode 364428 on readonly
FS
0:mon>
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: kernel BUG() hit during PCI testing
2005-05-10 17:34 ` Linas Vepstas
@ 2005-05-10 18:25 ` Jeff Mahoney
0 siblings, 0 replies; 4+ messages in thread
From: Jeff Mahoney @ 2005-05-10 18:25 UTC (permalink / raw)
To: Linas Vepstas; +Cc: reiserfs-dev, reiserfs-list
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Linas Vepstas wrote:
> HI,
>
> On Tue, May 10, 2005 at 12:25:01PM -0400, Jeff Mahoney was heard to remark:
>>This one is on my radar among several others of the same type. What's
>>happening is that somehow buffers are getting dirtied despite not being
>>uptodate. They're getting allowed to be put back into the write cycle
>>which is totally invalid, so they're getting caught rather than being
>>written to disk. ext3 has similar problems, but tends to handle them as
>>buffer errors rather than BUGs. I'm investigating whether or not these
>>errors could occur outside individual filesystems.
>
> OK, if I don't get busy with other things, I'll look more closely at
> this as well. Maybe :-/ Meanwhile here's the dmesg output between
> the pci outage and the crash. Don't know if this will be useful.
> If you want any kind of tracing turned on, let me know.
It should be just a matter of performing an audit of where these buffers
are getting re-introduced into the write cycle. I don't really need any
more data points, I've got quite a bit already from various reports.
Thanks though.
- -Jeff
- --
Jeff Mahoney
SuSE Labs
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)
iD8DBQFCgPyrLPWxlyuTD7IRAmeEAJ9coIRFqDgtcR6/HM2W3Ub6cDCnPQCdEfDD
n98S1iOxoEdrFwASM8FRohE=
=/v+v
-----END PGP SIGNATURE-----
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2005-05-10 18:25 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-05-09 22:23 kernel BUG() hit during PCI testing Linas Vepstas
2005-05-10 16:25 ` Jeff Mahoney
2005-05-10 17:34 ` Linas Vepstas
2005-05-10 18:25 ` Jeff Mahoney
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.