From: Frederik Nosi <fredi@e-salute.it>
To: linux-kernel@vger.kernel.org
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: Kernel (2.4.19-pre8) hang
Date: 28 May 2002 12:43:56 +0200 [thread overview]
Message-ID: <1022582637.1565.20.camel@linux> (raw)
In-Reply-To: <1022534650.11859.316.camel@irongate.swansea.linux.org.uk>
Il lun, 2002-05-27 alle 23:24, Alan Cox ha scritto:
> On Mon, 2002-05-27 at 20:24, Frederik Nosi wrote:
> > May 27 18:28:13 linux kernel: EXT3-fs error (device ide0(3,7)):
> > ext3_free_blocks: bit already cleared for block 215665
> >
> > I suspect at my hd too but for being sure... Please CC me because I'm
> > not subscribed to the list and excuse me for my bad english and the long
> > mail.
>
> What mode is your hard disk reported to be in. If it is using UDMA then
> its very unlikely to be the disk itself. We also should now have all the
> needed workarounds for VIA chipset bugs.
Well, the thing that makes me suspect of an hardware problem is that
with the very same kernel (and with ide0=ata66 option stupidly settet by
me for "using all hardware's power" and witch I have disabled from the
first problems I had) the pc worked happily from the 2.4.19-pre8 release
day till 3 or for days ago. In bios I've set PIO 4 && (U?)DMA 2. My
chipset is kx133 (mainboard: asus k7v-rm), CPU athlon 700 (not
overclocked) and the disk is a quantum 15Gb. I dont know what cabling is
used to connect the hd because I dont know to distinguish 80pin from
40pin. I've been using this hardware from 2 years and this is the first
"strange" problem. I've seen too that this problem happens expecialy in
massively writes to disk (for swapping ecc). Maybe this is useful:
#cat /proc/ide/ide0/hda/settings
name value min max mode
---- ----- --- --- ----
acoustic 0 0 254 rw
address 0 0 2 rw
bios_cyl 1826 0 65535 rw
bios_head 255 0 255 rw
bios_sect 63 0 63 rw
breada_readahead 8 0 255 rw
bswap 0 0 1 r
current_speed 68 0 69 rw
failures 0 0 65535 rw
file_readahead 124 0 16384 rw
ide_scsi 0 0 1 rw
init_speed 12 0 69 rw
io_32bit 1 0 3 rw
keepsettings 0 0 1 rw
lun 0 0 7 rw
max_failures 1 0 65535 rw
max_kb_per_request 128 1 255 rw
multcount 16 0 16 rw
nice1 1 0 1 rw
nowerr 0 0 1 rw
number 0 0 3 rw
pio_mode write-only 0 255 w
slow 0 0 1 rw
unmaskirq 1 0 1 rw
using_dma 1 0 1 rw
wcache 0 0 1 rw
#cat /proc/ide/ide0/hda/driver
ide-disk version 1.12
If you need more information I'll be happy to give that.
Well, did I have to buy a new hd ? :)
> Has this box been stable with older kernels ?
I think so
>
> Alan
>
Thank you for your time,
Fredi.
next prev parent reply other threads:[~2002-05-28 10:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-27 19:24 Kernel (2.4.19-pre8) hang Frederik Nosi
2002-05-27 21:24 ` Alan Cox
2002-05-28 10:43 ` Frederik Nosi [this message]
2002-06-01 21:57 ` Olivier Galibert
-- strict thread matches above, loose matches on Subject: below --
2002-05-28 13:41 Frederik Nosi
2002-05-28 15:05 ` Alan Cox
[not found] <1022610217.4123.133.camel@irongate.swansea.linux.org.uk>
2002-05-28 20:03 ` Frederik Nosi
2002-05-28 22:24 ` Alan Cox
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=1022582637.1565.20.camel@linux \
--to=fredi@e-salute.it \
--cc=alan@lxorguk.ukuu.org.uk \
--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