FreeBSD 5.1 PowerPak Installation problem
Ion-Mihai Tetcu
itetcu at apropo.ro
Mon Dec 22 05:31:13 PST 2003
On Mon, 22 Dec 2003 12:51:13 -0000
"Admin" <admin at sycos.co.uk> wrote:
> Dec 19 18:26:44 syslogd: kernel boot file is /boot/kernel/kernel
> Dec 19 18:26:44 kernel:
> Dec 19 18:26:44 kernel:
> Dec 19 18:26:44 kernel: Fatal trap 12: page fault while in kernel mode
> Dec 19 18:26:44 kernel: fault virtual address = 0xc6cd4880
> Dec 19 18:26:44 kernel: fault code = supervisor write, page not present
> Dec 19 18:26:44 kernel: instruction pointer = 0x8:0xc0480f27
> Dec 19 18:26:44 kernel: stack pointer = 0x10:0xdcc7f7e8
> Dec 19 18:26:44 kernel: frame pointer = 0x10:0xdcc7f878
> Dec 19 18:26:44 kernel: code segment = base 0x0, limit 0xfffff, type 0x1b
> Dec 19 18:26:44 kernel: = DPL 0, pres 1, def32 1, gran 1
> Dec 19 18:26:44 kernel: processor eflags = interrupt enabled, resume, IOPL = 0
> Dec 19 18:26:44 kernel: current process = 5329 (tar)
> Dec 19 18:26:44 kernel: trap number = 12
> Dec 19 18:26:44 kernel: panic: page fault
> Dec 19 18:26:44 kernel:
As I've already sad, this is as far as I can go, esp. without a
backtrace. Compile your kernel with debug symbols, set your comuter to
save the kernel's core, etc. It is all documented in the handbook and
the faq. Beeing a programmer it shouldn't be hard to understad how to
set up that.
> Dec 19 18:26:44 kernel: syncing disks, buffers remaining... 3485 3485 3484 3484 3483 3483 3483 3483 3483 3483 3483 3483 3483 3483 3483 3483 3483 3483 3483 3483 3483 3483 3483 3483
[..]
> Dec 19 18:26:44 kernel: Mounting root from ufs:/dev/ad0s1a
> Dec 19 18:26:44 kernel: WARNING: / was not properly dismounted
> Dec 19 18:26:44 kernel: WARNING: /tmp was not properly dismounted
> Dec 19 18:26:44 kernel: WARNING: /usr was not properly dismounted
> Dec 19 18:26:44 kernel: WARNING: /var was not properly dismounted
> Dec 19 18:26:44 kernel: /var: mount pending error: blocks 368 files 175
> Dec 19 18:27:47 fsck: /dev/ad0s1e: 4 files, 2 used, 126837 free (21 frags, 15852 blocks, 0.0% fragmentation)
> Dec 19 18:28:34 fsck: /dev/ad0s1f: INCORRECT BLOCK COUNT I=566744 (4 should be 0) (CORRECTED)
> Dec 19 18:28:34 fsck: /dev/ad0s1f: INCORRECT BLOCK COUNT I=566745 (4 should be 0) (CORRECTED)
> Dec 19 18:28:34 fsck: /dev/ad0s1f: INCORRECT BLOCK COUNT I=566748 (4 should be 0) (CORRECTED)
[..]
fsck work
> Dec 19 18:28:34 fsck: /dev/ad0s1f: INCORRECT BLOCK COUNT I=567394 (4 should be 0) (CORRECTED)
> Dec 19 18:28:34 fsck: /dev/ad0s1f: SETTING DIRTY FLAG IN READ_ONLY MODE
haven't dow that untill now
> Dec 19 18:28:34 fsck:
> Dec 19 18:28:34 fsck: /dev/ad0s1f: UNEXPECTED SOFT UPDATE INCONSISTENCY; RUN fsck MANUALLY.
run it manually, by booitng in single user.
--
IOnut
Unregistered ;) FreeBSD user
More information about the freebsd-questions
mailing list