mergemaster merge left/right
I'd really like mergemaster to tell me whether the left or the right side is the new file. # $FreeBSD: src/etc/devd.conf,v 1.38. | # $FreeBSD: src/etc/devd.conf,v 1.38. Like this I have no idea which one to pick. ___ 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
trap 12
Is this likely to be hardware? Details will follow if not. [copied from a screen dump] Fatal trap 12: page fault while in kernel mode cpuid = 1; apic id = 01 fault virtual address = 0x0 fault code = supervisor write data, page not present instruction pointer = 0x8:0x807c6c12 stack pointer = 0x10:0x510e7890 frame pointer = 0x10:0xff00054a6c90 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 = 75372 (printf) trap number = 12 panic: page fault cpuid = 1 uptime: 8m2s Cannot dump. No dump device defined. -- ian j hart This message was sent using IMP, the Internet Messaging Program. ___ 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: mergemaster merge left/right
Speaking of mergemaster, it would be really really nice to have freebsd-update install get the following functionality/options from mergemaster: -i Automatically install any files that do not exist in the destination directory. -F If the files differ only by VCS Id ($FreeBSD) install the new file. This would help avoid having to manually approve installation of hundreds of files in /etc when you upgrade to new releases using freebsd-update. - Sincerely, Dan Naumov On Fri, Jul 3, 2009 at 11:51 AM, Dominic Fandreykamik...@bsdforen.de wrote: I'd really like mergemaster to tell me whether the left or the right side is the new file. # $FreeBSD: src/etc/devd.conf,v 1.38. | # $FreeBSD: src/etc/devd.conf,v 1.38. Like this I have no idea which one to pick. ___ 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: mergemaster merge left/right
On Fri, Jul 3, 2009 at 10:51 AM, Dominic Fandreykamik...@bsdforen.de wrote: I'd really like mergemaster to tell me whether the left or the right side is the new file. # $FreeBSD: src/etc/devd.conf,v 1.38. | # $FreeBSD: src/etc/devd.conf,v 1.38. From - To The new one is *always* the right one. -- Cris, member of G.U.F.I Italian FreeBSD User Group http://www.gufi.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
good old intel troubles
Now that the intel driver is stable and performs well, again, it's time to start complainig about all the things that still do not work. This is basically going to the console and back. Well, it actually works but X will entirely lock up unless the mouse is in motion. It's not hard to imagine that this is really bad. With violent mouse movement I can get glxgears to render 0.3 frames per second. That's it. 1 frame every 3 seconds. Back on the console everything is fine, so it's really just X misbehaving. No scheduling issue or the like. Oh, btw, when I switch to the Konsole I get the following message on my dmesg. error: [drm:pid1318:i915_get_vblank_counter] *ERROR* trying to get vblank count for disabled pipe 0 My system is a core2duo (amd64) running RELENG_7 (sources are from ~2 hours ago). Maybe this snippet from my Xorg.0.log is also of interest: (--) Using syscons driver with X support (version 2.0) (--) using VT number 9 (--) PCI:*(0...@0:2:0) Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller rev 12, Mem @ 0xe460/1048576, 0xd000/268435456, I/O @ 0x4000/8, BIOS @ 0x/65536 (--) PCI: (0...@0:2:1) Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller rev 12, Mem @ 0xe470/1048576 I'm running X without HAL. (**) Option AllowEmptyInput off (**) Option AutoAddDevices off ___ 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: mergemaster merge left/right
Cristiano Deana wrote: On Fri, Jul 3, 2009 at 10:51 AM, Dominic Fandreykamik...@bsdforen.de wrote: I'd really like mergemaster to tell me whether the left or the right side is the new file. # $FreeBSD: src/etc/devd.conf,v 1.38. | # $FreeBSD: src/etc/devd.conf,v 1.38. From - To The new one is *always* the right one. I don't have to merge files all that often. mergmaster is pretty easy to use, apart from the lack of that information. It wouldn't be very hard to print old file | new file at the beginning of a merge. ___ 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: good old intel troubles
Dominic Fandrey wrote: Now that the intel driver is stable and performs well, again, it's time to start complainig about all the things that still do not work. This is basically going to the console and back. Well, it actually works but X will entirely lock up unless the mouse is in motion. It's not hard to imagine that this is really bad. With violent mouse movement I can get glxgears to render 0.3 frames per second. That's it. 1 frame every 3 seconds. Back on the console everything is fine, so it's really just X misbehaving. No scheduling issue or the like. These issues have been recently addressed in 8-CURRENT. I assume some MFCs will happen at some point. Cheers, Lawrence ___ 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: mergemaster merge left/right
On Fri, 2009-07-03 at 10:51 +0200, Dominic Fandrey wrote: I'd really like mergemaster to tell me whether the left or the right side is the new file. # $FreeBSD: src/etc/devd.conf,v 1.38. | # $FreeBSD: src/etc/devd.conf,v 1.38. Like this I have no idea which one to pick. The right hand side is always the new file. robert. ___ 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 -- Robert Noland rnol...@freebsd.org FreeBSD signature.asc Description: This is a digitally signed message part
Re: trap 12
On Fri, 2009-07-03 at 10:06 +0100, Ian J Hart wrote: Is this likely to be hardware? Details will follow if not. [copied from a screen dump] Fatal trap 12: page fault while in kernel mode cpuid = 1; apic id = 01 fault virtual address = 0x0 fault code = supervisor write data, page not present instruction pointer = 0x8:0x807c6c12 stack pointer = 0x10:0x510e7890 frame pointer = 0x10:0xff00054a6c90 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 = 75372 (printf) trap number = 12 panic: page fault cpuid = 1 uptime: 8m2s Cannot dump. No dump device defined. I would doubt it. Are you using drm, with the radeon driver? There are a few corner cases where this can happen. http://people.freebsd.org/~rnoland/drm_radeon-copyin-fix-try2.patch should help if this is the case. robert. -- Robert Noland rnol...@freebsd.org FreeBSD signature.asc Description: This is a digitally signed message part
Re: good old intel troubles
On Fri, 2009-07-03 at 12:14 +0200, Dominic Fandrey wrote: Now that the intel driver is stable and performs well, again, it's time to start complainig about all the things that still do not work. This is basically going to the console and back. Well, it actually works but X will entirely lock up unless the mouse is in motion. It's not hard to imagine that this is really bad. With violent mouse movement I can get glxgears to render 0.3 frames per second. That's it. 1 frame every 3 seconds. Back on the console everything is fine, so it's really just X misbehaving. No scheduling issue or the like. Oh, btw, when I switch to the Konsole I get the following message on my dmesg. error: [drm:pid1318:i915_get_vblank_counter] *ERROR* trying to get vblank count for disabled pipe 0 This is still harmless, though I hope that I have caught most of the cases where it occurs. Userland (mesa) may still call this ioctl with the wrong or both crtc's though. It is converted back to a debug message in HEAD. My system is a core2duo (amd64) running RELENG_7 (sources are from ~2 hours ago). This is all fixed in HEAD. It is waiting jhb@ to MFC r194644 to get -STABLE fixed up. I have additional MFC's to cleanup vblank support issues, but the primary issue is that msi interrupts don't work after a vt switch without the above MFC. robert. Maybe this snippet from my Xorg.0.log is also of interest: (--) Using syscons driver with X support (version 2.0) (--) using VT number 9 (--) PCI:*(0...@0:2:0) Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller rev 12, Mem @ 0xe460/1048576, 0xd000/268435456, I/O @ 0x4000/8, BIOS @ 0x/65536 (--) PCI: (0...@0:2:1) Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller rev 12, Mem @ 0xe470/1048576 I'm running X without HAL. (**) Option AllowEmptyInput off (**) Option AutoAddDevices off ___ 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 -- Robert Noland rnol...@freebsd.org FreeBSD signature.asc Description: This is a digitally signed message part
From 7.1 to 7.2 ezjail jails mergemaster not working.
Hello all I have just updated my 7.1 machine to 7.2. I have updated the 7.1 machine several times with a builworld to follow the Security issues, and always use the same approuch. cd /us/src make cleanworld make buildworld make kernel mergemaster -p shutdown now cd /usr/src make installworld mergemaster -iU ezjail-admin update -i mergemaster -iU -D /usr/jails/jail1 mergemaster -iU -D /usr/jails/jail2 this has been working from 7.0 where this machine came from. After my update to 7.2 and after the ezjail-admin update -i i did the mergemaster step and here it goes wrong. this is what i get after the command mergemaster -iU -D /usr/jails/jail1 There is no installed version of ./boot/device.hints install: mkdir /usr.jails/jail1//boot : File exists install: /usr/jails/jail1//boot: no such file or directory *** FATAL ERROR : unable to install ./boot/device.hints to /usr/jails/jail1//boot. what am i doing wrong or what am i forgotten. Thanks for your time. regards, Johan Hendriks ___ 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
What is /boot/kernel/*.symbols?
Hi, all, When I upgraded some of our machines from 6.x to 7.2 I noticed that the root filesystems seemed to fill up. I thought this might come from makeoptions DEBUG=-g in the kernel config, but somehow that doesn't make sense, since our older systems have the same option present. 6.3-System: --- makeoptions DEBUG=-g $ du -sk /boot/kernel 27920 /boot/kernel No *.symbols files in /boot/kernel. 7.2-System: --- makeoptions DEBUG=-g $ du -sk /boot/kernel 214778 /boot/kernel Lots of those files filling /boot/kernel. On a current server with 512 MB /, the filesystem is at 97% after installing a new kernel twice. Can I get rid of these files somehow or are they necessary, in which case I will need way bigger root filesystems? I mean, get rid automatically and never install them again. I know the chflags and rm commands ;-) But then the question of they are needed is still open. Thanks, Patrick -- punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe Tel. 0721 9109 0 * Fax 0721 9109 100 i...@punkt.de http://www.punkt.de Gf: Jürgen Egeling AG Mannheim 108285 ___ 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: mergemaster merge left/right
Robert Noland wrote: On Fri, 2009-07-03 at 10:51 +0200, Dominic Fandrey wrote: I'd really like mergemaster to tell me whether the left or the right side is the new file. # $FreeBSD: src/etc/devd.conf,v 1.38. | # $FreeBSD: src/etc/devd.conf,v 1.38. Like this I have no idea which one to pick. The right hand side is always the new file. I know. Trial and error can tell you that. But I want mergemaster to tell me. ___ 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: kern/135412: [zfs] [nfs] zfs(v13)+nfs and open(..., O_WRONLY|O_CREAT|O_EXCL, ...)
On Thu, 2009-07-02 at 16:08 -0400, Mike Andrews wrote: On Wed, 1 Jul 2009, Danny Braniss wrote: On 2009-06-30, Mike Andrews wrote: Jaakko Heinonen wrote: On 2009-06-30, Danny Braniss wrote: This pr is realy holding me back, I can't upgrade this server, and telling serveral tens of users to us cp, etc is not an option. The open works fine if not using O_EXCL. I guess that r185586 needs to be MFCd to stable/7. Here's an untested patch against stable/7: The patch doesn't help over here, sorry. Simply doing 'touch' or 'mv' to an NFSv3 mount (using either a v6 or v13 zpool) is the test case I've been using; touch doesn't even use O_EXCL as far as I can tell. I could reproduce the problem with O_EXCL and verified that the patch fixes it. However I couldn't reproduce the problem you are seeing with touch and mv. same here, touch worked before too - so i think it's unrelated, btw, it seems that the problem does not exist on i386, though I'm pretty sure I tried there too, oh well, thanks! danny I'm not sure if what was commited to stable/7 yesterday is substantially different from that patch (and if not, what in the world I was doing wrong/stupid in testing), but everything now works for me... thanks :) Looks like it's working pretty well to me. It's almost not worth mentioning, but I have an old FreeBSD 4.8 server (which is the midst of being retired) that is still having an issue related to this. When I edit a file with vim 7.0, it creates the swapfile with no perms (which causes it to complain that the file already exists, and not clean up after itself) This only occurs from a 4.8 client, not 5.2.1, 6.2, or 7.2. Vim is the only program that replicates the problem on that box. touch works, mv works, procmail works. I only mention because maybe there's another OS, that's still supported, that might still have the same issues. Rick ___ 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: What is /boot/kernel/*.symbols?
On 2009-07-03 16:25, Patrick M. Hausen wrote: On a current server with 512 MB /, the filesystem is at 97% after installing a new kernel twice. Can I get rid of these files somehow or are they necessary, in which case I will need way bigger root filesystems? I mean, get rid automatically and never install them again. I know the chflags and rm commands ;-) But then the question of they are needed is still open. You can find this in /usr/src/UPDATING: 20060118: This actually occured some time ago, but installing the kernel now also installs a bunch of symbol files for the kernel modules. This increases the size of /boot/kernel to about 67Mbytes. You will need twice this if you will eventually back this up to kernel.old on your next install. If you have a shortage of room in your root partition, you should add -DINSTALL_NODEBUG to your make arguments or add INSTALL_NODEBUG=yes to your /etc/make.conf. However, you should consider increasing the size of your root partition, if possible. It can be extremely handy to have symbol files available whenever there's a crash. :) ___ 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: mergemaster merge left/right
Dominic Fandrey wrote: Robert Noland wrote: On Fri, 2009-07-03 at 10:51 +0200, Dominic Fandrey wrote: I'd really like mergemaster to tell me whether the left or the right side is the new file. # $FreeBSD: src/etc/devd.conf,v 1.38. | # $FreeBSD: src/etc/devd.conf,v 1.38. Like this I have no idea which one to pick. The right hand side is always the new file. I know. Trial and error can tell you that. But I want mergemaster to tell me. I'm sure Doug would be very happy to receive a patch to review. Mergemaster is a shell script so shouldn't be too difficult to hack something up. Cheers, Lawrence ___ 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: What is /boot/kernel/*.symbols?
Hello, On Fri, Jul 03, 2009 at 04:35:54PM +0200, Dimitry Andric wrote: You can find this in /usr/src/UPDATING: 20060118: This actually occured some time ago, but installing the kernel now also installs a bunch of symbol files for the kernel modules. This increases the size of /boot/kernel to about 67Mbytes. You will need twice this if you will eventually back this up to kernel.old on your next install. If you have a shortage of room in your root partition, you should add -DINSTALL_NODEBUG to your make arguments or add INSTALL_NODEBUG=yes to your /etc/make.conf. Thanks a lot. I've been searching the handbook and Google for at least one hour. However, you should consider increasing the size of your root partition, if possible. It can be extremely handy to have symbol files available whenever there's a crash. :) But I thought, they were in the kernel itself? %file /boot/kernel/kernel /boot/kernel/kernel: ELF 64-bit LSB executable, x86-64, version 1 (FreeBSD), dynamically linked (uses shared libs), not stripped not stripped - i.e. with debug symbols. Wrong? Since when? Thanks, Patrick -- punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe Tel. 0721 9109 0 * Fax 0721 9109 100 i...@punkt.de http://www.punkt.de Gf: Jürgen Egeling AG Mannheim 108285 ___ 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: What is /boot/kernel/*.symbols?
On 2009-07-03 16:41, Patrick M. Hausen wrote:
But I thought, they were in the kernel itself?
%file /boot/kernel/kernel
/boot/kernel/kernel: ELF 64-bit LSB executable, x86-64, version 1 (FreeBSD),
dynamically linked (uses shared libs), not stripped
not stripped - i.e. with debug symbols. Wrong? Since when?
Well, only the debug symbols have been stripped, not any others. If you
look in /usr/src/sys/conf/kern.post.mk, you will see this fragment:
${KERNEL_KO}: ${FULLKERNEL} ${KERNEL_KO}.symbols
${OBJCOPY} --strip-debug --add-gnu-debuglink=${KERNEL_KO}.symbols\
${FULLKERNEL} ${.TARGET}
${KERNEL_KO}.symbols: ${FULLKERNEL}
${OBJCOPY} --only-keep-debug ${FULLKERNEL} ${.TARGET}
E.g. the debug stuff is put into the .symbols files. The kernel itself
still contains the function and data names, though:
$ objdump -t /boot/kernel/kernel
/boot/kernel/kernel: file format elf32-i386-freebsd
SYMBOL TABLE:
c092de00 l .data tmpstk
c092de58 l .data physfree
c092de64 l .data proc0uarea
[...]
If you want to build absolutely without any symbols whatsover, remove
the makeoptions DEBUG=-g line from your kernel config file.
___
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: What is /boot/kernel/*.symbols?
Hi! On Fri, Jul 03, 2009 at 05:05:08PM +0200, Dimitry Andric wrote: E.g. the debug stuff is put into the .symbols files. The kernel itself still contains the function and data names, though: Understood. Thanks. No, I don't want the kernel to be void of any information ;-) Kind regards, Patrick -- punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe Tel. 0721 9109 0 * Fax 0721 9109 100 i...@punkt.de http://www.punkt.de Gf: Jürgen Egeling AG Mannheim 108285 ___ 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: FreeBSD child process die for root
Carlos A. M. dos Santos writes: Try to debug the login program: (become root) # cd /usr/src/usr.bin/login # make clean # make CFLAGS=-g # gdb /usr/obj/usr/src/usr.bin/login/login (supposing that sagara is your user name) #run sagara (fill-in the password name, if requested) If the signal 11 is caught, issue bt command in gcc. It will show you where the break happened. I tried to debug the login program, here are the results: 1. For normal users, gdb exists Program exited normally. 2. For root, gdb says Login incorrect. On /var/log/messages: login: pam_acct_mgmt(): authentication error login: 1 LOGIN FAILURE ON ttyp0 Btw, I have mentioned in my first post that I do not have an issue with normal user logins. Its only root has a problem. When try to su -l from a normal user, there is no pam_acct_mgmt(): authentication error on logs. Its only a (su), uid 0: exited on signal 11. Regards Sagara ___ 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: FreeBSD child process die for root
Roland Smith writes: Is there anything else from su in the logfiles? That might help narrow down where it crashes. No, other than the same “uid 0: exited on signal 11” for login, su and cron. What we see is after the fork, child process run for some time and crashes. Are you using the standard FreeBSD su? If not, check your modifications. Does the version of the userland that you are using match the version of the kernel? Our su is slightly modified. Tomorrow, I can try with standard su. Our userland is in some areas different. We normally try to use newer versions wherever possible. Our build method used to produce acceptable systems till FreeBSD 7.0. Its only on FreeBSD 7.2 now this issue. Other than that there is no other noticeable issue. I've verified that 'su -l' works fine on FreeBSD 7.2-RELEASE-p2 on the amd64 architecture. What you could do is run 'su -l' under a debugger. I just ran our normal su (without debugging info) under gdb: gdb /usr/bin/su GNU gdb 6.6 This GDB was configured as i386-unknown-freebsd7.2... (no debugging symbols found) (gdb) run -l Starting program: /usr/bin/su -l (no debugging symbols found) (no debugging symbols found) su: not running setuid Program exited with code 01. ls -l /usr/bin/su -r-sr-xr-x 1 root freebsd 14452 Jun 28 13:50 /usr/bin/su This shows su is setuid root. Anyway, I'll run su with debugging info tomorrow. regards Sagara ___ 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
