From: Andries Brouwer <aebr@win.tue.nl>
To: Jens Axboe <axboe@suse.de>
Cc: Andries.Brouwer@cwi.nl, linux-kernel@vger.kernel.org
Subject: Re: 2.5.37 oopses at boot in ide_toggle_bounce
Date: Mon, 30 Sep 2002 03:59:48 +0200 [thread overview]
Message-ID: <20020930015948.GA18680@win.tue.nl> (raw)
In-Reply-To: <20020923100219.GG25682@suse.de>
On Mon, Sep 23, 2002 at 12:04:24PM +0200, Jens Axboe wrote:
> > On Mon, Sep 23 2002, Andries Brouwer wrote:
> > > It no longer sees my disks on an HPT366,
> > Can you send me the kernel boot log
>
> Ah hang on, please boot with this patch from Ivan.
Patch makes no difference.
Situation:
no special kernel boot parameters concerning these disks,
no hdparm used
no CONFIG_BLK_DEV_HPT366
For 2.5.33:
HPT366: IDE controller on PCI bus 00 dev 48
HPT366: detected chipset, but driver not compiled in!
HPT366: chipset revision 1
HPT366: not 100%% native mode: will probe irqs later
ide2: BM-DMA at 0x9c00-0x9c07, BIOS settings: hde:pio, hdf:pio
HPT366: IDE controller on PCI bus 00 dev 49
HPT366: chipset revision 1
HPT366: not 100%% native mode: will probe irqs later
ide3: BM-DMA at 0xa800-0xa807, BIOS settings: hdg:pio, hdh:pio
For 2.5.38:
The string HPT does not occur in the boot log.
For 2.5.38 with CONFIG_BLK_DEV_HPT366:
all OK at first sight, the disks mount, have not tried to stress them
warnings in boot.log:
HPT366: chipset revision 1
HPT366: not 100%% native mode: will probe irqs later
ide2: BM-DMA at 0x9c00-0x9c07, BIOS settings: hde:DMA, hdf:DMA
hde: Maxtor 93652U8, ATA DISK drive
hdf: Maxtor 96147H6, ATA DISK drive
hde: set_drive_speed_status: status=0x51 { DriveReady SeekComplete Error }
hde: set_drive_speed_status: error=0x04 { DriveStatusError }
hdf: set_drive_speed_status: status=0x51 { DriveReady SeekComplete Error }
hdf: set_drive_speed_status: error=0x04 { DriveStatusError }
Funny that 2.5.33 reports "BIOS settings: hde:pio, hdf:pio"
while 2.5.38 says "BIOS settings: hde:DMA, hdf:DMA".
Long ago I would get (sporadic) disk errors and fs corruption with
CONFIG_BLK_DEV_HPT366, while all worked without. Today
CONFIG_BLK_DEV_HPT366 is required, but apart from the messages quoted
I have not seen any error messages or problems. Everything works.
Precisely the same holds for 2.5.39.
Andries
next prev parent reply other threads:[~2002-09-30 1:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-21 12:11 2.5.37 oopses at boot in ide_toggle_bounce Andries.Brouwer
2002-09-22 19:54 ` Thunder from the hill
2002-09-23 7:41 ` Jens Axboe
2002-09-23 10:01 ` Andries Brouwer
2002-09-23 10:02 ` Jens Axboe
2002-09-23 10:04 ` Jens Axboe
2002-09-30 1:59 ` Andries Brouwer [this message]
2002-09-30 13:51 ` Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2002-09-30 18:30 Andries.Brouwer
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=20020930015948.GA18680@win.tue.nl \
--to=aebr@win.tue.nl \
--cc=Andries.Brouwer@cwi.nl \
--cc=axboe@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