Promise Ultra133-TX2 (PCD20269).

Promise Ultra133-TX2 (PCD20269).

[Mark Williams (MWP)]

Hi all,
Sorry if this post to the list is inapropriate, i havnt been on the
kernel mailing list for long.

I am having rather ugly problems with this card using the PDC20269 chip.
Almost as soon as either of the HDDs on the controller are used, the
kernel hangs solid with a dump of debugging info.

Ive tried moving cards, diff, ram, cpu, etc everything short of changing
MB (never been a problem before installing this card), so im sure that
its this new IDE controller card that is the problem.
I have also tried changing interrupts via the BIOS to remove possible
clashes, but it also has not helped.

I am getting this problem with both the 2.4.22 and the 2.6.0-test7
kernels (tried different minimal configs).

Can anyone help me with this problem?
If any other info is needed, please let me know.

Thanks,
 Mark Williams.

Re: Promise Ultra133-TX2 (PCD20269).

[Måns Rullgård]

"Mark Williams (MWP)" <mwp@internode.on.net> writes:

> I am having rather ugly problems with this card using the PDC20269 chip.
> Almost as soon as either of the HDDs on the controller are used, the
> kernel hangs solid with a dump of debugging info.

That dump could be useful.  Also full output of dmesg and "lspci -vv"
can be helpful.

-- 
Måns Rullgård
mru@users.sf.net

Re: ReiserFS causing kernel panic?

[Mark Williams (MWP)]

