From: Fabio Coatti <cova@ferrara.linux.it>
To: "Brown, Len" <len.brown@intel.com>
Cc: "Andrew Morton" <akpm@osdl.org>, <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.3-mm1 and aic7xxx
Date: Tue, 2 Mar 2004 00:33:43 +0100 [thread overview]
Message-ID: <200403020033.43356.cova@ferrara.linux.it> (raw)
In-Reply-To: <200403010139.28956.cova@ferrara.linux.it>
Alle 01:39, lunedì 1 marzo 2004, Fabio Coatti ha scritto:
> Alle 00:45, lunedì 1 marzo 2004, Brown, Len ha scritto:
> > To verify with the latest software, please apply the latest ACPI patch
> > to 2.6.4-rc1:
> >
> > http://ftp.kernel.org/pub/linux/kernel/people/lenb/acpi/patches/release/
> > 2.6.4/acpi-20040220-2.6.4.diff.gz
> >
> > If it works, then something else in -mm is causing your problem. If it
> > fails, then something in the latest ACPI patch (which is included in
> > -mm1) is causing the failure.
>
> Tried, and with the patch all works just fine. So it can be something else,
> applied in -mm tree after 2.6.3-rc3-mm1, tha causes the failure; i'll try
> to have a look at changes, trying to find which one causes the problem.
I've just tried, as suggested by john stultz <johnstul@us.ibm.com> in thread
"2.6.3-mm3 hangs on boot x440 (scsi?)":
>> Index: arch/i386/kernel/acpi/boot.c
>> ===================================================================
>> RCS file: /var/cvs/linux-2.6/arch/i386/kernel/acpi/boot.c,v
>> retrieving revision 1.10
>> diff -u -p -r1.10 boot.c
>> --- a/arch/i386/kernel/acpi/boot.c 17 Feb 2004 12:51:46 -0000 1.10
>> +++ b/arch/i386/kernel/acpi/boot.c 26 Feb 2004 16:34:12 -0000
>> @@ -506,24 +461,17 @@ acpi_boot_init (void)
>>
>> acpi_lapic = 1;
>>
>> -#endif /*CONFIG_X86_LOCAL_APIC*/
>> +#endif /* CONFIG_X86_LOCAL_APIC */
>>
>> #if defined(CONFIG_X86_IO_APIC) && defined(CONFIG_ACPI_INTERPRETER)
>>
>> /*
>> * I/O APIC
>> - * --------
>> */
>>
>> - /*
>> - * ACPI interpreter is required to complete interrupt setup,
>> - * so if it is off, don't enumerate the io-apics with ACPI.
>> - * If MPS is present, it will handle them,
>> - * otherwise the system will stay in PIC mode
>> - */
>> - if (acpi_disabled || acpi_noirq) {
>> + if (acpi_noirq) {
>> return 1;
>> - }
>> + }
>>
>> /*
>> * if "noapic" boot option, don't look for IO-APICs
>
>
>That chunk shouldn't drop the "if (acpi_disabled ..." bit.
>Adding that check back in fixes it for me.
In fact, this fixes 2.6.4-rc1-mm1 and now I'm writing using that kernel. I
don't knoe w if this is a quick hack or a definitive solution, but now mmX
series works again for me, and scsi devices seems to be correctly handled.
--
Fabio Coatti http://www.ferrara.linux.it/members/cova
Ferrara Linux Users Group http://ferrara.linux.it
GnuPG fp:9765 A5B6 6843 17BC A646 BE8C FA56 373A 5374 C703
Old SysOps never die... they simply forget their password.
next prev parent reply other threads:[~2004-03-01 23:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-29 23:45 2.6.3-mm1 and aic7xxx Brown, Len
2004-03-01 0:39 ` Fabio Coatti
2004-03-01 23:33 ` Fabio Coatti [this message]
[not found] <A6974D8E5F98D511BB910002A50A6647615F2BAD@hdsmsx402.hd.intel.com>
2004-02-23 7:28 ` Len Brown
2004-02-23 9:06 ` Fabio Coatti
2004-02-29 23:30 ` Fabio Coatti
2004-02-29 23:42 ` Andrew Morton
2004-03-01 0:37 ` Fabio Coatti
-- strict thread matches above, loose matches on Subject: below --
2004-02-21 10:47 P. Christeas
2004-02-19 21:34 Fabio Coatti
2004-02-20 0:21 ` Andrew Morton
2004-02-20 20:22 ` Fabio Coatti
2004-02-21 0:53 ` Fabio Coatti
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=200403020033.43356.cova@ferrara.linux.it \
--to=cova@ferrara.linux.it \
--cc=akpm@osdl.org \
--cc=len.brown@intel.com \
--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