All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chuck Ebbert <cebbert@redhat.com>
To: linux-kernel@vger.kernel.org,
	Ivan Kokshaysky <ink@jurassic.park.msu.ru>,
	Greg Kroah-Hartman <gregkh@suse.de>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: regression on quad Xeon: no SCSI-disks
Date: Tue, 01 May 2007 12:01:56 -0400	[thread overview]
Message-ID: <46376474.8090505@redhat.com> (raw)
In-Reply-To: <20070501142431.GA11667@erig.dyndns.org>

Wolfgang Erig wrote:
> Sorry
> for detecting this 2 year old regression so late.
> 
> 2.6.13 or later is bad.
> 2.6.12 is good,
> 
> "git bisect" worked fine and points to the attached patch.
> The patch is pretty small. The problem seemed to be dependant
> on the PCI-architecture of these particular systems.
> Tried this on two machines with the same behaviour.
> 
> Wolfgang
> 
> 
> $ git bisect bad 
> 299de0343c7d18448a69c635378342e9214b14af is first bad commit
> commit 299de0343c7d18448a69c635378342e9214b14af
> Author: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
> Date:   Wed Jun 15 18:59:27 2005 +0400
> 
>     [PATCH] PCI: pci_assign_unassigned_resources() on x86
>     
>     - Add sanity check for io[port,mem]_resource in setup-bus.c. These
>       resources look like "free" as they have no parents, but obviously
>       we must not touch them.
>     - In i386.c:pci_allocate_bus_resources(), if a bridge resource cannot be
>       allocated for some reason, then clear its flags. This prevents any child
>       allocations in this range, so the setup-bus code will work with a clean
>       resource sub-tree.
>     - i386.c:pcibios_enable_resources() doesn't enable bridges, as it checks
>       only resources 0-5, which looks like a clear bug to me. I suspect it
>       might break hotplug as well in some cases.
>     
>     From: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
>     Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
> 
> :040000 040000 ecab084beb95987f3e4ead8b61ce19cc052a5fa3 4c1364a6fd511b6dc6ddec06d787bcf105687835 M      arch
> :040000 040000 0956f28cde32bd7494d7a87e2814bcd726547a32 0d2e2b611b007085e5a0994a66fd9c0a873ac8f8 M      drivers
> 
> ====== on console =======
> sym0: <875> rev 0x26 at pci 0000:01:02.0 irq 30
> sym0: Symbios NVRAM, ID 7, Fast-20, SE, parity checking
> sym0: open drain IRQ line driver, using on-chip SRAM
> sym0: using LOAD/STORE-based firmware.
> sym0: SCSI BUS has been reset.
> scsi0 : sym-2.2.0
> scsi 0:0:0:0 ABORT operation started.
> scsi 0:0:0:0 ABORT operation timed-out.
> scsi 0:0:0:0 DEVICE RESET operation started.
> scsi 0:0:0:0 DEVICE RESET operation timed-out.
> scsi 0:0:0:0 BUS RESET operation started.
> scsi 0:0:0:0 BUS RESET operation timed-out.
>       ....

Output from kernel with CONFIG_PCI_DEBUG could be useful.


  reply	other threads:[~2007-05-01 16:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-01 14:24 regression on quad Xeon: no SCSI-disks Wolfgang Erig
2007-05-01 16:01 ` Chuck Ebbert [this message]
2007-05-02 14:47   ` Wolfgang Erig
2007-05-02 17:12     ` Ivan Kokshaysky
2007-05-03  8:41       ` Wolfgang Erig
2007-05-03 23:18         ` Ivan Kokshaysky
2007-05-04 13:22           ` Wolfgang Erig

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=46376474.8090505@redhat.com \
    --to=cebbert@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=gregkh@suse.de \
    --cc=ink@jurassic.park.msu.ru \
    --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 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.