Re: panic in propagate_priority w/ postgresql under heavy load
On Sun, 2 Oct 2005, Koen Martens wrote: kernel trap 12 with interrupts disabled Fatal trap 12: page fault while in kernel mode cpuid = 1; apic id = 06 fault virtual address = 0x24 fault code = supervisor read, page not present instruction pointer = 0x8:0xc051c253 stack pointer = 0x10:0xe93efb3c frame pointer = 0x10:0xe93efb50 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= resume, IOPL = 0 current process = 6092 (postgres) And that, that is all.. No ddb> no 'dumping MB', just that. So basically, i fear this is a non-debugable problem, since putting in witness and such slows the kernel to a point where the panic does not occur anymore (at least, not in the 4 weeks i've been running the box with witness & invariants). Clueless :) This looks like a NULL pointer dereference in kernel code. Probably, this is not a locking problem, so running without WITNESS to debug this should be OK. Are you using a serial console? If not, you might find that it increases the reliability of entering DDB. If this box is an SMP box, you may also want to add options KDB_STOP_NMI to your kernel config. Using gdb, could you work out what function 0xc051c253 is, and where in the function. You should be able to run gdb on your kernel.debug (or kernel on 7.x), and use "l *0xc051c253" to generate a pointer to the line and snippet, which will give us a substantial hint about what is happening. Robert N M Watson Best, Koen [ full kernel config: # # GENERIC -- Generic kernel configuration file for FreeBSD/i386 # # For more information on this file, please read the handbook section on # Kernel Configuration Files: # # http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-config.html # # The handbook is also available locally in /usr/share/doc/handbook # if you've installed the doc distribution, otherwise always see the # FreeBSD World Wide Web server (http://www.FreeBSD.org/) for the # latest information. # # An exhaustive list of options and more detailed explanations of the # device lines is also present in the ../../conf/NOTES and NOTES files. # If you are in doubt as to the purpose or necessity of a line, check first # in NOTES. # # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.413.2.13 2005/04/02 16:37:58 scottl Exp $ machine i386 cpu I486_CPU cpu I586_CPU cpu I686_CPU ident YIN-YANG # debug #options WITNESS #options INVARIANTS #optionsINVARIANT_SUPPORT options KDB options DDB # options KDB_TRACE # makeoptions DEBUG=-g # debug # To statically compile in device wiring instead of /boot/device.hints #hints "GENERIC.hints" # Default places to look for devices. options SCHED_4BSD # 4BSD scheduler options INET# InterNETworking options INET6 # IPv6 communications protocols options FFS # Berkeley Fast Filesystem options SOFTUPDATES # Enable FFS soft updates support options UFS_ACL # Support for access control lists options UFS_DIRHASH # Improve performance on big directories options MD_ROOT # MD is a potential root device options NFSCLIENT # Network Filesystem Client options NFSSERVER # Network Filesystem Server options NFS_ROOT# NFS usable as /, requires NFSCLIENT options MSDOSFS # MSDOS Filesystem options CD9660 # ISO 9660 Filesystem options PROCFS # Process filesystem (requires PSEUDOFS) options PSEUDOFS# Pseudo-filesystem framework options GEOM_GPT# GUID Partition Tables. options COMPAT_43 # Compatible with BSD 4.3 [KEEP THIS!] options COMPAT_FREEBSD4 # Compatible with FreeBSD4 options SCSI_DELAY=15000# Delay (in ms) before probing SCSI options KTRACE # ktrace(1) support options SYSVSHM # SYSV-style shared memory options SYSVMSG # SYSV-style message queues options SYSVSEM # SYSV-style semaphores options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time extensions options KBD_INSTALL_CDEV# install a CDEV entry in /dev options AHC_REG_PRETTY_PRINT# Print register bitfields in debug # output. Adds ~128k to driver. options AHD_REG_PRETTY_PRINT# Print register bitfields in debug # output. Adds ~215k to driver. options ADAPTIVE_GIANT
Too many segments in the physical address map, giving up
Hello, I've got an AMD64 compatible machine which dies with "Too many segments in the physical address map, giving up". This error is defined in src/sys/amd64/amd64/machdep.c Changing the following define: #define PHYSMAP_SIZE(2 * 8) to #define PHYSMAP_SIZE(2 * 16) has solved the problem, the machine boots and works without any noticeable side effect. Are there any reasons to keep this and not to increase PHYSMAP_SIZE? Thanks, -- Attila Nagy e-mail: [EMAIL PROTECTED] Adopt a directory on our free software phone: +3630 306 6758 server! http://www.fsn.hu/?f=brick ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
flock() returns EHOSTUNREACH on 5.3 with 4.5 NFS server
I'm applying flock() to a file that is on an NFS server. The program calling flock() is built on a 4.5 system, with the 4.5 libraries, etc... The NFS server is a 4.5-RELEASE system. The program running on a 4.5-release system doesn't display any problems. But - when I run that same program on a 5.3-RELEASE system, flock() returns with a -1 and sets errno to EHOSTUNREACH. Of course, the code is checking for EEOPNOTSUPP, but it doesn't expect to see EHOSTUNREACH from flock(). We changed it to set errno to zero to make sure that simply wasn't a dangling value in errno. Any ideas about what could be going on? Should flock() be setting errno to EHOSTUNREACH? And, as the file can be read, I don't understand where the EHOSTUNREACH comes from (the host is very reachable.) - Thanks! - - Dave Rivers - -- [EMAIL PROTECTED]Work: (919) 676-0847 Get your mainframe programming tools at http://www.dignus.com ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
diskless broken in 6.x ?
Hi, I am trying to boot a diskless box (via PXE), both server and diskless run FreeBSD 6.0-BETA4. The diskless machine hangs after printing the date on the console. I added debug output to /etc/rc, /etc/initdiskless and finally /sbin/init. It seems to hang in init after calling multi_user(). A bit before the hang, rc.initdiskless does sysctl -n kern.bootp_cookie and it prints: sysctl: unknown oid 'kern.bootp_cookie' Is this a known issue? I can upgrade to -current if needed. PS in the process of setting up the diskless root I also updated clone_root to work with fbsd > 4.x, retaining 4.x compatibility, seems to work fine. thanks marco -- He who receives an idea from me, receives instruction himself without lessening mine; as he who lights his taper at mine, receives light without darkening me. -- Thomas Jefferson ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: diskless broken in 6.x ?
On Wed, Oct 05, 2005 at 09:07:58PM +0200, Marco Molteni wrote: > Hi, > > I am trying to boot a diskless box (via PXE), both server and diskless > run FreeBSD 6.0-BETA4. The diskless machine hangs after printing > the date on the console. I added debug output to /etc/rc, > /etc/initdiskless and finally /sbin/init. It seems to hang in init > after calling multi_user(). > > A bit before the hang, rc.initdiskless does > sysctl -n kern.bootp_cookie and it prints: > sysctl: unknown oid 'kern.bootp_cookie' > > Is this a known issue? I can upgrade to -current if needed. > > PS in the process of setting up the diskless root I also updated > clone_root to work with fbsd > 4.x, retaining 4.x compatibility, > seems to work fine. It works for me basicly the same way it has since 4.x. I don't use the clone_root procedure and use installworld/kernel with DESTDIR set. -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 pgpsqkSFE05bd.pgp Description: PGP signature
ggtrace
I'd like to announce a new utility for FreeBSD, named "ggtrace". It's a graphical (X11) utility that displays I/O on a ggate device in a window. It can attach to any device or file, producing a /dev/ggateN device which can be used as usual - for example for hosting filesystems. All I/O requests are logged and displayed as a histogram of activity. The sources are here: http://ivoras.sharanet.org/stuff/ggtrace.tgz You'll need X11, libpng and wxgtk26-contrib ports installed before building it. Read the README file before using the application! This is still software under development and I'd like to hear any feedback you might have on it :) -- Ivan Voras ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
IPFW+DUMMYNET UPLOAD PROBLEM
I have the following rules: $fwcmd add 600 pipe 602 src-ip 192.168.0.0/24 out $fwcmd add 601 pipe 603 dst-ip 192.168.0.0/24 in $fwcmd pipe 602 config mask src-ip 0x00ff bw 128Kbit/s queue 10KBytes $fwcmd pipe 603 config mask dst-ip 0x00ff bw 128Kbit/s queue 10KBytes And my test speed from ip 192.168.0.5 is: Down 123.66kbps Up 766.24kbps Which the problem? -- Daniel Dias Gonçalves DGNET Network Solutions [EMAIL PROTECTED] (37) 99824809 ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: diskless broken in 6.x ?
On Wed, 5 Oct 2005 13:14:14 -0700 Brooks Davis <[EMAIL PROTECTED]> wrote: > On Wed, Oct 05, 2005 at 09:07:58PM +0200, Marco Molteni wrote: > > Hi, > > > > I am trying to boot a diskless box (via PXE), both server and > > diskless run FreeBSD 6.0-BETA4. The diskless machine hangs after > > printing the date on the console. I added debug output to /etc/rc, > > /etc/initdiskless and finally /sbin/init. It seems to hang in init > > after calling multi_user(). > > > > A bit before the hang, rc.initdiskless does > > sysctl -n kern.bootp_cookie and it prints: > > sysctl: unknown oid 'kern.bootp_cookie' > > > > Is this a known issue? I can upgrade to -current if needed. > > > > PS in the process of setting up the diskless root I also updated > > clone_root to work with fbsd > 4.x, retaining 4.x compatibility, > > seems to work fine. > > It works for me basicly the same way it has since 4.x. I don't use > the clone_root procedure and use installworld/kernel with DESTDIR set. mmmh, I'll try installworld then. thanks marco -- He who receives an idea from me, receives instruction himself without lessening mine; as he who lights his taper at mine, receives light without darkening me. -- Thomas Jefferson ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
