public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Joshua Schmidlkofer <menion-8BColdH5dlvzIImvGDD8mw@public.gmane.org>
To: Len Brown <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: ACPI List <acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: ACPI + SiS IRQ Routing?
Date: Mon, 13 Oct 2003 21:21:46 -0700	[thread overview]
Message-ID: <1066105305.4424.9.camel@menion.home> (raw)
In-Reply-To: <1065852976.4112.84.camel-D2Zvc0uNKG8@public.gmane.org>

Well first I have a little trouble sorting out the problem with that bug
report.  It looks like USB failure is the key symptom.  I see no
symptoms, except the oops.  I will enshrine this in a new bug report.

Also, my problems are with 2.6.0-testX, and I have not done much testing
with 2.4.xx.  Tell me, is pci=noacpi, or acpi=off a recommended way to
go?  I have a similar problem with the 645 mostly.  The 648 has given me
very few problems.  I will create a report for the 645, and try to
re-produce reliable problems with the 648.

js


On Fri, 2003-10-10 at 23:16, Len Brown wrote:
> Does your SiS 648 system behave like this one?:
> http://bugme.osdl.org/show_bug.cgi?id=1283
> 
> Can you describe how the 645 behaviour differs -- hopefully in a bug
> report?
> 
> thanks,
> -Len
> 
> 
> 
> 
> -------------------------------------------------------
> 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
> _______________________________________________
> Acpi-devel mailing list
> Acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> https://lists.sourceforge.net/lists/listinfo/acpi-devel
-- 
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-14  4:21 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
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 [this message]

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=1066105305.4424.9.camel@menion.home \
    --to=menion-8bcoldh5dlvziimvgdd8mw@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@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