Re: UEFI, loader and keyboard problems

Dimitry Andric wrote: > On 16 May 2015, at 18:50, Roman Bogorodskiy wrote: > > > > I'm running -CURRENT amd64 > > > > and have weird problems with keyboard in loader. Specifically, some char > > keys produce numbers. For example: > > > > boot --> b66t > > > > The problem appears to be with

Re: UEFI, loader and keyboard problems

On May 16, 2015, at 14:47, Allan Jude wrote: > On 2015-05-16 17:27, Dimitry Andric wrote: >> On 16 May 2015, at 18:50, Roman Bogorodskiy wrote: >>> >>> I'm running -CURRENT amd64 >>> >>> and have weird problems with keyboard in loader. Specifically, some char >>> keys produce numbers. For exam

Re: UEFI, loader and keyboard problems

On 2015-05-16 17:27, Dimitry Andric wrote: > On 16 May 2015, at 18:50, Roman Bogorodskiy wrote: >> >> I'm running -CURRENT amd64 >> >> and have weird problems with keyboard in loader. Specifically, some char >> keys produce numbers. For example: >> >> boot --> b66t >> >> The problem appears to be

Re: UEFI, loader and keyboard problems

On 16 May 2015, at 18:50, Roman Bogorodskiy wrote: > > I'm running -CURRENT amd64 > > and have weird problems with keyboard in loader. Specifically, some char > keys produce numbers. For example: > > boot --> b66t > > The problem appears to be with the right side of the query layout. > > 'y'

UEFI, loader and keyboard problems

Hi, I'm running -CURRENT amd64 and have weird problems with keyboard in loader. Specifically, some char keys produce numbers. For example: boot --> b66t The problem appears to be with the right side of the query layout. 'y' is still 'y', but 'u' becomes '4', 'i' becomes '5', etc. The same for

Re: Deja vu: panic in hdaa_coonfigure() for i386, but not amd64 -- again

On 05/16/15 17:54, David Wolfskill wrote: On Sat, May 16, 2015 at 03:50:00PM +0200, Hans Petter Selasky wrote: ... Send output from bootverbose! Let's hunt this bug down :-) OK; after restoring r282650 & r282651, clearing /usr/obj, and performing a clean buildworld, kernel, and installwor

Re: Deja vu: panic in hdaa_coonfigure() for i386, but not amd64 -- again

On Sat, May 16, 2015 at 03:50:00PM +0200, Hans Petter Selasky wrote: > ... > Send output from bootverbose! Let's hunt this bug down :-) > OK; after restoring r282650 & r282651, clearing /usr/obj, and performing a clean buildworld, kernel, and installworld, the "smoke test" reboot yielded (a r

Re: Deja vu: panic in hdaa_coonfigure() for i386, but not amd64 -- again

On Sat, May 16, 2015 at 03:46:18PM +0200, Hans Petter Selasky wrote: > ... > > Can you collect output from booting with bootverbose set? From current > amd64 as of today. OK; I just copied it over; please see ; the dmesg in question is dmesg.boot.

Re: Deja vu: panic in hdaa_coonfigure() for i386, but not amd64 -- again

On 05/16/15 15:37, David Wolfskill wrote: On Sat, May 16, 2015 at 03:27:57PM +0200, Hans Petter Selasky wrote: ... After reverting both 282650 & 282651, the resulting kernel built. Hi, I'm seeing two of my commits mentioned here, r282650 & r282651. Are these what is causing the problem? You

Re: Deja vu: panic in hdaa_coonfigure() for i386, but not amd64 -- again

On 05/16/15 15:27, Hans Petter Selasky wrote: On 05/15/15 22:07, David Wolfskill wrote: On Fri, May 15, 2015 at 02:59:10PM -0400, John Baldwin wrote: ... Hummm, the only recent change is 281544, but that should be in your working kernel. Yes; that dates from 14 April, and I had been doing dai

Re: Deja vu: panic in hdaa_coonfigure() for i386, but not amd64 -- again

On Sat, May 16, 2015 at 03:27:57PM +0200, Hans Petter Selasky wrote: > ... > > After reverting both 282650 & 282651, the resulting kernel built. > > > > Hi, > > I'm seeing two of my commits mentioned here, r282650 & r282651. Are > these what is causing the problem? You are sure the built the ker

Re: Deja vu: panic in hdaa_coonfigure() for i386, but not amd64 -- again

On 05/15/15 22:07, David Wolfskill wrote: On Fri, May 15, 2015 at 02:59:10PM -0400, John Baldwin wrote: ... Hummm, the only recent change is 281544, but that should be in your working kernel. Yes; that dates from 14 April, and I had been doing daily build/boots of head/i386 through thta period