From: John R Lenton <john@grulic.org.ar>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: MSI6321 + PDC20265 + reiserfs + IBM deskstar => kernel BUG
Date: Sat, 19 May 2001 03:36:21 -0300 [thread overview]
Message-ID: <20010519033621.F562@grulic.org.ar> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1286 bytes --]
Running kernel 2.4.4 w/Jeff Garzik's via-apic patch, using
reiserfs on a IBM Deskstar on the PDC20265 of a MSI-6321, some
weird shtuff starts happening.
# mount /dev/hde /mnt
reiserfs: checking transaction log (device 21:00) ...
hde: timeout waiting for DMA
ide_dmaproc: chipset supported ide_dma_timeout func only: 14
hde: irq timeout: status=0x80 { Busy }
hde: DMA disabled
ide2: reset: success
reiserfs: replayed 12 transactions in 44 seconds
Using r5 hash to sort names
ReiserFS version 3.6.25
cool!
Now the fun starts: if I start creating a lot of files, I'll
never get to the 1000th, getting the BUG! that follows (the
farthest I've got is B/J/W, i.e. file # 933. Doing a dd instead
of just touching the file is worse). The drive never recovers; I
need to power down the box (a hard reset still leaves it making
these grunging noises).
I attach: the dewhatsitized oops, lspci -vvvxx, hdparm -i
/dev/hde, cat /proc/ide/pdc202xx (but before mounting hde), and
anything else I can think of before hitting y.
Holler if you need anything else.
--
John Lenton (john@grulic.org.ar) -- Random fortune:
O mangi la minestra, o minimizzi la finestra.
-- Andrea `Zuse' Balestrero, "Matemastica e Deformatica"
[-- Attachment #1.2: cpuinfo.gz --]
[-- Type: application/octet-stream, Size: 301 bytes --]
[-- Attachment #1.3: dma.gz --]
[-- Type: application/octet-stream, Size: 36 bytes --]
[-- Attachment #1.4: hdparm.gz --]
[-- Type: application/octet-stream, Size: 361 bytes --]
[-- Attachment #1.5: interrupts.gz --]
[-- Type: application/octet-stream, Size: 204 bytes --]
[-- Attachment #1.6: iomem.gz --]
[-- Type: application/octet-stream, Size: 385 bytes --]
[-- Attachment #1.7: ioports.gz --]
[-- Type: application/octet-stream, Size: 470 bytes --]
[-- Attachment #1.8: lspci.gz --]
[-- Type: application/octet-stream, Size: 1761 bytes --]
[-- Attachment #1.9: oops.gz --]
[-- Type: application/octet-stream, Size: 791 bytes --]
[-- Attachment #1.10: pdc202xx.gz --]
[-- Type: application/octet-stream, Size: 324 bytes --]
[-- Attachment #1.11: ver_linux.gz --]
[-- Type: application/octet-stream, Size: 414 bytes --]
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
reply other threads:[~2001-05-19 6:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010519033621.F562@grulic.org.ar \
--to=john@grulic.org.ar \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox