From: "JaniD++" <djani22@dynamicweb.hu>
To: <linux-kernel@vger.kernel.org>
Subject: ACPI: PCI Interrupt Link [LNKA] (IRQs *7)
Date: Mon, 28 Nov 2005 17:05:52 +0100 [thread overview]
Message-ID: <018c01c5f435$9e548370$0400a8c0@dcccs> (raw)
In-Reply-To: Pine.LNX.4.61.0511270927130.14029@yvahk01.tjqt.qr
Hi,
Nov 28 16:41:36 192.168.2.50 kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs
*7)
Nov 28 16:41:36 192.168.2.50 kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs
*7)
Nov 28 16:41:36 192.168.2.50 kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs
*7)
Nov 28 16:41:36 192.168.2.50 kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs
*7)
Nov 28 16:41:36 192.168.2.50 kernel: ACPI: PCI Interrupt Link [LNKE] (IRQs 3
4 5 6 7 10 11 12 14 15) *0, disabled.
Nov 28 16:41:36 192.168.2.50 kernel: ACPI: PCI Interrupt Link [LNKF] (IRQs 3
4 5 6 7 10 11 12 14 15) *0, disabled.
Nov 28 16:41:36 192.168.2.50 kernel: ACPI: PCI Interrupt Link [LNKG] (IRQs 3
4 5 6 7 10 11 12 14 15) *0, disabled.
Nov 28 16:41:36 192.168.2.50 kernel: ACPI: PCI Interrupt Link [LNKH] (IRQs 3
4 5 6 7 *10 11 12 14 15)
This is normal? :-)
Thanks,
Janos
next prev parent reply other threads:[~2005-11-28 16:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-27 3:23 PC speaker beeping on high CPU loads on an nForce2 Martin Drab
2005-11-27 3:31 ` Petr Vandrovec
2005-11-27 13:39 ` Martin Drab
2005-11-28 15:50 ` Jan Engelhardt
2005-11-28 16:05 ` JaniD++ [this message]
2005-11-29 8:15 ` ACPI: PCI Interrupt Link [LNKA] (IRQs *7) Denis Vlasenko
2005-11-29 15:36 ` Carlos Martín
2005-11-30 17:35 ` Jan Engelhardt
2005-11-30 23:25 ` JaniD++
2005-11-30 23:18 ` JaniD++
2005-11-30 23:14 ` JaniD++
2005-11-27 6:11 ` PC speaker beeping on high CPU loads on an nForce2 Gene Heskett
2005-11-27 14:34 ` Ivan Yosifov
2005-11-27 17:56 ` Martin Drab
2005-11-27 18:33 ` Willy Tarreau
2005-11-27 21:38 ` Martin Drab
2005-11-27 19:10 ` Paul Jackson
-- strict thread matches above, loose matches on Subject: below --
2005-12-01 8:22 ACPI: PCI Interrupt Link [LNKA] (IRQs *7) Brown, Len
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='018c01c5f435$9e548370$0400a8c0@dcccs' \
--to=djani22@dynamicweb.hu \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.