Re: NetBSD 7.0 i386 panic during boot

On Wed, Oct 14, 2015 at 11:07:08AM -0400, Christos Zoulas wrote: > Add some printfs to vmem_alloc? This is happening way too early. Is there a way to read source level info (line number etc) in the trace? May be, if that doesn't give a clue, I'll get into printfs? Mayuresh.

Re: NetBSD 7.0 i386 panic during boot

On Wed, Oct 14, 2015 at 11:07:08AM -0400, Christos Zoulas wrote: > Add some printfs to vmem_alloc? This is happening way too early. I tried enabling following option to see whether trace shows source level info. But it didn't. makeoptions DEBUG="-g" Is there any way to get source level

Re: NetBSD 7.0 i386 panic during boot

On Tue, Oct 13, 2015 at 08:20:23AM -0400, Christos Zoulas wrote: > So you have a usb keyboard and it does not work for you? > Comment out the following lines: > > #pckbc* at acpi?# PC keyboard controller > #pckbc0 at isa? # pc keyboard controller

Re: NetBSD 7.0 i386 panic during boot

On Oct 14, 8:52pm, mayur...@acm.org (Mayuresh) wrote: -- Subject: Re: NetBSD 7.0 i386 panic during boot | On Wed, Oct 14, 2015 at 11:07:08AM -0400, Christos Zoulas wrote: | > Add some printfs to vmem_alloc? This is happening way too early. | | Is there a way to read source level info (line

Re: NetBSD 7.0 i386 panic during boot

On Oct 14, 9:02pm, mayur...@acm.org (Mayuresh) wrote: -- Subject: Re: NetBSD 7.0 i386 panic during boot | On Wed, Oct 14, 2015 at 11:07:08AM -0400, Christos Zoulas wrote: | > Add some printfs to vmem_alloc? This is happening way too early. | | I tried enabling following option to see whether

bmake and interactive processes

Hello all - I've been a long time user of bmake/pmake for various tasks and have recently started using my make recipes to initiate an interactive PostgreSQL shell with the same set of arguments that I'm using elsewhere and reduce some duplication in my code. I'm finding that if I use ctrl-c to

Re: NetBSD 7.0 i386 panic during boot

On Tue, Oct 13, 2015 at 05:24:31PM +0530, Mayuresh wrote: > On Sun, Oct 11, 2015 at 01:13:42PM -0400, Christos Zoulas wrote: > > | > This looks like a NULL pointer dereference. Do you have a backtrace? > > | > > | Unfortunately the keyboard stops working when db prompt appears. So cannot > > |

View flags used in wd device

Hi! The wd (4) manpage shows some examples of the flags used with a particular device. In the output of "mount" in my system there is the following line: /dev/wd0a on / type ffs (log, local) So, could this "wd0a" device be related to wd (4)? And if it is, how can I view the flags actually used

Re: View flags used in wd device

On Wed, Oct 14, 2015 at 12:51:15PM +0200, Rocky Hotas wrote: > Hi! > The wd (4) manpage shows some examples of the flags used with a particular > device. > In the output of "mount" in my system there is the following line: > > /dev/wd0a on / type ffs (log, local) > > So, could this "wd0a"

Re: bmake and interactive processes

On Oct 13, 2015, at 8:49 PM, Malcolm Herbert wrote: I am able to restore my terminal with 'reset' or 'stty sane' however when I add these to rules within my Makefile they appear to be triggered by make but by the time it finishes, the terminal is back to its broken state. Is it any

Re: boot device unknown on netbsd 7.0

On 10 October 2015 at 11:07, Cayo Puigdefabregas wrote: > Hello, I try install netbsd 7.0 on my laptop with usb img install. > I'm get a problem with detected the root partition of usb stick. > My computer have ssd disk and I think that netbsd not found the correct >

Re: NetBSD 7.0 i386 panic during boot

On Oct 14, 2:54pm, mayur...@acm.org (Mayuresh) wrote: -- Subject: Re: NetBSD 7.0 i386 panic during boot | On a healthy system I tried triggering ddb with above kernel (with | DDB_ONPANIC set), with Ctrl-Alt-Esc. It did not print trace. yes, because that entry is not through panic(). | To cross

Re: View flags used in wd device

> Sent: Wednesday, October 14, 2015 at 1:19 PM > From: "Manuel Bouyer" > To: "Rocky Hotas" > Cc: "NetBSD Users Mailing List" > Subject: Re: View flags used in wd device [...] > The flags are defined in the kenrel config file,