On Mon, Oct 06, 2003 at 02:30:30AM -0700, Kris Kennaway wrote:
> I got this upon attempting to burn a CD with cdrecord on my
> freshly-updated current machine:
>
> panic: mutex vm object not owned at ../../../vm/vm_page.c:762
>
This should now be fixed.
Alan
> syncing disks, buffers remaining.
В вт, 07.10.2003, в 23:26, Soren Schmidt пишет:
> It seems Vladimir B. Grebenschikov wrote:
> > > Any solution or workaround ?
>
> Try this patch please:
>
> diff -u -r1.191 ata-all.c
Does not help, another panic in ad_attach:
...
GEOM: create disk ad1 dp=0xc2358a70
ad1: ATA-0 disk at ata1-mas
On Wed, Oct 08, 2003 at 02:16:52AM -0500, Alan Cox wrote:
> On Mon, Oct 06, 2003 at 02:30:30AM -0700, Kris Kennaway wrote:
> > I got this upon attempting to burn a CD with cdrecord on my
> > freshly-updated current machine:
> >
> > panic: mutex vm object not owned at ../../../vm/vm_page.c:762
> >
It seems Vladimir B. Grebenschikov wrote:
> Does not help, another panic in ad_attach:
ARGH, try this instead:
diff -u -r1.191 ata-all.c
--- ata-all.c 7 Oct 2003 13:44:15 - 1.191
+++ ata-all.c 8 Oct 2003 08:03:09 -
@@ -35,6 +35,7 @@
#include
#include
#include
+#include
Here are the contents of my /dev. As you can see, there are no entries
for the
partitions of ad3. My 5.0 system has no "bsdlabel" command. Can anyone
tell me how I can coax the ad3s1* entries into existence?
./ ad2s1c dspW0.1 pci
stdin@ ttypg
..
On Wed, 8 Oct 2003, ecsd wrote:
e>Here are the contents of my /dev. As you can see, there are no entries
e>for the
e>partitions of ad3. My 5.0 system has no "bsdlabel" command. Can anyone
e>tell me how I can coax the ad3s1* entries into existence?
You probably need to fdisk(8) your disk first. Th
I had already been able to go so far as to "disklabel -w -r ad3 auto".
After doing this
on a 4.X system I would then "disklabel -e /dev/ad3s1c", but /dev/ad3s1c
does
not exist, so I am stuck. Maybe there is a "rescan devices" command?
fdisk thinks it has no work to do:
*** Working on device
On Wed, 8 Oct 2003, ecsd wrote:
e>I had already been able to go so far as to "disklabel -w -r ad3 auto".
e>After doing this
e>on a 4.X system I would then "disklabel -e /dev/ad3s1c", but /dev/ad3s1c
e>does
e>not exist, so I am stuck. Maybe there is a "rescan devices" command?
e>
e>fdisk thinks it
On 2003/10/07 18:11:30, Doug White wrote:
> On Tue, 7 Oct 2003, YONETANI Tomokazu wrote:
>
> > The hardware is IBM NetFinity 6000R, and it has ServerWorks ROSB4 UDMA33
> > controller, to which the IDE disk is attached. The size of the IDE hard
> > disk is 4Gbytes, and the size of the kernel dump a
On Tue, 7 Oct 2003, Edward Aronyk wrote:
> Booting off the 5.1 boot floppies gives a page fault about 15 seconds
> after the mfsroot floppy finishes loading.
Boot off of a -CURRENT snapshot; 5.1 shipped with a broken IDA driver.
--
| Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/
Harti Brandt wrote:
On Wed, 8 Oct 2003, ecsd wrote:
e>I had already been able to go so far as to "disklabel -w -r ad3 auto".
e>After doing this on a 4.X system I would then "disklabel -e /dev/ad3s1c"
e>but /dev/ad3s1c does not exist, so I am stuck.
e>Maybe there is a "rescan devices" command?
e>
On Wed, 8 Oct 2003, ecsd wrote:
e>Harti Brandt wrote:
e>On Wed, 8 Oct 2003, ecsd wrote:
e>e>I had already been able to go so far as to "disklabel -w -r ad3 auto".
e>e>After doing this on a 4.X system I would then "disklabel -e /dev/ad3s1c"
e>e>but /dev/ad3s1c does not exist, so I am stuck.
e>e>May
TB --- 2003-10-08 09:25:40 - starting CURRENT tinderbox run for ia64/ia64
TB --- 2003-10-08 09:25:40 - checking out the source tree
TB --- cd /home/des/tinderbox/CURRENT/ia64/ia64
TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src
TB --- 2003-10-08 09:29:09 - building world
TB --- cd /home
Given that FreeBSD 5.1 is on the shelf in a box at CompUSA for sale to the
general public, I think the proper thing to do is address the matter of
documenting the revised operation of the devices in 5.X, rather than tell
people to downgrade if they don't understand the behavior of their system,
bes
On Wed, 8 Oct 2003, ecsd wrote:
e>Given that FreeBSD 5.1 is on the shelf in a box at CompUSA for sale to the
e>general public, I think the proper thing to do is address the matter of
e>documenting the revised operation of the devices in 5.X, rather than tell
e>people to downgrade if they don't und
If you read the early adopters doc at:
http://www.freebsd.org/releases/5.1R/early-adopter.html
You will se it clearly says:
"MAKEDEV is no longer available, nor is it required. FreeBSD 5.X uses a
device filesystem, which automatically creates device nodes on demand. For
more information, please
Derek Ragona wrote:
If you read the early adopters doc at:
http://www.freebsd.org/releases/5.1R/early-adopter.html
You will se it clearly says:
"MAKEDEV is no longer available, nor is it required. FreeBSD 5.X uses a
device filesystem, which automatically creates device nodes on demand. For
mor
Hello, everyone!
I've got a [uniprocessor 5.1-RELEASE] router machine with fxp and em nics.
I've built my kernel with the following included:
options DEVICE_POLLING
options HZ=2500
and enabled polling in /etc/sysctl.conf.
Having looked through a vmstat -i output I see
that the e
That is because there is no driver for that specific hardware. If
FreeBSD supports them, you need to recompile kernel with appropriate
drivers or dynamically load them. As for the unsupported devices, (like
winmodems), you can't help it.
-- Babak Farrokhi
Dikshie wrote:
why my dmesg always sh
Hiya
> I read that too. That appears to be just about all the information about
> the new devfs that there is,
> short of reading the source code.
If you look in /usr/share/doc (or someplace like that) there's a document
describing the rationale behind devfs and its implementation - it's geared
On Wed, Oct 08, 2003 at 03:59:40AM +0100, Stuart Walsh wrote:
> Aww crap, my apologies for the duplicate email.. sendmail appears to be
> on steroids or something.
The messages are sumited twice by your mailclient - it's not the MTAs
fault.
See that there are several minutes between them and that
On Wed Oct 08, 05:27P +0200, Bernd Walter wrote:
> On Wed, Oct 08, 2003 at 03:59:40AM +0100, Stuart Walsh wrote:
> > Aww crap, my apologies for the duplicate email.. sendmail appears to be
> > on steroids or something.
>
> The messages are sumited twice by your mailclient - it's not the MTAs
> fau
>> I read that too. That appears to be just about all the information about
>> the new devfs that there is,
>> short of reading the source code.
You shouldn't need to do that. You can, more or less entirely forget
about DEVFS unless you are a device driver writer.
If you needed to run mknod(8)
> Ahh!
> Here is a fragment of my loader.conf..
> nvidia_load="YES"
> machdep.disable_mtrrs="1"
> hw.nvidia.registry.ReqAGPRate="1"
>
> >
Although this fix alloes me to start up the nvidia driver, the machine
still reboots when I run certain apps (openuniverse, for instance) and
at random times
It seems some recent Dell machines have the amount of video memory
available set to 1MB by default. The desktop machines allow you to
set this in the BIOS, but the laptops don't seem to allow you to
adjust this. Christian Zietz has a hack for Linux that convinces
the BIOS to let you use more memory
TB --- 2003-10-08 16:00:01 - starting CURRENT tinderbox run for alpha/alpha
TB --- 2003-10-08 16:00:01 - checking out the source tree
TB --- cd /home/des/tinderbox/CURRENT/alpha/alpha
TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src
TB --- 2003-10-08 16:01:52 - building world
TB --- cd /
Hi,
Seems like I'm running into a serious problem upgrading my 5.1 machine
to the latest level:
The symptoms: I did an upgrade (cvsup) then went through the usual
build/install cycle (see below).
When I boot the new kernel everything runs straight up to
the moment when I start X-Windows. When
On Wed, 8 Oct 2003, ecsd wrote:
> The chronology is that I booted the system, did the disklabel -w -r ad3
> auto, turned around to disklabel -e /dev/ad3s1c (as I would normally
> do), and was told that /dev/ad3s1c did not exist. Then I wrote in here
> asking for help. ad3s1c does not exist.
Since
On Wed, Oct 08, 2003 at 11:20:16AM -0700, Andrew P. Lentvorski, Jr. wrote:
> On Wed, 8 Oct 2003, ecsd wrote:
>
> > The chronology is that I booted the system, did the disklabel -w -r ad3
> > auto, turned around to disklabel -e /dev/ad3s1c (as I would normally
> > do), and was told that /dev/ad3s1c
I see this problem as well. I'm running on a T40, with a DVD/CDRW in
the ultrabay, and -CURRENT as of this morning. At boot, it hangs
immediately after
ad0: 35174MB [71465/16/63] at ata0-master UDMA100
ata1: resetting devices ..
done
Backing out the most recent checkin to sys/dev/ata/ata-queu
On Wed, 8 Oct 2003 16:49:34 +0100
Stuart Walsh <[EMAIL PROTECTED]> wrote:
> They were, yes. But once when the sendmail daemon wasn't running. I
> checked the mail queue before i sent it again and it wasn't there.
> Perhaps sendmail stores failed mail somewhere I'm not familiar with.
> EUSERERROR
Hi,
I recently decided to update my alpha UP1000 to today's current from a
mid-July build. However, UDMA33 did not work on a hard disk attached
to the built-in Acer Aladdin controller (verbose dmesg appended).
I think I have narrowed the problem down to this line of code:
atadev->chann
> On Wed, 8 Oct 2003 16:49:34 +0100
> Stuart Walsh <[EMAIL PROTECTED]> wrote:
>
> > They were, yes. But once when the sendmail daemon wasn't running. I
> > checked the mail queue before i sent it again and it wasn't there.
> > Perhaps sendmail stores failed mail somewhere I'm not familiar with.
>
On Wed, 8 Oct 2003, Harti Brandt wrote:
> On Wed, 8 Oct 2003, ecsd wrote:
>
> e>I had already been able to go so far as to "disklabel -w -r ad3 auto".
This is in error and should have been:
fdisk -i -u /dev/ad3
[add a partition 1]
disklabel -r -w ad3s1 auto
he has a disklabel directly on the
On Wed, 8 Oct 2003, ecsd wrote:
> Harti Brandt wrote:
> On Wed, 8 Oct 2003, ecsd wrote:
> e>I had already been able to go so far as to "disklabel -w -r ad3 auto".
> e>After doing this on a 4.X system I would then "disklabel -e /dev/ad3s1c"
> e>but /dev/ad3s1c does not exist, so I am stuck.
> e>M
On Wed, 8 Oct 2003, Justin Smith wrote:
>
> > Ahh!
> > Here is a fragment of my loader.conf..
> > nvidia_load="YES"
> > machdep.disable_mtrrs="1"
> > hw.nvidia.registry.ReqAGPRate="1"
>
> Although this fix alloes me to start up the nvidia driver, the machine
> still reboots when I run certain app
One of my buddies is having panics with if_em after the last
set of changes a couple of weeks ago. He runs dhclient
on the interface to get a lease from a cable modem. The
panic is a recurse on a non-recursive mutex. I haven't
gotten a traceback from him yet, but a little perusing
through the so
On Wednesday 08 October 2003 05:27 pm, Daniel Eischen wrote:
> One of my buddies is having panics with if_em after the last
> set of changes a couple of weeks ago. He runs dhclient
> on the interface to get a lease from a cable modem. The
> panic is a recurse on a non-recursive mutex. I haven't
On Thursday 09 October 2003 01:41, Justin Smith wrote:
> > Ahh!
> > Here is a fragment of my loader.conf..
> > nvidia_load="YES"
> > machdep.disable_mtrrs="1"
> > hw.nvidia.registry.ReqAGPRate="1"
>
> Although this fix alloes me to start up the nvidia driver, the machine
> still reboots when I run
On Tue, 7 Oct 2003, Kris Kennaway wrote:
> On Tue, Oct 07, 2003 at 06:11:30PM -0700, Doug White wrote:
> > On Tue, 7 Oct 2003, YONETANI Tomokazu wrote:
> >
> > > The hardware is IBM NetFinity 6000R, and it has ServerWorks ROSB4 UDMA33
> > > controller, to which the IDE disk is attached. The size o
On Wed, Oct 08, 2003 at 07:05:49PM -0700, Doug White wrote:
> > > The ROSB4 is known to have data-corruption problems with running in UDMA
> > > mode. The dump is probably tripping over this, which is why Tor's patch
> > > works since it demotes the device back to PIO.
> >
> > I also had problems
Andrew Gallatin wrote:
Hi,
I recently decided to update my alpha UP1000 to today's current from a
mid-July build. However, UDMA33 did not work on a hard disk attached
to the built-in Acer Aladdin controller (verbose dmesg appended).
I think I have narrowed the problem down to this line of code:
Hi There.
I have 2 PCI wireless card with the Atheros chipset some one know
how can i setup a point-to-point with 2 of this wireless card on
Freebsd, I could made work Access Point client, but i couln't adhoc
turbo mode 11a
thanks
--
Marcos Biscaysaqu
Systems Administrator
ThePacific.Net L
On Wednesday 08 October 2003 08:45 pm, Marcos Biscaysaqu wrote:
> Hi There.
> I have 2 PCI wireless card with the Atheros chipset some one know
> how can i setup a point-to-point with 2 of this wireless card on
> Freebsd, I could made work Access Point client, but i couln't adhoc
> turbo mode 1
Hi,
I see some posts from late Sept about people having issues with SCHED_ULE.
I just wanted to add in that I am having the exact same problems. In
short:
Anything that seems disk intensive: bzip2 (unbzip2ing one big file makes
this happen), making world, building ports, etc makes my X environm
I was using ipfw and natd but I wanted to move nat into the kernel so I
recompiled with ipfilter and ipnat. Now, after terminating natd, and
setting up ipnat rules in /etc/ipnat.rules, I see memory increase at a rate
of just under 1MB per minutes. Has anyone else seen a memory leak in ipnat
or ip
Hello!
Can not remove directory /usr/obj/usr/src/gnu/usr.bin/cc/cc1
rm: /usr/obj/usr/src/gnu/usr.bin/cc/cc1: Directory not empty
bash-2.05b# pwd; ls -la
/usr/obj/usr/src/gnu/usr.bin/cc/cc1
total 4
drwxr-xr-x 2 root wheel 512 Oct 9 08:54 .
drwxr-xr-x 13 root wheel 512 Oct 9 08:54 ..
bas
man rm
Note -r and -f.
Boris Kovalenko wrote:
Hello!
Can not remove directory /usr/obj/usr/src/gnu/usr.bin/cc/cc1
rm: /usr/obj/usr/src/gnu/usr.bin/cc/cc1: Directory not empty
bash-2.05b# pwd; ls -la
/usr/obj/usr/src/gnu/usr.bin/cc/cc1
total 4
drwxr-xr-x 2 root wheel 512 Oct 9 08:54 .
drwx
In the last episode (Oct 09), Boris Kovalenko said:
> Can not remove directory /usr/obj/usr/src/gnu/usr.bin/cc/cc1
> rm: /usr/obj/usr/src/gnu/usr.bin/cc/cc1: Directory not empty
>
> bash-2.05b# pwd; ls -la
> /usr/obj/usr/src/gnu/usr.bin/cc/cc1
> total 4
> drwxr-xr-x 2 root wheel 512 Oct 9 08:
Navigation Bar
March-September 2003 Status Report
Introduction:
The FreeBSD Bi-monthly status reports are back! In this edition, we
catch up on seven highly productive months and look forward to the end
of 2003.
As always, the FreeBSD development
Hello!
I know about -r and -f options. They don't help.
Proc wrote:
man rm
Note -r and -f.
Boris Kovalenko wrote:
Hello!
Can not remove directory /usr/obj/usr/src/gnu/usr.bin/cc/cc1
rm: /usr/obj/usr/src/gnu/usr.bin/cc/cc1: Directory not empty
bash-2.05b# pwd; ls -la
/usr/obj/usr/src/gnu/
Hello!
Seems You are right:
BAD INODE NUMBER FOR '.' I=353381 OWNER=root MODE=40755
SIZE=512 MTIME=Oct 9 08:54 2003
DIR=/obj/usr/src/gnu/usr.bin/cc/cc1
UNEXPECTED SOFT UPDATE INCONSISTENCY
FIX? no
Will reboot and run fsck manually. Thanks for advance!
Yours truly,
Boris Kovalenko
Dan Nels
Several reasons:
Having it in the kernel improves performance
natd chokes on the latest windoze worms and I have implemented some DoS
prevention/worm protection in ipnat but I'm seeing this memory leak without
my improvements there at all.
If it's in the kernel, ipnat is kept under control when
Several reasons:
Having it in the kernel improves performance
natd chokes on the latest windoze worms and I have implemented some DoS
prevention/worm protection in ipnat but I'm seeing this memory leak without
my improvements there at all.
If it's in the kernel, ipnat is kept under control when
54 matches
Mail list logo
