linux-kernel - Re: [3.8-rc4 arm] SCSI_SYM53C8XX

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:	Sun, 27 Jan 2013 22:21:55 +0100
From:	Linus Walleij <linus.walleij@...aro.org>
To:	Tetsuo Handa <penguin-kernel@...ove.sakura.ne.jp>
Cc:	rob.herring@...xeda.com, grant.likely@...retlab.ca,
	rmk+kernel@....linux.org.uk, linux-kernel@...r.kernel.org
Subject: Re: [3.8-rc4 arm] SCSI_SYM53C8XX_2 module cannot register IRQ

On Sun, Jan 27, 2013 at 1:16 AM, Tetsuo Handa
<penguin-kernel@...ove.sakura.ne.jp> wrote:
> Linus Walleij wrote:
>> I'm trying to reproduce this, but how do you reconfigure the kernel to
>> get PCI, SCSI and such stuff enabled?
>>
>> The stock versatile_defconfig does not even have SCSI enabled...
>
> I'm using a customized config for qemu. I've just updated the config to
> http://I-love.SAKURA.ne.jp/tmp/config-3.8-rc1-arm .

Hm when I try this on the v3.7 I get this:

PCI: enabling device 0000:00:0d.0 (0100 -> 0102)
sym0: <895a> rev 0x0 at pci 0000:00:0d.0 irq 28
sym0: No NVRAM, ID 7, Fast-40, LVD, parity checking
sym0: SCSI BUS has been reset.

So IRQ 28 instead of 27???

Then the device does not work (no clue why it's like that)
but it's trying IRQ 28 atleast.

On v3.8-rc5 I get this:

PCI: enabling device 0000:00:0d.0 (0100 -> 0103)
sym0: <895a> rev 0x0 at pci 0000:00:0d.0 irq 28
sym0: No NVRAM, ID 7, Fast-40, LVD, parity checking
sym0: request irq 28 failure
sym0: giving up ...

OK, so half-guessing I've reproduced part of the problem
atleast...

Yours,
Linus Walleij
--
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/