At 07:34 PM 8/6/2005, Jhih-Sing Chen wrote:
Hi all,
I'm using 4.11 version of FreeBSD and I have a problem with the /
partition disk usage.
Actually the / partition was 90% usage, but after reboot, it turned
into 31% usage.
Jschen# df -h
FilesystemSize Used Avail Capacity Mounted on
/de
Hi all,
I'm using 4.11 version of FreeBSD and I have a problem with the /
partition disk usage.
Actually the / partition was 90% usage, but after reboot, it turned
into 31% usage.
Jschen# df -h
FilesystemSize Used Avail Capacity Mounted on
/dev/da0s1a20G 5.6G13G31%/
/dev
dpk wrote:
> On Thu, 4 Aug 2005, Frank McConnell wrote:
>> Further debugging led me to the conclusion that the problem is in
>> pmap_protect(), in src/sys/i386/i386/pmap.c; and has to do with a
[...]
>> Then I checked the cvs logs, and saw rev 1.524, which looks like what
>> I was thinking about as
On Sat, 6 Aug 2005, J. T. Farmer wrote:
Kevin Oberman wrote:
I would suggest that it would have been better to post to current as
6.0 is not yet stable and most of the people who deal with problems are
much more likely to see problems reported there.
Ok, so I'm a bit confused. The answer
I upgraded to 6.0_BETA2 yesterday. Today I built a new kernel. While the
booting, the following error is displayed.
acd0: SETFEATURES SET TRANSFER MODE semaphore timout !! DANGER Will
Robinson !!
I recompiled the kernel without atapicd and the kernel boots fine. At some
later time, that
While compiling bash for my new 6.0-BETA2 system, I received this error:
ad4: detached
panic: vm_fault
I don't have a dump for you and I really must be going to work now. More
later if I can get myself trained up on crash dumps.
Later,
Jason C. Wells
On Thu, 4 Aug 2005, Frank McConnell wrote:
> Further debugging led me to the conclusion that the problem is in
> pmap_protect(), in src/sys/i386/i386/pmap.c; and has to do with a
> 32-bit-truncated pt_entry_t being passed to PHYS_TO_VM_PAGE().
> (pt_entry_t is 64 bits if the kernel is built with P
On Sat, Aug 06, 2005 at 08:40:32AM -0400, J. T. Farmer wrote:
> Kevin Oberman wrote:
>
> >I would suggest that it would have been better to post to current as 6.0
> >is not yet stable and most of the people who deal with problems are much
> >more likely to see problems reported there.
> >
> >
>
On 8/6/05, Joe Koberg <[EMAIL PROTECTED]> wrote:
> make.conf:
>
:
> CPUTYPE=nocona
>
Try building the loader without the CPUTYPE set, there were some
problems caused by this setting with the loader. There was someone
working on this problem on the -CURRENT, and possibly the -STABLE
tree. Not su
I have a Dell Poweredge SC1425 server. I am
running FreeBSD AMD64.
I have been running 5.3-R on this machine since
Feburary. I decided to go ahead and upgrade
to 5.4.
installkernel - OK
reboot - OK
mergemaster -p OK
installworld - OK
mergemaster - OK...
reboot again
CRASH... loader crashes wit
Kevin Oberman wrote:
I would suggest that it would have been better to post to current as 6.0
is not yet stable and most of the people who deal with problems are much
more likely to see problems reported there.
Ok, so I'm a bit confused. The answer given for the the DMA_WRITE and
DMA_READ
On Fri, 29 Jul 2005, snort Snort wrote:
As I want to learn how to use /dev/tap in freebsd, I m looking for a
simple application that written for /dev/tap. OpenVPN is a bit too
complicated for a newbie to get start. Can anyone tell me a link or
reference for some of these examples? Thanks Sam
On Fri, 29 Jul 2005, Robert Watson wrote:
On Fri, 29 Jul 2005, Alexander S. Usov wrote:
I got a few similar panics.
It looks that I managet to get rid of them by setting mpsafenet=0, but I
am not sure -- I have to monitor it for a bit longer.
I have managed to get a few dumps, so the traces ar
On Sat, 6 Aug 2005, Indigo 23 wrote:
Is this the last beta before release (assuming there are no show
stopping bugs)?
Normally release cycles consistent of a pre-release period, which includes
betas, release candidates, and releases. Betas usually continue until
substantal movement has ceas
On Fri, 5 Aug 2005, Marc G. Fournier wrote:
How/where should we be reporting such bugs? I reported a *very* easy to
reproduce hang situation with unionfs in BETA1 (and have
updated/retested as I see commits going through) over a week ago, and
the biggest 'interest' I got out of it was from R
Is this the last beta before release (assuming there are no show stopping
bugs)?
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
>
> From: Zoran Kolic <[EMAIL PROTECTED]>
> Date: 2005/08/06 Sat AM 12:39:31 EDT
> To: [EMAIL PROTECTED]
> CC: freebsd-stable@freebsd.org
> Subject: Re: "Shutdown -p now" not working in 5.4 STABLE
>
> Hi Mike!
> If you still manage this puzzle,
> is there something in your bios that
> affects 5.
17 matches
Mail list logo