On 14/06/2013 23:33, Ewald Jenisch wrote:
On Fri, Jun 07, 2013 at 10:41:01AM +0930, Shane Ambler wrote:
Just guessing from what I see -
The panic is "No usable event timer found!"
I did say just guessing and thought someone more knowledgeable may have
spoken by now. One thing I did find - the
On Fri, Jun 07, 2013 at 10:41:01AM +0930, Shane Ambler wrote:
> Just guessing from what I see -
>
> The panic is "No usable event timer found!"
>
> .
Hi Shane,
Thanks much for the hints you sent me. Since I'm pretty swamped with
work it took me a couple of days before I could go on with my
On 06/06/2013 23:41, Ewald Jenisch wrote:
Here's what I tried so far:
o) Updating BIOS, array-controller, iLO to the latest version
o) Booting the installation DVD in safe-mode
o) Booting the installatino DVD verbose mode
o) Escaping to the loader prompt, entering
kern.eventtimer.perio
On Sun, Aug 12, 2012 at 1:29 PM, Dennis Glatting wrote:
> Looks like my screen shot was stripped. You can find it here:
>
> http://www.pki2.com/hp.JPG
>
>
> Also:
>
> Granny> cc -v
> Using built-in specs.
> Target: amd64-undermydesk-freebsd
> Configured with: FreeBSD/amd64 system compiler
> Thread
Looks like my screen shot was stripped. You can find it here:
http://www.pki2.com/hp.JPG
Also:
Granny> cc -v
Using built-in specs.
Target: amd64-undermydesk-freebsd
Configured with: FreeBSD/amd64 system compiler
Thread model: posix
gcc version 4.2.1 20070831 patched [FreeBSD]
On Sun, 2012-08
Looks like my screen shot was stripped. You can find it here:
http://www.pki2.com/hp.JPG
Also:
Granny> cc -v
Using built-in specs.
Target: amd64-undermydesk-freebsd
Configured with: FreeBSD/amd64 system compiler
Thread model: posix
gcc version 4.2.1 20070831 patched [FreeBSD]
On Sun, 2012-08
On 08/27/10 03:12, Tijl Coosemans wrote:
On Thursday 26 August 2010 05:55:42 Rem P Roberti wrote:
In an attempt to diagnose why my Thinkpad R51 completely locks up when
trying to access X I have done the following. I built a debugging
kernel, with KDB, DDB, WITNESS, INVARIANT*, AND DIAGNOSTIC
On Thursday 26 August 2010 05:55:42 Rem P Roberti wrote:
> In an attempt to diagnose why my Thinkpad R51 completely locks up when
> trying to access X I have done the following. I built a debugging
> kernel, with KDB, DDB, WITNESS, INVARIANT*, AND DIAGNOSTIC in addition
> to *BREAK_TO_DEBUGGER. N
In an attempt to diagnose why my Thinkpad R51 completely locks up
when trying to access X I have done the following. I built a
debugging kernel, with KDB, DDB, WITNESS, INVARIANT*, AND DIAGNOSTIC
in addition to *BREAK_TO_DEBUGGER. None of these things have yielded
any progress in isolating
On Mon, Mar 22, 2010 at 9:28 AM, Paul Halliday wrote:
> I have a couple VM's that randomly halt with this error:
>
> Sleeping thread (tid 10018, pid 1058) owns a non-sleepable lock
> panic: sleeping thread
> cpuid = 0
> Uptime 11h14m31s
> Cannot dump. Device not defined or unavailable.
>
> FreeBSD
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
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.
On Mon, Nov 16, 2009 at 11:28:44PM -0500, Glen Barber wrote:
> Hi Gary,
>
> On Mon, Nov 16, 2009 at 10:28 PM, Gary Kline wrote:
> > 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 wrote:
> >> >
> >> > something pan
Hi Gary,
On Mon, Nov 16, 2009 at 10:28 PM, Gary Kline wrote:
> 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 wrote:
>> >
>> > something panicked my dell. more than twice. i have loaded, the
>> > i386 7.2-R Dvd
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 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[
Hi
On Mon, Nov 16, 2009 at 5:58 PM, Gary Kline 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 ?
>
> then something ab
On Wed, September 23, 2009 21:07, Adam Vande More wrote:
> On Wed, Sep 23, 2009 at 6:35 PM, Doug Poland wrote:
>
>> Hello,
>>
>> I've got a 7.2-RELEASE (i386) box that has recently experienced
>> several panics when writing to a gjournaled partition. On this
>> particular partition, the journal
On Wed, Sep 23, 2009 at 6:35 PM, Doug Poland wrote:
> Hello,
>
> I've got a 7.2-RELEASE (i386) box that has recently experienced
> several panics when writing to a gjournaled partition. On this
> particular partition, the journal device is "mixed" in with the data
> provider. In both cases, I w
What modules are loaded from loader.conf?
I had two distinct issues on one machine that were entirely due to
module loading. One was sound, using snd_driver instead of a specific
sound driver caused the machine to reboot. The other issue was
nvidia. The binary nvidia driver caused an instant
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Meaghan Hayes wrote:
> When I try to boot FreeBSD, it cycles through all of my hardware etc.
> as with a regular boot then says:
>
> panic: ohci_add_done: addr 0x7fef16d0 not found
>
> and tells me that it's rebooting, and just keeps doing this.
>
>
Michael Grant wrote:
On Tue, Jul 15, 2008 at 10:44 PM, Kris Kennaway <[EMAIL PROTECTED]> wrote:
Michael Grant wrote:
I have been having panics on one of my machines, roughly every week or
so. I was running 6.3 pre-release and then I updated to 6.3 p2 and I
still have the panic, here's the mess
On Tue, Jul 15, 2008 at 10:44 PM, Kris Kennaway <[EMAIL PROTECTED]> wrote:
> Michael Grant wrote:
>>
>> I have been having panics on one of my machines, roughly every week or
>> so. I was running 6.3 pre-release and then I updated to 6.3 p2 and I
>> still have the panic, here's the message that ap
On Tuesday 15 July 2008, Kris Kennaway wrote:
> Mike Clarke wrote:
> > I'm getting frequent panics due to spin lock held too long when
> > booting my recently built 6.3 system with an Athlon 4850e dual core
> > processor on a Foxconn 6150M2MA motherboard (GeForce 6150 and
> > nForce 430 chipsets).
David Gurvich wrote:
Can you disable smp? I see reports on the same issue with 6.3 that
imply it may be related to smp.
You are spreading FUD :-) There is no information provided upon which
to base that conclusion.
Kris
___
freebsd-questions@free
Can you disable smp? I see reports on the same issue with 6.3 that
imply it may be related to smp.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTE
Michael Grant wrote:
I have been having panics on one of my machines, roughly every week or
so. I was running 6.3 pre-release and then I updated to 6.3 p2 and I
still have the panic, here's the message that appears on the console:
panic: kmem_kernel trap 12 with interrupts disabled
Fatal trap
Mike Clarke wrote:
On Tuesday 15 July 2008, Kris Kennaway wrote:
Mike Clarke wrote:
I'm getting frequent panics due to spin lock held too long when
booting my recently built 6.3 system with an Athlon 4850e dual core
processor on a Foxconn 6150M2MA motherboard (GeForce 6150 and
nForce 430 chips
On Tuesday 15 July 2008, Kris Kennaway wrote:
> Mike Clarke wrote:
> > I'm getting frequent panics due to spin lock held too long when
> > booting my recently built 6.3 system with an Athlon 4850e dual core
> > processor on a Foxconn 6150M2MA motherboard (GeForce 6150 and
> > nForce 430 chipsets).
Mike Clarke wrote:
I'm getting frequent panics due to spin lock held too long when booting
my recently built 6.3 system with an Athlon 4850e dual core processor
on a Foxconn 6150M2MA motherboard (GeForce 6150 and nForce 430
chipsets).
FreeBSD curlew.lan 6.3-STABLE FreeBSD 6.3-STABLE #2: Sat J
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Mel and all,
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.8 (Darwin)
iEYEARECAAYFAkh2CcUACgkQvVxKL9VSxXr6rgCgmK63mJx8GlFmsKELMnZ8EtZ6
/BQAoIW/3f7dt+bxjZnBy38V75Irv/Tc
=mPiu
-END PGP SIGNATURE-
2008/7/10 Mel <[EMAIL PROTECTED]>:
> Pro
On Thursday 10 July 2008 08:09:38 Horus Lee wrote:
> Hey all FreeBSD folks,
>
> I bought myself a new PC:
> AMD Athlon 64 X2 5000+ Black Edition
> Jetway HA06
> (http://www.jetway.com.tw/jw/motherboard_view.asp?productid=481&proname=HA0
>6, Integrated USB)
> Kingston DDR2 800 1GB * 2
>
> I want to
On Monday 12 May 2008 15:16:48 Aminuddin Abdullah wrote:
> I have 5 servers running almost at 70mbit/sec and each one of them will
> crash/reboot after more than 24 hours. The most it can stay up is 48 hours.
>
> How do I increase this memory from the default 320MB?
After some digging it looks li
On 3/7/08, Stacey Roberts <[EMAIL PROTECTED]> wrote:
> Hi Bob,
> Thanks for the response..,
>
> On Fri, 07 Mar 2008, Bob Johnson wrote:
>
> > On 3/7/08, Stacey Roberts <[EMAIL PROTECTED]> wrote:
[...]
> > Yep. The HP BIOS is a bit bogus. It won't reveal memory information to
> > the AMD64 boot code
Hi Bob,
Thanks for the response..,
On Fri, 07 Mar 2008, Bob Johnson wrote:
> On 3/7/08, Stacey Roberts <[EMAIL PROTECTED]> wrote:
> > Hello,
> > Is anyone aware if this issue is fixed in FreeBSD 7.0-RELEASE / STABLE?
> >
>
> It is NOT fixed in -RELEASE and I doubt it is fixed in -STABLE.
>
On 3/7/08, Stacey Roberts <[EMAIL PROTECTED]> wrote:
> Hello,
> Is anyone aware if this issue is fixed in FreeBSD 7.0-RELEASE / STABLE?
>
It is NOT fixed in -RELEASE and I doubt it is fixed in -STABLE.
> I've been trying to get FreeBSD-7 amd64 installed on an HP dc7700p
> workstation
> at work, b
On Thu, Feb 28, 2008 at 03:16:35PM +, Pedro Almeida wrote:
> I upgraded my system from 6.2 to 7.0 using cvsup.
> I'm using ULE and device polling. After doing make installworld and reboot,
> the system
> don't boot anymore. I have some variables in make.conf, but I don't know if
> this the ca
Pedro Almeida wrote:
I upgraded my system from 6.2 to 7.0 using cvsup.
I'm using ULE and device polling. After doing make installworld and
reboot, the system
don't boot anymore. I have some variables in make.conf, but I don't know
if this the cause of the problem.
CPUTYPE?=p3
CFLAGS= -O2 -pipe
Michael Lednev wrote:
Hello, Kris.
On 2 ?? 2008 ?., 14:07:36 you wrote:
KK> Yes, long-standing issue with unexpected mounted device removal. Don't
KK> do that :)
Thanks, already found this PR, it's already 5 yo, wow :)
There have been some recent partial workarounds committed in curren
Hello, Kris.
On 2 ?? 2008 ?., 14:07:36 you wrote:
KK> Yes, long-standing issue with unexpected mounted device removal. Don't
KK> do that :)
Thanks, already found this PR, it's already 5 yo, wow :)
--
Best regards,
Michael mailto:[EMAIL PROTECTED]
___
Michael Lednev wrote:
Hello, freebsd-questions.
After the following actions:
1. Insert USB Flash
2. mount_msdosfs /dev/da0s1 /mnt
3. Remove USB Flash
4. umount -f /mnt
I have kernel panic every time. Is this a known issue? My system is
FreeBSD 7.0-RC1 from 1.01.2008.
Yes, long-standing issue
On Dec 16, 2007, at 7:58 AM, Derek Ragona wrote:
At 07:32 PM 12/15/2007, jekillen wrote:
On Dec 15, 2007, at 5:21 PM, jekillen wrote:
Hello;
I have had an AMD64 754 system that I have 64 bit SCSI card and
two 15k rpm SCSI drives. It has been running fine with FreeBSD v 6.0
for about two yea
At 07:32 PM 12/15/2007, jekillen wrote:
On Dec 15, 2007, at 5:21 PM, jekillen wrote:
Hello;
I have had an AMD64 754 system that I have 64 bit SCSI card and
two 15k rpm SCSI drives. It has been running fine with FreeBSD v 6.0
for about two years now. I have several things I wanted to change
and
On Dec 15, 2007, at 5:21 PM, jekillen wrote:
Hello;
I have had an AMD64 754 system that I have 64 bit SCSI card and
two 15k rpm SCSI drives. It has been running fine with FreeBSD v 6.0
for about two years now. I have several things I wanted to change
and reconfigure, software wise, and hardware
On Jun 4, 2007, at 10:49 AM, Scott Willson wrote:
On May 29, 2007, at 4:26 PM, Kris Kennaway wrote:
On Tue, May 29, 2007 at 03:36:49PM -0700, Scott Willson wrote:
I am seeing hard (often no core dump) crashes on a new AMD64 box
running 6.2 RELEASE. When I try to rsync 10+ GB of backup files
Richard Puga wrote:
I have been installing FreeBSD 6.2 on IBM XSeries servers some of which
I need to run external USB drives.
While backing up to a USB hard drive at random times the computer locks
up or reboots with some, but not all of the systems.
The XP3100's work fine and dmesg shows a
On Wed, Jul 25, 2007 at 01:55:45PM +0800, Zhang hw wrote:
> Sometimes when I shutdown my system, it would tell me :
> "...
> All buffers synced
> Swap_pager: I/O error - pagein failed, blkno 744, size 4096, error 5
> panic: swap_pager_force_pagein: read from swap failed
> Uptime:...
#define EIO
Hi,
Cannot dump. No dump device defined.
At least I know what this means. If you don't define a dump device, the
swapper can't dump the corrupted swap data anywhere so you can analyse
it later. Rather than explain here I recommend you, and everyone else in
fact, read and digest these tutori
On May 29, 2007, at 4:26 PM, Kris Kennaway wrote:
On Tue, May 29, 2007 at 03:36:49PM -0700, Scott Willson wrote:
I am seeing hard (often no core dump) crashes on a new AMD64 box
running 6.2 RELEASE. When I try to rsync 10+ GB of backup files to
the new box, I can reliably crash it after about
On May 29, 2007, at 4:26 PM, Kris Kennaway wrote:
On Tue, May 29, 2007 at 03:36:49PM -0700, Scott Willson wrote:
I am seeing hard (often no core dump) crashes on a new AMD64 box
running 6.2 RELEASE. When I try to rsync 10+ GB of backup files to
the new box, I can reliably crash it after about
On Tue, May 29, 2007 at 03:36:49PM -0700, Scott Willson wrote:
> I am seeing hard (often no core dump) crashes on a new AMD64 box
> running 6.2 RELEASE. When I try to rsync 10+ GB of backup files to
> the new box, I can reliably crash it after about 20 minutes; often
> quicker if I do somethi
- Original Message
From: Lowell Gilbert <[EMAIL PROTECTED]>
To: Drew Jenkins <[EMAIL PROTECTED]>
Sent: Monday, February 19, 2007 12:00:54 PM
Subject: Re: Panic and Dump
>The filesystem clearly needs a good fsck. Remember that it can't be
>mounted read-write t
Never mind, turned out to be dodgy RAM.
--
Juha
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
From what I can tell, the function dflt_lock is only called if the dma
driver doesn't have a lock. This causes a panic (see busdma_machdep.c line
190). Can you provide the call stack?
Thanks,
Corey
On 8/25/06, Karim Nogas <[EMAIL PROTECTED]> wrote:
Hello,
I was wondering if someone could e
On Sun, May 14, 2006 at 11:35:01PM -0700, Malachi de ?lfweald wrote:
> Has anyone found a solution to the problem reported here:
> http://marc2.theaimsgroup.com/?l=freebsd-amd64&m=111219607318603&w=2
>
> >From what I can tell, unionfs is compiled into my kernel (said YES in the
> kernel config fil
At 09:14 AM 5/5/2006, you wrote:
Hello,
We have a group of web and mail servers that run under a moderate
load. We recently upgraded them from 4/5.x to 6.0. While we
thought we had done enough testing, apparently we hadn't and are now
experiencing panic's on a number of the servers. Some o
On Sun, May 07, 2006 at 06:24:52PM -0400, Robert H. Perry wrote:
> Thanks for taking the time to respond. Not good news obviously, but could
> be worse. This is my mule machine. I was using it as a gateway, to develop
> some networking skills, and had installed SAMBA and was also trying to
> ins
-Original Message-
From: Kris Kennaway [mailto:[EMAIL PROTECTED]
Sent: Sunday, May 07, 2006 3:20 PM
To: Robert H. Perry
Cc: freebsd-questions@freebsd.org
Subject: Re: Panic: vrele: negative ref cnt
On Sun, May 07, 2006 at 03:16:46PM -0400, Robert H. Perry wrote:
> I received a pa
On Sun, May 07, 2006 at 03:16:46PM -0400, Robert H. Perry wrote:
> I received a panic message (see Subject) yesterday following a GNOME
> upgrade. The upgrade was successful but I encountered subsequent problems
> trying to access Firefox websites and my mail site in Thunderbird. I
> noticed a Pl
On Fri, May 05, 2006 at 09:14:04AM -0600, Nick Wood wrote:
> Hello,
>
> We have a group of web and mail servers that run under a moderate
> load. We recently upgraded them from 4/5.x to 6.0. While we thought
> we had done enough testing, apparently we hadn't and are now
> experiencing panic's
On Sun, 9 Apr 2006, fbsd_user wrote:
Here is the standard causes.
I all most all cases this is a hardware problem.
Yes, this I suspected.
Motherboard is overheating because of years of accumulated dust.
Open box and use small paint brush to blow away dust on motherboard
chips.
Remove heat
Here is the standard causes.
I all most all cases this is a hardware problem.
Motherboard is overheating because of years of accumulated dust.
Open box and use small paint brush to blow away dust on motherboard
chips.
Remove heat sink on CPU and clean out chocking dust and reinstall.
Power supply
Heinrich Rebehn wrote:
Hi list,
i wanted to try out 64 bit support on my ASUS A8V Deluxe with
AMD Athlon(tm) 64 X2 Dual Core Processor 3800+
I downloaded 6.1-BETA4-amd64-disc1.iso from the FreeBSD ftp site, burned
a disc an booted from it.
However, it failed:
Waiting 5 seconds for SCSI dev
ery clear to me: can you transcribe EXACTLY what appears
on your screen, or provide a screen shot?
Also, don't top-post.
Kris
> -Original Message-
> From: Anish Mistry [mailto:[EMAIL PROTECTED]
> Sent: Monday, April 03, 2006 11:51 AM
> To: freebsd-questions@freebsd.org
> C
day, April 03, 2006 11:51 AM
To: freebsd-questions@freebsd.org
Cc: Wil Hatfield
Subject: Re: Panic Reboots
On Monday 03 April 2006 12:36, Wil Hatfield wrote:
> Well that didn't work. My Fatal Trap 12 just sits there until we
> get it plugged in and run a couple of fsck on it.
>
> S
On Monday 03 April 2006 12:36, Wil Hatfield wrote:
> Well that didn't work. My Fatal Trap 12 just sits there until we
> get it plugged in and run a couple of fsck on it.
>
> So why doesn't 5.4 reboot on panics? And is this also an issue
> with 6.x?
Does it sit at a db> prompt?
I normally have debu
Well that didn't work. My Fatal Trap 12 just sits there until we get it
plugged in and run a couple of fsck on it.
So why doesn't 5.4 reboot on panics? And is this also an issue with 6.x?
--
Wil Hatfield
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Wi
On Wed, Mar 29, 2006 at 11:15:53AM +0200, Helge Sandring wrote:
> > > what does that mean? the server ran without problems for 530+ days now
> > > suddenly this?
> >
> > Your hardware is failing?
> >
> > Kris
>
> Well, none of the log files shows any error indication ... the box runs and
> sudd
Helge Sandring <[EMAIL PROTECTED]> wrote:
> > -Original Message-
> > From: Kris Kennaway [mailto:[EMAIL PROTECTED]
> > Sent: Wednesday, March 29, 2006 2:12 AM
> > To: Helge Sandring
> > Cc: freebsd-questions@freebsd.org
> > Subject: Re: panic on 4.
> -Original Message-
> From: Kris Kennaway [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, March 29, 2006 2:12 AM
> To: Helge Sandring
> Cc: freebsd-questions@freebsd.org
> Subject: Re: panic on 4.10R
>
> On Tue, Mar 28, 2006 at 01:19:02PM +0200, Helge Sandr
On Tue, Mar 28, 2006 at 01:19:02PM +0200, Helge Sandring wrote:
> Dear list,
>
> for a few days i have every morning when I get up the following message on
> the console of my server:
>
> ===
>
> Syncing discs
>
> Fatal Tra
On Wed, Mar 22, 2006 at 02:29:38PM -0300, Guilherme wrote:
> Hello all, I have two freebsd servers workiing as
> email servers. Two days ago I got some crashes in the
> server and the error shown in the screen was:
>
> PANIC: SBFLUSH_LOCKER : cc 0 :: mb 0xc22be000 :: mbcnt
> 512
>
> and
>
> PANI
Kris,
The rule of thumb is that user code should not cause kernel panics.
Good to know, thanks.
But all software has bugs, of course.
Understood. This is just the first bug I've personally hit in FreeBSD in
4 years of use. /me weeps for his lost innocence
Is it likely that known umoun
On Mon, Mar 06, 2006 at 04:34:06PM -0500, Chad Whitacre wrote:
> Kris,
>
> > A number of problems with umount are due to be fixed in 6.1 ...
>
> Wow, ok. Thanks for the heads-up. That's honestly a little disappointing
> to hear. I had hoped it was a problem with my backup script.
The rule of th
Kris,
> A number of problems with umount are due to be fixed in 6.1 ...
Wow, ok. Thanks for the heads-up. That's honestly a little disappointing
to hear. I had hoped it was a problem with my backup script.
I posted a fuller description of this and another problem last week.
Here's the archiv
On Mon, Mar 06, 2006 at 04:00:45PM -0500, Chad Whitacre wrote:
> Kris,
>
> Thanks for the reply.
>
> > What version of FreeBSD?
>
> [EMAIL PROTECTED] uname -a
> FreeBSD www2.svsd.net 6.0-RELEASE FreeBSD 6.0-RELEASE #0: Thu Nov 3
> 09:36:13 UTC 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GE
Kris,
Thanks for the reply.
> What version of FreeBSD?
[EMAIL PROTECTED] uname -a
FreeBSD www2.svsd.net 6.0-RELEASE FreeBSD 6.0-RELEASE #0: Thu Nov 3
09:36:13 UTC 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC
i386
[EMAIL PROTECTED]
chad
Kris Kennaway wrote:
On Mon, Mar 06,
On Mon, Mar 06, 2006 at 09:32:50AM -0500, Chad Whitacre wrote:
> Dear All,
>
> Can anyone tell me what this error message means?
>
> Panic: unmount: dangling vnode
What version of FreeBSD?
Kris
> I believe it is caused by this script:
>
> #!/bin/sh
>
> /sbin/mount /backup/
> /usr/loc
] On Behalf Of Tamouh H.
Sent: January 21, 2006 4:18 PM
To: freebsd-questions@freebsd.org
Subject: RE: panic on 5.4 SMP kernel when jailed apache is used heavily
>
> Hi all,
>
>
>
> I upgraded a 5.3 system to 5.4 both with SMP kernels, I'm
> running 6 jails on a dual xe
>
> Hi all,
>
>
>
> I upgraded a 5.3 system to 5.4 both with SMP kernels, I'm
> running 6 jails on a dual xeon 1.26 hp rackmount. When apache
> (both 1.3 and 2.0) is being used heavily the system panics.
> With a 5.4 GENERIC kernel or a 5.3 SMP kernel this behaviour
> does not happen and the system
Neat thing ... its doing after ~8 hours of uptime ... I can't seem to trap
the error each time, this one was by a fluke, but suspect it is the same
each time ...
On Mon, 28 Nov 2005, Kris Kennaway wrote:
On Mon, Nov 28, 2005 at 06:16:38AM -0400, Marc G. Fournier wrote:
Is there any way of
On Mon, 28 Nov 2005, Kris Kennaway wrote:
On Mon, Nov 28, 2005 at 06:16:38AM -0400, Marc G. Fournier wrote:
Is there any way of determining *what* is causing this, based on the
information that I'm getting on the console? :(
dev=#da/0x20007, bno = 671547887, bsize = 16384, size = 16384, fs =
On Mon, Nov 28, 2005 at 06:16:38AM -0400, Marc G. Fournier wrote:
>
> Is there any way of determining *what* is causing this, based on the
> information that I'm getting on the console? :(
>
> dev=#da/0x20007, bno = 671547887, bsize = 16384, size = 16384, fs = /vm
> panic: ffs_blkfree: bad size
On 2005-11-24 19:44, "E.J Burritt" <[EMAIL PROTECTED]> wrote:
> Just wanted to drop a line and let you know that I fixed the issue. It
> was actually the IDE cable that was causing the problem. I followed
> the link Mike gave me and did try swapping IDE cables... it didn't
> help though. For the he
On Wed, Nov 23, 2005 at 11:38:49PM -0800, E.J Burritt wrote:
> Hey Mike, thanks for the reply. I went ahead and tried that link,
> but unfortunatley it didn't help. I also made a post over at the
> FreeBSD forums, but also no reply. Not sure what to do now...
For one thing, you omitted all context
On Mon, 2005-11-21 at 00:10 -0800, E.J Burritt wrote:
> Hi, I'm kind of a noob to BSD am having some configuration errors. I had my
> BSD running fine on an older pc, and have recently gotten a newer one. I
> want to use the same hd that was in my old box though insteading of
> reformatting f
On Friday 16 September 2005 19:25, Chuck Swiger wrote:
> > To get a crashdump I should have swapspace >= total ram.
> > Currently it is only 2G, I'm trying to think of smth. to get more
> > swapspace. dmesg is available @ http://getfile.biz/dmesg.txt
>
> Take a look at /boot/loader.conf, you can
Greetings!
On Friday 16 September 2005 19:25, Chuck Swiger wrote:
> Take a look at /boot/loader.conf, you can limit the amount of physical RAM
> FreeBSD uses to less than 2GB for long enough to get a valid dump, assuming
> the crash is easily reproducable.
Will look into it...
Currently it is u
AK wrote:
Hello!
Hello.
On Friday 16 September 2005 18:40, Chuck Swiger wrote:
Please read "man crash" and the part of the handbook which talks about how
to obtain a crashdump or backtrace with more information about the panic
you see.
You might consider putting both a backtrace and a dmesg
Hello!
On Friday 16 September 2005 18:40, Chuck Swiger wrote:
> Please read "man crash" and the part of the handbook which talks about how
> to obtain a crashdump or backtrace with more information about the panic
> you see.
>
> You might consider putting both a backtrace and a dmesg from the sys
Please read "man crash" and the part of the handbook which talks about how to
obtain a crashdump or backtrace with more information about the panic you see.
You might consider putting both a backtrace and a dmesg from the system on the
web somewhere, and post links to that.
Alex wrote:
For s
On Wed, Aug 10, 2005 at 05:12:57AM -0700, Michael Louie Loria wrote:
> What's this message that I'm receiving
>
> panic: lockmgr: locking against myself
> Uptime: 1m31s
> Cannot dump: No dump device defined
> Automatic reboot in 15 seconds
> ~ - press a key on the consol to abort
>
>
> I was jus
Hi!
I managed to recover and am running 7-CURRENT now.
The morale of the story is
1.disable fancy drivers and scripts for binary compatibilites before
proceeding
2. Prepare a backup
3. READ UPDATING
4. use unload all when building and after rebooting with the new kernel.
Use GENERIC at first, t
Did as advised and reached to full booting system, which complained that
no dump devices were found, even when I had specified one in rc.conf.
Mergemaster grunts "cannot cd to /usr/src/etc and install files to
temproot", when booting in single mode and trying to update the files.
cap_mkdb quits
[EMAIL PROTECTED] wrote:
Hello all!
Yesterday I tried moving from RELENG_5 to RELENG_6 with a custom kernel.
Used cvsup for getting files.
Panic details follow at the end.
Here is what I did:
1. make clean in /usr/src
2. removed stale obj files.
3. commented out the NO_INFO and other knobs in /
NMH wrote:
Hello
I am having a odd problem I hope someone can help
with.
I have a TYAN 2882 board with 4 gigs of memory and a
single Opteron 248 Processor. I am using an Infortrend
RAID controller that won't play nice with Adaptec at
320 speeds so I am using an LSI 1030 based PCI-X SCSI
card inst
On Saturday 29 January 2005 13:41, Mike Hauber wrote:
> On Saturday 29 January 2005 08:15 am, Xian wrote:
> > I woke up this morning to find that my computer had rebooted
> > and panicked as soon as the kernel had started to run. it said:
> >
> > The rights of the University...
> > panic: vm_page_
On Saturday 29 January 2005 13:15, Xian wrote:
> I woke up this morning to find that my computer had rebooted and panicked
> as soon as the kernel had started to run. it said:
>
> The rights of the University...
> panic: vm_page_insert: alredy inserted
> uptime: 0s
>
> in bright white on the scree
On Saturday 29 January 2005 08:15 am, Xian wrote:
> I woke up this morning to find that my computer had rebooted
> and panicked as soon as the kernel had started to run. it said:
>
> The rights of the University...
> panic: vm_page_insert: alredy inserted
> uptime: 0s
>
> in bright white on the sc
Subhro wrote:
Is the ports tree up to date? IF not please do so and run portupgrade -au.
Your package list makes me feel that the port tree had been updated but only
partially. Also try avoiding fancy stuff like explicitly asking gnutella to
link with gtk2 using build time flags. Also if you are n
> On Mon, Nov 15, 2004 at 12:10:13AM -0500, kalin mintchev wrote:
>>
>> > On Sun, Nov 14, 2004 at 11:12:30PM -0500, kalin mintchev wrote:
>> >>
>> >> >
>> >> > Follow my advice then..
>> >>
>> >> about kernel debugging?!
>> >
>> > Not that specifically, but I told you three things to do in order,
1 - 100 of 143 matches
Mail list logo
