Re: s4bios

2003-06-05 Thread Stanislav Grozev
On Wed, Jun 04, 2003 at 08:37:11AM -0600, M. Warner Losh wrote: > In message: <[EMAIL PROTECTED]> > Mark Santcroos <[EMAIL PROTECTED]> writes: > : Is there anyone that has succesfully used "acpiconf -s 4"? > > Fails on my Dell i8000, but that's because I don't have a suspend > partitio

Re: Update to the DRM

2002-07-14 Thread Stanislav Grozev
On Fri, Jul 12, 2002 at 05:29:01PM -0600, Eric Anholt wrote: > > well if you give me details, i could try > > cvs -d:pserver:[EMAIL PROTECTED]:/cvsroot/dri login > cvs -d:pserver:[EMAIL PROTECTED]:/cvsroot/dri -z3 co -P xc > ok i'll try :-) I am not a kernel hacker, so MMMV (my mileage my va

Re: Update to the DRM

2002-07-12 Thread Stanislav Grozev
On Fri, Jul 12, 2002 at 01:06:31PM -0600, Eric Anholt wrote: > That's a Mach64-based chip, so the r128 driver won't work with it. i see... > Luckily for you, support for mach64s (Rage Pros specifically, which I > think your chip is) is being worked on in DRI CVS, so it should be > available soo

Re: Update to the DRM

2002-07-12 Thread Stanislav Grozev
On Fri, Jul 12, 2002 at 09:56:50AM +0200, Stanislav Grozev wrote: > > Missed the N on my cvs diff -uN. New patch is uploaded, including not > > stripping FreeBSD ID tags. > > http://people.freebsd.org/~anholt/dri/files/currentdrm-20020711.diff > > thanks, i'll tr

Re: Update to the DRM

2002-07-12 Thread Stanislav Grozev
On Thu, Jul 11, 2002 at 12:25:08PM -0600, Eric Anholt wrote: > On Thu, 2002-07-11 at 03:19, Stanislav Grozev wrote: > > i wanted to try the pci rage 128, as i have a sony vaio with it (i think) :-) > > so, the patch applied cleanly, but then, make buildkernel complains ab

Re: Update to the DRM

2002-07-11 Thread Stanislav Grozev
On Wed, Jul 10, 2002 at 05:23:25PM -0600, Eric Anholt wrote: > On Wed, 2002-07-10 at 17:17, Eric Anholt wrote: > > I've posted a diff to the DRM at > > http://people.freebsd.org/~anholt/dri/files/currentdrm-20020709.ta > > Evolution's "send" button is way too big. > > http://people.freebsd.org/

Re: GCC3.1 internal compiler error when compiling XFree86-4-libraries

2002-06-11 Thread Stanislav Grozev
On Mon, Jun 10, 2002 at 09:18:32PM +0200, Szilveszter Adam wrote: > Sorry David, but I experienced the same thing. No matter if I used the > base system c++ compiler, or the latest gcc31 port. The problem is all > the more interesting, because X worked for me fine, no matter what > compiler I used

Re: My postgresql7 not working for new gcc

2002-06-10 Thread Stanislav Grozev
On Mon, Jun 10, 2002 at 07:02:14AM -0700, Terry Lambert wrote: > Stanislav Grozev wrote: > That's ugly. well, i _did_ mention that it's a messy and a temporary solution, but at least it gets postgresql (and many others) to compile and run fine. > > Since it's

Re: My postgresql7 not working for new gcc

2002-06-10 Thread Stanislav Grozev
On Wed, Jun 05, 2002 at 04:35:40AM -0700, Shizuka Kudo wrote: > checking for readline/readline.h... no > checking for readline.h... no > checking for readline/history.h... no > checking for history.h... no > checking for openssl/ssl.h... no > configure: error: header file is > required for OpenS

Re: GCC3.1 internal compiler error when compiling XFree86-4-libraries

2002-06-08 Thread Stanislav Grozev
On Sat, Jun 08, 2002 at 10:11:13PM +0900, Yamada Ken Takeshi wrote: > (expr_list:REG_DEAD (reg:SF 8 st(0) [76]) > (nil))) > ../../../../extras/Mesa/src/trans_tmp.h:124: Internal compiler error in >failed_reload, at reload1.c:5050 > Please submit a full bug report, > with preprocessed

Re: GCC3.1 internal compiler error when compiling XFree86-4-libraries

2002-06-04 Thread Stanislav Grozev
On Tue, Jun 04, 2002 at 07:08:32AM -0500, Michael D. Harnois wrote: > > > #pragma weak foo = bar > > > with either > > > #pragma weak foo = "bar" /* this is easier */ > I tried the quotation mark fix, and all it does is change the error > message to > > UIThrStubs.c:102: warning: malformed #

Re: GCC3.1 internal compiler error when compiling XFree86-4-libraries

