All of lore.kernel.org
 help / color / mirror / Atom feed
From: acme <saur@acmelabs.de>
To: linux-acpi@vger.kernel.org, kristen.c.accardi@intel.com,
	len.brown@intel.com
Subject: RE: 2.6.17-rc4-mm3 - kernel panic
Date: Thu, 25 May 2006 20:05:34 +0000	[thread overview]
Message-ID: <44760E0E.90408@acmelabs.de> (raw)

Hello Kristen,

does it make sense for me to patch? I meen, if you want me to dmesg, I 
need a clean boot. But the panic occurs on boot. Since your patch makes 
nothing but logging, this makes less sense for me.
And what is that dock thing, could my WOL on S3 and NIC problem also 
have something to do with that?

Btw.: Len, I've compiled the 2.6.16.18 kernel last night, with and 
without your latest acpi-release. The result was, with patch the system 
woke up one time and the second time it died, without your patch the 
system died the very first time sending a magic packet. Funny, but 
keyboard and powerbutton are always working.

Regards,

Andreas

             reply	other threads:[~2006-05-25 20:05 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-25 20:05 acme [this message]
2006-05-25 20:34 ` 2.6.17-rc4-mm3 - kernel panic Kristen Accardi
  -- strict thread matches above, loose matches on Subject: below --
2006-05-26 23:14 Andreas Saur
2006-05-26  6:08 Andreas Saur
2006-05-25 22:33 Andreas Saur
2006-05-25 18:55 Brown, Len
2006-05-25 18:55 ` Brown, Len
2006-05-24 22:52 Andreas Saur
2006-05-24  5:03 Brown, Len
2006-05-25 16:52 ` Kristen Accardi
2006-05-25 19:01 ` Kristen Accardi
2006-05-25 22:12   ` Pavel Machek
2006-05-25 22:17     ` Pavel Machek
2006-05-26  0:04       ` Kristen Accardi
2006-05-26  0:04         ` Kristen Accardi
2006-05-26  7:15         ` Pavel Machek
2006-05-26  7:15           ` Pavel Machek
2006-05-26 18:29           ` Kristen Accardi
2006-05-26 18:29             ` Kristen Accardi
2006-05-30 10:25             ` Pavel Machek
2006-05-23 20:24 Andreas Saur

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=44760E0E.90408@acmelabs.de \
    --to=saur@acmelabs.de \
    --cc=kristen.c.accardi@intel.com \
    --cc=len.brown@intel.com \
    --cc=linux-acpi@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.