mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew de Quincey <adq_dvb@lidskialf.net>
To: Chris Wright <chrisw@osdl.org>
Cc: lkml <linux-kernel@vger.kernel.org>, acpi-devel@lists.sourceforge.net
Subject: Re: [ACPI] Re: [PATCH] Next round of ACPI IRQ fixes (VIA ACPI fixed)
Date: Sat, 6 Sep 2003 02:21:30 +0100	[thread overview]
Message-ID: <200309060221.30741.adq_dvb@lidskialf.net> (raw)
In-Reply-To: <20030905170224.A16217@osdlab.pdx.osdl.net>

On Saturday 06 Sep 2003 1:02 am, Chris Wright wrote:
> * Andrew de Quincey (adq_dvb@lidskialf.net) wrote:
> > On Friday 05 Sep 2003 10:35 pm, Jeff Garzik wrote:
> > > This is why we _really_ need you to split up your patches.  Multiple
> > > split-up patches, one per email, is preferred.  Don't worry about
> > > sending us too much email:  we like it like that.
> >
> > If/when I split it up, is it acceptable to number the patches to give the
> > order they have to be applied in? The major problem with these particular
> > fixes is that they all run over the same set of files, even the same
> > functions, so they all conflict with each other.
>
> Yes, please split them up.
>
> I finally narrowed down to the ChangeSet 1.1046.1.424 (ACPI: Allow irqs >
> 15...) as cause to my current hang-on-boot problem.  Quick test to see
> if this patch fixes...nope ;-(

I have reports of a number of systems with issues like this. 

I have a machine here (A Fujitsu Siemens TX150 server) in which the SCSI 
controller actually corrupts the low level format of the hard disk if I 
enable ACPI! (low level reformat required!). The ACPI IRQ setup seems to work 
fine on it (as I assume it does on your system). Its just that there seems to 
be "something else" wrong in ACPI still. Weirdly enough, it can read sector 0 
of the HDD fine.. just any reads of any other sectors cause this corruption.

Now that I've got the bulk of the changes to the basic ACPI IRQ setup done, I 
can concentrate on these issues. Can you give me details of your system and 
the following items:

successful dmesg
dmesg from a failed boot
/proc/acpi/dsdt
/proc/interrupts


  reply	other threads:[~2003-09-06  0:23 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-05 18:58 Andrew de Quincey
2003-09-05 21:35 ` Jeff Garzik
2003-09-05 23:16   ` [ACPI] " Andrew de Quincey
2003-09-05 22:28     ` Jeff Garzik
2003-09-05 22:28       ` Andrew Morton
2003-09-05 22:56         ` Randy.Dunlap
2003-09-06  0:15       ` [PATCH] 2.4.23-pre3 ACPI fixes series (1/3) Andrew de Quincey
2003-09-10 11:45         ` Bernhard Rosenkraenzer
2003-09-10 21:27           ` Andrew de Quincey
2003-09-10 15:31         ` Daniel Egger
2003-09-06  0:15       ` [PATCH] 2.4.23-pre3 ACPI fixes series (2/3) Andrew de Quincey
2003-09-06  0:15       ` [PATCH] 2.4.23-pre3 ACPI fixes series (3/3) Andrew de Quincey
2003-09-06  0:57       ` [PATCH] 2.6.0-test4 ACPI fixes series (1/4) Andrew de Quincey
2003-09-06  0:57       ` [PATCH] 2.6.0-test4 ACPI fixes series (2/4) Andrew de Quincey
2003-09-06  0:57       ` [PATCH] 2.6.0-test4 ACPI fixes series (3/4) Andrew de Quincey
2003-09-06  0:57       ` [PATCH] 2.6.0-test4 ACPI fixes series (4/4) Andrew de Quincey
2003-09-06  1:22         ` Jeff Garzik
2003-09-06 12:27           ` [ACPI] " Andrew de Quincey
2003-09-06 13:45             ` Andi Kleen
2003-09-08 19:46           ` Mikael Pettersson
2003-09-06 15:47         ` [ACPI] " Alan Cox
2003-09-07 14:54           ` Andrew de Quincey
2003-09-07 17:59             ` Alan Cox
2003-09-07 20:19               ` Andrew de Quincey
2003-09-06  0:02     ` [ACPI] Re: [PATCH] Next round of ACPI IRQ fixes (VIA ACPI fixed) Chris Wright
2003-09-06  1:21       ` Andrew de Quincey [this message]
2003-09-06  0:30         ` Jeff Garzik
2003-09-06  2:03           ` Chris Wright
2003-09-06 12:32             ` Andrew de Quincey
2003-09-11  1:36               ` Chris Wright

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=200309060221.30741.adq_dvb@lidskialf.net \
    --to=adq_dvb@lidskialf.net \
    --cc=acpi-devel@lists.sourceforge.net \
    --cc=chrisw@osdl.org \
    --cc=linux-kernel@vger.kernel.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

Powered by JetHome