From: Anton Tinchev <atl@top.bg>
To: Ville Herva <vherva@niksula.hut.fi>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Sharing Interrupt+HPT366 Problem on BP6
Date: Sat, 19 Jan 2002 16:51:01 -0800 [thread overview]
Message-ID: <3C4A1475.4D0BB1F6@top.bg> (raw)
In-Reply-To: <3C49A8AD.2BBC7F7A@top.bg> <20020119112555.GD135220@niksula.cs.hut.fi>
Without NIC hangs too...
I tried every combination that i can imagine and the result is:
Drives on only one channel - system works
Drives on both channels - system hangs
Ville Herva wrote:
> On Sat, Jan 19, 2002 at 09:11:09AM -0800, you [Anton Tinchev] claimed:
> >
> > The configuration is:
> > Abit BP6 MB
> > Single Celeron 366 processor
> > 1X10G hdd
> > 3X60G hdd
> > 256MB ram
> > Davicom 100MB/s NIC
> > S3 Trio3D AGP VGA
>
> Which slot did you put your nic (and other pci cards)? Don't put them in
> slot #3 (it shares the IRQ with HPT366). And even if slot 3 is empty, try
> switching the slow and see if it makes difference.
>
> Also, make sure you have the newest bios.
>
> I have BP6 here, three drives HPT366:
>
> hda: IBM-DCAA-34330, ATA DISK drive
> hdb: CD-532E-A, ATAPI CD/DVD-ROM drive
> hdd: CR-4804TE, ATAPI CD/DVD-ROM drive
> hde: IBM-DJNA-352030, ATA DISK drive
> hdf: IBM-DTTA-351680, ATA DISK drive
> hdg: SAMSUNG SV6004H, ATA DISK drive
> hdh: SAMSUNG SV6004H, ATA DISK drive
>
> No problems.
>
> -- v --
>
> v@iki.fi
> -
> 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/
prev parent reply other threads:[~2002-01-19 14:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-19 17:11 Sharing Interrupt+HPT366 Problem on BP6 Anton Tinchev
2002-01-19 9:44 ` Martin Eriksson
2002-01-19 11:25 ` Ville Herva
2002-01-20 0:51 ` Anton Tinchev [this message]
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=3C4A1475.4D0BB1F6@top.bg \
--to=atl@top.bg \
--cc=linux-kernel@vger.kernel.org \
--cc=vherva@niksula.hut.fi \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.