Re: Trouble building release with docs
On Sat, 20 Jul 2013, Daniel O'Connor wrote: Hi, I am trying to do a full (customised) release of 9.1 but I am having trouble building the docs. If I use NODOC it builds fine, but without that I get.. [andenes 7:04] /usr/src/release #/usr/bin/time make release BUILDNAME=$BUILDNAME make -C /usr/src/release BUILDNAME=9.1-GENESIS obj make -C /usr/src/release BUILDNAME=9.1-GENESIS ftp cdrom memstick cd /usr/src/release/doc make all install clean 'FORMATS=html txt' INSTALL_COMPRESSED='' URLS_ABSOLUTE=YES DOCDIR=/usr/obj/usr/src/release/rdoc === en_US.ISO8859-1 (all) === en_US.ISO8859-1/relnotes (all) /usr/bin/grep '^?xml version=.*?' article.xml article.parsed.xml.tmp grep: article.xml: No such file or directory *** [article.parsed.xml] Error code 2 Stop in /usr/src/release/doc/en_US.ISO8859-1/relnotes. *** [all] Error code 1 Stop in /usr/src/release/doc/en_US.ISO8859-1. *** [all] Error code 1 Stop in /usr/src/release/doc. *** [reldoc] Error code 1 Stop in /usr/src/release. *** [release] Error code 1 Stop in /usr/src/release. 0.48 real 0.37 user 0.10 sys There is article.sgml though.. I have installed textproc/docproj and I can build /usr/docs fine. What does svn say about that file? % cd /usr/src/release/doc/en_US.ISO8859-1/relnotes/ % svn stat The article.sgml suggests a leftover file from an earlier /usr/src that was not removed before svn checkout. That does not explain why article.xml is missing, though. It is present on my 9-stable and 8-stable checkouts. Maybe a mixed or partial checkout? FWIW, it wasn't in my checkout from July 2, either (8-STABLE) --Chris ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Trouble building release with docs
On Sat, Jul 20, 2013 at 04:44:56PM +0930, Daniel O'Connor wrote: Hi, I am trying to do a full (customised) release of 9.1 but I am having trouble building the docs. If I use NODOC it builds fine, but without that I get.. [...] May I ask why 9.1? Glen pgpfrnmjTGwgQ.pgp Description: PGP signature
Re: Trouble building release with docs
On 21/07/2013, at 16:19, Glen Barber g...@freebsd.org wrote: On Sat, Jul 20, 2013 at 04:44:56PM +0930, Daniel O'Connor wrote: Hi, I am trying to do a full (customised) release of 9.1 but I am having trouble building the docs. If I use NODOC it builds fine, but without that I get.. [...] May I ask why 9.1? Actually that's an excellent question :) I though 9.1 was coming out not 9.2 but that is not correct. So, if I rebuild with 9.2 checked out will the docs build? Thanks -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au The nice thing about standards is that there are so many of them to choose from. -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C signature.asc Description: Message signed with OpenPGP using GPGMail
Re: Trouble building release with docs
On Sun, Jul 21, 2013 at 05:19:23PM +0930, Daniel O'Connor wrote: On 21/07/2013, at 16:19, Glen Barber g...@freebsd.org wrote: On Sat, Jul 20, 2013 at 04:44:56PM +0930, Daniel O'Connor wrote: Hi, I am trying to do a full (customised) release of 9.1 but I am having trouble building the docs. If I use NODOC it builds fine, but without that I get.. [...] May I ask why 9.1? Actually that's an excellent question :) I though 9.1 was coming out not 9.2 but that is not correct. So, if I rebuild with 9.2 checked out will the docs build? Yes. Glen pgps1UAFUAUzN.pgp Description: PGP signature
Panic: 9.2-PRERELEASE - enc_daemon usb LOR?
Hi Folks, I'm seeing a panic with the 9.2-PRERELEASE code. The system will stay up for anywhere from a couple of seconds to a few hours and then panic. Fatal trap 12: page fault while in kernel mode cpuid = 31; apic id = 2f fault virtual address = 0x0 fault code = supervisor read data, page not present instruction pointer = 0x20:0x80d2b018 stack pointer = 0x28:0xffbfd0fea080 frame pointer = 0x28:0xffbfd0fea0b0 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 25 (enc_daemon7) and: db:0:kdb.enter.default show pcpu cpuid= 31 dynamic pcpu = 0xff807f203880 curthread= 0xfe0032f53920: pid 25 enc_daemon7 curpcb = 0xffbfd0feabc0 fpcurthread = none idlethread = 0xfe002600b920: tid 100034 idle: cpu31 curpmap = 0x8141b510 tssp = 0x81489e98 commontssp = 0x81489e98 rsp0 = 0xffbfd0feabc0 gs32p= 0x81487fd0 ldt = 0x81488010 tss = 0x81488000 This looks like a bug I started tracing down a while back with the new enclosure services (r246437 and later). I added witness into the kernel and received the following LOR: Kernel page fault with the following non-sleepable locks held: exclusive sleep mutex MPT2SAS lock (MPT2SAS lock) r = 0 (0xff8003c851b8) locked @ cam/cam_periph.h:192 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2a/frame 0xffbfd0f3cb20 kdb_backtrace() at kdb_backtrace+0x37/frame 0xffbfd0f3cbe0 _witness_debugger() at _witness_debugger+0x2c/frame 0xffbfd0f3cc00 witness_warn() at witness_warn+0x2d2/frame 0xffbfd0f3cd40 trap_pfault() at trap_pfault+0x6a/frame 0xffbfd0f3cdd0 trap() at trap+0x344/frame 0xffbfd0f3cfd0 calltrap() at calltrap+0x8/frame 0xffbfd0f3cfd0 --- trap 0xc, rip = 0x80ca8478, rsp = 0xffbfd0f3d090, rbp = 0xffbfd0f3d0c0 --- memcpy() at memcpy+0x8/frame 0xffbfd0f3d0c0 ses_setphyspath_callback() at ses_setphyspath_callback+0xb3/frame 0xffbfd0f3d1d0 ses_path_iter_devid_callback() at ses_path_iter_devid_callback+0x1c6/frame 0xffbfd0f3d770 ses_devids_iter() at ses_devids_iter+0xb1/frame 0xffbfd0f3d7f0 ses_paths_iter() at ses_paths_iter+0x20/frame 0xffbfd0f3d810 ses_publish_physpaths() at ses_publish_physpaths+0x264/frame 0xffbfd0f3da40 enc_daemon() at enc_daemon+0x2a4/frame 0xffbfd0f3daa0 fork_exit() at fork_exit+0x11d/frame 0xffbfd0f3daf0 fork_trampoline() at fork_trampoline+0xe/frame 0xffbfd0f3daf0 --- trap 0, rip = 0, rsp = 0xffbfd0f3dbb0, rbp = 0 --- Fatal trap 12: page fault while in kernel mode cpuid = 8; apic id = 08 fault virtual address = 0x0 fault code = supervisor read data, page not present instruction pointer = 0x20:0x80ca8478 stack pointer = 0x28:0xffbfd0f3d090 frame pointer = 0x28:0xffbfd0f3d0c0 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 30 (enc_daemon12) lock order reversal: (Giant after non-sleepable) 1st 0xff8003c851b8 MPT2SAS lock (MPT2SAS lock) @ cam/cam_periph.h:192 2nd 0x8139bc80 Giant (Giant) @ dev/usb/input/ukbd.c:1942 ^^^ I'm wondering if there is a bad interaction here. The system has 8 DS2700 shelves dual attached to a pair of LSI 8e cards, thus the kernel configuration with an increased msgbuf size. Kernel conf: include GENERIC ident ZFS options DDB options KDB options WITNESS options MSGBUF_SIZE=(32768*16) And some ddb output: db:0:kdb.enter.default run lockinfo db:1:lockinfo show locks exclusive sleep mutex MPT2SAS lock (MPT2SAS lock) r = 0 (0xff8003c851b8) locked @ cam/cam_periph.h:192 db:1:locks show alllocks Process 30 (enc_daemon12) thread 0xfe003421a000 (100155) exclusive sleep mutex MPT2SAS lock (MPT2SAS lock) r = 0 (0xff8003c851b8) locked @ cam/cam_periph.h:192 db:1:alllocks show lockedvnods Locked vnodes db:0:kdb.enter.default show pcpu cpuid= 8 dynamic pcpu = 0xff807f1e4800 curthread= 0xfe003421a000: pid 30 enc_daemon12 curpcb = 0xffbfd0f3dbc0 fpcurthread = none idlethread = 0xfe0021ffe490: tid 100011 idle: cpu8 curpmap = 0x81399590 tssp = 0x815a5640 commontssp = 0x815a5640 rsp0 = 0xffbfd0f3dbc0 gs32p= 0x815a3778 ldt = 0x815a37b8 tss = 0x815a37a8 spin locks held: db:0:kdb.enter.default bt Tracing pid 30 tid 100155 td 0xfe003421a000 memcpy() at memcpy+0x8/frame 0xffbfd0f3d0c0 ses_setphyspath_callback() at
Problem entering GELI password at boot
Hi, I recently up consists of a ZFS RAID-1 upon a GELI-encrypted container. Before the update I could enter the passphrases during boot (before root mount) via my USB keyboard and geli would created the nodes and root could be mounted. In 8.0 I had a related problem (some keystrokes would not be recognized) but this has been fixed since. Now the keyboard is functional (I can scroll up and down) but GELI doesn't recognize anything (not even 'return'). Any ideas or hints? Thanks! --- Alle Postfächer an einem Ort. Jetzt wechseln und E-Mail-Adresse mitnehmen! http://email.freenet.de/basic/Informationen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
RE: Problem entering GELI password at boot
sorry I accidentally messed up the last message: I recently up consists of a ZFS RAID-1 upon a GELI-encrypted container. Before the update I could enter the passphrases during boot (before root mount) via my USB keyboard and geli would created the nodes and root could be mounted. In 8.0 I had a related problem (some keystrokes would not be recognized) but this has been fixed since. Now the keyboard is functional (I can scroll up and down) but GELI doesn't recognize anything (not even 'return'). --- Alle Postfächer an einem Ort. Jetzt wechseln und E-Mail-Adresse mitnehmen! http://email.freenet.de/basic/Informationen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Trouble building release with docs
On Sun, 21 Jul 2013, Glen Barber wrote: On Sun, Jul 21, 2013 at 05:19:23PM +0930, Daniel O'Connor wrote: On 21/07/2013, at 16:19, Glen Barber g...@freebsd.org wrote: On Sat, Jul 20, 2013 at 04:44:56PM +0930, Daniel O'Connor wrote: Hi, I am trying to do a full (customised) release of 9.1 but I am having trouble building the docs. If I use NODOC it builds fine, but without that I get.. [...] May I ask why 9.1? Actually that's an excellent question :) I though 9.1 was coming out not 9.2 but that is not correct. So, if I rebuild with 9.2 checked out will the docs build? Yes. Depending on the use, just downloading the built documents from ftp://ftp.freebsd.org/pub/FreeBSD/doc/en_US.ISO8859-1/ could be more effective. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Problem entering GELI password at boot
I've seen similar behaviour recently intermittently on releng-9.1 on an laptop (HP) with USB keyboard, and like you said I had also seen it a number of years ago when 8.0 first came out with a desktop with USB keyboard (iirc, it was an HP as well). It seems fine most of the time but occasionally it won't respond to keyboard input, especially if I've accidentally left the computer for a few moments before attempting to enter the passphrase. Vaguely remember it was something to do with AHCI but it was years ago and given it's not a massive problem the now I haven't bothered to look it up again. On 21 July 2013 14:55, pe...@freenet.de wrote: Hi, I recently up consists of a ZFS RAID-1 upon a GELI-encrypted container. Before the update I could enter the passphrases during boot (before root mount) via my USB keyboard and geli would created the nodes and root could be mounted. In 8.0 I had a related problem (some keystrokes would not be recognized) but this has been fixed since. Now the keyboard is functional (I can scroll up and down) but GELI doesn't recognize anything (not even 'return'). Any ideas or hints? Thanks! --- Alle Postfächer an einem Ort. Jetzt wechseln und E-Mail-Adresse mitnehmen! http://email.freenet.de/basic/Informationen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Help with filing a [maybe] ZFS/mmap bug.
George Hartzell writes:
George Hartzell writes:
[...]
So, it would seem that there's something about the filesystem in which
my home directory resides that contributes to the problem.
[...]
Another data point.
[...]
Yet another data point or three.
I took an unused disk, set it up with a single pool and copied
everything from my two disk system to it using zfs send recv. I was
hoping that if there was something goofy about the state of the
filesystems on the older two disk pool it might get cleaned up in the
transfer.
I tagged the entire set of flac files, they were all successfully
validated via the plugin. After exiting Picard, one failed
validation. After rebooting, many failed validation.
Next I created a new filesystem on this new pool, mounted it,
configured Picard to save to that filesystem and ran through all of
the tracks. They validated fine via the plugin and by hand after
exiting Picard. They also validated properly after unmounting and
remounting the filesystem and after a reboot. Sigh.
Then I destroyed all of the snapshots on the filesystems that I
transfered over from my real dual-disk system. Tagging all of the
flac files into my home directory generated errors from the validation
plugin and by hand after exiting picard. I didn't bother rebooting
and checking.
So it seems to be something about the filesystem{s} themselves.
I'm running a scrub now.
g.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Problem entering GELI password at boot
This webmail crap keeps truncating my mails. I hope this time it'll work... I cannot say with certainty that the problem is related to the 8.0 thing but it sure feels like it. At least according to subversion the GELI code in -STABLE hasn't been changed for over 12 months now. Therefore I assume, GELI is not to blame. The thing with my system is that it only allows a USB keyboard, hence I cannot access anything currently which renders the problem rather severe for me. I, too, recall that the old (8.0) problem was related to interrupts storms due to faulty(?) AHCI code/hardware. Since then, I keep AHCI disabled on my system so this can't be the cause this time. --- Alle Postfächer an einem Ort. Jetzt wechseln und E-Mail-Adresse mitnehmen! http://email.freenet.de/basic/Informationen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Trouble building release with docs
On 21/07/2013, at 23:56, Warren Block wbl...@wonkity.com wrote: So, if I rebuild with 9.2 checked out will the docs build? Yes. Depending on the use, just downloading the built documents from ftp://ftp.freebsd.org/pub/FreeBSD/doc/en_US.ISO8859-1/ could be more effective. I can build /usr/doc OK, I am having trouble building /usr/src/release/doc. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au The nice thing about standards is that there are so many of them to choose from. -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Trouble building release with docs
On Mon, Jul 22, 2013 at 07:55:03AM +0930, Daniel O'Connor wrote: On 21/07/2013, at 23:56, Warren Block wbl...@wonkity.com wrote: So, if I rebuild with 9.2 checked out will the docs build? Yes. Depending on the use, just downloading the built documents from ftp://ftp.freebsd.org/pub/FreeBSD/doc/en_US.ISO8859-1/ could be more effective. I can build /usr/doc OK, I am having trouble building /usr/src/release/doc. doc/ build as of at least r253470 is fine for stable/9 branch. Are you saying you are still having a problem? Glen pgpqPlZu0kNnP.pgp Description: PGP signature
Re: Trouble building release with docs
On 22/07/2013, at 7:58, Glen Barber g...@freebsd.org wrote: On Mon, Jul 22, 2013 at 07:55:03AM +0930, Daniel O'Connor wrote: On 21/07/2013, at 23:56, Warren Block wbl...@wonkity.com wrote: So, if I rebuild with 9.2 checked out will the docs build? Yes. Depending on the use, just downloading the built documents from ftp://ftp.freebsd.org/pub/FreeBSD/doc/en_US.ISO8859-1/ could be more effective. I can build /usr/doc OK, I am having trouble building /usr/src/release/doc. doc/ build as of at least r253470 is fine for stable/9 branch. Are you saying you are still having a problem? No, it builds now (after I checked out r253470). Sorry for the confusion. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au The nice thing about standards is that there are so many of them to choose from. -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C signature.asc Description: Message signed with OpenPGP using GPGMail
