All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Frank <mflt1@micrologica.com.hk>
To: linux-kernel <linux-kernel@vger.kernel.org>
Cc: Pavel Machek <pavel@suse.cz>, John Belmonte <jvb@prairienet.org>
Subject: Yenta_socket lsPCI IRQ reads incorrect
Date: Mon, 14 Jul 2003 13:41:44 +0800	[thread overview]
Message-ID: <200307141333.03911.mflt1@micrologica.com.hk> (raw)

[mhf@mhfl2 13:40:27 mhf]$ cat /proc/interrupts
           CPU0
  0:    1242348          XT-PIC  timer
  1:       5253          XT-PIC  i8042
  2:          0          XT-PIC  cascade
  5:         88          XT-PIC  Toshiba America Info ToPIC95 PCI to Cardb, serial
  8:          0          XT-PIC  rtc
  9:        162          XT-PIC  acpi
 10:       1003          XT-PIC  eth0
 12:      23967          XT-PIC  i8042
 14:       8698          XT-PIC  ide0
NMI:          0
LOC:          0
ERR:          5
MIS:          0


lspci shows that IRQ level: byte 3C is FF, it should be 5

00:12.0 CardBus bridge: Toshiba America Info Systems ToPIC95 PCI to Cardbus Bridge with ZV Support (rev 32)
00: 79 11 17 06 00 00 90 04 32 00 07 06 00 40 82 00
10: 00 10 00 10 80 00 80 04 00 01 04 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 00 00 00 00 00 00 00 00 ff 01 00 00
40: 79 11 01 00 01 00 00 00 00 00 00 00 00 00 00 00
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

When this value is used by pci_restore_state, interrupt 
obviously dies.

Dunno if this is hardware readback fault or driver issue.

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-14  5:38 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-14  5:41 Michael Frank [this message]
2003-07-14  9:07 ` Yenta_socket lsPCI IRQ reads incorrect 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
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=200307141333.03911.mflt1@micrologica.com.hk \
    --to=mflt1@micrologica.com.hk \
    --cc=jvb@prairienet.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@suse.cz \
    /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.