Re: Manual root filesystem specification
On Sun, Feb 12, 2006 at 11:50:37PM +0100, Julius Hacker wrote: I've installed a 6.0 here on my computer. Alright, all works fine but at boot time I've to specify manually a root filesystem. Can you post the messages printed just before you are asked to manually specify the filesystem? There might be a clue as to why it is not finding it automatically. David. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD6 freeze at boot
Hi, I use freebsd 6 on my main router without problems since it was released by i am actually working on an embedded system, i built the minimal system without much problems it now works well but the problem here is that sometime it will just freze while booting and wait there for a random time, and sometime it never unfreeze, I don't know if it can help but here is the output of 'dmesg' : real memory = 528416768 (503 MB) avail memory = 507764736 (484 MB) npx0: [FAST] npx0: math processor on motherboard npx0: INT 16 interface cpu0 on motherboard pcib0: Host to PCI bridge pcibus 0 on motherboard pir0: PCI Interrupt Routing Table: 7 Entries on motherboard $PIR: BIOS IRQ 5 for 0.7.INTC does not match link 0x5 irq 11 $PIR: BIOS IRQ 11 for 0.7.INTD does not match link 0x1 irq 12 pci0: PCI bus on pcib0 agp0: VIA 8601 (Apollo ProMedia/PLE133Ta) host to PCI bridge mem 0xe000-0xe3ff at device 0.0 on pci0 pcib1: PCI-PCI bridge at device 1.0 on pci0 pci1: PCI bus on pcib1 pci1: display, VGA at device 0.0 (no driver attached) isab0: PCI-ISA bridge at device 7.0 on pci0 isa0: ISA bus on isab0 atapci0: VIA 82C686B UDMA100 controller port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xc000-0xc00f at device 7.1 on pci0 ata0: ATA channel 0 on atapci0 ata1: ATA channel 1 on atapci0 uhci0: VIA 83C572 USB controller port 0xc400-0xc41f irq 11 at device 7.2 on pci0 uhci0: [GIANT-LOCKED] usb0: VIA 83C572 USB controller 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 uhci1: VIA 83C572 USB controller port 0xc800-0xc81f irq 11 at device 7.3 on pci0 uhci1: [GIANT-LOCKED] usb1: VIA 83C572 USB controller 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 pci0: bridge at device 7.4 (no driver attached) pci0: multimedia, audio at device 7.5 (no driver attached) rl0: RealTek 8139 10/100BaseTX port 0xd800-0xd8ff mem 0xe581-0xe58100ff irq 12 at device 8.0 on pci0 miibus0: MII bus on rl0 rlphy0: RealTek internal media interface on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto rl0: Ethernet address: 00:40:f4:b8:f4:9e rl1: RealTek 8139 10/100BaseTX port 0xdc00-0xdcff mem 0xe5811000-0xe58110ff irq 10 at device 9.0 on pci0 miibus1: MII bus on rl1 rlphy1: RealTek internal media interface on miibus1 rlphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto rl1: Ethernet address: 00:40:f4:b8:f4:9d rl2: RealTek 8139 10/100BaseTX port 0xe000-0xe0ff mem 0xe5812000-0xe58120ff irq 11 at device 11.0 on pci0 miibus2: MII bus on rl2 rlphy2: RealTek internal media interface on miibus2 rlphy2: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto rl2: Ethernet address: 00:40:f4:b8:f4:9c pmtimer0 on isa0 orm0: ISA Option ROMs at iomem 0xc-0xcbfff,0xcc000-0xc,0xd-0xda7ff,0xdb000-0xe57ff on isa0 atkbdc0: Keyboard controller (i8042) at port 0x60,0x64 on isa0 atkbd0: AT Keyboard irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] fdc0: Enhanced floppy controller at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: [FAST] ppc0: Parallel port at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode ppbus0: Parallel port bus on ppc0 plip0: PLIP network interface on ppbus0 lpt0: Printer on ppbus0 lpt0: Interrupt-driven port ppi0: Parallel I/O on ppbus0 sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x300 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 unknown: PNP0303 can't assign resources (port) unknown: PNP0c01 can't assign resources (memory) unknown: PNP0c02 can't assign resources (memory) unknown: PNP0700 can't assign resources (port) unknown: PNP0501 can't assign resources (port) unknown: PNP0501 can't assign resources (port) unknown: PNP0400 can't assign resources (port) Timecounter TSC frequency 998701672 Hz quality 800 Timecounters tick every 1.000 msec ad2: 976MB Transcend 1G02 1.1 at ata1-master PIO4 Trying to mount root from nfs:192.168.0.1:/usr/jails/neo NFS ROOT: 192.168.0.1:/usr/jails/neo speaker0: PC speaker at port 0x61 on isa0 This system is booted with a remote disk via nfs but the same problem happen when i boot from a local disk (compact flash). The freeze happens after this line: npx0: [FAST] With my understanding of this, it seems it have something against the math processor or something near since it is the line following this one. I really hope someone can help me, I don't really want to have to drop freebsd for another system for this system. Ps: The kernel is GENERIC, I wait until everything works before recompiling a new one. I know there are some warnings but they happen after my freeze problem so i don't think they are related, and the system works well after booting
Re: BIG BIG problem with Xorg and... something else...
Michael W. Lucas wrote: On Wed, Feb 08, 2006 at 10:58:45AM +0100, Gerard Milhaud wrote: Michael W. Lucas wrote: Hook up a serial console, and use script(1) to capture any panic messages, etc. That'll give you a hint as to what's going on, and you can see how to proceed. Thanks a lot for your answer... But how can I use script, because when the problem happens, all the processes are frozen and the file script is being writing is not saved... And which process/command do you suggest I attempt to audit ??? Use script on the machine acting as your console. If it's a Windows box, hyperterm has a capture to file option that will work as well. OK. I've disbaled soft-updates on /. I've sysloged *.info (and therefore *.x where x is more critical than info) to /var/log/all.log. When the X freeze comes, I've no accurate message in my log file... Do you think an external console machine could give me more info ?? It's very hard to figure this out within x11. (Yes, this is a pain, but it could be worse; I'm currently doing a binary search to figure out when, exactly, -current stopped booting on my laptop. :-) Argh !!! I'm not alone lost at the edge of the road... Good luck... No, there are quite a few of us here. Welcome to the cutting edge. :-) Maybe too much sharp-edged for me... Bye and thank you for any idea... -- Gérard MILHAUD École Supérieure d'Ingénieurs de Luminy (ESIL) Université de la Méditerranée Coordonnées : http://annuaire.univ-mrs.fr/showuser.php?uid=milhaud -- [Détente] Essayez donc mon tireur au sort de citations marseillaises : http://planete-marseille.esil.univ-mrs.fr/les.cgi-bin.a.G/citations.pl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: BIG BIG problem with Xorg and... something else...
J. Buck Caldwell wrote: [EMAIL PROTECTED] wrote: Hi all, First don't blame me for cross-posting on stable and x11 lists but both seem relevant for my problem. I'm tracking 6-STABLE. Since one week, I can't use my computer under FreeBSD. The boot is OK, xdm screen is OK. But if I launch a KDE session, I've some color problems during initializing session, then X freezes (before end of loading !!!) and the only way is to poweroff the computer !!! No ssh, no way to CTRL-ALT F1 switching to a console screen, the box is down... I seem to recall something similar being posted recently, having more to do with the X.ORG 6.9 upgrade than anything else. You might try doing a 'portupgrade -af' to rebuild everything against the new libraries. I've done it (19 hours...). It's a little bit better. I've about 300 seconds before the freeze... Thank you for your suggestion. Any other idea from anyone ??? -- Gérard MILHAUD École Supérieure d'Ingénieurs de Luminy (ESIL) Université de la Méditerranée Coordonnées : http://annuaire.univ-mrs.fr/showuser.php?uid=milhaud -- [Détente] Essayez donc mon tireur au sort de citations marseillaises : http://planete-marseille.esil.univ-mrs.fr/les.cgi-bin.a.G/citations.pl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD6 freeze at boot
On Feb 13, 2006, at 7:33 AM, Julien Ammous wrote: I use freebsd 6 on my main router without problems since it was released by i am actually working on an embedded system, i built the minimal system without much problems it now works well but the problem here is that sometime it will just freze while booting and wait there for a random time, and sometime it never unfreeze, I don't know if it can help but here is the output of 'dmesg' : if you disable ACPI does it boot safely? I have a Dell PE 800 server that will not boot with ACPI in freebsd 6.0 or anything newer up thru the 6.1-BETA1 from last friday, but will run 5.4 just fine (all in amd64 mode). ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD6 freeze at boot
In fact i forgot this but I disabled acpi and apic (i don't even know what apic is) in my current config, i tried different configurations like disabling only acpi but the current proved to be the best. Without disabling any of these the system nearly freeze everytime at same point as described in my firt message. What is really annoying is that I have absolutely no idea of what is wrong how i could make things better, since the system is designed to be deployed in closed server rooms at the client company if the server freeze we are in great troubles if noone is around :\ Trying with freebsd 5.4 would really be hard to do and to maintain since my host system is under freebsd 6 (the computer i build compact flash system image on) so i would really prefer another option. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD6 freeze at boot
On Mon, 2006-Feb-13 13:33:56 +0100, Julien Ammous wrote: I use freebsd 6 on my main router without problems since it was released Is this 6.0-RELEASE, RELENG_6_0 or RELENG_6? What motherboard are you using? What CPU is it (you cut this out of your dmesg)? The freeze happens after this line: npx0: [FAST] With my understanding of this, it seems it have something against the math processor or something near since it is the line following this one. This implies it's hanging in npx_probe() which suggests that there is something wrong with the math co-processor interface. Ps: The kernel is GENERIC, I wait until everything works before recompiling a new one. I know there are some warnings but they happen after my freeze problem so i don't think they are related, and the system works well after booting (when it boots). What warnings? Are you able to successfully use floating point (and get correct answers)? -- Peter Jeremy ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
pkg_sign pkg_check missing with ports openssl
I am using the ports beta version of openssl in order to try to get OpenCA working on a 6.1pre release system. I buildworld and installworld with the following in /etc/make.conf NO_OPENSSL=true WITH_OPENSSL_PORT=yes WITH_OPENSSL_BETA=yes This doesn't install pkg_sign and pkg_check since they depend on openssl. I installed the ports for openssl-beta, openssh-portable and heimdal to add back in the crypto left out of the base system, but I cannot figure out how to get pkg_sign and pkg_check back and if I even need to worry about it. Bill ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: pkg_sign pkg_check missing with ports openssl
On Mon, Feb 13, 2006 at 12:47:50PM -0600, Bill Milford wrote: I am using the ports beta version of openssl in order to try to get OpenCA working on a 6.1pre release system. I buildworld and installworld with the following in /etc/make.conf NO_OPENSSL=true WITH_OPENSSL_PORT=yes WITH_OPENSSL_BETA=yes This doesn't install pkg_sign and pkg_check since they depend on openssl. Right. They won't link to an openssl in a non-default location. I installed the ports for openssl-beta, openssh-portable and heimdal to add back in the crypto left out of the base system, but I cannot figure out how to get pkg_sign and pkg_check back and if I even need to worry about it. You probably wanted to tell them to install into /usr, not /usr/local. Check the port makefiles for the knob for enabling this. Kris pgpwR7Sp8c4vv.pgp Description: PGP signature
Re: FreeBSD6 freeze at boot
Peter Jeremy wrote: On Mon, 2006-Feb-13 13:33:56 +0100, Julien Ammous wrote: I use freebsd 6 on my main router without problems since it was released Is this 6.0-RELEASE, RELENG_6_0 or RELENG_6? What motherboard are you using? What CPU is it (you cut this out of your dmesg)? I use 6.0-RELEASE here what i cut (i didn't see i removed a part): Copyright (c) 1992-2005 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 6.0-RELEASE #0: Thu Nov 3 09:36:13 UTC 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC Timecounter i8254 frequency 1193182 Hz quality 0 CPU: VIA C3 Nehemiah+RNG+ACE (998.70-MHz 686-class CPU) Origin = CentaurHauls Id = 0x698 Stepping = 8 Features=0x381b93fFPU,VME,DE,PSE,TSC,MSR,CX8,SEP,MTRR,PGE,CMOV,PAT,MMX,FXSR,SSE And for motherboard you have full details here: http://www.lex.com.tw:8080/product/CV860A.htm Here is the chipsets list: . MB chipset : VIA PLE133 VT8601A and VT82C686B . VGA : Trident graphics integrated in VIA VT8601A chip . Sound : VIA VT1612,AC97 Sound . LAN : 1~ 3 x 10/100Mbps LAN( Optional of Realtek or Intel ) The freeze happens after this line: npx0: [FAST] With my understanding of this, it seems it have something against the math processor or something near since it is the line following this one. This implies it's hanging in npx_probe() which suggests that there is something wrong with the math co-processor interface. Ps: The kernel is GENERIC, I wait until everything works before recompiling a new one. I know there are some warnings but they happen after my freeze problem so i don't think they are related, and the system works well after booting (when it boots). What warnings? I was just speaking about these lines in the dmesg output: unknown: PNP0303 can't assign resources (port) unknown: PNP0c01 can't assign resources (memory) unknown: PNP0c02 can't assign resources (memory) unknown: PNP0700 can't assign resources (port) unknown: PNP0501 can't assign resources (port) unknown: PNP0501 can't assign resources (port) unknown: PNP0400 can't assign resources (port) Are you able to successfully use floating point (and get correct answers)? What is the simplest way to test it ? I have tried rebooting the computer in loop today (something like 20 times) and it appears that the freeze is really totally random, sometimes it happens, sometimes not and when it freezes the frozen time is also random. Thanks for your help. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: smb_maperror: Unmapped error 1:158
Mike Jakubik wrote: Steve Hodgson wrote: Mike Jakubik wrote: Jan 26 17:01:47 desktop kernel: smb_maperror: Unmapped error 1:158 Jan 26 17:02:18 desktop last message repeated 52 times Jan 26 17:04:19 desktop last message repeated 646 times Jan 26 17:14:20 desktop last message repeated 6342 times The fix for this out of the NetBSD source tree is (apply in /usr/src): --- sys/netsmb/smb_subr.old Mon Feb 13 20:21:09 2006 +++ sys/netsmb/smb_subr.c Mon Feb 13 20:23:49 2006 @@ -273,6 +273,9 @@ return EEXIST; case ERRquota: return EDQUOT; + case ERRnotlocked: + /* it's okay to try to unlock already unlocked file */ + return 0; } break; case ERRSRV: When I tried this I got couldn't logon to the server, and I got smb_encrypt: password encryption is not available messages in syslog. The following patch just is essentially a noop, but removes the (original) unmapped 1:158 error: --- sys/netsmb/smb_subr.old Mon Feb 13 20:21:09 2006 +++ sys/netsmb/smb_subr.c Mon Feb 13 20:23:49 2006 @@ -273,6 +273,9 @@ return EEXIST; case ERRquota: return EDQUOT; + case ERRnotlocked: + return EBADRPC; } break; case ERRSRV: I've not tried this though. Steve ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
calcru: negative time (Interrupt Storm on cpu0: timer)
Hello, After reboot yesterday, my system suddenly started to flood syslog with following message: calcru: runtime went backwards from 1966191374 usec to 1966189453 usec for pid 29988 (screen) It's not only screen, i saw sh and su also, but in the last hour only screen. A vmstat -i and the same 5 seconds later: interrupt total rate irq1: atkbd0 1 0 irq13: npx01 0 irq14: ata0 410366 5 irq17: em0 20882069263 cpu0: timer158483081 2000 Total 179775518 2268 interrupt total rate irq1: atkbd0 1 0 irq13: npx01 0 irq14: ata0 410430 5 irq17: em0 20885602263 cpu0: timer158505514 2000 Total 179801548 2268 Is this an interrupt storm? I know that there is a FAQ entry about the negative time issue, but it seems this is more a bad workaround I guess. The system was running without problems for 3 months or so and as I said the problem suddenly appeared yesterday. Any hints on whats wrong here? Thanks in advance, Frank ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: calcru: negative time (Interrupt Storm on cpu0: timer)
Sorry, i forgot to mention: kern.osreldate: 600100 Frank ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: calcru: negative time (Interrupt Storm on cpu0: timer)
Only time I've ever seen this problem is running on a VMWARE virtual server. Is that the case here? If so, try: sysctl kern.timecounter.hardware=TSC That did the trick for me. Frank Steinborn wrote: Hello, After reboot yesterday, my system suddenly started to flood syslog with following message: calcru: runtime went backwards from 1966191374 usec to 1966189453 usec for pid 29988 (screen) It's not only screen, i saw sh and su also, but in the last hour only screen. A vmstat -i and the same 5 seconds later: interrupt total rate irq1: atkbd0 1 0 irq13: npx01 0 irq14: ata0 410366 5 irq17: em0 20882069263 cpu0: timer158483081 2000 Total 179775518 2268 interrupt total rate irq1: atkbd0 1 0 irq13: npx01 0 irq14: ata0 410430 5 irq17: em0 20885602263 cpu0: timer158505514 2000 Total 179801548 2268 Is this an interrupt storm? I know that there is a FAQ entry about the negative time issue, but it seems this is more a bad workaround I guess. The system was running without problems for 3 months or so and as I said the problem suddenly appeared yesterday. Any hints on whats wrong here? Thanks in advance, Frank ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: calcru: negative time (Interrupt Storm on cpu0: timer)
J. Buck Caldwell wrote: Only time I've ever seen this problem is running on a VMWARE virtual server. This is not a VMware system. kern.timecounter.hardware is set to ACPI-fast. Frank ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: calcru: negative time (Interrupt Storm on cpu0: timer)
On Tue, Feb 14, 2006 at 12:09:34AM +0100 I heard the voice of Frank Steinborn, and lo! it spake thus: cpu0: timer158483081 2000 That's not a storm, that's normal. -- Matthew Fuller (MF4839) | [EMAIL PROTECTED] Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
clock reverts to epoch on boot?
I have an odd problem... I've recently upgraded (binary) from FreeBSD 5.4 to FreeBSD 6.0 then CVSUP'ed to STABLE (6.1 Pre-release) a few days ago, around February 10th it looks like (back when my time worked right) :). I went through the whole thing like normal, rebuilt world, built custom kernel, etc... I also updated the BIOS and RAID firmware on the server, a Dell 2650. During this update process it seems FreeBSD's time handling went a little crazy. Although my CMOS clock is correct (I can verify it by rebooting and going into the setup), every time FreeBSD boots, it thinks it is the beginning of Epoch time... I can sync it with ntp, but upon reboot it is right back to Epoch again. I searched the archives and couldn't find this exact problem... Now, I did do a lot of updates and unfortunately didn't notice exactly when it broke. Some programs were acting a little strange (BIND in particular consuming my CPU on bootup until I manually restart it) and my RRD databases are very confused as well as other programs naturally. I *think* this started happening after I did a buildworld/installworld (in single user of course) but I'm not positive. Here is my dmesg output for my hardware: Copyright (c) 1992-2006 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 6.1-PRERELEASE #8: Sat Feb 11 01:39:04 EST 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/ENGBOX ACPI APIC Table: DELL PE2650 Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(TM) CPU 2.80GHz (2782.06-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf29 Stepping = 9 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,C MOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0x4400CNTX-ID,b14 real memory = 4026400768 (3839 MB) avail memory = 3946569728 (3763 MB) FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 6 ioapic0: Changing APIC ID to 8 ioapic1: Changing APIC ID to 9 ioapic2: Changing APIC ID to 10 MADT: Forcing active-low polarity and level trigger for SCI ioapic0 Version 1.1 irqs 0-15 on motherboard ioapic1 Version 1.1 irqs 16-31 on motherboard ioapic2 Version 1.1 irqs 32-47 on motherboard npx0: [FAST] npx0: math processor on motherboard npx0: INT 16 interface acpi0: DELL PE2650 on motherboard acpi0: Power Button (fixed) Timecounter ACPI-safe frequency 3579545 Hz quality 1000 acpi_timer0: 32-bit timer at 3.579545MHz port 0x808-0x80b on acpi0 cpu0: ACPI CPU on acpi0 cpu1: ACPI CPU on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 pci0: unknown at device 4.0 (no driver attached) pci0: unknown at device 4.1 (no driver attached) pci0: unknown at device 4.2 (no driver attached) pci0: display, VGA at device 14.0 (no driver attached) atapci0: ServerWorks CSB5 UDMA100 controller port 0x1f0-0x1f7,0x3f6,0x170-0x17 7,0x376,0x8b0-0x8bf at device 15.1 on pci0 ata0: ATA channel 0 on atapci0 ata1: ATA channel 1 on atapci0 ohci0: OHCI (generic) USB controller mem 0xfe10-0xfe100fff irq 5 at device 15.2 on pci0 ohci0: [GIANT-LOCKED] usb0: OHCI version 1.0, legacy support usb0: SMM does not respond, resetting usb0: OHCI (generic) USB controller on ohci0 usb0: USB revision 1.0 uhub0: (0x1166) OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 4 ports with 4 removable, self powered isab0: PCI-ISA bridge at device 15.3 on pci0 isa0: ISA bus on isab0 pcib1: ACPI Host-PCI bridge on acpi0 pci4: ACPI PCI bus on pcib1 pcib2: ACPI PCI-PCI bridge at device 8.0 on pci4 pci5: ACPI PCI bus on pcib2 aac0: Dell PERC 3/Di mem 0xf000-0xf7ff irq 30 at device 8.1 on pci4 aac0: [FAST] aac0: Adaptec Raid Controller 2.0.0-1 pcib3: ACPI Host-PCI bridge on acpi0 pci3: ACPI PCI bus on pcib3 bge0: Broadcom BCM5703 Gigabit Ethernet, ASIC rev. 0x1002 mem 0xfcf1-0xfcf 1 irq 28 at device 6.0 on pci3 miibus0: MII bus on bge0 brgphy0: BCM5703 10/100/1000baseTX PHY on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX -FDX, auto bge0: Ethernet address: 00:0d:56:ba:73:bf bge1: Broadcom BCM5703 Gigabit Ethernet, ASIC rev. 0x1002 mem 0xfcf0-0xfcf 0 irq 29 at device 8.0 on pci3 miibus1: MII bus on bge1 brgphy1: BCM5703 10/100/1000baseTX PHY on miibus1 brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX -FDX, auto bge1: Ethernet address: 00:0d:56:ba:73:c1 pcib4: ACPI Host-PCI bridge on acpi0 pci2: ACPI PCI bus on pcib4 pcib5: ACPI Host-PCI bridge on acpi0 pci1: ACPI PCI bus on pcib5 fdc0: floppy drive controller port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: [FAST] fd0: 1440-KB 3.5 drive on fdc0 drive 0 atkbdc0: Keyboard controller (i8042) port 0x60,0x64 irq 1 on acpi0 atkbd0: AT Keyboard irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: PS/2 Mouse irq 12 on atkbdc0 psm0:
Re: clock reverts to epoch on boot?
Vinny Abello wrote: [ ... ] I may try doing a cvsup of source and rebuilding again. My make.conf settings are pretty tame: CPUTYPE=pentium4 CFLAGS= -O2 -pipe COPTFLAGS= -O -pipe Remove the CPUTYPE declaration, or at least decrease it to just pentium. -- -Chuck ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: clock reverts to epoch on boot?
At 09:49 PM 2/13/2006, Chuck Swiger wrote: Vinny Abello wrote: [ ... ] I may try doing a cvsup of source and rebuilding again. My make.conf settings are pretty tame: CPUTYPE=pentium4 CFLAGS= -O2 -pipe COPTFLAGS= -O -pipe Remove the CPUTYPE declaration, or at least decrease it to just pentium. OK, I can try that. Come to think of it, I did have it set to p4 previously and I believe it was working. Why would this make a difference? Also, I just booted in single user mode and the clock is correct. Does this likely confirm it is a problem when I did a buildworld with that CPUTYPE set? Vinny Abello Network Engineer Server Management [EMAIL PROTECTED] (973)300-9211 x 125 (973)940-6125 (Direct) PGP Key Fingerprint: 3BC5 9A48 FC78 03D3 82E0 E935 5325 FBCB 0100 977A Tellurian Networks - The Ultimate Internet Connection http://www.tellurian.com (888)TELLURIAN Courage is resistance to fear, mastery of fear - not absence of fear -- Mark Twain ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: clock reverts to epoch on boot?
At 10:04 PM 2/13/2006, Vinny Abello wrote: At 09:49 PM 2/13/2006, Chuck Swiger wrote: Vinny Abello wrote: [ ... ] I may try doing a cvsup of source and rebuilding again. My make.conf settings are pretty tame: CPUTYPE=pentium4 CFLAGS= -O2 -pipe COPTFLAGS= -O -pipe Remove the CPUTYPE declaration, or at least decrease it to just pentium. OK, I can try that. Come to think of it, I did have it set to p4 previously and I believe it was working. Why would this make a difference? Also, I just booted in single user mode and the clock is correct. Does this likely confirm it is a problem when I did a buildworld with that CPUTYPE set? Nevermind. I just answered my own question. I should have RTFM more carefully. :) If CPUTYPE is defined in your /etc/make.conf, make sure to use the ?= instead of the = assignment operator, so that buildworld can override the CPUTYPE if it needs to. I am thinking if I change to CPUTYPE?=pentium4 I will be ok. Does that sound correct or am I still barking up the wrong tree? Thanks!! Vinny Abello Network Engineer Server Management [EMAIL PROTECTED] (973)300-9211 x 125 (973)940-6125 (Direct) PGP Key Fingerprint: 3BC5 9A48 FC78 03D3 82E0 E935 5325 FBCB 0100 977A Tellurian Networks - The Ultimate Internet Connection http://www.tellurian.com (888)TELLURIAN Courage is resistance to fear, mastery of fear - not absence of fear -- Mark Twain ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: clock reverts to epoch on boot?
Vinny Abello wrote: [ ... ] Nevermind. I just answered my own question. I should have RTFM more carefully. :) :-) If CPUTYPE is defined in your /etc/make.conf, make sure to use the ?= instead of the = assignment operator, so that buildworld can override the CPUTYPE if it needs to. I am thinking if I change to CPUTYPE?=pentium4 I will be ok. Does that sound correct or am I still barking up the wrong tree? If you weren't having any problems, feel free to experiment. Since you don't gain much by using the machine-specific compiler optimizations for the kernel, it is worth turning them off to see whether the resulting kernel still has the same problem... -- -Chuck ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: clock reverts to epoch on boot?
At 10:25 PM 2/13/2006, Chuck Swiger wrote: Vinny Abello wrote: [ ... ] Nevermind. I just answered my own question. I should have RTFM more carefully. :) :-) If CPUTYPE is defined in your /etc/make.conf, make sure to use the ?= instead of the = assignment operator, so that buildworld can override the CPUTYPE if it needs to. I am thinking if I change to CPUTYPE?=pentium4 I will be ok. Does that sound correct or am I still barking up the wrong tree? If you weren't having any problems, feel free to experiment. Since you don't gain much by using the machine-specific compiler optimizations for the kernel, it is worth turning them off to see whether the resulting kernel still has the same problem... Will give it a shot and see what happens. So far buildworld isn't using CPU specific optimizations with the CPUTYPE?=pentium4 as documented so I have a feeling that will fix my problem. I actually started having problems after rebuilding world from this source a second time with (what I thought) were more optimized compiler settings. Obviously not if they cause it to break. :) My kernel is the same from when it was working from the original CVSUP and original buildworld so I think I'll be ok with that. I'll rebuild it to be safe anyway though. Thanks again for your help! :) Vinny Abello Network Engineer Server Management [EMAIL PROTECTED] (973)300-9211 x 125 (973)940-6125 (Direct) PGP Key Fingerprint: 3BC5 9A48 FC78 03D3 82E0 E935 5325 FBCB 0100 977A Tellurian Networks - The Ultimate Internet Connection http://www.tellurian.com (888)TELLURIAN Courage is resistance to fear, mastery of fear - not absence of fear -- Mark Twain ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
locale questions
Hi folks, Okay, OpenOffice 2.0 is now spewing out the error message: I18N: Operating system doesn't support locale en_US Hmmm. So, from what I understand from the documentation I have looked at, this is because I do not have an entry in the /etc/ login.conf file covering this entry. Yes/no? Another thing - as I look in /etc/login.conf, I DO have a Russian entry. Why? I assume this is a default, since I have not done anything to /etc/login.conf previously. So, if I do need to create an entry in the login.con file, what is the charset that I define? Thank you, Bruce -- I like bad! Bruce BurdenAustin, TX. - Thuganlitha The Power and the Prophet Robert Don Hughes ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
kernel panic on 6.1-PRERELEASE with Lexar Jumpdrive2
Hello, I've been having kernel panics when I use one particular USB flash drive (LEXAR MEDIA JUMPDRIVE2, rev 2.00/1.25, addr 2) with FreeBSD 6.1-PRERELEASE (See [1] below). All I have to do to get the kernel to panic is to insert and remove the drive from the USB port 2 or 3 times (without mounting the drive. Entries in /dev do not get created. See [2] for error I get when I insert the drive and [3] for the error I get when I remove the drive.) This problem happens only if the ehci device is enabled in the kernel (GENERIC has it enabled by default). If I comment out the ehci device and use only the uhci device, then I get a device entry in /dev and I'm able to mount the flash drive just fine and, insert and remove as many times as I like without any problems. So I suspect that it is a problem with the ehci driver. Unfortunately I'm not being able to get a crash dump as the system starts dumping and then freezes. I wanted to see if there is anybody on the list who has experienced anything similar. I have 2 other newer flash drives and they seem to work fine. The system seems to panic only when I use this particular flash drive. The flash drive is empty and I'm able to mount it fine if I use only the uhci driver. regards, joseph [1]: FreeBSD 6.1-PRERELEASE #0: Sun Feb 12 21:39:40 CST 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC [2]: umass1: LEXAR MEDIA JUMPDRIVE2, rev 2.00/1.25, addr 2 da4 at umass-sim1 bus 1 target 0 lun 0 da4: Generic STORAGE DEVICE 1.25 Removable Direct Access SCSI-0 device da4: 40.000MB/s transfers da4: 125MB (256000 512 byte sectors: 64H 32S/T 125C) (da4:umass-sim1:1:0:0): Synchronize cache failed, status == 0x10, scsi status == 0x0 umass1: Invalid CSW: sig 0x53555355 should be 0x53425355 [3]: umass0: at uhub0 port 5 (addr 2) disconnected (da0:umass-sim0:0:0:0): lost device (da0:umass-sim0:0:0:0): removing device entry umass0: detached umass0: LEXAR MEDIA JUMPDRIVE2, rev 2.00/1.25, addr 2 umass0: BBB reset failed, IOERROR umass0: BBB bulk-in clear stall failed, IOERROR umass0: BBB bulk-out clear stall failed, IOERROR umass0: BBB reset failed, IOERROR umass0: BBB bulk-in clear stall failed, IOERROR umass0: BBB bulk-out clear stall failed, IOERROR umass0: BBB reset failed, IOERROR umass0: BBB bulk-in clear stall failed, IOERROR umass0: BBB bulk-out clear stall failed, IOERROR umass0: BBB reset failed, IOERROR umass0: BBB bulk-in clear stall failed, IOERROR umass0: BBB bulk-out clear stall failed, IOERROR umass0: BBB reset failed, IOERROR umass0: BBB bulk-in clear stall failed, IOERROR umass0: BBB bulk-out clear stall failed, IOERROR umass0: BBB reset failed, IOERROR umass0: BBB bulk-in clear stall failed, IOERROR umass0: BBB bulk-out clear stall failed, IOERROR umass0: BBB reset failed, IOERROR umass0: BBB bulk-in clear stall failed, IOERROR umass0: BBB bulk-out clear stall failed, IOERROR umass0: BBB reset failed, IOERROR umass0: BBB bulk-in clear stall failed, IOERROR umass0: BBB bulk-out clear stall failed, IOERROR umass0: BBB reset failed, IOERROR umass0: BBB bulk-in clear stall failed, IOERROR umass0: BBB bulk-out clear stall failed, IOERROR (da0:umass-sim0:0:0:0): got CAM status 0x4 (da0:umass-sim0:0:0:0): fatal error, failed to attach to device (da0:umass-sim0:0:0:0): lost device umass0: BBB reset failed, IOERROR umass0: BBB bulk-in clear stall failed, IOERROR umass0: BBB bulk-out clear stall failed, IOERROR umass0: BBB reset failed, IOERROR umass0: BBB bulk-in clear stall failed, IOERROR umass0: BBB bulk-out clear stall failed, IOERROR umass0: BBB reset failed, IOERROR umass0: BBB bulk-in clear stall failed, IOERROR umass0: BBB bulk-out clear stall failed, IOERROR umass0: BBB reset failed, IOERROR umass0: BBB bulk-in clear stall failed, IOERROR umass0: BBB bulk-out clear stall failed, IOERROR umass0: BBB reset failed, IOERROR umass0: BBB bulk-in clear stall failed, IOERROR umass0: BBB bulk-out clear stall failed, IOERROR (da0:umass-sim0:0:0:0): removing device entry Opened disk da0 - 5 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Encrypt existing filesystem/partition to GEOM GELI
Hello, I installed FreeBSD-6.0-RELEASE on my laptop and cvsuped to FreeBSD-STABLE. It is working pretty much stable. If possible I would like to migrate existing whole filesystem and partitions to GEOM GELI based encrypted filesystem. How can I to convert/migrate to GEOM GELI without erase/delete/reinstall existing filesystem? Thanks, Balgaa ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: locale questions
On Mon, Feb 13, 2006 at 09:32:18PM -0600, Bruce Burden wrote: Okay, OpenOffice 2.0 is now spewing out the error message: I18N: Operating system doesn't support locale en_US Hmmm. So, from what I understand from the documentation I have looked at, this is because I do not have an entry in the /etc/ login.conf file covering this entry. Yes/no? Sorry, I don't know, but you can also define the cahrset and lang variables in your tcshrc, cshrc or bashrc (depends on the used shell). Another thing - as I look in /etc/login.conf, I DO have a Russian entry. Why? I assume this is a default, since I have not done anything to /etc/login.conf previously. Yes, you have a Russian entry in the login.conf - why not? In the login.conf you can define several login classes and in the fifth column of the master.passwd you can specify the login class for each user. If no login class is specifed the login class default is used. Jan -- Jan Schlesner Tel: +49 30 314 27681 Institut für Theoretische PhysikFax: +49 30 314 21130 Technische Universität Berlin Hardenbergstr. 36, Sekr. PN 7-1, 10623 Berlin -- [ gpg key: http://wwwds.physik.tu-berlin.de/~jan/jschlesn.gpg ] [ key fingerprint: 4236 3497 C4CF 4F3A 274F B6E2 C4F6 B639 1DF4 CF0A ] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Encrypt existing filesystem/partition to GEOM GELI
http://events.ccc.de/congress/2005/fahrplan/attachments/586-paper_Complete_Hard_Disk_Encryption.pdf That pdf covers it pretty well. On 2/13/06, Balgansuren Batsukh [EMAIL PROTECTED] wrote: Hello, I installed FreeBSD-6.0-RELEASE on my laptop and cvsuped to FreeBSD-STABLE. It is working pretty much stable. If possible I would like to migrate existing whole filesystem and partitions to GEOM GELI based encrypted filesystem. How can I to convert/migrate to GEOM GELI without erase/delete/reinstall existing filesystem? Thanks, Balgaa ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: clock reverts to epoch on boot?
At 10:28 PM 2/13/2006, Vinny Abello wrote: At 10:25 PM 2/13/2006, Chuck Swiger wrote: Vinny Abello wrote: [ ... ] Nevermind. I just answered my own question. I should have RTFM more carefully. :) :-) If CPUTYPE is defined in your /etc/make.conf, make sure to use the ?= instead of the = assignment operator, so that buildworld can override the CPUTYPE if it needs to. I am thinking if I change to CPUTYPE?=pentium4 I will be ok. Does that sound correct or am I still barking up the wrong tree? If you weren't having any problems, feel free to experiment. Since you don't gain much by using the machine-specific compiler optimizations for the kernel, it is worth turning them off to see whether the resulting kernel still has the same problem... Will give it a shot and see what happens. So far buildworld isn't using CPU specific optimizations with the CPUTYPE?=pentium4 as documented so I have a feeling that will fix my problem. I actually started having problems after rebuilding world from this source a second time with (what I thought) were more optimized compiler settings. Obviously not if they cause it to break. :) My kernel is the same from when it was working from the original CVSUP and original buildworld so I think I'll be ok with that. I'll rebuild it to be safe anyway though. Thanks again for your help! :) Just following up on this further. It seems the problem was a little more complex (or simple) than this... I had the same problem despite what settings I used for CPUTYPE in my make.conf file. As I stated earlier, booting into single user mode works fine and I have the correct date. I started looking at what was loading on startup when going multiuser. I basically commented out my whole rc.conf.local file except for SSH and then time was correct upon bootup! I put everything back except for time related programs, but the problem came back. I uncommented all my time stuff and on a hunch, I commented out only the line to enable a Backup Exec port from starting. Having this disabled made it so on every startup my system time is now correct. I had noticed an error when that agent was starting since upgrading which I was going to look into. I know it is actually a Linux binary and relies on Linux compatibility in FreeBSD. I'm not sure if the binary was just damaged or if my Linux binary compatibility or some libraries are out of sync. Regardless, I seem to have found the problem... I need to update to the newest agent from Veritas/Symantec anyway instead of this port, although I don't know if that works well either. I'll look into that tomorrow and look into possibly rebuilding my Linux binary port containing the libraries as well, although that was really the only reason I had it installed and my not need it. What is odd is my kernsecurelevel is set to 2 and the time still gets massively adjusted, incorrectly somehow to boot. I think that binary was run in the startup rc scripts prior to kernsecurelevel being raised from -1 to 2 though. Actually, I'm sure of that now, so nevermind. Thanks again for the help. I just wanted to post back what I found to share with others in case someone ever runs into the same oddity. P.S. I CVSUP'ed STABLE, built the kernel and did buildworld with CPUTYPE?=prescott which more accurately matches my actual CPU type. No problems at all to report. :) Vinny Abello Network Engineer Server Management [EMAIL PROTECTED] (973)300-9211 x 125 (973)940-6125 (Direct) PGP Key Fingerprint: 3BC5 9A48 FC78 03D3 82E0 E935 5325 FBCB 0100 977A Tellurian Networks - The Ultimate Internet Connection http://www.tellurian.com (888)TELLURIAN Courage is resistance to fear, mastery of fear - not absence of fear -- Mark Twain ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
