panic: vm_fault: fault on nofault entry, addr: d0a5c000
There were messages about rl1 receiving oversized frames just before
the panic. They didn't get recorded, sorry. (Working remotely, no
serial console.)
I've still got the dump. I can do more if required.
Regards,
David
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 "i386-marcel-freebsd".
Unread portion of the kernel message buffer:
panic: vm_fault: fault on nofault entry, addr: d0a5c000
KDB: enter: panic
panic: from debugger
Uptime: 1d18h30m35s
Dumping 255 MB (2 chunks)
chunk 0: 1MB (159 pages) ... ok
chunk 1: 255MB (65280 pages) 240 224 208 192 176 160 144 128 112 96 80 64 48
32 16
#0 doadump () at pcpu.h:165
165 __asm __volatile("movl %%fs:0,%0" : "=r" (td));
(kgdb) bt
#0 doadump () at pcpu.h:165
#1 0xc0564748 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:399
#2 0xc05649f3 in panic (fmt=0xc076844f "from debugger")
at /usr/src/sys/kern/kern_shutdown.c:555
#3 0xc0457be9 in db_panic (addr=-1067991289, have_addr=0, count=-1,
modif=0xcbfec924 "") at /usr/src/sys/ddb/db_command.c:438
#4 0xc0457b80 in db_command (last_cmdp=0xc0825ee4, cmd_table=0x0,
aux_cmd_tablep=0xc07b02a4, aux_cmd_tablep_end=0xc07b02a8)
at /usr/src/sys/ddb/db_command.c:350
#5 0xc0457c48 in db_command_loop () at /usr/src/sys/ddb/db_command.c:458
#6 0xc045983d in db_trap (type=3, code=0) at /usr/src/sys/ddb/db_main.c:221
#7 0xc057c183 in kdb_trap (type=3, code=0, tf=0xcbfeca64)
at /usr/src/sys/kern/subr_kdb.c:473
#8 0xc0734a5c in trap (frame=
{tf_fs = -872546296, tf_es = -1068040152, tf_ds = -1065877464, tf_edi =
1, tf_esi = -1065735013, tf_ebp = -872494428, tf_isp = -872494448, tf_ebx =
-872494384, tf_edx = 0, tf_ecx = -1056878592, tf_eax = 18, tf_trapno = 3,
tf_err = 0, tf_eip = -1067991289, tf_cs = 32, tf_eflags = 658, tf_esp =
-872494396, tf_ss = -1068086877}) at /usr/src/sys/i386/i386/trap.c:591
#9 0xc07277ea in calltrap () at /usr/src/sys/i386/i386/exception.s:139
#10 0xc057bf07 in kdb_enter (msg=0x12 )
at cpufunc.h:60
#11 0xc05649a3 in panic (
fmt=0xc07a2c9b "vm_fault: fault on nofault entry, addr: %lx")
at /usr/src/sys/kern/kern_shutdown.c:539
#12 0xc06d61ec in vm_fault (map=0xc1043000, vaddr=3500523520,
fault_type=1 '\001', fault_flags=0) at /usr/src/sys/vm/vm_fault.c:277
#13 0xc0734c4f in trap_pfault (frame=0xcbfecc0c, usermode=0, eva=3500523520)
at /usr/src/sys/i386/i386/trap.c:731
#14 0xc07348e9 in trap (frame=
{tf_fs = -1068171256, tf_es = -1049034712, tf_ds = 40, tf_edi =
-1048979612, tf_esi = -794443778, tf_ebp = -872493928, tf_isp = -872494024,
tf_ebx = -1049118720, tf_edx = -1048979456, tf_ecx = 39, tf_eax = -254535834,
tf_trapno = 12, tf_err = 0, tf_eip = -1066193906, tf_cs = 32, tf_eflags =
66054, tf_esp = 10896, tf_ss = 2048}) at /usr/src/sys/i386/i386/trap.c:432
#15 0xc07277ea in calltrap () at /usr/src/sys/i386/i386/exception.s:139
#16 0xc0732c0e in generic_bcopy () at /usr/src/sys/i386/i386/support.s:489
(kgdb) quit
#
# 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.422 2005/01/05 05:25:21 kuriyama Exp $
machine i386
cpu I586_CPU
cpu I686_CPU
ident TOR
# To statically compile in device wiring instead of /boot/device.hints
#hints "GENERIC.hints" # Default places to look for devices.
makeoptions DEBUG=-g# Build kernel with gdb(1) debug symbols
#optionsSCHED_ULE # ULE scheduler
options SCHED_4BSD # 4BSD scheduler
options PREEMPTION # Enable kernel thread preemption
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 # Imp
Re: Laptop choices
On Wed, Nov 23, 2005 at 03:36:07PM -0500, Parv wrote: > in message <[EMAIL PROTECTED]>, wrote Gary Kline > thusly... > > > > I'm looking for a newer laptop (a newer, faster ThinkPad, > > probably). There are ' some seriously cheap laptops "on-sale", > > but they would probably be a bad choice because they have those > > touch/scratch mouse-pad things that I can't use. So:: does > > anybody know of a ThinkPad clone? Or, can the touch pads be > > disabled in the bios? > > Yes, yes the touch pad can be disabled in BIOS, at least on IBM > ThinkPad T41 (my sister dislikes touchpad) & T42 (i noticed the > option in BIOS to disable touchpad) . I've got a ThinkPad T42. The trackpad can be turned off in the bios. As a truely added bonus, the stick mouse has three buttons; if you turn the trackpad off in the bios, the stick works like a plain old-fashioned three-buttoned ps/2 mouse. I like the sticks, a whole lot. I hate mice, as I can type, thanks, muchly. Using a mouse means that I have to take my hand away from the keyboard. With the stick, while I have to displace my hand from the keys, it's only about half an inch, so it's not much loss of time. I really would like one for the desktop, but they're expensive, and I don't know of one with three buttons. Incidently, there are a whole buncy of T41/42/43 models, which have different features. The T42s and T43s are available in versions that will do 1400X1050, with either screen size. David ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Swapfile problem in 6?
On Tue, Nov 15, 2005 at 07:18:35PM -0800, David Wolfskill wrote: > On Tue, Nov 15, 2005 at 06:09:33PM -0800, Rob wrote: > > ... > > > > > What is this "serial BREAK"? > > How do I "send a serial BREAK" at the serial > > console? Is this some magic key combination? > > I'm probably saying something about my age by doing this :-} > > A "BREAK" (in serial communications) is an absence of start or stop > bits for more than a character's worth of bits, is handled as a > "framing error," and is distinct from any character. > > Now, to generate one, you would normally hit the BREAK key of your > terminal (Control-BREAK on some; I think Hazeltine had this feature of > dubious merit). > > If you are using a serial communications program (such as "tip") instead > of an ASCII terminal, it depends on the program you're using. > > In the case of tip, the sequence "~#" at the beginning of a line will > generate tip's best approximation of a framing error. > > In the case of kermit, Control-\B does it. If you're using a terminal program on something like Windows or a Macintosh, there's usually a menu option to send a BREAK. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Strange boot messages under 6.0-STABLE
On Mon, Nov 14, 2005 at 03:01:19PM -0500, Kris Kennaway wrote: > On Mon, Nov 14, 2005 at 06:45:15PM +0100, Ales wrote: > > During boot process under 6.0-STABLE I spoted some strange messages. > > > > Nov 14 18:18:45 romcek savecore: reboot after panic: page fault > > Nov 14 18:18:45 romcek savecore: no dump, not enough free space on > > Your system panicked at some point in the past, but it can't save the > dump for the reason specified. If you just want to prevent the message from printing at the next boot time, run 'savecore -c'. If you want to try and retrieve the dump, you can specify an alternate location to save the dump on the savecore command line. David ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ACPI Suspend/resume [was Re: ATA mkIII first official patches...]
Vlad Manilici wrote: Hi, Does 5-STABLE have a working acpi based suspend/resume for anyone? I have a 5-STABLE from 27.01, on an IBM R40e. Suspend to memory (-s 3) seems to work, but there is no way to resume. How do you trigger a resume?? On my IBM T42, I set hw.acpi.lid_switch_state to S3, so opening the lid is enough. If I suspend with acpiconf or the switch, pressing fn-F4 (It's got a cresent moon on it, I think IBM does the same keys on other models) or pressing the holding the power switch for a couple seconds does the trick. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ACPI Suspend/resume [was Re: ATA mkIII first official patches...]
George Hartzell wrote: I haven't had time to upgrade (cobbler's kids, no shoes, etc...) but it's on my list of things to do. Does 5.3 Release have a working acpi based suspend/resume for anyone? Does 5-STABLE have a working acpi based suspend/resume for anyone? Suspend to memory works on my T42 on 5.3-STABLE as of 1/1/05. except i've got to restart mosed. I've not bothered to investigate what's going on. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: XDM/CHOOSER Xfree 401 and Xfree 336 on FBSD 4.2
On Wed, 15 Nov 2000, O. Hartmann wrote: :configuration situations the exact same behaviour! So I should exclude any :trouble with IPFW or similar filtering tools or anything with autheticatio :schemes. : :Well, I never read anything about problems or changes in how XDM works in :XFree86 4.0.1, so if there is anybody out here who has some information :he's very welcome to email me. I remember that there was a problem with some early XFree 4.x, where the default configuration was broken. I don't remember the details, but it's possible to fix by recompiling with the correct options. It was discussed here, or maybe in -chat. Maybe this jogs someone's memory? David To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
