All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ondrej Zary <linux@rainbow-software.org>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: linux-pm@lists.linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [linux-pm] Invalid opcode on resume from STR on Asus P4P800-VM
Date: Mon, 26 Apr 2010 21:55:05 +0200	[thread overview]
Message-ID: <201004262155.06949.linux@rainbow-software.org> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1004261512540.1764-100000@iolanthe.rowland.org>

On Monday 26 April 2010 21:17:27 Alan Stern wrote:
> On Mon, 26 Apr 2010, Ondrej Zary wrote:
> > Hello,
> > I'm trying to debug oops on resume from suspend-to-RAM on Asus P4P800-VM
> > mainboard. It crashes with invalid opcode (see below). The kernel is
> > 2.6.32-trunk from Debian but the same problem is present with vanilla
> > kernels - both newer and older (but screen remains blank most of the
> > time, only keyboard LEDs blink indicating an oops).
> >
> > What can cause this problem?
> >
> >      8.000339  invalid opcode: 0000 [#1] SMP
> >      8.003529  last sysfs file: /sys/power/state
> >      8.004265  Modules linked in: sco bridge stp bnep l2cacp crc16
> > bluetooth rfkill loop i2c_i801 snd_intel8x0 snd_ac97_codec shpchp
> > ac97_bus parport_pc parport
> > rng_core pci_hotplug snd_pcsp snd_pcm snd_timer snd soundcore psmouse
> > snd_page_alloc serio_raw evdev processor ext3 jbd mbcache ide_gd_mod
> > ata_generic libata scsi_mod
> > ide_pci_generic i915 drm_kms_helper uhci_hcd drm i2c_algo_bit piix
> > i2c_core ehci_hcd intel_agp e100 video ide_core mii floppy agpgart output
> > usbcore nls_base button
> > thermal fan thermal_sys [last unloaded: scsi_wait_scan]
> > [  148.004265]
> > [  148.004265] Pid: 0, comm: swapper Not tainted (2.6.32-trunk-686 #1) To
> > Be Filled By O.E.M. [  148.004265] EIP: 0060:[<c1008ff3>] EFLAGS:
> > 00010086 CPU: 0
> > [  148.004265] EIP is at mwait_idle+0x4e/0x6c
>
> I had exactly the same problem (on an HP computer with an Intel
> chipset).  As far as anyone could figure out, it is caused by a bug in
> the BIOS.  It's not entirely clear that this is the complete answer,
> but nothing else turned up.  See
>
> 	http://bugzilla.kernel.org/show_bug.cgi?id=15385
>
> for the complete record.  The best solution I could find was to boot
> with "idle=halt" on the command line.  You might check to see if any
> BIOS updates are available.

Thanks, it does not crash with "idle=halt" or "idle=poll". According to this:
http://siyobik.info/index.php?module=x86&id=215
the MWAIT instruction can be enabled/disabled in IA32_MISC_ENABLES MSR. Kernel 
probably should enable it at boot and also on resume.
Here's some more info:
http://software.intel.com/en-us/forums/showthread.php?t=63654

-- 
Ondrej Zary

  parent reply	other threads:[~2010-04-26 19:55 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-26 18:43 Invalid opcode on resume from STR on Asus P4P800-VM Ondrej Zary
2010-04-26 19:17 ` [linux-pm] " Alan Stern
2010-04-26 19:55   ` Ondrej Zary
2010-04-26 19:55   ` Ondrej Zary [this message]
2010-04-26 20:34     ` [linux-pm] " Alan Stern
2010-04-27  1:07       ` Robert Hancock
2010-04-27  1:07       ` [linux-pm] " Robert Hancock
2010-04-27 10:05         ` Ondrej Zary
2010-04-27 18:23           ` Alan Stern
2010-04-27 18:23           ` [linux-pm] " Alan Stern
2010-04-27 10:05         ` Ondrej Zary
2010-06-04 22:29       ` [PATCH] Re: [linux-pm] " Ondrej Zary
2010-06-05  1:45         ` [PATCH] " Alan Stern
2010-06-05  1:45         ` [PATCH] Re: [linux-pm] " Alan Stern
2010-06-07 15:17         ` Alan Stern
2010-06-07 15:17         ` [PATCH] " Alan Stern
2010-06-04 22:29       ` Ondrej Zary
2010-04-26 20:34     ` Alan Stern
2010-04-26 19:17 ` Alan Stern

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=201004262155.06949.linux@rainbow-software.org \
    --to=linux@rainbow-software.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=stern@rowland.harvard.edu \
    /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.