linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Trever L. Adams" <tadams-lists@myrealbox.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [NETWORKING] Re: More ACPI funnies in 2.6.0test1
Date: 20 Jul 2003 17:02:01 -0400	[thread overview]
Message-ID: <1058734920.3012.9.camel@aurora.localdomain> (raw)
In-Reply-To: <1058714000.2488.2.camel@aurora.localdomain>

Ok, I was mistaken.  ACPI has nothing to do with it.  I got an actual
oops on shutdown without it.  It was in the ip 6 routing code.  Attached
is a bunch of alt-sysrq-p from when it gets stuck trying to down eth0. 
The program running at the time was ip... said something like ip 6 route
del in ps xa.  That was the program running.  The oopses were induced,
it is gzip because I have so many.  I will try to trigger the real oops
and show it here in this thread.

Actually, I will attach the log after I know that P and T in sysrq don't
leak passwords and such.  I am not entirely sure what is or isn't in
something like:

Jul 20 11:35:08 aurora kernel: spamd         S DBFB73FC 4278501676 
2156      1          2165  2145 (NOTLB)
Jul 20 11:35:08 aurora kernel: daed9eb4 00000082 daed9f44 dbfb73fc
c0137e13 c110fa18 dbe8d300 00000000 
Jul 20 11:35:08 aurora kernel:        7fffffff 00000006 00000006
c0123951 c02562a4 dbae8190 dbfb73fc daed9f44 
Jul 20 11:35:08 aurora kernel:        c0320880 00000020 00000005
00000005 c0232e59 dbae8190 dbfb73e4 00000000 

Anyway, I will continue to try and get a real oops.  I will post this
once someone lets me know it is safe.

Trever

On Sun, 2003-07-20 at 11:13, Trever L. Adams wrote:
> Alright, same board here, Asus A7N8X-Deluxe (nVidia nForce 2).  I have
> pci=noacpi.  However, if I leave ACPI on, I get two funnies:
> 
> 1) My disk seems to be more active, I hear it clicking much more
> 2) When eth0 gets shutdown on power off, it freezes.  However, I just
> tried to force it by manually shutting it off and it works fine.
> 
> I will provide the sysrq output later today when I will have more paper
> around to write down the output.
> 
> This box works fine with pci=noacpi and acpi=off.  So, I am just trying
> to figure out how to get it to work fine with the power stuff working,
> even if the irq related part is broken.  It would be nice to fix it all
> actually.
> 
> Trever
> --
> "It was as true as taxes is. And nothing's truer than them." -- Charles
> Dickens (1812-70)
> 
> -
> 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/
--
"The era of setting this up as a competition between Apple and Microsoft
is over, as far as I'm concerned." -- S. Jobs


      parent reply	other threads:[~2003-07-20 20:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-20 15:13 More ACPI funnies in 2.6.0test1 Trever L. Adams
2003-07-20 15:20 ` Sean Neakums
2003-07-20 15:33   ` Trever L. Adams
2003-07-20 21:02 ` Trever L. Adams [this message]

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=1058734920.3012.9.camel@aurora.localdomain \
    --to=tadams-lists@myrealbox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).