On 01-Sep-03 Unnamed Administration sources reported Scott Long said :
Scott M. Likens wrote:
I have a question related to FreeBSD Serial console,
I am aware you can use -Dh for both internal and serial, but is it
possible to see the 'kernel' boot messages sent on both the serial and
the
My notes on getting a serial console at 115200
-must be com1
-com1 must be at port 0x3F8 irq 4
-in bios set the port and irq as above
-in bios set serial redirection to com1
-in bios set baud rate 115200
-in bios set RTS/CTS flow control
-edit (or create) /etc/make.conf to add these lines:
Aaron Wohl wrote:
My notes on getting a serial console at 115200
-must be com1
-com1 must be at port 0x3F8 irq 4
-in bios set the port and irq as above
-in bios set serial redirection to com1
-in bios set baud rate 115200
-in bios set RTS/CTS flow control
-edit (or create) /etc/make.conf to add
*SIGH*
No what I want is NO serial console. DO NOT FOR ANY REASON turn off/not resp
ond to the keyboard port
Nicole
On 01-Sep-03 Unnamed Administration sources reported Scott Long said :
Aaron Wohl wrote:
My notes on getting a serial console at 115200
-must be com1
-com1 must be at
On Sep 1, 2003, at 6:36 PM, Nicole wrote:
*SIGH*
No what I want is NO serial console. DO NOT FOR ANY REASON turn
off/not resp
ond to the keyboard port
-Dh means both keyboard and serial console... what's the problem? And
please
stop shouting.
Dave
Nicole
On 01-Sep-03 Unnamed
Hey folks,
It looks like we may need to rethink the way swap is mounted at boot time
if we want crashdumps to work.
Recently(?), a change was made so you can no longer open a swap partition
read/write after it is activated with swapon(8). In the current boot
sequence, swap is mounted before the
On Mon, Sep 01, 2003 at 05:29:09PM -0600, Scott Long wrote:
At one time I was working on patches to the loader to make the console
speed configurable. At the time, at least, I didn't see any evidence
that the settings were stored in the boot0 block, but maybe I was wrong.
AFAIK, the boot0
I don't believe that I responded to your email, so I'm not sure why you
are shouting at me.
Figuring out what the Right Thing is for handling disconnected keyboards
seems to be highly debatable. Until someone comes along and solves the
problem the way that you want it, one workaround to
Doug White wrote:
Hey folks,
It looks like we may need to rethink the way swap is mounted at boot time
if we want crashdumps to work.
Recently(?), a change was made so you can no longer open a swap partition
read/write after it is activated with swapon(8). In the current boot
sequence, swap is
John Birrell wrote:
On Mon, Sep 01, 2003 at 05:29:09PM -0600, Scott Long wrote:
At one time I was working on patches to the loader to make the console
speed configurable. At the time, at least, I didn't see any evidence
that the settings were stored in the boot0 block, but maybe I was wrong.
On Tue, 2 Sep 2003, Seishi Hiragushi wrote:
5.1-CURRENT-20030720 (daily run 7/26):
Network interface status:
NameMtu Network Address Ipkts IerrsOpkts Oerrs Coll
dc01500 Link#1 00:90:cc:a2:59:56 38342027 441061 0 260568
This is really sort of two problems, but I'll focus on the primary
concern here and maybe the more basic (but less significant) problem
will get addressed at some point. (Or I'll PR it.)
I have noticed that my stable system never seems to leave the
filesystems clean after a crash on CURRENT. I
On Monday 01 September 2003 05:38 pm, Kevin Oberman wrote:
This is really sort of two problems, but I'll focus on the primary
concern here and maybe the more basic (but less significant) problem
will get addressed at some point. (Or I'll PR it.)
I have noticed that my stable system never
If you do try a USB keyboard be sure and test reboot -d (make a kernel
core). On the intel servers I have reboot -d (or any panic) causes the
kernel to lockup forever. In the routine where it writes out kernel
dumps it pools for a control-c hit on the console that routine (poll for
a char) turns
--9dgjiU4MmWPVapMU
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Hi,
got a panic with a kernel from sources around September 1st, 8pm.
Dump and debugging kernel available for further debugging.
cg@ got the same panic on his
On Mon, 2003-09-01 at 16:13, Nicole wrote:
On 01-Sep-03 Unnamed Administration sources reported Scott Long said :
Scott M. Likens wrote:
I have a question related to FreeBSD Serial console,
I am aware you can use -Dh for both internal and serial, but is it
possible to see the 'kernel'
On Mon, 1 Sep 2003, Nicole wrote:
It just drives me crazy when important things get broken and people
act like.. What the big deal. I don't need it why should you?
You're certainly free to draw that conclusion, however you'd be
mistaken. There are times when adding new features means that
Kevin Oberman wrote:
Finally I do a reboot. No partition has ever been mounted except root
which is read-only. Syncer reports 1 or more buffers remain and
reports this until it gives up.
On Tue, 29 Jul 2003 08:13:27 +1000 (EST) Andy Farkas [EMAIL PROTECTED] wrote:
Subject: buffers
On Tue, 2 Sep 2003, Christian Brueffer wrote:
Hi,
got a panic with a kernel from sources around September 1st, 8pm.
Dump and debugging kernel available for further debugging.
cg@ got the same panic on his machine.
This is probably my fault. I will look into it tonight. Until then you
On 02-Sep-03 Unnamed Administration sources reported Doug Barton said :
On Mon, 1 Sep 2003, Nicole wrote:
It just drives me crazy when important things get broken and people
act like.. What the big deal. I don't need it why should you?
You're certainly free to draw that conclusion,
Scott Long wrote:
Scott M. Likens wrote:
I have a question related to FreeBSD Serial console,
I am aware you can use -Dh for both internal and serial, but is it
possible to see the 'kernel' boot messages sent on both the serial and
the console?
It was a question that was asked to me
From: Kent Stewart [EMAIL PROTECTED]
Date: Mon, 1 Sep 2003 17:52:13 -0700
On Monday 01 September 2003 05:38 pm, Kevin Oberman wrote:
This is really sort of two problems, but I'll focus on the primary
concern here and maybe the more basic (but less significant) problem
will get addressed
Scott Long wrote:
Doug White wrote:
Hey folks,
It looks like we may need to rethink the way swap is mounted at boot
time
if we want crashdumps to work.
I question the wizdom of what you're describing. If swap space needs to
be made available for fsck to run, then what happens to the
David Leimbach wrote:
On Sep 1, 2003, at 6:36 PM, Nicole wrote:
*SIGH*
No what I want is NO serial console. DO NOT FOR ANY REASON turn
off/not resp
ond to the keyboard port
-Dh means both keyboard and serial console... what's the problem? And
please
stop shouting.
man 8 boot:
Doug White wrote:
It looks like we may need to rethink the way swap is mounted at boot time
if we want crashdumps to work.
Recently(?), a change was made so you can no longer open a swap partition
read/write after it is activated with swapon(8). In the current boot
sequence, swap is
Pawel Worach wrote:
Is fsck really that memory heavy so that it needs swap?
Yes, if you have a huge FS.
The problem is that the checking of the CG bitmaps during an fsck
require that you have all the bitmaps in core, and then linearly
traverse the entire directory structure to identify which
Is fsck really that memory heavy so that it needs swap?
Yes, if you have a huge FS.
The problem is that the checking of the CG bitmaps during an fsck
require that you have all the bitmaps in core
Hmm
For a one TB FS with 8KB block size you need 2^(40-13) bits
to keep track of blocks.
On Mon, 1 Sep 2003, Nicole wrote:
Sorry I didn't mean to be so testy I guess would discribe it. It's
an old issue for me.
Not to put too fine a point on it, but I've seen numerous posts from
you, on several topics, all of them berating people for not giving you
what you want, when you wanted
Doug Barton wrote:
On Mon, 1 Sep 2003, Nicole wrote:
In my 5.1 system I see this in my .hints file. So I assume I edit it
there or do I treat it like a defaults file and import and change in
in my config file?
I didn't say anything about your hints file. You need to edit your
kernel config file,
Scott Long wrote:
Doug Barton wrote:
On Mon, 1 Sep 2003, Nicole wrote:
In my 5.1 system I see this in my .hints file. So I assume I edit it
there or do I treat it like a defaults file and import and change in
in my config file?
I didn't say anything about your hints file. You need to edit your
I usualy have a number of swap partitions since the max size of a swap
partition is kind of limited. I was thinking of changing it to do swapon
twice. The first time early in the boot would skip mounting any swap
areas that had kernel core dumps. Then after the savecore it could do
swapon
ATAng does not seem to detect my RAID set, while ATAold boots it
fine, first boot -v with ATAng kernel and then ATAold.
Any ideas if raid configs should be compatible between them? Should
make sense that they are so people upgrading don't get burned...
ata2-master: pio=0x0c wdma=0x22 udma=0x45
In message [EMAIL PROTECTED], Aaron Wohl writes:
I usualy have a number of swap partitions since the max size of a swap
partition is kind of limited. I was thinking of changing it to do swapon
twice. The first time early in the boot would skip mounting any swap
areas that had kernel core dumps.
I also noticed that earlier ATAng spits out these messages; (cutpasting boot -v
is a little tedious, but I can copy it all if it helps)
The err=0x01 caught my eye.
Pete
atapci0: Promise PDC20619 UDMA133 controller port
0x1080-0x10ff,0x1480-0x148f,0x1000-0x107f mem
On Sun, Aug 31, 2003 at 05:52:24PM +0300, Ruslan Ermilov wrote:
Now it looks like this:
install -C -o root -g wheel -m 444 libalias.a /foo/usr/lib
install -s -o root -g wheel -m 444 libalias.so.4 /foo/lib
ln -fs libalias.so.4 /foo/lib/libalias.so
ln -fs /lib/libalias.so.4
On Sun, Aug 31, 2003 at 10:10:49PM -0700, David O'Brien wrote:
On Sun, Aug 31, 2003 at 05:52:24PM +0300, Ruslan Ermilov wrote:
I might be missing an obvious, but I just don't see a reason
why we should use relative linking here: we should just link
to where we really install. With
I have a file .fsck_snapshot in /usr (of 7 GB ?!)
-r 1 root wheel 7220781056 Aug 22 18:08 .fsck_snapshot
I hope I can delete it without consequences (after chmod'ing it
of course :-)
--
Chris Christoph P. U. Kukulies kukulies (at) rwth-aachen.de
On Mon, 1 Sep 2003, Scott Long wrote:
Device flags are not specified in the kernel config anymore unless you
try really, really hard. /etc/device.hints is the correct place to
adjust this flag.
Yeah, I was looking at the kernel config on the wrong box. This flag did
used to be in GENERIC, so
It seems Petri Helenius wrote:
I also noticed that earlier ATAng spits out these messages; (cutpasting boot -v
is a little tedious, but I can copy it all if it helps)
The err=0x01 caught my eye.
Err=0x01 is actually OK Im' there signal from an ATA device :)
What I need to know is if the
It seems Petri Helenius wrote:
ATAng does not seem to detect my RAID set, while ATAold boots it
fine, first boot -v with ATAng kernel and then ATAold.
Any ideas if raid configs should be compatible between them? Should
make sense that they are so people upgrading don't get burned...
Do you
On Tue, 2 Sep 2003, Poul-Henning Kamp wrote:
Hmm, that was an unfortunate side effect.
Heh, well, stuff happens. I think your idea of opening swap exclusive is
probably a good one, but it will require some gymnastics to accomodate
it. One thing that'd really help is an option to savecore that
In message [EMAIL PROTECTED], Doug Barton writes:
On Tue, 2 Sep 2003, Poul-Henning Kamp wrote:
Hmm, that was an unfortunate side effect.
Heh, well, stuff happens. I think your idea of opening swap exclusive is
probably a good one, but it will require some gymnastics to accomodate
it.
Yeah, but
Doug Barton wrote:
On Tue, 2 Sep 2003, Poul-Henning Kamp wrote:
Hmm, that was an unfortunate side effect.
Heh, well, stuff happens. I think your idea of opening swap exclusive is
probably a good one, but it will require some gymnastics to accomodate
it. One thing that'd really help is an
On Tue, Sep 02, 2003 at 12:58:40AM -0600 I heard the voice of
Scott Long, and lo! it spake thus:
I still think that the real problem is in running swapon before
savecore. In 99% of the cases out there, RAM scales with storage,
so I really can't imaging fsck needing to swap, and certainly not
On Tue, 2 Sep 2003, Christoph Kukulies wrote:
I have a file .fsck_snapshot in /usr (of 7 GB ?!)
-r 1 root wheel 7220781056 Aug 22 18:08 .fsck_snapshot
As long as it isn't mounted it should be safe to remove.
--
Doug White| FreeBSD: The Power to Serve
[EMAIL
On Tue, 2 Sep 2003, Matthew D. Fuller wrote:
On Tue, Sep 02, 2003 at 12:58:40AM -0600 I heard the voice of
Scott Long, and lo! it spake thus:
I still think that the real problem is in running swapon before
savecore. In 99% of the cases out there, RAM scales with storage,
so I really
According to the first stages of your buildworld output,
You are trying to upgrade from FreeBSD-4.x.
This problem is known and described in the Problem Report bin/53201
See http://www.freebsd.org/cgi/query-pr.cgi?pr=bin%2F53201
P.S. There are no problems to upgrade from FreeBSD-4.x to
On Tue, 2 Sep 2003, Scott Long wrote:
I still think that the real problem is in running swapon before
savecore. In 99% of the cases out there, RAM scales with storage,
so I really can't imaging fsck needing to swap, and certainly not
in it's 'preen-before-background' mode.
I agree, but the
On Tue, 2 Sep 2003, Poul-Henning Kamp wrote:
In message [EMAIL PROTECTED], Doug Barton writes:
On Tue, 2 Sep 2003, Poul-Henning Kamp wrote:
Hmm, that was an unfortunate side effect.
Heh, well, stuff happens. I think your idea of opening swap exclusive is
probably a good one, but it will
Doug Barton wrote:
On Mon, 1 Sep 2003, M. Warner Losh wrote:
My tool is initially just a 'delete these files' tool, but now that I
think about it, it wouldn't be hard to say also 'create these
symlinks'. The hard part here is generating the 'obsolete' lists.
I posted one approach to
On (2003/09/02 09:43), Ian Freislich wrote:
I posted one approach to this today... touch a file right before you
start installworld, then consider anything not newer than that file a
candidate for disposal. There is currently something weird going on in
/usr/lib though... a lot of the
* Alexander Portnoy [EMAIL PROTECTED] [20030902 10:18]: wrote:
According to the first stages of your buildworld output,
You are trying to upgrade from FreeBSD-4.x.
This problem is known and described in the Problem Report bin/53201
See http://www.freebsd.org/cgi/query-pr.cgi?pr=bin%2F53201
Sheldon Hearn wrote:
On (2003/09/02 09:43), Ian Freislich wrote:
I posted one approach to this today... touch a file right before you
start installworld, then consider anything not newer than that file a
candidate for disposal. There is currently something weird going on in
/usr/lib
On Mon, Sep 01, 2003 at 01:16:00PM +0200, Soren Schmidt wrote:
I've gone over the probe code once again.
Please test, and in case it fails to detect or misdetects anything,
mail me the output of dmesg from a verbose boot, and state what
devices actually are there.
Hello,
The new stuff
About the original question: multiple consoles in the kernel are
unsupported in FreeBSD-4 but are standard in -current. Unfortunately,
their implementation is slightly incomplete even in -current. In
-current, you get them by booting with -D after booting using the
kern.console sysctl. The
On Mon, Sep 01, 2003 at 07:53:48PM +0300, Lefteris Chatzibarbas wrote:
Hello,
I have a problem with kernels, built the last couple of days, where
during shutdown syncer is giving up on buffers. During the next boot
all filesystems are checked because of improper dismount. Here follow
the
On Tue, Sep 02, 2003 at 10:23:02AM +0200, Jan Srzednicki wrote:
I've gone over the probe code once again.
Please test, and in case it fails to detect or misdetects anything,
mail me the output of dmesg from a verbose boot, and state what
devices actually are there.
Hello,
The new
On Tue, Sep 02, 2003 at 08:27:00AM +0200, Christoph Kukulies wrote:
I have a file .fsck_snapshot in /usr (of 7 GB ?!)
-r 1 root wheel 7220781056 Aug 22 18:08 .fsck_snapshot
The '7GB' does not mean you'll free up 7GB of disk space by freeing
it. IIRC, it's actually the size of the
Hello!
May somebody tell me the status of ALTQ integration with FreeBSD? I
need to know status for 5.x as well for 4.x too. Have read
http://www.csl.sony.co.jp/person/kjc/kjc/software.html#ALTQ and
misunderstood something. May somebody tell me in details what is the
status of ALTQ
On Tue, Sep 02, 2003 at 03:13:54PM +0600, Boris Kovalenko wrote:
May somebody tell me the status of ALTQ integration with FreeBSD? I
need to know status for 5.x as well for 4.x too. Have read
http://www.csl.sony.co.jp/person/kjc/kjc/software.html#ALTQ and
misunderstood something. May
Hi,
At 00:36 2/9/03, Nicole wrote:
*SIGH*
No what I want is NO serial console. DO NOT FOR ANY REASON turn off/not resp
ond to the keyboard port
Unfortunately, many motherboards (BIOSs?) won't initialise a PS/2 keyboard
interface unless a keyboard is connected at boot time, so if you plug in a
Please try out this patch if you have a sis based network card.
It sets a 400usec interrupt holdoff, and this seems to have a profound
impact on network performance.
The patch is relative to FreeBSD-current but probably applies on
5.0, 5.1 and even 4.x as well.
In my tests, using a soekris
On Tue, Sep 02, 2003 at 06:58:04PM +1000, Peter Jeremy wrote:
On Tue, Sep 02, 2003 at 08:27:00AM +0200, Christoph Kukulies wrote:
I have a file .fsck_snapshot in /usr (of 7 GB ?!)
-r 1 root wheel 7220781056 Aug 22 18:08 .fsck_snapshot
The '7GB' does not mean you'll free up 7GB
On Tue, Sep 02, 2003 at 05:10:48AM +1000, Bruce Evans wrote:
Apparently the bug fixed in ext2fs/fs.h revs 1.3, 1.4 and 1.6 (etc.)
was restored in rev.1.14. I think this is because B_LOCKED buffers
were ignored in the sync() in boot() and flushed later when
vfs_unmountall() calls
On Monday, 01 September 2003 23:02, Bill Moran wrote:
Alastair G. Hogge wrote:
On Monday, 01 September 2003 02:24, Steve Kargl wrote:
On Sun, Aug 31, 2003 at 07:52:15PM +1000, Alastair G. Hogge wrote:
Hello list,
For the past couple of weeks I've been tyring to keep my system up to
date
;), Mon, Sep 01, 2003 at 01:16:00PM +0200, Soren Schmidt said that
I've gone over the probe code once again.
Please test, and in case it fails to detect or misdetects anything,
mail me the output of dmesg from a verbose boot, and state what
devices actually are there.
Thanks!
-Søren
I'm sure there's lots of errors, so be gentle. :) It does work though,
so that's a plus.
Doug
--
This .signature sanitized for your protectionIndex: savecore.8
===
RCS file: /usr/local/ncvs/src/sbin/savecore/savecore.8,v
Hiya
Unfortunately, many motherboards (BIOSs?) won't initialise a PS/2 keyboard
interface unless a keyboard is connected at boot time, so if you plug in a
keyboard subsequently it won't work. Nothing the OS can do in this case (I
believe), and yes it's a PITA.
Keyboard and mouse
On Tue, 2 Sep 2003, Jan Srzednicki wrote:
On Mon, Sep 01, 2003 at 07:53:48PM +0300, Lefteris Chatzibarbas wrote:
I have a problem with kernels, built the last couple of days, where
during shutdown syncer is giving up on buffers. During the next boot
all filesystems are checked because
On Tue, 2 Sep 2003 10:32:43 +1000 (EST)
Andy Farkas [EMAIL PROTECTED] wrote:
On Tue, 2 Sep 2003, Seishi Hiragushi wrote:
5.1-CURRENT-20030720 (daily run 7/26):
Network interface status:
NameMtu Network Address Ipkts IerrsOpkts Oerrs Coll
dc01500 Link#1
Soren Schmidt wrote:
It seems Petri Helenius wrote:
ATAng does not seem to detect my RAID set, while ATAold boots it
fine, first boot -v with ATAng kernel and then ATAold.
Any ideas if raid configs should be compatible between them? Should
make sense that they are so people upgrading don't get
On Tue, 2 Sep 2003, Tim Robbins wrote:
On Tue, Sep 02, 2003 at 05:10:48AM +1000, Bruce Evans wrote:
Apparently the bug fixed in ext2fs/fs.h revs 1.3, 1.4 and 1.6 (etc.)
was restored in rev.1.14. I think this is because B_LOCKED buffers
were ignored in the sync() in boot() and flushed
It seems Petri Helenius wrote:
Soren Schmidt wrote:
It seems Petri Helenius wrote: ATAng does not seem to detect my RAID set,
while ATAold boots itfine, first boot -v with ATAng kernel and then
ATAold.Any ideas if raid configs should be compatible between them?
Shouldmake sense that they
Running -CURRENT with sources updated between 0347 - 0356 hrs. PDT
(US/Pacific -- 7 hrs. west of GMT at this time of year) yesterday;
in the process of building today's -CURRENT. (Had a similar-looking
problem yesterday, but I got involved in some other things, and didn't
make the time to report
I got this over the weekend on one of the alpha package machines:
panic: pmap_emulate_reference(0xfc0017034be0, 0x8002a4c0, 0, 0): pa
0x82a000 not managed
Stack backtrace:
db_print_backtrace() at db_print_backtrace+0x18
backtrace() at backtrace+0x2c
panic() at panic+0x148
On Mon, Aug 18, 2003 at 11:40:09PM -0500, Alan L. Cox wrote:
Kris Kennaway wrote:
I got this on alpha just now (kernel updated 2 days ago, filesystems
created with -b 32768 -f 4096 to test reports of panics with these
settings, which may or may not be relevant). I don't think I've seen
Soren Schmidt wrote on Monday, September 01, 2003 6:16 AM
I've gone over the probe code once again.
Please test, and in case it fails to detect or misdetects anything,
mail me the output of dmesg from a verbose boot, and state what
devices actually are there.
I cvsupped after I saw this
On Tue, 2 Sep 2003, Peter Jeremy wrote:
On Tue, Sep 02, 2003 at 08:27:00AM +0200, Christoph Kukulies wrote:
I have a file .fsck_snapshot in /usr (of 7 GB ?!)
-r 1 root wheel 7220781056 Aug 22 18:08 .fsck_snapshot
The '7GB' does not mean you'll free up 7GB of disk space by
On Tue, 2 Sep 2003, Tim Robbins wrote:
Rev.1.3 of ext2fs/fs.h (etc.) abuses B_LOCKED to do little more than
make the sync() ignore ext2fs's private buffers (its complications are
mainly to handle the resulting B_LOCKED buffers). It wants to brelse()
the buffers so that their
In the course of portsupgrading it happened that some X11 stuff
got rebuilt (don't know if it came from wrongly applying
portsupgrade -r instead of -R) anyway, I noticed that
I was bailed out of my xsession as soon as an xterm was opened.
Starting the xterm in a shell reveiled the following
Hello everyone,
I am looking for help on producing a core-dump or some other solution to
survive a strange kernel panic, which begins to appear from the beginning of
August, and persists in recent kernels, including the kernel made from
yesterday's source. It seemed that the panic was triggered
I'm running a ~2 week old -current, and when debugging some hacks of
mine, I noticed that gdb -k seems to be missing at least one frame
in its stack. Eg, ddb shows:
panic: page fault
cpuid = 0; lapic.id =
Stack backtrace:
backtrace(c0380cf2,0,c036e757,d96d4bd4,100) at backtrace+0x17
Bizarre. I use ACLs in my kernel daily, and I use nmap almost daily,
and haven't seen this. If you re-add ACLs with a fresh kernel build,
does the problem come back? Could you look at ktraces of nmap with and
without ACLs and see what causes it? Do you have ACLs enabled on any
file
On Tue, 2003-09-02 at 01:33, Bruce Evans wrote:
About the original question: multiple consoles in the kernel are
unsupported in FreeBSD-4 but are standard in -current. Unfortunately,
their implementation is slightly incomplete even in -current. In
-current, you get them by booting with -D
Hi,
latest kernel causes a panic early during boot:
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x68
fault code = supervisor read, page not present
instruction pointer = 0x8:0xc02667cf
stack pointer = 0x10:0xc0641cf8
frame pointer
Soren Schmidt schrieb:
I've gone over the probe code once again.
Please test, and in case it fails to detect or misdetects anything,
mail me the output of dmesg from a verbose boot, and state what
devices actually are there.
Hi,
again no luck. Same problem persists, the devices got probed
Alright, it had nothing to do with ACL's. Unknown to me, someone got on
that machine and enabled the firewall, and added rules. Those rules were
causing the problem (I'm not sure why he added a firewall on a machine
already behind one on a 192.168.0.0/24 network). Anyway, sorry for
wasting
I have a perl script that dd's each audio track from an audio cd. The
tracks are copied just fine until it gets about 75% into a 70 minute
cd. dd then gets slower and slower until it seems to grind to a halt.
eventually, I'll set TIMEOUT messages and won't be able to kill the
current dd
On Tue, Sep 02, 2003 at 12:56:24PM -0400, Bryan Liesner wrote:
I have a perl script that dd's each audio track from an audio cd. The
tracks are copied just fine until it gets about 75% into a 70 minute
cd. dd then gets slower and slower until it seems to grind to a halt.
eventually, I'll
I'm trying to compile mozilla thunderbird on -current and the
configure program stops with this error:
checking whether C++ compiler has -pedantic long long bug... yes
configure: error: Your compiler appears to have a known bug where
long long is miscompiled when using -pedantic.
Reconfigure using
Please try out this patch if you have a sis based network card.
It sets a 400usec interrupt holdoff, and this seems to have a profound
impact on network performance.
The patch is relative to FreeBSD-current but probably applies on
5.0, 5.1 and even 4.x as well.
In my tests, using a
In message [EMAIL PROTECTED], Sam Leffler writes:
In my tests, using a soekris 4801 computer I have found:
It is especially important that folks with Soekris 45xx boards try this.
My tests appeared to indicate there might be issues, but my operating
environment is so different from -current
It seems Sean Kelly wrote:
I have a perl script that dd's each audio track from an audio cd. The
tracks are copied just fine until it gets about 75% into a 70 minute
cd. dd then gets slower and slower until it seems to grind to a halt.
eventually, I'll set TIMEOUT messages and won't be
latest kernel causes a panic early during boot:
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x68
fault code = supervisor read, page not present
instruction pointer = 0x8:0xc02667cf
stack pointer = 0x10:0xc0641cf8
frame pointer
On Mon, Sep 01, 2003 at 05:29:09PM -0600, Scott Long wrote:
At one time I was working on patches to the loader to make the console
speed configurable. At the time, at least, I didn't see any evidence
that the settings were stored in the boot0 block, but maybe I was wrong.
In any case,
On Tue, 2 Sep 2003, Doug White wrote:
On Tue, 2 Sep 2003, Christoph Kukulies wrote:
I have a file .fsck_snapshot in /usr (of 7 GB ?!)
-r 1 root wheel 7220781056 Aug 22 18:08 .fsck_snapshot
As long as it isn't mounted it should be safe to remove.
Er, rather, if *fsck* isn't
Soren Schmidt wrote:
Oh, that one :) fixed...
-Søren
Do you have an idea why my SMP system would crash under heavy load, like
mysql shutdown, just a reboot, etc.?
The system did not have any issues before ATAng was committed.
This is one of the panics;
Hi,
make buildworld fails (cvsup from about 2 hours ago), it looks like the
amd import caused this:
/usr/src/usr.sbin/amd/doc/../../../contrib/amd/doc/am-utils.texi:45:
@include version.texi: No such file or directory
bye,
--
--- --
Date: Tue, 2 Sep 2003 10:53:43 +0200
From: Jan Srzednicki [EMAIL PROTECTED]
Sender: [EMAIL PROTECTED]
On Mon, Sep 01, 2003 at 07:53:48PM +0300, Lefteris Chatzibarbas wrote:
Hello,
I have a problem with kernels, built the last couple of days, where
during shutdown syncer is giving
Hi,
make buildworld fails (cvsup from about 2 hours ago), it looks like the
amd import caused this:
/usr/src/usr.sbin/amd/doc/../../../contrib/amd/doc/am-utils.texi:45:
@include version.texi: No such file or directory
Fixed 30 minutes ago. Please re-cvsup.
Martin
Martin Blapp, [EMAIL
1 - 100 of 119 matches
Mail list logo
