Re: GEOM_MBR breaks my kernel
On Fri, Mar 14, 2003 at 03:37:53PM +0100, Poul-Henning Kamp wrote:
> In message <[EMAIL PROTECTED]>, walt writes:
> >I've been unable to boot any kernel I've built since about March 11
> >and I've narrowed it down to the GEOM_MBR option.
> >
> >With GEOM_MBR I get a kernel page fault error when trying to
> >mount the root filesystem at boot time.
>
> Can you get us the messages and a traceback ?
I saw the same thing on my system. I don't have the exact message
or traceback around, but the problem was essentially a null pointer
dereference while in kernel mode.
I was able to locate the offending line in the source:
In devfs_allocv:
if (de->de_dirent->d_type == DT_CHR) {
dev = *devfs_itod(de->de_inode);
if (dev == NULL)
return (ENOENT);
} else {
...
The first comparison causes the problem, since de->de_dirent == NULL.
The problem did not exist until I turned WITNESS & INVARIANTS off
(in a kernel with all GEOM_* stuff enabled).
Let me know if you need more information. If you need the traceback,
I'd appreciate if you told me how to get it written to a file. :)
Krzysztof
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: panic on boot (devfs_find)
On Sun, Mar 16, 2003 at 09:29:15AM +0100, Poul-Henning Kamp wrote: > > I don't think I'll stand a chance on this one until I can reproduce it > on one of my machines :-( I'm not sure if that helps, but on my machine it it enough to take GENERIC kernconf file, add all GEOM_ options and comment out INVARIANTS and WITNESSES. I don't thing this it the least amount of changes, but it reliably causes trap 12: Mounting root from ufs:/dev/ad1s1a Fatal trap 12: page fault while in kernel mode fault virtual address = 0x7 fault code = supervisor read, page not present instruction pointer = 0x8:0xc02b0ae3 stack pointer = 0x10:0xd5279934 frame pointer = 0x10:0xd527994c code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32, gran 1 processor eflags= interrupt enabled, resumr, IOPL = 0 current process = 45 (init) kernel: type 12 trap, code=0 Stopped at devfs_find+0x23:movzbl 0x7(%eax),%eax db> trace devfs_find(c3b15300,c058d4a0,2,c38cd3c0,2) at devfs_find+0x23 devfs_populate(c3bac200,0,c38cd3c0,0,0) at devfs_populate+0x1ea devfs_lookupx(d5279b08,1,0,c38cd3c0,6) at defvs_lookupx+0x22e devfs_lookup(d5279b08,c38cd3c0,0,c38cd3c0,c38cd3c0) at defvs_lookup+0x4b lookup(d5279c08,c3c5f400,400,d5279c24,c38cd3c0) at lookup+0x302 namei(d5279c08,0,0,0,0) at namei+0x20b revoke(c38cd3c0,d5279d10,4,c38cd3c0,1) at revoke+0x52 syscall(2f,2f,2f,bfbffdf8,0) at syscall+0x2aa Xint0x80_syscall() at Xint0x80_syscall+0x1d --- syscall (56, FreeBSD ELF32, revoke), eip = 0x8052c23, esp = 0xbfbffc6c, ebp = 0xbfbffc88 --- This was all copied from the screen by hand, but I hope there are no mistakes. I was unable to generate a crash dump, despite many attempts... :( Krzysztof To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Generating crash dumps
Hello, I don't seem to be able to generate a crash dump on -CURRENT. I was getting a kernel trap (I have DDB enabled). From the debugger I entered `panic', but I got another trap. `Continue' got me back to the first trap and repeated `panic' rebooted the machine w/o dumping anything. I tried setting the dumpdev variable in loader, to both, `disk3s1b' (after `curdev') or `ad1s3b' (/dev/ad1s3b is the swap partition). The swap partition is larger than the physical memory. Disabling DDB didn't help. I have read the Handbook. What am I doing wrong? Krzysztof To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Buildkernel broken
Hello, I cvsupped the source this morning and I get: [...] ===> firewire/firewire cc -O -pipe -march=pentium2 -D_KERNEL -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -DKLD_MODULE -nostdinc -I- -I. -I@ -I@/dev -I@/../include -fno-common -g -mno-align-long-strings -mpreferred-stack-boundary=2 -ffreestanding -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -c /usr/src/sys/dev/firewire/firewire.c cc -O -pipe -march=pentium2 -D_KERNEL -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -DKLD_MODULE -nostdinc -I- -I. -I@ -I@/dev -I@/../include -fno-common -g -mno-align-long-strings -mpreferred-stack-boundary=2 -ffreestanding -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -c /usr/src/sys/dev/firewire/fwohci.c In file included from /usr/src/sys/dev/firewire/fwohci.c:72: @/dev/firewire/fwdma.h:38: redefinition of `bus_dmasync_op_t' machine/bus_dma.h:94: `bus_dmasync_op_t' previously declared here *** Error code 1 [...] Krzysztof ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
login coredumps
At the login prompt using the arrow keys to move the cursor up and down causes login to dump core. System was cvsupped today. Krzysztof To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
shutdown doesn't
It goes into background and nothing happens. Krzysztof To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Using laptop with lid closed
Is there any way to prevent the system from reacting to the lid being closed? At this time when I close the lid I get the following messages: ed1: detached pccard: card disabled, slot 0 Then after re-opening, I have to press the power button for the system to wake up. I'm using Thinkpad A22m. Krzysztof To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
rman coredump in gv-3.5.8
rman on -current chokes and dies on gv.man from gv-3.5.8. rman on -stable can take it with no problems at all. [transcript of the failure] ===> Installing for gv-3.5.8 ===> gv-3.5.8 depends on executable: mkhtmlindex - found ===> gv-3.5.8 depends on shared library: Xaw3d.7 - found ===> gv-3.5.8 depends on shared library: X11.6 - found installing in ./source... /usr/bin/install -c -s gv /usr/X11R6/bin/gv /usr/bin/install -c -m 0644 gv_system.ad /usr/X11R6/lib/X11/gv/ /usr/bin/install -c -m 0644 gv_user.ad /usr/X11R6/lib/X11/gv/ /usr/bin/install -c -m 0644 gv_class.ad /usr/X11R6/lib/X11/gv/ /usr/bin/install -c -m 0644 GV.ad /usr/X11R6/lib/X11/app-defaults/GV install in source done install in . done installing man pages in ./doc... rm -f gv._man cd `dirname gv` && ln -s `basename gv.man` `basename gv._man` rm -f gv.1.html gv.1-html rman -f HTML < gv._man > gv.1-html && mv -f gv.1-html gv.1.html macro "tr" not recognized -- ignoring macro "ec" not recognized -- ignoring macro "\}" not recognized -- ignoring Segmentation fault - core dumped *** Error code 139 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: rman coredump in gv-3.5.8
On Mon, May 06, 2002 at 10:07:53PM -0700, Kris Kennaway wrote: > On Tue, May 07, 2002 at 12:02:41AM -0500, Krzysztof Parzyszek wrote: > > rman on -current chokes and dies on gv.man from gv-3.5.8. > > rman on -stable can take it with no problems at all. > > It's an XFree86-4.x problem. I'm not sure what you mean. It this a wrong mailing list for such things or is it just an issue with X 4.2.0? Anyway, I compiled X 4.2.0 from sources on both -stable and -current and I'm only seeing this problem on -current. Krzysztof To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
