All of lore.kernel.org
 help / color / mirror / Atom feed
From: thomas schorpp <t.schorpp@gmx.de>
To: SCSI development list <linux-scsi@vger.kernel.org>
Subject: Re: aic7xxx: aic7892(B): BUG: soft lockup detected on CPU#0!
Date: Fri, 23 Mar 2007 08:32:12 +0100	[thread overview]
Message-ID: <4603827C.4080701@gmx.de> (raw)
In-Reply-To: <1174625139.30030.31.camel@mulgrave.il.steeleye.com>

James Bottomley wrote:
> On Fri, 2007-03-23 at 02:26 +0100, thomas schorpp wrote:
>> ok, overriding the first while(ahc_is_paused) that blocked before 
>> (i see no sense for doing this in a pci mmap test function, cause 
>> proper resource setup is required *before* using such I/O functions, 
>> otherwise the adapter had entered SEQ paused status)
>> i got the kernel to boot at least at pio mode.
>>
>> this is surely not the correct resource and looks like a datatype 
>> boundary overflow, the upper 0x0f is missing:
>> [   49.278810] Trying to free nonexistent resource
>> <00000000fffff000-00000000fff
>> fffff>
> 
> That's because ahc->platform_data->mem_busaddr is u32
> 
> 
>> [   54.513224] scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 7.0
>> [   54.513226]         <Adaptec 19160B Ultra160 SCSI adapter>
>> [   54.513227]         aic7892: Ultra160 Wide Channel A, SCSI Id=7, 32/253 SCBs
> 
> The driver code suggests that the 7892 can't do the AHC_LARGE_SCBS
> features ... which means the card itself cannot address more than 32
> bits of memory, so it would be unable to decode a BAR that's beyond the
> 32 bit range.  So this looks like some type of error in the PCI config
> system (or possibly in the BIOS).  I think this card needs its BARs to
> be in the lower 32 bits to function.
> 
> James
> 
> 

i agree for this to be a 32bit dma busmaster chip,
since pci_resource_flags and lspci say 64bit mem resource type

aic7xxx: pci_resource_start fffff000 *maddr 20000 mem64 4

we've a bug in the x86_64 linux pci config, BIOS is ok, 
the hardware worked fine in a winxp_x64 test setup a few months ago.

will ask LKML.

y
tom

  reply	other threads:[~2007-03-23  7:32 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-22 15:14 aic7xxx: aic7892(B): BUG: soft lockup detected on CPU#0! thomas schorpp
2007-03-22 16:57 ` thomas schorpp
2007-03-22 21:02   ` thomas schorpp
2007-03-22 23:00     ` thomas schorpp
2007-03-23  1:26       ` thomas schorpp
2007-03-23  4:45         ` James Bottomley
2007-03-23  7:32           ` thomas schorpp [this message]
2007-03-23 16:28             ` thomas schorpp
2007-03-23 17:23               ` James Bottomley
2007-03-23 18:23                 ` thomas schorpp
2007-03-23 18:59                   ` thomas schorpp
2007-03-24  0:51                     ` thomas schorpp
2007-03-24  1:17                       ` James Bottomley
2007-03-24  3:44                         ` thomas schorpp
2007-03-24  4:05                           ` thomas schorpp
2007-03-27  6:52                             ` thomas schorpp
2007-03-29 20:13                               ` thomas schorpp

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=4603827C.4080701@gmx.de \
    --to=t.schorpp@gmx.de \
    --cc=linux-scsi@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.