linux-kernel - Re: [Bug 43331] Re: Bug on bootup of Linux kernel on Panasonic Toughbook S10

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Mon, 9 Jul 2012 11:26:19 -0600
From:	Bjorn Helgaas <bhelgaas@...gle.com>
To:	Yinghai Lu <yinghai@...nel.org>
Cc:	Bill Unruh <unruh@...sics.ubc.ca>, Jiang Liu <liuj97@...il.com>,
	linux-kernel@...r.kernel.org, linux-pci@...r.kernel.org,
	bugzilla-daemon@...zilla.kernel.org
Subject: Re: [Bug 43331] Re: Bug on bootup of Linux kernel on Panasonic
 Toughbook S10

> looks like they do not bios update for S10 yet.
>
> http://www.panasonic.com/business/toughbook/computer-support-bios.asp#CF-U1
>
> maybe you can try to email or call their support.

Please stop suggesting a BIOS upgrade.  The BIOS is totally out of our
control, and if the current BIOS works with Windows but not Linux,
99.99% of users will just run Windows.  Those users will just give up
on Linux, and we'll never even hear about it.

Fortunately, Bill is a sophisticated user who cared enough to report
the issue, so we have a chance to do something about it.  What we need
is for Linux to deal with this situation better, and that *IS* in our
control.

For example, we could detect the BAR being read-only when we size it.
We could use the read-only address to derive the worst-case BAR size
(32K in this case).  We could mark it as IORESOURCE_PCI_FIXED and use
that to avoid trying to move it.  We could log a message to this
effect so the next time it will take 10 minutes instead of 6 weeks to
diagnose the problem.

The end result for Bill will be the same (an unexpected message while
booting), but we can at least make the message intelligible rather
than "BAR 0: error updating (0xdfa00004 != 0xfed98004)".
--
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/