[-- Attachment #1: Type: text/plain, Size: 866 bytes --]

> "Mark Williams (MWP)" <mwp@internode.on.net> writes:
> 
> > I am having rather ugly problems with this card using the PDC20269 chip.
> > Almost as soon as either of the HDDs on the controller are used, the
> > kernel hangs solid with a dump of debugging info.
> 
> That dump could be useful.  Also full output of dmesg and "lspci -vv"
> can be helpful.

Ok, seems this is not a controller fault, but really a problem with
ReiserFS (!!).

It seems one of the HDDs on the controller i thought had a problem is
corrupted, and the corrupted ReiserFS on it is causing the kernel to
panic.

Attached is the dump of the kern log from where the problem begins to
where it rebooted itself.

The other HDD on the same controller (same HDD model, WD1200JB) is also
ReiserFS, but works fine.

BTW, sorry for the large attachment, but i didnt know if you would want
all of it.

[-- Attachment #2: dump.txt --]
[-- Type: text/plain, Size: 18399 bytes --]

Oct 12 21:48:03 linux kernel: ide3(34,2):Using r5 hash to sort names
Oct 12 21:48:52 linux kernel: vs-500: unknown uniqueness 45644
Oct 12 21:48:52 linux last message repeated 5 times
Oct 12 21:48:52 linux kernel: ide3(34,2):vs-5150: search_by_key: invalid format found in block 5471028. Fsck?
Oct 12 21:48:52 linux kernel: ide3(34,2):vs-13070: reiserfs_read_inode2: i/o failure occurred trying to find stat data of [45464 45630 0x0 SD]
Oct 12 21:48:52 linux kernel: vs-500: unknown uniqueness 45644
Oct 12 21:48:52 linux last message repeated 5 times
Oct 12 21:48:52 linux kernel: ide3(34,2):vs-5150: search_by_key: invalid format found in block 5471028. Fsck?
Oct 12 21:48:52 linux kernel: ide3(34,2):vs-13070: reiserfs_read_inode2: i/o failure occurred trying to find stat data of [45464 45631 0x0 SD]
Oct 12 21:48:52 linux kernel: vs-500: unknown uniqueness 45644
Oct 12 21:48:52 linux last message repeated 5 times
Oct 12 21:48:52 linux kernel: ide3(34,2):vs-5150: search_by_key: invalid format found in block 5471028. Fsck?
Oct 12 21:48:52 linux kernel: ide3(34,2):vs-13070: reiserfs_read_inode2: i/o failure occurred trying to find stat data of [45464 45632 0x0 SD]
Oct 12 21:48:52 linux kernel: vs-500: unknown uniqueness 45644
Oct 12 21:48:52 linux last message repeated 5 times
Oct 12 21:48:52 linux kernel: ide3(34,2):vs-5150: search_by_key: invalid format found in block 5471028. Fsck?
Oct 12 21:48:52 linux kernel: ide3(34,2):vs-13070: reiserfs_read_inode2: i/o failure occurred trying to find stat data of [45464 45633 0x0 SD]
Oct 12 21:48:52 linux kernel: vs-500: unknown uniqueness 45644
Oct 12 21:48:52 linux last message repeated 5 times
Oct 12 21:48:52 linux kernel: ide3(34,2):vs-5150: search_by_key: invalid format found in block 5471028. Fsck?
Oct 12 21:48:52 linux kernel: ide3(34,2):vs-13070: reiserfs_read_inode2: i/o failure occurred trying to find stat data of [45464 45634 0x0 SD]
Oct 12 21:48:52 linux kernel: vs-500: unknown uniqueness 45644
Oct 12 21:48:52 linux last message repeated 5 times
Oct 12 21:48:52 linux kernel: ide3(34,2):vs-5150: search_by_key: invalid format found in block 5471028. Fsck?
Oct 12 21:48:52 linux kernel: ide3(34,2):vs-13070: reiserfs_read_inode2: i/o failure occurred trying to find stat data of [45464 45635 0x0 SD]
Oct 12 21:48:52 linux kernel: vs-500: unknown uniqueness 45644
Oct 12 21:48:52 linux last message repeated 5 times
Oct 12 21:48:52 linux kernel: ide3(34,2):vs-5150: search_by_key: invalid format found in block 5471028. Fsck?
Oct 12 21:48:52 linux kernel: ide3(34,2):vs-13070: reiserfs_read_inode2: i/o failure occurred trying to find stat data of [45464 45636 0x0 SD]
Oct 12 21:48:52 linux kernel: vs-500: unknown uniqueness 45644
Oct 12 21:48:52 linux last message repeated 5 times
Oct 12 21:48:52 linux kernel: ide3(34,2):vs-5150: search_by_key: invalid format found in block 5471028. Fsck?
Oct 12 21:48:52 linux kernel: ide3(34,2):vs-13070: reiserfs_read_inode2: i/o failure occurred trying to find stat data of [45464 45637 0x0 SD]
Oct 12 21:48:52 linux kernel: vs-500: unknown uniqueness 45644
Oct 12 21:48:52 linux last message repeated 5 times
Oct 12 21:48:52 linux kernel: ide3(34,2):vs-5150: search_by_key: invalid format found in block 5471028. Fsck?
Oct 12 21:48:52 linux kernel: ide3(34,2):vs-13070: reiserfs_read_inode2: i/o failure occurred trying to find stat data of [45464 45638 0x0 SD]
Oct 12 21:48:52 linux kernel: vs-500: unknown uniqueness 45644
Oct 12 21:48:52 linux last message repeated 5 times
Oct 12 21:48:52 linux kernel: ide3(34,2):vs-5150: search_by_key: invalid format found in block 5471028. Fsck?
Oct 12 21:48:52 linux kernel: ide3(34,2):vs-13070: reiserfs_read_inode2: i/o failure occurred trying to find stat data of [45464 45639 0x0 SD]
Oct 12 21:48:52 linux kernel: vs-500: unknown uniqueness 45644
Oct 12 21:48:52 linux last message repeated 5 times
Oct 12 21:48:52 linux kernel: ide3(34,2):vs-5150: search_by_key: invalid format found in block 5471028. Fsck?
Oct 12 21:48:52 linux kernel: ide3(34,2):vs-13070: reiserfs_read_inode2: i/o failure occurred trying to find stat data of [45464 45640 0x0 SD]
Oct 12 21:48:52 linux kernel: vs-500: unknown uniqueness 45644
Oct 12 21:48:52 linux last message repeated 5 times
Oct 12 21:48:52 linux kernel: ide3(34,2):vs-5150: search_by_key: invalid format found in block 5471028. Fsck?
Oct 12 21:48:52 linux kernel: ide3(34,2):vs-13070: reiserfs_read_inode2: i/o failure occurred trying to find stat data of [45464 45641 0x0 SD]
Oct 12 21:48:52 linux kernel: vs-500: unknown uniqueness 45644
Oct 12 21:48:52 linux last message repeated 5 times
Oct 12 21:48:52 linux kernel: ide3(34,2):vs-5150: search_by_key: invalid format found in block 5471028. Fsck?
Oct 12 21:48:52 linux kernel: ide3(34,2):vs-13070: reiserfs_read_inode2: i/o failure occurred trying to find stat data of [45464 45642 0x0 SD]
Oct 12 21:48:52 linux kernel: vs-500: unknown uniqueness 45644
Oct 12 21:48:52 linux last message repeated 5 times
Oct 12 21:48:52 linux kernel: ide3(34,2):vs-5150: search_by_key: invalid format found in block 5471028. Fsck?
Oct 12 21:48:52 linux kernel: ide3(34,2):vs-13070: reiserfs_read_inode2: i/o failure occurred trying to find stat data of [45464 45643 0x0 SD]
Oct 12 21:48:52 linux kernel: vs-500: unknown uniqueness 45644
Oct 12 21:48:52 linux last message repeated 5 times
Oct 12 21:48:52 linux kernel: ide3(34,2):vs-5150: search_by_key: invalid format found in block 5471028. Fsck?
Oct 12 21:48:52 linux kernel: ide3(34,2):vs-13070: reiserfs_read_inode2: i/o failure occurred trying to find stat data of [45464 45644 0x0 SD]
Oct 12 21:48:52 linux kernel: vs-500: unknown uniqueness 45644
Oct 12 21:48:52 linux last message repeated 5 times
Oct 12 21:48:52 linux kernel: ide3(34,2):vs-5150: search_by_key: invalid format found in block 5471028. Fsck?
Oct 12 21:48:52 linux kernel: ide3(34,2):vs-13070: reiserfs_read_inode2: i/o failure occurred trying to find stat data of [45464 45645 0x0 SD]
Oct 12 21:48:52 linux kernel: vs-500: unknown uniqueness 45644
Oct 12 21:48:52 linux last message repeated 5 times
Oct 12 21:48:52 linux kernel: ide3(34,2):vs-5150: search_by_key: invalid format found in block 5471028. Fsck?
Oct 12 21:48:52 linux kernel: ide3(34,2):vs-13070: reiserfs_read_inode2: i/o failure occurred trying to find stat data of [45464 45646 0x0 SD]
Oct 12 21:48:52 linux kernel: vs-500: unknown uniqueness 45644
Oct 12 21:48:52 linux last message repeated 5 times
Oct 12 21:48:52 linux kernel: ide3(34,2):vs-5150: search_by_key: invalid format found in block 5471028. Fsck?
Oct 12 21:48:52 linux kernel: ide3(34,2):vs-13070: reiserfs_read_inode2: i/o failure occurred trying to find stat data of [45464 45647 0x0 SD]
Oct 12 21:48:52 linux kernel: vs-500: unknown uniqueness 45644
Oct 12 21:48:52 linux last message repeated 5 times
Oct 12 21:48:52 linux kernel: ide3(34,2):vs-5150: search_by_key: invalid format found in block 5471028. Fsck?
Oct 12 21:48:52 linux kernel: ide3(34,2):vs-13070: reiserfs_read_inode2: i/o failure occurred trying to find stat data of [45464 45648 0x0 SD]
Oct 12 21:48:52 linux kernel: vs-500: unknown uniqueness 45644
Oct 12 21:48:52 linux last message repeated 5 times
Oct 12 21:48:52 linux kernel: ide3(34,2):vs-5150: search_by_key: invalid format found in block 5471028. Fsck?
Oct 12 21:48:52 linux kernel: ide3(34,2):vs-13070: reiserfs_read_inode2: i/o failure occurred trying to find stat data of [45464 45649 0x0 SD]
Oct 12 21:48:52 linux kernel: vs-500: unknown uniqueness 45644
Oct 12 21:48:52 linux last message repeated 5 times
Oct 12 21:48:52 linux kernel: ide3(34,2):vs-5150: search_by_key: invalid format found in block 5471028. Fsck?
Oct 12 21:48:52 linux kernel: ide3(34,2):vs-13070: reiserfs_read_inode2: i/o failure occurred trying to find stat data of [45464 45650 0x0 SD]
Oct 12 21:48:52 linux kernel: vs-500: unknown uniqueness 45644
Oct 12 21:48:52 linux last message repeated 5 times
Oct 12 21:48:52 linux kernel: ide3(34,2):vs-5150: search_by_key: invalid format found in block 5471028. Fsck?
Oct 12 21:48:52 linux kernel: ide3(34,2):vs-13070: reiserfs_read_inode2: i/o failure occurred trying to find stat data of [45464 45651 0x0 SD]
Oct 12 21:48:52 linux kernel: vs-500: unknown uniqueness 45644
Oct 12 21:48:52 linux last message repeated 5 times
Oct 12 21:48:52 linux kernel: ide3(34,2):vs-5150: search_by_key: invalid format found in block 5471028. Fsck?
Oct 12 21:48:52 linux kernel: ide3(34,2):vs-13070: reiserfs_read_inode2: i/o failure occurred trying to find stat data of [45464 45652 0x0 SD]
Oct 12 21:48:52 linux kernel: vs-500: unknown uniqueness 45644
Oct 12 21:48:52 linux last message repeated 5 times
Oct 12 21:48:52 linux kernel: ide3(34,2):vs-5150: search_by_key: invalid format found in block 5471028. Fsck?
Oct 12 21:48:52 linux kernel: ide3(34,2):vs-13070: reiserfs_read_inode2: i/o failure occurred trying to find stat data of [45464 45653 0x0 SD]
Oct 12 21:48:52 linux kernel: vs-500: unknown uniqueness 45644
Oct 12 21:48:52 linux last message repeated 5 times
Oct 12 21:48:52 linux kernel: ide3(34,2):vs-5150: search_by_key: invalid format found in block 5471028. Fsck?
Oct 12 21:48:52 linux kernel: ide3(34,2):vs-13070: reiserfs_read_inode2: i/o failure occurred trying to find stat data of [45464 45654 0x0 SD]
Oct 12 21:48:52 linux kernel: vs-500: unknown uniqueness 45644
Oct 12 21:48:52 linux last message repeated 5 times
Oct 12 21:48:52 linux kernel: ide3(34,2):vs-5150: search_by_key: invalid format found in block 5471028. Fsck?
Oct 12 21:48:52 linux kernel: ide3(34,2):vs-13070: reiserfs_read_inode2: i/o failure occurred trying to find stat data of [45464 45655 0x0 SD]
Oct 12 21:48:52 linux kernel: vs-500: unknown uniqueness 45644
Oct 12 21:48:52 linux last message repeated 5 times
Oct 12 21:48:52 linux kernel: ide3(34,2):vs-5150: search_by_key: invalid format found in block 5471028. Fsck?
Oct 12 21:48:52 linux kernel: ide3(34,2):vs-13070: reiserfs_read_inode2: i/o failure occurred trying to find stat data of [45464 45656 0x0 SD]
Oct 12 21:48:52 linux kernel: vs-500: unknown uniqueness 45644
Oct 12 21:48:52 linux last message repeated 5 times
Oct 12 21:48:52 linux kernel: ide3(34,2):vs-5150: search_by_key: invalid format found in block 5471028. Fsck?
Oct 12 21:48:52 linux kernel: ide3(34,2):vs-13070: reiserfs_read_inode2: i/o failure occurred trying to find stat data of [45464 45657 0x0 SD]
Oct 12 21:48:52 linux kernel: vs-500: unknown uniqueness 45644
Oct 12 21:48:52 linux last message repeated 5 times
Oct 12 21:48:52 linux kernel: ide3(34,2):vs-5150: search_by_key: invalid format found in block 5471028. Fsck?
Oct 12 21:48:52 linux kernel: ide3(34,2):vs-13070: reiserfs_read_inode2: i/o failure occurred trying to find stat data of [45464 45658 0x0 SD]
Oct 12 21:48:52 linux kernel: vs-500: unknown uniqueness 45644
Oct 12 21:48:52 linux last message repeated 5 times
Oct 12 21:48:52 linux kernel: ide3(34,2):vs-5150: search_by_key: invalid format found in block 5471028. Fsck?
Oct 12 21:48:52 linux kernel: ide3(34,2):vs-13070: reiserfs_read_inode2: i/o failure occurred trying to find stat data of [45464 45659 0x0 SD]
Oct 12 21:48:52 linux kernel: vs-500: unknown uniqueness 45644
Oct 12 21:48:52 linux last message repeated 5 times
Oct 12 21:48:52 linux kernel: ide3(34,2):vs-5150: search_by_key: invalid format found in block 5471028. Fsck?
Oct 12 21:48:52 linux kernel: ide3(34,2):vs-13070: reiserfs_read_inode2: i/o failure occurred trying to find stat data of [45464 45660 0x0 SD]
Oct 12 21:48:52 linux kernel: vs-500: unknown uniqueness 45644
Oct 12 21:48:52 linux last message repeated 5 times
Oct 12 21:48:52 linux kernel: ide3(34,2):vs-5150: search_by_key: invalid format found in block 5471028. Fsck?
Oct 12 21:48:52 linux kernel: ide3(34,2):vs-13070: reiserfs_read_inode2: i/o failure occurred trying to find stat data of [45464 45662 0x0 SD]
Oct 12 21:48:53 linux kernel: vs-500: unknown uniqueness 1319
Oct 12 21:48:53 linux last message repeated 6 times
Oct 12 21:48:53 linux kernel: ide3(34,2):vs-5150: search_by_key: invalid format found in block 305854. Fsck?
Oct 12 21:48:53 linux kernel: ide3(34,2):vs-13070: reiserfs_read_inode2: i/o failure occurred trying to find stat data of [1626 1631 0x0 SD]
Oct 12 21:48:53 linux kernel: vs-500: unknown uniqueness 1319
Oct 12 21:48:53 linux last message repeated 6 times
Oct 12 21:48:53 linux kernel: ide3(34,2):vs-5150: search_by_key: invalid format found in block 305854. Fsck?
Oct 12 21:48:53 linux kernel: ide3(34,2):vs-13070: reiserfs_read_inode2: i/o failure occurred trying to find stat data of [1626 1636 0x0 SD]
Oct 12 21:48:53 linux kernel: vs-500: unknown uniqueness 1319
Oct 12 21:48:53 linux last message repeated 6 times
Oct 12 21:48:53 linux kernel: ide3(34,2):vs-5150: search_by_key: invalid format found in block 305854. Fsck?
Oct 12 21:48:53 linux kernel: ide3(34,2):vs-13070: reiserfs_read_inode2: i/o failure occurred trying to find stat data of [1626 1632 0x0 SD]
Oct 12 21:48:53 linux kernel: vs-500: unknown uniqueness 1319
Oct 12 21:48:53 linux last message repeated 6 times
Oct 12 21:48:53 linux kernel: ide3(34,2):vs-5150: search_by_key: invalid format found in block 305854. Fsck?
Oct 12 21:48:53 linux kernel: ide3(34,2):vs-13070: reiserfs_read_inode2: i/o failure occurred trying to find stat data of [1626 1634 0x0 SD]
Oct 12 21:48:53 linux kernel: vs-500: unknown uniqueness 1319
Oct 12 21:48:53 linux last message repeated 6 times
Oct 12 21:48:53 linux kernel: ide3(34,2):vs-5150: search_by_key: invalid format found in block 305854. Fsck?
Oct 12 21:48:53 linux kernel: ide3(34,2):vs-13070: reiserfs_read_inode2: i/o failure occurred trying to find stat data of [1637 1642 0x0 SD]
Oct 12 21:48:53 linux kernel: vs-500: unknown uniqueness 1319
Oct 12 21:48:53 linux last message repeated 6 times
Oct 12 21:48:53 linux kernel: ide3(34,2):vs-5150: search_by_key: invalid format found in block 305854. Fsck?
Oct 12 21:48:53 linux kernel: ide3(34,2):vs-13070: reiserfs_read_inode2: i/o failure occurred trying to find stat data of [1637 1640 0x0 SD]
Oct 12 21:48:53 linux kernel: vs-500: unknown uniqueness 1319
Oct 12 21:48:53 linux last message repeated 6 times
Oct 12 21:48:53 linux kernel: ide3(34,2):vs-5150: search_by_key: invalid format found in block 305854. Fsck?
Oct 12 21:48:53 linux kernel: ide3(34,2):vs-13070: reiserfs_read_inode2: i/o failure occurred trying to find stat data of [1236 1276 0x0 SD]
Oct 12 21:48:53 linux kernel: vs-500: unknown uniqueness 1319
Oct 12 21:48:53 linux last message repeated 6 times
Oct 12 21:48:53 linux kernel: ide3(34,2):vs-5150: search_by_key: invalid format found in block 305854. Fsck?
Oct 12 21:48:53 linux kernel: ide3(34,2):vs-13070: reiserfs_read_inode2: i/o failure occurred trying to find stat data of [1312 1337 0x0 SD]
Oct 12 21:48:53 linux kernel: vs-500: unknown uniqueness 1319
Oct 12 21:48:53 linux last message repeated 6 times
Oct 12 21:48:53 linux kernel: ide3(34,2):vs-5150: search_by_key: invalid format found in block 305854. Fsck?
Oct 12 21:48:53 linux kernel: ide3(34,2):vs-13070: reiserfs_read_inode2: i/o failure occurred trying to find stat data of [1312 1317 0x0 SD]
Oct 12 21:48:53 linux kernel: vs-500: unknown uniqueness 1319
Oct 12 21:48:53 linux last message repeated 6 times
Oct 12 21:48:53 linux kernel: ide3(34,2):vs-5150: search_by_key: invalid format found in block 305854. Fsck?
Oct 12 21:48:53 linux kernel: ide3(34,2):vs-13070: reiserfs_read_inode2: i/o failure occurred trying to find stat data of [1312 1346 0x0 SD]
Oct 12 21:48:53 linux kernel: vs-500: unknown uniqueness 1319
Oct 12 21:48:53 linux last message repeated 6 times
Oct 12 21:48:53 linux kernel: ide3(34,2):vs-5150: search_by_key: invalid format found in block 305854. Fsck?
Oct 12 21:48:53 linux kernel: ide3(34,2):vs-13070: reiserfs_read_inode2: i/o failure occurred trying to find stat data of [1312 1347 0x0 SD]
Oct 12 21:48:53 linux kernel: vs-500: unknown uniqueness 1319
Oct 12 21:48:53 linux last message repeated 6 times
Oct 12 21:48:53 linux kernel: ide3(34,2):vs-5150: search_by_key: invalid format found in block 305854. Fsck?
Oct 12 21:48:53 linux kernel: ide3(34,2):vs-13070: reiserfs_read_inode2: i/o failure occurred trying to find stat data of [1312 1349 0x0 SD]
Oct 12 21:48:53 linux kernel: vs-500: unknown uniqueness 1319
Oct 12 21:48:53 linux last message repeated 6 times
Oct 12 21:48:53 linux kernel: ide3(34,2):vs-5150: search_by_key: invalid format found in block 305854. Fsck?
Oct 12 21:48:53 linux kernel: ide3(34,2):vs-13070: reiserfs_read_inode2: i/o failure occurred trying to find stat data of [1312 1319 0x0 SD]
Oct 12 21:48:53 linux kernel: vs-500: unknown uniqueness 1319
Oct 12 21:48:53 linux last message repeated 6 times
Oct 12 21:48:53 linux kernel: ide3(34,2):vs-5150: search_by_key: invalid format found in block 305854. Fsck?
Oct 12 21:48:53 linux kernel: ide3(34,2):vs-13070: reiserfs_read_inode2: i/o failure occurred trying to find stat data of [1312 1320 0x0 SD]
Oct 12 21:48:53 linux kernel: vs-500: unknown uniqueness 1319
Oct 12 21:48:53 linux last message repeated 6 times
Oct 12 21:48:53 linux kernel: ide3(34,2):vs-5150: search_by_key: invalid format found in block 305854. Fsck?
Oct 12 21:48:53 linux kernel: ide3(34,2):vs-13070: reiserfs_read_inode2: i/o failure occurred trying to find stat data of [1312 1326 0x0 SD]
Oct 12 21:48:53 linux kernel: vs-500: unknown uniqueness 1319
Oct 12 21:48:53 linux last message repeated 6 times
Oct 12 21:48:53 linux kernel: ide3(34,2):vs-5150: search_by_key: invalid format found in block 305854. Fsck?
Oct 12 21:48:53 linux kernel: ide3(34,2):vs-13070: reiserfs_read_inode2: i/o failure occurred trying to find stat data of [1312 1327 0x0 SD]
Oct 12 21:48:53 linux kernel: vs-500: unknown uniqueness 1319
Oct 12 21:48:53 linux last message repeated 6 times
Oct 12 21:48:53 linux kernel: ide3(34,2):vs-5150: search_by_key: invalid format found in block 305854. Fsck?
Oct 12 21:48:53 linux kernel: ide3(34,2):vs-13070: reiserfs_read_inode2: i/o failure occurred trying to find stat data of [1312 1325 0x0 SD]
Oct 12 21:48:53 linux kernel: vs-500: unknown uniqueness 1319
Oct 12 21:48:53 linux last message repeated 6 times
Oct 12 21:48:53 linux kernel: ide3(34,2):vs-5150: search_by_key: invalid format found in block 305854. Fsck?
Oct 12 21:48:53 linux kernel: ide3(34,2):vs-13070: reiserfs_read_inode2: i/o failure occurred trying to find stat data of [1488 1496 0x0 SD]
O

Re: ReiserFS causing kernel panic?

[Tomas Szepe]

On Oct-12 2003, Sun, 23:30 +0930
Mark Williams (MWP) <mwp@internode.on.net> wrote:

> > "Mark Williams (MWP)" <mwp@internode.on.net> writes:
> > 
> > > I am having rather ugly problems with this card using the PDC20269 chip.
> > > Almost as soon as either of the HDDs on the controller are used, the
> > > kernel hangs solid with a dump of debugging info.
> > 
> > That dump could be useful.  Also full output of dmesg and "lspci -vv"
> > can be helpful.
> 
> Ok, seems this is not a controller fault, but really a problem with
> ReiserFS (!!).

Do you really expect reiserfs code (or any other fs code for that matter)
not to choke on a corrupted filesystem?

Put the disk on a trusted controller and fsck.

-- 
Tomas Szepe <szepe@pinerecords.com>

Re: ReiserFS causing kernel panic?

[Mark Williams (MWP)]

> On Oct-12 2003, Sun, 23:30 +0930
> Mark Williams (MWP) <mwp@internode.on.net> wrote:
> 
> > > "Mark Williams (MWP)" <mwp@internode.on.net> writes:
> > > 
> > > > I am having rather ugly problems with this card using the PDC20269 chip.
> > > > Almost as soon as either of the HDDs on the controller are used, the
> > > > kernel hangs solid with a dump of debugging info.
> > > 
> > > That dump could be useful.  Also full output of dmesg and "lspci -vv"
> > > can be helpful.
> > 
> > Ok, seems this is not a controller fault, but really a problem with
> > ReiserFS (!!).
> 
> Do you really expect reiserfs code (or any other fs code for that matter)
> not to choke on a corrupted filesystem?
> 
> Put the disk on a trusted controller and fsck.

No, i wouldnt expect reiserfs to handle the data on the FS, but i also
wouldnt have expected it to cause a kernel panic and hang the system.

Re: ReiserFS causing kernel panic?

[Hans Reiser]

Mark Williams (MWP) wrote:

>>"Mark Williams (MWP)" <mwp@internode.on.net> writes:
>>
>>    
>>
>>>I am having rather ugly problems with this card using the PDC20269 chip.
>>>Almost as soon as either of the HDDs on the controller are used, the
>>>kernel hangs solid with a dump of debugging info.
>>>      
>>>
>>That dump could be useful.  Also full output of dmesg and "lspci -vv"
>>can be helpful.
>>    
>>
>
>Ok, seems this is not a controller fault, but really a problem with
>ReiserFS (!!).
>
>It seems one of the HDDs on the controller i thought had a problem is
>corrupted, and the corrupted ReiserFS on it is causing the kernel to
>panic.
>  
>
reiserfs is not warranted to work on corrupted hdds.....

-- 
Hans

Re: ReiserFS causing kernel panic?

[Hans Reiser]

Mark Williams (MWP) wrote:

>>On Oct-12 2003, Sun, 23:30 +0930
>>Mark Williams (MWP) <mwp@internode.on.net> wrote:
>>
>>    
>>
>>>>"Mark Williams (MWP)" <mwp@internode.on.net> writes:
>>>>
>>>>        
>>>>
>>>>>I am having rather ugly problems with this card using the PDC20269 chip.
>>>>>Almost as soon as either of the HDDs on the controller are used, the
>>>>>kernel hangs solid with a dump of debugging info.
>>>>>          
>>>>>
>>>>That dump could be useful.  Also full output of dmesg and "lspci -vv"
>>>>can be helpful.
>>>>        
>>>>
>>>Ok, seems this is not a controller fault, but really a problem with
>>>ReiserFS (!!).
>>>      
>>>
>>Do you really expect reiserfs code (or any other fs code for that matter)
>>not to choke on a corrupted filesystem?
>>
>>Put the disk on a trusted controller and fsck.
>>    
>>
>
>No, i wouldnt expect reiserfs to handle the data on the FS, but i also
>wouldnt have expected it to cause a kernel panic and hang the system.
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at  http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at  http://www.tux.org/lkml/
>
>
>  
>
I'll be happy to accept a patch changing it to remount the fs ro instead 
of panicking.

-- 
Hans

Re: Promise Ultra133-TX2 (PCD20269).

[Marcelo Tosatti]

On Sun, 12 Oct 2003, Mark Williams (MWP) wrote:

> Hi all,
> Sorry if this post to the list is inapropriate, i havnt been on the
> kernel mailing list for long.
> 
> I am having rather ugly problems with this card using the PDC20269 chip.
> Almost as soon as either of the HDDs on the controller are used, the
> kernel hangs solid with a dump of debugging info.

> Ive tried moving cards, diff, ram, cpu, etc everything short of changing
> MB (never been a problem before installing this card), so im sure that
> its this new IDE controller card that is the problem.
> I have also tried changing interrupts via the BIOS to remove possible
> clashes, but it also has not helped.
> 
> I am getting this problem with both the 2.4.22 and the 2.6.0-test7
> kernels (tried different minimal configs).
> 
> Can anyone help me with this problem?
> If any other info is needed, please let me know.

Please copy the exact information after the hang and post it.

Thank you

Re: ReiserFS causing kernel panic?

[Hans Reiser]

Ihar 'Philips' Filipau wrote:

> Hans Reiser wrote:
>
>> reiserfs is not warranted to work on corrupted hdds.....
>
>
>   Is there any kind of error statistics for hard drives?
>
>   Geometry is known.
>   I suspect that structure of damages, caused by contact of plates 
> surface with head, can be classified. 

>
>
>   It may be possible to classify manufacturing glitches. I think HD 
> producers have this kind of classification/statistics - to improve 
> quality, keeping price low.
>
>   Actually what I'm thinking of: some kind of design rules for file 
> systems, how to minimize crashing due to hdd glitches.
>   Let's say, if some of hdd regions are know to be more error prone - 
> desing fs to use those regions less.
>   If hdd damages used to have some specific structure - design file 
> system to keep renundant data in regions which are less likely to be 
> lost both at the same time. So renundancy would make sense.
>
>   Is there any thing like this?
>
>   Or file systems now do outlive hard drives?-)
>


Block allocation policies affect performance a lot, and keeping them 
simple is important.    I would however be interested in knowing what 
the distribution function for errors by geometry is.  If it turned out 
that, say, errors were higher at the platter edges, I could make some 
format changes....

I think that for users it is best to think about how to mask drive 
errors in the device layer or the device using RAID and mirroring.

-- 
Hans

Re: ReiserFS causing kernel panic?

[Ihar 'Philips' Filipau]

Hans Reiser wrote:
> reiserfs is not warranted to work on corrupted hdds.....

   Is there any kind of error statistics for hard drives?

   Geometry is known.
   I suspect that structure of damages, caused by contact of plates 
surface with head, can be classified.

   It may be possible to classify manufacturing glitches. I think HD 
producers have this kind of classification/statistics - to improve 
quality, keeping price low.

   Actually what I'm thinking of: some kind of design rules for file 
systems, how to minimize crashing due to hdd glitches.
   Let's say, if some of hdd regions are know to be more error prone - 
desing fs to use those regions less.
   If hdd damages used to have some specific structure - design file 
system to keep renundant data in regions which are less likely to be 
lost both at the same time. So renundancy would make sense.

   Is there any thing like this?

   Or file systems now do outlive hard drives?-)

-- 
Ihar 'Philips' Filipau  / with best regards from Saarbruecken.
--
   "... and for $64000 question, could you get yourself vaguely
      familiar with the notion of on-topic posting?"
				-- Al Viro @ LKML