this kind of thing is pretty common. Linux has intermittent problems working on machines built without a real(TM) bios. Few people test in unnatural(TM) coreboot environments so you see errors you might not expect. I've had this off and on since we started in 1999 ....
On Mon, Oct 9, 2017 at 5:26 AM Trammell Hudson hudson@trmm.net wrote:
On Mon, Oct 09, 2017 at 12:58:25PM +0300, Аладышев Константин wrote:
I try to port coreboot on boards with Haswell CPU and Lynxpoint LP
chipset
(IBASE IB908AF-4650 board, DFI HU968) and I've encountered a strange problem. USB devices stop working shortly after OS boot (or after USB
device
replug in OS) with flooding system with messages:
Interesting -- I ran into the exact same bug with Haswell while porting the NERF firmware and a 4.9.x kernel, and had attributed it to my not setting up something right. It's good to hear that maybe it isn't my fault (maybe).
[...] Through some digging I've found out that this problem persist on kernels <3.5. I've investigated this problem more closely and come down to the
fact
that the kernel commit that solves this problem is:
3d9545c EHCI: maintain the ehci->command value properly
https://github.com/torvalds/linux/commit/3d9545cc375d117554a9b35dfddadf9189c 62775?diff=split
Does it work if you back out that patch? For my purpose it might be enough to maintain a patch until we figure out what is really going on.
-- Trammell
-- coreboot mailing list: coreboot@coreboot.org https://mail.coreboot.org/mailman/listinfo/coreboot