Re: 2.5.75-mm1 yenta-socket lsPCI IRQ reads incorrect

[Russell King <rmk@arm.linux.org.uk>]

On Tue, Jul 15, 2003 at 06:42:17PM +0800, Michael Frank wrote:
> On Tuesday 15 July 2003 17:34, Michael Frank wrote:
> > Jul 15 17:05:00 mhfl2 kernel: Suspending devices
> > Jul 15 17:05:00 mhfl2 kernel: Yenta: dev suspend
> > Jul 15 17:05:00 mhfl2 kernel: Yenta: suspend saved state ff
> > Jul 15 17:05:00 mhfl2 kernel: /critical section: Counting pages to
> > copy[nosave c03e2000] (pages needed: 3426+512=3938 free: 57849) Jul 15
> > 17:05:00 mhfl2 kernel: Alloc pagedir
> > Jul 15 17:05:00 mhfl2 kernel: ....[nosave c03e2000]Enabling SEP on CPU 0
> > Jul 15 17:05:00 mhfl2 kernel: Freeing prev allocated pagedir
> >
> > power down - resume
> >
> > Jul 15 17:05:00 mhfl2 kernel: Yenta: dev resume
> 
> Dev resume ahead of socket resume?

Yes, the dev resume triggers the per-socket resume.

> > Jul 15 17:05:00 mhfl2 kernel: Yenta: init restored state ff
> > Jul 15 17:05:00 mhfl2 kernel: Trying to free nonexistent resource
> > <000003f8-000003ff> Jul 15 17:05:00 mhfl2 kernel: Yenta: init restored
> > state ff
> > Jul 15 17:05:00 mhfl2 kernel: hda: Wakeup request inited, waiting for
> > !BSY... Jul 15 17:05:00 mhfl2 kernel: hda: start_power_step(step: 1000)
> > Jul 15 17:05:00 mhfl2 kernel: hda: completing PM request, resume
> > Jul 15 17:05:01 mhfl2 kernel: Devices Resumed
> > Jul 15 17:05:01 mhfl2 kernel: Devices Resumed
> > Jul 15 17:05:01 mhfl2 kernel: Yenta: dev resume
> 
> One more dev resume

The extra resume is caused by not having all the PM information available
to PCI device drivers.  This is probably another bit of the PM interface
which needs to be fixed for 2.6.0.

-- 
Russell King (rmk@arm.linux.org.uk)                The developer of ARM Linux
             http://www.arm.linux.org.uk/personal/aboutme.html