public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Joshua Schmidlkofer <kernel-cK5OC/E6E2U6GGFevw1D/A@public.gmane.org>
To: ACPI List <acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: ACPI + SiS IRQ Routing?
Date: Fri, 10 Oct 2003 07:19:19 -0700	[thread overview]
Message-ID: <1065795559.2876.5.camel@menion.home> (raw)
In-Reply-To: <1065673482.26205.10.camel-nJ1XZiZhfd3/9pzu0YdTqQ@public.gmane.org>

On Wed, 2003-10-08 at 21:24, Joshua Schmidlkofer wrote:
> On Wed, 2003-10-08 at 17:17, Joshua Schmidlkofer wrote:
> > What is the status of the SiS IRQ router?  I have two motherboards, one
> > with a 645, and one with a 648.  I have confirmed that all the way up to
> > [and including] 2.6.0-test6 I am having problems.  I am going to test
> > with mm4, but on another system I experienced a wierd Oops with mm4.  
> > 
> > I have historically had issue w/ the 1 interrupt/4 device High Point IDE
> > contollers unless I have full ACPI support enabled.  Prior to test6, I
> > had a conflict between my Nvidia [w/ or w/o binary driver].  Now, it is
> > my main USB device that suffers.  What can I do to help with the
> > process.
> > 
> > The symptom is that the ACPI interrupt begins acumlating events in
> > /proc/interrupts until it reaches something like 100000, then I get an
> > Oops about an interrupt that no one cared about [I.e. IRQ 9], and the
> > system continues to run fine.  Aside from the Oops, I don't see any
> > other problems, but I am a little afraid to run at that point.
> 
> I wanted to follow up that the 648 chipset seems to be almost 100% with
> test6.  I am building test7 now, and I will post if I have any news on
> that.
> 


   Test 7 and the 645 continue to be a problem.  It takes a lot longer
now, but something eventually begins causing more interrupts problems
with ACPI.  

   Does anyone have any comment?  Help?



> js
-- 
VB programmers ask why no one takes them seriously, 
it's somewhat akin to a McDonalds manager asking employees 
why they don't take their 'career' seriously.



-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php

  parent reply	other threads:[~2003-10-10 14:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-09  0:17 ACPI + SiS IRQ Routing? Joshua Schmidlkofer
     [not found] ` <1065658665.26205.8.camel-nJ1XZiZhfd3/9pzu0YdTqQ@public.gmane.org>
2003-10-09  4:24   ` Joshua Schmidlkofer
     [not found]     ` <1065673482.26205.10.camel-nJ1XZiZhfd3/9pzu0YdTqQ@public.gmane.org>
2003-10-10 14:19       ` Joshua Schmidlkofer [this message]
2003-10-10 22:10   ` Alan Cox
     [not found]     ` <1065823816.14982.3.camel-Z+iYsftfazAXoXS6vNje7nviChZXdy279dF7HbQ/qKg@public.gmane.org>
2003-10-10 23:10       ` Joshua Schmidlkofer
     [not found]         ` <1065827434.26428.35.camel-ANb3ei3N/+zlcIzXXilT+kEOCMrvLtNR@public.gmane.org>
2003-10-11  6:16           ` Len Brown
     [not found]             ` <1065852976.4112.84.camel-D2Zvc0uNKG8@public.gmane.org>
2003-10-13 18:50               ` Joshua Schmidlkofer
2003-10-14  4:21               ` Joshua Schmidlkofer

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=1065795559.2876.5.camel@menion.home \
    --to=kernel-ck5oc/e6e2u6ggfevw1d/a@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox