'Fatal trap 12: page fault' with GENERIC, i386
Hi, I have a problem with the 5.0 GENERIC kernel from the miniinstall ISO image. Please note: I'm not subscribed to this list, so please reply to me. Download time was Jan. 20 from ftp://ftp7.de.FreeBSD.org/pub/FreeBSD/ For installation I used the GENERIC kernel from the CD, MD5 (boot/kernel/kernel) = 0441abf2a9970e24cbd856cf89fa32a1 During the boot process the system hangs and with 'boot -v' I get the following page-fault (I was only able to include the last lines of the boot process.): --- Begin of page fault message --- ata1-slave: ATA 04 00 ata1: devices=04 ata1: at 0x170 irq 15 on atapci0 uhci0: port 0-0x1f at device 1.2 on pci0 pci_cfgintr_virgin: using routable interrupt 3 Fatal trap 12: page fault while in kernel mode fault virtual address = 0xeb7bb fault code = supervisor read, page not present instruction pointer = 0x8:0xc00eb6bc stack pointer = 0x10:0xc0a8299c frame pointer = 0x10:0xc0a8299c 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 = 0 (swapper) trap number = 12 panic: page fault Uptime: 1s --- End of page fault message --- Here is also the dmesg.boot from 4.7-STABLE currently running on the machine, so that you can see the devices on the laptop. --- Begin of dmesg.boot from 4.7-STABLE --- Copyright (c) 1992-2002 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 4.7-STABLE #2: Mon Nov 4 20:06:27 CET 2002 [EMAIL PROTECTED]:/usr/src/sys/compile/LAPTOP Timecounter i8254 frequency 1193182 Hz CPU: AMD-K6(tm) 3D processor (299.76-MHz 586-class CPU) Origin = AuthenticAMD Id = 0x58c Stepping = 12 Features=0x8021bf AMD Features=0x8800 real memory = 33554432 (32768K bytes) avail memory = 29073408 (28392K bytes) Preloaded elf kernel kernel at 0xc03aa000. K6-family MTRR support enabled (2 registers) md0: Malloc disk Using $PIR table, 2 entries at 0xc00fe840 apm0: on motherboard apm0: found APM BIOS v1.2, connected at v1.2 npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 isab0: at device 1.0 on pci0 isa0: on isab0 atapci0: port 0x1100-0x110f at device 1.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: irq 0 at device 1.2 on pci0 uhci0: Could not map ports device_probe_and_attach: uhci0 attach returned 6 chip1: port 0x1400-0x140f at device 1.3 on pci0 pci0: at 2.0 pcic0: irq 10 at device 3.0 on pci0 pcic0: PCI Memory allocated: 0x8800 pcic0: TI12XX PCI Config Reg: [speaker enable][pwr save][CSC serial isa irq] pccard0: on pcic0 pcic1: irq 10 at device 3.1 on pci0 pcic1: PCI Memory allocated: 0x88001000 pcic1: TI12XX PCI Config Reg: [speaker enable][pwr save][CSC serial isa irq] pccard1: on pcic1 orm0: at iomem 0xc-0xc9fff,0xf1000-0xf1fff on isa0 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: on fdc0 drive 0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sc0: at flags 0x100 on isa0 sc0: VGA 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 ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode lpt0: on ppbus0 lpt0: Interrupt-driven port sbc1: at port 0x220-0x22f,0x388-0x38b,0x330-0x331 irq 5 drq 1,0 on isa0 pcm0: on sbc1 RTC BIOS diagnostic error 20 ad0: 2067MB [4200/16/63] at ata0-master UDMA33 acd0: CDROM at ata1-master PIO4 Mounting root from ufs:/dev/ad0s1a --- End of dmesg.boot from 4.7-STABLE --- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
I've just had a massive file system crash
I'm rather astounded. I'm currently at a Linux conference, and have of course been boasting about the stability of ufs, and today I had a crash which tore apart my /home file system. This is on a laptop, one which has been running -CURRENT for years with no trouble. At the moment it's running 5.0-RELEASE. Today I shut it down cleanly, and a couple of hours later rebooted it. It has three file systems, one of which came up dirty. fsck -y reported thousands of errors, and when it was finished, my home directory and some other files were gone, and all the subdirectories of my home directory were in lost+found, a total of 1.4 GB. Most of the errors appear to be duplicate Inode numbers. Obviously it's too late to work out what happened, but I thought it's worth mentioning in case somebody else is having the same trouble. Greg -- See complete headers for address and phone numbers To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: kernel panic with today's CURRENT on sparc64 at boot
On Wed, Jan 22, 2003 at 08:59:51PM +0100, Thomas Moestl wrote: On Tue, 2003/01/21 at 17:33:42 +, [EMAIL PROTECTED] wrote: Hi cvsup'd to . today on an E220R, single CPU with two Symbios scsi cards. Box had been running fine with RC3, but would not boot with -CURRENT kernel: Current: hme4: Ethernet address: 08:00:20:b7:ef:44 miibus4: MII bus on hme4 ukphy3: Generic IEEE 802.3u media interface on miibus4 ukphy3: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto sym0: 875 port 0x1000-0x10ff mem 0x1090a000-0x1090afff,0x10908000-0x109080ff i rq 32 at device 3.0 on pci0 panic: trap: fast data access mmu miss cpuid = 0; Debugger(panic) Stopped at Debugger+0x1c: ta %xcc, 1 Can you please cvsup again to pick up some changes that were made yesterday and try again? Hi there Well, after a panic last night in IPFW on -RELEASE, I decided to try -CURRENT again. I just CVSUP'd, built kernel and rebooted. Here's what happened: FreeBSD/sparc64 bootstrap loader, Revision 1.0 ([EMAIL PROTECTED], Wed Jan 22 11:31:27 GMT 2003) bootpath=/pci@1f,4000/scsi@3/disk@0,0:a Loading /boot/defaults/loader.conf /boot/kernel/kernel data=0x2cc308+0xe4178 syms=[0x8+0x44310+0x8+0x34e6f] Hit [Enter] to boot immediately, or any other key for command prompt. Booting [/boot/kernel/kernel]... nothing to autoload yet. jumping to kernel entry at 0xc0038000. stray vector interrupt 2029 Copyright (c) 1992-2003 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #7: Fri Jan 24 10:36:24 GMT 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/NS Preloaded elf kernel /boot/kernel/kernel at 0xc042c000. Timecounter tick frequency 450026203 Hz cpu0: Sun Microsystems UltraSparc-II Processor (450.03 MHz CPU) Model: SUNW,Ultra-60 Initializing GEOMetry subsystem nexus0: OpenFirmware Nexus device pcib0: U2P UPA-PCI bridge on nexus0 pcib0: Psycho, impl 0, version 4, ign 0x7c0 initialializing counter-timer Timecounter counter-timer frequency 100 Hz DVMA map: 0xfe00 to 0x device 0/1/0: latency timer 0 - 82 pcib0: ofw_pci_init: no interrupt mapping found for 0/1/0 (preset 128) device 0/1/1: latency timer 0 - 82 pcib0: ofw_pci_init: mapping intr for 0/1/1 to 33 (preset was 0) device 0/3/0: latency timer 0 - 140 pcib0: ofw_pci_init: mapping intr for 0/3/0 to 32 (preset was 0) device 0/3/1: latency timer 0 - 140 pcib0: ofw_pci_init: mapping intr for 0/3/1 to 38 (preset was 0) PCI-PCI bridge at 0/2/0: setting bus #s to 0/1/1 pcib0: ofw_pci_init: descending to subordinate PCI bus device 1/0/0: latency timer 0 - 82 pcib0: ofw_pci_init: mapping intr for 1/0/0 to 16 (preset was 0) device 1/0/1: latency timer 0 - 82 pcib0: ofw_pci_init: mapping intr for 1/0/1 to 17 (preset was 0) device 1/1/0: latency timer 0 - 82 pcib0: ofw_pci_init: mapping intr for 1/1/0 to 17 (preset was 0) device 1/1/1: latency timer 0 - 82 pcib0: ofw_pci_init: mapping intr for 1/1/1 to 18 (preset was 0) device 1/2/0: latency timer 0 - 82 pcib0: ofw_pci_init: mapping intr for 1/2/0 to 18 (preset was 0) device 1/2/1: latency timer 0 - 82 pcib0: ofw_pci_init: mapping intr for 1/2/1 to 19 (preset was 0) device 1/3/0: latency timer 0 - 82 pcib0: ofw_pci_init: mapping intr for 1/3/0 to 19 (preset was 0) device 1/3/1: latency timer 0 - 82 pcib0: ofw_pci_init: mapping intr for 1/3/1 to 16 (preset was 0) PCI-PCI bridge at 0/4/0: setting bus #s to 0/2/2 pcib0: ofw_pci_init: descending to subordinate PCI bus device 2/0/0: latency timer 0 - 82 pcib0: ofw_pci_init: mapping intr for 2/0/0 to 24 (preset was 0) device 2/0/1: latency timer 0 - 82 pcib0: ofw_pci_init: mapping intr for 2/0/1 to 25 (preset was 0) device 2/1/0: latency timer 0 - 82 pcib0: ofw_pci_init: mapping intr for 2/1/0 to 25 (preset was 0) device 2/1/1: latency timer 0 - 82 pcib0: ofw_pci_init: mapping intr for 2/1/1 to 26 (preset was 0) device 2/2/0: latency timer 0 - 82 pcib0: ofw_pci_init: mapping intr for 2/2/0 to 26 (preset was 0) device 2/2/1: latency timer 0 - 82 pcib0: ofw_pci_init:
Re: I've just had a massive file system crash
Greg Lehey [EMAIL PROTECTED] wrote: It has three file systems, one of which came up dirty. fsck -y reported thousands of errors, and when it was finished, my home directory and some other files were gone, and all the subdirectories of my home directory were in lost+found, a total of 1.4 GB. Most of the errors appear to be duplicate Inode numbers. Don't be too hasty to blame UFS. Everytime this has happened to me (even on Linux) it has been because the disk drive was failing. It has happened to me *many* times with IDE drives. I wind up replacing about 1/4 of them every year, on average. But, I did go through a run of those bad IBM drives :-) Did you happen to drop the laptop? :-) - Dave Rivers - -- [EMAIL PROTECTED]Work: (919) 676-0847 Get your mainframe programming tools at http://www.dignus.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Performance problems with 5.0-RELEASE
If you lean on the keyboard, or if you set up the network adapters as entropy sources, does the problem fix itself? If you're thinking it's /dev/random blocking on him, 5.0's output never blocks. Its output is a PRNG periodically seeded from random data, including interrupt timings and LAN traffic by default. Mostly, I was thinking that the other suggestions (WITNESS, INVARIANTS, malloc flags) didn't really have any chance of being the cause of the lock-ups, and without some message on the console, it's unlikely that it was a driver tiemout, either. No messages on console. If it's long enough to pause the console noticibly, the next thing to try is breaking to the debugger -- which might require an NMI card -- to see what code it's stuck in during the pause. It's noticeable - if you type under heavy load in console, you experience similar to ssh lag - you can't see what you type, but it appears a second later to the screen. I've spoken about this issue on IRC for a few times, and ran into a guy who said he was experiencing similar problems on 5.0-REL. Just to let you know. I've tried adding HR to malloc.conf and removing ALL unneccessary options from the kernel, no help. Atte Peltomäki http://kameli.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
(kein Betreff)
subscribe freebsd-current subscribe cvs-all To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
No man page for /etc/malloc.conf ?
Where can I find the definitions for the AJ, aj, HR, etc. that are being discussed in the 'performance' thread? Thanks. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: No man page for /etc/malloc.conf ?
Hello, Where can I find the definitions for the AJ, aj, HR, etc. that are being discussed in the 'performance' thread? In malloc(3): http://www.freebsd.org/cgi/man.cgi?query=mallocapropos=0sektion=0manpath=FreeBSD+5.0-currentformat=html man malloc --[ Free Software ISOs - http://www.fsn.hu/?f=download ]-- Attila Nagy e-mail: [EMAIL PROTECTED] Free Software Network (FSN.HU)phone @work: +361 210 1415 (194) cell.: +3630 306 6758 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
firewire hangs on Thinkpad
Hi all, I'm having a bad time trying to get a firewire cardbus adapter to work. First of all, let me say that I'm under no pressure - I just bought it to test our firewire implementation but I have no pressing need for it. Anyway, new kernel from last night, when I insert the card I get the following: cardbus0: Expecting link target, got 0x42 cardbus0: Resource not specified in CIS: id=10, size=800 cardbus0: Resource not specified in CIS: id=14, size=4000 cardbus0: Resource not specified in CIS: id=18, size=800 fwohci0: Texas Instruments TSB43AB22/A mem 0x880 08000-0x880087ff,0x88004000-0x88007fff,0x88008800-0x88008fff irq 11 at device 0.0 on cardbus0 fwohci0: PCI bus latency was changing to 250. fwohci0: OHCI version 1.10 (ROM=1) fwohci0: No. of Isochronous channel is 4. fwohci0: EUI64 00:01:fb:00:00:00:00:6e fwohci0: Phy 1394a available S400, 2 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: IEEE1394(FireWire) bus on fwohci0 fwohci0: BUS reset fwohci0: BUS reset fwohci0: node_id = 0xc000ffc0, CYCLEMASTER mode firewire0: 1 nodes, maxhop = 0, cable IRM = 0 (me) Sometimes it hangs the machine solid to the point I can't enter DDB, other times it takes a few seconds during which the machine is responsive, other times DDB is usable. I wasn't able to determine any rule to explain the different behaviors, but if anybody has any idea, I can try go get to DDB again and get any required info. Bye, Andrea -- Where do you think you're going today? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: I've just had a massive file system crash
Next time you run fsck -y in this scenario, log the output to an md partition and stick it somewhere for analysis. At least, that was the moral of the story last time I hosed a box in this form (incidentally, I think it ended up being a failing hard disk). Robert N M Watson FreeBSD Core Team, TrustedBSD Projects [EMAIL PROTECTED] Network Associates Laboratories On Fri, 24 Jan 2003, Greg Lehey wrote: I'm rather astounded. I'm currently at a Linux conference, and have of course been boasting about the stability of ufs, and today I had a crash which tore apart my /home file system. This is on a laptop, one which has been running -CURRENT for years with no trouble. At the moment it's running 5.0-RELEASE. Today I shut it down cleanly, and a couple of hours later rebooted it. It has three file systems, one of which came up dirty. fsck -y reported thousands of errors, and when it was finished, my home directory and some other files were gone, and all the subdirectories of my home directory were in lost+found, a total of 1.4 GB. Most of the errors appear to be duplicate Inode numbers. Obviously it's too late to work out what happened, but I thought it's worth mentioning in case somebody else is having the same trouble. Greg -- See complete headers for address and phone numbers To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: kernel panic with today's CURRENT on sparc64 at boot
On Fri, 2003/01/24 at 11:54:41 +, Steven Haywood wrote:
hme6: Sun HME 10/100 Ethernet mem 0xc80-0xc807fff irq
26 at device 1.1 on
pci2
hme6: DMA buffer map load error 12
hme6: could not be configured
device_probe_and_attach: hme6 attach returned 6
pci2: bridge, PCI-unknown at device 2.0 (no driver
attached)
hme6: Sun HME 10/100 Ethernet mem 0xe80-0xe807fff irq
27 at device 2.1 on
pci2
hme6: DMA buffer map load error 12
hme6: could not be configured
device_probe_and_attach: hme6 attach returned 6
pci2: bridge, PCI-unknown at device 3.0 (no driver
attached)
pci2: bridge, PCI-unknown at device 3.0 (no driver
attached)
n pci2
hme6: DMA buffer map load error 12
hme6: could not be configured
device_probe_and_attach: hme6 attach returned 6
pci0: display at device 5.0 (no driver attached)
pcib3: U2P UPA-PCI bridge on nexus0
pcib3: Psycho, impl 0, version 4, ign 0x7c0
pci3: PCI bus on pcib3
Timecounters tick every 10.000 msec
ipfw2 initialized, divert disabled, rule-based forwarding
enabled, default to de
ny, logging limited to 100 packets/entry by default
Waiting 5 seconds for SCSI devices to settle
da0 at sym0 bus 0 target 1 lun 0
da0: FUJITSU MAG3091L SUN9.0G Fixed Direct Access
SCSI-2 device
da0: 40.000MB/s transfers (20.000MHz, offset 16, 16bit),
Tagged Queueing Enabled
da0: 8637MB (17689267 512 byte sectors: 255H 63S/T 1101C)
Mounting root from ufs:/dev/da0a
exec /sbin/init: error 8
init: not found in path
/sbin/init:/sbin/oinit:/sbin/init.bak:/stand/sysinstall
panic: no init
cpuid = 0;
Debugger(panic)
Stopped at Debugger+0x1c: ta %xcc, 1
This is probably easy to work around for you by increasing the amount
of available DVMA:
--
diff -u -r1.26 psycho.c
--- sparc64/pci/psycho.c21 Jan 2003 08:56:14 - 1.26
+++ sparc64/pci/psycho.c24 Jan 2003 16:05:00 -
@@ -565,7 +565,7 @@
sc-sc_is-is_sb[1] = 0;
if (OF_getproplen(sc-sc_node, no-streaming-cache) 0)
sc-sc_is-is_sb[0] = sc-sc_pcictl + PCR_STRBUF;
- psycho_iommu_init(sc, 2);
+ psycho_iommu_init(sc, 3);
} else {
/* Just copy IOMMU state, config tag and address */
sc-sc_is = osc-sc_is;
--
If that still doesn't help, you can further increase the constant to 4
or 5 (at the expense of another 64kB or 192kB of memory).
- Thomas
--
Thomas Moestl [EMAIL PROTECTED] http://www.tu-bs.de/~y0015675/
[EMAIL PROTECTED] http://people.FreeBSD.org/~tmm/
PGP fingerprint: 1C97 A604 2BD0 E492 51D0 9C0F 1FE6 4F1D 419C 776C
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
lib/libdisk compile failure during 'make world'
Greetings, Running -CURRENT, I cvsupped today... and afterwards ran 'world' which bailed out here: cc1: warnings being treated as errors /usr/src/lib/libdisk/rules.c: In function `Check_Chunk': /usr/src/lib/libdisk/rules.c:265: warning: enumeration value `p_any' not handled in switch /usr/src/lib/libdisk/rules.c:265: warning: enumeration value `p_alpha' not handled in switch /usr/src/lib/libdisk/rules.c:265: warning: enumeration value `p_sparc64' not handled in switch /usr/src/lib/libdisk/rules.c:265: warning: enumeration value `p_ia64' not handled in switch /usr/src/lib/libdisk/rules.c:265: warning: enumeration value `p_ppc' not handled in switch Please cc: me on replies, I am not subscribed. Cheers, Dylan Carlson [[EMAIL PROTECTED]] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: kernel panic with today's CURRENT on sparc64 at boot
On Fri, Jan 24, 2003 at 05:10:07PM +0100, Thomas Moestl wrote:
This is probably easy to work around for you by increasing the amount
of available DVMA:
--
diff -u -r1.26 psycho.c
--- sparc64/pci/psycho.c 21 Jan 2003 08:56:14 - 1.26
+++ sparc64/pci/psycho.c 24 Jan 2003 16:05:00 -
@@ -565,7 +565,7 @@
sc-sc_is-is_sb[1] = 0;
if (OF_getproplen(sc-sc_node, no-streaming-cache) 0)
sc-sc_is-is_sb[0] = sc-sc_pcictl + PCR_STRBUF;
- psycho_iommu_init(sc, 2);
+ psycho_iommu_init(sc, 3);
} else {
/* Just copy IOMMU state, config tag and address */
sc-sc_is = osc-sc_is;
--
If that still doesn't help, you can further increase the constant to 4
or 5 (at the expense of another 64kB or 192kB of memory).
I upped it to 4, recompiled and it works! Thanks :)
Steven
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
RE: I've just had a massive file system crash
three file systems, one of which came up dirty. fsck -y reported thousands of errors, and when it was finished, my home directory and some other files were gone, and all the subdirectories of my home This may (or may not) have anything to do with it, but I had a problem with a couple of filesystem back in September that had the error: (Running on RELENG_4 that was very recent at the time) CG 22: BAD MAGIC NUMBER fsck -y gave thousands of errors (similar to what you had) and when it was done, nothing was on the filesystem. (I didn't think to check lost+found at the time, just restored the filesystem, so the files may have been placed in there) During the space of 2 days, I had a total of 3 of these on two different systems. Forcing a mount (without cleaning) on the other two showed a perfect filesystem (which I backed up, newfs'd and restored). I even compared one of these with a backup and there wasn't a single thing different. It sort of baffled me at the time, since one of those filesystems didn't have any writing (other than atime perhaps) and still had the error. I haven't had a problem since then, and I know there are quite a bit of changes between 4 and 5, but it really does sound similar. At least the fsck part sounds almost exactly the same. Jaime bozza To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: calcru: negative time ... messages in 5.0-RELEASE
On Thu, 23 Jan 2003, Bill Moran wrote: Nate Lawson wrote: See thread just above your post, titled Re: Time keeping problems with 5.0-RELEASE Thanks for the reply, Nate. I've searched the -CURRENT mailing list archives for a number of combinations of the title you describe and haven't found anything. Any suggestions? Archives aren't updated more often than weekly. http://docs.freebsd.org/mail/current/freebsd-current.html -Nate To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: acpi problem ???
On Thu, 23 Jan 2003, Bryan Liesner wrote: On Thu, 23 Jan 2003, Nate Lawson wrote: On Thu, 23 Jan 2003, Bryan Liesner wrote: I just upgraded my 4.7 system to 5.0-current via sources. Everything went smoothly, and I was up and running quickly, but with an acpi related problem. When booting, the kernel loads, detects the devices, then hangs right here: Mounting root from ufs:/dev/ad0s1a pid 84 (fsck_ufs), uid 0: exited on signal 8 No panic, just a hang. One thing you have wrong is that you have both acpi and apm enabled. Nix apm and try again. Also, try without the usb drive plugged in. I took out the apm and the usb drive, same issue. Thanks... Boot single user, run fsck manually on each partition, then go multiuser. -Nate To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Performance problems with 5.0-RELEASE
On Thu, 23 Jan 2003, Terry Lambert wrote: Atte Peltomaki wrote: Description: Every time machine is under heavy load (CPU, network, disks) it completely jamms for fraction of a second for every ten seconds or so, everything just stops and then continues. I noticed this while compiling software and copying files over NFS while listening to MP3's, later realized it wasn't just MP3's that lagged, but the whole machine, including console and everything. If you lean on the keyboard, or if you set up the network adapters as entropy sources, does the problem fix itself? This can't be it since /dev/random is non-blocking in 5.x -Nate To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
GEOM disklabel
Hi, trying to disklabel new disks I get: (nihil)(root) # disklabel -w -B da0s1 auto (nihil)(root) # disklabel -r da0s1 # /dev/da0s1c: type: unknown disk: amnesiac label: flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 24792 sectors/unit: 398297025 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds drivedata: 0 8 partitions: #size offsetfstype [fsize bsize bps/cpg] c: 398297025 63unused0 0# (Cyl.0*- 24792*) partition c: partition extends past end of unit Warning, partition c doesn't start at 0! Warning, An incorrect partition c may cause problems for standard system utilities (nihil)(root) # disklabel -e da0s1 # /dev/da0s1c: type: unknown disk: amnesiac label: flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 24792 sectors/unit: 398297025 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds drivedata: 0 8 partitions: #size offsetfstype [fsize bsize bps/cpg] c: 3982970250unused0 0# (Cyl.0 - 24792*) Why? sysctl -b kern.geom.confxml is attached Bye! Michael Reifenberger ^.*Plaut.*$, IT, R/3 Basis, GPS mesh class id=0xc02e8bc0 nameDEV/name geom id=0xc2f9e980 class ref=0xc02e8bc0/ namemd10c/name rank3/rank consumer id=0xc2f9c580 geom ref=0xc2f9e980/ provider ref=0xc2f9e800/ moder1w1e0/mode /consumer /geom geom id=0xc2f9db80 class ref=0xc02e8bc0/ namemd10/name rank2/rank consumer id=0xc2f9c9c0 geom ref=0xc2f9db80/ provider ref=0xc2f9ee80/ moder0w0e0/mode /consumer /geom geom id=0xc2de3100 class ref=0xc02e8bc0/ nameda1s1c/name rank4/rank consumer id=0xc2de86c0 geom ref=0xc2de3100/ provider ref=0xc2de3300/ moder0w0e0/mode /consumer /geom geom id=0xc2cab600 class ref=0xc02e8bc0/ nameda0s1c/name rank4/rank consumer id=0xc2de8800 geom ref=0xc2cab600/ provider ref=0xc2de2100/ moder0w0e0/mode /consumer /geom geom id=0xc2dd6f00 class ref=0xc02e8bc0/ nameda1s1/name rank3/rank consumer id=0xc2de8a00 geom ref=0xc2dd6f00/ provider ref=0xc2dd6400/ moder0w0e0/mode /consumer /geom geom id=0xc2de3080 class ref=0xc02e8bc0/ nameda0s1/name rank3/rank consumer id=0xc2de8c00 geom ref=0xc2de3080/ provider ref=0xc2de2d80/ moder0w0e0/mode /consumer /geom geom id=0xc2cab380 class ref=0xc02e8bc0/ nameda1/name rank2/rank consumer id=0xc2de8d80 geom ref=0xc2cab380/ provider ref=0xc2cab480/ moder0w0e0/mode /consumer /geom geom id=0xc2de2a00 class ref=0xc02e8bc0/ nameda0/name rank2/rank consumer id=0xc2bb2b40 geom ref=0xc2de2a00/ provider ref=0xc2de2900/ moder0w0e0/mode /consumer /geom geom id=0xc2de3480 class ref=0xc02e8bc0/ namead1s3/name rank3/rank consumer id=0xc2bb22c0 geom ref=0xc2de3480/ provider ref=0xc2cacb00/ moder0w0e0/mode /consumer /geom geom id=0xc2cac980 class ref=0xc02e8bc0/ namead1s2/name rank3/rank consumer id=0xc2bb2200 geom ref=0xc2cac980/ provider ref=0xc2cacb80/ moder0w0e0/mode /consumer /geom geom id=0xc2dd6b00 class ref=0xc02e8bc0/ namead1s1/name rank3/rank consumer id=0xc2bb2400 geom ref=0xc2dd6b00/ provider ref=0xc2cacc00/ moder0w0e0/mode /consumer /geom geom id=0xc2dd6700 class ref=0xc02e8bc0/ namead0s3d/name rank4/rank consumer id=0xc2bc72c0 geom ref=0xc2dd6700/ provider ref=0xc2cace00/ moder1w1e0/mode /consumer /geom geom id=0xc2dd6300 class ref=0xc02e8bc0/ namead0s3c/name rank4/rank consumer id=0xc2bb2ac0 geom ref=0xc2dd6300/ provider ref=0xc2cace80/ moder0w0e0/mode /consumer /geom geom id=0xc2cac880 class ref=0xc02e8bc0/ namead0s3b/name rank4/rank consumer id=0xc2bb2740 geom ref=0xc2cac880/ provider ref=0xc2cacf00/ moder1w1e0/mode /consumer /geom geom id=0xc2caca00 class ref=0xc02e8bc0/
Re: GEOM disklabel
In message [EMAIL PROTECTED], Michael Reifenberger w rites: This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to [EMAIL PROTECTED] for more info. --0-240786022-1043432225=:647 Content-Type: TEXT/PLAIN; charset=US-ASCII Hi, trying to disklabel new disks I get: (nihil)(root) # disklabel -w -B da0s1 auto (nihil)(root) # disklabel -r da0s1 Don't use the '-r' option, it gets confused because geom::BSD does not lie to it. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: new wi driver
: dstumbler breaks; on startup it reports : unable to ioctl device socket: Input/output error. As root or no? I have a rebuilt system finally that I could test this against and I'm actually getting a different error message on startup of dstumbler: error: unable to ioctl device socket: Invalid argument From ktrace: 43042 dstumbler CALL sigaction(0x12,0x280b5850,0) 43042 dstumbler RET sigaction 0 43042 dstumbler CALL socket(0x2,0x2,0) 43042 dstumbler RET socket 3 43042 dstumbler CALL ioctl(0x3,SIOCGIFGENERIC,0xbfbff4b0) 43042 dstumbler RET ioctl 0 43042 dstumbler CALL ioctl(0x3,SIOCSIFGENERIC,0xbfbff4c0) 43042 dstumbler RET ioctl 0 43042 dstumbler CALL ioctl(0x3,SIOCGIFGENERIC,0xbfbff4b0) 43042 dstumbler RET ioctl 0 43042 dstumbler CALL ioctl(0x3,SIOCSIFGENERIC,0xbfbff4c0) 43042 dstumbler RET ioctl -1 errno 22 Invalid argument 43042 dstumbler CALL sigaction(0x12,0x280b5838,0x280b5850) 43042 dstumbler RET sigaction 0 43042 dstumbler CALL poll(0xbfbff3e8,0x1,0) 43042 dstumbler RET poll 0 43042 dstumbler CALL poll(0xbfbff3e8,0x1,0) 43042 dstumbler RET poll 0 43042 dstumbler CALL write(0x1,0x806,0x5e) 43042 dstumbler GIO fd 1 wrote 94 bytes \^[[52;22H\^[[34m\^[[1m[\^[[31m error: unable to ioctl device socket: \ Invalid argument \^[[C\^[[39;49m\^[[m\^O wistat.c, line 225 seems to be the offending line that is no longer working. Does dstumbler need to be updated or is this a bug in the new wlan code? -sc -- Sean Chittenden To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Performance problems with 5.0-RELEASE
Nate Lawson wrote: Every time machine is under heavy load (CPU, network, disks) it completely jamms for fraction of a second for every ten seconds or so, everything just stops and then continues. I noticed this while compiling software and copying files over NFS while listening to MP3's, later realized it wasn't just MP3's that lagged, but the whole machine, including console and everything. If you lean on the keyboard, or if you set up the network adapters as entropy sources, does the problem fix itself? This can't be it since /dev/random is non-blocking in 5.x See other posting; though I could certainly write an app that would keep hitting /dev/random until it got what it wanted... -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Performance problems with 5.0-RELEASE
On Fri, 24 Jan 2003, Terry Lambert wrote: Nate Lawson wrote: Every time machine is under heavy load (CPU, network, disks) it completely jamms for fraction of a second for every ten seconds or so, everything just stops and then continues. I noticed this while compiling software and copying files over NFS while listening to MP3's, later realized it wasn't just MP3's that lagged, but the whole machine, including console and everything. If you lean on the keyboard, or if you set up the network adapters as entropy sources, does the problem fix itself? This can't be it since /dev/random is non-blocking in 5.x See other posting; though I could certainly write an app that would keep hitting /dev/random until it got what it wanted... In fact, it's non-blocking AND never returns a 0 byte read len when its entropy is depleted. Try cat /dev/random (I am not saying this behavior is good, just that it is.) -Nate To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: cvs commit: src/sys/netinet if_ether.c
hsu 2003/01/16 23:59:35 PST Modified files: sys/netinet if_ether.c Log: SMP locking for ARP. I just got: lock order reversal 1st 0xc0436078 arp mutex (arp mutex) @ /usr/src/sys/netinet/if_ether.c:151 2nd 0xf800a0668ef0 radix node head (radix node head) @ /usr/src/sys/net/route.c:549 Unfortunately, witness_ddb wasn't on so I don't have a stack trace. Bill To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Problem during alpha cross-building
I'm getting this when trying to cross-build an alpha world. Is anyone else seeing it? cc -O -pipe -DNLIST_ELF64 -static -o crunchide crunchide.o exec_elf64.o exec_elf64.o: In function `hide_elf64': exec_elf64.o(.text+0x30b): undefined reference to `be64toh' exec_elf64.o(.text+0x530): undefined reference to `be64toh' exec_elf64.o(.text+0x575): undefined reference to `be64toh' exec_elf64.o(.text+0x59f): undefined reference to `be64toh' exec_elf64.o(.text+0x5e6): undefined reference to `be64toh' exec_elf64.o(.text+0x639): more undefined references to `be64toh' follow *** Error code 1 Stop in /a/asami/portbuild/alpha/5/src/usr.sbin/crunch/crunchide. *** Error code 1 kris msg50876/pgp0.pgp Description: PGP signature
Re: /dev/dsp disappears while being used
Just thought i'd let you guys know... this problem happens with the onboard sound card on my epox nforce2 board aswell. (it uses the AC97 driver) Thus spake Kenneth Culver ([EMAIL PROTECTED]): This may be related to the vchans stuff in in the pcm driver. Good point. I don't know when I activated the vchans stuff, but I think it was approx. the time the error occured for the first time. Let's see if the error occurs again. Alex To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: acpi problem ???
On Fri, 24 Jan 2003, Nate Lawson wrote: On Thu, 23 Jan 2003, Bryan Liesner wrote: On Thu, 23 Jan 2003, Nate Lawson wrote: On Thu, 23 Jan 2003, Bryan Liesner wrote: I just upgraded my 4.7 system to 5.0-current via sources. Everything went smoothly, and I was up and running quickly, but with an acpi related problem. When booting, the kernel loads, detects the devices, then hangs right here: Mounting root from ufs:/dev/ad0s1a pid 84 (fsck_ufs), uid 0: exited on signal 8 No panic, just a hang. One thing you have wrong is that you have both acpi and apm enabled. Nix apm and try again. Also, try without the usb drive plugged in. I took out the apm and the usb drive, same issue. Thanks... Boot single user, run fsck manually on each partition, then go multiuser. No dice. I'm still getting the FPE on fsck_ufs. I'm kind of puzzled here. One possible clue - I forgot to unset the acpi_load, booted single user, and got the same hang when mounting root. The difference was that I didn't see fsck_ufs exit, the machine just sat there. The system isn't locked up in either case. I can hit ctrl-alt-delete and the system will reboot properly... -- == = Bryan D. Liesner LeezSoft Communications, Inc. = = A subsidiary of LeezSoft Inc. = = [EMAIL PROTECTED]Home of the Gipper= == To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Thanks for the work on devfs and devd!
I just want to thank those who worked on NEWCARD, devfs and devd in V5.0, primarily Dima and imp, I guess. It's been badly needed for a long time, but the advent of USB and Firewire as well as the common use of FreeBSD on laptops had made the lack of dynamic device support a glaring problem in V4. Now that devd is working, things just work--like they should. While this might not be a project the size of the new SMP code, I wanted to let those responsible know that it is really appreciated. I also should thank the NetBSD folks who did the original NEWCARD work, but I don't know where they are. Lots of cool stuff in 5.0, but this one has been annoying me for a LONG time and I know it was really non-trivial to implement some parts of this. Thanks again! I now return you to your regular ration of gripes, some probably from me. 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 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Problem during alpha cross-building
I'm getting this when trying to cross-build an alpha world. Is anyone else seeing it? I got exactly this when I did a 5-CURRENT make world on an alpha running 4.7-RELEASE. I fixed it by hacking the src/Makefile.inc1 cross-tools target to remove crunch(hide?). cc -O -pipe -DNLIST_ELF64 -static -o crunchide crunchide.o exec_elf64.o exec_elf64.o: In function `hide_elf64': exec_elf64.o(.text+0x30b): undefined reference to `be64toh' exec_elf64.o(.text+0x530): undefined reference to `be64toh' exec_elf64.o(.text+0x575): undefined reference to `be64toh' exec_elf64.o(.text+0x59f): undefined reference to `be64toh' exec_elf64.o(.text+0x5e6): undefined reference to `be64toh' exec_elf64.o(.text+0x639): more undefined references to `be64toh' follow *** Error code 1 Stop in /a/asami/portbuild/alpha/5/src/usr.sbin/crunch/crunchide. *** Error code 1 M -- Mark Murray iumop ap!sdn w,I idlaH To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Problem during alpha cross-building
On Fri, Jan 24, 2003 at 02:45:44PM -0800, Kris Kennaway wrote: I'm getting this when trying to cross-build an alpha world. Is anyone else seeing it? cc -O -pipe -DNLIST_ELF64 -static -o crunchide crunchide.o exec_elf64.o exec_elf64.o: In function `hide_elf64': exec_elf64.o(.text+0x30b): undefined reference to `be64toh' exec_elf64.o(.text+0x530): undefined reference to `be64toh' exec_elf64.o(.text+0x575): undefined reference to `be64toh' exec_elf64.o(.text+0x59f): undefined reference to `be64toh' exec_elf64.o(.text+0x5e6): undefined reference to `be64toh' exec_elf64.o(.text+0x639): more undefined references to `be64toh' follow *** Error code 1 Stop in /a/asami/portbuild/alpha/5/src/usr.sbin/crunch/crunchide. *** Error code 1 I get the same problem trying to cross-build sparc64. Looks like cross-building is broken. Kris msg50881/pgp0.pgp Description: PGP signature
Re: 5.0-RELEASE failing on Thinkpad T30
In article [EMAIL PROTECTED], stark [EMAIL PROTECTED] wrote: I tried installing 4.7, cvsup-ing to RELENG_5 (then to '.' cuz there is no RELENG_5. Why not?) but I can't get '.' to compile because gbde keeps failing, looking for rijlaen-alg-fast.c (i think i spelled that right) which isn't there. IN FACT, cvsup-ing didn't put anything in src/sys/crypto at all. You are missing the src-sys-crypto collection in your supfile. Either use the src-all collection (*strongly* recommended) or else read the examples in /usr/share/examples/cvsup carefully and make sure you are getting all the collections you need. John -- John Polstra John D. Polstra Co., Inc.Seattle, Washington USA Disappointment is a good sign of basic intelligence. -- Chögyam Trungpa To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: I've just had a massive file system crash
On Friday, 24 January 2003 at 20:34:24 +1000, Andy Farkas wrote: I'm rather astounded. I'm currently at a Linux conference, and have of course been boasting about the stability of ufs, and today I had a crash which tore apart my /home file system. This is on a laptop, one which has been running -CURRENT for years with no trouble. At the moment it's running 5.0-RELEASE. Today I shut it down cleanly, and a couple of hours later rebooted it. It has three file systems, one of which came up dirty. fsck -y reported thousands of errors, and when it was finished, my home directory and some other files were gone, and all the subdirectories of my home directory were in lost+found, a total of 1.4 GB. Most of the errors appear to be duplicate Inode numbers. Obviously it's too late to work out what happened, but I thought it's worth mentioning in case somebody else is having the same trouble. I can only think that your disk is going bad. That was one of my thoughts too. Try a dd if=/dev/ad0 of=/dev/null and see if you get any read errors. Nope, runs fine. It also doesn't explain why it happened at startup time. On Friday, 24 January 2003 at 6:53:41 -0500, Thomas David Rivers wrote: Don't be too hasty to blame UFS. I'm not. I've just reported what happened, in case others see it. On Friday, 24 January 2003 at 11:06:26 -0500, Robert Watson wrote: Next time you run fsck -y in this scenario, log the output to an md partition and stick it somewhere for analysis. At least, that was the moral of the story last time I hosed a box in this form (incidentally, I think it ended up being a failing hard disk). Yes, if you know it's going to happen. I could easily have written it to /var/tmp, which was mounted. I just wasn't expecting anything like this to happen. I've been using UFS on a daily basis for over 10 years, and this is the first time this has happened to me. I've been thinking about what happened, and I have a possibility: the session before shutdown included a lot of writing to that file system, and I did a shutdown -p. It's possible that the shutdown powered off the system before the disk had flushed its cache. For the moment I'm avoiding shutdown -p, but when I get home I'll try to provoke it again. Greg -- See complete headers for address and phone numbers To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: FreeBSD port of BitTorrent is done. Help test
On Sat, 2003-01-25 at 06:15, Hunter Peress wrote:
http://www.thiago.joi.com.br/andre/bittorrent.html
Basically, all that is required to minimally get things running is that you have
python2.2 available in your ports tree. (for X GUI u'll need wxpython2.3 for
python2.2 (which the package DOESNT require), but there are still 2 nice command
line interfaces: btdownloadheadless.py, and btdownloadcurses.py).
A few suggestions..
- Install the executables without the .py extension
- Dynamically generate pkg-message and substitute PREFIX
Also, the curses version bails with..
Traceback (most recent call
last):---
File /usr/local/bin/btdownloadcurses.py, line 167, in ?
run(argv[1:])
File /usr/local/bin/btdownloadcurses.py, line 115, in run
download(params, d.chooseFile, d.display, d.finished, d.error, Event(), fieldw)
File /usr/local/lib/python2.2/site-packages/BitTorrent/download.py, line 88, in
download
errorfunc('arguments are -\n' + formatDefinitions(defaults, cols))
File /usr/local/bin/btdownloadcurses.py, line 67, in error
self.display()
File /usr/local/bin/btdownloadcurses.py, line 98, in display
fieldwin.addstr(7 + i, 0, self.errors[i], curses.A_BOLD)
_curses.error: addstr() returned ERR
--
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
The nice thing about standards is that there
are so many of them to choose from.
-- Andrew Tanenbaum
GPG Fingerprint - 9A8C 569F 685A D928 5140 AE4B 319B 41F4 5D17 FDD5
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
5.0 SMP status.
I've got a Intel-motherboard-based SMP box I'm going to be using as a fairly heavily loaded mail server. I've currently got 4-Stable on it, but for various reasons I need to blow the installation away and start over. I'm currently wavering between putting 4.x or 5.x on it. I'd like to put 5.x on it since I will have some time (month or so) to stabilize it before it really goes into production. On the other hand, I'm seeing notes in various that indicate that the SMP subsystem might not be nearly stable enough for anything even resembling production work. So I guess my question really is something along the lines of What is the consensus on the stablility of 5.x in an SMP environment? or Other than the newness and lack of real world experience with 5.x is there any other compelling reasons why I shouldn't be putting 5.x on this box? - Forrest W. Christian ([EMAIL PROTECTED]) AC7DE -- The Innovation Machine Ltd. P.O. Box 5749 http://www.imach.com/Helena, MT 59604 Home of PacketFlux Technologies and BackupDNS.com (406)-442-6648 -- Protect your personal freedoms - visit http://www.lp.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: 5.0 SMP status.
I would recomend 4.7 for a production machine. Until 5.0 is -STABLE I wouldn't use it for anything as mission-critical as a Mail server. Adam - Original Message - From: Forrest W. Christian [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Saturday, January 25, 2003 12:25 AM Subject: 5.0 SMP status. I've got a Intel-motherboard-based SMP box I'm going to be using as a fairly heavily loaded mail server. I've currently got 4-Stable on it, but for various reasons I need to blow the installation away and start over. I'm currently wavering between putting 4.x or 5.x on it. I'd like to put 5.x on it since I will have some time (month or so) to stabilize it before it really goes into production. On the other hand, I'm seeing notes in various that indicate that the SMP subsystem might not be nearly stable enough for anything even resembling production work. So I guess my question really is something along the lines of What is the consensus on the stablility of 5.x in an SMP environment? or Other than the newness and lack of real world experience with 5.x is there any other compelling reasons why I shouldn't be putting 5.x on this box? - Forrest W. Christian ([EMAIL PROTECTED]) AC7DE -- The Innovation Machine Ltd. P.O. Box 5749 http://www.imach.com/Helena, MT 59604 Home of PacketFlux Technologies and BackupDNS.com (406)-442-6648 -- Protect your personal freedoms - visit http://www.lp.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: I've just had a massive file system crash
Thus spake Greg Lehey [EMAIL PROTECTED]: I've been thinking about what happened, and I have a possibility: the session before shutdown included a lot of writing to that file system, and I did a shutdown -p. It's possible that the shutdown powered off the system before the disk had flushed its cache. For the moment I'm avoiding shutdown -p, but when I get home I'll try to provoke it again. FreeBSD's ``fix'' for this problem is the same as Windows 98's. Specifically, there is a 5-second delay (tuneable: kern.shutdown.poweroff_delay) after all buffers are flushed but before the power is cut. Maybe we ought to be sending FLUSH CACHE commands to all drives and waiting for them to finish. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
openpam error from sshd
I've just updated bento to 5.0, and sshd is now giving the following error every few seconds: auth.err bento sshd[55737]: in _openpam_check_error_code(): pam_sm_setcred(): unexpected return value 24 Peter says he's seen this elsewhere on the cluster. What's going on? Kris msg50888/pgp0.pgp Description: PGP signature
rcconf.sh error
I get the following at boot time: Loading configuration files. load_rc_config: not found Indeed, rcconf.sh does not appear to have load_rc_config() in scope. Kris msg50889/pgp0.pgp Description: PGP signature
Re: rcconf.sh error
On Fri, Jan 24, 2003 at 11:38:15PM -0800, Kris Kennaway wrote: I get the following at boot time: Loading configuration files. load_rc_config: not found Indeed, rcconf.sh does not appear to have load_rc_config() in scope. This turns out to be because I had local_startup=/etc/rc.d, and rcconf.sh is not a valid shell script. Kris msg50890/pgp0.pgp Description: PGP signature
acquiring duplicate lock of same type: system map
bento found the following about 5 minutes after I upgraded it to 5.0. acquiring duplicate lock of same type: system map 1st system map @ ../../../vm/vm_map.c:2168 2nd system map @ ../../../vm/vm_kern.c:325 Debugger(witness_lock) Stopped at Debugger+0x55: xchgl %ebx,in_Debugger.0 db trace Debugger(c031e895,c03431d1,c034306c,145,0) at Debugger+0x55 witness_lock(c082f110,8,c034306c,145,0) at witness_lock+0x667 _mtx_lock_flags(c082f110,0,c034306c,145,e2e709bc) at _mtx_lock_flags+0xb2 _vm_map_lock(c082f0b0,c034306c,145,e2e709c0,c0398ad8) at _vm_map_lock+0x36 kmem_malloc(c082f0b0,1000,5,e2e70a28,c02bceed) at kmem_malloc+0x65 page_alloc(c083a380,1000,e2e70a1b,5,c03988a8) at page_alloc+0x27 slab_zalloc(c083a380,5,c0344a06,667,c083a564) at slab_zalloc+0xfd uma_zone_slab(c083a380,5,c0344a06,667,0) at uma_zone_slab+0xd8 uma_zalloc_internal(c083a380,0,5,6e7,0) at uma_zalloc_internal+0x55 uma_zfree_arg(c083a540,c6612260,0,263,c01bc2e4,c082e8e8) at uma_zfree_arg+0x2c9 vm_object_terminate(c6612260,0,c0343b02,1b4,c082e8e8) at vm_object_terminate+0x246 vm_object_deallocate(c6612260,c082e8e8,c6612260,c082e8e8,e2e70b54) at vm_object_deallocate+0x1cc vm_map_entry_delete(c082f000,c082e8e8,c034323f,85b,8) at vm_map_entry_delete+0x3b vm_map_delete(c082f000,e2eef000,e2ef3000,c63948f0,c63948f0) at vm_map_delete+0x3c0 vm_map_remove(c082f000,e2eef000,e2ef3000,e2e70ba8,c01ddccd) at vm_map_remove+0x55 kmem_free(c082f000,e2eef000,4000,536,c63948f0) at kmem_free+0x32 pipe_free_kmem(c63948f0,0,c0336818,58b,0) at pipe_free_kmem+0x9d pipeclose(c63948f0,c6392654,e2e70c44,c019b7ac,c6392654) at pipeclose+0x25c pipe_close(c6392654,c65930e0,c0330e48,739,0) at pipe_close+0x33 fdrop_locked(c6392654,c65930e0,c0330e48,673,c65930e0) at fdrop_locked+0x17c fdrop(c6392654,c65930e0,c0396b80,c0398ad8,246) at fdrop+0x3e closef(c6392654,c65930e0,c0330e48,33a,c6392654) at closef+0xac close(c65930e0,e2e70d10,c0348e68,407,1) at close+0x158 syscall(2f,2f,2f,bfbff8db,bfbff8c0) at syscall+0x28e Xint0x80_syscall() at Xint0x80_syscall+0x1d --- syscall (6, FreeBSD ELF32, close), eip = 0x807bd13, esp = 0xbfbff87c, ebp = 0xbfbff968 --- db msg50891/pgp0.pgp Description: PGP signature
