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]
Message-ID: <20061022163141.GF4354@rhun.haifa.ibm.com>
Date:	Sun, 22 Oct 2006 18:31:41 +0200
From:	Muli Ben-Yehuda <muli@...ibm.com>
To:	Andi Kleen <ak@...e.de>
Cc:	Yinghai Lu <yinghai.lu@....com>,
	"Eric W. Biederman" <ebiederm@...ssion.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] x86-64: typo in __assign_irq_vector when updating pos for vector and offset

On Sun, Oct 22, 2006 at 03:29:38PM +0200, Andi Kleen wrote:
> 
> > This patch breaks my x366 machine:
> >  
> > aic94xx: device 0000:01:02.0: SAS addr 5005076a0112df00, PCBA SN , 8 phys, 8 enabled phys, flash present, BIOS build 1323
> > aic94xx: couldn't get irq 25 for 0000:01:02.0
> > ACPI: PCI interrupt for device 0000:01:02.0 disabled
> > aic94xx: probe of 0000:01:02.0 failed with error -38
> > 
> > Reverting it allows it to boot again. Since the patch is "obviously
> > correct", it must be uncovering some other problem with the genirq
> > code.
> 
> I wonder if the machine works when booted with a 32bit kernel?

Mostly... I don't have a 32-bit initrd environment for aic94xx, so I
gave it a spin with aic94xx built in and without firmware. It made it
as far as trying to mount the root device, and then sat there spitting
this out continously:

atkbd.c: Spurious ACK on isa0060/serio0. Some program might be trying
access hardware directly

I can put together a 32-bit initrd and try booting all the way if
it'll be a useful experiment, let me know.

Cheers,
Muli
-
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