lkml.org 
[lkml]   [2002]   [Jan]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: Disk corruption - Abit KT7, 2.2.19+ide patches
Date

> On Tue, Jan 15, 2002 at 11:40:49PM +0200, Ville Herva wrote:
> >
> > Hmm, do the pci ids map somehow to physical pci slots? It seems one
>
> Im not sure. Someone in the mailing list should know though. 8)
>
> > particular physical pci slot location is troublesome in our case. It
caused
> > problems with nic and even with a scsi adapter. Unfortunately I can't
> > remember which slot it was - I'll have to check (I _think_ it was the
third
> > counting from bottom).
> >
> > So I'm interested in the physical location of you nic...
>
> Ok. I can't check the machine in Wellington, but in the machine here.
> Not couting the AGP slot, the NIC is sitting in the third slot in the
> back of the box.
>
>
> I'd have to open it (later today when the office is closed) to comfirm
> its sitting in the 'third' PCI slot from the CPU.
>
> The NIC is the only PCI card in this machines. The video card being a
> basic AGP one. (This is the other difference with the machine in
> Wellington which has an old but expensive PCI video card.)
>
>
> The problem with moving the card, is that the problem exhibits very
> slowly. After the previous problems with the Seagate drive reseting and
> the computer finally crashing majorly I replaced the drive and
> everything seemed fine.
>
> Only now have I notice the problems.
>

sounds like you're using the shared irq slot, might want to verify that with
lspci -vvv to see if anything else is using an irq at the time that's the
same as the card in that slot. Also some places will do various special
things to one of the last pci slots, you should be able to find out by
looking in the manual. Some cards just dont play nicely with shared irqs.

Then there's always the locality to some other device in the case possibly
causing your problem. many reasons could cause the problem you're
describing. I'm not really sure how this is a linux problem though since
you mention it's occuring only in a certain physical slot.

-
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/

\
 
 \ /
  Last update: 2005-03-22 13:23    [W:0.083 / U:1.844 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site