RE: [Fwd: Re: [PROBLEM] 2.6.3-rc1: still no suspend/resume on Centrino notebook (contains agp, lapic, swsusp)]

RE: [Fwd: Re: [PROBLEM] 2.6.3-rc1: still no suspend/resume on Centrino notebook (contains agp, lapic, swsusp)]

[Yu, Luming]

> Right now it appears to be a kernel issue, as my ASUS M2N occasionally
> booted with APIC&ACPI just fine -- but not the 2.6.x kernels with the
> exception of 2.6.2-rc2, I think.

To issue of booting hang with APIC &ACPI, please verify http://bugzilla.kernel.org/attachment.cgi?id=1257&action=view
can help. Maybe we need to figure out what's wrong with the SMM & APIC timer.

--Luming


-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn

Re: [Fwd: Re: [PROBLEM] 2.6.3-rc1: still no suspend/resume on Centrino notebook (contains agp, lapic, swsusp)]

[Georg C. F. Greve]

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

 || On Wed, 11 Feb 2004 11:04:55 +0800
 || "Yu, Luming" <luming.yu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org> wrote: 

 >> Right now it appears to be a kernel issue, as my ASUS M2N
 >> occasionally booted with APIC&ACPI just fine -- but not the 2.6.x
 >> kernels with the exception of 2.6.2-rc2, I think.

 yl> To issue of booting hang with APIC &ACPI, please verify
 yl> http://bugzilla.kernel.org/attachment.cgi?id=1257&action=view can
 yl> help. Maybe we need to figure out what's wrong with the SMM &
 yl> APIC timer.

Just checked this, compiled a 2.6.2 with ACPI 20040116 + the patch
above. That patch rejects on arch/i386/kernel/apic.c because the ACPI
patch (I believe) contains a half-fix for the issue, so the setup
routine looks like

 ver = GET_APIC_VERSION(apic_read(APIC_LVR));
 lvtt_value = APIC_LVT_TIMER_PERIODIC | LOCAL_TIMER_VECTOR;
 if (!APIC_INTEGRATED(ver))
    lvtt_value |= SET_APIC_TIMER_BASE(APIC_TIMER_BASE_DIV);
 apic_write_around(APIC_LVTT, lvtt_value);

the patch applies fine to drivers/acpi/bus.c, which is apparently
missing in the ACPI 20040116 patch.

When booting the machine with lapic enabled, the machine boots (!) and
dmesg shows the "Found and enabled local APIC!" "Using local APIC
timer interrupts." "calibrating APIC timer... [...]" messages.

Of course, pressing Fn+F8 (switch CRT/LCD display) makes me hit

 http://bugzilla.kernel.org/show_bug.cgi?id=1963
 http://bugzilla.kernel.org/show_bug.cgi?id=1890

and so the machine crashes hard & instantly, followed by reboot.

Unless I want an "instant crash" key, I guess I better leave LAPIC off
for now. .-)

Regards,
Georg

-- 
Georg C. F. Greve                                       <greve-mXXj517/zsQ@public.gmane.org>
Free Software Foundation Europe	                 (http://fsfeurope.org)
Brave GNU World	                           (http://brave-gnu-world.org)

[-- Attachment #2: Type: application/pgp-signature, Size: 258 bytes --]

Re: [Fwd: Re: [PROBLEM] 2.6.3-rc1: still no suspend/resume on Centrino notebook (contains agp, lapic, swsusp)]

[Bruno Ducrot]

On Wed, Feb 11, 2004 at 01:10:24PM +0100, Georg C. F. Greve wrote:
> 
> and so the machine crashes hard & instantly, followed by reboot.

That sound like a memory fault in a SMI handler, imho.


-- 
Bruno Ducrot

--  Which is worse:  ignorance or apathy?
--  Don't know.  Don't care.


-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn

Re: [Fwd: Re: [PROBLEM] 2.6.3-rc1: still no suspend/resume on Centrino notebook (contains agp, lapic, swsusp)]

[Georg C. F. Greve]

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

 || On Wed, 11 Feb 2004 13:36:01 +0100
 || Bruno Ducrot <ducrot-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org> wrote: 

 >> and so the machine crashes hard & instantly, followed by reboot.

 bd> That sound like a memory fault in a SMI handler, imho.

Furher info: when the same kernel is booted with "nolapic" and FN+F8
is pressed, display switching occurs, but the top of the screen is
screwed -- and seems to show parts from the framebuffer console.

When using the i810switch tool, switching the crt on/off works fine,
while LCD cannot be switched at all with that tool...

If anyone has concrete suggestions where to look or what to try, let
me know...

Regards,
Georg

-- 
Georg C. F. Greve                                       <greve-mXXj517/zsQ@public.gmane.org>
Free Software Foundation Europe	                 (http://fsfeurope.org)
Brave GNU World	                           (http://brave-gnu-world.org)

[-- Attachment #2: Type: application/pgp-signature, Size: 258 bytes --]

Re: [Fwd: Re: [PROBLEM] 2.6.3-rc1: still no suspend/resume on Centrino notebook (contains agp, lapic, swsusp)]

[Bruno Ducrot]

On Wed, Feb 11, 2004 at 02:16:12PM +0100, Georg C. F. Greve wrote:
>  || On Wed, 11 Feb 2004 13:36:01 +0100
>  || Bruno Ducrot <ducrot-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org> wrote: 
> 
>  >> and so the machine crashes hard & instantly, followed by reboot.
> 
>  bd> That sound like a memory fault in a SMI handler, imho.
> 
> Furher info: when the same kernel is booted with "nolapic" and FN+F8
> is pressed, display switching occurs, but the top of the screen is
> screwed -- and seems to show parts from the framebuffer console.
> 
> When using the i810switch tool, switching the crt on/off works fine,
> while LCD cannot be switched at all with that tool...
> 
> If anyone has concrete suggestions where to look or what to try, let
> me know...
> 

Perhaps wait for the little ACPI video driver I am currently polishing a
little ?

I think it should be OK tomorrow, but I have not tested it throughfully
though.

-- 
Bruno Ducrot

--  Which is worse:  ignorance or apathy?
--  Don't know.  Don't care.


-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click

Re: [Fwd: Re: [PROBLEM] 2.6.3-rc1: still no suspend/resume on Centrino notebook (contains agp, lapic, swsusp)]

[Georg C. F. Greve]

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

 || On Wed, 11 Feb 2004 18:58:42 +0100
 || Bruno Ducrot <ducrot-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org> wrote: 

 bd> Perhaps wait for the little ACPI video driver I am currently
 bd> polishing a little ?  I think it should be OK tomorrow, but I
 bd> have not tested it throughfully though.

Well, I'll be waiting with my compiler warmed up for that driver... :)

Regards,
Georg

-- 
Georg C. F. Greve                                       <greve-mXXj517/zsQ@public.gmane.org>
Free Software Foundation Europe	                 (http://fsfeurope.org)
Brave GNU World	                           (http://brave-gnu-world.org)

[-- Attachment #2: Type: application/pgp-signature, Size: 258 bytes --]

Re: [Fwd: Re: [PROBLEM] 2.6.3-rc1: still no suspend/resume on Centrino notebook (contains agp, lapic, swsusp)]

[Luca Capello]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

on 02/12/04 12:06, Georg C. F. Greve wrote:
>  || On Wed, 11 Feb 2004 18:58:42 +0100
>  || Bruno Ducrot <ducrot-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org> wrote:
>
>  bd> Perhaps wait for the little ACPI video driver I am currently
>  bd> polishing a little ?  I think it should be OK tomorrow, but I
>  bd> have not tested it throughfully though.
>
> Well, I'll be waiting with my compiler warmed up for that driver... :)
I would be wait, too, as I've the same problems on suspend/resume (S3)
as you, Georg, on ASUS Centrino M3N & Intel 855GM, but actually this
evening I'll get in touch with my new Cetrino notebook (ASUS M6800N),
which has an ATI Mobility Radeon 9600 and I hope it won't have
suspend/resume problems.

I'm sorry to cannot test and help you in solving this problem.

Thx, bye,
Gismo / Luca
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Debian - http://enigmail.mozdev.org

iD8DBQFAK2k7VAp7Xm10JmkRAk+VAJ0U7mGcwcQUSmhZyatJGveeK9sCcACeJS6e
bXeZqmb4nPLIaVVRm7oHi+M=
=wsTU
-----END PGP SIGNATURE-----


-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click

Re: [Fwd: Re: [PROBLEM] 2.6.3-rc1: still no suspend/resume on Centrino notebook (contains agp, lapic, swsusp)]

[Georg C. F. Greve]

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

 || On Wed, 11 Feb 2004 11:04:55 +0800
 || "Yu, Luming" <luming.yu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org> wrote: 

 yl> To issue of booting hang with APIC &ACPI, please verify
 yl> http://bugzilla.kernel.org/attachment.cgi?id=1257&action=view can
 yl> help. Maybe we need to figure out what's wrong with the SMM &
 yl> APIC timer.


 || On Wed, 11 Feb 2004 13:10:24 +0100
 || "Georg C. F. Greve" <greve-mXXj517/zsQ@public.gmane.org> wrote: 

 gg> Just checked this, compiled a 2.6.2 with ACPI 20040116 + the
 gg> patch above. That patch rejects on arch/i386/kernel/apic.c
 gg> because the ACPI patch (I believe) contains a half-fix for the
 gg> issue, so the setup routine looks like

 gg>  ver = GET_APIC_VERSION(apic_read(APIC_LVR));
 gg>  lvtt_value = APIC_LVT_TIMER_PERIODIC | LOCAL_TIMER_VECTOR;
 gg>  if (!APIC_INTEGRATED(ver))
 gg>     lvtt_value |= SET_APIC_TIMER_BASE(APIC_TIMER_BASE_DIV);
 gg>  apic_write_around(APIC_LVTT, lvtt_value);

 gg> the patch applies fine to drivers/acpi/bus.c, which is apparently
 gg> missing in the ACPI 20040116 patch.

Interesting side-effect: the kernel doesn't compile with ACPI but no
APIC enabled. 

Apparently, the patch for drivers/apci/bus.c should have some "ifdefs"
added to make sure these calls only get included when LAPIC is
enabled:

drivers/built-in.o(.init.text+0xf12): In function `acpi_bus_init':
: undefined reference to `disable_APIC_timer'
drivers/built-in.o(.init.text+0xf9c): In function `acpi_bus_init':
: undefined reference to `enable_APIC_timer'
drivers/built-in.o(.init.text+0xff5): In function `acpi_bus_init':
: undefined reference to `enable_APIC_timer'
make: *** [.tmp_vmlinux1] Error 1

Regards,
Georg

-- 
Georg C. F. Greve                                       <greve-mXXj517/zsQ@public.gmane.org>
Free Software Foundation Europe	                 (http://fsfeurope.org)
Brave GNU World	                           (http://brave-gnu-world.org)

[-- Attachment #2: Type: application/pgp-signature, Size: 258 bytes --]

RE: [Fwd: Re: [PROBLEM] 2.6.3-rc1: still no suspend/resume on Centrino notebook (contains agp, lapic, swsusp)]

[Yu, Luming]

> Perhaps wait for the little ACPI video driver I am currently 
> polishing a
> little ?
> 
> I think it should be OK tomorrow, but I have not tested it 
> throughfully
> though.
> 

In this case, as a workaround, APIC timer should be disabled
before any write operation to port 0xB2.  Please refer
http://bugzilla.kernel.org/show_bug.cgi?id=1269#c18 .

I think it will help this case.

--Luming


-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id\x1356&alloc_id438&op=click

Re: [Fwd: Re: [PROBLEM] 2.6.3-rc1: still no suspend/resume on Centrino notebook (contains agp, lapic, swsusp)]

[Bruno Ducrot]

On Thu, Feb 12, 2004 at 11:07:33AM +0800, Yu, Luming wrote:
> > Perhaps wait for the little ACPI video driver I am currently 
> > polishing a
> > little ?
> > 
> > I think it should be OK tomorrow, but I have not tested it 
> > throughfully
> > though.
> > 
> 
> In this case, as a workaround, APIC timer should be disabled
> before any write operation to port 0xB2.  Please refer
> http://bugzilla.kernel.org/show_bug.cgi?id=1269#c18 .
> 
> I think it will help this case.
> 

Yes, something wrong happens in the SMI handler.  I guess that when APIC
is enabled, then the SMI handler do at least a double page fault, or a
segment register is cleared somehow, but that hard to debug without
the source of that handler.

-- 
Bruno Ducrot

--  Which is worse:  ignorance or apathy?
--  Don't know.  Don't care.


-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click

RE: [Fwd: Re: [PROBLEM] 2.6.3-rc1: still no suspend/resume on Centrino notebook (contains agp, lapic, swsusp)]

[Yu, Luming]

> MP processor do have lapic support, but actually that one may 
> be broken if
> the OEM do "forget" to connect it.  Therefore, forcing it like Linux
> does hang your machine not matter what.

I don't understand your statement. How OEM could forget ot connect lapic ?

lapic is on the CPU.

--Luming


-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn

RE: [Fwd: Re: [PROBLEM] 2.6.3-rc1: still no suspend/resume on Centrino notebook (contains agp, lapic, swsusp)]

[Sérgio Monteiro Basto]

On Wed, 2004-02-11 at 03:09, Yu, Luming wrote:
> > MP processor do have lapic support, but actually that one may 
> > be broken if
> > the OEM do "forget" to connect it.  Therefore, forcing it like Linux
> > does hang your machine not matter what.
> 
> I don't understand your statement. How OEM could forget to connect lapic ?

I think Bruno is talking about this line in dmesg : 

Local APIC disabled by BIOS -- reenabling.


-- 
Sérgio M. B.



-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn

Re: [Fwd: Re: [PROBLEM] 2.6.3-rc1: still no suspend/resume on Centrino notebook (contains agp, lapic, swsusp)]

[Bruno Ducrot]

On Wed, Feb 11, 2004 at 11:09:55AM +0800, Yu, Luming wrote:
> 
> > MP processor do have lapic support, but actually that one may 
> > be broken if
> > the OEM do "forget" to connect it.  Therefore, forcing it like Linux
> > does hang your machine not matter what.
> 
> I don't understand your statement. How OEM could forget ot connect lapic ?
> 
> lapic is on the CPU.

That what I say with "MP processor do have lapic support", but in order
to use it, you need external circuitry (IO-APIC, etc).  If there is an IO-APIC
but that one is not fully connected, booom.

-- 
Bruno Ducrot

--  Which is worse:  ignorance or apathy?
--  Don't know.  Don't care.


-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn

RE: [Fwd: Re: [PROBLEM] 2.6.3-rc1: still no suspend/resume on Centrino notebook (contains agp, lapic, swsusp)]

[Yu, Luming]

>  >> The moment I enable AGP (no DRM/DRI, no intel fb), things break.
> 
>  dj> If you have DRI & FB disabled, AGP isn't going to get used.  It's
>  dj> just dead code.  For this reason, I find it hard to believe its
>  dj> causing a problem.
> 
> So was I... but empirical evidence pointed towards it.
> 
> Maybe it was a false positive created by the PCMCIA (yenta) stuff,
> which seems flakey wrt to ACPI/suspend/resume, but that is unlikely.
> 
> I am fairly confident that AGP breaks powermanagement for most
> Centrino notebooks, in particular the 855GM ones.

I think we need an alternative console which can be used to verify
 whether the problem is lying in AGP.  


-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn

Re: [Fwd: Re: [PROBLEM] 2.6.3-rc1: still no suspend/resume on Centrino notebook (contains agp, lapic, swsusp)]

[Karol Kozimor]

Thus wrote Yu, Luming:
> > I am fairly confident that AGP breaks powermanagement for most
> > Centrino notebooks, in particular the 855GM ones.
> I think we need an alternative console which can be used to verify
>  whether the problem is lying in AGP.  

Simple "modprobe intel-agp" will do, the system will reboot or hang when
resuming from swsusp1/pmdisk even when AGP is not used.
Best regards,

-- 
Karol 'sziwan' Kozimor
sziwan-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org


-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn

Re: [Fwd: Re: [PROBLEM] 2.6.3-rc1: still no suspend/resume on Centrino notebook (contains agp, lapic, swsusp)]

[Dave Jones]

On Wed, Feb 11, 2004 at 11:55:31AM +0100, Karol Kozimor wrote:
 > Thus wrote Yu, Luming:
 > > > I am fairly confident that AGP breaks powermanagement for most
 > > > Centrino notebooks, in particular the 855GM ones.
 > > I think we need an alternative console which can be used to verify
 > >  whether the problem is lying in AGP.  
 > 
 > Simple "modprobe intel-agp" will do, the system will reboot or hang when
 > resuming from swsusp1/pmdisk even when AGP is not used.

Hmm, some of the Intel chipset code has resume callbacks already.
These _will_ get called even if AGP isn't in use.

I'm wondering if they're doing something they shouldn't.
It might even be possible that those callbacks should just do nothing
if agp isn't in use.  Need to think some more on this one.

		Dave


-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn

Re: [Fwd: Re: [PROBLEM] 2.6.3-rc1: still no suspend/resume on Centrino notebook (contains agp, lapic, swsusp)]

[Karol Kozimor]

Thus wrote Dave Jones:
>  > Simple "modprobe intel-agp" will do, the system will reboot or hang when
>  > resuming from swsusp1/pmdisk even when AGP is not used.
> Hmm, some of the Intel chipset code has resume callbacks already.
> These _will_ get called even if AGP isn't in use.

Right.

> I'm wondering if they're doing something they shouldn't.
> It might even be possible that those callbacks should just do nothing
> if agp isn't in use.  Need to think some more on this one.

That's especially strange as Nigel's swsusp2 survives the suspend. Here's
how it looks currently on my system [1]:


				pmdisk	swsusp	swsusp2
intel-agp not loaded		OK	OK	OK
intel-agp loaded, not in use	(?)	reboot	OK
intel-agp in use		reboot	reboot	OK

I haven't used pmdisk for some time, so I might be not authoritative.

[1] 00:01.0 PCI bridge: Intel Corp. 82845 845 (Brookdale) Chipset AGP
Bridge (rev 04)

I'm willing to test anything you come up with.
Best regards,

-- 
Karol 'sziwan' Kozimor
sziwan-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org


-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn

Re: [Fwd: Re: [PROBLEM] 2.6.3-rc1: still no suspend/resume on Centrino notebook (contains agp, lapic, swsusp)]

[Dave Jones]

On Wed, Feb 11, 2004 at 12:25:05PM +0100, Karol Kozimor wrote:
 > Thus wrote Dave Jones:
 > >  > Simple "modprobe intel-agp" will do, the system will reboot or hang when
 > >  > resuming from swsusp1/pmdisk even when AGP is not used.
 > > Hmm, some of the Intel chipset code has resume callbacks already.
 > > These _will_ get called even if AGP isn't in use.
 > 
 > Right.
 > 
 > > I'm wondering if they're doing something they shouldn't.
 > > It might even be possible that those callbacks should just do nothing
 > > if agp isn't in use.  Need to think some more on this one.
 > 
 > That's especially strange as Nigel's swsusp2 survives the suspend. Here's
 > how it looks currently on my system [1]:
 > 
 > 
 > 				pmdisk	swsusp	swsusp2
 > intel-agp not loaded		OK	OK	OK
 > intel-agp loaded, not in use	(?)	reboot	OK
 > intel-agp in use		reboot	reboot	OK
 > 
 > I haven't used pmdisk for some time, so I might be not authoritative.
 > 
 > [1] 00:01.0 PCI bridge: Intel Corp. 82845 845 (Brookdale) Chipset AGP
 > Bridge (rev 04)
 > 
 > I'm willing to test anything you come up with.

Take a look at drivers/char/agp/intel-agp.c around line 1427 or so
function agp_intel_resume().

Does it still hang if you just return 0 there ?

I'm guessing that will fix it. Maybe we don't quite have the
initialisation routine perfect, and reinitialising the chipset
twice causes it to hang..

		Dave



-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn

Re: [Fwd: Re: [PROBLEM] 2.6.3-rc1: still no suspend/resume on Centrino notebook (contains agp, lapic, swsusp)]

[Georg C. F. Greve]

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

 || On Wed, 11 Feb 2004 12:25:05 +0100
 || Karol Kozimor <sziwan-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org> wrote: 

 kk> That's especially strange as Nigel's swsusp2 survives the
 kk> suspend. Here's how it looks currently on my system [1]:

 kk> 				pmdisk	swsusp	swsusp2
 kk> intel-agp not loaded		OK	OK	OK
 kk> intel-agp loaded, not in use	(?)	reboot	OK
 kk> intel-agp in use		reboot	reboot	OK

That is interesting. Did you have X running while doing that?

I just ran a similar series with a Kernel 2.6.2 + ACPI 20040116 + the
ACPI/LAPIC patch + swsusp2 on my machine [1]. LAPIC compiled in --
otherwise it won't link, see other mail -- but always booted with
"nolapic" to disable "instant crash" button FN+F8.

Results:

agpgart   intel-agp   i830(DRI)   X11            Result of suspend
                                                 to disk and resume

  -           -          -       without DRI           OK

  *           -          -       without DRI           OK

  *           *          -       without DRI           OK

  *           *          *       without DRI           OK

  *           *          *         with DRI       hung upon resume


So the mere presence of the AGP and DRM/DRI structures doesn't seem to
create the conditions for things to fail. 

Only running an X Server that makes use of DRM/DRI does.


But the intel-agp module is not without fault, either. Because when I
load the i830 DRM/DRI, run the X server on it, turn X off, unload i830
DRM/DRI, the intel_agp still claims to be used by 1.

Also, I tried S3 (suspend to ram) for the hell of it while running X11
without DRM/DRI but with agpgart module loaded.

It showed the typical behaviour (suspends well, resumes very much
successfully with many lines complaining about codec_semaphore (syslog
attached), but very much functional (I can type on the keyboard to
bring up the network and log in remotely). 

Unfortunately, the screen is entirely dead.

I can toggle the /proc/acpi/asus/{brn,lcd} switches as much as I want
without any change. (Un)loading agpgart doesn't change anything
either.

But when doing "modprobe intel-agp" now, the command just simply
hangs. No reaction on that console... no output in dmesg, either.

Trying a shutdown -r, the machine seems to be hanging somewhere, but
since network is dead by then and the screen is dead, it is hard to
tell where.

Having the intel-agp module already loaded while trying S3 doesn't
change the behaviour.


Hope this helps someone to get a clearer idea what might be broken or
missing,

Regards,
Georg



[1] ASUS M2N Intel 855GM Centrio, more details at
    http://bugzilla.kernel.org/show_bug.cgi?id=1774


[-- Attachment #1.2: Type: text/plain, Size: 14334 bytes --]

Feb 11 15:31:33 myhost kernel: Back to C!
Feb 11 15:31:33 myhost kernel: atkbd.c: Unknown key pressed (translated set 2, code 0x61 on isa0060/serio0).
Feb 11 15:31:33 myhost kernel: atkbd.c: Use 'setkeycodes 61 <keycode>' to make it known.
Feb 11 15:31:33 myhost kernel: PM: Finishing up.
Feb 11 15:31:33 myhost kernel: PCI: Enabling device 0000:00:1f.5 (0005 -> 0007)
Feb 11 15:31:33 myhost kernel: PCI: Setting latency timer of device 0000:00:1f.5 to 64
Feb 11 15:31:33 myhost kernel: AC'97 warm reset still in progress? [0xffffffff]
Feb 11 15:31:33 myhost kernel: codec_semaphore: semaphore is not ready [0xff][0xffffffff]
Feb 11 15:31:33 myhost kernel: codec_write 0: semaphore is not ready for register 0x26
Feb 11 15:31:33 myhost kernel: codec_semaphore: semaphore is not ready [0xff][0xffffffff]
Feb 11 15:31:33 myhost kernel: codec_write 0: semaphore is not ready for register 0x0
Feb 11 15:31:33 myhost kernel: codec_semaphore: semaphore is not ready [0xff][0xffffffff]
Feb 11 15:31:33 myhost kernel: codec_write 0: semaphore is not ready for register 0x26
Feb 11 15:31:33 myhost kernel: codec_semaphore: semaphore is not ready [0xff][0xffffffff]
Feb 11 15:31:33 myhost kernel: codec_write 0: semaphore is not ready for register 0x20
Feb 11 15:31:33 myhost kernel: codec_semaphore: semaphore is not ready [0xff][0xffffffff]
Feb 11 15:31:33 myhost kernel: codec_write 0: semaphore is not ready for register 0x26
Feb 11 15:31:33 myhost kernel: codec_semaphore: semaphore is not ready [0xff][0xffffffff]
Feb 11 15:31:33 myhost kernel: codec_write 0: semaphore is not ready for register 0x2
Feb 11 15:31:33 myhost kernel: codec_semaphore: semaphore is not ready [0xff][0xffffffff]
Feb 11 15:31:33 myhost kernel: codec_read 0: semaphore is not ready for register 0x2
Feb 11 15:31:33 myhost kernel: codec_semaphore: semaphore is not ready [0xff][0xffffffff]
Feb 11 15:31:33 myhost kernel: codec_read 0: semaphore is not ready for register 0x2
Feb 11 15:31:33 myhost kernel: codec_semaphore: semaphore is not ready [0xff][0xffffffff]
Feb 11 15:31:33 myhost kernel: codec_read 0: semaphore is not ready for register 0x2
Feb 11 15:31:33 myhost kernel: codec_semaphore: semaphore is not ready [0xff][0xffffffff]
Feb 11 15:31:33 myhost kernel: codec_read 0: semaphore is not ready for register 0x2
Feb 11 15:31:33 myhost kernel: codec_semaphore: semaphore is not ready [0xff][0xffffffff]
Feb 11 15:31:33 myhost kernel: codec_read 0: semaphore is not ready for register 0x2
Feb 11 15:31:33 myhost kernel: codec_semaphore: semaphore is not ready [0xff][0xffffffff]
Feb 11 15:31:33 myhost kernel: codec_read 0: semaphore is not ready for register 0x2
Feb 11 15:31:33 myhost kernel: codec_semaphore: semaphore is not ready [0xff][0xffffffff]
Feb 11 15:31:33 myhost kernel: codec_read 0: semaphore is not ready for register 0x2
Feb 11 15:31:33 myhost kernel: codec_semaphore: semaphore is not ready [0xff][0xffffffff]
Feb 11 15:31:33 myhost kernel: codec_read 0: semaphore is not ready for register 0x2
Feb 11 15:31:33 myhost kernel: codec_semaphore: semaphore is not ready [0xff][0xffffffff]
Feb 11 15:31:33 myhost kernel: codec_read 0: semaphore is not ready for register 0x2
Feb 11 15:31:33 myhost kernel: codec_semaphore: semaphore is not ready [0xff][0xffffffff]
Feb 11 15:31:33 myhost kernel: codec_read 0: semaphore is not ready for register 0x2
Feb 11 15:31:33 myhost kernel: codec_semaphore: semaphore is not ready [0xff][0xffffffff]
Feb 11 15:31:33 myhost kernel: codec_write 0: semaphore is not ready for register 0x2
Feb 11 15:31:33 myhost kernel: codec_semaphore: semaphore is not ready [0xff][0xffffffff]
Feb 11 15:31:33 myhost kernel: codec_read 0: semaphore is not ready for register 0x2
Feb 11 15:31:33 myhost kernel: codec_semaphore: semaphore is not ready [0xff][0xffffffff]
Feb 11 15:31:33 myhost kernel: codec_write 0: semaphore is not ready for register 0x4
Feb 11 15:31:33 myhost kernel: codec_semaphore: semaphore is not ready [0xff][0xffffffff]
Feb 11 15:31:33 myhost kernel: codec_read 0: semaphore is not ready for register 0x4
Feb 11 15:31:33 myhost kernel: codec_semaphore: semaphore is not ready [0xff][0xffffffff]
Feb 11 15:31:33 myhost kernel: codec_write 0: semaphore is not ready for register 0x6
Feb 11 15:31:33 myhost kernel: codec_semaphore: semaphore is not ready [0xff][0xffffffff]
Feb 11 15:31:33 myhost kernel: codec_semaphore: semaphore is not ready [0xff][0xffffffff]
Feb 11 15:31:33 myhost kernel: codec_write 0: semaphore is not ready for register 0xa
Feb 11 15:31:33 myhost kernel: codec_semaphore: semaphore is not ready [0xff][0xffffffff]
Feb 11 15:31:33 myhost kernel: codec_read 0: semaphore is not ready for register 0xa
Feb 11 15:31:33 myhost kernel: codec_semaphore: semaphore is not ready [0xff][0xffffffff]
Feb 11 15:31:33 myhost kernel: codec_write 0: semaphore is not ready for register 0xc
Feb 11 15:31:33 myhost kernel: codec_semaphore: semaphore is not ready [0xff][0xffffffff]
Feb 11 15:31:33 myhost kernel: codec_read 0: semaphore is not ready for register 0xc
Feb 11 15:31:33 myhost kernel: codec_semaphore: semaphore is not ready [0xff][0xffffffff]
Feb 11 15:31:33 myhost kernel: codec_write 0: semaphore is not ready for register 0xe
Feb 11 15:31:33 myhost kernel: codec_semaphore: semaphore is not ready [0xff][0xffffffff]
Feb 11 15:31:33 myhost kernel: codec_read 0: semaphore is not ready for register 0xe
Feb 11 15:31:33 myhost kernel: codec_semaphore: semaphore is not ready [0xff][0xffffffff]
Feb 11 15:31:33 myhost kernel: codec_write 0: semaphore is not ready for register 0x10
Feb 11 15:31:33 myhost kernel: codec_semaphore: semaphore is not ready [0xff][0xffffffff]
Feb 11 15:31:33 myhost kernel: codec_read 0: semaphore is not ready for register 0x10
Feb 11 15:31:33 myhost kernel: codec_semaphore: semaphore is not ready [0xff][0xffffffff]
Feb 11 15:31:33 myhost kernel: codec_write 0: semaphore is not ready for register 0x12
Feb 11 15:31:33 myhost kernel: codec_semaphore: semaphore is not ready [0xff][0xffffffff]
Feb 11 15:31:33 myhost kernel: codec_read 0: semaphore is not ready for register 0x12
Feb 11 15:31:33 myhost kernel: codec_semaphore: semaphore is not ready [0xff][0xffffffff]
Feb 11 15:31:33 myhost kernel: codec_write 0: semaphore is not ready for register 0x14
Feb 11 15:31:33 myhost kernel: codec_semaphore: semaphore is not ready [0xff][0xffffffff]
Feb 11 15:31:33 myhost kernel: codec_read 0: semaphore is not ready for register 0x14
Feb 11 15:31:33 myhost kernel: codec_semaphore: semaphore is not ready [0xff][0xffffffff]
Feb 11 15:31:33 myhost kernel: codec_write 0: semaphore is not ready for register 0x16
Feb 11 15:31:33 myhost kernel: codec_semaphore: semaphore is not ready [0xff][0xffffffff]
Feb 11 15:31:33 myhost kernel: codec_read 0: semaphore is not ready for register 0x16
Feb 11 15:31:33 myhost kernel: codec_semaphore: semaphore is not ready [0xff][0xffffffff]
Feb 11 15:31:33 myhost kernel: codec_write 0: semaphore is not ready for register 0x18
Feb 11 15:31:33 myhost kernel: codec_semaphore: semaphore is not ready [0xff][0xffffffff]
Feb 11 15:31:33 myhost kernel: codec_read 0: semaphore is not ready for register 0x18
Feb 11 15:31:33 myhost kernel: codec_semaphore: semaphore is not ready [0xff][0xffffffff]
Feb 11 15:31:33 myhost kernel: codec_write 0: semaphore is not ready for register 0x1a
Feb 11 15:31:33 myhost kernel: codec_semaphore: semaphore is not ready [0xff][0xffffffff]
Feb 11 15:31:33 myhost kernel: codec_read 0: semaphore is not ready for register 0x1a
Feb 11 15:31:33 myhost kernel: codec_semaphore: semaphore is not ready [0xff][0xffffffff]
Feb 11 15:31:33 myhost kernel: codec_write 0: semaphore is not ready for register 0x1c
Feb 11 15:31:33 myhost kernel: codec_semaphore: semaphore is not ready [0xff][0xffffffff]
Feb 11 15:31:33 myhost kernel: codec_read 0: semaphore is not ready for register 0x1c
Feb 11 15:31:33 myhost kernel: codec_semaphore: semaphore is not ready [0xff][0xffffffff]
Feb 11 15:31:33 myhost kernel: codec_write 0: semaphore is not ready for register 0x20
Feb 11 15:31:33 myhost kernel: codec_semaphore: semaphore is not ready [0xff][0xffffffff]
Feb 11 15:31:33 myhost kernel: codec_read 0: semaphore is not ready for register 0x20
Feb 11 15:31:33 myhost kernel: codec_semaphore: semaphore is not ready [0xff][0xffffffff]
Feb 11 15:31:33 myhost kernel: codec_write 0: semaphore is not ready for register 0x22
Feb 11 15:31:33 myhost kernel: codec_semaphore: semaphore is not ready [0xff][0xffffffff]
Feb 11 15:31:33 myhost kernel: codec_read 0: semaphore is not ready for register 0x22
Feb 11 15:31:33 myhost kernel: codec_semaphore: semaphore is not ready [0xff][0xffffffff]
Feb 11 15:31:33 myhost kernel: codec_write 0: semaphore is not ready for register 0x2a
Feb 11 15:31:33 myhost kernel: codec_semaphore: semaphore is not ready [0xff][0xffffffff]
Feb 11 15:31:33 myhost kernel: codec_read 0: semaphore is not ready for register 0x2a
Feb 11 15:31:33 myhost kernel: codec_semaphore: semaphore is not ready [0xff][0xffffffff]
Feb 11 15:31:33 myhost kernel: codec_write 0: semaphore is not ready for register 0x2c
Feb 11 15:31:33 myhost kernel: codec_semaphore: semaphore is not ready [0xff][0xffffffff]
Feb 11 15:31:33 myhost kernel: codec_read 0: semaphore is not ready for register 0x2c
Feb 11 15:31:33 myhost kernel: codec_semaphore: semaphore is not ready [0xff][0xffffffff]
Feb 11 15:31:33 myhost kernel: codec_write 0: semaphore is not ready for register 0x32
Feb 11 15:31:33 myhost kernel: codec_semaphore: semaphore is not ready [0xff][0xffffffff]
Feb 11 15:31:33 myhost kernel: codec_read 0: semaphore is not ready for register 0x32
Feb 11 15:31:33 myhost kernel: codec_semaphore: semaphore is not ready [0xff][0xffffffff]
Feb 11 15:31:33 myhost kernel: codec_write 0: semaphore is not ready for register 0x3a
Feb 11 15:31:33 myhost kernel: codec_semaphore: semaphore is not ready [0xff][0xffffffff]
Feb 11 15:31:33 myhost kernel: codec_read 0: semaphore is not ready for register 0x3a
Feb 11 15:31:33 myhost kernel: codec_semaphore: semaphore is not ready [0xff][0xffffffff]
Feb 11 15:31:33 myhost kernel: codec_write 0: semaphore is not ready for register 0x2a
Feb 11 15:31:33 myhost kernel: codec_semaphore: semaphore is not ready [0xff][0xffffffff]
Feb 11 15:31:33 myhost kernel: codec_write 0: semaphore is not ready for register 0x2a
Feb 11 15:31:33 myhost kernel: codec_semaphore: semaphore is not ready [0xff][0xffffffff]
Feb 11 15:31:33 myhost kernel: codec_write 0: semaphore is not ready for register 0x3a
Feb 11 15:31:33 myhost kernel: codec_semaphore: semaphore is not ready [0xff][0xffffffff]
Feb 11 15:31:33 myhost kernel: codec_write 0: semaphore is not ready for register 0x2a
Feb 11 15:31:33 myhost kernel: codec_semaphore: semaphore is not ready [0xff][0xffffffff]
Feb 11 15:31:33 myhost kernel: codec_write 1: semaphore is not ready for register 0x26
Feb 11 15:31:33 myhost kernel: codec_semaphore: semaphore is not ready [0xff][0xffffffff]
Feb 11 15:31:33 myhost kernel: codec_write 1: semaphore is not ready for register 0x0
Feb 11 15:31:33 myhost kernel: codec_semaphore: semaphore is not ready [0xff][0xffffffff]
Feb 11 15:31:33 myhost kernel: codec_write 1: semaphore is not ready for register 0x26
Feb 11 15:31:33 myhost kernel: codec_semaphore: semaphore is not ready [0xff][0xffffffff]
Feb 11 15:31:33 myhost kernel: codec_write 1: semaphore is not ready for register 0x20
Feb 11 15:31:33 myhost kernel: codec_semaphore: semaphore is not ready [0xff][0xffffffff]
Feb 11 15:31:33 myhost kernel: codec_write 1: semaphore is not ready for register 0x26
Feb 11 15:31:33 myhost kernel: codec_semaphore: semaphore is not ready [0xff][0xffffffff]
Feb 11 15:31:33 myhost kernel: codec_write 1: semaphore is not ready for register 0x2
Feb 11 15:31:33 myhost kernel: codec_semaphore: semaphore is not ready [0xff][0xffffffff]
Feb 11 15:31:33 myhost kernel: codec_read 1: semaphore is not ready for register 0x2
Feb 11 15:31:33 myhost kernel: codec_semaphore: semaphore is not ready [0xff][0xffffffff]
Feb 11 15:31:33 myhost kernel: codec_read 1: semaphore is not ready for register 0x2
Feb 11 15:31:33 myhost kernel: codec_semaphore: semaphore is not ready [0xff][0xffffffff]
Feb 11 15:31:33 myhost kernel: codec_read 1: semaphore is not ready for register 0x2
Feb 11 15:31:33 myhost kernel: codec_semaphore: semaphore is not ready [0xff][0xffffffff]
Feb 11 15:31:33 myhost kernel: codec_read 1: semaphore is not ready for register 0x2
Feb 11 15:31:33 myhost kernel: codec_semaphore: semaphore is not ready [0xff][0xffffffff]
Feb 11 15:31:33 myhost kernel: codec_read 1: semaphore is not ready for register 0x2
Feb 11 15:31:33 myhost kernel: codec_semaphore: semaphore is not ready [0xff][0xffffffff]
Feb 11 15:31:33 myhost kernel: codec_read 1: semaphore is not ready for register 0x2
Feb 11 15:31:33 myhost kernel: codec_semaphore: semaphore is not ready [0xff][0xffffffff]
Feb 11 15:31:33 myhost kernel: codec_read 1: semaphore is not ready for register 0x2
Feb 11 15:31:33 myhost kernel: codec_semaphore: semaphore is not ready [0xff][0xffffffff]
Feb 11 15:31:33 myhost kernel: codec_read 1: semaphore is not ready for register 0x2
Feb 11 15:31:33 myhost kernel: codec_semaphore: semaphore is not ready [0xff][0xffffffff]
Feb 11 15:31:33 myhost kernel: codec_read 1: semaphore is not ready for register 0x2
Feb 11 15:31:33 myhost kernel: codec_semaphore: semaphore is not ready [0xff][0xffffffff]
Feb 11 15:31:33 myhost kernel: codec_read 1: semaphore is not ready for register 0x2
Feb 11 15:31:33 myhost kernel: codec_semaphore: semaphore is not ready [0xff][0xffffffff]
Feb 11 15:31:33 myhost kernel: codec_write 1: semaphore is not ready for register 0x1c
Feb 11 15:31:33 myhost kernel: codec_semaphore: semaphore is not ready [0xff][0xffffffff]
Feb 11 15:31:33 myhost kernel: codec_read 1: semaphore is not ready for register 0x1c
Feb 11 15:31:33 myhost kernel: hda: Wakeup request inited, waiting for !BSY...
Feb 11 15:31:33 myhost kernel: hda: start_power_step(step: 1000)
Feb 11 15:31:33 myhost kernel: blk: queue df4f3400, I/O limit 4095Mb (mask 0xffffffff)
Feb 11 15:31:33 myhost kernel: hda: completing PM request, resume
Feb 11 15:31:33 myhost kernel: hdc: Wakeup request inited, waiting for !BSY...
Feb 11 15:31:33 myhost kernel: hdc: start_power_step(step: 1000)
Feb 11 15:31:33 myhost kernel: hdc: completing PM request, resume

[-- Attachment #1.3: Type: text/plain, Size: 242 bytes --]


-- 
Georg C. F. Greve                                       <greve-mXXj517/zsQ@public.gmane.org>
Free Software Foundation Europe	                 (http://fsfeurope.org)
Brave GNU World	                           (http://brave-gnu-world.org)

[-- Attachment #2: Type: application/pgp-signature, Size: 258 bytes --]

Re: [Fwd: Re: [PROBLEM] 2.6.3-rc1: still no suspend/resume on Centrino notebook (contains agp, lapic, swsusp)]

[Karol Kozimor]

Thus wrote Karol Kozimor:
> 				pmdisk	swsusp	swsusp2
> intel-agp not loaded		OK	OK	OK
> intel-agp loaded, not in use	(?)	reboot	OK
> intel-agp in use		reboot	reboot	OK
> 

It seems I have rushed a bit with that declaration (I'm not using 2.6 on a
regular basis due to lack of USB PM) -- suspending and resuming with
intel-agp used is quite unstable, even with swsusp2. What probably happens
is that it suspends when the X is started for the first time, but any VT
switch will make it reboot. I'll try to verify that in the following days.
Best regards,

-- 
Karol 'sziwan' Kozimor
sziwan-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org


-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click

[Fwd: Re: [PROBLEM] 2.6.3-rc1: still no suspend/resume on Centrino notebook (contains agp, lapic, swsusp)]

[Sérgio Monteiro Basto]

Hi list 
I would like to know your opinion about my guess.

-----Forwarded Message-----
> From: Sérgio Monteiro Basto <sergiomb-hHo3WeeoaswVhHzd4jOs4w@public.gmane.org>
> To: Georg C F Greve <greve-1r/uNngapc3YtjvyW6yDsg@public.gmane.org>
> Subject: Re: [ACPI] [PROBLEM] 2.6.3-rc1: still no suspend/resume on Centrino notebook (contains agp, lapic, swsusp)
> Date: Mon, 09 Feb 2004 03:55:47 +0000
> 
> Hi Georg
> If your laptop is one APIC victim, I think until this problem isn't
> resolved, suspend/resume also doesn't work, is my guess.
-- 
Sérgio M. B.



-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn

Re: [Fwd: Re: [PROBLEM] 2.6.3-rc1: still no suspend/resume on Centrino notebook (contains agp, lapic, swsusp)]

[Georg C. F. Greve]

 || On Tue, 10 Feb 2004 00:58:06 +0000
 || Sérgio Monteiro Basto <sergiomb-hHo3WeeoaswVhHzd4jOs4w@public.gmane.org> wrote: 

 >> If your laptop is one APIC victim, I think until this problem
 >> isn't resolved, suspend/resume also doesn't work, is my guess.

My laptop definitely experiences the ACPI+APIC troubles, but I'm not
sure whether that is what you refer to as "victim." :)

However: suspend/resume _almost_ work under 2.6.x -- the problem is
the AGP code, it seems. 

If I disable AGP, DRM/DRI and the intel framebuffer (which depends on
intel AGP! vesa fb is activated and works, though), compile at least
yenta_socket as a module, I can do suspend to disk (swsusp2) on kernel
2.6.2 and resume even while X11 is running.

The moment I enable AGP (no DRM/DRI, no intel fb), things break.

As for S1/S3, it seems that S1 is almost/more or less working, but I
can only wake up the machine with the power button and that creates an
event to shut down the machine. :-/ Oh yeah: and the keyboard is
broken after resume from S1.

On S3, the machine comes back up -- apparently with working keyboard,
although I can't be 100% sure -- and the screen is dead. After typing
"ifup eth0" on the console I can log into it over the network,
though. :)

On the swsusp2 list, someone made a survey and found out that noone
has AGP working on 2.6.x for their Centrino notebooks. So the problem
really seems to be with the graphics/AGP/ACPI support of the Intel
855GM/PM chipsets.

Is there any way people can help to make sure someone finds the time
to look into this?

Regards,
Georg

-- 
Georg C. F. Greve                                       <greve-mXXj517/zsQ@public.gmane.org>
Free Software Foundation Europe	                 (http://fsfeurope.org)
Brave GNU World	                           (http://brave-gnu-world.org)


-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn

Re: [Fwd: Re: [PROBLEM] 2.6.3-rc1: still no suspend/resume on Centrino notebook (contains agp, lapic, swsusp)]

[Dave Jones]

On Tue, Feb 10, 2004 at 11:32:26AM +0100, Georg C. F. Greve wrote:

 > If I disable AGP, DRM/DRI and the intel framebuffer (which depends on
 > intel AGP! vesa fb is activated and works, though), compile at least
 > yenta_socket as a module, I can do suspend to disk (swsusp2) on kernel
 > 2.6.2 and resume even while X11 is running.
 > 
 > The moment I enable AGP (no DRM/DRI, no intel fb), things break.

If you have DRI & FB disabled, AGP isn't going to get used.
It's just dead code.  For this reason, I find it hard to believe its
causing a problem.

		Dave



-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn

Re: [Fwd: Re: [PROBLEM] 2.6.3-rc1: still no suspend/resume on Centrino notebook (contains agp, lapic, swsusp)]

[Georg C. F. Greve]

 || On Tue, 10 Feb 2004 19:48:16 +0000
 || Dave Jones <davej-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> wrote: 

 >> The moment I enable AGP (no DRM/DRI, no intel fb), things break.

 dj> If you have DRI & FB disabled, AGP isn't going to get used.  It's
 dj> just dead code.  For this reason, I find it hard to believe its
 dj> causing a problem.

So was I... but empirical evidence pointed towards it.

Maybe it was a false positive created by the PCMCIA (yenta) stuff,
which seems flakey wrt to ACPI/suspend/resume, but that is unlikely.

I am fairly confident that AGP breaks powermanagement for most
Centrino notebooks, in particular the 855GM ones.

Btw: Does anyone plan to pick this up anytime soon?

Regards,
Georg

-- 
Georg C. F. Greve                                       <greve-mXXj517/zsQ@public.gmane.org>
Free Software Foundation Europe	                 (http://fsfeurope.org)
Brave GNU World	                           (http://brave-gnu-world.org)


-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn

Re: [Fwd: Re: [PROBLEM] 2.6.3-rc1: still no suspend/resume on Centrino notebook (contains agp, lapic, swsusp)]

[Huw Rogers]

Near identical symptoms with SiS 648FX / 963 chipsets, and desktop P4.
I doubt this is 855 specific. More like any recent ACPI BIOS + AGP 3
specific. -Huw

>  >> If your laptop is one APIC victim, I think until this problem
>  >> isn't resolved, suspend/resume also doesn't work, is my guess.
> 
> My laptop definitely experiences the ACPI+APIC troubles, but I'm not
> sure whether that is what you refer to as "victim." :)
> 
> However: suspend/resume _almost_ work under 2.6.x -- the problem is
> the AGP code, it seems. 
> 
> If I disable AGP, DRM/DRI and the intel framebuffer (which depends on
> intel AGP! vesa fb is activated and works, though), compile at least
> yenta_socket as a module, I can do suspend to disk (swsusp2) on kernel
> 2.6.2 and resume even while X11 is running.
> 
> The moment I enable AGP (no DRM/DRI, no intel fb), things break.
> 
> As for S1/S3, it seems that S1 is almost/more or less working, but I
> can only wake up the machine with the power button and that creates an
> event to shut down the machine. :-/ Oh yeah: and the keyboard is
> broken after resume from S1.
> 
> On S3, the machine comes back up -- apparently with working keyboard,
> although I can't be 100% sure -- and the screen is dead. After typing
> "ifup eth0" on the console I can log into it over the network,
> though. :)
> 
> On the swsusp2 list, someone made a survey and found out that noone
> has AGP working on 2.6.x for their Centrino notebooks. So the problem
> really seems to be with the graphics/AGP/ACPI support of the Intel
> 855GM/PM chipsets.
> 
> Is there any way people can help to make sure someone finds the time
> to look into this?

-- 
Huw Rogers <count0-tC47gz4GrgtWk0Htik3J/w@public.gmane.org>



-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click

Re: [Fwd: Re: [PROBLEM] 2.6.3-rc1: still no suspend/resume on Centrino notebook (contains agp, lapic, swsusp)]

[Bruno Ducrot]

On Tue, Feb 10, 2004 at 12:58:06AM +0000, Sérgio Monteiro Basto wrote:
> Hi list 
> I would like to know your opinion about my guess.

MP processor do have lapic support, but actually that one may be broken if
the OEM do "forget" to connect it.  Therefore, forcing it like Linux
does hang your machine not matter what.

Note that this statement may be false for the Asus, though, and
it's not easy to be sure what actually is broken (ACPI IRQ routing code, or
hardware bug).

> 
> -----Forwarded Message-----
> > From: Sérgio Monteiro Basto <sergiomb-hHo3WeeoaswVhHzd4jOs4w@public.gmane.org>
> > To: Georg C F Greve <greve-1r/uNngapc3YtjvyW6yDsg@public.gmane.org>
> > Subject: Re: [ACPI] [PROBLEM] 2.6.3-rc1: still no suspend/resume on Centrino notebook (contains agp, lapic, swsusp)
> > Date: Mon, 09 Feb 2004 03:55:47 +0000
> > 
> > Hi Georg
> > If your laptop is one APIC victim, I think until this problem isn't
> > resolved, suspend/resume also doesn't work, is my guess.
> -- 
> Sérgio M. B.
> 
> 
> 
> -------------------------------------------------------
> The SF.Net email is sponsored by EclipseCon 2004
> Premiere Conference on Open Tools Development and Integration
> See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
> http://www.eclipsecon.org/osdn
> _______________________________________________
> Acpi-devel mailing list
> Acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> https://lists.sourceforge.net/lists/listinfo/acpi-devel

-- 
Bruno Ducrot

--  Which is worse:  ignorance or apathy?
--  Don't know.  Don't care.


-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn

Re: [Fwd: Re: [PROBLEM] 2.6.3-rc1: still no suspend/resume on Centrino notebook (contains agp, lapic, swsusp)]

[Georg C. F. Greve]

 || On Tue, 10 Feb 2004 11:34:09 +0100
 || Bruno Ducrot <ducrot-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org> wrote: 

 bd> Note that this statement may be false for the Asus, though, and
 bd> it's not easy to be sure what actually is broken (ACPI IRQ
 bd> routing code, or hardware bug).

If there is anything I can provide to clear this, let me know.

Right now it appears to be a kernel issue, as my ASUS M2N occasionally
booted with APIC&ACPI just fine -- but not the 2.6.x kernels with the
exception of 2.6.2-rc2, I think.

Regards,
Georg

-- 
Georg C. F. Greve                                       <greve-mXXj517/zsQ@public.gmane.org>
Free Software Foundation Europe	                 (http://fsfeurope.org)
Brave GNU World	                           (http://brave-gnu-world.org)


-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn