All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Georg C. F. Greve" <greve@gnu.org>
To: "Nakajima, Jun" <jun.nakajima@intel.com>
Cc: Martin Loschwitz <madkiss@madkiss.org>,
	linux-kernel@vger.kernel.org, "Brown, Len" <len.brown@intel.com>,
	acpi-devel@lists.sourceforge.net
Subject: Re: PROBLEM: ACPI freezes 2.6.1 on boot
Date: Wed, 21 Jan 2004 22:21:52 +0100	[thread overview]
Message-ID: <m3u12pgfpr.fsf@reason.gnu-hamburg> (raw)
In-Reply-To: <7F740D512C7C1046AB53446D3720017361885C@scsmsx402.sc.intel.com> (Jun Nakajima's message of "Wed, 21 Jan 2004 08:32:50 -0800")

 || On Wed, 21 Jan 2004 08:32:50 -0800
 || "Nakajima, Jun" <jun.nakajima@intel.com> wrote: 

 nj> Right now I forwarded this to linux-acpi@intel.com, but copying
 nj> the ACPI mailing list acpi-devel@lists.sourceforge.net would be
 nj> helpful in general. Len can provide more specific directions for
 nj> reporting ACPI bugs.

Thanks.

FYI, there is a bug on the Linux kernel bugzilla corresponding to this
problem: 

         http://bugzilla.kernel.org/show_bug.cgi?id=1774

Regards,
Georg

-- 
Georg C. F. Greve                                       <greve@gnu.org>
Free Software Foundation Europe	                 (http://fsfeurope.org)
Brave GNU World	                           (http://brave-gnu-world.org)

WARNING: multiple messages have this Message-ID (diff)
From: "Georg C. F. Greve" <greve@gnu.org>
To: "Nakajima, Jun" <jun.nakajima@intel.com>
Cc: "Martin Loschwitz" <madkiss@madkiss.org>,
	<linux-kernel@vger.kernel.org>,
	"Brown, Len" <len.brown@intel.com>,
	<acpi-devel@lists.sourceforge.net>
Subject: Re: PROBLEM: ACPI freezes 2.6.1 on boot
Date: Wed, 21 Jan 2004 22:21:52 +0100	[thread overview]
Message-ID: <m3u12pgfpr.fsf@reason.gnu-hamburg> (raw)
In-Reply-To: <7F740D512C7C1046AB53446D3720017361885C@scsmsx402.sc.intel.com> (Jun Nakajima's message of "Wed, 21 Jan 2004 08:32:50 -0800")

 || On Wed, 21 Jan 2004 08:32:50 -0800
 || "Nakajima, Jun" <jun.nakajima@intel.com> wrote: 

 nj> Right now I forwarded this to linux-acpi@intel.com, but copying
 nj> the ACPI mailing list acpi-devel@lists.sourceforge.net would be
 nj> helpful in general. Len can provide more specific directions for
 nj> reporting ACPI bugs.

Thanks.

FYI, there is a bug on the Linux kernel bugzilla corresponding to this
problem: 

         http://bugzilla.kernel.org/show_bug.cgi?id=1774

Regards,
Georg

-- 
Georg C. F. Greve                                       <greve@gnu.org>
Free Software Foundation Europe	                 (http://fsfeurope.org)
Brave GNU World	                           (http://brave-gnu-world.org)

  reply	other threads:[~2004-01-21 21:21 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-21 16:32 PROBLEM: ACPI freezes 2.6.1 on boot Nakajima, Jun
2004-01-21 16:32 ` Nakajima, Jun
2004-01-21 21:21 ` Georg C. F. Greve [this message]
2004-01-21 21:21   ` Georg C. F. Greve
     [not found]   ` <m3u12pgfpr.fsf-glUV91rXKAHWIjgkaejU9x2eb7JE58TQ@public.gmane.org>
2004-01-21 22:29     ` Georg C. F. Greve
2004-01-21 22:29       ` Georg C. F. Greve
     [not found]       ` <m3ptddgckg.fsf-glUV91rXKAHWIjgkaejU9x2eb7JE58TQ@public.gmane.org>
2004-01-22 12:08         ` Karol Kozimor
2004-01-22 12:08           ` [ACPI] " Karol Kozimor
     [not found]           ` <20040122120854.GB3534-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>
2004-01-22 13:59             ` Mikael Pettersson
2004-01-22 13:59               ` [ACPI] " Mikael Pettersson
     [not found]               ` <16399.55109.244040.516731-mKzD8scclNAGILsNoAPbNA@public.gmane.org>
2004-01-22 14:05                 ` Karol Kozimor
2004-01-22 14:05                   ` [ACPI] " Karol Kozimor
     [not found]                   ` <20040122140546.GD5194-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>
2004-01-22 14:28                     ` Luca Capello
2004-01-22 17:15                 ` Linus Torvalds
2004-01-22 17:15                   ` [ACPI] " Linus Torvalds
     [not found]                   ` <Pine.LNX.4.58.0401220900510.2123-Xqd2YWsQM6mXDw4h08c5KA@public.gmane.org>
2004-01-22 17:49                     ` Mikael Pettersson
2004-01-22 17:49                       ` [ACPI] " Mikael Pettersson
2004-01-22 14:08             ` Georg C. F. Greve
2004-01-22 14:08               ` [ACPI] " Georg C. F. Greve
     [not found]               ` <m3browulc7.fsf-glUV91rXKAHWIjgkaejU9x2eb7JE58TQ@public.gmane.org>
2004-01-22 14:26                 ` Georg C. F. Greve
2004-01-22 14:26                   ` [ACPI] " Georg C. F. Greve
  -- strict thread matches above, loose matches on Subject: below --
2004-01-21 21:57 Brown, Len
2004-01-21 21:57 ` Brown, Len
2004-01-21 11:12 Georg C. F. Greve
2004-01-21 15:35 ` Martin Loschwitz
2004-01-21 16:12   ` Georg C. F. Greve
     [not found] ` <m3isj5a73u.fsf-glUV91rXKAHWIjgkaejU9x2eb7JE58TQ@public.gmane.org>
2004-01-21 18:56   ` Linus Torvalds
2004-01-21 18:56     ` Linus Torvalds
     [not found]     ` <Pine.LNX.4.58.0401211051530.2123-Xqd2YWsQM6mXDw4h08c5KA@public.gmane.org>
2004-01-21 21:15       ` Georg C. F. Greve
2004-01-21 21:15         ` Georg C. F. Greve
     [not found]         ` <m3d69dhukz.fsf-glUV91rXKAHWIjgkaejU9x2eb7JE58TQ@public.gmane.org>
2004-01-21 22:18           ` Linus Torvalds
2004-01-21 22:18             ` Linus Torvalds

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=m3u12pgfpr.fsf@reason.gnu-hamburg \
    --to=greve@gnu.org \
    --cc=acpi-devel@lists.sourceforge.net \
    --cc=jun.nakajima@intel.com \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=madkiss@madkiss.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.