From: "JaniD++" <djani22@dynamicweb.hu>
To: "Denis Vlasenko" <vda@ilport.com.ua>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: ACPI: PCI Interrupt Link [LNKA] (IRQs *7)
Date: Thu, 1 Dec 2005 00:14:56 +0100 [thread overview]
Message-ID: <041f01c5f605$6b65cbf0$0400a8c0@dcccs> (raw)
In-Reply-To: 200511291015.55181.vda@ilport.com.ua
----- Original Message -----
From: "Denis Vlasenko" <vda@ilport.com.ua>
To: "JaniD++" <djani22@dynamicweb.hu>
Cc: <linux-kernel@vger.kernel.org>
Sent: Tuesday, November 29, 2005 9:15 AM
Subject: Re: ACPI: PCI Interrupt Link [LNKA] (IRQs *7)
> 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
Sorry! :-)
I am a little bit lazy... :-P
>
> >X-Mailer: Microsoft Outlook Express 6.00.2800.1437
> >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
>
> No wonder...
>
> > 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
(next mail)
> --
> vda
> -
> 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:31 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++
2005-11-30 23:14 ` JaniD++ [this message]
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='041f01c5f605$6b65cbf0$0400a8c0@dcccs' \
--to=djani22@dynamicweb.hu \
--cc=linux-kernel@vger.kernel.org \
--cc=vda@ilport.com.ua \
/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