> > P.S. This also reminds me that FreeBSD is non-standard relative
> > to Linux and all of the major vender commercial Unices in that a disallowed
> > access, such as a write to a read-only region of memory, generates
> > a SIGBUS rather than a SIGSEGV.
>
> Yes, this even violates the 1996 POSI
Marcel Moolenaar wrote:
>
> > But this still doesn't entirely solve the problem. You still have
> > to build and install a new kernel before installing the world.
> > While this is typically what most -current folks do anyways, it
> > still prevents backing up to a previous kernel after the inst
On 1 Okt, Poul-Henning Kamp wrote:
>
> Please boot your old system and email the output from
> fdisk da0
> disklabel da0
If it matters: It's a dangerous dedicated disk.
(72) netchild@ttyp0 > fdisk da0
*** Working on device /dev/rda0 ***
parameters extracted from in-core dis
"Daniel C. Sobral" wrote:
>
> Marcel Moolenaar wrote:
> >
> > You can easily install a kernel as part of the upgrade process. A
> > complete upgrade would be something like:
> >
> > 1. Verify and/or install cross-compilation tools
> > 2. Build world
> > 3. Build kernel
> > 4. Copy tools that are
On Wed, Sep 29, 1999 at 11:05:49PM +1200, Joe Abley wrote:
> On Wed, Sep 29, 1999 at 12:02:09PM +0200, Mark Murray wrote:
> > There is breakage in the new FICL. This fixes it...
> >
> > [awk diff]
>
> I remember a long time ago someone asked me to make some modifications
> to softcore.awk to com
Ok, I've committed what I belive is a fix for the problem. It was not
the locking as Bruce suggested, although his suggestion still has a point,
it was si_iosize_max which was uninitialized, which confuses minphys
and subsequently various other stuff.
--
Poul-Henning Kamp FreeBSD co
On Sat, 2 Oct 1999, David O'Brien wrote:
> > > P.S. This also reminds me that FreeBSD is non-standard relative
> > > to Linux and all of the major vender commercial Unices in that a disallowed
> > > access, such as a write to a read-only region of memory, generates
> > > a SIGBUS rather than a
Hi,
panic: free vnode isn't
with yesterday's kernel (cvsup Fri Oct 1 04:02:32 BST 1999), on an SMP
system early on in buildworld.
Skeletal traceback (must get serial console fixed up):
panic
getnewvnode
ffs_vget
ufs_lookup
ufs_vnoperate
vfs_cache_lookup
ufs_vnoperate
lookup
namei
unlink
sysca
I, too, am having problems with the CAM code; but my SCSI drive(s) are NOT
boot drives!
Attempting ANY transfer on the drive evokes this response:
Oct 2 21:34:29 bsd300 /kernel: (da0:ncr0:0:3:0): extraneous data discarded.
Oct 2 21:34:29 bsd300 /kernel: (da0:ncr0:0:3:0): COMMAND FAILED (9 0)
@0
On Fri, Oct 01, 1999 at 05:57:14PM -0500, Chris Costello wrote:
>Try ``gdb cvsup cvsup.core''
jos:/tmp# file cvsup.core
cvsup.core: lif file
jos:/tmp# gdb /usr/local/bin/cvsup cvsup.core
GNU gdb 4.18
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the GNU Genera
CVsup'ed current 2 oct 10 GMT.
made and installed kernel, reboot.
make world
went for groceries(sp?)
When i came back, screen in powersave, hit return (too many times)
screen only showing "db>"
typed panic to reboot.
Now system is hosed: it fails in rc.init (thereabout), because it claims /bin
At 01:19 PM 10/02/99 +0200, Poul-Henning Kamp wrote:
>Ok, I've committed what I belive is a fix for the problem. It was not
>the locking as Bruce suggested, although his suggestion still has a point,
>it was si_iosize_max which was uninitialized, which confuses minphys
>and subsequently various
It fixed my AHC problem with ASUS P6 MB.
Thank you!!
From: Poul-Henning Kamp <[EMAIL PROTECTED]>
phk> Ok, I've committed what I belive is a fix for the problem. It was not
phk> the locking as Bruce suggested, although his suggestion still has a point,
phk> it was si_iosize_max which was unin
"Daniel C. Sobral" wrote:
> Marcel Moolenaar wrote:
> >
> > > But this still doesn't entirely solve the problem. You still have
> > > to build and install a new kernel before installing the world.
> > > While this is typically what most -current folks do anyways, it
> > > still prevents backing
[CC: trimmed to -current]
> > > > But this still doesn't entirely solve the problem. You still have
> > > > to build and install a new kernel before installing the world.
> > > > While this is typically what most -current folks do anyways, it
> > > > still prevents backing up to a previous kerne
On Sat, 2 Oct 1999, Rodney W. Grimes wrote:
> > Read my lips: *NEVER* do a 'make world' until you've got a new bootable
> > kernel. You can go back to a 'kernel.old' in 5 seconds. Undoing a 'make
> > world' because a new kernel doesn't workd is a major drama.
>
> These folks are 100% correct
"Rodney W. Grimes" wrote:
>
> These folks are 100% correct, some place some where we made a mistake
> and are telling users to do things in the wrong order. It might have
> even been myself that caused this, I just can't recall when and who
> said to build the world before building the kernel.
On Sat, Oct 02, 1999 at 09:45:30AM -0700, Rodney W. Grimes wrote:
> > Read my lips: *NEVER* do a 'make world' until you've got a new bootable
> > kernel. You can go back to a 'kernel.old' in 5 seconds. Undoing a 'make
> > world' because a new kernel doesn't workd is a major drama.
>
> These
sft updates?
is it possible the filesystem got totally full?
(that combination prooduces a bug that kirk is looking at...)
julian
On Sat, 2 Oct 1999, Bob Bishop wrote:
> Hi,
>
> panic: free vnode isn't
>
> with yesterday's kernel (cvsup Fri Oct 1 04:02:32 BST 1999), on an SMP
> system early
On Fri, 1 Oct 1999, Daniel Eischen wrote:
> Soren Schmidt wrote:
> > It seems Daniel M. Eischen wrote:
> > >
> > > More info on the kernel hang.
> > >
> > > Removing pnp from the kernel configuration will allow me to boot
> > > and successfully detects my pnp modem. So the culprit seems to
> >
> When did we go wrong and start saying that users should build the world
> before building a new kernel?If it was ``I'' that said it, I full
> retract any such statement, I was WRONG!. It may have been said in the
> patchkit days, or very early FreeBSD 1.x.
It's been "common culture" ever s
David O'Brien wrote:
>> > P.S. This also reminds me that FreeBSD is non-standard relative
>> > to Linux and all of the major vender commercial Unices in that a disallowed
>> > access, such as a write to a read-only region of memory, generates
>> > a SIGBUS rather than a SIGSEGV.
>>
>> Yes, this
At 10:58 am -0700 2/10/99, Julian Elischer wrote:
>sft updates?
Yes
>is it possible the filesystem got totally full?
>(that combination prooduces a bug that kirk is looking at...)
No, There's about 700M free on /usr/obj, and it was in the early
tree-cleaning phase anyway.
I forgot to mention t
On Sat, Oct 02, 1999 at 02:05:37PM +0200, Leif Neland wrote:
> Now system is hosed: it fails in rc.init (thereabout), because it claims /bin/sh:
>Exec format error.
> I can't enter single user mode either for same reason.
What about using /bin/csh for single user mode?
--
B.Walter
On Sat, 2 Oct 1999, Bob Bishop wrote:
> >
> >On Sat, 2 Oct 1999, Bob Bishop wrote:
> >
> >> Hi,
> >>
> >> panic: free vnode isn't
> >>
> >> with yesterday's kernel (cvsup Fri Oct 1 04:02:32 BST 1999), on an SMP
> >> system early on in buildworld.
> >>
> >> Skeletal traceback (must get serial co
Doug Rabson wrote:
>
> > Here, it might be the opposite. The normal sio probes pick up the
> > pnp modem just fine, and then perhaps pnp comes along and trounces
> > on what has already been setup/configured.
>
> Could you try this patch for me. It attempts to disable pnp devices before
> runni
:On Sat, Oct 02, 1999 at 02:05:37PM +0200, Leif Neland wrote:
:> Now system is hosed: it fails in rc.init (thereabout), because it claims /bin/sh:
:Exec format error.
:> I can't enter single user mode either for same reason.
:
:What about using /bin/csh for single user mode?
:
:--
:B.Walter
On 2 October 1999 at 9:45, "Rodney W. Grimes" <[EMAIL PROTECTED]> wrote:
> When did we go wrong and start saying that users should build the world
> before building a new kernel?If it was ``I'' that said it, I full
> retract any such statement, I was WRONG!. It may have been said in the
> pa
>
> > Just how much code will break?
>
> Boehm-gc, maybe. Modula-3, maybe. I can't remember whether it
> catches both signals or just SIGBUS.
I believe electric-fence would change as well.
- Dave R. -
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current
On Sat, 2 Oct 1999, Daniel M. Eischen wrote:
> What's the unknown0? Shouldn't that be sio2? Do we need the logical
> device ID?
Yes. Try adding 0x8024b04e to sio.c
--
| Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD |
| [EMAIL PROTECTED] | 2 x '84 Volvo 245DL
Matthew N. Dodd wrote:
> On Sat, 2 Oct 1999, Daniel M. Eischen wrote:
> > What's the unknown0? Shouldn't that be sio2? Do we need the logical
> > device ID?
>
> Yes. Try adding 0x8024b04e to sio.c
OK, I originally did that to no avail, but I didn't make the change to
the correct file (sys/isa
On Sat, 2 Oct 1999, Matthew Dillon wrote:
>
> Also, when all else fails try booting from a FreeBSD CD. Altneratively
> it may be possible to boot the normal kernel and use a FreeBSD CD as root
> by typing 'boot /kernel -C' (or -c, I forget which).
>
It's -C
Note however that -C is
On Sat, 2 Oct 1999, Matthew Dillon wrote:
>
> :On Sat, Oct 02, 1999 at 02:05:37PM +0200, Leif Neland wrote:
> :> Now system is hosed: it fails in rc.init (thereabout), because it claims /bin/sh:
>Exec format error.
> :> I can't enter single user mode either for same reason.
> :
> :What about
On Sun, Oct 03, 1999 at 09:42:45AM +1000, Bruce Evans wrote:
>
> I think the POSIX way is to use an auxiliary error code in siginfo_t to
> distinguish the causes of the signal. This only works for SA_SIGINFO
> handlers. We do something similar using the signal code of 3-arg signal
> handlers.
>
I have a very wierd case of a Dual PPRo SuperMicro board (two PCI
busses) and when running -stable, I/O through boards on the second PCI bus
is *really* delayed.
Any notion on this? -verbose boot stuff below...
-matt
Copyright (c) 1992-1999 FreeBSD Inc.
Copyright (c) 1982, 1986, 1989, 1991, 19
> >> > P.S. This also reminds me that FreeBSD is non-standard relative
> >> > to Linux and all of the major vender commercial Unices in that a disallowed
> >> > access, such as a write to a read-only region of memory, generates
> >> > a SIGBUS rather than a SIGSEGV.
> >>
> >> Yes, this even viol
Bruce Evans wrote:
>
>> first implement the SA_SIGINFO support to the point where it could
>> accomplish that before changing SIGBUS to SIGSEGV. I think that makes
>> sense.
>
> SA_SIGINFO is implemented now.
Oh, when I checked it a couple of days ago it seemed like it wasn't
fully implemented
On Sun, Oct 03, 1999 at 01:48:12AM +0200, Leif Neland wrote:
>
> /bin/csh: Exec format error
>
Even if you boot the old kernel?
That's strange...
--
B.Walter COSMO-Project http://www.cosmo-project.de
[EMAIL PROTECTED] Usergroup[EMAIL
> On 2 October 1999 at 9:45, "Rodney W. Grimes" <[EMAIL PROTECTED]> wrote:
>
> > When did we go wrong and start saying that users should build the world
> > before building a new kernel?If it was ``I'' that said it, I full
> > retract any such statement, I was WRONG!. It may have been said i
< said:
> More details on the POSIX signal numbers: SIGBUS is mainly for accesses
> beyond the end of mmap()ed objects. It's not clear what this means in
> an address space with multiple mmap()ed objects and/or non-mmap()ed
> objects.
`Beyond the end of the object' refers to the situation where
We've added quite a few new CVSup mirror sites this year. I thought
it might be a good idea to list them, in the hope that some of you
would help spread the load by switching to them for your CVSup
updates.
One common misconception is that cvsup(N+1).FreeBSD.org is somehow
less up-to-date than o
> > Justin has said that porting old scsi aic to cam wouldn't be too hard,
> > but would still provide a level of buginess that is too high..
> > Otherwise, i'd have done that a long time ago...
>
> I don't know, I have never used the aic driver before. It would seem
> that aic users were not tha
"Daniel C. Sobral" wrote:
> "Rodney W. Grimes" wrote:
> >
> > These folks are 100% correct, some place some where we made a mistake
> > and are telling users to do things in the wrong order. It might have
> > even been myself that caused this, I just can't recall when and who
> > said to build t
Richard Wackerbarth wrote:
> Why isn't the kernel BUILT automatically as a part of "buildworld"?
> Except for the fact that the object directory is in the wrong place, why isn't
> a kernel just like any other module?
>
This may be difficult. Which kernel do you build? I use
the same source tre
Peter Wemm wrote:
>
> For things like config etc, that particular problem is almost over. It
> does very VERY little now and I can't see that we'll have incompatable
> changes (apart from shooting it and using a lightweight kernel/module build
> organizer/manager/whatever). All config(8) does a
45 matches
Mail list logo
