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: Tue, 27 Mar 2007 08:52:06 +0200 [thread overview]
Message-ID: <4608BF16.3000100@gmx.de> (raw)
In-Reply-To: <4604A397.6000402@gmx.de>
thomas schorpp wrote:
> thomas schorpp wrote:
>> James Bottomley wrote:
>>> On Sat, 2007-03-24 at 01:51 +0100, thomas schorpp wrote:
>>>>> no. so the pci layer reports wrong start:
>>>> nonsense. it succeeds, confused function return with the error flag:
>>>>
>>>> // u_long start;
>>>> // u_long start = 0xFFEFF000;
>>>> u_long start = 0x30000000;
>>>> int error;
>>>>
>>>> struct resource* ret1;
>>>> error = 0;
>>>> // start = pci_resource_start(ahc->dev_softc, 1);
>>>> if (start != 0) {
>>>> *bus_addr = start;
>>>> if ((ret1 = request_mem_region(start, 0x1000,
>>>> "aic7xxx")) == 0)
>>>
>>> You can't do this. The pci_resource_start is getting the address of
>>> something called a Bus Address Register (BAR) it says in physical
>>> address space where the card is responding ... you can't simply set that
>>> to a random value.
>>>
>>> The problem you seem to have is that your system is reporting a BAR
>>> beyond 32 bits (4GB) which the card physically can't use. This could be
>>> because of a BIOS misconfiguration or because there's a bug in the PCI
>>> subsystem somewhere.
>>>
>>> James
>>
>> understood. waiting for LKML answers... meanwhile i found harder
>> reason for a possible bounds problem with the driver code on x86_64:
>>
>> if i do:
>>
>> static int
>> ahc_linux_pci_reserve_mem_region(struct ahc_softc *ahc,
>> u_long *bus_addr,
>> uint8_t __iomem **maddr)
>> {
>> // u_long start;
>> uint32_t start;
>>
>> i get no free warning of "*nonexistant* resource" (it cant be
>> nonexistant, cause it was definitely something mapped):
>>
>> tom1:/usr/src/linux# dmesg |grep -i free
>> Freeing unused kernel memory: 208k freed
>>
>> with u_long type start i get it:
>> Mar 24 03:41:47 localhost kernel: Trying to free nonexistent resource
>> <00000000fffff000-00000000ffffffff>
>>
>> investigating further...
>> -
>
> hmm well i dont get the free warning cause
> release_mem_region(ahc->platform_data->mem_busaddr,
> 0x1000);
> isnt called, the hack fails
> error = ahc_linux_pci_reserve_mem_region(ahc, &base, &maddr);
> if (error == 0) {
>
> ok, so no bounds issue in the driver.
>
LKML people are ignoring my report, i take this as agreement to a mb bios issue.
will test the card with a latest debian kernel x86_64 netinstall cd on some other amd64
machine, but i need to find some in my reach here.
i need more confirmation before working in the linux pci hal.
y
tom
next prev parent reply other threads:[~2007-03-27 6:52 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
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 [this message]
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=4608BF16.3000100@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox