Re: kern/52034 (Kernel panic on Google Compute Engine)

To: jdolecek%NetBSD.org@localhost, netbsd-bugs%netbsd.org@localhost, gnats-admin%netbsd.org@localhost, jdolecek%NetBSD.org@localhost, bsiegert%NetBSD.org@localhost
Subject: Re: kern/52034 (Kernel panic on Google Compute Engine)
From: jdolecek%NetBSD.org@localhost
Date: Tue, 7 Mar 2017 22:05:04 +0000 (UTC)

Synopsis: Kernel panic on Google Compute Engine

State-Changed-From-To: analyzed->feedback
State-Changed-By: jdolecek%NetBSD.org@localhost
State-Changed-When: Tue, 07 Mar 2017 22:05:04 +0000
State-Changed-Why:
A fix was committed to -current, can you try it out?

FWIW, I tried booting 7.1_RC2 kernel on 'micro' google compute instance
and it worked, as well as -current kernel before my change. I guess
it depends on amount of RAM for the VM.

Follow-Ups:
- Re: kern/52034 (Kernel panic on Google Compute Engine)
  - From: Benny Siegert

Prev by Date: NetBSD Nightly Trouble Ticket Report
Next by Date: PR/52034 CVS commit: src/sys/dev/pci
Previous by Thread: Re: kern/52034 (Kernel panic on Google Compute Engine)
Next by Thread: Re: kern/52034 (Kernel panic on Google Compute Engine)
Indexes:

Home | Main Index | Thread Index | Old Index