boot crash with ddb & break_to_debugger
i386 cvsupped as of yesterday
ÚÄ¿
³ ³
³ ³ ,,
³ ³ /()`
³ Welcome to FreeBSD!³ \ \___ / |
³ ³ /- _ `-/ '
³ ³ (/\/ \ \ /\
³ 1. Boot FreeBSD [default] ³ / / | `\
³ 2. Boot FreeBSD with ACPI disabled ³ O O ) /|
³ 3. Boot FreeBSD in Safe Mode ³ `-^--'`< '
³ 4. Boot FreeBSD in single user mode³(_.) _ ) /
³ 5. Boot FreeBSD with verbose logging ³ `.___/`/
³ 6. Escape to loader prompt ³ `-' /
³ 7. Reboot ³ <. __ / __ \
³ ³ <|O)))==) \) /|
³ ³ <'`--' `.__,' \
³ ³ ||
³ ³\ / /\
³ Select option, [Enter] for default ³ __( (_ / \__/
³ or [Space] to pause timer -1 ³ ,' ,-' |
ÀÄÙ `--{__)
KDB: debugger backends: ddb
KDB: current backend: ddb
131072K of memory above 4GB ignored
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 #28: Wed Jul 15 08:11:56 GMT 2009
r...@psg.com:/usr/obj/usr/src/sys/PSG
kmem_suballoc: bad status return of 3.
panic: kmem_suballoc
cpuid = 0
KDB: enter: panic
[thread pid 0 tid 0 ]
Stopped at kdb_enter_why+0x3a: movl$0,kdb_why
db> trace
Tracing pid 0 tid 0 td 0xc07fad60
kdb_enter_why(c078b1b8,c078b1b8,c079e7a8,c0c20d04,0,...) at kdb_enter_why+0x3a
panic(c079e7a8,3,0,0,c07fb8a0,...) at panic+0x138
kmem_suballoc(c1071000,c07fb8a0,c07fb8a4,4000,1,...) at kmem_suballoc+0x91
kmeminit(0,c1ec00,c1ec00,c1e000,c25000,...) at kmeminit+0x18a
mi_startup() at mi_startup+0xa6
begin() at begin+0x2c
db>
___
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: ATA driver update for 7.2RELEASE available
Søren Schmidt wrote: Over the past months I've gotten huge amounts of requests for ATA related things, so I've whipped up what I use here for FreeBSD 7.2-Release. This is a total replacement of the ATA driver, modulerized as in -current, but based on my WIP not from what might have happend to -current since I gave up maintainership. There is a number of new chipsets supported in here that I dont think is in any of the official sources (havn't checked in quite some time though), mostly newish ATI, nVidia and Marvell chips (yeah those buggers with both ATA & SATA ports). You can find and install.sh script and a tarball of the needed files at: http://www.deepcore.dk/pub/ATA Put both in /usr/src and run install.sh. As I dont subscribe to any of the mailing lists nor does my FreeBSD.org mail address seem to work anymore, you will need to reply to me directly if needed. As always - Enjoy! -Søren i think i'm dumb, but can you tell me how can atapicam be enabled with this implementation of ata? i couldn't still find a way :( -- SY, Marat smime.p7s Description: S/MIME Cryptographic Signature
mergemaster ezjails. different behaviour between 7.1 and 7.2 and up
Hello all . I have an issue using mergemaster and ezjail after the update to FreeBSD 7.2 from 7.1 I have several boxes running ezjails from FreeBSD 7.0 to 7.1 and i always use the same way to update these machines. First a buildworld cycle. then reboot and make sure jails are not running. then ezjail-admin update -i After that i do a mergemaster of the jails. #mergemaster -iU -D /usr/jails/jail1 on a 7.2 and above system i get the following error. cd /usr/src/etc/..; install -o root -g wheel -m 444 COPYRIGHT /var/tmp/temproot/ install -o root -g wheel -m 444 /usr/src/etc/../sys/amd64/conf/GENERIC.hints /var/tmp/temproot/boot/device.hints *** Beginning comparison *** Checking /usr/jails/test//etc/rc.d for stale files *** No stale files found *** There is no installed version of ./boot/device.hints install: mkdir /usr/jails/test//boot: File exists install: /usr/jails/test//boot: No such file or directory *** FATAL ERROR: Unable to install ./boot/device.hints to /usr/jails/test//boot jailhost_co test # And it drops me to the commandline again. On the old 7.0 and 7.1 it works well. It does not drop to commandline but carries on like the example below. cd /usr/src/etc/..; install -o root -g wheel -m 444 COPYRIGHT /var/tmp/temproot/ install -o root -g wheel -m 444 /usr/src/etc/../sys/i386/conf/GENERIC.hints /var/tmp/temproot/boot/device.hints *** Beginning comparison *** Checking /usr/jails/ftp/etc/rc.d for stale files *** No stale files found *** There is no installed version of ./boot/device.hints install: mkdir /usr/jails/ftp/boot: File exists install: /usr/jails/ftp/boot: No such file or directory *** Problem installing ./boot/device.hints, it will remain to merge by hand *** Temp ./etc/bluetooth/hcsecd.conf and installed have the same CVS Id, deleting Here it comes with the *** Problem installing ./boot/device.hints, it will remain to merge by hand line On 7.2 and up (also 8.0BETA1) ir gives me this *** FATAL ERROR: Unable to install ./boot/device.hints to /usr/jails/test//boot Do i need another option i need to give mergemaster? I hope things are clear, i am not that good in explaining things in another language. Regards, Johan ___ 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: problem with Soekris net5501 and USB hub
Marat N.Afanasyev wrote: > Graham Menhennitt wrote: >> I originally sent this to the Soekris list thinking it was platform >> specific. I got a couple of replies suggesting that it's a FreeBSD >> problem instead. So, if anybody can offer any insights, I would most >> appreciate it. >> >> I have a Soekris net5501 running FreeBSD 7-Stable. I want to connect >> a number of USB devices to it: >> - a HP Laserjet 1020 printer >> - an APC Back UPS 350 UPS >> - a 6-in-one card reader (not so fussed about this one). >> The Soekris box has only one USB port brought out to a connector on >> the case, so rather than mod the box to add another port, I thought I >> would just use an external hub. >> >> If I plug any of the devcies directly into the Soekris's USB port it >> works fine. However, if I use a USB hub then it doesn't work at all. > see http://www.freebsd.org/cgi/query-pr.cgi?pr=131074 i think your > case is very similar to mine Thanks Marat (and the others that replied). It is the same problem as in that PR - if the devices are connected at boot time everything works. If I power them on later it doesn't. For now that will be my workaround. I'll look at upgrading to 8 some time soon. Thanks again, Graham ___ 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: trap 12
Quoting John Baldwin : On Tuesday 14 July 2009 9:51:01 am Ian J Hart wrote: Quoting John Baldwin : > On Tuesday 07 July 2009 5:51:03 am Ian J Hart wrote: >> Quoting Ian J Hart : >> >>> Quoting Ian J Hart : >>> 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. >>> Ran crashinfo, now have much more info than I need ;) >>> >>> Starting another portupgrade run now to see how reproducable this is. >>> >>> Later BIOS waiting in USB floppy. >>> >> [snip dmesg] >> >> It took 2 runs of portupgrade -af.Some corruption in the dbs may have >> to pkg_delete -a. >> >> FreeBSD * 7.2-RELEASE-p1 FreeBSD 7.2-RELEASE-p1 #0: Tue Jun 16 >> 18:03:10 BST 2009 *...@*:/usr/obj/usr/src/sys/GENERIC amd64 >> >> panic: page fault >> >> GNU gdb 6.1.1 [FreeBSD] >> Copyright 2004 Free Software Foundation, Inc. >> GDB is free software, covered by the GNU General Public License, and you are >> welcome to change it and/or distribute copies of it under certain > conditions. >> Type "show copying" to see the conditions. >> There is absolutely no warranty for GDB. Type "show warranty" for details. >> This GDB was configured as "amd64-marcel-freebsd"... >> >> Unread portion of the kernel message buffer: >> >> >> Fatal trap 12: page fault while in kernel mode >> cpuid = 1; apic id = 01 >> fault virtual address = 0xf570 >> fault code = supervisor write data, page not present >> instruction pointer = 0x8:0x807c429b >> stack pointer = 0x10:0x511e4710 >> frame pointer = 0x10:0x20 >> 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 = 69996 (mkdir) >> trap number = 12 >> panic: page fault > > This one does look like a hardware issue from the stack trace. It's hard to > know if the first panic you saw was a hardware issue as well without the > stack trace information. > >> #7 0x807b706e in calltrap () >> at /usr/src/sys/amd64/amd64/exception.S:209 >> #8 0x807c429b in free_pv_entry (pmap=0x80b66c80, >> pv=Variable "pv" is not available. >> ) >> at /usr/src/sys/amd64/amd64/pmap.c:1905 >> #9 0x807c4403 in pmap_remove_entry (pmap=Variable "pmap" is >> not available. >> ) >> at /usr/src/sys/amd64/amd64/pmap.c:2131 >> #10 0x807c6447 in pmap_remove_pte (pmap=0x80b66c80, >> ptq=0xaaa8, va=18446744070506639360, ptepde=23601251, >> free=0x511e4790) at /usr/src/sys/amd64/amd64/pmap.c:2366 >> #11 0x807cab87 in pmap_remove (pmap=0x80b66c80, >> sva=18446744070506639360, eva=18446744070506909696) >> at /usr/src/sys/amd64/amd64/pmap.c:2510 > > -- > John Baldwin > The remote backup continues to run so there was definitely some issue there. No more reboots, but it wasn't doing that regularly without some additional load. Hopefully I can swap parts around until I find the offending item. Thanks for your input. I would try running memtest86 to check your RAM. -- John Baldwin It's ECC and was extensively tested when new so I suspect it's something else, but I'll memtest it overnight anyway. Sat at a panic when I went to put the floppy in.No debugger prompt and unresponsive so I power cycled it :( -- 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: ATA driver update for 7.2RELEASE available
On 15Jul, 2009, at 11:33 , Marat N.Afanasyev wrote: Søren Schmidt wrote: Over the past months I've gotten huge amounts of requests for ATA related things, so I've whipped up what I use here for FreeBSD 7.2- Release. This is a total replacement of the ATA driver, modulerized as in - current, but based on my WIP not from what might have happend to - current since I gave up maintainership. There is a number of new chipsets supported in here that I dont think is in any of the official sources (havn't checked in quite some time though), mostly newish ATI, nVidia and Marvell chips (yeah those buggers with both ATA & SATA ports). You can find and install.sh script and a tarball of the needed files at: http://www.deepcore.dk/pub/ATA Put both in /usr/src and run install.sh. As I dont subscribe to any of the mailing lists nor does my FreeBSD.org mail address seem to work anymore, you will need to reply to me directly if needed. As always - Enjoy! -Søren i think i'm dumb, but can you tell me how can atapicam be enabled with this implementation of ata? i couldn't still find a way :( You could just grap atapi-cam.c from stock 7.2 and use that I guess (as a module or compiled in), newer used it though... -Søren -- ___ 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"
