On Sat, 6 Mar 2004, Forrest W. Christian wrote:
> I recently swapped out a motherboard in a FreeBSD server for a new Intel
> Pentium 4 motherboard/processor to gain speed.
>
> Since that time, this machine has been randomly panicing such as:
>
> Fatal trap 12: page fault while in kernel mode
> mp_
On Mon, 8 Mar 2004, Doug White wrote:
> null pointer offset deref.
>
> thats not too unsuprising. Can you follow the instructions in the handbook
> to get a crashdump and use gdb to get a backtrace?
There is a backtrace and more detail in another message I posted to the
list within the last few h
02 vlandev sis2"
ifconfig_carp2="vhid 3 advskew 200 pass awe4jkfha4jkfha4f 10.50.0.1"
cloned_interfaces="... carp2 ... vlan2"
However, if I do the carp2 setup "manually" after the system is
booted, it is working fine.
ifconfig carp2 vhid 3 advskew 200 pass hjarefh
Hi,
I am having kernel dumps with FreeBSD 7.1
panic: semexit - semid not allocated
cpuid = 1
Uptime : 8m22s
Cannot dump. No dump device defined
Sleeping thread (tid 100129, pid 1479) owns a non-sleepable lock
I know it is not clear and there were no swap space configured on this
server (which I
if I do the carp2 setup "manually" after the system is
> booted, it is working fine.
>
> ifconfig carp2 vhid 3 advskew 200 pass hjarefhakjewfha 10.50.0.1
>
> Any ideas?
>
> (kernel dump below)
>
> - ask
>
>
> fault virtual address = 0x15c
> fa
However, if I do the carp2 setup "manually" after the system is
A> booted, it is working fine.
A>
A> ifconfig carp2 vhid 3 advskew 200 pass hjarefhakjewfha 10.50.0.1
A>
A> Any ideas?
A>
A> (kernel dump below)
A>
A> - ask
A>
A>
A> fault virtual add
Hi,
I'm assuming you configured a a dump-device in rc.conf, but just in
case, here are the options:
db ~> grep dump /etc/defaults/rc.conf
[...@gonzales]
dumpdev="AUTO"# Device to crashdump to (device name, AUTO, or
NO).
dumpdir="/var/crash" # D
On Fri, Jan 09, 2009 at 06:39:53PM +0200, Omer Faruk Sen wrote:
> Hi,
>
> I am having kernel dump with FreeBSD 7.1:
>
> Here is crashinfo output of it (Actually i don't know the state of
> crashinfo in Fbsd 7.1)
>
> 7.1-RELEASE FreeBSD 7.1-RELEASE #0: Thu
Hello,
I've discovered reproducable kernel panic but I cannot obtain a dump.
I have in rc.conf:
dumpdev="/dev/ad2s1b"
savecore_flags="-f"
... and in kernel configuration:
options KDB
options DDB
options KDB_UNATTENDED
makeoptions DEBUG=-g# Build kern
On Thu, Feb 22, 2007 at 01:56:44PM +0200, Alexander Shikoff wrote:
> Hello,
>
> I've discovered reproducable kernel panic but I cannot obtain a dump.
>
> I have in rc.conf:
>
> dumpdev="/dev/ad2s1b"
> savecore_flags="-f"
>
> ... and in kernel configuration:
>
> options KDB
> options
Hello,
funny questions for me as I'm not a newbie in FreeBSD... ;) But
I'll answer.
On Thu, Feb 22, 2007 at 05:22:24AM -0800, Jeremy Chadwick wrote:
> Is /dev/ad2s1b the correct location? Possibly you meant ad0s1b
> or some other adX device? (Common mistake.)
/home/minotaur>ls -l /dev/ad2s1b
c
On Thu, Feb 22, 2007 at 04:13:33PM +0200, Alexander Shikoff wrote:
> /etc/rc.d/dumpon creates symbolic link /dev/dumpdev. It's present in
> my /dev directory. I think a problem is somewhere deeply, probably
> with savecore(8). When a panic occurs I see in console process of
> dumping (size of RAM,
---> savecore -f -vv /var/crash /dev/ad2s1b
unable to open bounds file, using 0
checking for kernel dump on device /dev/ad2s1b
mediasize = 1073741824
sectorsize = 512
magic mismatch on last dump header on /dev/ad2s1b
savecore: unable to force dump - bad magic
savecore: no dumps found
Feb 23 10:
13 matches
Mail list logo
