> > The output of lspci -v:
> [...]
> > 00:0e.0 Ethernet controller: Intel Corporation 82557 [Ethernet Pro 100] (rev 08)
> > Subsystem: Intel Corporation 82559 Fast Ethernet LAN on Motherboard
> > Flags: bus master, medium devsel, latency 64, IRQ 5
>
> Hmm, this is the device
The output of lspci -v:
[...]
00:0e.0 Ethernet controller: Intel Corporation 82557 [Ethernet Pro 100] (rev 08)
Subsystem: Intel Corporation 82559 Fast Ethernet LAN on Motherboard
Flags: bus master, medium devsel, latency 64, IRQ 5
Hmm, this is the device you reported
On Mon, 27 Nov 2000, Maciej W. Rozycki wrote:
> On Mon, 27 Nov 2000, Mr. Big wrote:
>
> > But maybe the /proc/interrupts could be usefull:
> >CPU0 CPU1
> > 0: 413111 0 XT-PIC timer
> > 1:687 0
> > How could an APIC 'forget' how to deliver the interrupts? Could this mean
> > a problem with the mainboard, or with the CPU?
>
> Do you have an USB host controller in your system? If so, could you
> please send me an output of `/sbin/lspci' and the contents of
> /proc/interrupts? I
> > In the afternoon we decided to put back the original mainboard+ram+cpu.
> > We booted the kernel described above.
>
> With `noapic', I assume?
Yes, of course
>
> It could be hardware or a driver or whatever. Suggest you
> go to a more recent kernel and if the problems persist,
> swap
In the afternoon we decided to put back the original mainboard+ram+cpu.
We booted the kernel described above.
With `noapic', I assume?
Yes, of course
It could be hardware or a driver or whatever. Suggest you
go to a more recent kernel and if the problems persist,
swap hardware out.
How could an APIC 'forget' how to deliver the interrupts? Could this mean
a problem with the mainboard, or with the CPU?
Do you have an USB host controller in your system? If so, could you
please send me an output of `/sbin/lspci' and the contents of
/proc/interrupts? I wonder if
On Mon, 27 Nov 2000, Maciej W. Rozycki wrote:
On Mon, 27 Nov 2000, Mr. Big wrote:
But maybe the /proc/interrupts could be usefull:
CPU0 CPU1
0: 413111 0 XT-PIC timer
1:687 0 XT-PIC keyboard
2: 0
> Alan Cox <[EMAIL PROTECTED]> writes:
>
> > > benn compiled into the kernel, and not as a module) always gave the
> > > errors:
> > >
> > > eth0: Transmit timed out: status 0050 0090 at 134704418/134704432
> > > eth0: Trying to restart the transmitter...
> >
> > Known problem. This one
> > benn compiled into the kernel, and not as a module) always gave the
> > errors:
> >
> > eth0: Transmit timed out: status 0050 0090 at 134704418/134704432
> > eth0: Trying to restart the transmitter...
>
> Known problem. This one might be fixed in current 2.2.18pre. SOme people
> see it
[1.]
Kernels 2.2.14, 2.2.17, 2.4.0-test11 crash with various errors
(I know this is too simple, but this is what I could say in one line)
[2.]
We're running a quite bussy site, and updateing our servers hardware quite
often. Since a while ago we're expecting many troubles, that usually end
with
[1.]
Kernels 2.2.14, 2.2.17, 2.4.0-test11 crash with various errors
(I know this is too simple, but this is what I could say in one line)
[2.]
We're running a quite bussy site, and updateing our servers hardware quite
often. Since a while ago we're expecting many troubles, that usually end
with
benn compiled into the kernel, and not as a module) always gave the
errors:
eth0: Transmit timed out: status 0050 0090 at 134704418/134704432
eth0: Trying to restart the transmitter...
Known problem. This one might be fixed in current 2.2.18pre. SOme people
see it some dont
Ok,
Alan Cox [EMAIL PROTECTED] writes:
benn compiled into the kernel, and not as a module) always gave the
errors:
eth0: Transmit timed out: status 0050 0090 at 134704418/134704432
eth0: Trying to restart the transmitter...
Known problem. This one might be fixed in current
14 matches
Mail list logo
