linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Tilman Schmidt <tilman@imap.cc>,
	linux-kernel@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>,
	john stultz <johnstul@us.ibm.com>, Andi Kleen <ak@suse.de>,
	Len Brown <lenb@kernel.org>,
	linux-acpi@vger.kernel.org, Dave Jones <davej@codemonkey.org.uk>,
	Thomas Renninger <trenn@suse.de>,
	Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>
Subject: Re: 2.6.23-rc3-mm1
Date: Sat, 25 Aug 2007 00:28:09 -0400	[thread overview]
Message-ID: <20070825042809.GA15863@redhat.com> (raw)
In-Reply-To: <20070824203000.1d710cee.akpm@linux-foundation.org>

On Fri, Aug 24, 2007 at 08:30:00PM -0700, Andrew Morton wrote:
 
 > >  <6>Linux agpgart interface v0.102
 > > +<6>rtc_cmos 00:03: rtc core: registered rtc_cmos as rtc0
 > > +<4>rtc_cmos: probe of 00:03 failed with error -16
 > > +<6>agpgart: suspend/resume problematic: resume with 3D/DRI active may lockup X.Org
 > > +<4>on some chipset/BIOS combos (see DEBUG_AGP_PM in intel-agp.c)
 > >  <6>agpgart: Detected an Intel 965Q Chipset.
 > >  <6>agpgart: Unknown page table size, assuming 512KB
 > >  <6>agpgart: Detected 7676K stolen memory.
 > >  <6>agpgart: AGP aperture is 256M @ 0x40000000
 > > -<6>rtc_cmos 00:03: rtc core: registered rtc_cmos as rtc0
 > > -<4>rtc_cmos: probe of 00:03 failed with error -16
 > 
 > I wonder if that was supposed to happen.  It's also happening in 2.6.23-rc3
 > base.
 
EBUSY. I've seen this happen when you have both CONFIG_RTC and
CONFIG_RTC_DRV_CMOS set.

	Dave

-- 
http://www.codemonkey.org.uk

  reply	other threads:[~2007-08-25  4:29 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20070822020648.5ea3a612.akpm@linux-foundation.org>
     [not found] ` <46CF695D.1020008@imap.cc>
2007-08-25  0:07   ` 2.6.23-rc3-mm1 Andrew Morton
2007-08-25  0:13     ` 2.6.23-rc3-mm1 Pallipadi, Venkatesh
2007-08-25  0:38       ` 2.6.23-rc3-mm1 Pallipadi, Venkatesh
2007-08-25 23:26         ` 2.6.23-rc3-mm1 Tilman Schmidt
2007-08-25 23:57           ` 2.6.23-rc3-mm1 Randy Dunlap
2007-08-27 13:35             ` 2.6.23-rc3-mm1 Tilman Schmidt
2007-08-25  0:14     ` 2.6.23-rc3-mm1 Dave Jones
2007-08-25  0:21     ` 2.6.23-rc3-mm1 john stultz
2007-08-25 22:39       ` 2.6.23-rc3-mm1 Tilman Schmidt
2007-08-25  0:47     ` 2.6.23-rc3-mm1 Tilman Schmidt
2007-08-25  3:30       ` 2.6.23-rc3-mm1 Andrew Morton
2007-08-25  4:28         ` Dave Jones [this message]
2007-08-25  7:55           ` 2.6.23-rc3-mm1 Paul Rolland
2007-08-25 23:37             ` 2.6.23-rc3-mm1 Tilman Schmidt
2007-09-05 20:41         ` Clock trouble retest results with 2.6.23-rc4-mm1 (was: 2.6.23-rc3-mm1) Tilman Schmidt
2007-08-27 21:27 ` [-mm patch] make "struct menu_governor" static (again) Adrian Bunk
2007-08-27 22:32   ` Adam Belay

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=20070825042809.GA15863@redhat.com \
    --to=davej@redhat.com \
    --cc=ak@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=davej@codemonkey.org.uk \
    --cc=johnstul@us.ibm.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=tilman@imap.cc \
    --cc=trenn@suse.de \
    --cc=venkatesh.pallipadi@intel.com \
    /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).