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]
Date:	Mon, 22 Mar 2010 15:18:21 -0700
From:	Bjorn Helgaas <bjorn.helgaas@...com>
To:	Otavio Salvador <otavio@...ystems.com.br>
Cc:	Giampaolo Bellini <iw2lsi@...il.com>,
	Linux PCI <linux-pci@...r.kernel.org>,
	linux-kernel@...r.kernel.org, "Rafael J. Wysocki" <rjw@...k.pl>
Subject: Re: PCI conflicts with latest kernels

On Monday 22 March 2010 03:27:18 pm Otavio Salvador wrote:
> Hello Bjorn,
> 
> On Mon, Mar 22, 2010 at 11:50 AM, Bjorn Helgaas <bjorn.helgaas@...com> wrote:
> > On Monday 22 March 2010 08:41:03 am Otavio Salvador wrote:
> >> I have this same problem in VortexSX machine.
> > Can you post your entire dmesg log and a description of what
> > problem you're seeing (e.g., device X doesn't work or whatever)?
> > If this is a regression, i.e., your system used to work and
> > now doesn't work, please tell us which version used to work
> > and when it broke.

Since you don't mention any working version, I assume that Linux
has never worked correctly on this system.

> This has already been done at http://article.gmane.org/gmane.linux.kernel/916237

That post is about the fact that your disk doesn't work unless you
use "irqpoll".  That just means the interrupts don't appear where
we expect them, which has nothing to do with the PCI address space
collisions.

I'm sorry I don't know enough about interrupts to help more.  If
I were debugging it, I would start by adding printks to the
pirq_enable_irq() path and see if I could figure out why it works
for some devices, but for IDE.

Bjorn
--
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