On Mon, Dec 25, 2000 at 04:55:08PM -0800, Mike Smith wrote:
> > Trying to upgrade an existing 3.4 system to 4.2
> > failed due to kernel.GENERIC not having mcd0 built in
> > anymore (MITSUMI CDROM) :-(
> >
> > Please add that back again.
>
> No. The Matsushita/Mitsumi/Sony CDROM interfaces hav
> > > Please add that back again.
> >
> > No. The Matsushita/Mitsumi/Sony CDROM interfaces have gone the way of
> > the 3c501. The drivers are there, and if you're really desperate, you're
> > welcome to try them, but they're not supported install devices anymore.
> >
> > Note that it's triv
Hi Matt
I'm getting a reliable panic on CURRENT (2000/12/26) with INVARIANTS
set. I suppose I could "fix" this by taking out INVARIANTS, but it
seems to make more sense to try to get it fixed.
The panic() is "freeing free entry", and the traceback (minus most
of the numbers) is:
panic
zerror
zf
> Since we are on the subject of ACPI, it is working great except for one
> thing, it can't attach my sound card to the pcm device (does that sound
> correct?). It definitely sees it:
>
> unknown: can't assign resources
This would suggest that something else is taking one or more of the
resour
> > We got old Mylex DAC960PD-Ultra-raid-adapter and have tried to use it
> > with FreeBSD 4.2-stable and 5.0-current. Adapter is configured with
> > three luns 5+5*9G, 8+8*9G (raid5) and 1+1*2G (mirrored boot disk).
> > All 9G disks are quite old Seagate Barracuda 9 disks ST19171W. System
>
Mike Smith wrote:
>
> > > > Please add that back again.
> > >
> > > No. The Matsushita/Mitsumi/Sony CDROM interfaces have gone the way of
> > > the 3c501. The drivers are there, and if you're really desperate, you're
> > > welcome to try them, but they're not supported install devices anymore.
I'll try to summarise the position so far:
1) Legacy a.out executable support is broken for a subset (size unknown)
of such executables.
2) We can ignore this or repair this.
3) We can build a new binary or just look around on old 3.x CDs until
we find one that works.
4) We can generate a work
:Hi Matt
:
:I'm getting a reliable panic on CURRENT (2000/12/26) with INVARIANTS
:set. I suppose I could "fix" this by taking out INVARIANTS, but it
:seems to make more sense to try to get it fixed.
:
:The panic() is "freeing free entry", and the traceback (minus most
:of the numbers) is:
:
:panic
>From the keyboard of Mike Smith:
> It is a space problem. You can trivially put modules on a third floppy,
> but you would first need to turn the matcd driver into a module, which
> you are encouraged to do as you appear to be one of the three people left
> in the world with a functioning Ma
On Wed, Dec 27, 2000 at 02:01:24AM +1000, Stephen McKay wrote:
> I'll try to summarise the position so far:
>
> 1) Legacy a.out executable support is broken for a subset (size unknown)
> of such executables.
Define "legacy". I have been speaking specifically about FreeBSD 2.2
support. That jus
Akinori MUSHA wrote:
>
> Seems you broke an error message of src/etc/netstart when committing a
> series of quoting style fixes.
So I did, thanks for pointing it out. :) It's fixed now.
Doug
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the bod
On Tue, Dec 26, 2000 at 02:00:54PM +0200, Mark Murray wrote:
> I'm getting a reliable panic on CURRENT (2000/12/26) with INVARIANTS
> set. I suppose I could "fix" this by taking out INVARIANTS, but it
> seems to make more sense to try to get it fixed.
Do you have NFS compiled in to the kernel? I
:Do you have NFS compiled in to the kernel? I've had trouble using
:INVARIANTS in the kernel and NFS as a module many times - it always
:panics in the zone allocation stuff.
:
:(Either you always need to compile modules with the same INVARIENTS
:options as the kernel, or we need to fix INVARIENTS
Matt Dillon <[EMAIL PROTECTED]> writes:
> I think the only real solution is to rip out the externally visible
> zalloc/zfree inlines and replace them with real routines. I will happily
> do this, those inlines have always been an eyesore to me and the
> performance benefit is mini
:
:Matt Dillon <[EMAIL PROTECTED]> writes:
:> I think the only real solution is to rip out the externally visible
:> zalloc/zfree inlines and replace them with real routines. I will happily
:> do this, those inlines have always been an eyesore to me and the
:> performance benefit
Matt Dillon <[EMAIL PROTECTED]> writes:
> We can't just go do an end-run around the established API as a
> hack around the problem.
I fail too se how my suggestion would change the API at all, but in
case I was unclear, diffs are below.
/assar
Index: vm_zone.c
:Matt Dillon <[EMAIL PROTECTED]> writes:
:> We can't just go do an end-run around the established API as a
:> hack around the problem.
:
:I fail too se how my suggestion would change the API at all, but in
:case I was unclear, diffs are below.
:
:/assar
:
Well, yes... that's essential
Matt Dillon <[EMAIL PROTECTED]> writes:
> Well, yes... that's essentially what I suggested. You didn't say
> anything about removing the externalized inlines, which is what you
> do in your patch. Looks like a fine patch to me.
Except it didn't work. Now here's a patch that survive
:--=-=-=
:
:Matt Dillon <[EMAIL PROTECTED]> writes:
:> Well, yes... that's essentially what I suggested. You didn't say
:> anything about removing the externalized inlines, which is what you
:> do in your patch. Looks like a fine patch to me.
:
:Except it didn't work. Now here's a
[NX}XI
¢ë`ñÈíÞÌGb`ªWª¯³êÄA
³¿Å©êéæB
http://216.101.214.74/omankoheaven/
·²[¢¾©çÉÈÉÅà©ÄÝÄËB
½Ü±
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
[Noted that you don't like being cc:'d, David. On the other hand,
I like to be kept in the cc: list.]
On Tuesday, 26th December 2000, "David O'Brien" wrote:
>On Wed, Dec 27, 2000 at 02:01:24AM +1000, Stephen McKay wrote:
>> I'll try to summarise the position so far:
>>
>> 1) Legacy a.out execu
> On Tue, Dec 26, 2000 at 02:00:54PM +0200, Mark Murray wrote:
>
> > I'm getting a reliable panic on CURRENT (2000/12/26) with INVARIANTS
> > set. I suppose I could "fix" this by taking out INVARIANTS, but it
> > seems to make more sense to try to get it fixed.
>
> Do you have NFS compiled in to
22 matches
Mail list logo
