linux-kernel - Re: pnp bug in 2.6.27-rc1 (ad1816a / mpu401 / parport

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

Message-Id: <200808131054.06469.bjorn.helgaas@hp.com>
Date:	Wed, 13 Aug 2008 10:54:05 -0600
From:	Bjorn Helgaas <bjorn.helgaas@...com>
To:	Uwe Bugla <uwe.bugla@....de>
Cc:	akpm@...l.org, perex@...ex.cz, abelay@....edu,
	debian-kernel@...ts.debian.org, linux-kernel@...r.kernel.org
Subject: Re: pnp bug in 2.6.27-rc1 (ad1816a / mpu401 / parport_pc issue)

On Wednesday 13 August 2008 09:47:04 am Uwe Bugla wrote:
> Am Tuesday 12 August 2008 23:26:12 schrieben Sie:
> > On Tuesday 12 August 2008 12:10:51 pm Bjorn Helgaas wrote:
> > > On Tuesday 12 August 2008 05:17:26 am Uwe Bugla wrote:
> > > > Case C:
> > > > same preconditions as case B, but additionally:
> > > > 1. no IRQs reserved for ISA use only (in BIOS)
> > > > This option I would call "PNP pure"
> > > >
> > > > ...
> > > > My only criticism within the desired case C (no additional screwing
> > > > around done by user)
> > > > consists of two points:
> > > > 1. I'd prefer the second parport running with IRQ 5 instead of in
> > > > polling mode.
> > >
> > > Yes, that would be good.  But I think the only way to achieve this
> > > reliably is to use the "pnp_reserve_irq=5" kernel parameter and the
> > > "options parport_pc io=0x278 irq=5" module parameter.

I see several things that should be fixed in ISAPNP.  I'm working
on those, but they're probably post-2.6.27 material.

In the meantime, are you seeing new problems that were introduced
between 2.6.26 and 2.6.27-rc3?  If so, I should try to fix them
right away so we can get a fix in 2.6.27.

Your original report of "WARNING: at lib/vsprintf.c:609 vsnprintf+0x36/0x43d()"
has been fixed already.  I *think* the remaining issues about the
parport1 IRQ and the MPU401 are related to the BIOS configuration
and the parport_pc module parameters and are not regressions from
2.6.26, but please correct me if I'm wrong.

Thanks for your patience with all this.  I'm putting together an ISA
machine at home now, so hopefully I'll soon have a way to test this
better without wasting your time.

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/