Re: Difficulty playing DVDs under AHCI/CAM?
< said: > Not sure if debugging with CAMDEBUG would be easier or not. > There could be lots of output. I never found out, as once I rebooted with the new CAMDEBUG-ified kernel, everything started working. No idea why. (Maybe the DVD player just wanted to be rebooted with a disc in it?) -GAWollman ___ 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: ZFS v28 is ready for wider testing.
I got this compile error agains todays current patched with patch -p0 -E < /usr/src9/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_ioctl.c: In function 'zfs_ioc_recv': /usr/src9/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_ioctl.c:3586: error: too few arguments to function 'getf' cc1: warnings being treated as errors /usr/src9/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_ioctl.c:3761: warning: passing argument 1 of 'releasef' makes pointer from integer without a cast /usr/src9/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_ioctl.c: In function 'zfs_ioc_send': /usr/src9/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_ioctl.c:3831: error: too few arguments to function 'getf' /usr/src9/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_ioctl.c:3844: warning: passing argument 1 of 'releasef' makes pointer from integer without a cast /usr/src9/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_ioctl.c: In function 'zfs_ioc_diff': /usr/src9/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_ioctl.c:4356: error: too few arguments to function 'getf' /usr/src9/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_ioctl.c:4369: warning: passing argument 1 of 'releasef' makes pointer from integer without a cast /usr/src9/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_ioctl.c: In function 'zfsdev_ioctl': /usr/src9/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_ioctl.c:4930: error: 'FKIOCTL' undeclared (first use in this function) *** Error code 1 /usr/src9/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_onexit.c: In function 'zfs_onexit_fd_hold': /usr/src9/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_onexit.c:127: error: too few arguments to function 'getf' cc1: warnings being treated as errors /usr/src9/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_onexit.c: In function 'zfs_onexit_fd_rele': /usr/src9/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_onexit.c:145: warning: passing argument 1 of 'releasef' makes pointer from integer without a cast *** Error code 1 2 errors *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error ___ 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: problem with amd64 minidump
on 02/09/2010 16:08 Andriy Gapon said the following: > on 02/09/2010 13:10 Andriy Gapon said the following: >> >> Not sure if this is some local issue or a problem in FreeBSD code. >> I remember minidumps working perfectly well for me, but now I can not get >> data >> from them. >> Example: >> dmesg -M /var/crash/vmcore.4 >> dmesg: _kvm_vatop: direct map address 0xff012fe0 not in minidump >> dmesg: kvm_read: invalid address (0xff012fe0) > > Not sure if it can help, but it seems that this virtual address in DMAP > corresponds to a physical address in the last page of RAM. > Do we use that for anything special? Message buffer? > I had a quick look at getmemsize() function in sys/amd64/amd64/machdep.c and > it > looks like the following code in the function could be doing just that: > > Maxmem = atop(phys_avail[pa_indx]); > > /* Trim off space for the message buffer. */ > phys_avail[pa_indx] -= round_page(MSGBUF_SIZE); > > /* Map the message buffer. */ > msgbufp = (struct msgbuf *)PHYS_TO_DMAP(phys_avail[pa_indx]); > > Oh, and yeah: > (gdb) p msgbufp > $4 = (struct msgbuf *) 0xff012fe0 > > But we do dump the message buffer. > But somehow its dmap address is not resolved correctly. > > This should ring a bell for someone knowledgeable of minidump and libkvm > code, I > believe. Just for the record: this was triggered by having non-default MSGBUF_SIZE, see r212174 for the fix. -- Andriy Gapon ___ 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"
[head tinderbox] failure on i386/i386
TB --- 2010-09-04 17:15:00 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2010-09-04 17:15:00 - starting HEAD tinderbox run for i386/i386 TB --- 2010-09-04 17:15:00 - cleaning the object tree TB --- 2010-09-04 17:15:59 - cvsupping the source tree TB --- 2010-09-04 17:15:59 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/i386/i386/supfile TB --- 2010-09-04 17:16:52 - building world TB --- 2010-09-04 17:16:52 - MAKEOBJDIRPREFIX=/obj TB --- 2010-09-04 17:16:52 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2010-09-04 17:16:52 - TARGET=i386 TB --- 2010-09-04 17:16:52 - TARGET_ARCH=i386 TB --- 2010-09-04 17:16:52 - TZ=UTC TB --- 2010-09-04 17:16:52 - __MAKE_CONF=/dev/null TB --- 2010-09-04 17:16:52 - cd /src TB --- 2010-09-04 17:16:52 - /usr/bin/make -B buildworld >>> World build started on Sat Sep 4 17:16:52 UTC 2010 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Sat Sep 4 19:07:04 UTC 2010 TB --- 2010-09-04 19:07:04 - generating LINT kernel config TB --- 2010-09-04 19:07:04 - cd /src/sys/i386/conf TB --- 2010-09-04 19:07:04 - /usr/bin/make -B LINT TB --- 2010-09-04 19:07:04 - building LINT kernel TB --- 2010-09-04 19:07:04 - MAKEOBJDIRPREFIX=/obj TB --- 2010-09-04 19:07:04 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2010-09-04 19:07:04 - TARGET=i386 TB --- 2010-09-04 19:07:04 - TARGET_ARCH=i386 TB --- 2010-09-04 19:07:04 - TZ=UTC TB --- 2010-09-04 19:07:04 - __MAKE_CONF=/dev/null TB --- 2010-09-04 19:07:04 - cd /src TB --- 2010-09-04 19:07:04 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Sat Sep 4 19:07:04 UTC 2010 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -fstack-protector -Werror -pg -mprofiler-epilogue /src/sys/dev/twa/tw_cl_io.c -I/src/sys/dev/twa cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -fstack-protector -Werror -pg -mprofiler-epilogue /src/sys/dev/twa/tw_cl_misc.c -I/src/sys/dev/twa cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -fstack-protector -Werror -pg -mprofiler-epilogue /src/sys/dev/twa/tw_osl_cam.c -I/src/sys/dev/twa cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -fstack-protector -Werror -pg -mprofiler-epilogue /src/sys
Using ipfw table names instead of numbers.
Hello developers, I use the ipfw firewall with many tables and, I would like of able to use it with name/alias instead of just numbers. E.g: lab# ipfw table 1 name lanetwork Setting table 1 to lanetwork lab# ipfw table lanetwork add 192.168.0.0/24 lab# ipfw table lanetwork list 192.168.0.0/24 0 lab# I think a good idea a patch to do that. Any comments? -- Anderson Eduardo Diretor Geral Tel.: +55 (71) 3641-6450 Secover - Serviços em Tecnologia e Segurança da Informação http://www.secover.com.br ___ 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: ZFS v28 is ready for wider testing.
On 09/03/2010 13:02, Pawel Jakub Dawidek wrote: > On Fri, Sep 03, 2010 at 04:50:44PM +0100, Peter Molnar, BSD wrote: >> Hi, >> I would like to try ZFS + VirtualBox but I have got problems: >> >> >> 1) Linux 2.6.32-24-generic #42-Ubuntu SMP Fri Aug 20 14:21:58 UTC 2010 >> x86_64 GNU/Linux >> >> I tried import that file in my VirtualBox but I have got error: >> Failed to import appliance. >> /home/peter/FreeBSD/zfsv28.ovf >> Too many IDE controllers in OVF; import facility only supports one. > > Which VirtualBox version do you use? 3.2.8? > > Exporting appliances is a bit broken (if you have more than one disk, it > will point all disks at the last one from configuration), so I had to > edit .ovf file manually to fix this. Maybe I messed something up, but I > was able to successfully import it before publishing it. > > PS. I waited for so long for decent virtualization software for FreeBSD, > and I must say VirtualBox is really great, and free, and open-source > Are you reading this, VMWare? > They will only read it if it comes with a disclaimer and they're license attached to the top along with a contract signed by you so when they disagree with it they can hand you a pink-slip with they're license attached to the top. As for VirtualBox, which is a Sun thing, gone Oratorically wrong... How long does anyone expect this technology to stick around?. -- jhell,v ___ 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: Trouble with a atapi-cam backup..
* Randy Stewart, 2010-09-02 : > And now my backup to atapi-cam is failing.. I get: > > r...@lakerest /usr/tmp]# /usr/local/bin/growisofs -Z /dev/cd0 -R -J > backup_init.08-31-2010.gz > :-( unable to CAMGETPASSTHRU for /dev/cd0: Inappropriate ioctl for > device Would be interesting to see the output of truss or ktrace for this command. Can you open a PR and send that info? Does "camcontrol inq cd0" work? Thomas. ___ 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: trying /sbin/init => panic: bad pte
On Fri, Sep 03, 2010 at 11:34:10PM -0700, David O'Brien (@FreeBSD) wrote: > This happens on AMD64 for me, r212166 (2010-09-02 15:37:13 -0700) kernel > sources. Sorry for the false alarm - this was a local environment problem. -- David ___ 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"
