Re: Obscure ethernet/IDE trouble
W. Paul Mills wrote: [EMAIL PROTECTED] (Adam C Powell IV) writes: William T Wilson wrote: They probably aren't, but based on what you have to say here, I'd check and make sure that your network card isn't sharing an interrupt with your ide interface. Ahem, from the original post: Adam C Powell IV wrote: Greetings, [snip] There shouldn't be an IRQ conflict, because the net cards are on IRQs 10 and 5, and the ide0 and ide1 are at 14 and 15 respectively. I tried network stop; ifconfig eth0 down; rmmod 3c59x; modprobe 3c59x; network start but the network is still dead. It remains dead until I do a full halt and power down, after which it comes back- until the next disk access. Other ideas? Could be ioport conflict. I've seen times when boot-up messages were incorrect on IRQ settings. So it is wise to look around in /proc to verify everything. Akhaa! You are correct. IRQ 10 on one ethernet card was shared with some bridge device, and also with a PCI sound card which was installed about when this trouble started happening. Moving the cards around seems to have done the trick. The sound card still conflicts with some other bridge device, I'll try moving it around and see if that helps. (If I were a little more adventurous I'd try assigning IRQs directly in the BIOS...) *** Running Debian Linux *** * For God so loved the world that He gave his only begotten Son, * * that whoever believes in Him should not perish...John 3:16 * * W. Paul Mills * Topeka, Kansas, U.S.A. * * EMAIL= [EMAIL PROTECTED] * WWW= http://Mills-USA.com/ * * Bill, I was there several years ago, why would I want to go back? * * pgp public key on keyservers everywhere? */ Cool. -Adam P. (New creative .sig coming any day now...)
Re: Obscure ethernet/IDE trouble
[EMAIL PROTECTED] (Adam C Powell IV) writes: William T Wilson wrote: On Fri, 3 Sep 1999, Adam C Powell IV wrote: I get this all the time when I try to access a drive that is in sleep mode. It takes it a minute or two and then it comes back to life and works normally. I have an old '96 era Intel Triton motherboard. Okay, but why would my drives be sleeping? This happens during the first disk access after a net access, could the net driver be putting the drives to sleep? And why does resetting the IDE interfaces kill my networking ability? They probably aren't, but based on what you have to say here, I'd check and make sure that your network card isn't sharing an interrupt with your ide interface. Ahem, from the original post: Adam C Powell IV wrote: Greetings, [snip] There shouldn't be an IRQ conflict, because the net cards are on IRQs 10 and 5, and the ide0 and ide1 are at 14 and 15 respectively. I tried network stop; ifconfig eth0 down; rmmod 3c59x; modprobe 3c59x; network start but the network is still dead. It remains dead until I do a full halt and power down, after which it comes back- until the next disk access. Other ideas? Could be ioport conflict. I've seen times when boot-up messages were incorrect on IRQ settings. So it is wise to look around in /proc to verify everything. -- *** Running Debian Linux *** * For God so loved the world that He gave his only begotten Son, * * that whoever believes in Him should not perish...John 3:16 * * W. Paul Mills * Topeka, Kansas, U.S.A. * * EMAIL= [EMAIL PROTECTED] * WWW= http://Mills-USA.com/ * * Bill, I was there several years ago, why would I want to go back? * * pgp public key on keyservers everywhere? */ --
Re: Obscure ethernet/IDE trouble
In article [EMAIL PROTECTED] you wrote:
Greetings,
I'm having bizarre troubles with the base 2.1 system (2.0.36-scsimod) on
an Abit BP6 dual-celeron system with Triton IDE DMA chipset and twin
3C905 ethernet cards. After my first net access (via eth0), be it ping
or apt-get update or whatever, the next disk access causes an IRQ
problem:
hda: irq timeout: status=0x58 { DriveReady SeekComplete DataRequest }
hda: disabled DMA
hdb: disabled DMA
[same for hdc and hdd]
ide1: reset: success
ide0: reset: success
so IDE-DMA gets dropped and the interfaces reset, after which the net is
inaccessible!
I was getting the 'DriveReady SeekComplete DataRequest' error and
related hard drive problems after I selected the 'use DMA when
available' when configging the kernel source. Although I don't
have the flakey chipset mentioned in the help for this option,
deselecting the option fixed the problems.
Rick
--
Re: Obscure ethernet/IDE trouble
On Thu, 2 Sep 1999, rick wrote: I was getting the 'DriveReady SeekComplete DataRequest' error and related hard drive problems after I selected the 'use DMA when available' when configging the kernel source. Although I don't I get this all the time when I try to access a drive that is in sleep mode. It takes it a minute or two and then it comes back to life and works normally. I have an old '96 era Intel Triton motherboard. Never occurs on a drive that's in standby mode. Only the full drive shut off mode causes it.
Re: Obscure ethernet/IDE trouble
rick wrote:
In article [EMAIL PROTECTED] you wrote:
Greetings,
I'm having bizarre troubles with the base 2.1 system (2.0.36-scsimod) on
an Abit BP6 dual-celeron system with Triton IDE DMA chipset and twin
3C905 ethernet cards. After my first net access (via eth0), be it ping
or apt-get update or whatever, the next disk access causes an IRQ
problem:
hda: irq timeout: status=0x58 { DriveReady SeekComplete DataRequest }
hda: disabled DMA
hdb: disabled DMA
[same for hdc and hdd]
ide1: reset: success
ide0: reset: success
so IDE-DMA gets dropped and the interfaces reset, after which the net is
inaccessible!
I was getting the 'DriveReady SeekComplete DataRequest' error and
related hard drive problems after I selected the 'use DMA when
available' when configging the kernel source. Although I don't
have the flakey chipset mentioned in the help for this option,
deselecting the option fixed the problems.
I'm using the 2.0.36-scsimod kernel which comes with the base_2.1. I don't
think
this uses DMA by default. Even the newer .config files don't come with that
config
flag set, from what I've seen.
William T Wilson wrote:
On Thu, 2 Sep 1999, rick wrote:
I was getting the 'DriveReady SeekComplete DataRequest' error and
related hard drive problems after I selected the 'use DMA when
available' when configging the kernel source. Although I don't
I get this all the time when I try to access a drive that is in sleep
mode. It takes it a minute or two and then it comes back to life and
works normally. I have an old '96 era Intel Triton motherboard.
Okay, but why would my drives be sleeping? This happens during the first disk
access
after a net access, could the net driver be putting the drives to sleep? And
why
does resetting the IDE interfaces kill my networking ability?
Example: I cold boot, login as root, and can ping to my heart's delight, then I
dselect- update, and it manages to download the first 20K or so with no
problem,
then this IDE error, and the net dies!
Freaky, eh?
Thanks,
-Adam P.
Re: Obscure ethernet/IDE trouble
On Fri, 3 Sep 1999, Adam C Powell IV wrote: I get this all the time when I try to access a drive that is in sleep mode. It takes it a minute or two and then it comes back to life and works normally. I have an old '96 era Intel Triton motherboard. Okay, but why would my drives be sleeping? This happens during the first disk access after a net access, could the net driver be putting the drives to sleep? And why does resetting the IDE interfaces kill my networking ability? They probably aren't, but based on what you have to say here, I'd check and make sure that your network card isn't sharing an interrupt with your ide interface.
Re: Obscure ethernet/IDE trouble
William T Wilson wrote: On Fri, 3 Sep 1999, Adam C Powell IV wrote: I get this all the time when I try to access a drive that is in sleep mode. It takes it a minute or two and then it comes back to life and works normally. I have an old '96 era Intel Triton motherboard. Okay, but why would my drives be sleeping? This happens during the first disk access after a net access, could the net driver be putting the drives to sleep? And why does resetting the IDE interfaces kill my networking ability? They probably aren't, but based on what you have to say here, I'd check and make sure that your network card isn't sharing an interrupt with your ide interface. Ahem, from the original post: Adam C Powell IV wrote: Greetings, [snip] There shouldn't be an IRQ conflict, because the net cards are on IRQs 10 and 5, and the ide0 and ide1 are at 14 and 15 respectively. I tried network stop; ifconfig eth0 down; rmmod 3c59x; modprobe 3c59x; network start but the network is still dead. It remains dead until I do a full halt and power down, after which it comes back- until the next disk access. Other ideas? That the IDE reset an network failure always happen at the exact same time (and I've tried about 20 times now, so yes, it's repeatable) suggests the two things might be linked... I just got a new box with a CD-R, so I'm going to try to burn a Debian image then install the CD on the dual-celeron and just install the system from that. This is getting old. If it persists with the Slink install, then I've got bigger problems. :-( Thanks very much for your efforts! -Adam P.
Re: Obscure ethernet/IDE trouble
[EMAIL PROTECTED] (Adam C Powell IV) writes:
Greetings,
I'm having bizarre troubles with the base 2.1 system (2.0.36-scsimod) on
an Abit BP6 dual-celeron system with Triton IDE DMA chipset and twin
3C905 ethernet cards. After my first net access (via eth0), be it ping
or apt-get update or whatever, the next disk access causes an IRQ
problem:
hda: irq timeout: status=0x58 { DriveReady SeekComplete DataRequest }
hda: disabled DMA
hdb: disabled DMA
[same for hdc and hdd]
ide1: reset: success
ide0: reset: success
so IDE-DMA gets dropped and the interfaces reset, after which the net is
inaccessible!
There shouldn't be an IRQ conflict, because the net cards are on IRQs 10
and 5, and the ide0 and ide1 are at 14 and 15 respectively. I tried
network stop; ifconfig eth0 down; rmmod 3c59x; modprobe 3c59x; network
start but the network is still dead. It remains dead until I do a full
halt and power down, after which it comes back- until the next disk
access.
Okay, here's another: I halt, hit reset, it boots, and now I get:
eth0: Host error, FIFO diagnostic register 8000.
repeated over and over, interspersed with another error message which I
can't see (it's scrolling too fast) except that it ends in Temporarily
disabling functions. Sometimes. Sometimes I just don't see this
problem at all. But it sounds related to the other problems.
First, you need to look around in your /var/log/ files to see if
you can learn more about your error.
Second look at /proc/ioports and /proc/interrupts (and perhaps others)
for any hints at what is going on.
--
*** Running Debian Linux ***
* For God so loved the world that He gave his only begotten Son, *
* that whoever believes in Him should not perish...John 3:16 *
* W. Paul Mills * Topeka, Kansas, U.S.A. *
* EMAIL= [EMAIL PROTECTED] * WWW= http://Mills-USA.com/ *
* Bill, I was there several years ago, why would I want to go back? *
* pgp public key on keyservers everywhere? */
--
Obscure ethernet/IDE trouble
Greetings,
I'm having bizarre troubles with the base 2.1 system (2.0.36-scsimod) on
an Abit BP6 dual-celeron system with Triton IDE DMA chipset and twin
3C905 ethernet cards. After my first net access (via eth0), be it ping
or apt-get update or whatever, the next disk access causes an IRQ
problem:
hda: irq timeout: status=0x58 { DriveReady SeekComplete DataRequest }
hda: disabled DMA
hdb: disabled DMA
[same for hdc and hdd]
ide1: reset: success
ide0: reset: success
so IDE-DMA gets dropped and the interfaces reset, after which the net is
inaccessible!
There shouldn't be an IRQ conflict, because the net cards are on IRQs 10
and 5, and the ide0 and ide1 are at 14 and 15 respectively. I tried
network stop; ifconfig eth0 down; rmmod 3c59x; modprobe 3c59x; network
start but the network is still dead. It remains dead until I do a full
halt and power down, after which it comes back- until the next disk
access.
Okay, here's another: I halt, hit reset, it boots, and now I get:
eth0: Host error, FIFO diagnostic register 8000.
repeated over and over, interspersed with another error message which I
can't see (it's scrolling too fast) except that it ends in Temporarily
disabling functions. Sometimes. Sometimes I just don't see this
problem at all. But it sounds related to the other problems.
I suppose I could get a CD-ROM and buy a slink CD, but that would cost
more money and take more time and not necessarily solve the problem. I
can't download the system of course because the net is dead. Maybe I
should try installing RH6 from the net, using the more recent drivers,
and then somehow get Debian with a more recent kernel into another
partition... Is there a base2_2.tgz that I haven't been able to find?
So that's the problem as it exists today. Now for some history.
The funny thing is that this problem didn't exist until I went into the
BIOS and manually autodetected the hard drive configurations. You
see, I bought four identical hard drives to make a RAID5 array (haven't
tried this, so don't reply on this subject, I know it might not be
possible), but one autodetected slightly differently from the others.
Three autodetected as 16 heads, the fourth as 255 heads, so the
partition sizes weren't identical, which I think is a no-no for RAID.
So, figuring the fourth was defective, I returned it for a new one
(which also autodetected as 255 heads).
But in the meantime while waiting for the new drive, I had installed a
very nice slink/GNOME system on small identical partitions of the
original three drives (so I could later stripe large partitions
together). The network was fine, everything was great.
Then the new drive arrived, and autodetected as 255 heads, and I was
very sad. So I looked around the BIOS, where there was a hard drive
autodetect function, and I found I could switch the configuration to 16
heads. Awesome! So, I did so, and re-partitioned, all the small and
large partitions were the same size across all the disks, cool. It
installed, it booted, it networked, it was grand.
Then I upgraded to potato. (Why? I don't know, but had something to do
with the newer GNOME updates.) This happened to be at the time a couple
of days ago when netbase had some broken/missing dependencies, so when I
rebooted, the network didn't work. (Of course, I didn't connect the two
problems until the same trouble came up on my laptop...)
So I decided to go into the BIOS and configure all of the IDE drives
manually in the 16-head setup. This didn't solve the problem, so I
figured I had a hosed system, and did a complete reinstall.
Since then, I have had the problem described above. I tried undoing the
16-head config busines, but the problem persists! I unplugged the hard
drives, rebooted, plugged them in, reinstalled, no luck. (I reinstalled
about five times last night :-)
On some of the reinstalls, I tried to use both the nfs and 3c59x
modules, but this caused fatal ethernet errors before I could put in the
first base system disk. But this is a separate problem.
So I'm all out of ideas. Running out of hope. Help me Obi-wan Kenobe,
you're my only chance. Please. Someone. I don't like having a dead
system, and I've worked so hard for it- it would be a cool system if it
only worked. And I'm surrounded by NT users who just buy stuff from
Dell, and don't want them to laugh at me for trying to assemble the box
and install Debian myself. :-)
Forever grateful to whoever can help,
-Adam P.
