Re: powerd broken
On Sat, May 9, 2009 at 2:06 PM, Robert Noland wrote: > Which update, what? I haven't touched the kernel tree in a while, just > trying to sort it all out with patches here and there. Are you saying > the the 2.7.0 intel driver helped? Or maybe the Xserver or mesa > updates? updating intel driver, xserver and drm helped a lot! i've finally deinstalled intel 2.5.*, and started using (happily) exa instead of xaa in xorg -- Alberto Villa ___ 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"
7.2-STABLE: Inserting USB device causes Fatal Trap 12
Inserting a USB thumb drive into a running sytem result in a "Fatal trap 12: page fault while in kernel mode". Unfortunately, I was not able to save a core (not entirely sure why, I'll investigate separately). I have manually copied the backtrace: usb_transfer_complete bus_dmamap_load usbd_transfer usbd_do_request_flags_pipe usbd_do_request_flags usbd_get_string_desc usbd_get_string usbd_devinfo_vp usbd_devinfo usbd_new_device uhub_explore usb_event_thread fork_exit for_trampine The problem is repeatable. It only happens when I insert the thumb drive into a running system. If I boot with the thumb drive present, everything is fine. Any help is greatly appreciated. Cheers, -- Norbert Papke. = # uname -a FreeBSD proven.lan 7.2-STABLE FreeBSD 7.2-STABLE #0 r191841: Tue May 5 21:13:21 PDT 2009 npa...@proven.lan:/usr/obj/red/public/freebsd/sources/stable/sys/PROVEN amd64 = Kernel config: include GENERIC ident PROVEN options KDB # kernel debugger (just in case) options KDB_TRACE options DDB # kernel debugger (just in case) options WITNESS options WITNESS_SKIPSPIN options IPSEC device crypto device stf # for IPv6 tunneling # keep kernel messages from different cpus separate options PRINTF_BUFR_SIZE=64 option SC_HISTORY_SIZE=2000 options SC_NORM_ATTR=(FG_GREEN|BG_BLACK) options SC_NORM_REV_ATTR=(FG_YELLOW|BG_GREEN) options SC_KERNEL_CONS_ATTR=(FG_LIGHTRED|BG_BLACK) options SC_KERNEL_CONS_REV_ATTR=(FG_BLACK|BG_RED) # Alternate Queuing of network packets options ALTQ options ALTQ_CBQ# Class Bases Queuing (CBQ) options ALTQ_RED# Random Early Detection (RED) options ALTQ_RIO# RED In/Out options ALTQ_HFSC # Hierarchical Packet Scheduler (HFSC) options ALTQ_PRIQ # Priority Queuing (PRIQ) options ALTQ_NOPCC # Required for SMP build # load as module for debugging nodevicere # RealTek 8139C+/8169/8169S/8110S = Copyright (c) 1992-2009 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 7.2-STABLE #0 r191841: Tue May 5 21:13:21 PDT 2009 npa...@proven.lan:/usr/obj/red/public/freebsd/sources/stable/sys/PROVEN WARNING: WITNESS option enabled, expect reduced performance. Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Core(TM)2 Duo CPU E8500 @ 3.16GHz (3155.59-MHz K8-class CPU) Origin = "GenuineIntel" Id = 0x1067a Stepping = 10 Features=0xbfebfbff Features2=0x408e3fd,XSAVE> AMD Features=0x20100800 AMD Features2=0x1 Cores per package: 2 usable memory = 4279189504 (4080 MB) avail memory = 4097724416 (3907 MB) ACPI APIC Table: <100808 APIC1053> FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 cryptosoft0: on motherboard acpi0: <100808 XSDT1053> on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: reservation of ffc0, 30 (3) failed acpi0: reservation of fee0, 1000 (3) failed acpi0: reservation of 0, a (3) failed acpi0: reservation of 10, bff0 (3) failed Timecounter "ACPI-safe" frequency 3579545 Hz quality 850 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 acpi_hpet0: iomem 0xfed0-0xfed003ff on acpi0 Timecounter "HPET" frequency 14318180 Hz quality 900 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: irq 16 at device 1.0 on pci0 pci1: on pcib1 vgapci0: port 0xc000-0xc0ff mem 0xd000-0xdfff,0xfe9f-0xfe9f irq 16 at device 0.0 on pci1 drm0: on vgapci0 info: [drm] MSI enabled 1 message(s) vgapci0: child drm0 requested pci_enable_busmaster info: [drm] Initialized radeon 1.29.0 20080528 hdac0: mem 0xfe9ec000-0xfe9e irq 17 at device 0.1 on pci1 hdac0: HDA Driver Revision: 20090329_0131 hdac0: [ITHREAD] uhci0: port 0xbc00-0xbc1f irq 16 at device 26.0 on pci0 uhci0: [GIANT-LOCKED] uhci0: [ITHREAD] usb0: on uhci0 usb0: USB revision 1.0 uhub0: on usb0 uhub0: 2 ports with 2 removable, self powered uhci1: port 0xb880-0xb89f irq 21 at device 26.1 on pci0 uhci1: [GIANT-LOCKED] uhci1: [ITHREAD] usb1: on uhci1 usb1: USB revision 1.0 uhub1: on usb1 uhub1: 2 ports with 2 removable, self powered uhci2: port 0xb800-0xb81f irq 19 at device 26.2 on pci0 uhci2: [GIANT-LOCKED] uhci2: [ITHREAD] usb2: on uhci2 usb2: USB revision 1.0 uhub2: on usb2 uhub2: 2 ports with 2 removable, self powered ehci0: mem 0xfe8fe000-0xfe8fe3ff irq 18 at device 26.7 on pci0 ehci0: [GIANT-LOCKED] ehci0: [ITHREAD] usb3: EHCI version 1.0 usb3: companion controllers, 2 ports each: usb0 usb1 usb2 usb3: on ehci0 usb3: USB r
Re: 7.2-STABLE: Inserting USB device causes Fatal Trap 12
On May 10, 2009, Norbert Papke wrote: > Inserting a USB thumb drive into a running sytem result in a "Fatal trap > 12: page fault while in kernel mode". > > Unfortunately, I was not able to save a core (not entirely sure why, I'll > investigate separately). I have manually copied the backtrace: I now have a kernel dump and backtrace with symbols: #0 doadump () at pcpu.h:195 #1 0x801d239c in db_fncall (dummy1=Variable "dummy1" is not available. ) at /red/public/freebsd/sources/stable/sys/ddb/db_command.c:516 #2 0x801d28a9 in db_command (last_cmdp=0x80adc648, cmd_table=0x0, dopager=1) at /red/public/freebsd/sources/stable/sys/ddb/db_command.c:413 #3 0x801d2aab in db_command_loop () at /red/public/freebsd/sources/stable/sys/ddb/db_command.c:466 #4 0x801d42f7 in db_trap (type=Variable "type" is not available. ) at /red/public/freebsd/sources/stable/sys/ddb/db_main.c:228 #5 0x805159e5 in kdb_trap (type=12, code=0, tf=0xfffef5b69d10) at /red/public/freebsd/sources/stable/sys/kern/subr_kdb.c:524 #6 0x80798143 in trap_fatal (frame=0xfffef5b69d10, eva=Variable "eva" is not available. ) at /red/public/freebsd/sources/stable/sys/amd64/amd64/trap.c:752 #7 0x80798498 in trap_pfault (frame=0xfffef5b69d10, usermode=0) at /red/public/freebsd/sources/stable/sys/amd64/amd64/trap.c:673 #8 0x80798bcf in trap (frame=0xfffef5b69d10) at /red/public/freebsd/sources/stable/sys/amd64/amd64/trap.c:444 #9 0x8077edae in calltrap () at /red/public/freebsd/sources/stable/sys/amd64/amd64/exception.S:209 #10 0x80473265 in usb_transfer_complete (xfer=0xff00045cbc00) at /red/public/freebsd/sources/stable/sys/dev/usb/usbdi.c:949 #11 0x8077af55 in bus_dmamap_load (dmat=0xff0004598580, map=0xff000cbf5e00, buf=0xfffef5b69ff0, buflen=Variable "buflen" is not available. ) at /red/public/freebsd/sources/stable/sys/amd64/amd64/busdma_machdep.c:739 #12 0x80473955 in usbd_transfer (xfer=0xff00045cbc00) at /red/public/freebsd/sources/stable/sys/dev/usb/usbdi.c:312 #13 0x80473b36 in usbd_do_request_flags_pipe (dev=0xff009c1e4a00, pipe=0xff000c857680, req=0xfffef5b69f90, data=0xfffef5b69ff0, flags=Variable "flags" is not available. ) at /red/public/freebsd/sources/stable/sys/dev/usb/usbdi.c:1100 #14 0x80473c60 in usbd_do_request_flags (dev=Variable "dev" is not available. ) at /red/public/freebsd/sources/stable/sys/dev/usb/usbdi.c:1070 #15 0x80471d1a in usbd_get_string_desc (dev=0xff009c1e4a00, sindex=Variable "sindex" is not available. ) at /red/public/freebsd/sources/stable/sys/dev/usb/usb_subr.c:171 #16 0x80472f1d in usbd_get_string (dev=0xff009c1e4a00, si=1, buf=0xfffef5b6a200 "", len=128) ---Type to continue, or q to quit--- at /red/public/freebsd/sources/stable/sys/dev/usb/usbdi.c:1353 #17 0x80470fca in usbd_devinfo_vp (dev=0xff009c1e4a00, v=0xfffef5b6a200 "", p=0xfffef5b6a180 "�z�\200`��\200", usedev=Variable "usedev" is not available. ) at /red/public/freebsd/sources/stable/sys/dev/usb/usb_subr.c:216 #18 0x80471b76 in usbd_devinfo (dev=0xff009c1e4a00, showclass=1, cp=0xff0122986000 "\001") at /red/public/freebsd/sources/stable/sys/dev/usb/usb_subr.c:281 #19 0x8047243e in usbd_new_device (parent=0xff0004591900, bus=0xff000440a000, depth=Variable "depth" is not available. ) at /red/public/freebsd/sources/stable/sys/dev/usb/usb_subr.c:861 #20 0x80467b5b in uhub_explore (dev=0xff0004591400) at /red/public/freebsd/sources/stable/sys/dev/usb/uhub.c:523 #21 0x8046f391 in usb_discover (v=Variable "v" is not available. ) at /red/public/freebsd/sources/stable/sys/dev/usb/usb.c:724 #22 0x8046fc61 in usb_event_thread (arg=Variable "arg" is not available. ) at /red/public/freebsd/sources/stable/sys/dev/usb/usb.c:440 #23 0x804d05bd in fork_exit (callout=0x8046fbe5 , arg=0xff0004598d00, frame=0xfffef5b6ac80) at /red/public/freebsd/sources/stable/sys/kern/kern_fork.c:810 #24 0x8077f16e in fork_trampoline () at /red/public/freebsd/sources/stable/sys/amd64/amd64/exception.S:455 > The problem is repeatable. It only happens when I insert the thumb drive > into a running system. If I boot with the thumb drive present, everything > is fine. > > Any help is greatly appreciated. > > Cheers, > > -- Norbert Papke. > > = > > # uname -a > FreeBSD proven.lan 7.2-STABLE FreeBSD 7.2-STABLE #0 r191841: Tue May 5 > 21:13:21 PDT 2009 > npa...@proven.lan:/usr/obj/red/public/freebsd/sources/stable/sys/PROVEN > amd64 > > = > > Kernel config: > > include GENERIC > ident PROVEN > > options KDB # kernel debugger (just in case) > options KDB_TRACE >
Debugging server hangs in 7.2-RELEASE
I am so completely running out of ideas on how to debug this, maybe someone else has some ideas? The problem appears to be that very suddenly, the disk busy (according to vmstat) skyrockets to >100 (from 0) and then the 'runnable but swapped' column slowly rises ... One person suggested that for them, they saw similar when msi/msi-x was enabled ... after searching the source code, I found that msi was used in the bge driver, but I couldn't find msix used anywhere else on that machine, so disabled msi ... its still exhibiting the issue ... I get no errors on the serial console to indicate any problems, and until a relatively recent upgrade of the kernel ( (I can't give an exact date), this server was one of my most solid ... I figure there is a single process that is starting up on the machine that is causing this, but no matter what I try, it is eluding me. I have KDB enabled in the kernel, and the serial console setup so that I can break to it ... but when this problem happens, doing 'cr ~ ^b' through the serial console doesn't do anything, or, it just prints the message about breaking to the debugger and then hangs there ... My next option is to start time travelling backwards to see if I can find a 'stable kernel' again, but if it is just one process causing this, then going back to older kernels isn't necessarily going to accomplish anything ... Is there something else I can do here to debug this? Its hard to believe we are such an advance OS, but debugging issues like this is so elusive :( Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . scra...@hub.org MSN . scra...@hub.org Yahoo . yscrappy Skype: hub.orgICQ . 7615664 ___ 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
Doug Hardie wrote: > I have been following the discussion on mergemaster and one item is a > bit annoying. You can use -U in the command args which sets > "AUTO_UPGRADE=yes". So far so good. > That flag is not in mergemaster.rc. I'm not sure what that is supposed to mean. There is no rc file by default, you have to create it. If what you mean is that it wasn't mentioned in the man page, that has been fixed for a while now. > It could be > easily added to the rc file, but I suspect it would conflict with -p. It would not conflict with it, in fact if everything is working as it should it should be totally safe. > Hence it seems like if "unset AUTO_UPGRADE" were added to the -p section > then it would work. I try hard not to outthink what the user is trying to do, which of course works both ways. > It would be helpful to be able to include it in the > rc file so I don't have to remember the options each time. [ -z "$PRE_WORLD" ] && AUTO_UPGRADE=yes hth, Doug ___ 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: RELENG_7 - has mergemaster changed logic since 7.2-RELEASE?
Torfinn Ingolfsen wrote: > To be clear, I follow this procedure: > 1. make buildworld > 2. make kernel > 3. shutdown now > 4. mergemaster -p > 5. make installworld > 6. mergemaster -iU > 7. fastboot By any chance is any of this happening in a jail? Or by any chance is /etc a symlink? A user sent me a very interesting patch related to the use of -U in a jail that might be relevant here. Doug ___ 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"
failure building nanobsd with FreeBSD Stable
Hello all, I've been building nanobsd to run on my Soekris net4801 for some time now. I recently csupped to FreeBSD Stable and I can no longer build it. It gives an error early in "installworld" (see below). Does anybody please have any clues? Thanks, Graham mkdir -p /tmp/install.1JDmZzZe for prog in [ awk cap_mkdb cat chflags chmod chown date echo egrep find grep ln lockf make mkdir mtree mv pwd_mkdb rm sed sh sysctl test true uname wc zic; do cp `which $prog` /tmp/install.1JDmZzZe; done cd /usr/src; MAKEOBJDIRPREFIX=/usr/obj/nanobsd.maxwell/ MACHINE_ARCH=i386 MACH INE=i386 CPUTYPE= GROFF_BIN_PATH=/usr/obj/nanobsd.maxwell//usr/src/tmp/legacy/ usr/bin GROFF_FONT_PATH=/usr/obj/nanobsd.maxwell//usr/src/tmp/legacy/usr/share/ groff_font GROFF_TMAC_PATH=/usr/obj/nanobsd.maxwell//usr/src/tmp/legacy/usr/sha re/tmac PATH=/usr/obj/nanobsd.maxwell//usr/src/tmp/legacy/usr/sbin:/usr/obj/nan obsd.maxwell//usr/src/tmp/legacy/usr/bin:/usr/obj/nanobsd.maxwell//usr/src/tmp/l egacy/usr/games:/usr/obj/nanobsd.maxwell//usr/src/tmp/usr/sbin:/usr/obj/nanobsd. maxwell//usr/src/tmp/usr/bin:/usr/obj/nanobsd.maxwell//usr/src/tmp/usr/games:/tm p/install.1JDmZzZe make -f Makefile.inc1 reinstall -- >>> Making hierarchy -- cd /usr/src; make -f Makefile.inc1 hierarchy cd /usr/src/etc;make distrib-dirs mtree -eU -f /usr/src/etc/mtree/BSD.root.dist -p /usr/obj/nanobsd.maxwell//_.w/ ./bin missing (created) ./boot missing (created) ./boot/defaults missing (created) ./boot/firmware missing (created) ...skipping... rm -f /usr/obj/nanobsd.maxwell//_.w/usr/include/security/mac_partition; fi if [ -L /usr/obj/nanobsd.maxwell//_.w/usr/include/ufs/ffs ]; then rm -f /usr/ob j/nanobsd.maxwell//_.w/usr/include/ufs/ffs; fi if [ -L /usr/obj/nanobsd.maxwell//_.w/usr/include/ufs/ufs ]; then rm -f /usr/ob j/nanobsd.maxwell//_.w/usr/include/ufs/ufs; fi if [ -L /usr/obj/nanobsd.maxwell//_.w/usr/include/machine ]; then rm -f /usr/ob j/nanobsd.maxwell//_.w/usr/include/machine; fi if [ -L /usr/obj/nanobsd.maxwell//_.w/usr/include/crypto ]; then rm -f /usr/obj /nanobsd.maxwell//_.w/usr/include/crypto; fi mtree -deU -f /usr/src/include/../etc/mtree/BSD.include.dist -p /usr/obj/nano bsd.maxwell//_.w/usr/include creating osreldate.h from newvers.sh touch: not found *** Error code 127 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error ___ 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"
