r247095 Boot Failure
I'm on r247095. My box is failing to boot on a Dell Precision T7500. I'm running ZFS as root with a mirrored root pool. Here's a pic of the box failing: https://lh5.googleusercontent.com/-Lq_jlX8of0o/USY4cqZ5BOI/GoI/Nd1LGPbFjHc/s1112/IMG_20130221_100723.jpg There isn't much useful information in the pic. No crash dump is generated. Where do I go from here? I can boot into kernel.old and that works as a workaround for now. Thanks, Shawn ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: r247095 Boot Failure
On Thu, Feb 21, 2013 at 10:28:15AM -0500, Shawn Webb wrote: I'm on r247095. My box is failing to boot on a Dell Precision T7500. I'm running ZFS as root with a mirrored root pool. Here's a pic of the box failing: https://lh5.googleusercontent.com/-Lq_jlX8of0o/USY4cqZ5BOI/GoI/Nd1LGPbFjHc/s1112/IMG_20130221_100723.jpg There isn't much useful information in the pic. No crash dump is generated. Where do I go from here? Take a look at the -CURRENT userland regression thread. You may be able to boot if you choose safe mode in the boot loader menu. Regards, Navdeep I can boot into kernel.old and that works as a workaround for now. Thanks, Shawn ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: r247095 Boot Failure
On Thu, Feb 21, 2013 at 3:34 PM, Navdeep Parhar npar...@gmail.com wrote: Take a look at the -CURRENT userland regression thread. You may be able to boot if you choose safe mode in the boot loader menu. Regards, Navdeep What is safe mode as far as boot flags? boot -sv doesn't work on my system... Matt ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: r247095 Boot Failure
On 21 February 2013 19:38, matt sendtom...@gmail.com wrote: On Thu, Feb 21, 2013 at 3:34 PM, Navdeep Parhar npar...@gmail.com wrote: Take a look at the -CURRENT userland regression thread. You may be able to boot if you choose safe mode in the boot loader menu. Regards, Navdeep What is safe mode as far as boot flags? Currently that corresponds to: set kern.smp.disabled=1 set hw.ata.ata_dma=0 set hw.ata.atapi_dma=0 set hw.ata.wc=0 set hw.eisa_slots=0 set kern.eventtimer.periodic=1 set kern.geom.part.check_integrity=0 See /boot/menu-commands.4th -- wbr, pluknet ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: r247095 Boot Failure
On Thu, Feb 21, 2013 at 03:38:41PM +, matt wrote: On Thu, Feb 21, 2013 at 3:34 PM, Navdeep Parhar npar...@gmail.com wrote: Take a look at the -CURRENT userland regression thread. You may be able to boot if you choose safe mode in the boot loader menu. Regards, Navdeep What is safe mode as far as boot flags? This is the forth code that sets up safe mode: : safemode_enable ( -- ) s set kern.smp.disabled=1 evaluate s set hw.ata.ata_dma=0 evaluate s set hw.ata.atapi_dma=0 evaluate s set hw.ata.wc=0 evaluate s set hw.eisa_slots=0 evaluate s set kern.eventtimer.periodic=1 evaluate s set kern.geom.part.check_integrity=0 evaluate ; loader.conf should be able to set up those variables too (temporarily, as a workaround). I wonder which one does the trick - smp.disabled or eventtimer_periodic, or ..? Regards, Navdeep boot -sv doesn't work on my system... Matt ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: r247095 Boot Failure
On Thu, Feb 21, 2013 at 3:46 PM, Sergey Kandaurov pluk...@gmail.com wrote: Currently that corresponds to: set kern.smp.disabled=1 set hw.ata.ata_dma=0 set hw.ata.atapi_dma=0 set hw.ata.wc=0 set hw.eisa_slots=0 set kern.eventtimer.periodic=1 set kern.geom.part.check_integrity=0 See /boot/menu-commands.4th -- wbr, pluknet Enabling beastie, safe mode boots. The userland thread wasn't terribly descriptive about symptoms, and this sure doesn't *look* like a userland problem. Trying to reduce it to a specific option First, no variables or alternate kernels work until I type show (that seems broken) Setting all of the kern variables allow it to boot Setting all of the hw.ata.*dma doesn't change anything Setting hw.ata.wc causes a panic/reboot Matt ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: r247095 Boot Failure
On Thu, Feb 21, 2013 at 3:46 PM, Sergey Kandaurov pluk...@gmail.comwrote: Currently that corresponds to: set kern.smp.disabled=1 set hw.ata.ata_dma=0 set hw.ata.atapi_dma=0 set hw.ata.wc=0 set hw.eisa_slots=0 set kern.eventtimer.periodic=1 set kern.geom.part.check_integrity=0 See /boot/menu-commands.4th -- wbr, pluknet It's kern.smp.disabled=1 that allows boot. Matt ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: r247095 Boot Failure
Shawn Webb wrote this message on Thu, Feb 21, 2013 at 10:28 -0500: I'm on r247095. My box is failing to boot on a Dell Precision T7500. I'm running ZFS as root with a mirrored root pool. Here's a pic of the box failing: https://lh5.googleusercontent.com/-Lq_jlX8of0o/USY4cqZ5BOI/GoI/Nd1LGPbFjHc/s1112/IMG_20130221_100723.jpg There isn't much useful information in the pic. No crash dump is generated. Where do I go from here? I can boot into kernel.old and that works as a workaround for now. Some how, my changes to gcc in r247012 is causing this, even when using the default of clang as cc... I was able to reproduce a crash myself, and then I just backed my change and the new kernel booted... I'm about to do a binary diff between the broken kernel and the new kernel (since I only installed the kernel, not userland) and figure out which part of the system.. But clearly, we are still using gcc somehow in our kernel builds... If I don't figure out what it is in a few hours, I'll back out the change... -- John-Mark Gurney Voice: +1 415 225 5579 All that I will do, has been done, All that I have, has not. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: r247095 Boot Failure
Am 02/21/13 16:28, schrieb Shawn Webb: I'm on r247095. My box is failing to boot on a Dell Precision T7500. I'm running ZFS as root with a mirrored root pool. Here's a pic of the box failing: https://lh5.googleusercontent.com/-Lq_jlX8of0o/USY4cqZ5BOI/GoI/Nd1LGPbFjHc/s1112/IMG_20130221_100723.jpg There isn't much useful information in the pic. No crash dump is generated. Where do I go from here? I can boot into kernel.old and that works as a workaround for now. Thanks, Shawn Well, I guess you faced the same problem I reported in two days ago. I have this crash on ALL(!) of my FreeBSD 10.0-CURRENT boxes, which use CLANG as the default compiler as well as setting CXXFLAGS+= -stdlib=libc++ CXXFLAGS+= -std=c++1 The working kernel on those boxes is FreeBSD 10.0-CURRENT #0 r246949: Mon Feb 18 22:20:30 CET 2013/amd64 On our Intel Core2Duo (Q6600/E8400) boxes the crash looks like yours in the picture, but sometimes there is trap 18 or trap 16 instead of the cryptic signs. On a more modern Ivy-Bridge i3-3220, I get blinking, funky funny clock characters on the screen - this box uitilizes as a server the Intel iGPU of the CPU. Since I use customized kernels, I tried to start with the official GENERIC kernel and disabling every setting in /boot/loader.conf, but the result is even with such a setting the same - all boxes crashes with the kernel sources r246949. I also tried to enable the debugging features in the customized kernel (as they are enabled in the GENERIC), but there is no chance to get any backtrace, the kernel simply gets stuck or - on the mentioned box with the ivy Bridge, simply blinking funnily as a home computer in the late 80s. Sorry for being unable to report more substantial facts on that. Oliver signature.asc Description: OpenPGP digital signature
Re: r247095 Boot Failure
On Thu, Feb 21, 2013 at 08:40:44PM +0100, O. Hartmann wrote: Am 02/21/13 16:28, schrieb Shawn Webb: I'm on r247095. My box is failing to boot on a Dell Precision T7500. I'm running ZFS as root with a mirrored root pool. Here's a pic of the box failing: https://lh5.googleusercontent.com/-Lq_jlX8of0o/USY4cqZ5BOI/GoI/Nd1LGPbFjHc/s1112/IMG_20130221_100723.jpg There isn't much useful information in the pic. No crash dump is generated. Where do I go from here? I can boot into kernel.old and that works as a workaround for now. Thanks, Shawn Well, I guess you faced the same problem I reported in two days ago. I have this crash on ALL(!) of my FreeBSD 10.0-CURRENT boxes, which use CLANG as the default compiler as well as setting CXXFLAGS+= -stdlib=libc++ CXXFLAGS+= -std=c++1 The working kernel on those boxes is FreeBSD 10.0-CURRENT #0 r246949: Mon Feb 18 22:20:30 CET 2013/amd64 On our Intel Core2Duo (Q6600/E8400) boxes the crash looks like yours in the picture, but sometimes there is trap 18 or trap 16 instead of the cryptic signs. On a more modern Ivy-Bridge i3-3220, I get blinking, funky funny clock characters on the screen - this box uitilizes as a server the Intel iGPU of the CPU. Since I use customized kernels, I tried to start with the official GENERIC kernel and disabling every setting in /boot/loader.conf, but the result is even with such a setting the same - all boxes crashes with the kernel sources r246949. I also tried to enable the debugging features in the customized kernel (as they are enabled in the GENERIC), but there is no chance to get any backtrace, the kernel simply gets stuck or - on the mentioned box with the ivy Bridge, simply blinking funnily as a home computer in the late 80s. Sorry for being unable to report more substantial facts on that. The supposed fix was committed as r247117. pgpQhxzEdDqJD.pgp Description: PGP signature
Re: r247095 Boot Failure
Am 02/21/13 20:51, schrieb Konstantin Belousov: On Thu, Feb 21, 2013 at 08:40:44PM +0100, O. Hartmann wrote: Am 02/21/13 16:28, schrieb Shawn Webb: I'm on r247095. My box is failing to boot on a Dell Precision T7500. I'm running ZFS as root with a mirrored root pool. Here's a pic of the box failing: https://lh5.googleusercontent.com/-Lq_jlX8of0o/USY4cqZ5BOI/GoI/Nd1LGPbFjHc/s1112/IMG_20130221_100723.jpg There isn't much useful information in the pic. No crash dump is generated. Where do I go from here? I can boot into kernel.old and that works as a workaround for now. Thanks, Shawn Well, I guess you faced the same problem I reported in two days ago. I have this crash on ALL(!) of my FreeBSD 10.0-CURRENT boxes, which use CLANG as the default compiler as well as setting CXXFLAGS+= -stdlib=libc++ CXXFLAGS+= -std=c++1 The working kernel on those boxes is FreeBSD 10.0-CURRENT #0 r246949: Mon Feb 18 22:20:30 CET 2013/amd64 On our Intel Core2Duo (Q6600/E8400) boxes the crash looks like yours in the picture, but sometimes there is trap 18 or trap 16 instead of the cryptic signs. On a more modern Ivy-Bridge i3-3220, I get blinking, funky funny clock characters on the screen - this box uitilizes as a server the Intel iGPU of the CPU. Since I use customized kernels, I tried to start with the official GENERIC kernel and disabling every setting in /boot/loader.conf, but the result is even with such a setting the same - all boxes crashes with the kernel sources r246949. I also tried to enable the debugging features in the customized kernel (as they are enabled in the GENERIC), but there is no chance to get any backtrace, the kernel simply gets stuck or - on the mentioned box with the ivy Bridge, simply blinking funnily as a home computer in the late 80s. Sorry for being unable to report more substantial facts on that. The supposed fix was committed as r247117. Simply compiling a new kernel doesn't resolve the problem. -- Updating /usr/src using Subversion -- /usr/local/bin/svn update -r HEAD Updating '.': At revision 247121. This kernel crashes the same way. As it is supposed to be a gcc-change, I guess I have to recompile the whole world? Doing so by now. If not necessary to build world - then the bug is still persent - at least in my case. Regards, Oliver signature.asc Description: OpenPGP digital signature
Re: r247095 Boot Failure
On Thu, Feb 21, 2013 at 09:14:07PM +0100, O. Hartmann wrote: The supposed fix was committed as r247117. Simply compiling a new kernel doesn't resolve the problem. See the commit message why your kernel appears to not work. http://svnweb.freebsd.org/base?view=revisionrevision=247117 Did you update gas before building the new kernel? -- Steve ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: r247095 Boot Failure
I'm building now. I should know whether or not it works. I'm assuming the updated gas is in base? My userland is r247095, but my kernel is r246990. On Thu, Feb 21, 2013 at 3:21 PM, Steve Kargl s...@troutmask.apl.washington.edu wrote: On Thu, Feb 21, 2013 at 09:14:07PM +0100, O. Hartmann wrote: The supposed fix was committed as r247117. Simply compiling a new kernel doesn't resolve the problem. See the commit message why your kernel appears to not work. http://svnweb.freebsd.org/base?view=revisionrevision=247117 Did you update gas before building the new kernel? -- Steve ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: r247095 Boot Failure
Am 02/21/13 22:01, schrieb Shawn Webb: I'm building now. I should know whether or not it works. I'm assuming the updated gas is in base? My userland is r247095, but my kernel is r246990. On Thu, Feb 21, 2013 at 3:21 PM, Steve Kargl s...@troutmask.apl.washington.edu wrote: On Thu, Feb 21, 2013 at 09:14:07PM +0100, O. Hartmann wrote: The supposed fix was committed as r247117. Simply compiling a new kernel doesn't resolve the problem. See the commit message why your kernel appears to not work. http://svnweb.freebsd.org/base?view=revisionrevision=247117 Did you update gas before building the new kernel? -- Steve Update now in progress, didn't update gas in the first place. Oliver signature.asc Description: OpenPGP digital signature
Re: r247095 Boot Failure
The results are in: success! Thanks everyone. This is why I love FreeBSD: the community is amazing! On Thu, Feb 21, 2013 at 4:54 PM, O. Hartmann ohart...@zedat.fu-berlin.dewrote: Am 02/21/13 22:01, schrieb Shawn Webb: I'm building now. I should know whether or not it works. I'm assuming the updated gas is in base? My userland is r247095, but my kernel is r246990. On Thu, Feb 21, 2013 at 3:21 PM, Steve Kargl s...@troutmask.apl.washington.edu wrote: On Thu, Feb 21, 2013 at 09:14:07PM +0100, O. Hartmann wrote: The supposed fix was committed as r247117. Simply compiling a new kernel doesn't resolve the problem. See the commit message why your kernel appears to not work. http://svnweb.freebsd.org/base?view=revisionrevision=247117 Did you update gas before building the new kernel? -- Steve Update now in progress, didn't update gas in the first place. Oliver ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: r247095 Boot Failure
Am 02/21/13 22:55, schrieb Shawn Webb: The results are in: success! Thanks everyone. This is why I love FreeBSD: the community is amazing! On Thu, Feb 21, 2013 at 4:54 PM, O. Hartmann ohart...@zedat.fu-berlin.dewrote: Am 02/21/13 22:01, schrieb Shawn Webb: I'm building now. I should know whether or not it works. I'm assuming the updated gas is in base? My userland is r247095, but my kernel is r246990. On Thu, Feb 21, 2013 at 3:21 PM, Steve Kargl s...@troutmask.apl.washington.edu wrote: On Thu, Feb 21, 2013 at 09:14:07PM +0100, O. Hartmann wrote: The supposed fix was committed as r247117. Simply compiling a new kernel doesn't resolve the problem. See the commit message why your kernel appears to not work. http://svnweb.freebsd.org/base?view=revisionrevision=247117 Did you update gas before building the new kernel? -- Steve Update now in progress, didn't update gas in the first place. Oliver Works for me, too. Thanks a lot. oh signature.asc Description: OpenPGP digital signature
Re: r247095 Boot Failure
OK here as well. Tested sandybridge opteron. Matt On Thu, Feb 21, 2013 at 10:28 PM, O. Hartmann ohart...@zedat.fu-berlin.dewrote: Works for me, too. Thanks a lot. oh ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
