Hi, I would like to know if any owners of Voodoo Graphics boards have
tried using their card with the kernel driver I wrote. I would like to
know how stable the code is for both the Voodoo Graphics and Voodoo II
boards before I make any rash decisions (like tagging it for
RELENG_4). So far I have
On Wed, 7 Feb 2001, Michael C . Wu wrote:
> On Thu, Feb 08, 2001 at 01:56:11AM +0100, Leif Neland scribbled:
> | It seems pkg_update is only usable when installing from packages, not from
> | ports.
>
> Because it is a package update system. If you want to update
> from the ports, use 'pkg_ve
In message <[EMAIL PROTECTED]> Bruce Evans
writes:
: Becuase that's the right place for it. It is kernel sources that don't
: (shouldn't) use it, not kernel configuration files.
Ah. OK. I'll update the UPDATING entry I'm writing then.
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
w
On Wed, 7 Feb 2001, Warner Losh wrote:
> In message <[EMAIL PROTECTED]> Peter Wemm writes:
> : No, FFS_ROOT was unused. We have a generic mountroot mechanism, so we no
> : longer needed to compile the "special" FFS-specific version of the code
> : into autoconf.c. FFS is still optional. For i3
In message <[EMAIL PROTECTED]> Andrea Campi writes:
: While I was reading your patch I was wondering: what's the situation with
: IRQ sharing between PCCard and other devices? Since you're doing such a
: massive rework, wouldn't this be a good time to also deal with this if
: possible (well not no
In message <[EMAIL PROTECTED]> Peter Wemm writes:
: No, FFS_ROOT was unused. We have a generic mountroot mechanism, so we no
: longer needed to compile the "special" FFS-specific version of the code
: into autoconf.c. FFS is still optional. For i386 FFS_ROOT and CD9660_ROOT
: did nothing, and o
On Wed, 7 Feb 2001, Peter Wemm wrote:
> Alfred Perlstein wrote:
> > Does this mean that 'FFS' isn't optional anymore? I mean it probably
> > hasn't been (or never was) but the intention was that to build 4.4BSD
> > you needed _either_ UFS or INET, but you could ditch either one and
> > still bui
On 7 Feb 2001, Dag-Erling Smorgrav wrote:
> Brian Somers <[EMAIL PROTECTED]> writes:
> > Indeed. I've been doing a ``make build'' on an OpenBSD-current vm
> > for three days (probably about 36 hours excluding suspends) on a
> > 366MHz laptop with a ATA33 disk.
>
> Would it be possible for so
On Thu, Feb 08, 2001 at 01:56:11AM +0100, Leif Neland scribbled:
| It seems pkg_update is only usable when installing from packages, not from
| ports.
Because it is a package update system. If you want to update
from the ports, use 'pkg_version -c |sh'
| Even when I first do a make package, and
In message <[EMAIL PROTECTED]>, John Baldwin writes:
>> malloc(48,c0238100,0,c65feb80,0) at malloc+0x2a
>> exit1(c65feb80,0,0,c6623f78,c01fc852) at exit1+0x1b1
>> kthread_suspend(0,c0279a40,0,c022d1ec,a2) at kthread_suspend
>> ithd_loop(0,c6623fa8) at ithd_loop+0x56
>> fork_exit(c01fc7fc,0,c6623f
subscribe
On 07-Feb-01 Andrea Campi wrote:
> On Wed, Feb 07, 2001 at 02:20:43PM -0800, John Baldwin wrote:
>>
>> On 07-Feb-01 Andrea Campi wrote:
>> > Running a kernel I got with this:
>> >
>> >>
>> >> cvs co -D"2001-01-30" src/sys
>> >>
>> >
>> > /ithread.c/1.10/Mon Dec 4 21:15:14 2000//D2001.01.29.
> This is why you're getting the panic in exit1(), but I thought I fixed
> this in intr_machdep.c version 1.47.
>
> revision 1.47
> date: 2001/01/28 17:20:11; author: jake; state: Exp; lines: +2 -1
> Clear intr_nesting_level when an interrupt thread has no more
> handlers and wants to exit, so
> > Sort of killing a mosquito with a missile ;-)
> >
> > Seriously, I will try your patch to confirm it works, then I'll go back
> > to a regular -current kernel and live without ejecting the card...
>
> Keep your kernel.old around. Trust me, the new kernel won't be very usable.
> :)
Better y
On 08-Feb-01 Andrea Campi wrote:
>>
>> My patches may help with this, but they are a lot more than just a single
>> change, they are an overhaul of the interrupt threads code. :) If you are
>> really curious, you can find them at
>> http://www.FreeBSD.org/~jhb/patches/sys.patch. Currently, how
On 08-Feb-01 Alexander N. Kabaev wrote:
>> However, your problems with lpr are a known problem and one
>> that is in the process of being fixed.
> That was me who reported lpr problems in this thread. I just found it curious
> that Andrea's panics look absolutely identical to ones I am getting he
> However, your problems with lpr are a known problem and one
> that is in the process of being fixed.
That was me who reported lpr problems in this thread. I just found it curious
that Andrea's panics look absolutely identical to ones I am getting here when
attempting to use lpr. Do you really th
* Peter Wemm <[EMAIL PROTECTED]> [010207 17:25] wrote:
> Alfred Perlstein wrote:
> > * Peter Wemm <[EMAIL PROTECTED]> [010207 06:29] wrote:
> > > "Leif Neland" wrote:
> > > > While the error-messages are clear, I don't remember seeing any heads-up,
> or
> > > mentioning of this in UPDATI
>
> My patches may help with this, but they are a lot more than just a single
> change, they are an overhaul of the interrupt threads code. :) If you are
> really curious, you can find them at
> http://www.FreeBSD.org/~jhb/patches/sys.patch. Currently, however, they reduce
> the system to a cra
On Wed, 7 Feb 2001, Josef Karthauser wrote:
> On Wed, Feb 07, 2001 at 08:56:14PM +, Josef Karthauser wrote:
> > On Wed, Feb 07, 2001 at 08:26:15PM +0100, Dag-Erling Smorgrav wrote:
> > > Brian Somers <[EMAIL PROTECTED]> writes:
> > > > Indeed. I've been doing a ``make build'' on an OpenBSD-c
Alfred Perlstein wrote:
> * Peter Wemm <[EMAIL PROTECTED]> [010207 06:29] wrote:
> > "Leif Neland" wrote:
> > > While the error-messages are clear, I don't remember seeing any heads-up,
or
> > mentioning of this in UPDATING
> > >
> > > Or is it just me...?
> >
> > No, there wasn't one.
In message <[EMAIL PROTECTED]> Farid Hajji writes:
: > dev.lan.Awfulhak.org kernel log messages:
: > > microuptime() went backwards (18415.166882 -> 18415.158249)
: > > microuptime() went backwards (18490.192910 -> 18490.187579)
: > > microuptime() went backwards (19572.644000 -> 19572.638237)
: >
Looking for the finest handmade gourmet chocolate for that special someone?
http://chocolatejungle.com
Never stored, made fresh everyday, shipped anywhere on the same day you order it!
"Chocolate... 'cause its a jungle out there!"
[You are receiving this email because you opted for specials o
On 08-Feb-01 Andrea Campi wrote:
>>
>> Yes, the intr_nesting_level needs to be dropped before calling
>> kthread_exit().
>> I have this fixed in a different manner locally. You can try that to see if
>> it
>> gets farther. However, your problems with lpr are a known problem and one
>> that
>>
It seems pkg_update is only usable when installing from packages, not from
ports.
Even when I first do a make package, and then try a pkg_update it appears
it does not work correctly, as it wants to uninstall the latest version
before it reinstalls it.
Could pkg_update be a target in bsd.port.mk
>
> Yes, the intr_nesting_level needs to be dropped before calling kthread_exit().
> I have this fixed in a different manner locally. You can try that to see if it
> gets farther. However, your problems with lpr are a known problem and one that
> is in the process of being fixed.
No that was t
> On Wed, Feb 07, 2001 at 02:20:43PM -0800, John Baldwin wrote:
> >
> > On 07-Feb-01 Andrea Campi wrote:
> > > Running a kernel I got with this:
> > >
> > >>
> > >> cvs co -D"2001-01-30" src/sys
> > >>
> > >
> > > /ithread.c/1.10/Mon Dec 4 21:15:14 2000//D2001.01.29.23.00.00
> > >
> > > I g
> Re: the strace db trace above, is it possible that it might be because I
> have:
>
> CFLAGS ?= -O -pipe -mcpu=i686 -march=i686
> COPTFLAGS ?= -O -pipe -mcpu=i686 -march=i686
No, I was getting the same panic with the kernel, compiled with stock flags.
To Unsubscribe: send mail
* Peter Wemm <[EMAIL PROTECTED]> [010207 06:29] wrote:
> "Leif Neland" wrote:
> > While the error-messages are clear, I don't remember seeing any heads-up, or
> mentioning of this in UPDATING
> >
> > Or is it just me...?
>
> No, there wasn't one.. The commit message was pretty clear - You
On Wed, Feb 07, 2001 at 08:56:14PM +, Josef Karthauser wrote:
> On Wed, Feb 07, 2001 at 08:26:15PM +0100, Dag-Erling Smorgrav wrote:
> > Brian Somers <[EMAIL PROTECTED]> writes:
> > > Indeed. I've been doing a ``make build'' on an OpenBSD-current vm
> > > for three days (probably about 36 ho
On Wed, Feb 07, 2001 at 02:20:43PM -0800, John Baldwin wrote:
>
> On 07-Feb-01 Andrea Campi wrote:
> > Running a kernel I got with this:
> >
> >>
> >> cvs co -D"2001-01-30" src/sys
> >>
> >
> > /ithread.c/1.10/Mon Dec 4 21:15:14 2000//D2001.01.29.23.00.00
> >
> > I get:
> >
> > panic: mall
On 07-Feb-01 Andrea Campi wrote:
> Running a kernel I got with this:
>
>>
>> cvs co -D"2001-01-30" src/sys
>>
>
> /ithread.c/1.10/Mon Dec 4 21:15:14 2000//D2001.01.29.23.00.00
>
> I get:
>
> panic: malloc(M_WAITOK) in interrupt context
> Debugger("panic")
> Stopped at Debugger+0x45:
> > panic: malloc(M_WAITOK) in interrupt context
> > Debugger("panic")
> > Stopped at Debugger+0x45: pushl %ebx
> > db> trace
> > Debugger(c02119a3) at Debugger+0x45
> > panic()
> > malloc(48,c0238100,0,c65feb80,0) at malloc+0x2a
> > exit1(c65feb80,0,0,c6623f78,c01fc852) at exit1+0x1b1
On Wed, Feb 07, 2001 at 06:28:42AM -0800, Peter Wemm wrote:
> No, there wasn't one.. The commit message was pretty clear - You are
> reading them, right? We usually do HEAD UP's for stuff that will break
> people pretty badly or get them in trouble (eg: an unviable kernel if the
> instructions a
On Wed, Feb 07, 2001 at 08:26:15PM +0100, Dag-Erling Smorgrav wrote:
> Brian Somers <[EMAIL PROTECTED]> writes:
> > Indeed. I've been doing a ``make build'' on an OpenBSD-current vm
> > for three days (probably about 36 hours excluding suspends) on a
> > 366MHz laptop with a ATA33 disk.
>
> Wo
On Wed, Feb 07, 2001 at 08:26:15PM +0100, Dag-Erling Smorgrav wrote:
> Brian Somers <[EMAIL PROTECTED]> writes:
> > Indeed. I've been doing a ``make build'' on an OpenBSD-current vm
> > for three days (probably about 36 hours excluding suspends) on a
> > 366MHz laptop with a ATA33 disk.
>
> Wo
On 2001-Feb-07 08:13:31 +0100, Rasa Karapandza <[EMAIL PROTECTED]> wrote:
>I receive ctm-src current by e-mail, which I retrive using netscape.
>I save message as plain text then I try uudecode and I alvays get no begin
>line I tryed to edit file but I'm not able to get it work.
CTM mail isn't uu
Thank you for informing us about this. Sending unsolicited e-mail or making
inappropriate commercial newsgroup posts from our web servers is strictly forbidden.
It is also forbidden to promote web sites hosted on our servers in such mailings or
postings. You may see our acceptable use policy
Brian Somers <[EMAIL PROTECTED]> writes:
> Indeed. I've been doing a ``make build'' on an OpenBSD-current vm
> for three days (probably about 36 hours excluding suspends) on a
> 366MHz laptop with a ATA33 disk.
Would it be possible for someone experiencing this slowdown to try to
narrow down t
I want mailling list :)
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
> Running a kernel I got with this:
>
> >
> > cvs co -D"2001-01-30" src/sys
> >
>
> /ithread.c/1.10/Mon Dec 4 21:15:14 2000//D2001.01.29.23.00.00
>
> I get:
>
> panic: malloc(M_WAITOK) in interrupt context
> Debugger("panic")
> Stopped at Debugger+0x45: pushl %ebx
> db> trace
> Debu
On Tue, Feb 06, 2001 at 11:21:12PM +0900, [EMAIL PROTECTED] wrote:
> Today I tried with 4.2-RELEASE (sorry not -current) and,
> 1. Boot up the 4.2-RELEASE with GENERIC kernel.
> 2. Connect MO drive with PC Card SCSI(ncv).
> 3. Insert PC Card without medium in the MO drive.
> 4. The pccardd automat
"Leif Neland" wrote:
> While the error-messages are clear, I don't remember seeing any heads-up, or
mentioning of this in UPDATING
>
> Or is it just me...?
No, there wasn't one.. The commit message was pretty clear - You are
reading them, right? We usually do HEAD UP's for stuff that will
While the error-messages are clear, I don't remember seeing any heads-up, or
mentioning of this in UPDATING
Or is it just me...?
--
>>> Kernel build for GINA started on Mon Feb 5 07:13:06 CET 2001
-
Sources as of a few minutes ago.
cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes
-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi
-g -nostdinc -I- -I. -I../.. -I../../dev -I../../../include
-I../../contrib/dev/acpica/Subsystem/I
Running a kernel I got with this:
>
> cvs co -D"2001-01-30" src/sys
>
/ithread.c/1.10/Mon Dec 4 21:15:14 2000//D2001.01.29.23.00.00
I get:
panic: malloc(M_WAITOK) in interrupt context
Debugger("panic")
Stopped at Debugger+0x45: pushl %ebx
db> trace
Debugger(c02119a3) at Debugger+0x4
With a freshly CVSuped current I get:
===> usr.bin/ncal
cc -O -pipe -Wall -Wmissing-prototypes -fstrict-prototypes -ansi -pedantic
-I/usr/obj/usr/src/i386/usr/include -c /usr/src/usr.bin/ncal/ncal.c
/usr/src/usr.bin/ncal/ncal.c: In function `printeaster':
/usr/src/usr.bin/ncal/ncal.c:390: wa
I can easily reproduce the panic on my -CURRENT Athlon box by just starting any
print job. Other that that, the system seems to be running OK, i.e. no panics
occur unless some lpr activity is involved. Here is the stack dump:
#9 0xc02a9fbc in trap (frame={tf_fs = 24, tf_es = 16, tf_ds = 16,
> > Ok, I will. Can you give me a date I should try going back to, without kernel
> > getting out of sync with my world?
>
> A kernel on the 30th or so should work fine with an up to date world.
Thought I had tried this...
FreeBSD 5.0-CURRENT #0: Wed Jan 10 11:00:55 CET 2001
root@brian:/usr
49 matches
Mail list logo
