10-CURRENT i386 memstick snapshots broken?
Greetings - I had originally started playing with the 10-CURRENT amd64 release a couple of months ago (no complaints here - keep up the good work!) and had used the memstick snapshot to set things up back then with no problems. Now I'd like to wipe everything and switch to the i386 version, but the memstick images (all of the last 4 or 5) seem to be broken. My machine sees that the USB stick is there, but won't boot off of it at all. When I do 'fdisk' on /dev/da0 with the i386 stuff loaded, I get a invalid partition error, so on a hunch I decided to take a closer look at the memstick images using dd if=xxx-memstick bs=512 count=1 | hd The amd64 images look like what I would expect: some bootblock code with a partition table at the end and the "a5" type marker. The i386 image, however, is ALL '00'. It would appear the whatever puts those memstick images together (src/release/i386/make-memstick.sh, perhaps?) is failing for some reason. Has anyone else tried the i386 memstick and having the same problem? Jimmy ___ 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"
Should lock order reversals be reported?
If so, what is the perferred way of doing so? By PR? Jimmy ___ 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: Problem running VirtualBox
I had the same problem. Turned out that the offending libstdc++.so.6
had be installed by the compat8x package, which had been installed
by the bootstrap-openjdk package. Deleted both of those, and now
Virtualbox finds and use the one supplied by the GCC compiler
used to build it.
Jimmy
On Sun, Sep 15, 2013 at 11:42:04AM -0400, Alex wrote:
> Hi:
>
> When I try to run VirtualBox I get the following error:
>
> VirtualBox: Error -610 in supR3HardenedMainInitRuntime!
> VirtualBox: dlopen("/usr/local/lib/virtualbox/VBoxRT.so",)
> failed: /usr/local/lib/compat/libstdc++.so.6: version GLIBCXX_3.4.15
> required by /usr/local/lib/virtualbox/VBoxRT.so not found
>
> Reinstalling does not solve the issue. Does anyone know what could be
> going wrong?
>
> FreeBSD 10.0-CURRENT #31 r255465
>
> --
> Alex
>
___
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"
xl0: watchdog timeout
Hi I'm getting some strange xl0 timeout messages on 5.1-CURRENT (synced today). I've searched the archives, and it seems that this problem is related to ACPI (http://docs.freebsd.org/cgi/getmsg.cgi?fetch=608457+0+archive/2003/freebsd-current/20031109.freebsd-current) Strange thing is that this worked perfectly with FreeBSD-5.1-RELEASE. The NIC still works, just get "xl0: watchdog timeout" every now and then. I'm attaching a full dmesg in case you know what to look for. The hardware is : AMD Barton 2800 Asus A7V8X Deluxe 1024 mb. DDR333 Ram (PC2700 ?) Promise 20376 SATA raid and the 3x509-TX. /Jimmy 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 Nov 21 18:11:06 CET 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GRUMPY Preloaded elf kernel "/boot/kernel/kernel" at 0xc0905000. Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Athlon(TM) XP 2800+ (2083.11-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x6a0 Stepping = 0 Features=0x383fbff AMD Features=0xc040 real memory = 1073725440 (1023 MB) avail memory = 1033555968 (985 MB) Pentium Pro MTRR support enabled npx0: [FAST] npx0: on motherboard npx0: INT 16 interface pcibios: BIOS version 2.10 Using $PIR table, 12 entries at 0xc00f2080 pcib0: at pcibus 0 on motherboard pci0: on pcib0 pci_cfgintr: 0:8 INTA BIOS irq 10 pci_cfgintr: 0:16 INTA BIOS irq 9 pci_cfgintr: 0:16 INTB BIOS irq 9 pci_cfgintr: 0:16 INTC BIOS irq 9 pci_cfgintr: 0:16 INTD BIOS irq 9 agp0: mem 0xf000-0xf7ff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci_cfgintr: 1:0 INTA BIOS irq 11 pci1: at device 0.0 (no driver attached) fwohci0: port 0xd800-0xd87f mem 0xe480-0xe48007ff at device 7.0 on pci0 pci_cfgintr: 0:7 INTA routed to irq 10 fwohci0: OHCI version 1.0 (ROM=1) fwohci0: No. of Isochronous channel is 8. fwohci0: EUI64 00:e0:18:00:00:0b:51:39 fwohci0: Phy 1394a available S400, 3 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: on fwohci0 sbp0: on firewire0 fwe0: on firewire0 if_fwe0: Fake Ethernet address: 02:e0:18:0b:51:39 fwohci0: Initiate bus reset fwohci0: BUS reset fwohci0: node_id=0xc800ffc0, gen=1, CYCLEMASTER mode firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me) firewire0: bus manager 0 (me) atapci0: port 0xb800-0xb87f,0xd000-0xd00f,0xd400-0xd43f mem 0xe380-0xe381,0xe400-0xe4000fff irq 10 at device 8.0 on pci0 atapci0: [MPSAFE] ata2: at 0xe400 on atapci0 ata2: [MPSAFE] ata3: at 0xe400 on atapci0 ata3: [MPSAFE] ata4: at 0xe400 on atapci0 ata4: [MPSAFE] pci0: at device 9.0 (no driver attached) pci0: at device 10.0 (no driver attached) xl0: <3Com 3c905-TX Fast Etherlink XL> port 0xb400-0xb43f at device 11.0 on pci0 pci_cfgintr: 0:11 INTA routed to irq 4 xl0: Ethernet address: 00:10:4b:3e:1d:b4 miibus0: on xl0 nsphy0: on miibus0 nsphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto pci0: at device 14.0 (no driver attached) fwohci1: vendor=1102, dev=4001 fwohci1: <1394 Open Host Controller Interface> mem 0xe200-0xe2003fff,0xe280-0xe28007ff at device 14.2 on pci0 pci_cfgintr: 0:14 INTB routed to irq 4 fwohci1: OHCI version 1.10 (ROM=0) fwohci1: No. of Isochronous channel is 4. fwohci1: EUI64 00:02:3c:00:91:06:b2:c4 fwohci1: Phy 1394a available S400, 2 ports. fwohci1: Link S400, max_rec 2048 bytes. firewire1: on fwohci1 sbp1: on firewire1 fwe1: on firewire1 if_fwe1: Fake Ethernet address: 02:02:3c:06:b2:c4 fwohci1: Initiate bus reset fwohci1: BUS reset fwohci1: node_id=0xc800ffc0, gen=1, CYCLEMASTER mode firewire1: 1 nodes, maxhop <= 0, cable IRM = 0 (me) firewire1: bus manager 0 (me) uhci0: port 0xa400-0xa41f irq 9 at device 16.0 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered ums0: Microsoft Microsoft 5-Button Mouse with IntelliEye(TM), rev 1.10/3.00, addr 2, iclass 3/1 ums0: 5 buttons and Z dir. uhub0: port error, restarting port 2 uhub0: port error, giving up port 2 uhci1: port 0xa000-0xa01f irq 9 at device 16.1 on pci0 usb1: on uhci1 usb1: USB revision 1.0 uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2: port 0x9800-0x981f irq 9 at device 16.2 on pci0 usb2: on uhci2 usb2: USB revision 1.0 uhub2: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered ugen0: Microsoft SideWinder Game Voice, rev 1.10/1.01, addr 2 pci0: at device 16.3 (no driver attached) isab0: at device 17.0 on pci0 isa0: on isab0 atapci1: port 0x9400-0x940f at device 17.1 on pci0 ata0: at 0x1f0 irq 14 on atapci1 ata0: [MPSAFE] ata1: at 0x170 irq 15 on atapci1 ata1: [MPSAFE] orm0: at iomem 0xd-0xd4fff,0xc-0x
Re: xl0: watchdog timeout
On Fri, 2003-11-21 at 21:29, Kris Kennaway wrote: > On Fri, Nov 21, 2003 at 09:22:49PM +0100, Jimmy Selgen wrote: > I saw this with some of sam's locking changes that (temporarily) broke > DUMMYNET. I see you're using ipfilter - it's possible that this > configuration has not been well-tested. Are you passing much traffic > through ipfilter on this box? The box in question is my workstation, so I guess i'm not passing that much traffic through ipfilter. Also, when I said that the NIC still worked, I might have mislead you a bit. I had about 5-10 timeouts while scp'ing the dmesg output to my other workstation. Data seems to move from userland to the kernel, then get stuck in buffers there for 10-15 seconds, "generating" timeouts, before they're shipped off. I assume this is expected behaviour when a NIC isnt behaving correctly. > > It would be helpful if you can do a binary search to narrow down when > the problem started. What would you have me search ? I'm a faily seasoned C programmer (12 years experience, some of them doing RTOS kernel work), but dont know much about FreeBSD kernel development, or the process of checking out different kernel revisions. I've tried a build without IPFILTER, and the problem still exists. I've also tried booting with ACPI disabled, and the problem is still there. I have attached a copy of my kernel config file, in case i'm doing something wrong. # # GENERIC -- Generic kernel configuration file for FreeBSD/i386 # # For more information on this file, please read the handbook section on # Kernel Configuration Files: # #http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-config.html # # The handbook is also available locally in /usr/share/doc/handbook # if you've installed the doc distribution, otherwise always see the # FreeBSD World Wide Web server (http://www.FreeBSD.org/) for the # latest information. # # An exhaustive list of options and more detailed explanations of the # device lines is also present in the ../../conf/NOTES and NOTES files. # If you are in doubt as to the purpose or necessity of a line, check first # in NOTES. # # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.384 2003/05/18 20:39:15 ru Exp $ machine i386 #cpuI486_CPU #cpuI586_CPU cpu I686_CPU ident GRUMPY #To statically compile in device wiring instead of /boot/device.hints #hints "GENERIC.hints" #Default places to look for devices. #makeoptionsDEBUG=-g#Build kernel with gdb(1) debug symbols #optionsSCHED_4BSD #4BSD scheduler options SCHED_ULE #ULE scheduler options INET#InterNETworking options INET6 #IPv6 communications protocols options FFS #Berkeley Fast Filesystem options SOFTUPDATES #Enable FFS soft updates support options UFS_ACL #Support for access control lists options UFS_DIRHASH #Improve performance on big directories options MD_ROOT #MD is a potential root device options NFSCLIENT #Network Filesystem Client options NFSSERVER #Network Filesystem Server options NFS_ROOT#NFS usable as root device, requires NFSCLIENT options MSDOSFS #MSDOS Filesystem options CD9660 #ISO 9660 Filesystem options PROCFS #Process filesystem (requires PSEUDOFS) options PSEUDOFS#Pseudo-filesystem framework options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options COMPAT_FREEBSD4 #Compatible with FreeBSD4 options SCSI_DELAY=15000#Delay (in ms) before probing SCSI options KTRACE #ktrace(1) support options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores options _KPOSIX_PRIORITY_SCHEDULING #Posix P1003_1B real-time extensions options KBD_INSTALL_CDEV# install a CDEV entry in /dev options AHC_REG_PRETTY_PRINT# Print register bitfields in debug # output. Adds ~128k to driver. options AHD_REG_PRETTY_PRINT# Print register bitfields in debug # output. Adds ~215k to driver. #optionsIPFILTER #optionsPFIL_HOOKS #optionsIPFILTER_LOG #optionsIPFILTER_DEFAULT_BLOCK options CPU_ATHLON_SSE_HACK options CPU_ENABLE_SSE options CPU_FASTER_5X86_FPU options IPSEC options IPSEC_ESP options IPS
user confusion
Hi This might be a common error/misconfiguration, but i've been unable to locate it in the archives.. Using 5.1-RELEASE (upgraded from 5.0 through buildkernel/buildworld). I'm seeing the following "strangeness" I login as a normal user, run who .. shows my own username as logged in. su to another user, logout (back to my own uid), run who, and "su'ed" user is still listed for my session. Here's a little "screenshot" (names have been changed to protect the innocent :* ) -bash-2.05b$ w 11:09PM up 2 days, 11:27, 2 users, load averages: 1.19, 1.17, 1.16 USER TTY FROM LOGIN@ IDLE WHAT test1p0 xxx.xx.x.xxx 11:09PM - w -bash-2.05b$ su - test2 Password: Last login: Thu Mar 6 18:39:11 from something.somewhere. -su-2.05b$ w 11:09PM up 2 days, 11:27, 2 users, load averages: 1.24, 1.18, 1.17 USER TTY FROM LOGIN@ IDLE WHAT test2p0 -11:09PM - w -su-2.05b$ logout -bash-2.05b$ w 11:09PM up 2 days, 11:27, 2 users, load averages: 1.22, 1.18, 1.17 USER TTY FROM LOGIN@ IDLE WHAT test2p0 -11:09PM - w -bash-2.05b$ who am i test2ttyp0Jun 12 23:09 uname -a gives the following : FreeBSD some.where.com 5.1-RELEASE FreeBSD 5.1-RELEASE #16: Tue Jun 10 11:24:37 CEST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/KCONF i386 Any ideas ??. thought i'd run it though -current before submitting to bugs. Jimmy ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD 10.0-ALPHA3 #0 r255878M annoying in console
On Fri, Sep 27, 2013 at 07:43:08AM +0300, Alexander Panyushkin wrote: > Hi all. > > FreeBSD 10.0-ALPHA3 #0 r255878M: Thu Sep 26 18:14:08 EEST 2013 scorpion > kernel: r...@scorpion.kiev.ua:/usr/obj/usr/src/sys/Kernel amd64 > clang version 3.3 (tags/RELEASE_33/final 183502) 20130610 > > After rebuild world my box annoying in console > [...] > Sep 26 20:42:39 scorpion kernel: ata0: FAILURE - zero length DMA > transfer attempted > Sep 26 20:42:39 scorpion kernel: ata0: setting up DMA failed > Sep 26 20:42:39 scorpion kernel: ata0: FAILURE - zero length DMA > transfer attempted > Sep 26 20:42:39 scorpion kernel: ata0: setting up DMA failed > Sep 26 20:42:39 scorpion kernel: ata0: FAILURE - zero length DMA > transfer attempted > Sep 26 20:42:39 scorpion kernel: ata0: setting up DMA failed > Sep 26 20:42:39 scorpion kernel: ata0: FAILURE - zero length DMA > transfer attempted > Sep 26 20:42:39 scorpion kernel: ata0: setting up DMA failed > Sep 26 20:42:39 scorpion kernel: ata0: FAILURE - zero length DMA > transfer attempted > Sep 26 20:42:39 scorpion kernel: ata0: setting up DMA failed > If you have hald enabled, try rebuilding/reinstalling that port (sysutils/hal). That fixed it for me. Jimmy ___ 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: Virtual box require LIBCXX
On Tue, Oct 08, 2013 at 05:01:35PM -0300, Nilton Jose Rizzo wrote:
> Em Tue, 08 Oct 2013 09:43:19 -0700, Eric L. Camachat escreveu
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA256
> >
> > On 10/08/2013 07:17, Nilton Jose Rizzo wrote:
> > > root@valfenda:/usr/ports/emulators/virtualbox-ose # kldload vboxdrv
> > > root@valfenda:/usr/ports/emulators/virtualbox-ose #
> > >
> > > but whern I run it, the I got this error message:
> > > rizzo@valfenda:~/src/Doutorado/visao/testes % VirtualBox
> > > VirtualBox: Error -610 in supR3HardenedMainInitRuntime!
> > > VirtualBox: dlopen("/usr/local/lib/virtualbox/VBoxRT.so",) failed:
> > > /usr/local/lib/compat/libstdc++.so.6: version GLIBCXX_3.4.15 required by
> > > /usr/local/lib/virtualbox/VBoxRT.so not found
> > >
> > My box can be fixed by remove misc/compat8x package.
>
> In my box it was used by bootstrap jdk, look
>
> root@valfenda:/usr # pkg query %ro compat8x-amd64
> java/bootstrap-openjdk
> root@valfenda:/usr #
>
> You don't use java?
>
>
bootstrap-openjdk is only needed to BUILD openjdk. You can and
should remove it after you have successfully built one of the
openjdk packages (see java/bootstrap-openjdk/pkg-message).
You can delete misc/compat8x after that.
Jimmy
___
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"
