On Tue, 16 Jul 2002, John Baldwin wrote:
> On 17-Jul-2002 Bruce Evans wrote:
> > This change and the break after the panic() are bogus. panic() "never"
> > returns, and the compiler knows this. Unfortunately, the RESTARTABLE_PANICS
> > option subverts the semantics of panic(), so panic() someti
On Thu, Jul 11, 2002 at 03:42:49PM -0600, Eric Anholt wrote:
> perl installation. Shouldn't USE_PERL5 depend on ${LOCALBASE}/bin/perl
> on -current rather than just the existence of a binary called "perl" in
> the path?
Assuming the perl wrapper returns different errorcodes if it finds a working
just committed a fix for this.
The MFC will come shortly (note that there is no such a bug in
-stable unless you use ipfw2 which is outside of the tree; the MFC
will be just to keep the two files in sync).
cheers
luigi
On Wed, Jul 17, 2002 at 12:45:45AM +0900, [EMAIL PROTECTED] w
Hi!
It's very surprising for me, but /usr/ports/print/freetype2 doesn't
build on -current on my Alpha box because GNU make dumps core after signal 11
after GNU configure has finished.
Stack trace given by gdb shows the following:
(gdb) set heuristic-fence-post 10
(gdb) bt
#0 0x12003
> : 1) When trying to insert a Cisco Aironet 340 adapter, I get thrown to
> the : db> prompt after it has found the card (which it seems to do
> nicely). If I : boot with it inserted, I only get to the detection, then
> the boot stops. At : boot up dmesg says the following on the bridge :
> :
--
>>> Rebuilding the temporary build tree
--
>>> stage 1: bootstrap tools
--
>>> stage 2: cleaning up the object tree
On Wed, 2002-07-17 at 05:54, Dag-Erling Smorgrav wrote:
> ===> sbin/newfs
> /usr/home/des/tinderbox/sparc64/src/sbin/newfs/mkfs.c: In function `fsinit':
> /usr/home/des/tinderbox/sparc64/src/sbin/newfs/mkfs.c:711: structure has no member
>named `di_createtime'
> *** Error code 1
>
> Stop in /us
On (2002/07/17 06:49), Rob Hughes wrote:
> > ===> sbin/newfs
> > /usr/home/des/tinderbox/sparc64/src/sbin/newfs/mkfs.c: In function `fsinit':
> > /usr/home/des/tinderbox/sparc64/src/sbin/newfs/mkfs.c:711: structure has no member
>named `di_createtime'
> > *** Error code 1
> >
> > Stop in /usr/h
On 17-Jul-2002 Bruce Evans wrote:
> On Tue, 16 Jul 2002, John Baldwin wrote:
>
>> On 17-Jul-2002 Bruce Evans wrote:
>> >> mtx_lock_spin(&sched_lock);
>> >> if (cold || panicstr) {
>> >> /*
>> >> * After a panic, or during autoconfiguration,
>> >>
On 17-Jul-2002 Bruce Evans wrote:
> On Tue, 16 Jul 2002, John Baldwin wrote:
>
>> On 17-Jul-2002 Bruce Evans wrote:
>> > This change and the break after the panic() are bogus. panic() "never"
>> > returns, and the compiler knows this. Unfortunately, the RESTARTABLE_PANICS
>> > option subverts
I've seen some of the past postings relating to prolems experienced with
lib/csu, but the only file in my csu director is the Makefile. This error
has been with me for quite some time. I've made sure to do a make cleandir
prior to trying to build the world. I have built the latest GCC 3.1 from
th
Just upgraded my laptop to the latest -CURRENT ... everything boots fine,
but my ethernet no longer exists (it worked great on my June 6th kernel)
...
I'm using NEWCARD support in the kernel, and if_ed is loaded according to
kldstat ...
I've searched Google, and nadda there ... known problem, o
On Tue, Jul 16, 2002 at 11:39:41PM -0600, Eric Anholt wrote:
> > I thought the whole point of Wraphelp.c was that the person who
> > runs the machine (whatever machine X is being installed on) has
> > to obtain that file, so they would have to explicitly verify that
> > they -- personally -- have
On (2002/07/17 01:52), Dima Dorfman wrote:
> The devfs(8) manual page is a pretty good reference of the existing
> features and semantics, but it lacks polish needed to be able to serve
> as an introduction.
Actually, I think it's brilliant.
The only nits are the weird sections, which made it h
On Wed, Jul 17, 2002 at 09:57:41AM -0700, Bakul Shah wrote:
Terry suggested:
> > I believe setting DISABLE_PSE in the config file and rebuilding
> > will make this go away.
>
> Terry, thanks for the suggestion but that didn't do it.
Ok, so it's time to speculate a bit more about this.
Although
> I believe setting DISABLE_PSE in the config file and rebuilding
> will make this go away.
Terry, thanks for the suggestion but that didn't do it.
Time to review recent changes and single step the kernel.
BTW, how do you stop the kernel before it panics? It
panics so early that there is no time
Bakul Shah wrote:
> > I believe setting DISABLE_PSE in the config file and rebuilding
> > will make this go away.
>
> Terry, thanks for the suggestion but that didn't do it.
This surprises me. I thought it would be the result of Peter's
recent pmap changes, and the fact that there is a bad prob
Szilveszter Adam wrote:
> Ok, so it's time to speculate a bit more about this.
>
> Although I have been seeing this panic since Sunday, only one other
> person has reported it so far. Although it may be that this is due to
> the fact that developers do not run up-to-date -CURRENT and hence do not
On Wed, Jul 17, 2002 at 07:38:22PM +0200, Szilveszter Adam wrote:
> Bakul mentioned that the panic happens on a PPro. For me, it's a PII. I
> am using a CPUTYPE setting of "p2" in /etc/make.conf. This gets
> converted to a "-march=pentiumpro" on the actual compile line. This may
> be the same for
This worked 3 days ago but I just upgraded to -CURRENT from today
and its not quite working now. If you have tcp6 lines in your
inetd.conf but do not have IPv6 enabled in the kernel your inetd
will stop adding services after it encounters the first line with
a tcp6 in it:
mysystem# inetd -d
ADD
On Wed, Jul 17, 2002 at 11:35:35AM -0700, Terry Lambert wrote:
> My bet on the root cause, if I am correct, means that if you change
> the amount of physical RAM installed in the machine, the problem will
> go away, and that the problem is probably rare because it depends on
> certain things that
Szilveszter Adam wrote:
> On Wed, Jul 17, 2002 at 11:35:35AM -0700, Terry Lambert wrote:
> > My bet on the root cause, if I am correct, means that if you change
> > the amount of physical RAM installed in the machine, the problem will
> > go away, and that the problem is probably rare because it d
Hey all (ab)users of -current. Please try to work on getting -current
as stabilized as possible in the next few days and hold off on any
large changes until after re@ creates the Perforce branch for DP2 on
Friday. Of course, bug fixes can be merged from current back into the
DP2 branch before DP
John Baldwin wrote:
> Of course, bug fixes can be merged from current back into the
> DP2 branch before DP2 goes out if needed, but we'd like to try and get
> it as close to right as possible the first time. :)
A working fsck would surely be a good thing for DP2. :) See thread on
current@.
Reg
In message: <[EMAIL PROTECTED]>
Dima Dorfman <[EMAIL PROTECTED]> writes:
: Questions and comments are most welcome. In particular, if you use
: this with removable devices (e.g., USB), I'd like to hear about it. I
: haven't had much of an opportunity to test this with different
: rem
John Baldwin wrote:
> Hey all (ab)users of -current. Please try to work on getting -current
> as stabilized as possible in the next few days and hold off on any
> large changes until after re@ creates the Perforce branch for DP2 on
> Friday. Of course, bug fixes can be merged from current back i
Hello,
It seems like PCI_ENABLE_IO_MODES makes FreeBSD work on a lot of portable
computers and possible newer desktop computers with lazy BIOS'es.
As it is now, it is quite a hassle to complete something as simple as a
network install of FreeBSD on an affected computer.
My question is, when will
On Tue, Jul 16, 2002 at 07:14:05PM -0400, John Baldwin wrote:
>
> This is because USB network drivers are possibly doing bad things. Either
> that or the network locking is making bogus assumptions about what
> device driver routines will and will not do. Probably the network stack
> should not
> That there could be a real error in that code surprises me, since
> Peter really knows what he's doing, even if that low in the
> hardware, there are undocumented interactions that even Intel's
> errata doesn't seem to know about.
Turns out the workaround is to use DISABLE_PG_G.
Two things mad
On Thu, Jul 18, 2002 at 12:58:55AM +0200, Frode Nordahl wrote:
>
> It seems like PCI_ENABLE_IO_MODES makes FreeBSD work on a lot of portable
> computers and possible newer desktop computers with lazy BIOS'es.
> As it is now, it is quite a hassle to complete something as simple as a
> network inst
At 11:42 PM +0200 7/17/02, John Angelmo wrote:
>John Baldwin wrote:
>>Hey all (ab)users of -current. Please try to work on getting -current
>>as stabilized as possible in the next few days and hold off on any
>>large changes until after re@ creates the Perforce branch for DP2 on
>>Friday.
>
>Well
On Wednesday, July 17, 2002, at 10:24 AM, Marc G. Fournier wrote:
>
> Just upgraded my laptop to the latest -CURRENT ... everything boots
> fine,
> but my ethernet no longer exists (it worked great on my June 6th kernel)
> ...
>
> I'm using NEWCARD support in the kernel, and if_ed is loaded acco
I just thought I'd mention a little problem I ran into, because I had
not seen anyone else mention it. It might be specific to my PC
hardware, and actually it was pretty simple to solve once I took
the time to look into it. I don't know that anything needs to be
done about any of this, but perha
On Wed, 2002-07-17 at 18:40, Garance A Drosihn wrote:
> I have a Matrox G400 Dual Head 32mb AGP card running on a dual
> Pentium III system, and I have been using XFree86-4 on my system for
> testing -current. This worked fine for months, and I still have a
> snapshot of -current from about Apri
FreeBSD Gurus,
I would like to suggest for the FreeBSD team to please consider
disabling support for ssh1 in the default configuration of sshd starting
with FreeBSD 5.0 for the following reasons:
1) The ssh1 protocol is fundamentally insecure. The protocol uses a CRC
where a MAC is needed, permit
Eric Anholt wrote:
> This looks like the classic error of the agp module having been loaded
> by the drm because it's required, but agp doesn't probe/attach because
> a generic bridge driver has already claimed the agp device.
I doubt that would be a problem as long as it came with a patch to th
On Wed, 2002-07-17 at 20:59, Peter Wemm wrote:
> Eric Anholt wrote:
>
> > This looks like the classic error of the agp module having been loaded
> > by the drm because it's required, but agp doesn't probe/attach because
> > a generic bridge driver has already claimed the agp device.
>
> I doubt
--
>>> Rebuilding the temporary build tree
--
>>> stage 1: bootstrap tools
--
>>> stage 2: cleaning up the object tree
I build/install world last night
after reboot, one of my filesystem is broken (it uses soft-updates)
when I run fsck on it, it said :
cannot find filesystem superblock
** /dev/da0s3e
LOOK FOR ALTERNATE SUPERBLOCKS? yes
USING ALTERNATE SUPERBLOCK AT 32
numdirs is zero, try using an alternate
In message: <[EMAIL PROTECTED]>
"Frode Nordahl" <[EMAIL PROTECTED]> writes:
: My question is, when will PCI_ENABLE_IO_MODES be default?
It is a tiny piece of a larger puzzle that will be fixed as we do
proper resource allocation now that the BIOS specifications have been
changed by MS
40 matches
Mail list logo
