Yoics! Just upgraded and cc is (mostly) bus-error-ing on buildworld.
Just to prefix with my config: FreeBSD duncan.reilly.home 9.0-CURRENT FreeBSD 9.0-CURRENT #7: Sat May 29 11:20:54 EST 2010 r...@duncan.reilly.home:/nb/obj/nb/src/sys/DUNCAN amd64 Current source tree was csupped about half an hour ago. I don't think that my hardware has gone dodgy: everything else seems to be working properly. cc itself seems to work OK when compiling my own code, too. But make buildworld -- /nb/src/cddl/usr.bin/sgsmsg/../../../sys/cddl/contrib/opensolaris/common/avl/avl.c:128: internal compiler error: Bus error: 10 Please submit a full bug report, with preprocessed source if appropriate. See URL:http://gcc.gnu.org/bugs.html for instructions. *** Error code 1 Stop in /nb/src/cddl/usr.bin/sgsmsg. Also, if I run buildworld with -j4 (my usual config), then a different compile crashes the same way : /nb/src/cddl/usr.bin/sgsmsg/../../../cddl/contrib/opensolaris/cmd/sgs/tools/common/string_table.c:467: internal compiler error: Bus error: 10 but in that case it was not the first compile which broke, and several (parallel, I assume) broke at the same time. So: is anyone else seeing this? Is it likely that heisenbugs have found their way into the compiler in the last week, or perhaps in the kernel's page table handling code? More importantly: any thoughts about how I can proceed from here? Re-install from a snapshot? Cheers, -- Andrew ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: wpa_supplicant (Was: Re: wpi not working on today's current (r208626))
On 29 May 2010, at 05:39, b. f. wrote: On 5/28/10, Doug Barton do...@freebsd.org wrote: On 5/28/2010 4:50 PM, b. f. wrote: I can't see any problems when using WPA2 with AES on r208606 i386 with uath(4). I'm updating this machine to r208630 tonight, and if I encounter problems with the later revision, I'll let you know. Ok, thanks. Are you saying that you experienced problems when trying to use a r207134 base with a r208626 kernel? If that's the case, I would recommend updating the base to the same revision as the kernel, and then retesting. Yes, that's what I'm doing I actually tried running the newly built wpa_supplicant but that didn't work. I'm kind of hesitant to do the full upgrade since I'm having kernel problems with the nvidia driver, but if I'm sure wpa_supplicant will work then I suppose I can bite the bullet. It appears that something is wrong. My wireless stick no longer associates with the network with r208630. I'll do some tinkering. That's odd. The only way for that to happen would be caused bug in the taskqueue stuff that zml committed, I think, but that's a long shot. Regards, -- Rui Paulo ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: wpa_supplicant (Was: Re: wpi not working on today's current (r208626))
On 5/29/10, Rui Paulo rpa...@freebsd.org wrote: On 29 May 2010, at 05:39, b. f. wrote: On 5/28/10, Doug Barton do...@freebsd.org wrote: On 5/28/2010 4:50 PM, b. f. wrote: I can't see any problems when using WPA2 with AES on r208606 i386 with uath(4). I'm updating this machine to r208630 tonight, and if I encounter problems with the later revision, I'll let you know. Ok, thanks. Are you saying that you experienced problems when trying to use a r207134 base with a r208626 kernel? If that's the case, I would recommend updating the base to the same revision as the kernel, and then retesting. Yes, that's what I'm doing I actually tried running the newly built wpa_supplicant but that didn't work. I'm kind of hesitant to do the full upgrade since I'm having kernel problems with the nvidia driver, but if I'm sure wpa_supplicant will work then I suppose I can bite the bullet. It appears that something is wrong. My wireless stick no longer associates with the network with r208630. I'll do some tinkering. That's odd. The only way for that to happen would be caused bug in the taskqueue stuff that zml committed, I think, but that's a long shot. Regards, -- Rui Paulo Yes, that was also my suspicion, and after seeing, via top(1), that ifconfig is stuck in the *taskq state while attempting to set up the wlan, I believe either r208623, or r208624, or both, is responsible for the regression. b. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
[TESTING]: ClangBSD branch needs testing before the import to HEAD
hi,
ClangBSD was updated to LLVM/clang revision 104832 which is what we aim to
import
into HEAD in roughly a week. We would like the initial import to be as painless
as possible and therefore we ask you to test ClangBSD to assure that the
revision
we are importing does not have some really embarassing bugs.
How to do it (on i386 and amd64):
0) install fresh devel/llvm-devel port
1) svn co http://svn.freebsd.org/base/projects/clangbsd src
2) echo NO_WERROR= /etc/src.conf ; echo WERROR= /etc/src.conf
3) cd src make buildworld
4) make installworld DESTDIR=/usr/clangbsd
5) (optional) try to build kernel with clang and boot it
5.1) cd /sys/{arch}/conf
5.2) config YOUR_KERNEL
5.3) setenv CC clang in tcsh or export CC=clang in bash
5.4) cd ../compile/YOUR_KERNEL
5.5) make make install
please make sure that it builds (on amd64/i386) and that the resulting world
is runnable. ie. try to chroot into it and do stuff. ie.
chroot /clangbsd /bin/tcsh
... stuff ...
there's a wiki page on this effort:
http://wiki.freebsd.org/BuildingFreeBSDWithClang
please report back any problems/success to me and/or this mailing list.
thank you for your testing!
Roman Divacky on behalf of the ClangBSD team
pgpUUIeD9DJPS.pgp
Description: PGP signature
Re: clangBSD build error on r208621
Hi rdivacky. On Sat, 29 May 2010 02:17:41 +0900 Norikatsu Shigemura n...@freebsd.org wrote: error: unknown argument: '-ferror-limit' mkdep: compile failed Do you have any idea? Of cause I set following environment: - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - $ cat /etc/src.conf NO_WERROR= WERROR= - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - OK, I got so that clang is too old. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - $ /usr/bin/clang --version clang version 1.5 (trunk) Target: x86_64-undermydesk-freebsd9.0 Thread model: posix - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - So I did use latest clang by installing devel/llvm-devel. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - $ /usr/local/bin/clang --version clang version 2.0 (trunk) Target: x86_64-portbld-freebsd9.0 Thread model: posix - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - I can compile to well-known error point. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - === sys/boot/i386/boot2 (all) dd if=/dev/zero of=boot2.ldr bs=512 count=1 1+0 records in 1+0 records out 512 bytes transferred in 0.27 secs (18837576 bytes/sec) /usr/local/bin/clang -isysroot /usr/obj/usr/src/tmp -B/usr/obj/usr/src/tmp/usr/lib/ -L/usr/obj/usr/src/tmp/usr/lib/ -Os -fno-guess-branch-probability -fomit-frame-pointer -fno-unit-at-a-time -mno-align-long-strings -mrtd -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -DUFS1_AND_UFS2 -DFLAGS=0x80 -DSIOPRT=0x3f8 -DSIOFMT=0x3 -DSIOSPD=9600 -I/usr/src/sys/boot/i386/boot2/../../common -I/usr/src/sys/boot/i386/boot2/../btx/lib -I. -Wall -Waggregate-return -Wbad-function-cast -Wcast-align -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wshadow -Wstrict-prototypes -Wwrite-strings -Winline --param max-inline-insns-single=100 -ffreestanding -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -m32 -march=i386 -std=gnu99 -c /usr/src/sys/boot/i386/boot2/sio.S clang: warning: the clang compiler does not support '-fno-unit-at-a-time' clang: warning: argument unused during compilation: '-L/usr/obj/usr/src/tmp/usr/lib/' clang: warning: argument unused during compilation: '-fno-guess-branch-probability' clang: warning: argument unused during compilation: '-mno-align-long-strings' clang: warning: argument unused during compilation: '-mrtd' clang: warning: argument unused during compilation: '--param max-inline-insns-single=100' clang: warning: argument unused during compilation: '-mpreferred-stack-boundary=2' objcopy -S -O binary boot1.out boot1 /usr/local/bin/clang -isysroot /usr/obj/usr/src/tmp -B/usr/obj/usr/src/tmp/usr/lib/ -L/usr/obj/usr/src/tmp/usr/lib/ -Os -fno-guess-branch-probability -fomit-frame-pointer -fno-unit-at-a-time -mno-align-long-strings -mrtd -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -DUFS1_AND_UFS2 -DFLAGS=0x80 -DSIOPRT=0x3f8 -DSIOFMT=0x3 -DSIOSPD=9600 -I/usr/src/sys/boot/i386/boot2/../../common -I/usr/src/sys/boot/i386/boot2/../btx/lib -I. -Wall -Waggregate-return -Wbad-function-cast -Wcast-align -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wshadow -Wstrict-prototypes -Wwrite-strings -Winline --param max-inline-insns-single=100 -ffreestanding -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -m32 -march=i386 -std=gnu99 -S -o boot2.s.tmp /usr/src/sys/boot/i386/boot2/boot2.c clang: warning: the clang compiler does not support '-fno-unit-at-a-time' clang: warning: argument unused during compilation: '-L/usr/obj/usr/src/tmp/usr/lib/' clang: warning: argument unused during compilation: '-fno-guess-branch-probability' clang: warning: argument unused during compilation: '-mno-align-long-strings' clang: warning: argument unused during compilation: '-mrtd' clang: warning: argument unused during compilation: '--param max-inline-insns-single=100' clang: warning: argument unused during compilation: '-mpreferred-stack-boundary=2' /usr/src/sys/boot/i386/boot2/boot2.c:234:1: warning: no previous prototype for function 'main' [-Wmissing-prototypes] main(void) ^ 1 warning generated. sed -e '/align/d' -e '/nop/d' boot2.s.tmp boot2.s rm -f boot2.s.tmp as --32 -o boot2.o boot2.s ld -static -N --gc-sections -nostdlib -m elf_i386_fbsd -Ttext 0x2000 -o boot2.out /usr/obj/usr/src/sys/boot/i386/boot2/../btx/lib/crt0.o boot2.o sio.o objcopy -S -O binary boot2.out boot2.bin btxld -v -E 0x2000 -f bin -b /usr/obj/usr/src/sys/boot/i386/boot2/../btx/btx/btx -l boot2.ldr -o boot2.ld -P 1 boot2.bin kernel: ver=1.02 size=690 load=9000 entry=9010 map=16M pgctl=1:1 client: fmt=bin size=1705 text=0 data=0 bss=0 entry=0 output: fmt=bin
Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver
Hi, with yesterday's CURRENT my bwn works partially. this is my hardware siba_b...@pci0:4:0:0: class=0x028000 card=0x04b514e4 chip=0x431514e4 rev=0x01 hdr=0x00 vendor = 'Broadcom Corporation' device = 'Broadcom Wireless b/g (BCM4315/BCM22062000)' class = network it works with WPA ap without destroy/re-create wlan0 , but it's unstable, at the first time it works, it goes forth and back between associated and no carrier, the other times it stay associated but network is down. and this usually followed by system freeze if I `/etc/rc.d/netif restart` later. and it never get associated with a open ap. --Buganini ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: wpa_supplicant (Was: Re: wpi not working on today's current (r208626))
On 05/29/10 03:54, b. f. wrote: On 5/29/10, Rui Paulorpa...@freebsd.org wrote: On 29 May 2010, at 05:39, b. f. wrote: On 5/28/10, Doug Bartondo...@freebsd.org wrote: On 5/28/2010 4:50 PM, b. f. wrote: I can't see any problems when using WPA2 with AES on r208606 i386 with uath(4). I'm updating this machine to r208630 tonight, and if I encounter problems with the later revision, I'll let you know. Ok, thanks. Are you saying that you experienced problems when trying to use a r207134 base with a r208626 kernel? If that's the case, I would recommend updating the base to the same revision as the kernel, and then retesting. Yes, that's what I'm doing I actually tried running the newly built wpa_supplicant but that didn't work. I'm kind of hesitant to do the full upgrade since I'm having kernel problems with the nvidia driver, but if I'm sure wpa_supplicant will work then I suppose I can bite the bullet. It appears that something is wrong. My wireless stick no longer associates with the network with r208630. I'll do some tinkering. That's odd. The only way for that to happen would be caused bug in the taskqueue stuff that zml committed, I think, but that's a long shot. Regards, -- Rui Paulo Yes, that was also my suspicion, and after seeing, via top(1), that ifconfig is stuck in the *taskq state while attempting to set up the wlan, I believe either r208623, or r208624, or both, is responsible for the regression. Reverting those two changes allows wpa_supplicant to work again. Thanks for the hint bf. Zach? Doug -- ... and that's just a little bit of history repeating. -- Propellerheads Improve the effectiveness of your Internet presence with a domain name makeover!http://SupersetSolutions.com/ ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: nvidia-driver 195.22 use horribly broken on amd64 between r206173 and
On 05/26/10 09:51, Kostik Belousov wrote: I did a quick glance over the driver, try this: http://people.freebsd.org/~kib/misc/nvidia-vm_page_lock.1.patch I did not even compiled the patched driver. Ok, I just tried this with an r208622 kernel and sources, and the system locks up as soon as I type 'startx'. No panic, no core dump, it just wedges, requiring it to be powered off. Doug -- ... and that's just a little bit of history repeating. -- Propellerheads Improve the effectiveness of your Internet presence with a domain name makeover!http://SupersetSolutions.com/ ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: nvidia-driver 195.22 use horribly broken on amd64 between r206173 and
On Sun, May 30, 2010 at 2:11 AM, Doug Barton do...@freebsd.org wrote: On 05/26/10 09:51, Kostik Belousov wrote: I did a quick glance over the driver, try this: http://people.freebsd.org/~kib/misc/nvidia-vm_page_lock.1.patchhttp://people.freebsd.org/%7Ekib/misc/nvidia-vm_page_lock.1.patch I did not even compiled the patched driver. Ok, I just tried this with an r208622 kernel and sources, and the system locks up as soon as I type 'startx'. No panic, no core dump, it just wedges, requiring it to be powered off. http://www.nvnews.net/vbulletin/showthread.php?t=150719 NVIDIA-FreeBSD-x86_64-195.36.24 with r208117 in my T61 laptop works well. Thanks, Kevin ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: nvidia-driver 195.22 use horribly broken on amd64 between r206173 and
On Sat, May 29, 2010 at 11:48 AM, datastream datastream.freecity datastream.freec...@gmail.com wrote: On Sun, May 30, 2010 at 2:11 AM, Doug Barton do...@freebsd.org wrote: On 05/26/10 09:51, Kostik Belousov wrote: I did a quick glance over the driver, try this: http://people.freebsd.org/~kib/misc/nvidia-vm_page_lock.1.patch I did not even compiled the patched driver. Ok, I just tried this with an r208622 kernel and sources, and the system locks up as soon as I type 'startx'. No panic, no core dump, it just wedges, requiring it to be powered off. http://www.nvnews.net/vbulletin/showthread.php?t=150719 NVIDIA-FreeBSD-x86_64-195.36.24 with r208117 in my T61 laptop works well. I'll try out this driver then. I'll have to see what the delta was with the kernel glue... Thanks for the feedback, -Garrett ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: clangBSD build error on r208621
On Sat, May 29, 2010 at 11:31:52PM +0900, Norikatsu Shigemura wrote: Hi rdivacky. On Sat, 29 May 2010 02:17:41 +0900 Norikatsu Shigemura n...@freebsd.org wrote: error: unknown argument: '-ferror-limit' mkdep: compile failed Do you have any idea? Of cause I set following environment: - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - $ cat /etc/src.conf NO_WERROR= WERROR= - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - OK, I got so that clang is too old. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - $ /usr/bin/clang --version clang version 1.5 (trunk) Target: x86_64-undermydesk-freebsd9.0 Thread model: posix - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - So I did use latest clang by installing devel/llvm-devel. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - $ /usr/local/bin/clang --version clang version 2.0 (trunk) Target: x86_64-portbld-freebsd9.0 Thread model: posix - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - I can compile to well-known error point. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - === sys/boot/i386/boot2 (all) dd if=/dev/zero of=boot2.ldr bs=512 count=1 1+0 records in 1+0 records out 512 bytes transferred in 0.27 secs (18837576 bytes/sec) /usr/local/bin/clang -isysroot /usr/obj/usr/src/tmp -B/usr/obj/usr/src/tmp/usr/lib/ -L/usr/obj/usr/src/tmp/usr/lib/ -Os -fno-guess-branch-probability -fomit-frame-pointer -fno-unit-at-a-time -mno-align-long-strings -mrtd -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -DUFS1_AND_UFS2 -DFLAGS=0x80 -DSIOPRT=0x3f8 -DSIOFMT=0x3 -DSIOSPD=9600 -I/usr/src/sys/boot/i386/boot2/../../common -I/usr/src/sys/boot/i386/boot2/../btx/lib -I. -Wall -Waggregate-return -Wbad-function-cast -Wcast-align -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wshadow -Wstrict-prototypes -Wwrite-strings -Winline --param max-inline-insns-single=100 -ffreestanding -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -m32 -march=i386 -std=gnu99 -c /usr/src/sys/boot/i386/boot2/sio.S clang: warning: the clang compiler does not support '-fno-unit-at-a-time' clang: warning: argument unused during compilation: '-L/usr/obj/usr/src/tmp/usr/lib/' clang: warning: argument unused during compilation: '-fno-guess-branch-probability' clang: warning: argument unused during compilation: '-mno-align-long-strings' clang: warning: argument unused during compilation: '-mrtd' clang: warning: argument unused during compilation: '--param max-inline-insns-single=100' clang: warning: argument unused during compilation: '-mpreferred-stack-boundary=2' objcopy -S -O binary boot1.out boot1 /usr/local/bin/clang -isysroot /usr/obj/usr/src/tmp -B/usr/obj/usr/src/tmp/usr/lib/ -L/usr/obj/usr/src/tmp/usr/lib/ -Os -fno-guess-branch-probability -fomit-frame-pointer -fno-unit-at-a-time -mno-align-long-strings -mrtd -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -DUFS1_AND_UFS2 -DFLAGS=0x80 -DSIOPRT=0x3f8 -DSIOFMT=0x3 -DSIOSPD=9600 -I/usr/src/sys/boot/i386/boot2/../../common -I/usr/src/sys/boot/i386/boot2/../btx/lib -I. -Wall -Waggregate-return -Wbad-function-cast -Wcast-align -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wshadow -Wstrict-prototypes -Wwrite-strings -Winline --param max-inline-insns-single=100 -ffreestanding -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -m32 -march=i386 -std=gnu99 -S -o boot2.s.tmp /usr/src/sys/boot/i386/boot2/boot2.c clang: warning: the clang compiler does not support '-fno-unit-at-a-time' clang: warning: argument unused during compilation: '-L/usr/obj/usr/src/tmp/usr/lib/' clang: warning: argument unused during compilation: '-fno-guess-branch-probability' clang: warning: argument unused during compilation: '-mno-align-long-strings' clang: warning: argument unused during compilation: '-mrtd' clang: warning: argument unused during compilation: '--param max-inline-insns-single=100' clang: warning: argument unused during compilation: '-mpreferred-stack-boundary=2' /usr/src/sys/boot/i386/boot2/boot2.c:234:1: warning: no previous prototype for function 'main' [-Wmissing-prototypes] main(void) ^ 1 warning generated. sed -e '/align/d' -e '/nop/d' boot2.s.tmp boot2.s rm -f boot2.s.tmp as --32 -o boot2.o boot2.s ld -static -N --gc-sections -nostdlib -m elf_i386_fbsd -Ttext 0x2000 -o boot2.out /usr/obj/usr/src/sys/boot/i386/boot2/../btx/lib/crt0.o boot2.o sio.o objcopy -S -O binary boot2.out boot2.bin btxld -v -E 0x2000 -f bin -b /usr/obj/usr/src/sys/boot/i386/boot2/../btx/btx/btx -l boot2.ldr
Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver
Hi, with yesterday's CURRENT my bwn works partially. this is my hardware siba_bwn0 at pci0:4:0:0:class=0x028000 card=0x04b514e4 chip=0x431514e4 rev=0x01 hdr=0x00 vendor = 'Broadcom Corporation' device = 'Broadcom Wireless b/g (BCM4315/BCM22062000)' class = network it works with WPA ap without destroy/re-create wlan0 , but it's unstable, at the first time it works, it goes forth and back between associated and no carrier, the other times it stay associated but network is down. and this usually followed by system freeze if I `/etc/rc.d/netif restart` later. and it never get associated with a open ap. This sounds similar to the problems detailed in the recent wpa supplicant (Was: Re: wpi not working on today's current ... thread. Have you tried reverting r208623 and r208624? b. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: nvidia-driver 195.22 use horribly broken on amd64 between r206173 and
On Sun, May 30, 2010 at 02:48:13AM +0800, datastream datastream.freecity wrote:
http://www.nvnews.net/vbulletin/showthread.php?t=150719
NVIDIA-FreeBSD-x86_64-195.36.24 with r208117 in my T61 laptop works well.
Hi,
I did the following:
- updated r208649
- applied following patch to nvidia-driver port which bumps driver version
up to 195.36.24, and also applies kib's patch
My system still hangs after doing a startx.
I also tried recompiling the driver *without* kib's patch, and my
system still hangs.
--
Craig Rodrigues
rodr...@crodrigues.org
? a.txt
? nvidia-vm_page_lock.1.patch
? work
Index: Makefile
===
RCS file: /home/pcvs/ports/x11/nvidia-driver/Makefile,v
retrieving revision 1.98
diff -r1.98 Makefile
9c9
DISTVERSION?= 195.36.15
---
DISTVERSION?= 195.36.24
Index: distinfo
===
RCS file: /home/pcvs/ports/x11/nvidia-driver/distinfo,v
retrieving revision 1.36
diff -r1.36 distinfo
1,15c1,3
MD5 (NVIDIA-FreeBSD-x86-195.36.15.tar.gz) = 2537ca726240344c7eaa44857e2b134e
SHA256 (NVIDIA-FreeBSD-x86-195.36.15.tar.gz) =
21fc89fa59e2cc96e560af856a3fa583ce4bfb7975465c71170c64962201e7a1
SIZE (NVIDIA-FreeBSD-x86-195.36.15.tar.gz) = 25614326
MD5 (NVIDIA-FreeBSD-x86_64-195.36.15.tar.gz) =
95af03aedc818a3dfd8ae9f289746ba4
SHA256 (NVIDIA-FreeBSD-x86_64-195.36.15.tar.gz) =
d64c664398cb4dade24af6b108e03607614f1f7584c71449230c646c313d0e7e
SIZE (NVIDIA-FreeBSD-x86_64-195.36.15.tar.gz) = 26449559
MD5 (NVIDIA-FreeBSD-x86-173.14.25.tar.gz) = 1eca3916a9ae86b953f54405e1881774
SHA256 (NVIDIA-FreeBSD-x86-173.14.25.tar.gz) =
c432ed94ce71e297b2d9304d9f34f906b58e2c7c4bc13d8dbac264ed52fd6261
SIZE (NVIDIA-FreeBSD-x86-173.14.25.tar.gz) = 16682722
MD5 (NVIDIA-FreeBSD-x86-96.43.16.tar.gz) = 3fc5c2bb537d4a7664d84a7a0df09c7c
SHA256 (NVIDIA-FreeBSD-x86-96.43.16.tar.gz) =
38bf334284dc600d92d8436333c98d5577e34d69456ed71f175caa6dffcd
SIZE (NVIDIA-FreeBSD-x86-96.43.16.tar.gz) = 11842453
MD5 (NVIDIA-FreeBSD-x86-71.86.13.tar.gz) = 19000b906225ebd39ca3edc1b0c3c7a5
SHA256 (NVIDIA-FreeBSD-x86-71.86.13.tar.gz) =
27ae01cd6fe050871f7785c2146b18e74ea882f6262e46dc965bf26061238447
SIZE (NVIDIA-FreeBSD-x86-71.86.13.tar.gz) = 8066159
---
MD5 (NVIDIA-FreeBSD-x86-195.36.24.tar.gz) = b09ee65d4d445fe8679e50bc49bba8c7
SHA256 (NVIDIA-FreeBSD-x86-195.36.24.tar.gz) =
d175c6848ac174f4c0c54ce7325959e21132f833e13d34004fab116c7034244f
SIZE (NVIDIA-FreeBSD-x86-195.36.24.tar.gz) = 25632339
Index: files/patch-nvidia-vm_page_lock.1
===
RCS file: files/patch-nvidia-vm_page_lock.1
diff -N files/patch-nvidia-vm_page_lock.1
0a1,34
--- src/nvidia_subr.c.orig2010-05-26 19:34:20.722118986 +0300
+++ src/nvidia_subr.c 2010-05-26 19:50:00.198768786 +0300
@@ -1237,6 +1237,7 @@
struct nvidia_alloc *at;
struct nvidia_softc *sc = nv-os_state;
vm_offset_t address;
+vm_page_t m;
uint32_t i;
vm_memattr_t attr;
uint32_t size = (count * PAGE_SIZE);
@@ -1301,9 +1302,10 @@
for (i = 0; i count; i++) {
pte_array[i] = at-pte_array[i].physical_address;
-vm_page_lock_queues();
-vm_page_wire(PHYS_TO_VM_PAGE(pte_array[i]));
-vm_page_unlock_queues();
+m = PHYS_TO_VM_PAGE(pte_array[i]);
+vm_page_lock(m);
+vm_page_wire(m);
+vm_page_unlock(m);
sglist_append_phys(at-sg_list, pte_array[i], PAGE_SIZE);
}
@@ -1365,9 +1367,7 @@
os_flush_cpu_cache();
for (i = 0; i count; i++) {
-vm_page_lock_queues();
vm_page_unwire(PHYS_TO_VM_PAGE(at-pte_array[i].physical_address),
0);
-vm_page_unlock_queues();
kmem_free(kernel_map,
at-pte_array[i].virtual_address, PAGE_SIZE);
malloc_type_freed(M_NVIDIA, PAGE_SIZE);
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
