Good and bad observations:
When using a relative new 15 GByte hard drive (vendor IBM) with the wd0
driver the HD-led never turned off, even without disk activity.
With the ata driver the hard drive led works as expected. When running a
"make buildworld"
i had the impression that all went very fa
>Am I also right in assuming that all the registers that the user was
>running when they did the KERNCALL have been saved on the KERNEL stack by
>the time that the above routines are called?
No, that's what the pushal (push all) does.
-DG
David Greenman
Co-founder/Principal Architect, The Fr
On 26 Nov 1999, Assar Westerlund wrote:
> there's (to my mind) a difference between it's not done by default and
> it will not work. I did it because I had hardwired it in my previous
> config.
Yes, and when I converted if_ep to newbus I mentioned that hardwire was no
longer supported.
I'm a l
On Tue, 23 Nov 1999, Mark Murray wrote:
> I have been charged with the duty of ensuring that FreeBSD gets a
> security audit that has the credibility of OpenBSD's.
Great news! I had tried to organise such an effort over a year ago with
little success, mostly because I was working for a startup.
I have just cvsupped and built the latest -current kernel and have noticed
a new quirk plus an old quirk or 2. uname -a output is:
FreeBSD 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Fri Nov 26 02:06:45 EST
1999 [EMAIL PROTECTED]:/usr/src/sys/compile/PACER i386
1) CMOS clock problem, dmesg out
in src/lib/libc/i386/SYS.h we see:
#ifdef __ELF__
#define KERNCALLint $0x80 /* Faster */
#else
#define KERNCALLLCALL(7,0) /* The old way */
#endif
and in /usr/src/sys/i386/i386/exception.s
we see:
/*
* Call gate entry for syscall.
* The intersegment call has been
"David O'Brien" <[EMAIL PROTECTED]> writes:
> > +# don't try to hardware ep0 - it will not work
>
> If we don't hardware it in GENERIC, then why do people think they should
> be doing so?
(s/hardware/hardwire/ of course)
there's (to my mind) a difference between it's not done by default and
it
> Not hardwiring ep0 in the configuration file made it work. Thanks
> again.
...
> +# don't try to hardware ep0 - it will not work
If we don't hardware it in GENERIC, then why do people think they should
be doing so?
--
-- David([EMAIL PROTECTED])
To Unsubscribe: send mail to [EMAIL PROT
Before I go do a fresh SNAP install, I wanted to see if there was an easier
way to fix this problem...
My -current box was a celeron...I had to switch the celeron and mboard to my
windoze machine to get a vidcard werkin...I recompiled the kernel to 486,
586, and 686, and moved the HD, the cards, e
In message <[EMAIL PROTECTED]> Poul-Henning Kamp writes:
: As I've understood the conclusion of this thread, we want a
: sysctl, and we want it open as default. This patch should
: do that.
:
: Once Warner nods in the vertical direction it will be committed.
The head is oscillating with and ag
Poul-Henning Kamp <[EMAIL PROTECTED]> writes:
> no. Try to disable ep1 (if you can).
Not hardwiring ep0 in the configuration file made it work. Thanks
again.
Here's an trivial patch to GENERIC to add comments about these
characteristics about ep0.
/assar
Index: GENERIC
==
In message <[EMAIL PROTECTED]>, Assar Westerlund writes:
>Poul-Henning Kamp <[EMAIL PROTECTED]> writes:
>> Don't use the generic kernel unchanged with the 3com card.
>>
>> Disable the ex0 and ie0 drivers, one of those pummel the 3com
>> cards magic config registers.
>
>Tack. Now it manages to fi
Poul-Henning Kamp <[EMAIL PROTECTED]> writes:
> Don't use the generic kernel unchanged with the 3com card.
>
> Disable the ex0 and ie0 drivers, one of those pummel the 3com
> cards magic config registers.
Tack. Now it manages to find ep0 properly. It still finds a `ghost'
ep1 and hangs hard wh
On Thu, 25 Nov 1999, Gary Jennejohn wrote:
!>I can only guess, but it looks like the user-land process isn't told
!>about the hangup and keeps sending packets down the line. The packets
!>never go out (no connection), so the mbufs eventually run out. The
!>raw interface evidently doesn't have th
On Wed, 24 Nov 1999, Poul-Henning Kamp wrote:
>
> I still hear reports of sporadic calcru() warnings.
>
> If any of you see these, could you try to see if they correlate
> to the uptime of the machine in question ?
Since I replaced a September 15 -current with October 14 -current, I
get lots
Don't use the generic kernel unchanged with the 3com card.
Disable the ex0 and ie0 drivers, one of those pummel the 3com
cards magic config registers.
>ep0: <3Com EtherLink III (3c509-Combo)> at port 0x300-0x30f irq 9 on isa0
>ep0: eeprom failed to come ready
>...
>Ethernet address ff:ff:ff:ff:
Hi.
When upgrading a box from current ~ 1999-11-15 to ~ today, the 3c509b
network interface fails to work.
These are the kernels (the first one working, the second one not).
/kernel.old:
FreeBSD 4.0-CURRENT #1: Mon Nov 15 00:03:00 CET 1999
/kernel:
FreeBSD 4.0-CURRENT #0: Fri No
In article <[EMAIL PROTECTED]>, Gary Jennejohn
<[EMAIL PROTECTED]> writes
>Can you a) increase the size of the message buffer in your config file
>(options MSGBUF_SIZE=81920, for example) b) turn on ALL the
>trace in the kernel with isdndebug c) cause the panic to happen again
>and get a
In article <[EMAIL PROTECTED]> you wrote:
> Hi,
> I am running 4.0-current of:
> FreeBSD gmarco.eclipse.org 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Thu Nov 18
> 09:33:43 CET
> 1999 [EMAIL PROTECTED]:/usr/src/sys/compile/GMARCO i386
>
> But I have now a lot of errors (as you can see in this log
In article <[EMAIL PROTECTED]>, Gary Jennejohn
<[EMAIL PROTECTED]> writes
>Are you using the code in -current or one of the releases ? Makes a
>difference.
cvsup'd current from Saturday morning.
>Can you a) increase the size of the message buffer in your config file
>(options MSGBUF_SIZE
Mark Knight writes:
>Repeatable mbuf leak leading to crash in current of Saturday 20th
>November and all snapshots I've taken prior to that since August (i.e.
>when I got the ISDN card).
>
Are you using the code in -current or one of the releases ? Makes a
difference.
Can you a) increase the si
Repeatable mbuf leak leading to crash in current of Saturday 20th
November and all snapshots I've taken prior to that since August (i.e.
when I got the ISDN card).
Hardware is BT Highway (AVM PCI) passive ISDN card.
It's triggered when I call my ISDN number from a PSTN telephone, and use
the sta
On 1999-Nov-26 05:09:20 +1100, Greg Lehey wrote:
>I don't suppose it would be that big a deal to remove the old driver,
>but what speaks against leaving it in the tree along with a comment in
>the GENERIC config file saying "if you use antediluvial disk hardware,
>you may prefer to use an old driv
Okay, I've had a couple of reports so far about the if_dc driver which
were mostly positive. I've also gotten some new hardware and did some
more testing and bug fixing:
- Fixed support for non-MII 10/100 cards based on the 21143 chip. This
includes the DEC DE500-BA and the built-in 21143 ether
As I've understood the conclusion of this thread, we want a
sysctl, and we want it open as default. This patch should
do that.
Once Warner nods in the vertical direction it will be committed.
Poul-Henning
Index: kern/kern_exec.c
==
On Wednesday, 24 November 1999 at 19:50:34 +0100, Poul-Henning Kamp wrote:
>
> I belive I have now fully assimilated the bdevs into the cdevs in
> the kernel. This means that we have reached the day where it should
> be of no consequence if you mount /dev/wd0a or /dev/rwd0a.
>
> Vinum users: Don'
On Wednesday, 24 November 1999 at 10:39:44 +0100, Poul-Henning Kamp wrote:
>
> Sørens new ATA driver can handle all IDE disks as far as has been
> tested now, but it doesn't provide bad sector remapping which is
> needed for ESDI and ST-506 disks.
>
> Having two drivers fight for the same class of
[EMAIL PROTECTED] wrote:
> In <[EMAIL PROTECTED]> Maxim Sobolev <[EMAIL PROTECTED]> wrote:
> > [EMAIL PROTECTED] wrote:
> >
> >> What (if any) are the problems with
> >> native FreeBSD ELF Netscape Communicator/Navigator binaries ?
> >
> > AFAIK one major problem exist - ELF version is st
Hi,
had the same trouble with yesterdays' build. Try running cvsup again and
it fixed the problem for me.
Regards,
Ilya
-Original Message-
From: Mikhail A. Sokolov [mailto:[EMAIL PROTECTED]]
Sent: Thursday, November 25, 1999 18:23
To: [EMAIL PROTECTED]
Subject: tcp (nfs?) troubles.
He
Hello,
environment is as follows, PII-Xeon, 1Gb RAM, -current as of yesterday,
nfsd serving some 12 nfsv3,mntudp,rdirplus clients.
Any clues, please?
# > {zz}/var/crash# gdb -k -symbols=/usr/src/sys/compile/WZ/kernel.debug *0
# > GNU gdb 4.18
# > Copyright 1998 Free Software Foundation, Inc.
On 25-Nov-99 [EMAIL PROTECTED] wrote:
> In <[EMAIL PROTECTED]> Maxim Sobolev <[EMAIL PROTECTED]>
> wrote:
>> [EMAIL PROTECTED] wrote:
> Sorry, but my question must be - WHY there still is no
> ELF version of Netscape Communicator for FreeBSD ?
> (FreeBSD's point of view to this problem ?)
In <[EMAIL PROTECTED]> Maxim Sobolev <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] wrote:
>
>> What (if any) are the problems with
>> native FreeBSD ELF Netscape Communicator/Navigator binaries ?
>
> AFAIK one major problem exist - ELF version is still unavailable.
Sorr
Poul-Henning Kamp wrote:
>>> I still hear reports of sporadic calcru() warnings.
>>>
>>> If any of you see these, could you try to see if they correlate
>>> to the uptime of the machine in question ?
>> Should they start or stop when a machine has been running a while? I see
>> neither (negativ
[EMAIL PROTECTED] wrote:
> What (if any) are the problems with
> native FreeBSD ELF Netscape Communicator/Navigator binaries ?
AFAIK one major problem exist - ELF version is still unavailable.
From
ftp://ftp.netscape.com/pub/communicator/english/4.7/unix/unsupported/freebsd/complete_ins
What (if any) are the problems with
native FreeBSD ELF Netscape Communicator/Navigator binaries ?
N.Dudorov
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Hello,
I also get some "calcru" warnings
As my MB is overclocked (100 MHz FSB for Celerons), I had not sent in a
PR
It's four days since I last rebooted and I don't have a single "calcru"
warning (they are usually on the "tail -f rc5.log" process I use to
follow the rc5 crunching).
Tf
36 matches
Mail list logo
