linux-kernel - Re: INITIO scsi driver fails to work properly

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 21 Dec 2007 17:43:03 -0500
From:	Chuck Ebbert <cebbert@...hat.com>
To:	James Bottomley <James.Bottomley@...senPartnership.com>
CC:	Filippos Papadopoulos <psybases@...il.com>,
	Boaz Harrosh <bharrosh@...asas.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, linux-scsi@...r.kernel.org
Subject: Re: INITIO scsi driver fails to work properly

On 12/21/2007 04:03 PM, James Bottomley wrote:
> On Fri, 2007-12-21 at 14:30 -0500, Chuck Ebbert wrote:
>> On 12/19/2007 03:48 AM, Filippos Papadopoulos wrote:
>>> On Dec 17, 2007 2:18 PM, Boaz Harrosh <bharrosh@...asas.com> wrote:
>>>> I have found one problem. Please try patch [2] below and report.
>>>> If it still fails try to enable debugging by setting with patch [1]
>>>> these values at top of drivers/scsi/initio.c. And send dmsgs.
>>>>
>>>> Boaz
>>>>
>>>
>>> I tried patch[2] (addition of   sg++)  at 2.6.24-rc5-mm1 but the
>>> system hangs after some seconds when the initio driver loads.
>>> I will try patch[1] next week to see what happens.
>>>
>>> Would it be better to open a bug report at bugzilla?
>>>
>> There is also a Fedora bug report against 2.6.23. The user has
>> applied commit e9e42faf47255274a1ed0b9bf1c46118023ec5fa from
>> 2.6.24-rc plus the two additional fixes under discussion and it
>> hangs for him too.
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=390531
> 
> It really sounds like there's some problem applying the patches.  The
> consistent report throughout is this one:
> 
> initio: I/O port range 0x0 is busy.
> 
> Which should be fixed by 99f1f534922a2f2251ba05b14657a1c62882a80e.  I
> didn't actually find that in the bug thread anywhere, but maybe I missed
> it?
> 

The "I/O port 0" bug just prints the message and the system continues
to run. It's only after that is fixed that the system just hangs on
boot shortly after loading the driver.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/