All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Brian J. Murrell" <brian@interlinx.bc.ca>
To: Dominik Brodowski <linux@dominikbrodowski.de>
Cc: Dave Jones <davej@redhat.com>, cpufreq@www.linux.org.uk
Subject: Re: oops on resume
Date: Mon, 09 Aug 2004 13:27:50 -0400	[thread overview]
Message-ID: <1092072470.14584.29.camel@pc> (raw)
In-Reply-To: <20040808162408.GA7986@dominikbrodowski.de>


[-- Attachment #1.1: Type: text/plain, Size: 3293 bytes --]

On Sun, 2004-08-08 at 18:24 +0200, Dominik Brodowski wrote:
> 
> Anyways, I've prepared a patch to work around the "local_irq_enable()" call.
> Could you test it, please?

No oops this time, but here is the console output:

Back to C!
zapping low mappings.
speedstep-lib: P4 - MSR_EBC_FREQUENCY_ID: 0x16300a16 0x0
FSB code = 0, msr_lo = 372247062
fsb = 100000
mult = 372247062
speedstep-lib: P4 - FSB 100000 kHz; Multiplier 22
pentium4_get_frequency() returns = 2200000
Warning: CPU frequency out of sync: cpufreq and timingcore thinks of 1200000, is 2200000 kHz.
here we are in time_cpufreq_notifier 0
here we are in time_cpufreq_notifier 1
calling cpufreq_scale(2162688, 2200000, 2200000)
here we are in cpufreq_scale 0, old = 2162688, div = 2200000, mult = 2200000
calling do_div(4757913600000, 2200000)
here we are in cpufreq_scale 1, returning 2162688
calling cpufreq_scale(2193778, 2200000, 2200000)
here we are in cpufreq_scale 0, old = 2193778, div = 2200000, mult = 2200000
calling do_div(4826311600000, 2200000)
here we are in cpufreq_scale 1, returning 2193778
here we are in time_cpufreq_notifier 2, cpu_khz = 2193778
calling cpufreq_scale(1957794, 2200000, 2200000)
here we are in cpufreq_scale 0, old = 1957794, div = 2200000, mult = 2200000
calling do_div(4307146800000, 2200000)
here we are in cpufreq_scale 1, returning 1957794
here we are in time_cpufreq_notifier 3, fast_gettimeoffset_quotient = 1957794
here we are in set_cyc2ns_scale 0, cpu_mhz = 2193
here we are in time_cpufreq_notifier 4
here we are in time_cpufreq_notifier 5
here we are in time_cpufreq_notifier 6
here we are in cpufreq_scale 0, old = 2162688, div = 2200000, mult = 2200000
calling do_div(4757913600000, 2200000)
here we are in cpufreq_scale 1, returning 2162688
PM: Finishing up.
PCI: Setting latency timer of device 0000:00:1d.0 to 64
PCI: Setting latency timer of device 0000:00:1d.0 to 64
ACPI: PCI interrupt 0000:00:1f.1[A] -> GSI 11 (level, low) -> IRQ 11
eth0: command 0x5800 did not complete! Status=0xffff
eth0: command 0x2804 did not complete! Status=0xffff
drivers/acpi/osl.c:737: spin_lock(drivers/acpi/osl.c:21fe0bf8) already locked by drivers/acpi/osl.c/737
drivers/acpi/osl.c:756: spin_unlock(drivers/acpi/osl.c:21fe0bf8) not locked
Restarting tasks... done
eth0: command 0x3002 did not complete! Status=0xffff
eth0: command 0x3002 did not complete! Status=0xffff
eth0: command 0x3002 did not complete! Status=0xffff
eth0: command 0x3002 did not complete! Status=0xffff
eth0: command 0x5800 did not complete! Status=0xffff
eth0: command 0x2804 did not complete! Status=0xffff
eth0: command 0x3002 did not complete! Status=0xffff
eth0: command 0x3002 did not complete! Status=0xffff
eth0: command 0x3002 did not complete! Status=0xffff
eth0: command 0x3002 did not complete! Status=0xffff
eth0: command 0x3002 did not complete! Status=0xffff


So we do hit "time_cpufreq_notifier 6" now, but we also get some errors
about spinlocks.  The screen is black and my ssh session is dead so I am
not so sure of the state of the machine.  I should have put a getty on
that serial console.  Wait, I just logged in "blindly" on the console
and did a shutdown, so it seems to have resumed ok, apart from the above
issues.

b.


[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 143 bytes --]

_______________________________________________
Cpufreq mailing list
Cpufreq@www.linux.org.uk
http://www.linux.org.uk/mailman/listinfo/cpufreq

  parent reply	other threads:[~2004-08-09 17:27 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-05 19:02 oops on resume Brian J. Murrell
2004-08-05 19:26 ` Dominik Brodowski
2004-08-05 19:34   ` Brian J. Murrell
2004-08-05 19:52     ` Dave Jones
2004-08-05 20:02       ` Brian J. Murrell
2004-08-05 20:08         ` Dave Jones
2004-08-05 20:19           ` Brian J. Murrell
2004-08-05 20:29             ` Dave Jones
2004-08-05 21:03               ` Dominik Brodowski
2004-08-05 21:26               ` Brian J. Murrell
2004-08-05 21:27                 ` Dave Jones
2004-08-05 21:29                 ` Dave Jones
2004-08-05 21:09             ` Dominik Brodowski
2004-08-05 21:45               ` Brian J. Murrell
2004-08-06 17:14                 ` Dominik Brodowski
2004-08-06 17:43               ` Brian J. Murrell
2004-08-06 17:55                 ` Dominik Brodowski
2004-08-06 21:13                   ` Dave Jones
2004-08-06 21:18                     ` Brian J. Murrell
2004-08-06 21:44                       ` Dave Jones
2004-08-06 22:10                         ` Brian J. Murrell
2004-08-06 22:51                           ` Dave Jones
2004-08-06 23:00                             ` Brian J. Murrell
2004-08-06 23:23                               ` Dave Jones
2004-08-07 13:24                   ` Dominik Brodowski
2004-08-07 19:03                     ` Brian J. Murrell
2004-08-08 16:24                       ` Dominik Brodowski
2004-08-09 13:37                         ` Brian J. Murrell
2004-08-09 14:53                           ` Dominik Brodowski
2004-08-09 17:27                         ` Brian J. Murrell [this message]
2004-08-09 19:38                           ` Dominik Brodowski

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=1092072470.14584.29.camel@pc \
    --to=brian@interlinx.bc.ca \
    --cc=cpufreq@www.linux.org.uk \
    --cc=davej@redhat.com \
    --cc=linux@dominikbrodowski.de \
    /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.