All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: linux-kernel@vger.kernel.org
Cc: Pavel Machek <pavel@suse.cz>, Andi Kleen <ak@suse.de>
Subject: Re: swsusp on x86-64 w/ nforce3
Date: Tue, 7 Sep 2004 01:10:35 +0200	[thread overview]
Message-ID: <200409070110.35826.rjw@sisk.pl> (raw)
In-Reply-To: <20040906203228.GA18105@atrey.karlin.mff.cuni.cz>

On Monday 06 of September 2004 22:32, Pavel Machek wrote:
> Hi!
> 
> > > Can you tell me, please, if swsusp, as in the 2.6.9-rc1-bk12 kernel, is 
> > > supposed to work on x86-64-based systems (specifically, with the nforce3 
> > > chipset)?
> > 
> > Anyway, on such a system (.config and the output of dmesg are attached), I 
get 
> > the following:
> > 
> > Stopping tasks: 
> > ==============================================================|
> > Freeing 
> > 
memory: ............................................................................................................|
> > Suspending devices... /critical section: counting pages to copy..[nosave 
pfn 
> > 0x59b]..................................................)
> > Alloc pagedir
> > ..[nosave pfn 
> > 
0x59b]................................................................................critical 
> > section/: done (40890 pa)
> > APIC error on CPU0: 80(08)
> 
> Try noapic?

The result is the same. :-(  It is quite strange, though, because I have:

rafael@albercik:~> cat /proc/interrupts
           CPU0
  0:     448292          XT-PIC  timer
  1:       1047          XT-PIC  i8042
  2:          0          XT-PIC  cascade
  5:        684          XT-PIC  ohci_hcd, NVidia nForce3
  8:          0          XT-PIC  rtc
  9:        839          XT-PIC  acpi, yenta
 10:          2          XT-PIC  ehci_hcd
 11:       3034          XT-PIC  SysKonnect SK-98xx, ohci_hcd, yenta, ohci1394
 12:       4520          XT-PIC  i8042
 14:       2522          XT-PIC  ide0
 15:       8635          XT-PIC  ide1
NMI:         74
LOC:     448090
ERR:          1
MIS:          0

but at the same time:

rafael@albercik:~> dmesg | grep -i apic
Bootdata ok (command line is root=/dev/hdc6 vga=792 resume=/dev/hdc3 noapic)
PCI bridge 00:0a from 10de found. Setting "noapic". Overwrite with "apic"
OEM ID: ASUSTeK  <6>Product ID: L5D          <6>APIC at: 0xFEE00000
Processor #0 15:4 APIC version 16
I/O APIC #1 Version 17 at 0xFEC00000.
Kernel command line: root=/dev/hdc6 vga=792 resume=/dev/hdc3 noapic 
console=tty0
Using local APIC NMI watchdog using perfctr0
Using local APIC timer interrupts.
Detected 12.468 MHz APIC timer.

The nolapic probably oopses, because the box sort of hanged when I set it, but 
I have to use the serial console to confirm it.

Regards,
RJW

-- 
For a successful technology, reality must take precedence over public 
relations, for nature cannot be fooled.
					-- Richard P. Feynman

  reply	other threads:[~2004-09-06 23:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-06 16:36 swsusp on x86-64 w/ nforce3 Rafael J. Wysocki
2004-09-06 19:23 ` Rafael J. Wysocki
2004-09-06 20:32   ` Pavel Machek
2004-09-06 23:10     ` Rafael J. Wysocki [this message]
2004-09-08 20:42   ` Tony Lindgren
2004-09-08 20:52     ` Rafael J. Wysocki
2004-09-09  1:18       ` Tony Lindgren
2004-09-09  7:06         ` Rafael J. Wysocki
2004-09-09 10:19         ` Rafael J. Wysocki
2004-09-09 22:28           ` Tony Lindgren

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=200409070110.35826.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=ak@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@suse.cz \
    /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.