2002-06-03 Thread Stanislav Grozev
On Mon, Jun 03, 2002 at 05:06:23PM +0200, Stanislav Grozev wrote: > On Mon, Jun 03, 2002 at 11:44:43AM -0300, Marc G. Fournier wrote: > > > > stupid question, but what is the fix for the #pragma weak issue? :( > > you replace > #pragma weak foo = bar > with

Re: GCC3.1 internal compiler error when compiling XFree86-4-libraries

2002-06-03 Thread Stanislav Grozev
On Mon, Jun 03, 2002 at 11:44:43AM -0300, Marc G. Fournier wrote: > > stupid question, but what is the fix for the #pragma weak issue? :( you replace #pragma weak foo = bar with either #pragma weak foo = "bar" /* this is easier */ or if __GNUC__ >= 3 int

GCC3.1 internal compiler error when compiling XFree86-4-libraries

2002-06-03 Thread Stanislav Grozev
Hello, I have a -CURRENT system (world from yesterday, ports from today). I'm trying to compile the XFree86-libraries-4.2.0 from ports, but I have troubles. After resolving the one with the #pragma weak, and also one with a missing ../ from one of the Mesa Makefiles, now I get the following: ---

lock order reversal

2001-06-21 Thread Stanislav Grozev
lock order reversal 1st 0xc03f0140 mntvnode @ /usr/src/sys/ufs/ffs/ffs_vfsops.c:1007 2nd 0xcaec972c vnode interlock @ /usr/src/sys/ufs/ffs/ffs_vfsops.c:1016 this is with softupdates enabled, and surprisingly enough it works, but only on my ThinkPad A21m. a desktop with the same source fails mis

Re: -current scheduler strangeness

2000-11-20 Thread Stanislav Grozev
On Mon, Nov 20, 2000 at 02:37:39PM +0200, Maxim Sobolev wrote: > > > pcm0: at port >0x220-0x22f,0x530-0x537,0x388-0x38b,0x330-0x331,0x370-0x371 irq 5 drq 0,1 on isa0 > > It could be due to my commit in which I reduced buffer size in mss driver from 64K >to 4K. Please try to increase it to 8KB,

Re: -current scheduler strangeness

2000-11-20 Thread Stanislav Grozev
as a followup, whenever I have disk access the problem shows also... On Mon, Nov 20, 2000 at 02:23:26PM +0200, Stanislav Grozev wrote: > Hi, > today I upgraded my 5.0-CURRENT from PRE_SMPNG to -current from about 5-6 > hours. everything went fine, the system is working, but I now n

-current scheduler strangeness

2000-11-20 Thread Stanislav Grozev
Hi, today I upgraded my 5.0-CURRENT from PRE_SMPNG to -current from about 5-6 hours. everything went fine, the system is working, but I now notice the following: whenever I compile something (say a port) and play an mp3 in xmms at the same time, the mp3 playing is frequently interrupted, or loops

Re: dfe-650 on -current

2000-11-07 Thread Stanislav Grozev
On Tue, Nov 07, 2000 at 12:19:40PM +0100, Rogier R. Mulhuijzen wrote: > > >it is detected by the kernel and pccardd correctly as an ed0 device, > >ifconfig configures it correctly, but as soon as the interface > >is up, the kernel starts spewing ed0: device timeout... > > This usually means IRQ

dfe-650 on -current

2000-11-07 Thread Stanislav Grozev
Hi, i've updated one of my systems (a fujitsu-siemens series C) laptop to the current from yesterday, and my dfe-650 10/100 ethernet pcmcia card started to behave strangely: it is detected by the kernel and pccardd correctly as an ed0 device, ifconfig configures it correctly, but as soon as the i

Re: -CURRENT crashes under heavy disk activity

2000-09-25 Thread Stanislav Grozev
On Mon, Sep 25, 2000 at 10:48:34AM -0400, Kenneth Wayne Culver wrote: > Well, I downgraded to PRE_SMPNG and it still crashes on heavy disk > activity. > the funny thing is that the same kernel that crashed on my desktop pc (with SMPng, but UP kernel) works like a charm on my laptop;-)) the only

Re: -CURRENT crashes under heavy disk activity

2000-09-25 Thread Stanislav Grozev
On Fri, Sep 22, 2000 at 03:37:32PM -0400, Kenneth Wayne Culver wrote: > I will try to build a debug kernel, and get a backtrace of what's > happening to send to the list, but basically what happened is that I was > running a cvsup of the cvs source repository and the ports repository and > it just

D-Link DFE-650 PCMCIA Ethernet on 5-CURRENT

2000-09-01 Thread Stanislav Grozev
Hi all, i have a Fujitsu-Siemens Lifebook C Series notebook, which is equipped with a D-Link DFE-650 NE-2000 Compatible PCCard Ethernet. on 4.1-RELEASE it works like a charm - once you have an 'ed' driver in the kernel, pccardd attaches it to the card and all is fine. Today I upgraded the laptop