All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J.A. Magallon" <jamagallon@able.es>
To: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.23-rc4
Date: Mon, 24 Nov 2003 23:01:46 +0100	[thread overview]
Message-ID: <20031124220146.GA1823@werewolf.able.es> (raw)
In-Reply-To: <Pine.LNX.4.44.0311241656430.8709-100000@logos.cnet> (from marcelo.tosatti@cyclades.com on Mon, Nov 24, 2003 at 19:58:06 +0100)


On 11.24, Marcelo Tosatti wrote:
> 
> Hi, 
> 
> Here goes -rc4, fixing modular IDE breakage present in 2.4.23 kernels.
> 

Hey, you posted rc4 before I could talk about rc3... ;)
Good and bad news. Good are that pci=noacpi works. Bad are that
ACPI still fails to setup PCI bus 1 on a ServerWorks LE.
I think this is not a showstopper, but...
Relevant info is at

http://giga.cps.unizar.es/~magallon/linux/acpi/

dmesg for -rc3 without acpi, just what CONFIG_SMP uses, with acpi, and with
acpi but booted with pci=noacpi (all with lspci at the end), and output
from dmidecode, biosdecode and acpidmp.

I have also submited an entry in bugzilla.
For my blind eyes, it looks like an IRQ routing problem.

TIA

-- 
J.A. Magallon <jamagallon()able!es>     \                 Software is like sex:
werewolf!able!es                         \           It's better when it's free
Mandrake Linux release 10.0 (Cooker) for i586
Linux 2.4.23-rc3-jam1 (gcc 3.3.1 (Mandrake Linux 9.2 3.3.1-4mdk))

  parent reply	other threads:[~2003-11-24 22:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-24 18:58 Linux 2.4.23-rc4 Marcelo Tosatti
2003-11-24 19:39 ` Chuck Harding
2003-11-24 19:59   ` Marcelo Tosatti
     [not found] ` <Pine.LNX.4.44.0311241656430.8709-100000-IP5UegVbiV6sTnJN9+BGXg@public.gmane.org>
2003-11-24 22:01   ` J.A. Magallon
2003-11-24 22:01 ` J.A. Magallon [this message]
2003-11-24 22:21 ` [Linux 2.4.23-rc4] NFS mounts on top of initrd J.A. Magallon
2003-11-26  0:25   ` Trond Myklebust

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=20031124220146.GA1823@werewolf.able.es \
    --to=jamagallon@able.es \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo.tosatti@cyclades.com \
    /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.