On Wed, 29 Nov 2000, Maciej W. Rozycki wrote:
> You appear to have the PIIX4 ISA bridge -- it contains an embedded ACPI
> controller. It has it's IRQ hardwired to 11. Try to move device IRQs
> away from it (by setting IRQ 11 to "ISA/Legacy" in BIOS). While I've not
> heard of ACPI IRQ problem
On Tue, 28 Nov 2000, Mr. Big wrote:
> Yes You are right. This Ether Express is integrated on the motherboard, so
> we couldn't get it out totally :( But there isn't any cable connected to
> it, we also doesn't have the driver in the kernel. This is the same with
> the USB too. Do You mind, that t
> > 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 yo
On Mon, 27 Nov 2000, Mr. Big wrote:
> We've disabled the apic, because there was a hint, that maybe there's some
> bug with the hardware or software on it. I belive that it's could be
> better to use the apic.
>
> The output of lspci -v:
[...]
> 00:0e.0 Ethernet controller: Intel Corporation 825
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:
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 0 XT-PIC cascade
> 7: 75
On Sunday 26 November 2000 19:36, Rik van Riel wrote:
> On Sun, 26 Nov 2000, Ingo Oeser wrote:
> > On Sun, Nov 26, 2000 at 10:49:50AM +1100, Andrew Morton wrote:
> > > You may also get some benefit from running:
> > >
> > > # echo "512 1024 1536" > /proc/sys/vm/freepages
> > >
> > > after booting.
> > 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
On Sun, 26 Nov 2000, Mr. Big wrote:
> 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
/pr
> > 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 hard
Previous day I followed the hint of Alan, and made a 2.2.14 kernel, with
the DAC960 driver taken from the 2.2.17, for these changes I've copied
the:
drivers/block/DAC960.c
drivers/block/DAC960.h
drivers/pci/oldrpoc.c
include/linux/pci.h
from the 2.2.17 sourcetree into the 2.2.14. Ok, it compiled.
On Sun, Nov 26, 2000 at 10:49:50AM +1100, Andrew Morton wrote:
> You may also get some benefit from running:
>
> # echo "512 1024 1536" > /proc/sys/vm/freepages
>
> after booting.
... which is a NOOP on recent 2.4.0-testX-kernels. So please
complain at Rik for this (CC'ed him) ;-)
It's simply
Nice report. Wish they were all like that.
Look:
"Mr. Big" wrote:
>
> I thought that the khttpd is guilty, I won't use it anymore. Next morning
> it crashed again, now without khttpd, without high load, without high
> memory usage, just the 3Com driver said:
> kernel: eth0: Interrupt posted bu
> 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 migh
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 curre
> Ok, I'll try. Since I'm not a kernel developer, I have the fool question,
> wether it is enough to overwrite the .c and .h files in the 2.2.14 source
> tree, or do I need to apply other changes too?
I believe that is all you need to do for that driver
-
To unsubscribe from this list: send the
> > 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 so
> 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
> mistak
[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
19 matches
Mail list logo
