linux-kernel - Re: Conflict when loading initio driver

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] [day] [month] [year] [list]

Message-ID: <79759ec90710100722s4384ca79if67167257cb431bc@mail.gmail.com>
Date:	Wed, 10 Oct 2007 07:22:52 -0700
From:	"Scott Simpson" <simpson100@...il.com>
To:	"Alan Cox" <alan@...rguk.ukuu.org.uk>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Conflict when loading initio driver

OK. I did some debugging in this initio.c driver. I put printk
statements at the beginning of each routine and I got the following
output:

initio_se2_rd
initio_se2_instr
(The previous two routines repeat a bunch of times then I get:)
initio_stop_bm
i91u: PCI Base=0xEC00, IRQ=0, BIOS=0x0000, SCSI ID=7
i91u: Reset SCSI Bus...
initio_reset_scsi
scsi2: Initio INI-9X00U/UW SCSI device driver
i91u_queuecommand
initio_alloc_scb

So it seems to be dieing in initio_alloc_scb. I think it is dieing on
the first spin lock if that makes any sense, but it could be dieing
somewhere else in that routine. Hope this helps.
-
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/