mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Rudmer van Dijk <rudmer@legolas.dynup.net>
To: Dave Jones <davej@suse.de>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.5.13-dj1
Date: Sat, 04 May 2002 12:43:48 +0200	[thread overview]
Message-ID: <4.1.20020504114136.0094c330@pop.cablewanadoo.nl> (raw)
In-Reply-To: <4.1.20020504102844.00940230@pop.cablewanadoo.nl>

At 10:49 4-5-02 +0200, I wrote:
>compiled ok, booted ok, but got the same problem as with 2.5.1[02]-dj1 on
>my p100 (with F00F bug):
>
>the boot process stopped after fsck of hda1 (root partition) and the
>message 'hda lost interrupt' popped up every 5 sec or so.
>reboot into 2.4.19-pre8 resulted in a panic due to ext2 corruption, fscking
>hda1 from a rescue partition gave the message: Group descriptors look
>bad... using backup 
>
>so how can I try to find the cause of this problem??
>
applied the pio-patch of Osamu Tomita:
--- linux-2.5.10/drivers/ide/ide-taskfile.c Wed Apr 24 16:15:19 2002
+++ linux/drivers/ide/ide-taskfile.c Fri Apr 26 15:44:42 2002
@@ -202,7 +202,7 @@
 			ata_write_slow(drive, buffer, wcount);
 		else
 #endif
- 			ata_write_16(drive, buffer, wcount<<1); 
+ 			ata_write_16(drive, buffer, wcount); 
 	} 
 }

now the system keeps working after fsck and thus surviving the first write
to the disk...

after ~half an hour of heavy use (finding+grepping through the kernel
sources, hdparm -tT, dd from /dev/zero to file, all while running
SETI@home) it silently stopped. no messages, no response, SysRq-space gave
no message and it took about five times pressing SysRq-b for the system to
reboot. This time no kernel panic and no errors on filesystem.

	Rudmer

  reply	other threads:[~2002-05-04 10:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-03 18:58 Dave Jones
2002-05-03 21:25 ` Adrian Bunk
2002-05-04  8:49 ` Rudmer van Dijk
2002-05-04 10:43   ` Rudmer van Dijk [this message]
2002-05-04 12:29 ` Adrian Bunk
2002-05-04 12:42   ` Dave Jones

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=4.1.20020504114136.0094c330@pop.cablewanadoo.nl \
    --to=rudmer@legolas.dynup.net \
    --cc=davej@suse.de \
    --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

all inboxes | Powered by JetHome®