From: Nick Warne <nick@linicks.net>
To: linux-kernel@vger.kernel.org
Subject: [QUESTION] Unnamed syslog kernel logs
Date: Mon, 29 Dec 2014 13:23:18 +0000 [thread overview]
Message-ID: <54A155C6.5050005@linicks.net> (raw)
Hello developers,
Not being very familiar with kernel debugging, I have a question about
strange syslogs.
History:
I have been trying to tie-down a strange problem on my headless AMD64
box - it occasionally just turns-off if just as if the power supply is
cut. It can happen anywhere between 2 months or 2 days - just intermittent.
Analysing logs (which when this occurs they do not report anything), I
noticed this in syslog (typical):
Dec 28 09:37:19 sauron kernel: ACPI: PCI Interrupt Link [APCL] enabled
at IRQ 22
Dec 28 09:37:19 sauron kernel: ACPI: PCI Interrupt Link [APC5] enabled
at IRQ 16
Dec 28 09:37:19 sauron kernel: 1030
Dec 28 09:37:19 sauron kernel: 0200
Dec 28 09:37:19 sauron kernel: 0110
Dec 28 09:37:19 sauron kernel: 0111
Dec 28 09:37:19 sauron kernel: 0113
Dec 28 09:37:19 sauron kernel: 0362
Dec 28 09:37:19 sauron kernel: ACPI: PCI Interrupt Link [APSI] enabled
at IRQ 21
Dec 28 09:37:19 sauron kernel: ACPI: PCI Interrupt Link [APSJ] enabled
at IRQ 20
I don't understand what the middle lines are telling me here?
Anyway, today I took the machine down, and removed ram a module (as I
found it's sister slot was bad) and also the graphics card as I don't
use it.
Now when I boot, these mysterious line have vanished from syslog:
ec 29 13:05:49 sauron kernel: ACPI: Enabled 1 GPEs in block 00 to 1F
Dec 29 13:05:49 sauron kernel: ACPI: PCI Interrupt Link [APCF] enabled
at IRQ 23
Dec 29 13:05:49 sauron kernel: ACPI: PCI Interrupt Link [APCL] enabled
at IRQ 22
Dec 29 13:05:49 sauron kernel: ACPI: PCI Interrupt Link [APSI] enabled
at IRQ 21
Dec 29 13:05:49 sauron kernel: ACPI: PCI Interrupt Link [APSJ] enabled
at IRQ 20
Dec 29 13:05:49 sauron kernel: ACPI: PCI Interrupt Link [APCH] enabled
at IRQ 23
is all I get now in that section.
Was the kernel attempting to tell me something was bad with them funny
unnamed lines?
Thanks for any help,
Regards,
Nick
--
"A bug in the code is worth two in the documentation."
http://linicks.net/
http://slackpi.linicks.net/
reply other threads:[~2014-12-29 13:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54A155C6.5050005@linicks.net \
--to=nick@linicks.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox