Re: Ways to report trace when boot panics [Was NetBSD 7.0 i386 panic during boot]

On 12 October 2015 at 10:32, Robert Elz wrote: > Long long ago I did an implementation of config code (more or less a console) > for a device that had nothing but ethernet. For that (and to avoid the > issue that would arise here, of needing specialised client code) I used

Re: Ways to report trace when boot panics [Was NetBSD 7.0 i386 panic during boot]

2015-10-12 7:50 GMT+02:00 Robert Elz : > No, that makes no sense. The whole point is that no-one has RS232 > on anything modern - forcing it to exist, just because it is what used > to be used helps nothing. This generalising statement is at least wrong in an industrial

Re: Ways to report trace when boot panics [Was NetBSD 7.0 i386 panic during boot]

> no-one has RS232 on anything modern In my experience, this isn't true. Granted, it might be for Laptops, but even modern desktop/workstation hardware tends to have RS232 -- they just don't expose the physical connector on the backside. I have yet to see an mainboard that wouldn't have a 9-pin

Ways to report trace when boot panics [Was NetBSD 7.0 i386 panic during boot]

On Mon, Oct 12, 2015 at 11:21:41AM +0700, Robert Elz wrote: > Without that, all that you can get is what you can see on the screen. I think this topic is worth discussing. I have seen several mail threads where people paste threads, obviously gathered systematically. But I do not know how they do

Re: Ways to report trace when boot panics [Was NetBSD 7.0 i386 panic during boot]

Date:Mon, 12 Oct 2015 10:31:32 +0530 From:Mayuresh Message-ID: <20151012050132.GA11271@odin> | Even nicer if such device could be a smartphone, which can make it | convenient to collect data, just from ease point of view. Yes, that would work