vm_fault on umass transfers
Hello, I've had an Olympus camera which I've been able to access under -CURRENT for some time until recently. I can mount_msdosfs the device (da0s1) OK, but when I try to copy or move files from the device to my hard disk drive I get the following kernel message: panic: mv_fault: fault on nofault entry, addr: dc346000 And then the system will start to shutdown and sync disks. Unfortunately I've been unable to boot with a generic kernel at this stage to see if there would be more information spat out. Thanks in advance -Al ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ATA problems(unlean fs) on recent cvsup
Just a follow up. I've since been able to get my -CURRENT system running under the new build. However the booting process is still slow around those ata?: [MPSAFE] messages. Any ideas on getting a speed up? -Al ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ATA problems(unlean fs) on recent cvsup
Hello list, I've recently cvsup'd current (14th of Sep). After a build and install world/kernel I rebooted to find some new and interesting kernel messages about ata? MPSAFE. Well as the booting continued I notcied the machine was going through more disk activity then usal. It was also taking alot longer to actully start. Eventully the kernel dropped into single user mode. It appears my filesystem is playing up for some reason. I haven't had any power failures for random hangs/reboots. After the recent cvsup my /usr fs appears to be coruppt or something. In single user mode I'm unable fix the problem with fsck. At first when I had softupdates /usr fsck would give me messages like "UNEXPECTED SOFT UPDATE INCONSISTENCY" I turned of softupate to see if it would help...it didn't. I still can't fix the fs. I get output like "CANNOT WRITE BLK: xxx" and I'm always unable to salvage blks and what not. Anyway my dmesg is as follows: Copyright (c) 1992-2003 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.1-CURRENT #0: Sun Sep 14 12:59:35 EST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC Preloaded elf kernel "/boot/kernel.GENERIC/kernel" at 0xc076. Preloaded elf module "/boot/modules/acpi.ko" at 0xc076024c. Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) 4 CPU 2.53GHz (2533.05-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf27 Stepping = 7 Features=0xbfebfbff real memory = 536854528 (511 MB) avail memory = 513466368 (489 MB) Pentium Pro MTRR support enabled npx0: [FAST] npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard pcibios: BIOS version 2.10 Using $PIR table, 11 entries at 0xc00f1720 acpi0: power button is handled as a fixed feature programming model. Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0xe408-0xe40b on acpi0 acpi_cpu0: on acpi0 acpi_cpu1: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib0: slot 2 INTA is routed to irq 11 pcib0: slot 3 INTA is routed to irq 9 pcib0: slot 3 INTB is routed to irq 9 pcib0: slot 3 INTC is routed to irq 9 pcib0: slot 14 INTA is routed to irq 11 agp0: mem 0xe000-0xe7ff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pcib1: slot 0 INTA is routed to irq 11 pci1: at device 0.0 (no driver attached) isab0: at device 2.0 on pci0 isa0: on isab0 fwohci0: vendor=1039, dev=7007 fwohci0: <1394 Open Host Controller Interface> mem 0xde80-0xde800fff at device 2.3 on pci0 pcib0: slot 2 INTB is routed to irq 5 fwohci0: [MPSAFE] fwohci0: OHCI version 1.0 (ROM=1) fwohci0: No. of Isochronous channel is 4. fwohci0: EUI64 00:e0:18:00:00:0a:83:4c fwohci0: Phy 1394a available S400, 2 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: on fwohci0 if_fwe0: on firewire0 if_fwe0: Fake Ethernet address: 02:e0:18:0a:83:4c sbp0: on firewire0 fwohci0: Initiate bus reset atapci0: port 0xb400-0xb40f,0xb800-0xb803,0xd000-0xd007,0xd400-0xd403,0xd800-0xd807 irq 11 at device 2.5 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata0: [MPSAFE] ata1: at 0x170 irq 15 on atapci0 ata1: [MPSAFE] pci0: at device 2.7 (no driver attached) ohci0: mem 0xde00-0xde000fff irq 9 at device 3.0 on pci0 usb0: OHCI version 1.0, legacy support usb0: SMM does not respond, resetting usb0: on ohci0 usb0: USB revision 1.0 uhub0: SiS OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered ums0: KYE Genius USB Wheel Mouse, rev 1.00/2.42, addr 2, iclass 3/1 ums0: 5 buttons and Z dir. ohci1: mem 0xdd80-0xdd800fff irq 9 at device 3.1 on pci0 usb1: OHCI version 1.0, legacy support usb1: SMM does not respond, resetting usb1: on ohci1 usb1: USB revision 1.0 uhub1: SiS OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered ohci2: mem 0xdd00-0xdd000fff irq 9 at device 3.2 on pci0 usb2: OHCI version 1.0, legacy support usb2: SMM does not respond, resetting usb2: on ohci2 usb2: USB revision 1.0 uhub2: SiS OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered pci0: at device 3.3 (no driver attached) pci0: at device 9.0 (no driver attached) pci0: at device 9.1 (no driver attached) rl0: port 0x8800-0x88ff mem 0xdb80-0xdb8000ff at device 10.0 on pci0 pcib0: slot 10 INTA is routed to irq 11 rl0: Ethernet address: 00:50:bf:77:3c:97 miibus0: on rl0 rlphy0: on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto atapci1: port 0x7800-0x787f,0x8000-0x800f,0x8400-0x843f mem 0xda80-0xda81,0xdb00-0xdb000fff irq 11 at device 14.0 on pci0 atapci1: [MPSAFE] ata2: at 0xdb00 on atapci1 ata2: [MPSAFE] ata3: at 0xdb00 on atapci1 ata3: [MPSAFE] ata4: at 0xdb00 on atapci1 ata4: [MPSAFE] fdc0: port 0x3f7,0x3f2-0x3f5 irq 6 drq 2 on acpi0 fdc0: FIFO enabled,
Re: Portupgrade problems
On Sunday, 07 September 2003 00:43, Lars Eggert wrote: > Alastair G. Hogge wrote: > > Hey all, > > > > I haven't updated my ports for a few weeks and after after a recent cvsup > > of world and the ports tree I tried to run portupgrade -aCC and was > > displayed with the following: > > n /var/db/pkg ... - 318 packages found > > (-8 +6) (...)/usr/local/lib/ruby/site_ruby/1.6/ports.rb:4:in `require': > > /usr/loc > > al/lib/ruby/site_ruby/1.6/portinfo.rb:98: unterminated string meets end > > of file > > (SyntaxError) > > ... > > Try "pkgdb -fu". Awesome! Thanks for the help. That solved my problem :-) > Lars Al ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Portupgrade problems
Hey all, I haven't updated my ports for a few weeks and after after a recent cvsup of world and the ports tree I tried to run portupgrade -aCC and was displayed with the following: n /var/db/pkg ... - 318 packages found (-8 +6) (...)/usr/local/lib/ruby/site_ruby/1.6/ports.rb:4:in `require': /usr/loc al/lib/ruby/site_ruby/1.6/portinfo.rb:98: unterminated string meets end of file (SyntaxError) /usr/local/lib/ruby/site_ruby/1.6/portinfo.rb:98: parse error from /usr/local/lib/ruby/site_ruby/1.6/ports.rb:4 from /usr/local/lib/ruby/site_ruby/1.6/pkgtools.rb:25:in `require' from /usr/local/lib/ruby/site_ruby/1.6/pkgtools.rb:25 from /usr/local/sbin/pkgdb:35:in `require' from /usr/local/sbin/pkgdb:35 /usr/local/lib/ruby/site_ruby/1.6/dl/types.rb:124: [BUG] Segmentation fault ruby 1.6.8 (2003-03-26) [i386-freebsd5] [Updating the pkgdb in /var/db/pkg ... - 318 packages found (-8 +6) (...)/usr/local/lib/ruby/site_ruby/1.6/pkgdb.rb:241:in `origin': Invalid argument: Cannot update the pkgdb!] (PkgDB::DBError) from /usr/local/lib/ruby/site_ruby/1.6/pkginfo.rb:178:in `origin' from /usr/local/sbin/portversion:301:in `check_pkgs' from /usr/local/sbin/portversion:300:in `each' from /usr/local/sbin/portversion:300:in `check_pkgs' from /usr/local/sbin/portversion:260:in `main' from /usr/local/sbin/portversion:77:in `initialize' from /usr/local/sbin/portversion:77:in `new' from /usr/local/sbin/portversion:77:in `main' from /usr/local/sbin/portversion:347 Below are the seg faults caused from above: Sep 6 15:06:43 nova kernel: pid 69492 (ruby), uid 0: exited on signal 6 (core dumped) Sep 6 15:08:04 nova kernel: pid 75934 (ruby), uid 0: exited on signal 6 (core dumped) Sep 6 15:08:49 nova kernel: pid 79479 (ruby), uid 0: exited on signal 6 (core dumped) I removed /var/db/pkg/ruby* and portupgrade and reinstall installed them but I get the same. Running portversion gets a hang portsdb -uU seemed to work ok. pkgdb -F returns: --> Checking the package registry database [Updating the pkgdb in /var/db/pkg ... - 316 packages found (-10 +6) (...)Invalid argument: Cannot update the pkgdb!] My uname -a retruns: FreeBSD nova 5.1-CURRENT FreeBSD 5.1-CURRENT #0: Sat Sep 6 09:03:57 EST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/NOVA i386 -Al ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: buildworld seg faulting.
On Monday, 01 September 2003 23:02, Bill Moran wrote: > Alastair G. Hogge wrote: > > On Monday, 01 September 2003 02:24, Steve Kargl wrote: > >>On Sun, Aug 31, 2003 at 07:52:15PM +1000, Alastair G. Hogge wrote: > >>>Hello list, > >>> > >>>For the past couple of weeks I've been tyring to keep my system up to > >>>date with cvsup. However, when ever I run a buildworld I get problems > >>>with gcc (I think it's gcc). I've tried nuking /usr/obj and running > >>> "make clean" many tims before each build but this doesn't help. What > >>> I've noticed is that the seg fault doesn't occur in the same place. > >> > >>There isn't enough context in the error messages you reported. > >>Are you using the -j option during your buildworld? > > > > No. just plain old "make buildworld" i did also try -j3 > > > >>However, your last sentence in the above quoted paragraph, > >>suggests that you have bad memory or a heating problem or a > >>suspect power supply. > > > > Ahhh. I don't like the sound of that. > > > > Is there something else I'm leaving out. I really hope it isn't memory I > > sold my thumbs to get 512megs of Corsair XSM :-( > > Download memtest86 and let it run for a couple of hours. If you see any > errors at all, try and get that memory replaced under warranty. OK install memtest from the ports. After running "/usr/bin/nice -35 memtest 512m 2 --log" I got: Current limits: RLIMIT_RSS 0x RLIMIT_VMEM 0x Raising limits... Unable to malloc 536870912 bytes. Allocated 535822336 bytes...trying mlock...failed: insufficient resources. Allocated 534773760 bytes...trying mlock...failed: insufficient resources. Allocated 533725184 bytes...trying mlock...failed: insufficient resources. Allocated 532676608 bytes...trying mlock...failed: insufficient resources. Allocated 531628032 bytes...trying mlock...failed: insufficient resources. Allocated 530579456 bytes...trying mlock...failed: insufficient resources. Allocated 529530880 bytes...trying mlock...failed: insufficient resources. Allocated 528482304 bytes...trying mlock...failed: insufficient resources. Allocated 527433728 bytes...trying mlock...failed: insufficient resources. Allocated 526385152 bytes...trying mlock...failed: insufficient resources. Allocated 525336576 bytes...trying mlock...failed: insufficient resources. Allocated 524288000 bytes...trying mlock...failed: insufficient resources. Allocated 523239424 bytes...trying mlock...failed: insufficient resources. Allocated 522190848 bytes...trying mlock...failed: insufficient resources. Allocated 521142272 bytes...trying mlock...failed: insufficient resources. Allocated 520093696 bytes...trying mlock...failed: insufficient resources. Allocated 519045120 bytes...trying mlock...failed: insufficient resources. Allocated 517996544 bytes...trying mlock...failed: insufficient resources. Allocated 516947968 bytes...trying mlock...failed: insufficient resources. Allocated 515899392 bytes...trying mlock...failed: insufficient resources. Allocated 514850816 bytes...trying mlock...failed: insufficient resources. Allocated 513802240 bytes...trying mlock...failed: insufficient resources. Allocated 512753664 bytes...trying mlock...failed: insufficient resources. Allocated 511705088 bytes...trying mlock...failed: insufficient resources. Allocated 510656512 bytes...trying mlock...failed: insufficient resources. Allocated 509607936 bytes...trying mlock...failed: insufficient resources. Allocated 508559360 bytes...trying mlock...failed: insufficient resources. Allocated 507510784 bytes...trying mlock...failed: insufficient resources. Allocated 506462208 bytes...trying mlock...failed: insufficient resources. Allocated 505413632 bytes...trying mlock...failed: insufficient resources. Allocated 504365056 bytes...trying mlock...failed: insufficient resources. Allocated 503316480 bytes...trying mlock...failed: insufficient resources. Allocated 502267904 bytes...trying mlock...failed: insufficient resources. Allocated 501219328 bytes...trying mlock...failed: insufficient resources. Allocated 500170752 bytes...trying mlock...failed: insufficient resources. Allocated 499122176 bytes...trying mlock...failed: insufficient resources. Allocated 498073600 bytes...trying mlock...failed: insufficient resources. Allocated 497025024 bytes...trying mlock...failed: insufficient resources. Allocated 495976448 bytes...trying mlock...failed: insufficient resources. Allocated 494927872 bytes...trying mlock...failed: insufficient resources. Allocated 493879296 bytes...trying mlock...failed: insufficient resources. Allocated 492830720 bytes...trying mlock...failed: insufficient resources. Allocated
Re: buildworld seg faulting.
On Monday, 01 September 2003 02:24, Steve Kargl wrote: > On Sun, Aug 31, 2003 at 07:52:15PM +1000, Alastair G. Hogge wrote: > > Hello list, > > > > For the past couple of weeks I've been tyring to keep my system up to > > date with cvsup. However, when ever I run a buildworld I get problems > > with gcc (I think it's gcc). I've tried nuking /usr/obj and running "make > > clean" many tims before each build but this doesn't help. What I've > > noticed is that the seg fault doesn't occur in the same place. > > There isn't enough context in the error messages you reported. > Are you using the -j option during your buildworld? No. just plain old "make buildworld" i did also try -j3 > However, your last sentence in the above quoted paragraph, > suggests that you have bad memory or a heating problem or a > suspect power supply. Ahhh. I don't like the sound of that. Is there something else I'm leaving out. I really hope it isn't memory I sold my thumbs to get 512megs of Corsair XSM :-( -Al ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
buildworld seg faulting.
Hello list, For the past couple of weeks I've been tyring to keep my system up to date with cvsup. However, when ever I run a buildworld I get problems with gcc (I think it's gcc). I've tried nuking /usr/obj and running "make clean" many tims before each build but this doesn't help. What I've noticed is that the seg fault doesn't occur in the same place. The following is snippets of two errors. ===> gnu/usr.bin/binutils/size /usr/obj/usr/src/gnu/usr.bin/binutils/size created for /usr/src/gnu/usr.bin/binu tils/size Segmentation fault (core dumped) *** Error code 139 Stop in /usr/src/gnu/usr.bin/binutils. *** Error code 1 Stop in /usr/src/gnu/usr.bin. *** Error code 1 Stop in /usr/src/gnu. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 And: insn-opinit.c: In function `init_all_optabs': insn-opinit.c:510: internal compiler error: Segmentation fault Please submit a full bug report, with preprocessed source if appropriate. See http://gcc.gnu.org/bugs.html> for instructions. *** Error code 1 Stop in /usr/src/gnu/usr.bin/cc/cc_int. *** Error code 1 Stop in /usr/src/gnu/usr.bin/cc. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. My current uname -a reports: FreeBSD nova 5.1-CURRENT FreeBSD 5.1-CURRENT #0: Sat Aug 16 12:32:29 EST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/NOVA i386 I was able to buildworld once a week ago. After each seg fault I would just continue the build again with out cleaning out the object files. Thanks in advance -Al ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: problem with nvidia graphics card and -current
On Tuesday, 05 August 2003 14:34, Matthew N. Dodd wrote: > On Mon, 4 Aug 2003, Glenn Johnson wrote: > > Question for the developers: Is there someway to avoid having the > > combination of vesa and nvidia cause a total lockup of the machine? I > > have a feeling I may not be the last person to try the nvidia driver > > with vesa enabled, either as a module, or compiled in the kernel. > > I'm running a system with the VESA stuff compiled in; the nvidia drivers > work just fine. > > IIRC you're running with ACPI; try not doing that. I'm also running a system with the vesa module loaded. I'm also running ACPI. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: problem with nvidia graphics card and -current
On Tuesday, 05 August 2003 13:07, Glenn Johnson wrote: > On Sun, Aug 03, 2003 at 11:48:56PM -0500, wrote: > > I was setting up a system today with an nvidia Geforce4-MX 440 > > graphics card. I am not at the system at the moment but the -current > > sources were from about 2:00 PM CDT. I installed the nvidia-driver > > port (1.0.4365) trying various combinations of WITH_FREEBSD_AGP, > > FORCE_AGP_RATE, and WITH_NVIDIA_HACKS. I get the same result. The > > first time an X server is started, everything works fine, including > > glx loading. After exiting the X session and shutting down the > > server and then at some point later starting the X server again, the > > system will freeze. No messages, no panic, nothing. The only thing > > to do is hit the reset button. > > I played with this a bit more tonight. I rebuilt the kernel (fresh > cvsup) and the nvidia-driver bits. I even tried loading without glx. > I still have the same problem. At this point I do not know if this is > a problem with the nvidia-driver port, a problem with -current, or > something I am doing wrong. Does anybody have a functioning nvidia card > with FreeBSD -current at this time? Yes I do. I posted to the list a few days with a glx problem. However the problem was solved when I did an update one day ago. I didn't have to changed anything either. I didn't know what was wrong for some reason X would about with sig 10 or 11 when the glx module was loaded. have you checked out: http://www.soulwax.net/nvidia/faq.shtml They list a whole bunch of things to try. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: nvidia-driver not loading GLX.
Another folloup: I've just re-cvsup today and built world an everythin appears ok so far uname -a: FreeBSD nova 5.1-CURRENT FreeBSD 5.1-CURRENT #4: Mon Aug 4 13:08:34 EST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/NOVA i386 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: nvidia-driver not loading GLX.
Just a follow-up. This is what happens when I run on an generic kernel. nvidia0: mem 0xf000-0xf7ff,0xdf00-0xdfff irq 11 at device 0.0 on pci1 malloc() of "32" with the following non-sleepablelocks held: exclusive sleep mutex dev.mtx_api r = 0 (0xc468718c) locked @ /usr/ports/x11/nvidia-driver/work/NVIDIA-FreeBSD-x86-1.0-4365/src/nvidia_subr.c:753 malloc() of "32" with the following non-sleepablelocks held: exclusive sleep mutex dev.mtx_api r = 0 (0xc468718c) locked @ /usr/ports/x11/nvidia-driver/work/NVIDIA-FreeBSD-x86-1.0-4365/src/nvidia_subr.c:753 malloc() of "4096" with the following non-sleepablelocks held: exclusive sleep mutex dev.mtx_api r = 0 (0xc468718c) locked @ /usr/ports/x11/nvidia-driver/work/NVIDIA-FreeBSD-x86-1.0-4365/src/nvidia_subr.c:753 malloc() of "32" with the following non-sleepablelocks held: exclusive sleep mutex dev.mtx_api r = 0 (0xc468718c) locked @ /usr/ports/x11/nvidia-driver/work/NVIDIA-FreeBSD-x86-1.0-4365/src/nvidia_subr.c:753 malloc() of "32" with the following non-sleepablelocks held: exclusive sleep mutex dev.mtx_api r = 0 (0xc468718c) locked @ /usr/ports/x11/nvidia-driver/work/NVIDIA-FreeBSD-x86-1.0-4365/src/nvidia_subr.c:753 malloc() of "4096" with the following non-sleepablelocks held: exclusive sleep mutex dev.mtx_api r = 0 (0xc468718c) locked @ /usr/ports/x11/nvidia-driver/work/NVIDIA-FreeBSD-x86-1.0-4365/src/nvidia_subr.c:753 malloc() of "32" with the following non-sleepablelocks held: exclusive sleep mutex dev.mtx_api r = 0 (0xc468718c) locked @ /usr/ports/x11/nvidia-driver/work/NVIDIA-FreeBSD-x86-1.0-4365/src/nvidia_subr.c:753 malloc() of "32" with the following non-sleepablelocks held: exclusive sleep mutex dev.mtx_api r = 0 (0xc468718c) locked @ /usr/ports/x11/nvidia-driver/work/NVIDIA-FreeBSD-x86-1.0-4365/src/nvidia_subr.c:753 malloc() of "4096" with the following non-sleepablelocks held: exclusive sleep mutex dev.mtx_api r = 0 (0xc468718c) locked @ /usr/ports/x11/nvidia-driver/work/NVIDIA-FreeBSD-x86-1.0-4365/src/nvidia_subr.c:753 malloc() of "32" with the following non-sleepablelocks held: exclusive sleep mutex dev.mtx_api r = 0 (0xc468718c) locked @ /usr/ports/x11/nvidia-driver/work/NVIDIA-FreeBSD-x86-1.0-4365/src/nvidia_subr.c:753 malloc() of "32" with the following non-sleepablelocks held: exclusive sleep mutex dev.mtx_api r = 0 (0xc468718c) locked @ /usr/ports/x11/nvidia-driver/work/NVIDIA-FreeBSD-x86-1.0-4365/src/nvidia_subr.c:753 malloc() of "32" with the following non-sleepablelocks held: exclusive sleep mutex dev.mtx_api r = 0 (0xc468718c) locked @ /usr/ports/x11/nvidia-driver/work/NVIDIA-FreeBSD-x86-1.0-4365/src/nvidia_subr.c:753 malloc() of "VM OBJECT" with the following non-sleepablelocks held: exclusive sleep mutex dev.mtx_api r = 0 (0xc468718c) locked @ /usr/ports/x11/nvidia-driver/work/NVIDIA-FreeBSD-x86-1.0-4365/src/nvidia_subr.c:753 malloc() of "DP fakepg" with the following non-sleepablelocks held: exclusive sleep mutex ctl.mtx_api r = 0 (0xc484a1ac) locked @ /usr/ports/x11/nvidia-driver/work/NVIDIA-FreeBSD-x86-1.0-4365/src/nvidia_subr.c:753 malloc() of "32" with the following non-sleepablelocks held: exclusive sleep mutex dev.mtx_api r = 0 (0xc468718c) locked @ /usr/ports/x11/nvidia-driver/work/NVIDIA-FreeBSD-x86-1.0-4365/src/nvidia_subr.c:753 malloc() of "32" with the following non-sleepablelocks held: exclusive sleep mutex dev.mtx_api r = 0 (0xc468718c) locked @ /usr/ports/x11/nvidia-driver/work/NVIDIA-FreeBSD-x86-1.0-4365/src/nvidia_subr.c:753 malloc() of "4096" with the following non-sleepablelocks held: exclusive sleep mutex dev.mtx_api r = 0 (0xc468718c) locked @ /usr/ports/x11/nvidia-driver/work/NVIDIA-FreeBSD-x86-1.0-4365/src/nvidia_subr.c:753 malloc() of "32" with the following non-sleepablelocks held: exclusive sleep mutex dev.mtx_api r = 0 (0xc468718c) locked @ /usr/ports/x11/nvidia-driver/work/NVIDIA-FreeBSD-x86-1.0-4365/src/nvidia_subr.c:753 malloc() of "32" with the following non-sleepablelocks held: exclusive sleep mutex dev.mtx_api r = 0 (0xc468718c) locked @ /usr/ports/x11/nvidia-driver/work/NVIDIA-FreeBSD-x86-1.0-4365/src/nvidia_subr.c:753 malloc() of "32768" with the following non-sleepablelocks held: exclusive sleep mutex dev.mtx_api r = 0 (0xc468718c) locked @ /usr/ports/x11/nvidia-driver/work/NVIDIA-FreeBSD-x86-1.0-4365/src/nvidia_subr.c:753 malloc() of "DP fakepg" with the following non-sleepablelocks held: exclusive sleep mutex ctl.mtx_api r = 0 (0xc484a1ac) locked @ /usr/ports/x11/nvidia-driver/work/NVIDIA-FreeBSD-x86-1.0-4365/src/nvidia_subr.c:753 pid 616 (XFree86), uid 0: exited on signal 6 (core dumped) lock order reversal ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
nvidia-driver not loading GLX.
Hello list, I'm having some problems getting 3D support on my Ti4800SE. I've built nvidia-driver-1.0.4365 with WITH_NVIDIA_HACKS and without. I've used and not used the FreeBSD agp module. but I keep getting the same error when I try to start X with the loading the glx module. Attached is my dmesg output, /var/log/XFree86.0.log and my X config. uname -a returns: FreeBSD nova 5.1-CURRENT FreeBSD 5.1-CURRENT #3: Fri Aug 1 01:16:29 EST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/NOVA i386 X loads up fine when I comment out 'Load "glx"'. Also I get "Bus error (core dumped)" with some programs, mplayer for one. Anyways some help would be much appreciated -Al Copyright (c) 1992-2003 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.1-CURRENT #3: Fri Aug 1 01:16:29 EST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/NOVA Preloaded elf kernel "/boot/kernel/kernel" at 0xc06da000. Preloaded elf module "/boot/modules/vesa.ko" at 0xc06da244. Preloaded elf module "/boot/modules/cd9660.ko" at 0xc06da2f0. Preloaded elf module "/boot/modules/msdosfs.ko" at 0xc06da39c. Preloaded elf module "/boot/modules/procfs.ko" at 0xc06da44c. Preloaded elf module "/boot/modules/pseudofs.ko" at 0xc06da4f8. Preloaded elf module "/boot/modules/md.ko" at 0xc06da5a8. Preloaded elf module "/boot/modules/linux.ko" at 0xc06da650. Preloaded elf module "/boot/modules/sysvshm.ko" at 0xc06da6fc. Preloaded elf module "/boot/modules/sysvsem.ko" at 0xc06da7ac. Preloaded elf module "/boot/modules/sysvmsg.ko" at 0xc06da85c. Preloaded elf module "/boot/modules/if_ppp.ko" at 0xc06da90c. Preloaded elf module "/boot/modules/if_tun.ko" at 0xc06da9b8. Preloaded elf module "/boot/modules/miibus.ko" at 0xc06daa64. Preloaded elf module "/boot/modules/if_rl.ko" at 0xc06dab10. Preloaded elf module "/boot/modules/ng_bpf.ko" at 0xc06dabbc. Preloaded elf module "/boot/modules/netgraph.ko" at 0xc06dac68. Preloaded elf module "/boot/modules/ng_ether.ko" at 0xc06dad18. Preloaded elf module "/boot/modules/ng_ppp.ko" at 0xc06dadc8. Preloaded elf module "/boot/modules/snd_pcm.ko" at 0xc06dae74. Preloaded elf module "/boot/modules/snd_emu10k1.ko" at 0xc06daf24. Preloaded elf module "/boot/modules/usb.ko" at 0xc06dafd8. Preloaded elf module "/boot/modules/uhid.ko" at 0xc06db084. Preloaded elf module "/boot/modules/ukbd.ko" at 0xc06db130. Preloaded elf module "/boot/modules/ums.ko" at 0xc06db1dc. Preloaded elf module "/boot/modules/umass.ko" at 0xc06db288. Preloaded elf module "/boot/modules/random.ko" at 0xc06db334. Preloaded elf module "/boot/modules/linprocfs.ko" at 0xc06db3e0. Preloaded elf module "/boot/modules/firewire.ko" at 0xc06db490. Preloaded elf module "/boot/modules/fdc.ko" at 0xc06db540. Preloaded elf module "/boot/modules/acpi.ko" at 0xc06db5ec. Preloaded elf module "/boot/modules/nvidia.ko" at 0xc06db698. Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 2533056136 Hz CPU: Intel(R) Pentium(R) 4 CPU 2.53GHz (2533.06-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf27 Stepping = 7 Features=0xbfebfbff real memory = 536854528 (511 MB) avail memory = 514031616 (490 MB) Pentium Pro MTRR support enabled VESA: v3.0, 131072k memory, flags:0x1, mode table:0xc0376c62 (122) VESA: NVIDIA npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard pcibios: BIOS version 2.10 Using $PIR table, 11 entries at 0xc00f1720 acpi0: power button is handled as a fixed feature programming model. Timecounter "ACPI-fast" frequency 3579545 Hz acpi_timer0: <24-bit timer at 3.579545MHz> port 0xe408-0xe40b on acpi0 acpi_cpu0: on acpi0 acpi_cpu1: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib0: slot 2 INTA is routed to irq 11 pcib0: slot 3 INTA is routed to irq 9 pcib0: slot 3 INTB is routed to irq 9 pcib0: slot 3 INTC is routed to irq 9 pcib0: slot 14 INTA is routed to irq 11 pcib1: at device 1.0 on pci0 pci1: on pcib1 pcib1: slot 0 INTA is routed to irq 11 nvidia0: mem 0xf000-0xf7ff,0xdf00-0xdfff irq 11 at device 0.0 on pci1 isab0: at device 2.0 on pci0 isa0: on isab0 fwohci0: vendor=1039, dev=7007 fwohci0: <1394 Open Host Controller Interface> mem 0xde80-0xde800fff at device 2.3 on pci0 pcib0: slot 2 INTB is routed to irq 5 fwohci0: OHCI version 1.0 (ROM=1) fwohci0: No. of Isochronous channel is 4. fwohci0: EUI64 00:e0:18:00:00:0a:83:4c fwohci0: Phy 1394a available S400, 2 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: on fwohci0 fwohci0: Initiate bus reset atapci0: port 0xb400-0xb40f,0xb800-0xb803,0xd000-0xd007,0xd400-0xd403,0xd800-0xd807 irq 11 at device 2.5 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: at device 2.7 (no driver attached) ohci0: mem 0xde00-0xde000fff irq 9 at device 3.0 on pci0 usb0: OHCI version 1.0, legacy support usb0: SMM does not respond, resetting usb0: on
Re: Anyone use WINE at all anywhere?
On Saturday, 02 August 2003 10:38, Julian Elischer wrote: > Is the re ANYONE that uses wine on -current...? > > for that matter, a -current user that uses wine on 4.x? Well I used to use wine to play Quake2 and load flash programs but ever since moving from Windows 98 to XP wine doesn't really seem to work at all. Not there is much reason left to use it as I don't use Windows XP much anymore. > julian > > > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Followup to: Trouble building XFree86-4-Clients.
Well it was Xft. I feel stupid, sorry for wasting peoples time. Anyways I think I recall what happened, during the portupgrade I was playing around with X and caused a system crash. This may have happened during the Xft removal/upgrade stage of portupgrade. All is well now, thanks Daniel To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Trouble building XFree86-4-Clients.
On Saturday, 22 March 2003 22:17, Daniel O'Connor wrote: > On Sat, 2003-03-22 at 20:38, Alastair G. Hogge wrote: > > I've been able to portupgrade my XFree86-4.2.1 system[1] to 4.3.0 expect > > the 4.3.0 clients port. I've tried completely removing and building it > > manuly thru "make install" but I get the same. > > -DMITSHM -DXFT -DXRENDER -c do_text.c > > do_text.c:403:25: X11/Xft/Xft.h: No such file or directory > > Tried making sure Xft and fontconfig are up to date? Both were updated with portupgrade. > I had trouble with that when I updated. Wait...blast Xft doesn't appear to be installed anymore. I know I updated to Xft-2.1_3 before the X-4.3.0 upgrade. Well I'll try clients again now, that I re-reinstall Xft. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Trouble building XFree86-4-Clients.
Hello, I've been able to portupgrade my XFree86-4.2.1 system[1] to 4.3.0 expect the 4.3.0 clients port. I've tried completely removing and building it manuly thru "make install" but I get the same. The log from the build can be found here: http://www4.tpg.com.au/users/jhogge/log But here is the tail++ end: cc -O -pipe -mcpu=pentiumpro -ansi -Dasm=__asm -Wall -Wpointer-arith -Wundef -I/usr/X11R6/include -I/usr/local/include/ freetype2 -I/usr/local/include -I/usr/ports/x11/XFree86-4-clients/work/xc -I/usr/ports/x11/XFree86-4-clients/work/xc/ex ports/include -I/usr/X11R6/include -DCSRG_BASED -DFUNCPROTO=15 -DNARROWPROTO -DMITSHM -DXFT -DXRENDER -c do_text.c do_text.c:403:25: X11/Xft/Xft.h: No such file or directory do_text.c:405: syntax error before '*' token do_text.c:405: warning: type defaults to `int' in declaration of `aafont' do_text.c:405: warning: data definition has no type or storage class do_text.c:406: syntax error before '*' token do_text.c:406: warning: type defaults to `int' in declaration of `aadraw' do_text.c:406: warning: data definition has no type or storage class do_text.c:407: syntax error before "aacolor" do_text.c:407: warning: type defaults to `int' in declaration of `aacolor' do_text.c:407: warning: data definition has no type or storage class do_text.c: In function `InitAAText': do_text.c:416: warning: implicit declaration of function `XftFontOpenName' do_text.c:416: warning: assignment makes pointer from integer without a cast do_text.c:425: warning: implicit declaration of function `XftDrawCreate' do_text.c:427: warning: assignment makes pointer from integer without a cast do_text.c:432: warning: implicit declaration of function `XftFontClose' do_text.c:439: warning: implicit declaration of function `XftColorAllocValue' do_text.c:446: warning: implicit declaration of function `XftDrawDestroy' do_text.c:453: request for member `height' in something not a structure or union do_text.c: In function `DoAAText': do_text.c:483: warning: implicit declaration of function `XftDrawString8' do_text.c: In function `EndAAText': do_text.c:508: warning: implicit declaration of function `XftColorFree' *** Error code 1 Stop in /usr/ports/x11/XFree86-4-clients/work/xc/programs/x11perf. *** Error code 1 Stop in /usr/ports/x11/XFree86-4-clients/work/xc/programs. *** Error code 1 Stop in /usr/ports/x11/XFree86-4-clients. Thanks in advance -Al 1]X system: /var/db/pkg/XFree86-4.3.0,1 /var/db/pkg/XFree86-FontServer-4.3.0 /var/db/pkg/XFree86-Server-4.3.0_2 /var/db/pkg/XFree86-VirtualFramebufferServer-4.3.0 /var/db/pkg/XFree86-documents-4.3.0 /var/db/pkg/XFree86-font100dpi-4.3.0 /var/db/pkg/XFree86-font75dpi-4.3.0 /var/db/pkg/XFree86-fontCyrillic-4.3.0 /var/db/pkg/XFree86-fontDefaultBitmaps-4.3.0 /var/db/pkg/XFree86-fontEncodings-4.3.0 /var/db/pkg/XFree86-fontScalable-4.3.0 /var/db/pkg/XFree86-libraries-4.3.0_1 /var/db/pkg/XFree86-manuals-4.3.0 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: sis chipset
On Wednesday, 26 February 2003 21:13, C. Kukulies wrote: > My ASUS board has a SiS 963 chip and I would like to get rid from the extra > 3COM card I have presently in my system. > > Is there a chance to get the built in 100MBit network adapter in the > chipset working somehow? I have an ASUS P4S8X with the SiS 963 South Bridge. The RealTek network chip works fine. I added "device miibus" and "device rl" to my kernel conf. I also added a startup script to set the device media to 100baseTX. 100baseTX-FDX for some reason returns "unknown media subtype: 100baseTX-FDX" even thou the kernel reports that mode on startup. HTH -Al To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Recent CVSup on a P4S8X mainboard.
Hello list, I've been using Current for some time now, and have in the last 2 or so weeks updated my box a little. I installed an ASUS P4S8X main board with all the options. Most things were running fine until today..my most recent CVSup. I think it may be the audio that causing my problem I now have no sound from my SBLive. I've tried disabling the Sigmatel AC97 chip thru the BIOS, but this changes nothing. Everytime I try to play something I get a constant beep. And kernel messages of "pcm0: pci error" Copyright (c) 1992-2003 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #5: Fri Feb 21 16:27:46 EST 2003 agh@nova:/usr/obj/usr/src/sys/NOVA Preloaded elf kernel "/boot/kernel/kernel" at 0xc04df000. Preloaded elf module "/boot/kernel/if_ppp.ko" at 0xc04df0a8. Preloaded elf module "/boot/kernel/if_tun.ko" at 0xc04df154. Preloaded elf module "/boot/kernel/miibus.ko" at 0xc04df200. Preloaded elf module "/boot/kernel/if_rl.ko" at 0xc04df2ac. Preloaded elf module "/boot/kernel/snd_pcm.ko" at 0xc04df358. Preloaded elf module "/boot/kernel/snd_emu10k1.ko" at 0xc04df404. Preloaded elf module "/boot/kernel/ugen.ko" at 0xc04df4b4. Preloaded elf module "/boot/kernel/uhid.ko" at 0xc04df560. Preloaded elf module "/boot/kernel/ukbd.ko" at 0xc04df60c. Preloaded elf module "/boot/kernel/ums.ko" at 0xc04df6b8. Preloaded elf module "/boot/kernel/umass.ko" at 0xc04df760. Preloaded elf module "/boot/kernel/agp.ko" at 0xc04df80c. Preloaded elf module "/boot/kernel/atspeaker.ko" at 0xc04df8b4. Preloaded elf module "/boot/kernel/acpi.ko" at 0xc04df964. Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 2533060308 Hz CPU: Intel(R) Pentium(R) 4 CPU 2.53GHz (2533.06-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf27 Stepping = 7 Features=0xbfebfbff real memory = 536854528 (511 MB) avail memory = 516120576 (492 MB) Pentium Pro MTRR support enabled npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard ACPI-0625: *** Info: GPE Block0 defined as GPE0 to GPE15 ACPI-0625: *** Info: GPE Block1 defined as GPE16 to GPE31 pcibios: BIOS version 2.10 Using $PIR table, 11 entries at 0xc00f1720 acpi0: power button is handled as a fixed feature programming model. Timecounter "ACPI-fast" frequency 3579545 Hz acpi_timer0: <24-bit timer at 3.579545MHz> port 0xe408-0xe40b on acpi0 acpi_cpu0: on acpi0 acpi_cpu1: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 agp0: mem 0xd000-0xd7ff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at device 0.0 (no driver attached) pci1: at device 0.1 (no driver attached) isab0: at device 2.0 on pci0 isa0: on isab0 pci0: at device 2.3 (no driver attached) atapci0: port 0xa400-0xa40f,0xa800-0xa803,0xb000-0xb007,0xb400-0xb403,0xb800-0xb807 irq 11 at device 2.5 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: at device 2.7 (no driver attached) ohci0: mem 0xce00-0xce000fff irq 9 at device 3.0 on pci0 usb0: OHCI version 1.0, legacy support usb0: SMM does not respond, resetting usb0: on ohci0 usb0: USB revision 1.0 uhub0: SiS OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered ohci1: mem 0xcd80-0xcd800fff irq 9 at device 3.1 on pci0 usb1: OHCI version 1.0, legacy support usb1: SMM does not respond, resetting usb1: on ohci1 usb1: USB revision 1.0 uhub1: SiS OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered ohci2: mem 0xcd00-0xcd000fff irq 9 at device 3.2 on pci0 usb2: OHCI version 1.0, legacy support usb2: SMM does not respond, resetting usb2: on ohci2 usb2: USB revision 1.0 uhub2: SiS OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered ums0: Microsoft Microsoft IntelliMouse\M-. Explorer, rev 1.10/1.14, addr 2, iclass 3/1 ums0: 5 buttons and Z dir. pci0: at device 3.3 (no driver attached) pci0: at device 4.0 (no driver attached) pcm0: port 0x8400-0x841f irq 5 at device 10.0 on pci0 pcm0: atapci1: port 0x7000-0x707f,0x7400-0x740f,0x7800-0x783f mem 0xcb00-0xcb01,0xcb80-0xcb800fff irq 11 at device 14.0 on pci0 atapci1: Busmastering DMA not configured ata2: at 0x7800 on atapci1 speaker0 port 0x61 on acpi0 fdc0: port 0x3f7,0x3f2-0x3f5 irq 6 drq 2 on acpi0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ppc0 port 0x778-0x77b,0x378-0x37f irq 7 drq 3 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/9 bytes threshold ppi0: on ppbus0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port sio0 port 0x3f8-0x3ff irq 4 on acpi0 sio0: type 16550A sio1 port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atk
