new kernel for testing

[Philip Balister]

I tried the 391 kernel and still have an immediate resume after an
attempt at S3 on a Dell D600.

This is from dmesg:

PM: Preparing system for suspend
Stopping tasks:
==================================================================================================|
PCI: Setting latency timer of device 0000:00:1d.7 to 64
PCI: Setting latency timer of device 0000:00:1f.5 to 64
Restarting tasks... done
agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
agpgart: Putting AGP V2 device at 0000:00:00.0 into 1x mode
agpgart: Putting AGP V2 device at 0000:01:00.0 into 1x mode
[drm] Loading R200 Microcode

Mind you, in some sense this is an improvement over earlier attempts at
S3, which led to hanging during resume :)

Philip


On Tue, 2004-05-25 at 14:47, Satish Balay wrote:
> ACPI with the new kernel doesn't work on IBM ThinkPad T40. With
> 
> echo 3 > /proc/acpi/sleep
> 
> the machine briefly attempts to go to sleep and then comes back.
> 
> The relavent info from the log
> 
> -----
> 383
> -----
> PM: Preparing system for suspend
> Stopping tasks: ==========================================================================|
> PCI: Setting latency timer of device 0000:00:1d.7 to 64
> PCI: Setting latency timer of device 0000:00:1f.5 to 64
> PCI: Setting latency timer of device 0000:00:1f.5 to 64
> PCI: Enabling device 0000:02:00.0 (0000 -> 0002)
> PCI: Enabling device 0000:02:00.1 (0000 -> 0002)
> PCI: Enabling device 0000:02:01.0 (0000 -> 0003)
> PCI: Setting latency timer of device 0000:02:01.0 to 64
> Restarting tasks... done
> agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
> agpgart: Putting AGP V2 device at 0000:00:00.0 into 1x mode
> agpgart: Putting AGP V2 device at 0000:01:00.0 into 1x mode
> [drm] Loading R200 Microcode
> e1000: eth0 NIC Link is Up 100 Mbps Full Duplex
> 
> ----------
> 358 - release kernel that works
> ---------
> PM: Preparing system for suspend
> Stopping tasks: ============================================================================|
> PM: Entering state.
> Back to C!
> zapping low mappings.
> PM: Finishing up.
> PCI: Setting latency timer of device 0000:00:1d.0 to 64
> PCI: Setting latency timer of device 0000:00:1d.1 to 64
> PCI: Setting latency timer of device 0000:00:1d.2 to 64
> PCI: Setting latency timer of device 0000:00:1f.5 to 64
> ehci_hcd 0000:00:1d.7: HC died; cleaning up
> blk: queue 39ed4e00, I/O limit 4095Mb (mask 0xffffffff)
> Restarting tasks...<6>input: PS/2 Generic Mouse on isa0060/serio1
>   done
> agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
> agpgart: Putting AGP V2 device at 0000:00:00.0 into 1x mode
> agpgart: Putting AGP V2 device at 0000:01:00.0 into 1x mode
> [drm] Loading R200 Microcode
> e1000: eth0 NIC Link is Up 100 Mbps Full Duplex
> 
> -----------------------
> 
> Will log the complete dmesg info in bugzilla.
> 
> Satish
> 
> 
> 
> On Tue, 25 May 2004, Arjan van de Ven wrote:
> 
> > Hi,
> >
> > I've built a new kernel (2.6.6-1.383) for testing; and it just got uploaded
> > to the testing area on the fedora download site.
> > Highlights include
> > * Update to 2.6.7-rc1
> > * A patch to improve suspend/resume to ram behavior
> >  (If your laptop failed before, please test with this)
> > * Major USB update
> > * The VIA C3 bug is fixed
> > * Minor ACPI update
> >
> > The idea is to do a final update kernel in a week or two, which will include
> > some more bugfixes and hopefully the 2.6.7-final kernel. However it's still
> > useful to get this "inbetween point" tested to see if we're going in the
> > right direction.
> >
> > Greetings,
> >    Arjan van de Ven
>