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 b
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 investig
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 mo
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.
AF
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 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 get
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 ma
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
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 t
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 remai
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
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 conclusio
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
> 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 ge
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 crashdump
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.
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 m
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 bi
> > 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 b
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 want
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 again
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 cabl
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
I also noticed that earlier ATAng spits out these messages; (cut&pasting boot -v
is a little tedious, but I can copy it all if it helps)
The err=0x01 caught my eye.
Pete
atapci0: port
0x1080-0x10ff,0x1480-0x148f,0x1000-0x107f mem 0x4020-0x4021,0x4040-0x40400fff
irq 9 at device 9.0
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
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
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 5.1-CURREN
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 t
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 o
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 appr
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
* 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
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
>
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 stu
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 numbe
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 follo
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,
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 f
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 implement
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. M
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 48
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
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 ext2fs_un
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 sys
;), 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!
>
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
retrie
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 manufact
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 b
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
> > dc015
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 flus
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 it>>fine, first boot -v with ATAng kernel and then
> >ATAold.Any ideas if raid configs should be compatible between them?
> >Should>>m
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
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
pmap_emulate
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'
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 thi
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 b
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 BUF_
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 error
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 by
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
pan
> 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 sy
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 correct
> 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
> wastin
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 process.
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'
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, u
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 -cu
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
> 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, fini
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*
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;
Debugger(c03ded4a,100,c03f40e5,dd88
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,
--
--- --
Mich
> 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 sync
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 PROT
On Tue, 2 Sep 2003, Kevin Oberman wrote:
> > 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, buil
I apologize to the list, I found the issue with cryptodev. One must
load the crypto core (crypto.ko) the crypto device (ubsec.ko) *AND* the
crypto device itself (cryptodev.ko). Again, I'm sorry to waste
everyone's time...
--
Jeremy C. McDermond
> Date: Tue, 2 Sep 2003 17:42:25 -0400 (EDT)
> From: Jeff Roberson <[EMAIL PROTECTED]>
>
>
> On Tue, 2 Sep 2003, Kevin Oberman wrote:
>
> > > Date: Tue, 2 Sep 2003 10:53:43 +0200
> > > From: Jan Srzednicki <[EMAIL PROTECTED]>
> > > Sender: [EMAIL PROTECTED]
> > >
> > > On Mon, Sep 01, 2003 at 07
From: Doug White <[EMAIL PROTECTED]>
On Fri, 29 Aug 2003, Oleg Polyakov wrote:
> I upgraded old Compaq Despro EP from 5.1-Release to Current as of Aug
> 27th (cvsupped) and last line I see after boot is "Mounting root from
> ufs:/dev/ad0s1a". The box just can't go past this point. boot -v give
Seishi Hiragushi wrote:
> I noticed that network collition increase, in log of 7/26.
> Such still a state continues.
> What became like this owing to?
>
> 5.1-CURRENT-20030720 (daily run 7/26):
> Network interface status:
> NameMtu Network Address Ipkts IerrsOpkts Oerrs
Jeff Roberson wrote:
> I don't know of any general syncer issues outside of this.
Boot single user, run fsck, then halt.
--
:{ [EMAIL PROTECTED]
Andy Farkas
System Administrator
Speednet Communications
http://www.speednet.com.au/
t text file in there.
>
> ODHIAMBO Washington wrote:
>
> * 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 d
The system crashed last night with the same phenomenon I have described in
last mail.
Please see the attachment for my configuration. I have not posting the debug
version of kernel configuration, because it's the current kernel I am
using. The debug options I have chosen are:
---snip---
/gcc/gcc/alias.c.diff?cvsroot=gcc&only_with_tag=gcc-3_3-branch&r1=1.181.2.2&r2=1.181.2.3
I confirm, that my FreeBSD version is 5.1-CURRENT (20030902).
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebs
OS: FreeBSD-CURRENT built within PicoBSD
Hardware: headless single-CPU PC with three Ethetnet cards:
- one single-interface dc card
- one quad fxp card
- one quad dc card
The kernel boots fine, and I don't have problem assigning IP
addresses on the fxp interfaces. When I try to configure the
On Tue, 2 Sep 2003, Oleg Polyakov wrote:
> > > I upgraded old Compaq Despro EP from 5.1-Release to Current as of Aug
> > > 27th (cvsupped) and last line I see after boot is "Mounting root from
> > > ufs:/dev/ad0s1a". The box just can't go past this point. boot -v gives
> > > one more line "start_i
I have a machine that panics reliably within ten minutes of
operation with ATAng. It subsequently locks up, so I can't obtain
a dump, and I get a small amount of random filesystem corruption
upon rebooting. Everything was fine with ATAog.
I don't have a serial cable handy at the moment, but the
I found the bug that I introduced around the 29th of august. It is fixed
in ffs_softdep.c rev 1.143. Truely, most of the leg work was done by
tegge. I just produced and tested a patch. This completes a buildworld
with 128M of memory now, whereas before it just completed with 64m and
512m. perh
Recently I have been trying to get inetd to start on a server of mine and it
prints the following error in dmesg:
Sep 2 23:09:18 iso inetd[703]: unknown rpc/udp or rpc/tcp
There is nothing but ftp turned on in the inetd.conf (turn ftp off, same
error). I have tried google, yet it's not returnin
1 - 100 of 105 matches
Mail list logo
