On Sat, Jun 27, 2020 at 04:24:21PM +0100, Patrick Welche wrote:
> Trying a today's -current/amd64 with DIAGNOSTIC/DEBUG/LOCKDEBUG, I can
> boot multiuser without a network. If I log in as root, as soon as I hit
> enter:
>
> # ifconfig wm0 inet 10.0.0.62 netmask 0xff00
> [ 127.5763268] Kernel
Hello, all.
On 2020/07/06 17:03, Masanobu SAITOH wrote:
Hi, all.
On 2020/06/29 12:53, Kengo NAKAHARA wrote:
Hi,
On 2020/06/28 0:24, Patrick Welche wrote:
Trying a today's -current/amd64 with DIAGNOSTIC/DEBUG/LOCKDEBUG, I can
boot multiuser without a network. If I log in as root, as soon as
Hi, all.
On 2020/06/29 12:53, Kengo NAKAHARA wrote:
> Hi,
>
> On 2020/06/28 0:24, Patrick Welche wrote:
>> Trying a today's -current/amd64 with DIAGNOSTIC/DEBUG/LOCKDEBUG, I can
>> boot multiuser without a network. If I log in as root, as soon as I hit
>> enter:
>>
>> # ifconfig wm0 inet
On Mon, Jun 29, 2020 at 12:53:23PM +0900, Kengo NAKAHARA wrote:
> It seems some other code have held KERNEL_LOCK too long time.
> Could you show the function of last locked address?
> # e.g. addr2line -e "your kernel image" -f 0x80a7d2f5
With Jun 28 14:26 code
# addr2line -e netbsd.3.gdb
Hi,
On 2020/06/28 0:24, Patrick Welche wrote:
Trying a today's -current/amd64 with DIAGNOSTIC/DEBUG/LOCKDEBUG, I can
boot multiuser without a network. If I log in as root, as soon as I hit
enter:
# ifconfig wm0 inet 10.0.0.62 netmask 0xff00
[ 127.5763268] Kernel lock error 127.5763268]
On Sat, Jun 27, 2020 at 04:24:21PM +0100, Patrick Welche wrote:
> (must try with biosboot instead fo EFI which is the case here)
makes no difference
Trying a today's -current/amd64 with DIAGNOSTIC/DEBUG/LOCKDEBUG, I can
boot multiuser without a network. If I log in as root, as soon as I hit
enter:
# ifconfig wm0 inet 10.0.0.62 netmask 0xff00
[ 127.5763268] Kernel lock error 127.5763268] lock address : 0x8106ab40
type :
