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:	Wed, 25 Jul 2007 06:55:07 -0600
From:	Bjorn Helgaas <bjorn.helgaas@...com>
To:	"Yinghai Lu" <yhlu.kernel@...il.com>
Cc:	"Jeff Garzik" <jeff@...zik.org>,
	"Maciej W. Rozycki" <macro@...ux-mips.org>,
	"Sébastien Dugué" 
	<sebastien.dugue@...l.net>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	"Andrew Morton" <akpm@...ux-foundation.org>,
	"Linus Torvalds" <torvalds@...ux-foundation.org>
Subject: Re: commit 7e92b4fc34 - x86, serial: convert legacy COM ports to platform devices - broke my serial console

On Tuesday 24 July 2007 10:27:26 pm Yinghai Lu wrote:
> On 7/24/07, Bjorn Helgaas <bjorn.helgaas@...com> wrote:
> > On Tuesday 24 July 2007 02:33:05 pm Yinghai Lu wrote:
> > > I have a system that has the same problem, and it turns out that FW
> > > missed PNP0501 is DSDT for uart. and add that it into DSDT works well.
> >
> > Is this FW that has been shipped?  Can you give any more details,
> > like DMI info and a copy of the DSDT?  We can't expect users to
> > upgrade their firmware or use a custom DSDT.
> 
> The system is not shipped yet.
> Normally PNP0501 is coming with superio section in DSDT. So i think
> late BIOS if have acpi there, that should be there already.
> Problem is that some new design may get rid of superio, but SB could
> have extra uart for serial port. at that case BIOS may not have that
> PNP0501...

If the system has a non-PCI UART that is usable by the OS, it
should be described by ACPI.  This is true regardless of whether
the UART is attached via superio or elsewhere.

So in this case, my patch just helped expose a defect in the
firmware, and it sounds like the firmware was fixed before
ever being shipped.

> or we can make legacy_serial.force=1 is default at this point.

At which point?  We already do the legacy probe if there are no
PNP devices.  Do you mean we should also do the legacy probe if
there are PNP devices, but no serial devices were found?  That
might be reasonable to do, but wouldn't have prevented the problem
on Sebastien's machine, because his machine *does* have PNP UARTs.

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