Problems with clock
Hi everyone! I have strange problems with my PC clock. Clock seems to be ~2 times faster. What's up? Andris Here is dmesg output: 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-RELEASE-p6 #0: Fri Mar 28 11:45:46 EET 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/MEZHS Preloaded elf kernel /boot/kernel/kernel at 0xc0407000. Preloaded elf module /boot/kernel/acpi.ko at 0xc04070a8. Timecounter i8254 frequency 1193182 Hz Timecounter TSC frequency 333516074 Hz CPU: AMD-K6(tm) 3D processor (333.52-MHz 586-class CPU) Origin = AuthenticAMD Id = 0x58c Stepping = 12 Features=0x8021bfFPU,VME,DE,PSE,TSC,MSR,MCE,CX8,PGE,MMX AMD Features=0x8800SYSCALL,3DNow! real memory = 134152192 (127 MB) avail memory = 125931520 (120 MB) Initializing GEOMetry subsystem K6-family MTRR support enabled (2 registers) VESA: v1.2, 2048k memory, flags:0x0, mode table:0xc00c4eeb (c0004eeb) VESA: S3 Incorporated. 86C775/86C785 npx0: math processor on motherboard npx0: INT 16 interface acpi0: ALi_ on motherboard ACPI-0625: *** Info: GPE Block0 defined as GPE0 to GPE15 ACPI-0625: *** Info: GPE Block1 defined as GPE16 to GPE31 Using $PIR table, 6 entries at 0xc00f7c40 acpi0: power button is handled as a fixed feature programming model. Timecounter ACPI-safe frequency 3579545 Hz acpi_timer0: 32-bit timer at 3.579545MHz port 0x4008-0x400b on acpi0 acpi_cpu0: CPU on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 agp0: Ali M1541 host to AGP bridge mem 0xd000-0xd1ff at device 0.0 on pci0 pcib1: PCI-PCI bridge at device 1.0 on pci0 pci1: PCI bus on pcib1 pci0: bridge, PCI-unknown at device 3.0 (no driver attached) isab0: PCI-ISA bridge at device 7.0 on pci0 isa0: ISA bus on isab0 pci0: display, VGA at device 8.0 (no driver attached) rl0: RealTek 8139 10/100BaseTX port 0xdc00-0xdcff mem 0xebfeff00-0xebfe irq 10 at device 9.0 on pci0 rl0: Realtek 8139B detected. Warning, this may be unstable in autoselect mode rl0: Ethernet address: 00:30:4f:16:8f:79 miibus0: MII bus on rl0 rlphy0: RealTek internal media interface on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto ed0: NE2000 PCI Ethernet (RealTek 8029) port 0xdf80-0xdf9f irq 9 at device 10.0 on pci0 ed0: address 00:48:45:00:07:9e, type NE2000 (16 bit) atapci0: AcerLabs Aladdin ATA33 controller port 0xffa0-0xffaf at device 15.0 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 acpi_button0: Sleep Button on acpi0 atkbdc0: Keyboard controller (i8042) port 0x64,0x60 irq 1 on acpi0 atkbd0: AT Keyboard flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 fdc0: cmd 3 failed at out byte 1 of 3 ppc0 port 0x378-0x37f irq 7 on acpi0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode lpt0: Printer 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 fdc0: cmd 3 failed at out byte 1 of 3 orm0: Option ROM at iomem 0xc-0xc7fff on isa0 pmtimer0 on isa0 fdc0: cannot reserve I/O port range (6 ports) sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x300 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 Timecounters tick every 10.000 msec ipfw2 initialized, divert enabled, rule-based forwarding enabled, default to accept, logging unlimited DUMMYNET initialized (011031) IP Filter: v3.4.29 initialized. Default = pass all, Logging = enabled acpi_cpu: CPU throttling enabled, 8 steps from 100% to 12.5% ad0: 3098MB ST33210A [6296/16/63] at ata0-master UDMA33 Mounting root from ufs:/dev/ad0s1a ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: including a kernel config in another
On Thu, 27 Mar 2003, Glenn Johnson wrote: I would like to include a kernel config file in another, as is done with the SMP config file and how it includes the GENERIC config file. When I try this with including any config file other than GENERIC, I get a syntax error. IS GENERIC the only config that can be included or am I doing something wrong? include in config files is buggy. Here is some saved mail about it. % On Tue, 25 Feb 2003, Bruce Evans wrote: % % On Mon, 24 Feb 2003, David O'Brien wrote: % % On Mon, Feb 24, 2003 at 12:55:04PM +1100, Bruce Evans wrote: %BTW, I've noticed the following defects in `include': %- doesn't work if nested. % % Hum... I have my own i386 kernel config that includes SMP, which in turn % includes GENERIC. Is this the type of nested includes you're referring % to? % % It was, but this seems to have been pilot error (I got a syntax error, % which was probably from not changing myKERNEL.core in the include % statement). % % More testing showed that it wasn't pilot error. Including GENERIC nested % worked in all cases that I tried, but including the core of my kernel % failed in all cases that I tried. I reduced the failure to the following. % Even non-nested includes are broken in some cases: % % %%% % Script started on Tue Feb 25 14:16:01 2003 % ttyp0:[EMAIL PROTECTED]:/usr/src/sys/i386/conf cat FOOBAR % include FOO % ttyp0:[EMAIL PROTECTED]:/usr/src/sys/i386/conf cat FOO % machine i386 % cpu I486_CPU % ident FOO % ttyp0:[EMAIL PROTECTED]:/usr/src/sys/i386/conf config FOOBAR % config: FOO:1: syntax error % ttyp0:[EMAIL PROTECTED]:/usr/src/sys/i386/conf config FOO % Kernel build directory is ../compile/FOO % Don't forget to do a ``make depend'' % ttyp0:[EMAIL PROTECTED]:/usr/src/sys/i386/conf exit % % Script done on Tue Feb 25 14:16:23 2003 % %%% % % Bruce Bruce ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: psmintr: out of sync
On Thu, 2003-03-27 at 21:14, Cameron Murdoch wrote: Hi, Not sure what happened to the original message, sorry for the noise! I am running a recent current: FreeBSD opal.macaroon.net 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Wed Mar 26 16:18:16 GMT 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 The machine is a Dell Inspiron 4000 laptop. It is running XFree86-4.3.0 It has both a trackpad and a pointing stick (?what is the real name for this, I always call them nipples?), and it is seems to be the mouse I am having a problem. Every now and again, but with great regularity the screen will freeze up, so that nothing works, not even the caps lock light. However, it isn't a crash as leaving the machine alone for a random amount of time will normally fix it. Sometimes this delay is a matter of seconds, other times I have left if for about 20+mins. Interestingly enough, pinging the laptop from another computer will always unfreeze it immediately. As this occurs the following is printed to the console: Mar 27 11:23:57 opal kernel: psmintr: out of sync (00c0 != ). Mar 27 11:23:58 opal kernel: psmintr: discard a byte (1). The above appears for each freeze, and every now and again this appears: Mar 27 11:23:57 opal kernel: psmintr: out of sync (00c0 != ). Mar 27 11:23:58 opal kernel: psmintr: discard a byte (1). Mar 27 11:23:58 opal kernel: psmintr: out of sync (0040 != ). Mar 27 11:23:58 opal kernel: psmintr: discard a byte (2). Mar 27 11:23:58 opal kernel: psmintr: out of sync (00c0 != ). Mar 27 11:23:58 opal kernel: psmintr: re-enable the mouse. When the re-enable the mouse message happens then the pointing stick stops working and only the trackpad functions. This started happening with 5-RELEASE though not when -RELEASE was first installed. I am not sure what has caused it. This has actually been happening to me a fair amount too since before 5.0-RELEASE and still on -CURRENT: FreeBSD laptop.internal.irrelevant.org 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Sat Mar 22 12:23:42 GMT 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/LAPTOP i386 If anyone has any ideas feel free to let me know too -- Simon Dick [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: panic: bremfree: removing a buffer not on a queue
My bitty box just crashed out while doing some light desktop work and a small amount of NFS server stuff. FWIW, this problem is repeatable - a few minutes after as I start doing any NFS service, the box crashes out and dies. Any clues on where to start looking? Nick ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ports broken due to -current change (Re: Ports broken on ia64)
Kris Kennaway [EMAIL PROTECTED] writes: On Tue, Mar 18, 2003 at 09:31:48PM -0500, Mike Barcroft wrote: stat.h: $FreeBSD: src/sys/sys/stat.h,v 1.34 2003/03/14 16:09:48 mike Exp $ I think I see the problem. I'll try to get a fix committed by tonight. Still appears to be broken with r1.35: Ugh. The next revision and associated changes fixes it (I actually tested it against osh). Best regards, Mike Barcroft ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: VIA82c686a sound problem
but it requires a reset. Can you apply the attached patch to the head version of via82c686.c and let me know if it works on your h/w and what the additional dmesg information is? It works, flawlessly (at least up to now). Here's the dmesg difference for the kernel with the patch applied: pcm0: VIA VT82C686A port 0xe000-0xe003,0xdc00-0xdcff irq 11 at device 7.5 on pci0 pcm0: Initial status 0x01 pcm0: Post reset status register 0x01 pcm0: Post reset control register 0xcc pcm0: ICEnsemble ICE1232 AC97 Codec Fred -- When I was in school, I cheated on my metaphysics exam: I looked into the soul of the boy sitting next to me. -- Woody Allen pgp0.pgp Description: PGP signature ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Fatal trap 9: general protection fault while in kernel mode
Been tracking -CURENT ( -STABLE, though that is of marginal relevance to this) on a daily basis for a couple of years now. Gone fairly well, usually; sometimes there's turbulence. I suspect this is just a bump, though -- and it's the first one I've encountered in at least a couple of weeeks. Sources updated as of 0347 hrs. US/Pacific; mirror I normally use is cvsup14 (though I noticed that my script fell back to others in the last few days, and I recall that cvsup13 was used yesterday). I'd need to reboot the system to be more definite than that. Got -CURRENT (re-)built; booted, logged in, poked around, seemed OK; issued: sudo boot0cfg -s 1 ad0 sudo halt -p (to switch to default to booting from -STABLE next time I bring the machine up, then power the machine off). Was greeted on the xterm that has the serial console by: ... Starting background file system checks in 60 seconds. Fri Mar 28 08:24:10 PST 2003 FreeBSD/i386 (freebeast.catwhisker.org) (cuaa0) login: [0] f:00 typ:165 s(CHS):0/1/1 e(CHS):4/254/127 s:63 l:4192902 [1] f:00 typ:165 s(CHS):5/0/65 e(CHS):9/254/191 s:4192965 l:4192965 [2] f:00 typ:165 s(CHS):10/0/129 e(CHS):14/254/25Expensive timeout(9) function: 0xc02cf3a0(50xc4025000) 0.067257430 s s:8385930 l:4192965 [3] f:80 typ:165 s(CHS):15/0/193 e(CHS):255/254/255 s:12578895 l:67697910 GEOM: Reconfigure ad0s1, start 32256 length 2146765824 end 2146798079 GEOM: Reconfigure ad0s2, start 2146798080 length 2146798080 end 4293596159 GEOM: Reconfigure ad0s3, start 4293596160 length 2146798080 end 6440394239 GEOM: Reconfigure ad0s4, start 6440394240 length 34661329920 end 41101724159 boot() called on cpu#0 Waiting (max 60 seconds) for system process `vnlru' to stop...stopped s) fong (max 60 second r system process `bufdaemon' to stop... Fatal trap 9: general protection fault while in kernel mode cpuid = 1; lapic.id = 0100 instruction pointer = 0x8:0xd68e2d0a stack pointer = 0x10:0xd68e2ce4 frame pointer = 0x10:0x8 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 11 (idle: cpu1)stopped r' to stop...60 seconds) for system process `synce kernel: type 9 trap, code=0 Stopped at 0xd68e2d0a: mov %si,%ss db tr Fatal trap 12: page fault while in kernel mode cpuid = 1; lapic.id = 0100 fault virtual address = 0xc fault code = supervisor read, page not present instruction pointer = 0x8:0xc0341a00 stack pointer = 0x10:0xd68e29e8 frame pointer = 0x10:0xd68e29ec code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= resume, IOPL = 0 current process = 11 (idle: cpu1) kernel: type 12 trap, code=0 db show pcpu 0 cpuid= 0 curthread= 0xc1505a50: pid 12 idle: cpu0 curpcb = 0xd68e5da0 fpcurthread = none idlethread = 0xc1505a50: pid 12 idle: cpu0 currentldt = 0x28 spin locks held: db show pcpu 1 cpuid= 1 curthread= 0xc1505960: pid 11 idle: cpu1 curpcb = 0xd68e2da0 fpcurthread = none idlethread = 0xc1505960: pid 11 idle: cpu1 currentldt = 0x28 spin locks held: db show locks db I have nothing urgent such that I need to get the machine up running soon, so I can leave it this way for a while. (Note that I had planned to power it off until tonight.) As you can see, the box is SMP (2x886 MHz PIIIs); 512 MB RAM iirc. Very little customization for the kernel beyond tweaking GENERIC for SMP. I'll try to check back here from time to time (have a project in the back yard that will require attention labor). I'm presently building -CURRENT from equivalent sources on my (UP) laptop. Anyway, if anyone thinks of something useful I can do to help figure this out and/or test patches, please let me know. (I do keep a private mirror of the CVS repo here, and testing patches is pretty straightforward for me.) Thanks, david -- David H. Wolfskill [EMAIL PROTECTED] Based on what I have seen to date, the use of Microsoft products is not consistent with reliability. I recommend FreeBSD for reliable systems. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: floppy controller
From: Tecumtah [EMAIL PROTECTED] Subject: floppy controller Date: Wed, 26 Mar 2003 14:13:27 +0100 Message-ID: [EMAIL PROTECTED] Here is the output of dmesg | grep fd fdc0: cmd 3 failed at out byte 1 of 3 fdc0: cmd 3 failed at out byte 1 of 3 fdc0: cannot reserve I/O port range (6 ports) My -CURRENT box(SiS650 chipset) has just same problem. This means that fdc requires IO port 0x3f7,0x3f0-0x3f5 , but some of them is already used by another device. (maybe) This is in my case, according to 'devinfo -r' output, it seems IO port 0x3f0-0x3f1 is used by ACPI related device. acpi_sysresource0 I/O ports: 0x10-0x1f 0x22-0x3f 0x44-0x5f 0x62-0x63 0x65-0x6f 0x72-0x7f 0x80 0x84-0x86 0x88 0x8c-0x8e 0x90-0x9f 0xa2-0xbf 0xe0-0xef 0x290-0x297 0x3f0-0x3f1 === this 0x480-0x48f 0x4d0-0x4d1 0x80c-0x88b 0x88c-0x90b 0xc00-0xc1f ACPI problem ??? Regards, ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: panic: bremfree: removing a buffer not on a queue
On 28 Mar 2003 11:36:04 +, Nick Hilliard wrote My bitty box just crashed out while doing some light desktop work and a small amount of NFS server stuff. FWIW, this problem is repeatable - a few minutes after as I start doing any NFS service, the box crashes out and dies. Any clues on where to start looking? Nick Yes I get the exact same thing. It's intermittant but normally happens during heavy NFS transfer between server and client. The NFS server will freeze and then just reboot as if someones pressed the reset button. No kernel panic or drop into DDB. Both client and server are -CURRENT. I have only ever had it actually give a proper panic/core dump once out of the 10 or so times I've seen this which I sent details of to this list and jeff/kirk who were quite helpful however it still does it :/ Matt. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
ypserv and sshd not getting along in -current
I can not login to a box with FreeBSD 5 -current via ssh because I get the following error from ypserv: Mar 28 12:48:15 node1 ypserv[317]: access to master.passwd.byuid denied -- client 192.168.1.1:49344 not privileged Other than this, the NIS system seems to be working. I tried using the openssh port as well but get the same result so it is definitely a problem with ypserv. This box is an upgrade from FreeBSD 4 -stable and I cloned the setup. In fact I still have the original FreeBSD-4 setup on another box and it all works fine there. Any ideas? I wanted to move to 5.0 on my cluster to take advantage of the improved SMP support but I absolutely need to be able to ssh into this box. Thanks. -- Glenn Johnson USDA, ARS, SRRC Phone: (504) 286-4252 New Orleans, LA 70124 e-mail: [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
where is rdist
I just noticed that rdist is not present on FreeBSD 5-current. Why was it removed? The /etc/periodic/daily/320.rdist file is still present. -- Glenn Johnson USDA, ARS, SRRC Phone: (504) 286-4252 New Orleans, LA 70124 e-mail: [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: where is rdist
On Fri, Mar 28, 2003 at 01:38:30PM -0600, Glenn Johnson wrote: I just noticed that rdist is not present on FreeBSD 5-current. Why was it removed? The /etc/periodic/daily/320.rdist file is still present. I think it was removed due to massive obsolesence. There's a port of it in net/44bsd-rdist. You might also use net/rdist6 if that works in your environment or use rsync instead. -- Brooks -- Any statement of the form X is the one, true Y is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 pgp0.pgp Description: PGP signature ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
No sound in -current?
Hello, I just updated my system last night around 8 PM PST and today I have no sound. XMMS says it's playing music and I can see that it thinks it's playing something, but I am hearing nothing. Same deal with RealPlayer and every other app I try. No crackles, pops or *anything*. Just dead silence. Is this a known issue? Sound was working fine with my previous system from a couple of weeks ago. I'm running: FreeBSD 5.0-CURRENT #0: Thu Mar 27 20:24:08 PST 2003 and 'cat /dev/sndstat' yields: FreeBSD Audio Driver (newpcm) Installed devices: pcm0: VIA VT82C686A at io 0xdc00 irq 5 (1p/1r/0v channels duplex default) Any ideas? Thanks in advance, Scott ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
No sound in -current?
Hello, I just updated my system last night around 8 PM PST and today I have no sound. XMMS says it's playing music and I can see that it thinks it's playing something, but I am hearing nothing. Same deal with RealPlayer and every other app I try. No crackles, pops or *anything*. Just dead silence. Is this a known issue? Sound was working fine with my previous system from a couple of weeks ago. I'm running: FreeBSD 5.0-CURRENT #0: Thu Mar 27 20:24:08 PST 2003 and 'cat /dev/sndstat' yields: FreeBSD Audio Driver (newpcm) Installed devices: pcm0: VIA VT82C686A at io 0xdc00 irq 5 (1p/1r/0v channels duplex default) Any ideas? Thanks in advance, Scott ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
init not loading? why?
I recently purchased a new laptop HDD, tossed three partitions onto the drive (/, /usr, and swap), newfs'ed them with UFS2, mounted the new drive as a umass device, copied files over (tar), and now when I boot with my new drive, the kernel is having problems launching /sbin/init. For the life of me, I can't figure out why it's not loading. After dropping to DDB, I don't see it in the process list and I'm not getting any output other than notice that the kernel is starting /sbin/init. Is there some kind of subtlety I'm missing someplace regarding UFS2? I'm still alive with my old drive, but it's clunking pretty loudly and I don't think it's going to live much longer. :( -sc -- Sean Chittenden ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re:No sound in -current?
Scott R. writes: | I just updated my system last night around 8 PM PST and today I have no | sound. XMMS says it's playing music and I can see that it thinks it's | playing something, but I am hearing nothing. Same deal with RealPlayer | and every other app I try. No crackles, pops or *anything*. Just dead | silence. Is this a known issue? Sound was working fine with my | previous system from a couple of weeks ago. Scott A fix for this was committed this morning (PST). Please let me know if you experience any audio problems after the next update. Thanks - Orion ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: init not loading? why?
I recently purchased a new laptop HDD, tossed three partitions onto the drive (/, /usr, and swap), newfs'ed them with UFS2, mounted the new drive as a umass device, copied files over (tar), and now when I boot with my new drive, the kernel is having problems launching /sbin/init. For the life of me, I can't figure out why it's not loading. After dropping to DDB, I don't see it in the process list and I'm not getting any output other than notice that the kernel is starting /sbin/init. Ah! Figured it out after reading through init's src: /dev didn't exist therefore the machine wouldn't start. No good. I may find a place to stick this got'cha in the docs or add an mkdir() call to init. -sc -- Sean Chittenden ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ports broken due to -current change (Re: Ports broken on ia64)
On Fri, Mar 28, 2003 at 10:28:07AM -0500, Mike Barcroft wrote: Kris Kennaway [EMAIL PROTECTED] writes: On Tue, Mar 18, 2003 at 09:31:48PM -0500, Mike Barcroft wrote: stat.h: $FreeBSD: src/sys/sys/stat.h,v 1.34 2003/03/14 16:09:48 mike Exp $ I think I see the problem. I'll try to get a fix committed by tonight. Still appears to be broken with r1.35: Ugh. The next revision and associated changes fixes it (I actually tested it against osh). OK, I'll update again. Thanks! Kris pgp0.pgp Description: PGP signature ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: init not loading? why?
On Fri, 28 Mar 2003, Sean Chittenden wrote: I recently purchased a new laptop HDD, tossed three partitions onto the drive (/, /usr, and swap), newfs'ed them with UFS2, mounted the new drive as a umass device, copied files over (tar), and now when I boot with my new drive, the kernel is having problems launching /sbin/init. For the life of me, I can't figure out why it's not loading. After dropping to DDB, I don't see it in the process list and I'm not getting any output other than notice that the kernel is starting /sbin/init. Ah! Figured it out after reading through init's src: /dev didn't exist therefore the machine wouldn't start. No good. I may find a place to stick this got'cha in the docs or add an mkdir() call to init. -sc mkdir(2) on / is not going to work if / is readonly. The kernel actually tries to do a vop_mkdir() already, I think. The eventual solution is probably a rootfs (blaim mux). Robert N M Watson FreeBSD Core Team, TrustedBSD Projects [EMAIL PROTECTED] Network Associates Laboratories ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: init not loading? why?
On Fri, 28 Mar 2003, Sean Chittenden wrote: Ah! Figured it out after reading through init's src: /dev didn't exist therefore the machine wouldn't start. No good. I may find a place to stick this got'cha in the docs or add an mkdir() call to init. mkdir(2) on / is not going to work if / is readonly. The kernel actually tries to do a vop_mkdir() already, I think. The eventual solution is probably a rootfs (blaim mux). Well, I haven't tested this, but I think you're right that it's nmount() that's failing and the lack of a check on it's return value. I haven't tested this beyond compiling it, but I suspect it'll work and fix this corner case. -sc Per our out-of-band conversation, it looks like this won't work because of a lack of /dev. It seems like the most reasonable solution is to generate a kernel warning message if the kernel-side devfs mount attempt fails. If we cause init to fail, the kernel will panic, and I can't quite decide if (a) the system hanging, or (b) the kernel panicking is a better answer. :-) Robert N M Watson FreeBSD Core Team, TrustedBSD Projects [EMAIL PROTECTED] Network Associates Laboratories ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: AC97 sound problems with current
More information on my AC97 experiences: I forced the card to 4.8 KHz which is what it was running at on V4. This seems to have not helped the performance of GnomeMeeting at all. The sound I hear is in spurts which are at the correct frequency and last about a tenth of a second. with gaps between them of about 1 second. Also, even though I have the mic muted under GnomeMeeting and no sound is actually sent out, I can hear everything I say with no delay (and perfect clarity). I suspect that this is a part of the problem. Even turning down the microphone volume does nothing. It is, instead, tied to the Record input. I also tested sending audio today and it was also in similar spurts. All of this was working perfectly with v4, so it's something that has changed between versions. This appears to be tied to duplex operation as players (mplayer, xmms) work just fine. Any clues? FreeBSD CURRENT (3/27/2003) in IBM ThinkPad T30 with ICH3 audio. GnomeMeeting 0.96.0. R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Unclean sync in current
Date: Fri, 28 Mar 2003 16:18:59 -0800 From: David Schultz [EMAIL PROTECTED] Thus spake Kevin Oberman [EMAIL PROTECTED]: I've been seeing this for a couple of weeks since I updated my laptop to CURRENT. I do a normal shutdown (-p or -r) and reboot. The shutdown looked normal, with no problems reported with the sync, but, when the system is rebooted, the partitions are all shown as possibly unclean. From my dmesg: Mounting root from ufs:/dev/ad0s3a WARNING: / was not properly dismounted WARNING: / was not properly dismounted WARNING: /tmp was not properly dismounted WARNING: /usr was not properly dismounted WARNING: /var was not properly dismounted All disks are mounted with soft-updates enabled. I don't see any other reports of this. Is this unique to my system? Unlike the SCSI driver, the ATA driver does not send a flush cache command to your disks before powering off the system. The kernel waits for five seconds in either case, but for some disks that may not be sufficient. The following patch should fix that, although it may have rotted a bit in the last two months given Soeren's sweeping ATA changes. I also edited an unrelated change out of the diff, which might confuse patch(1). If you run into problems getting it to apply, let me know and I'll fix it when I'm back from vacation. Thanks, but the issue was not a write cache problem. It was the change in the UFS1 super-block in V5. After I performed an fsck_ffs on each partition, the errors vanished. All appears to be running fine. R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Fatal trap 9: general protection fault while in kernel mode
Date: Fri, 28 Mar 2003 18:34:31 -0800 (PST) From: David Wolfskill [EMAIL PROTECTED] Date: Fri, 28 Mar 2003 08:46:39 -0800 (PST) From: David Wolfskill [EMAIL PROTECTED] [Yes, I'm responding to my own post] Again. Well, I tried panic, and that just got me Fatal trap 3: breakpoint instruction fault while in kernel mode so I said reset; after it came up, I re-did the same sequence -- logged in via SSH, poked around (OK; ran healthd -d and watched for at least a couple of different values to change), then issued sudo boot0cfg -s 1 ad0 sudo halt -p || sudo reboot (same as before), and got: Local package initialization: apache cvsupd . Additional TCP options:. Fri Mar 28 19:05:16 PST 2003 FreeBSD/i386 (freebeast.catwhisker.org) (console) login: Mar 28 19:10:03 freebeast halt: halted by david Mar 28 19:10:03 freebeast syslogd: exiting on signal 15 boot() called on cpu#1 Waiting (max 60 seconds) for system process `vnlru' to stop...stopped Waiting (max 60 seconds) for system process `bufdaemon' to stop...stopped Waiting (max 60 seconds) for system process `syncer' to stop...stopped syncing disks... 2 done Uptime: 9m7s [followed by a click and a cessation of 4 fans blowing]. So about the only thing I see that this last experiment demonstrates is that SMP vs. UP isn't known to be a significant issue for whatever was causing the problem. Tomorrow, I expect to be trying to build -CURRENT while running today's; that could prove interesting. Peace, david (links to my resume at http://www.catwhisker.org/~david) -- David H. Wolfskill [EMAIL PROTECTED] Based on what I have seen to date, the use of Microsoft products is not consistent with reliability. I recommend FreeBSD for reliable systems. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [Re: several background fsck panics
David Schultz wrote: Thus spake Terry Lambert [EMAIL PROTECTED]: o Put a counter in the first superblock; it would be incremented when the BG fsck is started, and reset to zero when it completes. If the counter reaches 3 (or some command line specified number), then the BG flagging is ignored, and a full FG fsck is then performed instead. I like this idea because it will always work, and it's not actually a hack, it's a correct solution. I'm glad you like it because AFAIK, it is already implemented. ;-) Nope. What's implemented is the FS_NEEDSFSCK flag. But that flag is not set in the superblock flags field as *the very first thing done*. Thus a failure that results in a panic will not set the flag in pfatal(), since it never gets there. Probably the correct thing to do is to set the flag as the very first operation, and then it will work as expected. FWIW, it looks like the code in pfatal() wanted to be in main(), since it complains about not being able to run in the background, the same way main() does. However, this still leaves a race window. The reason the panic happens is that FreeBSD is running processes on a corrupt FS. Even in the best case, this panic may occur when anything is loaded off the FS, so it could happen on init, or on fsck itself, etc.. So really, the only solution is a counter that the FS kernel code counts up, which is reset to zero when a BG fsck completes successfully. Say grabbing the first byte of fs_sparecon32[]. BTW: This still leaves a failure case: the BG fsck has to be able to complete successfully... but that's not enough to stave off a future panic from an undetected error that the fsck didn't see, because it was only pruning CG bitmaps. So the correct place to zero the counter is, once again, in the kernel. As a result of a successful unmount, from a non-panic shutdown. This does mean that three (or count) consecutive power failures gets you a FG fsck, but that's probably livable (if you were that certain there was no corruption, you could boot to a shell and override the count parameter to the FG fsck trigger threshold). o Implement soft read-only. The place that most of the complaints are coming from is desktop users, with relatively quiescent machines. Though swap is used, it does not occur in an FS partition. As a result, the FS could be marked read-only for long period of time. This marking would be in memory. The clean bit would be set on the superblock. When a write occurs, the clean bit would be reset to dirty, and committed to disk prior to the write operation being permitted to proceed (a stall barrier). I like this idea because, for the most part, it eliminates fsck, both BG and FG, on systems that crash while it's in effect. The net result is a system that is statistically much more tolerant of failures, but which still requires another safety net, such as the previous solution. I was thinking of doing something like this myself as part of an ``idle timeout'' for disks. (Marking the filesystem clean after a period of quiescence would actually interfere with ATA disks' built-in mechanism for spinning down after a timeout, which is important for laptops, so the OS would have to track the true amount of idle time.) Annoyingly, I can never get the disk containing /var to remain quiescent for long while cron is running (even without any crontabs), and I hope this can be solved without disabling cron or adding a nontrivial hack to bio. We implemented this when we implemented soft updates in FFS under Windows at Artisoft. That was back before ATX power supplies were wide spread, and we needed to be tolerant of users who simply turned off the power switch, without running the Windows95 shutdown sequence. I dunno about cron. I think it noticing crontab changes automatically has maybe made it too smart for its own good. Cron updates the access time on the crontab file every time it runs, which is once a second. If you disabled this for fstat, the problem would go away. I'm not sure the semantics are OK, though. The old pre-smarter cron would not have this problem, as it would run on intervals, and sleep for long periods (until the next job was scheduled to run), and you had to hit it over the head with kill -HUP to tell it the file changed. Probably the correct thing to do is to use old-style long delta intervals, and register a kevent interest in file modifications. The cruddy thing is, if it were really read-only, then the access time update wouldn't happen. Catch-22. I think maybe it's useful to distinguish the POSIX semantics here: shall be scheduled for update is not the same thing, really, as shall be updated. So, in practice, you could cache the access time update for long periods, as long as the correct time was marked in
Re: optimization/10189: pentium4 breaks suns libm code for__ieee754_pow(double x, double y)
On Wed, Mar 26, 2003 at 10:09:34PM +0100, Alexander Leidinger wrote: And trust me, as long as gcc ships with a description of other optimizations beneath -O there will be (clueless or smart... does it really matter here?) people which will try those optimizations on everything Not to mention bullshit ones like -O9. I see that all the time. What do these poeple think they are buying with that? GCC should stop accepting -O values higher than what does anything. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
