RE: Comments on Release Building for -current
Howdy, > -Original Message- > From: John Baldwin [mailto:[EMAIL PROTECTED]] > Sent: Friday, 2 August 2002 4:05 > To: Bruce Evans > Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; Chris Knight > Subject: RE: Comments on Release Building for -current > > > On 01-Aug-2002 Bruce Evans wrote: > > > > -mcpu=pentiumpro causes huge bloatage here (+400K text for > > a 2000K text kernel IIRC). I quickly turned it off here. > > Ok. I'll make some patches to use NO_CPU_CFLAGS and > NO_CPU_COPTFLAGS when building stuff to go on the crunches as > well as -Os. > -mcpu=pentiumpro is a huge pig-dog. It should be culled from the crunches and from the kernels. I managed to cull it from the kernels by simply adding KERNEL_FLAGS+= -D_NO_CPU_CFLAGS -DNO_CPU_COPTFLAGS into /usr/src/release/Makefile. I also managed to cull it from the crunches by adding the above defines into boot_crunch.conf and fixit_crunch.conf. The savings still aren't enough though :-( -Os may help here, but I'm having dificulty trying to find where this should go. Regards, Chris Knight Systems Administrator AIMS Independent Computer Professionals Tel: +61 3 6334 6664 Fax: +61 3 6331 7032 Mob: +61 419 528 795 Web: http://www.aims.com.au To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
CURRENT & notebook & suspend
I like to use 'suspend mode' with my notebook sony vaio z505hs. I don't like to shutdown FreeBSD every time I want to switch the notebook off. I have had a problem with suspend for a long long time. But before deep investigation I'd like to know if someone has the same problem. People, how don't use suspend with yours notebook, may be you try to repeat it? The problem is: Notebook works good untill 'suspend'.('zzz' or 'acpiconf -s3'). After resume it works fine a random period of time(1 minute or 3 days and several suspends) and then kernel has a panic with message "getnewvnode: free vnode isn't". It works with and without acpi. I see, that the panic usually appears during strong hard disk io operations (like when cvsup is working or programms is been compiling). I think, that in some conditions, linked with 'suspend mode', vnode with non zero v_usecount flag is placed in freevnode spool. First look at /sys/kern/vfs_subr.c told me that it is imposible, but... -- bye Juriy Goloveshkin To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Comments on Release Building for -current
On Sat, 3 Aug 2002, Mike Barcroft wrote: > Andrew Kolchoogin <[EMAIL PROTECTED]> writes: > > ... > > sorry, but some time ago I read here that gcc -O2 breaks our printf() in > > libc. I haven't find any assembler code in /usr/src/lib/libc/stdio/vfprintf.c, > > as such, if some C compiler can't handle VALID and STANDARDS-COMPLIANT C code, > > this compiler is broken. Isn't it? > > > > Indeed, all of FreeBSD users could help to catch such a bug in gcc optimizer > > code. :) > > If someone could find the small segment of code where the optimizer > screws up, and write a small program to demonstrate the problem, we > would have a good chance of it getting fixed. Er, someone (Dan Lukes) has already done this. See PR 40209. I'm sorry I haven't found time to look at it in detail. Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ACPI errors
[move to -current because STABLE don't have acpica support yet] Hi, > System: TOS 5005-S504 > Error with any kernel build: > Using $PIR table, 0 entries at 0xc00f0190 > ACPI-0171: *** Error: AcpiLoadTables: RSDP Failed validation: AE_BAD_SIGNATURE > ACPI-0213: *** Error: AcpiLoadTables: Could not load tables: AE_BAD_SIGNATURE > ACPI: Table load failed: AE_BAD_SIGNATURE It seems that this problem happens after sys/i386/i386/pmap.c rev 1.352 changes. Could you replace pmap.c with 1.351 ? Peter, do you have any ideas with this ? > Same thing happens if I do an unset acpi_load or if I try boot -s, or both. I think your kernel config file includes 'device acpica'. Thanks To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ACPI errors
It seems Mitsuru IWASAKI wrote: > [move to -current because STABLE don't have acpica support yet] > > Hi, > > > System: TOS 5005-S504 > > Error with any kernel build: > > Using $PIR table, 0 entries at 0xc00f0190 > > ACPI-0171: *** Error: AcpiLoadTables: RSDP Failed validation: AE_BAD_SIGNATURE > > ACPI-0213: *** Error: AcpiLoadTables: Could not load tables: AE_BAD_SIGNATURE > > ACPI: Table load failed: AE_BAD_SIGNATURE Yups that fails here on all systems I have as well... -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: About 5.0 and Nvidia drivers
Hi! On Sat, Aug 03, 2002 at 06:38:11PM -0400, Matthew N. Dodd wrote: >> ugh, sounds like the lip-service I was getting. "I'll look into that" :/ > No, they're working on it, and actually have GL running in the lab. Well, and, as under Linux, there will be an a closed-source library and a kernel module permamently takes kernel to the hell of core dumps? >> I'm starting to ponder the legality and challenge involved in reverse >> engineering the card and building a driver from scratch... maybe >> something that works with X the X way (dri/drm) > You're a funny guy. There is another FreeBSD/NVidia Initiative to develop DRI-capable driver for FreeBSD. Did you contact him? > You'd be better off working with ATI or the PowerVR people. You want to say me that there is an ATI graphics card that is more powerful than NVidia GeForce? Sorry, but FreeBSD is really good operating system. Good enough for use it on servers. As a system programmer, I wish to have a copy of it on my home desktop. And my son/daughter wish to play games on same desktop. What should I do? Change video cards every day? Whatever? Or use ancient 16-bit NVidia drivers not capable to use even 1152x864x110 Hz? Andrew. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
ACPI Errors
Reposted because I screwed up the first time and sent it to the wrong list System: TOS 5005-S504 Error with any kernel build: Using $PIR table, 0 entries at 0xc00f0190 ACPI-0171: *** Error: AcpiLoadTables: RSDP Failed validation: AE_BAD_SIGNATURE ACPI-0213: *** Error: AcpiLoadTables: Could not load tables: AE_BAD_SIGNATURE ACPI: Table load failed: AE_BAD_SIGNATURE Shortly after that, I get a hard lock at at either the load of the fxp driver, or when probing the pci bus. Same thing happens if I do an unset acpi_load or if I try boot -s, or both. Ideas? ¡Iì¹»®&Þ±éݨ¥¶Ý¢jçH:+éì¹»®&Þ~·nÇ\ººÞا¶¡Ü¨~Ø^ë,j
Re: About 5.0 and Nvidia drivers
| You want to say me that there is an ATI graphics card that is more powerful | than NVidia GeForce? | | Sorry, but FreeBSD is really good operating system. Good enough for use it | on servers. As a system programmer, I wish to have a copy of it on my home | desktop. And my son/daughter wish to play games on same desktop. | | What should I do? Change video cards every day? Whatever? It sounds like dual booting would be a better idea here. Boot into FreeBSD when you want to code, boot into Windows when your son/daughter wish to play games. -Dan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: ACPI errors
-Original Message- From: Mitsuru IWASAKI [mailto:[EMAIL PROTECTED]] Sent: Sun 8/4/2002 8:59 AM To: Robert D Hughes Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: ACPI errors [move to -current because STABLE don't have acpica support yet] I reposted it over there, so let's move the conversation there. Hi, > System: TOS 5005-S504 > Error with any kernel build: > Using $PIR table, 0 entries at 0xc00f0190 > ACPI-0171: *** Error: AcpiLoadTables: RSDP Failed validation: AE_BAD_SIGNATURE > ACPI-0213: *** Error: AcpiLoadTables: Could not load tables: AE_BAD_SIGNATURE > ACPI: Table load failed: AE_BAD_SIGNATURE It seems that this problem happens after sys/i386/i386/pmap.c rev 1.352 changes. Could you replace pmap.c with 1.351 ? How would I pull a specific version from cvs? Peter, do you have any ideas with this ? > Same thing happens if I do an unset acpi_load or if I try boot -s, or both. I think your kernel config file includes 'device acpica'. Nope. It's auto-loading as a module, as per NOTES. Thanks, Rob èR{.nÇ+·¬zwfj)m¢f£¢·hkyàRàÂ+aº{.nÇ+·ç±×.®·§¶)í æèw*¶¦zË
Re: About 5.0 and Nvidia drivers
"Dan Moschuk" <[EMAIL PROTECTED]> wrote in message news:aijim2$2t69$[EMAIL PROTECTED]... > It sounds like dual booting would be a better idea here. Boot into FreeBSD > when you want to code, boot into Windows when your son/daughter wish > to play games. > I don't think that's a good idea at all. That FreeBSD is very good as a server OS does not mean that it should not support my graphics hardware. 3D/2D graphics is not only about playing games. But the problem here is with NVidia. Because they have to provide the drivers. Selling a video card without specifying how to access the video card is like selling a microwave oven without labeled buttons. Anyway some part of my original question isn't listed under freebsd current mailing list archives. I don't know what the problem was, but here's the more relevant part with the current... -- By the time 5.0 is released do you aim to complete all the planned features at www.freebsd.org/smp? (like full kernel preemption) I know it's a tentative list but still if there's a consensus about that let me know. Will 5.0 stable be created after KSE milestone 4 commit? I just wanted to know more about the release policy. After 5.0 stable is released, is the development in the current branch completely be named 6.0? (and any possibly new features (like finer grained locking) will be available in 6.0 stable) Or is the development in current tree will continue to be merged with 5.x for some time? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
missing stuff for lazy BIOS?
When building my kernel with option PCI_ENABLE_IO_MODES it complains that it's an unknown option, has anything beend changed about that today? /John To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: missing stuff for lazy BIOS?
On Sun, Aug 04, 2002 at 07:33:44PM +0200, John Angelmo wrote: > When building my kernel with option PCI_ENABLE_IO_MODES it complains > that it's an unknown option, has anything beend changed about that today? > > /John > > To quote CVS: date: 2002/07/26 07:58:16; author: imp; state: Exp; lines: +0 -1 Make PCI_ENABLE_IO_MODES a sysctl hw.pci.enable_io_modes. It can also be set at boot time. It defaults to 1 now since it can be set in the boot loader. If this proves unwise, we can reset it to defaulting to 0. I guess that UPDATING needs to be, um, updated. That, or the option needs to be put back in to help with transition. Scott To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
current panic on apache2 after sys/kern/subr_mbuf.c commit
Dear all, I have been experiencing panic with Apache2 since Jul 31. The system boot, but panic when someone access the apache2 service. After trace back, the subr_mbuf.c commit at around Jul 30 21:30 GMT is the candidate for this panic. Does anyone see the same problem as me? The machine is currently very busy and can't afford a panic to get the message. But, I'll provide more info tomorrow __ Do You Yahoo!? Yahoo! Health - Feel better, live better http://health.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: About 5.0 and Nvidia drivers
On Sun, Aug 04, 2002 at 01:10:28PM -0400, Alp Atici wrote: > > By the time 5.0 is released do you aim to complete all the planned > features at www.freebsd.org/smp? (like full kernel preemption) I know it's > a tentative list but still if there's a consensus about that let me know. The aim is to complete as many feature as possiblei without shipping a broken 5.0. There is, however, a limited number of hands doing to dirty work. > Will 5.0 stable be created after KSE milestone 4 commit? No. 5.0-STABLE will be created after 5.0-RELEASE. However, Julian will probably have (a portion of) KSE milestone 4 committed before 5.0-RELEASE is released. > I just wanted to know more about the release policy. http://www.freebsd.org/releng/index.html > After 5.0 stable is released, is the development in the current > branch completely be named 6.0? Yes. > Or is the development in current tree will continue to be merged > with 5.x for some time? Features in the FreeBSD-current tree are often merged back to FreeBSD-stable. This include features in 5.x that get merged back to FreeBSD 4.x. There is no reason why features added to 6.x can't be merged back to 5.x (other than man power). -- Steve To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: missing stuff for lazy BIOS?
Scott Long wrote: > On Sun, Aug 04, 2002 at 07:33:44PM +0200, John Angelmo wrote: > >>When building my kernel with option PCI_ENABLE_IO_MODES it complains >>that it's an unknown option, has anything beend changed about that today? >> >>/John >> >> > > > To quote CVS: > > date: 2002/07/26 07:58:16; author: imp; state: Exp; lines: +0 -1 > Make PCI_ENABLE_IO_MODES a sysctl hw.pci.enable_io_modes. It can also > be set at boot time. It defaults to 1 now since it can be set in the > boot loader. If this proves unwise, we can reset it to defaulting to 0. > > I guess that UPDATING needs to be, um, updated. That, or the option > needs to be put back in to help with transition. > > Scott AH OK We Might need to remove it from GENERIC /John To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ACPI errors
Mitsuru IWASAKI wrote: > [move to -current because STABLE don't have acpica support yet] > > Hi, > > > System: TOS 5005-S504 > > Error with any kernel build: > > Using $PIR table, 0 entries at 0xc00f0190 > > ACPI-0171: *** Error: AcpiLoadTables: RSDP Failed validation: AE_BAD_SIGNAT URE > > ACPI-0213: *** Error: AcpiLoadTables: Could not load tables: AE_BAD_SIGNATU RE > > ACPI: Table load failed: AE_BAD_SIGNATURE > > It seems that this problem happens after sys/i386/i386/pmap.c rev > 1.352 changes. Could you replace pmap.c with 1.351 ? > > Peter, do you have any ideas with this ? If backing out rev 1.352 solves the problem, feel free to go ahead and either back it out or add #if 0 around the changes. But I think the fix is to change this: /* We have a 1MB direct mapped region at KERNBASE */ if (pa < 0x0010 && pa + size <= 0x0010) - return (void *)(pa + KERNBASE); + return (void *)(pa + offset + KERNBASE); I've committed this as 1.356. If it doesn't solve it, then go ahead and back out both 1.352 and 1.356. Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message