Gary Kline wrote:
[snip]
my network bud down in dallas is helping me get the dell as my
new server. my old hp kayak is from 1998 and on its death-bed.
okay: i have 7.2-R, i386. installs fine. jon horne changed the
IP that the op sys | DHCP suite chose from 10.47.0.112 to
10.47.0.230.
On Tue, Nov 17, 2009 at 05:23:53AM -0500, Michael Powell wrote:
Gary Kline wrote:
[snip]
my network bud down in dallas is helping me get the dell as my
new server. my old hp kayak is from 1998 and on its death-bed.
okay: i have 7.2-R, i386. installs fine. jon horne changed the
something panicked my dell. more than twice. i have loaded, the
i386 7.2-R Dvd. the panic was something like
PHY#1
panic[y/n]y
then something about cpu 0 being involved.
i have the 8.0 rc3 bootonly.iso cd. should i try that? or did
Hi
On Mon, Nov 16, 2009 at 5:58 PM, Gary Kline kl...@thought.org wrote:
something panicked my dell. more than twice. i have loaded, the
i386 7.2-R Dvd. the panic was something like
PHY#1
panic[y/n]y
Do you have a crash report in /var/crash
On Mon, Nov 16, 2009 at 07:57:19PM -0500, Glen Barber wrote:
Hi
On Mon, Nov 16, 2009 at 5:58 PM, Gary Kline kl...@thought.org wrote:
something panicked my dell. more than twice. i have loaded, the
i386 7.2-R Dvd. the panic was something like
PHY#1
, the
i386 7.2-R Dvd. the panic was something like
PHY#1
panic[y/n]y
Do you have a crash report in /var/crash ?
no, nada. i didnt know about /var/crash until now, thanks for the
datapoint. it is empty.
Very important location on your system after
:
something panicked my dell. more than twice. i have loaded, the
i386 7.2-R Dvd. the panic was something like
PHY#1
panic[y/n]y
Do you have a crash report in /var/crash ?
no, nada. i didnt know about /var/crash until now, thanks
# echo hello hello.txt
cannot create hello.txt: Read-only file system
6. That seems like the desired response. Next, attempt to modify a
file that already exists in the snapshot:
Fixit# echo hello test.txt
panic: dirtying snapshot!
I know I'm not supposed to be modifying a snapshot file
2009/10/20 Carl Chave c...@chave.us
Does file o exist? In my example I first try to create a new file
which fails as expected. I then try to append to an existing file
which triggers the panic.
On Tue, Oct 20, 2009 at 6:17 AM, krad kra...@googlemail.com wrote:
2009/10/19 Carl Chave
Le Mon, 19 Oct 2009 14:53:27 -0700,
Bogdan Webb bog...@pgn.ro a écrit :
Hello,
What's wrong with my bsd box (witch i'm in love so much now) and how
can i prevent it from panicking
No one will be able to answer without a dump of the panic.
Please see
http://www.freebsd.org/doc/en/books
Thanks for testing it out krad. I went ahead and submitted the PR:
http://www.freebsd.org/cgi/query-pr.cgi?pr=139806
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any
.
The first time i wasn't paying much attention to the process and can't tell
exactly what caused the panic (it was certainly a port install related) but
i've paid close attention to this 2nd time. The server runs FreeBSD
7.2-RELEASE #0 on a amd64 arch and it cracked when i tried to install
-only file system
6. That seems like the desired response. Next, attempt to modify a
file that already exists in the snapshot:
Fixit# echo hello test.txt
panic: dirtying snapshot!
I know I'm not supposed to be modifying a snapshot file, but a panic
doesn't seem like the best response
, the journal device is mixed in with the data
provider. In both cases, I was trying to copy a 19GB file from an
external USB device (da1p16.journal) to the filesystem on a 3Ware
RAID-10 (da7p0.journal).
This afternoon I saw...
panic: Journal overflow (joffset=xxx active=
inactive=zz
.journal) to the filesystem on a 3Ware
RAID-10 (da7p0.journal).
This afternoon I saw...
panic: Journal overflow (joffset=xxx active=
inactive=zz)
cpuid = 1
Uptime:
Physical memory: 1011 MB
Dumping 351MB
Fatal trap 12: page fault while in kernel mode
cpuid = 0, apic id = 00
fault
cases, I was trying to copy a 19GB file from an
external USB device (da1p16.journal) to the filesystem on a 3Ware
RAID-10 (da7p0.journal).
This afternoon I saw...
panic: Journal overflow (joffset=xxx active=
inactive=zz)
cpuid = 1
Uptime:
Physical memory: 1011 MB
Dumping
I've been trying to debug a server running FreeBSD 7.2-RELEASE/amd64
that's hanging intermittently or rebooting without much luck.
The machine hosts the home directories for the users over NFS. The
workstations that use it are pretty much all Solaris 10 boxes (mostly
sparc with five x86
0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= interrupt enabled, IOPL = 0
current process = 11 (idle: cpu0)
trap number = 18
panic: integer divide fault
cpuid = 0
Uptime: 2h56m59s
Physical memory: 115 MB
Dumping 33 MB: 18 2
Reading
)
Blocksize: 512
Dumptime: Thu Aug 13 09:14:44 2009
Hostname: gameface
Magic: FreeBSD Kernel Dump
Version String: FreeBSD 7.2-RELEASE #0: Wed May 20 16:56:48 EDT 2009
r...@gameface:/usr/obj/usr/src/sys/GENERICplus
Panic String: ufs_dirbad: /var: bad dir ino 3485849 at offset 3584
Здравствуйте, Mel.
Вы писали 12 августа 2009 г., 19:59:39:
MF On Wednesday 12 August 2009 08:01:07 Коньков Евгений wrote:
Aug 12 15:59:08 host savecore: reboot after panic: integer divide fault
Aug 12 15:59:08 host savecore: writing core to vmcore.4
How to obtain which process cause system
Here is the full error:
Aug 13 09:29:57 gameface savecore: reboot after panic: ufs_dirbad: /var:
bad dir ino 3485849 at offset 3584: mangled entry
The error causes the machine to keep rebooting on its own over and over
again.
i386 7.2-RELEASE FreeBSD 7.2-RELEASE #0: Wed May 20 16:56:48 EDT
On Thu, Aug 13, 2009 at 12:25:21PM -0400, B. Cook wrote:
Here is the full error:
Aug 13 09:29:57 gameface savecore: reboot after panic: ufs_dirbad: /var:
bad dir ino 3485849 at offset 3584: mangled entry
The error causes the machine to keep rebooting on its own over and over
again.
You
On Thu, August 13, 2009 3:15 pm, Roland Smith wrote:
On Thu, Aug 13, 2009 at 12:25:21PM -0400, B. Cook wrote:
Here is the full error:
Aug 13 09:29:57 gameface savecore: reboot after panic: ufs_dirbad: /var:
bad dir ino 3485849 at offset 3584: mangled entry
The error causes the machine
Aug 12 15:59:08 host savecore: reboot after panic: integer divide fault
Aug 12 15:59:08 host savecore: writing core to vmcore.4
How to obtain which process cause system to reboot?
--
С уважением,
Коньков mailto:kes-...@yandex.ru
On Wednesday 12 August 2009 08:01:07 Коньков Евгений wrote:
Aug 12 15:59:08 host savecore: reboot after panic: integer divide fault
Aug 12 15:59:08 host savecore: writing core to vmcore.4
How to obtain which process cause system to reboot?
kgdb /boot/kernel/kernel /var/crash/vmcore.4
--
Mel
The FreeBSD Developers' Handbook describes how to get panic information (and
dig out further details).
http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html#KERNELDEBUG-OBTAIN
Was there any output before ad7: FAILURE - device detached? Losing the drive
Hi guys,
I use mount_smbfs on my notebook and I have a little nasty problem..
Sometimes I have kernel panic when resuming after the suspend. The
issue seems to happen when I go to suspend with my USB network (WiFi)
adapter plugged in (I do use /etc/rc.d/netif stop rum0 before going
to suspend
I've been having a problem for the past few weeks with a file server I
have. It's recently started throwing a panic after about 24 hours of
service (it's rare that it lasts longer then that...sometimes as low as 20
hrs): Panic String: Journal overflow (joffset=12964580764160
active=12964584978944
I'm trying to figure out a strange panic issue (see:
http://lists.freebsd.org/pipermail/freebsd-questions/2009-July/201842.html).
The problem is I generally need to run it overnight in order to reproduce it.
By the time I get back to it, the machine has auto-rebooted, losing
precious info
Hi.
On Sat, Jul 11, 2009 at 12:25 AM, jwjwde...@gmail.com wrote:
I'm trying to figure out a strange panic issue (see:
http://lists.freebsd.org/pipermail/freebsd-questions/2009-July/201842.html).
The problem is I generally need to run it overnight in order to reproduce it.
By the time I get
(RAID 1), which is the boot device.
A seagate drive connected via SATA
A WD external drive via USB
I will have the system running fine, then the seagate will apparently
fall off the bus, resulting in a panic.
The dump fails as well, presumably due to the 3ware driver not being
able to handle
...
# mount -t xfs -o ro /dev/ad0s2 /mnt
# ls /mnt
# cp /mnt/my_file /home/zbigniew
I forgot add here that I do then
# umount /mnt
and after that was kernel panic.
I'm sorry for the mistake.
Zbigniew
___
freebsd-questions@freebsd.org mailing list
Hello,
I have a Dabian 5.0 and FreeBSD 7.2-RELEASE-p2 on i386 athlon-xp. I have two
partitions under Debian. They are xfs file system.
So I mount it from FreeBSD
# mount -t xfs -o ro /dev/ad0s1 /mnt
# ls /mnt
# umount /mnt
Everything is OK, but now I do the following
# mount -t xfs -o ro
Hi,
Could use some pointers here. I have an AMD64 system Gigabyte GA-MA770
motherboard, 4 GB RAM, Athlon 64 CPU. System won't boot. Flags error,
panic ohci_add_done : addr 0x... not found
Then it reboots. Tried disabling everything in the bios. (Including usb
kbd and mouse)
At wit's end
Hi,
After 6-7 reboots, I managed to get the 7.2-RELEASE installation media to
boot and install properly.
2 issues still remain however.
1) No sound : My Gigabyte GA-MA78GM-US2H board has onboard Realtek High
Definition Audio. Since I couldn't figure out which driver would work with
this, I put
this, the system prompts for panic (y/n). Accepting y leads to
a bye-bye, and entering n leads to a PHY# 2 failed message and
another panic prompt.
What is this supposed to mean ?
Thanks for any help.
--
Regards
Manish Jain
invalid.poin...@gmail.com
+91-96500-10329
Laast year I kudn't spell
I forgot to mention that Windows installs and runs very smoothly on
the system.
Windows system information reports :
System Manufacturer Gigabyte Technology Co., Ltd.
System ModelGA-MA78GM-US2H
System Type X86-based PC
Processor x86 Family 16 Model 2 Stepping 3
to - 7.2 panic during installation : AP #1 (PHY#
1) failed !
I forgot to mention that Windows installs and runs very smoothly on
the system.
Windows system information reports :
System Manufacturer Gigabyte Technology Co., Ltd.
System Model GA-MA78GM-US2H
System Type X86-based PC
Subject: In addition to - 7.2 panic during installation : AP #1 (PHY#
1) failed !
I forgot to mention that Windows installs and runs very smoothly on
the system.
Windows system information reports :
System Manufacturer Gigabyte Technology Co., Ltd.
System ModelGA-MA78GM-US2H
System
The only thing that strikes me as odd is that right-clicking on My Computer
reports the amount of RAM as 768 MB, while the diagnostics above states 1024
MB.
For the brief period of time the FreeBSD installer runs, it reports the
amount of RAM as 768 MB too.
Don't you have shared-memory
Manish Jain wrote:
I forgot to mention that Windows installs and runs very smoothly on the
system.
Windows system information reports :
System ManufacturerGigabyte Technology Co., Ltd.
System ModelGA-MA78GM-US2H
snip
The only thing that strikes me as odd is that
On Friday 22 May 2009 05:30:42 Shawn Badger wrote:
Hi, I installed FreeBSD 7.2 Release on a mini nettop (Intel
Atom/945gc/ICH7 hardware), and everything seemed to go smoothly.
However, when I boot the system and the filesystem checks have been
going for awhile, it always ends in a panic
proven
so stable for me, I'm curious what on earth could cause this sort
of regular panic?
It's not time of day; if I reboot at 2:00 AM, 3:55 PM, or any other
time, it's 23:55 or so later I get a panic, whenever that may be.
I think this rules out cron jobs, external attacks, and load-based
Hi, I installed FreeBSD 7.2 Release on a mini nettop (Intel
Atom/945gc/ICH7 hardware), and everything seemed to go smoothly.
However, when I boot the system and the filesystem checks have been
going for awhile, it always ends in a panic. Here's the dump:
dev = ad4s1f, block = 1, fs = /usr
On Sun, May 17, 2009 at 2:06 PM, Doug Lee d...@dlee.org wrote:
One of the weirder things I've seen in a while here...
OS: FreeBSD 4.11 (yeah I know, old, but generally stable)
CPU: Intel(R) Pentium(R) 4 CPU 2.00GHz
real memory = 536608768 (524032K bytes)
Hds: IDE
Problem: Ever since a
@freebsd.org
Subject: Re: 4.11 panic every 23 hours 55 minutes or so
Why does the panic happen 24 hours after the last reboot; who
knows and one may never know. Are you finally hitting, the bad
RAM? Are you finally getting the computer over-warm to act
up?
Or running a heavy process around the time
of regular panic?
It's not time of day; if I reboot at 2:00 AM, 3:55 PM, or any other
time, it's 23:55 or so later I get a panic, whenever that may be.
I think this rules out cron jobs, external attacks, and load-based
issues.
I'll provide the latest two panic logs below, followed by a few
rounds
,
and hopefully in line for upgrade; but as FreeBSD has always proven
so stable for me, I'm curious what on earth could cause this sort
of regular panic?
It's not time of day; if I reboot at 2:00 AM, 3:55 PM, or any other
time, it's 23:55 or so later I get a panic, whenever that may be.
I
minutes either way. ?Obviously hardware is suspect,
and hopefully in line for upgrade; but as FreeBSD has always proven
so stable for me, I'm curious what on earth could cause this sort
of regular panic?
It's not time of day; if I reboot at 2:00 AM, 3:55 PM, or any other
time, it's 23
exhibiting kernel panics about every 23 hours 55 minutes, give or
take about 4 minutes either way. ?Obviously hardware is suspect,
and hopefully in line for upgrade; but as FreeBSD has always proven
so stable for me, I'm curious what on earth could cause this sort
of regular panic
On Sun, May 17, 2009 at 09:42:05AM -0400, Mehmet Erol Sanliturk wrote:
Another problem may be as follows :
I am living an area nearby to industrial factories .
When they are started or stopped . they are causing important
fluctuation in my home current in such a way that even
Trap 12 are usually hardware related many times RAM.
Since it happened after bad power, I would besides testing your RAM but
make sure your power supply and fans are operating normally.
Why does the panic happen 24 hours after the last reboot; who knows and
one may never know. Are you finally
-Original Message-
From: owner-freebsd-questi...@freebsd.org
[mailto:owner-freebsd-questi...@freebsd.org] On Behalf Of Mark Tinguely
Sent: zondag 17 mei 2009 17:30
To: d...@dlee.org
Cc: freebsd-questions@freebsd.org
Subject: Re: 4.11 panic every 23 hours 55 minutes or so
Why does
I'm using an Intel DG33BU board with a SATA HD and SATA optical drives.
Using FreeBSD 7.1 AMD64 I get a kernel panic and subsequent file system
corruption when attempting to burn a cd using the burncd utility. I can
avoid this easily enough by using cdrecord and growisofs which work
I'm using an Intel DG33BU board with a SATA HD and SATA optical drives.
Using FreeBSD 7.1 AMD64 I get a kernel panic and subsequent file system
corruption when attempting to burn a cd using the burncd utility. I can
avoid this easily enough by using cdrecord and growisofs which work
prefer a simple error message and not a
kernel panic, I can change the disk with a hotspare remotely. Impossible
when the server is down.
Big thanks,
Jan
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd
About every 5-10 minutes, my freshly installed freeBSD 7.1 stable box
hangs and begains a kernal dump. I get the following error message:
dev = twed0s1d, block = 1, fs = /archive
panic: ffs_blkfree freeing free block
cpuid = 1
Uptime = 11m23s
Physical memory: 1011 MB
Dumping 67 MB: 52 36 20 4
dev = twed0s1d, block = 1, fs = /archive
panic: ffs_blkfree freeing free block
looks like ffs related panic, not ZFS.
something is completely wrong here.
cpuid = 1
Uptime = 11m23s
Physical memory: 1011 MB
Dumping 67 MB: 52 36 20 4
Dump complete
/archive has no files in it as it is an empty
!!
TFC
On Sun, Mar 29, 2009 at 2:49 PM, Polytropon free...@edvax.de wrote:
On Sun, 29 Mar 2009 14:23:13 -0400, Tsu-Fan Cheng tfch...@gmail.com wrote:
init: not found in path /sbin/ (a lot of paths)
panic: no init
what is that??
The init process is the root of the FreeBSD startup
On Mon, 30 Mar 2009 08:20:46 -0400, Tsu-Fan Cheng tfch...@gmail.com wrote:
But while I was testing an
exact same mborad I got from ebay, I noticed that the replacing board
name my SATA differently from the old board, its designated as ad10
and ad12 instead of ad4 and ad6. What is the mechanism
On Monday 30 March 2009 14:46:08 Polytropon wrote:
Note that this change of the device name usually requires changes
in /etc/fstab, e. g. ad4 - ad10 to make the system start on this
hardware.
fstab problem can be solved by using glabel sensibly. Also, isn't
ATA_STATIC_ID supposed to solve
/rescue/init error8
init: not found in path /sbin/ (a lot of paths)
panic: no init
what is that??
TFC
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail
On Sun, 29 Mar 2009 14:23:13 -0400, Tsu-Fan Cheng tfch...@gmail.com wrote:
init: not found in path /sbin/ (a lot of paths)
panic: no init
what is that??
The init process is the root of the FreeBSD startup, and the last
part of the OS loader cannot find it, so the OS cannot start.
http
eflags= resume, IOPL = 0
current process = 1072 (Thunar)
trap number = 12
panic: page fault
cpuid = 1
Uptime: 7h35m34s
Physical memory: 3058 MB
Dumping 310 MB: 295 279 263 247 231 215 199 183 167 151 135 119 103 87
71 55 39 23 7
#0 doadump () at pcpu.h:195
195
Hi,
7.1-RELEASE installs fine on the machine, but when I try to start
xorg I get kernel page fault.
it's Intel G45 GMA-4500HD. I saw a thread back in September 2008 that
added support for the G45 chipset, did it make its way into the 7.1
release?
Thanks,
Howard
[long number] too short/too long appear
for several minutes. When /stand/sysinstall running as init on vty0
is finally reached, more of the messages appear. Finally, sysinstall
is started, but keyboard response is very slow. After, a few minutes
a kernel panic occurs spin lock held too long
Peter Jeremy peterjer...@optushome.com.au writes:
Kamlesh Patel shilp.ka...@yahoo.com writes:
How do i recover the system from this error. I can't reload the
loader.old
If you press any key during the first spinner [...] You can then
enter the name of the program you wish to run - eg
On Mon, Jan 12, 2009 at 6:50 AM, Dag-Erling Smørgrav d...@des.no wrote:
Peter Jeremy peterjer...@optushome.com.au writes:
Kamlesh Patel shilp.ka...@yahoo.com writes:
How do i recover the system from this error. I can't reload the
loader.old
If you press any key during the first spinner
Garrett Cooper yanef...@gmail.com writes:
Dag-Erling Smørgrav d...@des.no writes:
Peter Jeremy peterjer...@optushome.com.au writes:
If you press any key during the first spinner [...] You can then
enter the name of the program you wish to run - eg /boot/loader.old
That won't work - he
On 2009-Jan-09 00:05:47 -0800, Kamlesh Patel shilp.ka...@yahoo.com wrote:
How do i recover the system from this error. I can't reload the loader.old
If you press any key during the first spinner, you should get a prompt
similar to the following:
FreeBSD/i386 BOOT
Default: 0:ad(0,a)/boot/loader
On Fri, Jan 9, 2009 at 1:07 PM, Glen Barber glen.j.bar...@gmail.com wrote:
I'm in the process of sync'ing up my system with source . . . but, in the
meantime I'm wondering about the choice of Broadcom driver. Is it really
a
matter of trying different ones?
It was for me. It took me 3
Neal Hogan wrote:
Well, it took me all day, but I did synch-up the source with the kernel.
However, being new to the ways of fBSD I (accidentally) ended up
building the -CURRENT source and kernel (8.0). I tried ndisgen on the
latest driver and it didn't work . . . I'll tell you why in a
:
---
panic: free: guard1 fail @ 0x6e104 from
/usr/src/sys/boot/i386/loader/../../common/module.c:959
-- Press a key on the console to reboot --
How do i recover the system from this error. I can't reload
Hi there,
I changed the following file of FreeBSD 7.0:
sys/boot/forth/beastie.4th
variable rebootkey
variable mykey (added line)
I built and installed kernel, then i reboot the system, it gives me the
following error:
---
panic: free
,
Well, I never loaded into /boot/modules and at this point I've removed the
*bcmwl5-stuff* to begin again. Note that *kldload bcmwl5_sys.ko* output
that there was no such file. Below is some info as to what lead to the panic
(it's info I gave in response to another generous fellow on the list).
I have
to the panic
(it's info I gave in response to another generous fellow on the list).
Just use `kldload bcmwl5_sys` without the `.ko' at the end.
I have not formally sync'd the system and source. But what I did prior to
the panicking was freshly install 7.0-RELEASE from disc, did not add any
bcmwl5_sys.ko* output
that there was no such file. Below is some info as to what lead to the
panic
(it's info I gave in response to another generous fellow on the list).
Just use `kldload bcmwl5_sys` without the `.ko' at the end.
I have not formally sync'd the system and source. But what I did
I'm in the process of sync'ing up my system with source . . . but, in the
meantime I'm wondering about the choice of Broadcom driver. Is it really a
matter of trying different ones?
It was for me. It took me 3 tries before I found one that 'worked'.
I updated the driver this morning to a
I'm father new to fBSD. I hope this is the appropriate list to send this
question to.
I just installed 7.1-RELEASE on my HP pavilion and attempted to configure my
Broadcom wlan card (BCM94309 version 4.10.40.0) using ndisgen. I cp'd the
bcmwl5_sys.ko to /boot/kernel and added
On 1/8/09, Neal Hogan nealho...@gmail.com wrote:
I'm father new to fBSD. I hope this is the appropriate list to send this
question to.
I just installed 7.1-RELEASE on my HP pavilion and attempted to configure my
Broadcom wlan card (BCM94309 version 4.10.40.0) using ndisgen. I cp'd the
On Thu, Jan 8, 2009 at 3:10 PM, Paul B. Mahol one...@gmail.com wrote:
On 1/8/09, Neal Hogan nealho...@gmail.com wrote:
I'm father new to fBSD. I hope this is the appropriate list to send this
question to.
I just installed 7.1-RELEASE on my HP pavilion and attempted to configure
my
On Thu, Jan 8, 2009 at 11:37 AM, Neal Hogan nealho...@gmail.com wrote:
I'm father new to fBSD. I hope this is the appropriate list to send this
question to.
I just installed 7.1-RELEASE on my HP pavilion and attempted to configure my
Broadcom wlan card (BCM94309 version 4.10.40.0) using
On 1/8/09, Neal Hogan nealho...@gmail.com wrote:
On Thu, Jan 8, 2009 at 3:10 PM, Paul B. Mahol one...@gmail.com wrote:
On 1/8/09, Neal Hogan nealho...@gmail.com wrote:
I'm father new to fBSD. I hope this is the appropriate list to send this
question to.
I just installed 7.1-RELEASE on
On Thu, Jan 8, 2009 at 3:37 PM, Glen Barber glen.j.bar...@gmail.com wrote:
On Thu, Jan 8, 2009 at 11:37 AM, Neal Hogan nealho...@gmail.com wrote:
I'm father new to fBSD. I hope this is the appropriate list to send this
question to.
I just installed 7.1-RELEASE on my HP pavilion and
On Thu, Jan 8, 2009 at 4:59 PM, Neal Hogan nealho...@gmail.com wrote:
On Thu, Jan 8, 2009 at 3:37 PM, Glen Barber glen.j.bar...@gmail.com wrote:
On Thu, Jan 8, 2009 at 11:37 AM, Neal Hogan nealho...@gmail.com wrote:
I'm father new to fBSD. I hope this is the appropriate list to send this
On Thu, Jan 8, 2009 at 5:20 PM, Glen Barber glen.j.bar...@gmail.com wrote:
On Thu, Jan 8, 2009 at 4:59 PM, Neal Hogan nealho...@gmail.com wrote:
On Thu, Jan 8, 2009 at 3:37 PM, Glen Barber glen.j.bar...@gmail.com wrote:
On Thu, Jan 8, 2009 at 11:37 AM, Neal Hogan nealho...@gmail.com wrote:
Update of kernel panic.
Rebuilt kernel without 80211node, seems to have cured the panics.
Removed all wireless support for now.
Thanks to Toni Schmidbauer
--- On Thu, 1/1/09, Mark Busby redt...@sbcglobal.net wrote:
From: Mark Busby redt...@sbcglobal.net
Subject: kernel panic
To: help help
At Thu, 1 Jan 2009 12:05:25 -0800 (PST),
Mark Busby wrote:
Jan 1 08:56:39 mars savecore: reboot after panic: kmem_malloc(12288):
kmem_map too small: 128778240 total allocated
as you probably already know this means you ran out of kernel memory.
80211node 8081 21705K - 8081
I've had a few panics. Attached are the output from vmsat -m then -z.
uname -a
FreeBSD mars.sbcglobal.net 7.0-RELEASE-p5 FreeBSD 7.0-RELEASE-p5 #0: Mon Nov 24
23:03:01 CST 2008 box...@mars.sbcglobal.net:/usr/src/sys/i386/compile/MARS
i386
Jan 1 08:56:39 mars savecore: reboot after panic
can someone explain to me, please, why i get a kernel panic on boot w/ the
latest 7.1 when i have something plugged into a usb port?
thx.
david coder
network engineer emeritus
verio/ntt
___
freebsd-questions@freebsd.org mailing list
http
Anyone that can help, I would appreciate it a lot.
I have a Dell 1950 1U server running FreeBSD 6.3. It's connected to 2.5tb
of RAID 6 storage via Fibre Channel. I have setup some 2 tb slices on this
array, the problem one being /dev/da0p1. It is throwing errors to the
console when people touch
On Mon, Nov 10, 2008 at 01:44:58PM -0600, Trevor Hearn wrote:
Anyone that can help, I would appreciate it a lot.
I have a Dell 1950 1U server running FreeBSD 6.3. It's connected to 2.5tb
of RAID 6 storage via Fibre Channel. I have setup some 2 tb slices on this
How does one fit more than
Hello all, I keep getting a kernel panic every Saturday night, so I
figured I would go through the core dump.
# uname -a
FreeBSD xx.fsklaw.com 7.0-RELEASE FreeBSD 7.0-RELEASE #1: Wed Apr 23
08:01:10 PDT 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/TEST amd64
# kgdb kernel.symbols /var
sorry, /usr/local/sbin/setkey failed on parsing that specific add, not
panic. no specific info, just say parse failed. maybe something is
not supported ...?
On Thu, Oct 9, 2008 at 8:46 AM, alan yang [EMAIL PROTECTED] wrote:
i wonder people ran into similar issue on setkey with freebsd7
i wonder people ran into similar issue on setkey with freebsd7 that
panic at ~/crypto/sha1.c:263 within sha1_result()
digest[0] = ctxt-h.b8[3]; digest[1] = ctxt-h.b8[2];
on the following sadb add with setkey:
add 192.168.0.101 192.168.0.110 esp-old 0x10001 -m any -E des-cbc
12345678 -A keyed
Thanks, that took care of it.
On Wed, Oct 1, 2008 at 4:49 PM, Manolis Kiagias [EMAIL PROTECTED] wrote:
Walter Venable wrote:
Our box, without readily obvious provocation, started doing this today:
Panic: softdep_setup_inomapdep: dependency for new inode already exists.
cpuid: 0
physical
Hi.
On Thu, Oct 09, 2008 at 08:46:32AM -0700, alan yang wrote:
i wonder people ran into similar issue on setkey with freebsd7 that
panic at ~/crypto/sha1.c:263 within sha1_result()
digest[0] = ctxt-h.b8[3]; digest[1] = ctxt-h.b8[2];
on the following sadb add with setkey:
add
, VANHULLEBUS Yvan [EMAIL PROTECTED] wrote:
Hi.
On Thu, Oct 09, 2008 at 08:46:32AM -0700, alan yang wrote:
i wonder people ran into similar issue on setkey with freebsd7 that
panic at ~/crypto/sha1.c:263 within sha1_result()
digest[0] = ctxt-h.b8[3]; digest[1] = ctxt-h.b8[2];
on the following sadb
Our box, without readily obvious provocation, started doing this today:
Panic: softdep_setup_inomapdep: dependency for new inode already exists.
cpuid: 0
physical memory: 1971 MB
dumping 78MB: 63 47 31 15
The system then immediately reboots, and hits the panic, reboots, etc.
What can I do
Walter Venable wrote:
Our box, without readily obvious provocation, started doing this today:
Panic: softdep_setup_inomapdep: dependency for new inode already exists.
cpuid: 0
physical memory: 1971 MB
dumping 78MB: 63 47 31 15
The system then immediately reboots, and hits the panic, reboots
101 - 200 of 1036 matches
Mail list logo
