From: "JaniD++" <djani22@dynamicweb.hu>
To: "Carlos Martín" <carlosmn@gmail.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: ACPI: PCI Interrupt Link [LNKA] (IRQs *7)
Date: Thu, 1 Dec 2005 00:18:57 +0100 [thread overview]
Message-ID: <042001c5f605$6bd5cbd0$0400a8c0@dcccs> (raw)
In-Reply-To: fe726f4e0511290736w6931ec83q@mail.gmail.com
Hi,
----- Original Message -----
From: "Carlos Martín" <carlosmn@gmail.com>
To: "JaniD++" <djani22@dynamicweb.hu>
Cc: <linux-kernel@vger.kernel.org>; "Denis Vlasenko" <vda@ilport.com.ua>
Sent: Tuesday, November 29, 2005 4:36 PM
Subject: Re: ACPI: PCI Interrupt Link [LNKA] (IRQs *7)
> On 29/11/05, Denis Vlasenko <vda@ilport.com.ua> wrote:
> > On Monday 28 November 2005 18:05, JaniD++ wrote:
> > >References: <Pine.LNX.4.60.0511270409430.30055@kepler.fjfi.cvut.cz>
<43892897.9020900@vc.cvut.cz>
<Pine.LNX.4.61.0511270927130.14029@yvahk01.tjqt.qr>
> >
> > You abuse your reply button
> >
> > >X-Mailer: Microsoft Outlook Express 6.00.2800.1437
> > >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
> >
> > No wonder...
>
> Hey, MS bashing! Can I join in?
> Now, wouldn't it be sacrilege to post to any technical list with
> something like Outlook?
Sorry, i hate M$ generally, but.... :-P
(....i like outlook....
this is the one exception.)
> >
> > > 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? :-)
> >
> > I do not understand your question
>
> That's output from the kernel bootup-sequence, he's seen it and is
> asking if that is normal behavior/output.
>
> To answer the question, yes, it is perfectly normal to see that.
> That's just the kernel describing how the PCI IRQs are set up. You
> have nothing to worry about.
Thanks for the answer!
I ask that because i newer seen this format befor: "[LNKA] (IRQs *7)"
Thanks
Janos
>
> cmn
> --
> Carlos Martín Nieto http://www.cmartin.tk
>
> "¿Cómo voy a decir bobadas si soy mudo?" -- CACHAI
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2005-11-30 23:30 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 ` ACPI: PCI Interrupt Link [LNKA] (IRQs *7) JaniD++
2005-11-29 8:15 ` 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++ [this message]
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='042001c5f605$6bd5cbd0$0400a8c0@dcccs' \
--to=djani22@dynamicweb.hu \
--cc=carlosmn@gmail.com \
--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.