Re: What's wrong here? Can't reinstall graphics/lcms2
There was an entry in vuxml for lcms2 2.5 earlier this week that initially included 2.5 accidentally. It's been corrected now, so an update of your ports vulnerability database should allow you to install/update lcms2. Ryan On 08/20/2013 01:15 PM, Kurt Buff wrote: On Tue, Aug 20, 2013 at 10:23 AM, Walter Hurry walterhu...@gmail.com wrote: $ sudo portupgrade -f graphics/lcms2 snip = Please update your ports tree and try again. *** [check-vulnerable] Error code 1 I have of course updated the ports tree but it made no difference. Try updating ports again. I was successful in updating lcms2 this morning on a couple of boxes, after failures yesterday. Kurt ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Curl -7.24.0_4 heap corruption
Update your ports vulnerability database before attempting to compile curl. `portaudit -Fda` should do the trick. Ryan On 07/02/2013 08:49 AM, Reggie Euser wrote: We're running FreeBSD 8.3-RELEASE-p3 and portaudit says: Affected package: curl-7.24.0_2 Type of problem: cURL library -- heap corruption in curl_easy_unescape. Reference: http://portaudit.FreeBSD.org/01cf67b3-dc3b-11e2-a6cd-c48508086173.html 1 problem(s) in your installed packages found. You are advised to update or deinstall the affected package(s) immediately. Have updated ports tree, checked UPDATING (nothing on curl since 2010). For last several days, portmaster curl has attempted to install curl-7.24.0_3 - same heap corruption issue. Today, portmaster curl attempted to install curl-7.24.0_4. I thought, great, the port has been updated! Except that the heap corruption issue persists and the update fails. Anyone have any insights into this issue? Thanks! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: update from apache22 to apache24
The Apache site has documentation on upgrading from 2.2 to 2.4 -- http://httpd.apache.org/docs/2.4/upgrading.html The main change for me was the new allow/deny syntax. I've updated almost all of my Apache installs from 2.2 to 2.4 with no issues. The only installs I haven't updated yet are those using mod_evasive, since it's currently broken with 2.4 Ryan On 05/03/2013 09:47 AM, Jerry wrote: I was just wondering if anyone had updated from apache22 to apache24. Specifically, are there any problems to be overcome? Does the existing httpd.conf file work with the apache24 branch. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
freesbd-update Continuously Wants to Update linker.hints
I have a number of boxes running 9.1-RELEASE (amd64) that I updated to p3 yesterday via freebsd-update. However freebsd-update still indicates that linker.hints needs to be updated. Running `freebsd-update install` appears to install a new linker.hints file but still doesn't appear to satisfy freebsd-update. Incidentally I have another amd64 system that I did a clean install on last week, and it isn't exhibiting the same issue. Has/is anyone run(ning) into this issue? Ryan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Procmail Decoding Mime Messages
Forgot to cc the list. On 04/24/2013 04:47 PM, Ryan Frederick wrote: I believe mimencode is in ports as converters/mmencode. It is also included as part of mail/metamail. Ryan On 04/24/2013 04:07 PM, Martin McCormick wrote: Is there a filter that one can run in procmail in which base64 encoded data go in and text comes out so one can allow procmailrc to do its work? I use bogofilter to filter spam and it does a very good job after one builds a core of spammishness, but legitimate messages are often-times filled with base64 sections that look like garbage to the regular expressions that one puts in .procmailrc for sorting mail. When searching for information, I found something called mimencode which both encodes and decodes these attachments, but there is no FreeBSD port called mimencode so it occurred to me that some other application might exist which is in the ports that does basically the same thing. Is there anything which will take a raw email message and spit out linear strings which can be processed like normal text? Thank you. Martin McCormick ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Virtual FreeBSD9.0 ISO Image Won't Mount Root FS
What option argument did you specify for the -V (volume ID) option when you created the ISO with the `mkisofs` command? I believe that the root filesystem lies under /dev/iso9660/volumeID for which the ISO loader's default configuration specifies as /dev/iso9660/FREEBSD_INSTALL. Thus you'll need to change the vfs.root.mountfrom loader variable to be cd9660:/dev/iso9660/volumeID Ryan On 09/05/2012 09:26 AM, Martin McCormick wrote: The ISO image is the FreeBSD9.0 bootonly CDROM for amd64 systems. I added loader.conf to /boot in order to activate a serial console and this along with socat appears to be working as it should. This is great because remote desktop is not an option. The VM boot starts normally with the spinning bars and normal startup messages until: cd0: cd present [85585 x 2048 byte records] Timecounter TSC frequency 3368628976 Hz quality 800 Trying to mount root from cd9660:/dev/iso9660/FREEBSD_INSTALL [ro]... mountroot: waiting for device /dev/iso9660/FREEBSD_INSTALL ... Mounting from cd9660:/dev/iso9660/FREEBSD_INSTALL failed with error 19. Loader variables: vfs.root.mountfrom=cd9660:/dev/iso9660/FREEBSD_INSTALL vfs.root.mountfrom.options=ro Manual root filesystem specification: fstype:device [options] Mountdevice using filesystemfstype and with the specified (optional) option list. eg. ufs:/dev/da0s1a zfs:tank cd9660:/dev/acd0 ro (which is equivalent to: mount -t cd9660 -o ro /dev/acd0 /) ? List valid disk boot devices . Yield 1 second (for background tasks) empty line Abort manual input mountroot I enter a Question Mark. mountroot ? List of GEOM managed disk devices: iso9660/CDROM cd0 ada0 mountroot The host system is a fairly new 64-bit Macintosh which is using VirtualBox. Here is the script to define the new machine. VBoxManage createvm --name vsys --ostype FreeBSD_64 --register VBoxManage modifyvm vsys --memory 1000 --vram 128 --acpi on \ --boot2 dvd --boot1 disk --nic1 nat #setup ttyu0 so the VM can communicate. VBoxManage modifyvm vsys --uart1 0x3F8 4 VBoxManage -q modifyvm vsys --uartmode1 server '/tmp/vmx' VBoxManage createhd --filename FreeBSD.VMDK --size 1 VBoxManage storagectl x --name SATA Controller --add sata --controller \ IntelAHCI --hostiocache on VBoxManage storageattach x --storagectl SATA Controller \ --port 0 --device 0 --type hdd --medium FreeBSD.VMDK VBoxManage storagectl vsys --name IDE Controller \ --add ide --controller PIIX4 VBoxManage storageattach vsys --storagectl IDE Controller \ --port 0 --device 0 --type dvddrive --medium /users/sysbuild/headless.iso ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Building a Headless FreeBSD Virtual System
When you define the virtual serial port in VirtualBox for the guest VM one of the options available for connection of the port to the host system is a named pipe (I believe it's called Host Pipe in the configuration). You can then specify whatever named pipe on the host system you wish to attach the VM's serial port to then use a utility such as `socat` to present the I/O from the named pipe as a PTY device. From there it's simply a matter of using a utility such as `cu` or `screen` to connect to the PTY. Ryan On 08/29/2012 10:16 AM, Martin McCormick wrote: I am using Oracle's VirtualBox package for the Mac. It is free and I am not sure that Dollars would get past the issue I have, here. VirtualBox uses Microsoft's remote desktop as the one and only output channel to allow remote access to the virtual system one is creating and this is really bad design for computer users who are blind and use screen readers. Pictures of text just don't work. If you had some very complex system with OCR, it might sort of work, but such systems don't exist as a drop-in for a good old ASCII terminal so that's not an option. So far, I downloaded the bootonly ISO image of FreeBSD9.0, mounted it and added the following loader.conf: boot_multicons=YES boot_serial=YES comconsole_speed=115200 console=comconsole,vidconsole vesa_load=YES Next, I used VirtualBoxmanage to define the disk and create the machine with a virtual IDE controller that is pointed to the ISO image for FreeBSD9.0 with the serial console. Has anybody been able to use VirtualBox and a fake serial console to get around the remote desktop non solution? I will probably have to add a virtual serial port in the machine definition one puts in the original machine build, but I am not sure this doesn't just go to that remote desktop channel where it gets scrubbed of any usefulness except for eyeballs on screens. This whole thing looks very promising but there's got to be a way around that shoe which doesn't fit in the form of that GUI remote desk top. In my case, the machine build goes without error but I can't tell yet if it is even booting. Mac's, by the way, have a relatively good screen reader built in but VirtualBox doesn't work with it, something that is a problem with a number of third-party programs especially when they were originally developed for Windows. This, of course, does not pertain to the main topic of this list, but I say it here so that you know I am aware you are supposed to be able to use the GUI on the Mac to manage your new virtual system. Essentially, the local GUI and the remote desktop don't work for me for the same reasons. My hope is to get FreeBSD running as a guest system on a powerful Mac and retire an old Dell server with noisy fans and several BTU of heat output which is in the realm of 15 years old and will probably retire itself at some random date in the future. Thank you for any good suggestions. Martin McCormick WB5AGZ Stillwater, OK Systems Engineer OSU Information Technology Department Telecommunications Services Group ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
freebsd-update Not Recognizing Updated Custom Kernel for 9.0-RELEASE-p3
I have several FreeBSD 9 systems with custom compiled kernels. After using freebsd-update to go from 9.0-RELEASE-p2 to 9.0-RELEASE-p3 this morning I rebuilt the kernels. However after recompiling, installing, and rebooting with the custom kernels subsequent update checks using freebsd-update cron or freebsd-update fetch indicate that /boot/kernel/kernel (and only /boot/kernel/kernel) needs to be updated despite the custom kernel indicating 9.0-RELEASE-p3 in the output of uname -a. Ryan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: freebsd-update Not Recognizing Updated Custom Kernel for 9.0-RELEASE-p3
I realized I made a couple of wording/clarification errors in my original message. First just about all of these kernels are not custom but simply locally compiled with no custom modifications. Second the locally compiled kernels are all named GENERIC (no custom name). Ryan On 6/12/12 2:29 PM, Ryan Frederick wrote: I have several FreeBSD 9 systems with custom compiled kernels. After using freebsd-update to go from 9.0-RELEASE-p2 to 9.0-RELEASE-p3 this morning I rebuilt the kernels. However after recompiling, installing, and rebooting with the custom kernels subsequent update checks using freebsd-update cron or freebsd-update fetch indicate that /boot/kernel/kernel (and only /boot/kernel/kernel) needs to be updated despite the custom kernel indicating 9.0-RELEASE-p3 in the output of uname -a. Ryan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: /lib/exec/ld-elf.so.1: Shared object libpcre.so.0 not found, required by libxfsm-4.6.so.0 amd64 FreeBSD 8.2
It looks like others have run into this problem with avahi-app as well:
http://lists.freebsd.org/pipermail/freebsd-ports/2011-July/068658.html
A cursory search shows that uninstalling avahi-app then reinstalling
should take care of the compilation failure. Afterward you should be
able to run portmaster as shown in the error message (minus
'net/avahi-app') to finish recompiling the ports that depend on pcre.
Ryan
On 02/15/2012 10:55 PM, Antonio Olivares wrote:
On Wed, Feb 15, 2012 at 9:33 PM, Robert Bonomibon...@mail.r-bonomi.com wrote:
Antonio Olivaresolivares14...@gmail.com wrote;
I am doing this and see how it goes. I used ldd to check for
libprce.so and I got :
ldd /usr/local/lib/libprce.so:
libc.so.7 = /lib/libc.so.7 (0x800647000)
ldd /usr/local/lib/libprce.so.1:
libc.so.7 = /lib/libc.so.7 (0x800647000)
There are two of them :( Should there be only one?
This is _normal_. The .so (with no further sufix), is generally just a link
to the 'latest' .so *with* a numeric suffix.
I am in a not good state now. I broke two machines by updating to
latest and get the same error on both machines.
I get the /libexec/ld-elf.so.1: Shared object libpcre.so.0 is needed
by * and nothing works, I run
# portmaster -r pcre-8.30
and it bombs out with the following:
signals-marshal.c:186: warning: ISO C forbids conversion of object
pointer to function pointer type
CC libavahi_gobject_la-ga-client-enumtypes.lo
CC libavahi_gobject_la-ga-entry-group-enumtypes.lo
CC libavahi_gobject_la-ga-enums-enumtypes.lo
CCLD libavahi-gobject.la
GISCAN Avahi-0.6.gir
g-ir-scanner: warning: Option --strip-prefix has been deprecated;
see --identifier-prefix and --symbol-prefix.
/usr/include/machine/endian.h:123: syntax error, unexpected '{' in '
return (__extension__ ({ register __uint64_t __X = (_x); __asm (bswap
%0 : +r (__X)); __X; }));' at '{'
/usr/include/machine/endian.h:123: syntax error, unexpected ';' in '
return (__extension__ ({ register __uint64_t __X = (_x); __asm (bswap
%0 : +r (__X)); __X; }));' at ';'
/usr/include/machine/endian.h:130: syntax error, unexpected '{' in '
return (__extension__ ({ register __uint32_t __X = (_x); __asm (bswap
%0 : +r (__X)); __X; }));' at '{'
/usr/include/machine/endian.h:130: syntax error, unexpected ';' in '
return (__extension__ ({ register __uint32_t __X = (_x); __asm (bswap
%0 : +r (__X)); __X; }));' at ';'
/libexec/ld-elf.so.1: Shared object libpcre.so.0 not found, required
by libavahi-glib.so.1
Command
'['/usr/ports/net/avahi-app/work/avahi-0.6.29/avahi-gobject/tmp-introspectGYNEXM/Avahi-0.6',
'--introspect-dump=/usr/ports/net/avahi-app/work/avahi-0.6.29/avahi-gobject/tmp-introspectGYNEXM/types.txt,/usr/ports/net/avahi-app/work/avahi-0.6.29/avahi-gobject/tmp-introspectGYNEXM/dump.xml']'
returned non-zero exit status 1
gmake[3]: *** [Avahi-0.6.gir] Error 1
gmake[3]: Leaving directory
`/usr/ports/net/avahi-app/work/avahi-0.6.29/avahi-gobject'
gmake[2]: *** [all] Error 2
gmake[2]: Leaving directory
`/usr/ports/net/avahi-app/work/avahi-0.6.29/avahi-gobject'
gmake[1]: *** [all-recursive] Error 1
gmake[1]: Leaving directory `/usr/ports/net/avahi-app/work/avahi-0.6.29'
gmake: *** [all] Error 2
*** Error code 1
Stop in /usr/ports/net/avahi-app.
=== make failed for net/avahi-app
=== Aborting update
=== Update for avahi-app-0.6.29_1 failed
=== Aborting update
=== Update for gvfs-1.6.6_2 failed
=== Aborting update
=== Update for Thunar-1.3.0 failed
=== Aborting update
Terminated
=== There are messages from installed ports to display,
but first take a moment to review the error messages
above. Then press Enter when ready to proceed.
=== pkg-message for gamin-0.1.10_4
===
Gamin will only provide realtime notification of changes for at most n files,
where n is the minimum value between (kern.maxfiles * 0.7) and
(kern.maxfilesperproc - 200). Beyond that limit, files will be polled.
If you often open several large folders with Nautilus, you might want to
increase the kern.maxfiles tunable (you do not need to set
kern.maxfilesperproc, since it is computed at boot time from kern.maxfiles).
For a typical desktop, add the following line to /boot/loader.conf, then
reboot the system:
kern.maxfiles=25000
The behavior of gamin can be controlled via the various gaminrc files.
See http://www.gnome.org/~veillard/gamin/config.html on how to create
these files. In particular, if you find gam_server is taking up too much
CPU time polling for changes, something like the following may help
in one of the gaminrc files:
# reduce polling frequency to once per 10 seconds
# for UFS file systems in order to lower CPU load
fsset ufs poll 10
===
=== pkg-message for liblqr-1-0.4.1_2
==
Re: /lib/exec/ld-elf.so.1: Shared object libpcre.so.0 not found, required by libxfsm-4.6.so.0 amd64 FreeBSD 8.2
You can recompile all ports that depend on pcre so that they'll use the new shared library. You can do so with: # portmaster -r pcre-8.30 Ryan On 02/15/2012 08:42 PM, Antonio Olivares wrote: Dear folks, I updated ports and one failed, gimp-app. I checked /usr/src/UPDATING and I followed advice there to run # portmaster -w devel/pcre and I did this, and now machine won't get X. How can I bypass this mistake? I am now hesitant to update the other machines :(, I will get into problems starting X because of some update of a certain lib. Any thoughts, ideas or suggestions? Regards, Antonio ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Kernel Panic on 9.0-RELEASE When Attempting to Remove Files
I'm attempting to remove a number of old files within a directory that was rsynced over from another box. However a number of files (old symlinks and regular files in this instance) cause a kernel panic when attempting to remove them using rm or unlink. This is the panic message output: Fatal trap 12: page fault while in kernel mode cpuid = 1; apic id = 01 fault virtual address = 0x160 fault code = supervisor read data, page not present instruction pointer = 0x20:0x81476306 stack pointer = 0x28:0xff811aacf880 frame pointer = 0x28:0xff811aacf940 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 = 4729 (rm) trap number = 12 panic: page fault cpuid = 1 KDB: stack backtrace: #0 0x808680fe at kdb_backtrace+0x5e #1 0x80832cb7 at panic+0x187 #2 0x80b18400 at trap_fatal+0x290 #3 0x80b18749 at trap_pfault+0x1f9 #4 0x80b18c0f at trap+0x3df #5 0x80b0313f at calltrap+0x8 #6 0x80b7d694 at VOP_REMOVE_APV+0x34 #7 0x808cb4fd at kern_unlinkat+0x32d #8 0x80b17cf0 at amd64_syscall+0x450 #9 0x80b03427 at Xfast_syscall+0xf7 And this is the backtrace from kgdb: #0 doadump (textdump=Variable textdump is not available. ) at pcpu.h:224 #1 0x808327f5 in kern_reboot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:442 #2 0x80832ca1 in panic (fmt=Variable fmt is not available. ) at /usr/src/sys/kern/kern_shutdown.c:607 #3 0x80b18400 in trap_fatal (frame=0xc, eva=Variable eva is not available. ) at /usr/src/sys/amd64/amd64/trap.c:819 #4 0x80b18749 in trap_pfault (frame=0xff811aacf7d0, usermode=0) at /usr/src/sys/amd64/amd64/trap.c:735 #5 0x80b18c0f in trap (frame=0xff811aacf7d0) at /usr/src/sys/amd64/amd64/trap.c:474 #6 0x80b0313f in calltrap () at /usr/src/sys/amd64/amd64/exception.S:228 #7 0x81476306 in zfs_freebsd_remove (ap=Variable ap is not available. ) at /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_vnops.c:1842 #8 0x80b7d694 in VOP_REMOVE_APV (vop=Variable vop is not available. ) at vnode_if.c:1333 #9 0x808cb4fd in kern_unlinkat (td=0xfe00046cb8c0, fd=-100, path=0x7fffdd73 Address 0x7fffdd73 out of bounds, pathseg=UIO_USERSPACE, oldinum=0) at vnode_if.h:575 #10 0x80b17cf0 in amd64_syscall (td=0xfe00046cb8c0, traced=0) at subr_syscall.c:131 #11 0x80b03427 in Xfast_syscall () at /usr/src/sys/amd64/amd64/exception.S:387 #12 0x0008009315fc in ?? () This particular system is a VM running on a VMWare ESXi hypervisor. So far I haven't had any luck in finding a cause. Ryan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Kernel Panic on 9.0-RELEASE When Attempting to Remove Files
In response to the related thread started by Martin McCormick we did run a `zpool scrub` on the zpool, and the scrub completed successfully with no repairs performed. I successfully tried importing the zpool in Linux using the native Linux ZFS module. However attempting to remove the files via Linux results in `rm` either being killed or hanging. Ryan On 02/10/2012 10:43 AM, Ryan Frederick wrote: I'm attempting to remove a number of old files within a directory that was rsynced over from another box. However a number of files (old symlinks and regular files in this instance) cause a kernel panic when attempting to remove them using rm or unlink. This is the panic message output: Fatal trap 12: page fault while in kernel mode cpuid = 1; apic id = 01 fault virtual address = 0x160 fault code = supervisor read data, page not present instruction pointer = 0x20:0x81476306 stack pointer = 0x28:0xff811aacf880 frame pointer = 0x28:0xff811aacf940 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 = 4729 (rm) trap number = 12 panic: page fault cpuid = 1 KDB: stack backtrace: #0 0x808680fe at kdb_backtrace+0x5e #1 0x80832cb7 at panic+0x187 #2 0x80b18400 at trap_fatal+0x290 #3 0x80b18749 at trap_pfault+0x1f9 #4 0x80b18c0f at trap+0x3df #5 0x80b0313f at calltrap+0x8 #6 0x80b7d694 at VOP_REMOVE_APV+0x34 #7 0x808cb4fd at kern_unlinkat+0x32d #8 0x80b17cf0 at amd64_syscall+0x450 #9 0x80b03427 at Xfast_syscall+0xf7 And this is the backtrace from kgdb: #0 doadump (textdump=Variable textdump is not available. ) at pcpu.h:224 #1 0x808327f5 in kern_reboot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:442 #2 0x80832ca1 in panic (fmt=Variable fmt is not available. ) at /usr/src/sys/kern/kern_shutdown.c:607 #3 0x80b18400 in trap_fatal (frame=0xc, eva=Variable eva is not available. ) at /usr/src/sys/amd64/amd64/trap.c:819 #4 0x80b18749 in trap_pfault (frame=0xff811aacf7d0, usermode=0) at /usr/src/sys/amd64/amd64/trap.c:735 #5 0x80b18c0f in trap (frame=0xff811aacf7d0) at /usr/src/sys/amd64/amd64/trap.c:474 #6 0x80b0313f in calltrap () at /usr/src/sys/amd64/amd64/exception.S:228 #7 0x81476306 in zfs_freebsd_remove (ap=Variable ap is not available. ) at /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_vnops.c:1842 #8 0x80b7d694 in VOP_REMOVE_APV (vop=Variable vop is not available. ) at vnode_if.c:1333 #9 0x808cb4fd in kern_unlinkat (td=0xfe00046cb8c0, fd=-100, path=0x7fffdd73 Address 0x7fffdd73 out of bounds, pathseg=UIO_USERSPACE, oldinum=0) at vnode_if.h:575 #10 0x80b17cf0 in amd64_syscall (td=0xfe00046cb8c0, traced=0) at subr_syscall.c:131 #11 0x80b03427 in Xfast_syscall () at /usr/src/sys/amd64/amd64/exception.S:387 #12 0x0008009315fc in ?? () This particular system is a VM running on a VMWare ESXi hypervisor. So far I haven't had any luck in finding a cause. Ryan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
