Re: Crash on -current on i386 (NOT amd64)

2015-12-05 Thread John Nemeth
On Dec 5, 7:56am, Christos Zoulas wrote: } On Dec 5, 3:30pm, p...@vps1.whooppee.com (Paul Goyette) wrote: } } | > } The same sources were used to create a amd64-current system, and I was } | > } able to install it successfully. } | > } } | > } FWIW, my source tree is time-stamped at "2015-12-05

Re: Crash on -current on i386 (NOT amd64)

2015-12-05 Thread John Nemeth
On Dec 6, 6:36am, Paul Goyette wrote: } On Sat, 5 Dec 2015, John Nemeth wrote: } > On Dec 6, 6:12am, Paul Goyette wrote: } > } On Sat, 5 Dec 2015, John Nemeth wrote: } > } } > } > } What's the backtrace? Ideally I'd like to remove the DIOCGPART code... } > } > } > } > I don't think there was

Re: Crash on -current on i386 (NOT amd64)

2015-12-05 Thread Paul Goyette
On Sat, 5 Dec 2015, John Nemeth wrote: On Dec 6, 6:12am, Paul Goyette wrote: } On Sat, 5 Dec 2015, John Nemeth wrote: } } > } What's the backtrace? Ideally I'd like to remove the DIOCGPART code... } > } > I don't think there was a backtrace. ... } } Correct. I was unable to get a backtrace

Re: Crash on -current on i386 (NOT amd64)

2015-12-05 Thread John Nemeth
On Dec 6, 6:12am, Paul Goyette wrote: } On Sat, 5 Dec 2015, John Nemeth wrote: } } > } What's the backtrace? Ideally I'd like to remove the DIOCGPART code... } > } > I don't think there was a backtrace. ... } } Correct. I was unable to get a backtrace - ddb got a recursive fault } when I t

Re: Crash on -current on i386 (NOT amd64)

2015-12-05 Thread Paul Goyette
On Sat, 5 Dec 2015, John Nemeth wrote: } What's the backtrace? Ideally I'd like to remove the DIOCGPART code... I don't think there was a backtrace. ... Correct. I was unable to get a backtrace - ddb got a recursive fault when I tried to get the backtrace. +--+---

Re: Crash on -current on i386 (NOT amd64)

2015-12-05 Thread Christos Zoulas
On Dec 5, 1:57pm, jnem...@cue.bc.ca (John Nemeth) wrote: -- Subject: Re: Crash on -current on i386 (NOT amd64) | I don't think there was a backtrace. I saw your comment on | chat that you had fixed the lseek(SEEK_END) issue, and was curious | what it was, so I looked for the commit

Re: Crash on -current on i386 (NOT amd64)

2015-12-05 Thread Christos Zoulas
On Dec 5, 3:30pm, p...@vps1.whooppee.com (Paul Goyette) wrote: -- Subject: Re: Crash on -current on i386 (NOT amd64) | > } The same sources were used to create a amd64-current system, and I was | > } able to install it successfully. | > } | > } FWIW, my source tree is time-stamped

Re: Crash on -current on i386 (NOT amd64)

2015-12-05 Thread John Nemeth
On Dec 5, 1:25pm, Paul Goyette wrote: } On Sat, 5 Dec 2015, Paul Goyette wrote: } } >>> With up-to-the-minute sources, I got the following crash while trying } >>> to install i386-current in a qemu-VM. } >>> } >>> ioctl DIOCGMEDIASIZE failed 19ge media | } >>> uvm_fault(0xc2983d40, 0, 1) -> 0xe

Re: Crash on -current on i386 (NOT amd64)

2015-12-05 Thread Paul Goyette
} With up-to-the-minute sources, I got the following crash while trying } to install i386-current in a qemu-VM. } } ioctl DIOCGMEDIASIZE failed 19ge media | } uvm_fault(0xc2983d40, 0, 1) -> 0xe | } fatal page fault in supervisor mode| } trap type 6

Re: Crash on -current on i386 (NOT amd64)

2015-12-04 Thread Paul Goyette
On Sat, 5 Dec 2015, Paul Goyette wrote: Let me try this again ... With up-to-the-minute sources, I got the following crash while trying to install i386-current in a qemu-VM. ioctl DIOCGMEDIASIZE failed 19ge media | uvm_fault(0xc2983d40, 0, 1) -> 0xe | fatal page fault

Re: Crash on -current on i386 (NOT amd64)

2015-12-04 Thread Paul Goyette
Let me try this again ... With up-to-the-minute sources, I got the following crash while trying to install i386-current in a qemu-VM. ioctl DIOCGMEDIASIZE failed 19ge media | uvm_fault(0xc2983d40, 0, 1) -> 0xe | fatal page fault in supervisor mode