All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Frank <mflt1@micrologica.com.hk>
To: Russell King <rmk@arm.linux.org.uk>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	Pavel Machek <pavel@suse.cz>, John Belmonte <jvb@prairienet.org>
Subject: Re: 2.5.75-mm1 yenta-socket lsPCI IRQ reads incorrect
Date: Tue, 15 Jul 2003 18:42:17 +0800	[thread overview]
Message-ID: <200307151842.19851.mflt1@micrologica.com.hk> (raw)
In-Reply-To: <200307151734.46616.mflt1@micrologica.com.hk>

I'll try to trace where the interrupt dies.

I tried already an int 0x25 in yenta_init which has no effect...

BTW:

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?

> 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

Regards
Michael

-- 
Powered by linux-2.5.75-mm1. Compiled with gcc-2.95-3 - mature and rock solid

My current linux related activities:
- 2.5 yenta_socket testing
- Test development and testing of swsusp for 2.4/2.5 and ACPI S3 of 2.5 kernel 
- Everyday usage of 2.5 kernel

More info on 2.5 kernel: http://www.codemonkey.org.uk/post-halloween-2.5.txt
More info on swsusp: http://sourceforge.net/projects/swsusp/


  reply	other threads:[~2003-07-15 10:48 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-14  5:41 Yenta_socket lsPCI IRQ reads incorrect Michael Frank
2003-07-14  9:07 ` Pavel Machek
2003-07-14  9:28 ` 2.5.75-mm1 yenta-socket " Michael Frank
2003-07-14 11:01   ` Russell King
2003-07-14 11:37     ` Michael Frank
2003-07-14 14:50       ` Russell King
2003-07-14 15:04         ` Jeff Garzik
2003-07-14 15:21           ` Russell King
2003-07-14 15:18             ` Michael Frank
2003-07-14 15:34               ` Russell King
2003-07-14 15:27                 ` Michael Frank
2003-07-15  5:31         ` Michael Frank
2003-07-15  6:08           ` Michael Frank
2003-07-15  7:56           ` Russell King
2003-07-15  9:34             ` Michael Frank
2003-07-15 10:42               ` Michael Frank [this message]
2003-07-15 14:39                 ` Russell King
2003-07-15 16:09               ` Michael Frank
2003-07-16  3:16                 ` Michael Frank
2003-07-16  5:04                   ` Michael Frank

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=200307151842.19851.mflt1@micrologica.com.hk \
    --to=mflt1@micrologica.com.hk \
    --cc=jvb@prairienet.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@suse.cz \
    --cc=rmk@arm.linux.org.uk \
    /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.