"Kok, Auke" <[EMAIL PROTECTED]> writes:
> PERR+ set... not good - this certainly will cause major issues
Unfortunately some devices assert PERR without a good reason,
and it may do no special harm.
Should be handled and cleared, probably.
--
Krzysztof Halasa
-
To unsubscribe from this list: sen
William Montgomery <[EMAIL PROTECTED]> writes:
> I am able to analyze the primary bus while the using the card in the
> secondary and I see a very interesting thing on lockup - the primary
> side appears to be stuck on a read access to the memory mapped control
> regs of the LAN chip (82559) in wh
Kok, Auke wrote:
00:1e.0 PCI bridge: Intel Corp. 82801BA/CA/DB/EB/ER Hub interface to
PCI Bridge (rev 82) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR+ FastB2B-
Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=fa
William Montgomery wrote:
Krzysztof Halasa wrote:
William Montgomery <[EMAIL PROTECTED]> writes:
I am using a PCI analyzer and it shows the bus in an idle state after
the lockup. The PCI transactions just prior to the lockup show a
couple of interrupts from the card which appear to be han
Krzysztof Halasa wrote:
William Montgomery <[EMAIL PROTECTED]> writes:
I am using a PCI analyzer and it shows the bus in an idle state after
the lockup. The PCI transactions just prior to the lockup show a
couple of interrupts from the card which appear to be handled
correctly. Anything I
Krzysztof Halasa wrote:
William Montgomery <[EMAIL PROTECTED]> writes:
I am using a PCI analyzer and it shows the bus in an idle state after
the lockup. The PCI transactions just prior to the lockup show a
couple of interrupts from the card which appear to be handled
correctly. Anything I
William Montgomery <[EMAIL PROTECTED]> writes:
> I am using a PCI analyzer and it shows the bus in an idle state after
> the lockup. The PCI transactions just prior to the lockup show a
> couple of interrupts from the card which appear to be handled
> correctly. Anything I should be looking for
Krzysztof Halasa wrote:
William Montgomery <[EMAIL PROTECTED]> writes:
In an earlier post to the list I described a hard lockup condition
that occurs on linux kernels 2.4.22, 2.6.13, and 2.6.17 when using
a 4 port 10/100 fast ethernet card. The lockup is easily repeatable
and occurs on 2 o
William Montgomery <[EMAIL PROTECTED]> writes:
> In an earlier post to the list I described a hard lockup condition
> that occurs on linux kernels 2.4.22, 2.6.13, and 2.6.17 when using
> a 4 port 10/100 fast ethernet card. The lockup is easily repeatable
> and occurs on 2 out of 3 computers.
>
>
Kok, Auke wrote:
William Montgomery wrote:
Thanks for responding. I am very interested to find the source of
this problem.
Kok, Auke wrote:
William Montgomery wrote:
In an earlier post to the list I described a hard lockup condition
that occurs on linux kernels 2.4.22, 2.6.13, and 2.6.1
William Montgomery wrote:
Thanks for responding. I am very interested to find the source of this
problem.
Kok, Auke wrote:
William Montgomery wrote:
In an earlier post to the list I described a hard lockup condition
that occurs on linux kernels 2.4.22, 2.6.13, and 2.6.17 when using
a 4 por
Thanks for responding. I am very interested to find the source of this
problem.
Kok, Auke wrote:
William Montgomery wrote:
In an earlier post to the list I described a hard lockup condition
that occurs on linux kernels 2.4.22, 2.6.13, and 2.6.17 when using
a 4 port 10/100 fast ethernet card
William Montgomery wrote:
In an earlier post to the list I described a hard lockup condition
that occurs on linux kernels 2.4.22, 2.6.13, and 2.6.17 when using
a 4 port 10/100 fast ethernet card. The lockup is easily repeatable
and occurs on 2 out of 3 computers.
Further testing has revealed th
In an earlier post to the list I described a hard lockup condition
that occurs on linux kernels 2.4.22, 2.6.13, and 2.6.17 when using
a 4 port 10/100 fast ethernet card. The lockup is easily repeatable
and occurs on 2 out of 3 computers.
Further testing has revealed that the lockup can be preve
14 matches
Mail list logo
