topic Re: liunx system log error in Operating System - Linux

liunx system log error

hany elromany — Tue, 10 Mar 2009 08:09:45 GMT

i have three serves Hp DL380R05 E5310 with Linux release
every time i check the server i see these error
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.IP2P._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.IPTA._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.IPTB._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PT02._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PT02.IPE4._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PT02.IPE4.IPE1._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PT02.IPE4.IPE2._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PT02.IPE4.IPE3._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PT03._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PT04._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PT06._PRT]
ACPI: PCI Interrupt Link [LNKA] (IRQs *5 7 10 11)
ACPI: PCI Interrupt Link [LNKB] (IRQs 5 *7 10 11)
ACPI: PCI Interrupt Link [LNKC] (IRQs 5 7 *10 11)
ACPI: PCI Interrupt Link [LNKD] (IRQs 5 7 *10 11)
ACPI: PCI Interrupt Link [LNKE] (IRQs 5 7 10 11) *0, disabled.
ACPI: PCI Interrupt Link [LNKF] (IRQs *5 7 10 11)
ACPI: PCI Interrupt Link [LNKG] (IRQs 5 7 *10 11)
ACPI: PCI Interrupt Link [LNKH] (IRQs 5 *7 10 11)

so why this error how i fix it?

Re: liunx system log error

Ivan Krastev — Tue, 10 Mar 2009 08:36:29 GMT

This is not an error. This is an informational message when kernel boots - boot.msg file.

regards,
ivan

Re: liunx system log error

Matti_Kurkela — Tue, 10 Mar 2009 08:43:06 GMT

Welcome to the ITRC Forums!

Not all log messages are errors.

These are informative messages generated when the kernel is starting up. It is reading the ACPI tables included in the system firmware, describing the hardware interrupt routing settings.

These messages are printed out so that if there is a problem at the hardware set-up causing the system to freeze at boot, you can see exactly how far the boot procedure got.

The "disabled" at the PCI interrupt link LNKE simply means that link is not used in your system board. You would have to be a fairly advanced hardware engineer to know if this is true or not. If the LNKE is actually in use, then the ACPI table contains an error and you would need an updated BIOS firmware to fix it. But if LNKE is actually not connected to anything on the system board, disabling it is the correct thing to do.

If you're building prototype PCI cards or developing a driver for new hardware, these messages might contain useful information for you. But in that case, you would already have read the PCI and ACPI specifications and could understand these messages better than I do.

But if you're using well-known, supported hardware with production-quality drivers, you won't need to care about this.

MK

Re: liunx system log error

hany elromany — Fri, 13 Mar 2009 20:37:44 GMT

hii
i update the BIOS after that i check the OS log error with dmesg | tail -1000:

ACPI: PCI Interrupt 0000:00:1c.1[B] -> GSI 17 (level, low) -> IRQ 177
ACPI: PCI Interrupt 0000:00:1d.0[A] -> GSI 16 (level, low) -> IRQ 169
ACPI: PCI Interrupt 0000:00:1d.1[B] -> GSI 17 (level, low) -> IRQ 177
GSI 18 sharing vector 0xB9 and IRQ 18
ACPI: PCI Interrupt 0000:00:1d.2[C] -> GSI 18 (level, low) -> IRQ 185
GSI 19 sharing vector 0xC1 and IRQ 19
ACPI: PCI Interrupt 0000:00:1d.3[D] -> GSI 19 (level, low) -> IRQ 193
ACPI: PCI Interrupt 0000:00:1d.7[A] -> GSI 16 (level, low) -> IRQ 169
ACPI: PCI Interrupt 0000:00:1f.1[A] -> GSI 17 (level, low) -> IRQ 177
ACPI: PCI Interrupt 0000:0a:00.0[A] -> GSI 16 (level, low) -> IRQ 169
ACPI: PCI Interrupt 0000:0a:01.0[A] -> GSI 17 (level, low) -> IRQ 177
ACPI: PCI Interrupt 0000:0a:02.0[A] -> GSI 18 (level, low) -> IRQ 185
ACPI: PCI Interrupt 0000:0b:00.0[A] -> GSI 16 (level, low) -> IRQ 169
ACPI: PCI Interrupt 0000:0c:08.0[A] -> GSI 16 (level, low) -> IRQ 169
ACPI: PCI Interrupt 0000:0f:08.0[A] -> GSI 17 (level, low) -> IRQ 177
ACPI: PCI Interrupt 0000:03:00.0[A] -> GSI 16 (level, low) -> IRQ 169
ACPI: PCI Interrupt 0000:05:00.0[A] -> GSI 17 (level, low) -> IRQ 177

are this massage are error?if it how to fix it?
regards
hany

Re: liunx system log error

Matti_Kurkela — Fri, 13 Mar 2009 22:13:04 GMT

Not an error.

Just a table showing how the PCI hardware interrupt lines are mapped to software interrupts handled by the kernel (or at least how the ACPI table of the BIOS *says* they are).

MK

Re: liunx system log error

hany elromany — Wed, 25 Mar 2009 08:48:18 GMT

hi
i check i found two things that it may help
1-the RAM take all load and the SWAP take nothing from load .
free RAM 17m and the SWAP 3855m
how i fix this?
2-when i check the fdisk -l it show this:
Disk /dev/cciss/c0d0: 293.4 GB, 293496628224 bytes
255 heads, 32 sectors/track, 70249 cylinders
Units = cylinders of 8160 * 512 = 4177920 bytes

Device Boot Start End Blocks Id System
/dev/cciss/c0d0p1 * 1 70249 286615904 83 Linux

Disk /dev/cciss/c0d1: 146.7 GB, 146778685440 bytes
255 heads, 32 sectors/track, 35132 cylinders
Units = cylinders of 8160 * 512 = 4177920 bytes

Device Boot Start End Blocks Id System
/dev/cciss/c0d1p1 * 1 52 208813+ 83 Linux
Partition 1 does not end on cylinder boundary.
/dev/cciss/c0d1p2 8912 35132 106981680 83 Linux
/dev/cciss/c0d1p3 52 1079 4192965 82 Linux swap
Partition 3 does not end on cylinder boundary.
/dev/cciss/c0d1p4 1079 8911 31953285 5 Extended
Partition 4 does not end on cylinder boundary.
/dev/cciss/c0d1p5 1079 8911 31953253+ 83 Linux

this may happen the error.
how i fix it?
reagrds
hany

Re: liunx system log error

Matti_Kurkela — Wed, 25 Mar 2009 15:43:14 GMT

1.) RAM is much faster than swap, so swap is used only when all RAM is already used. You don't want your servers to use swap on a regular basis. When actually using swap, your system is trading away I/O and processing capacity to compensate for the lack of RAM.

You should think of the swap as an emergency reserve for short-term memory overload spikes.

So, not a problem.

2.) "Partition 1 does not end on cylinder boundary" is a problem only if you're dual-booting your Linux servers to some old OS that cannot use the LBA method of addressing the disk. (Anything over 8.4 GB is considered "large" in this sense.) Otherwise, this message is completely meaningless.

Your partition table indicates your system has only Linux installed. So you don't need to care about this.

MK