vinum zero divide crashes under RELENG_4
Dear colleagues, is anyone interested in analyzing vinum crashdumps under RELENG_4? The problem is that crash situations are not easily reproducible (they are related to changing in-memory and on-disk vinum configs), but almost every refers to #6 0xc01ff69b in __divdi3 (a=0x1000, b=0x0) at /FreeBSD/src.411/sys/libkern/divdi3.c:61 #7 0xc02abc8e in driveio (drive=0xc38e41f8, buf=0xc3c96c00 IN VINO, length=0x200, offset=0x1000, flag=0x0) at /FreeBSD/src.411/sys/modules/vinum/../../dev/vinum/vinumio.c:330 which is 330 bp-b_blkno = offset / drive-partinfo.disklab-d_secsize; /* block number */ (in my last case, drive-partinfo.disklab is filled with zeros except d_magic field) Thanks in advacne. Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- [EMAIL PROTECTED] *** ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
xSeries346 and FreeBSD 5.3
Welcome, I've just bought IBM xSeries346 server. There was no problem with installing FreeBSD 5.3, but problem is with LAN card - BCM5721 (I think, reseller told me this name). Is there any possibility to run this card? Best Regards, -- Przemysaw Ciesielski ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xSeries346 and FreeBSD 5.3
On Wed, 9 Mar 2005 12:10:09 +0100, pck [EMAIL PROTECTED] wrote: Welcome, I've just bought IBM xSeries346 server. There was no problem with installing FreeBSD 5.3, but problem is with LAN card - BCM5721 (I think, reseller told me this name). Is there any possibility to run this card? You have to install a 5-STABLE or manually get following files src/sys/dev/bge/* src/sys/dev/mii/miidevs src/sys/dev/mii/brgphy.c and recompile kernel. without those two mii files, you can only run 100-baseTX. Regards, Rong-En Fan ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xSeries346 and FreeBSD 5.3
Hi, On Wed, 9 Mar 2005 19:22:09 +0800, Rong-En Fan [EMAIL PROTECTED] wrote: On Wed, 9 Mar 2005 12:10:09 +0100, pck [EMAIL PROTECTED] wrote: Welcome, I've just bought IBM xSeries346 server. There was no problem with installing FreeBSD 5.3, but problem is with LAN card - BCM5721 (I think, reseller told me this name). Is there any possibility to run this card? You have to install a 5-STABLE or manually get following files src/sys/dev/bge/* src/sys/dev/mii/miidevs src/sys/dev/mii/brgphy.c and recompile kernel. without those two mii files, you can only run 100-baseTX. From where i must download these files? I've just made cvsup on my workstation (*default release=cvs tag=RELENG_5) and got: saucepan# pwd /usr/src/sys/dev/bge saucepan# ls -al total 186 drwxr-xr-x2 root wheel 512 Mar 9 12:51 . drwxr-xr-x 155 root wheel2560 Mar 9 12:53 .. -rw-r--r--1 root wheel 101313 Mar 2 21:29 if_bge.c -rw-r--r--1 root wheel 81011 Mar 2 11:08 if_bgereg.h saucepan# Best regards, -- Przemysaw Ciesielski ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: if_bfe/uhci: storm interrupt Fatal trap 12
On 7 Mar, Doug White wrote:
Thanks for the detailed message. I didn't realize that we'd enabled DDB in
the snapshot kernel :)
Anyway this looks like a bug in the bfe driver. It appears to be trying
to free a DMA map that is either unallocated or got spammed. You may want
to repost this to freebsd-current@freebsd.org and use a subject like
Use-after-free in bfe since I think the interrupt storm message is
secondary.
A capture of boot -v might also be useful, or at minumum anything the bfe
driver output during boot ('dmesg | grep bfe' might work with the fixit
disc). A crashdump would be nice too, but you'd likely need to find a
different network adapter.
I have escalated this problem to [EMAIL PROTECTED]
I have also built a STABLE kernel with DDD and KDB options and the line
where the problem occurs is
_bus_dmamap_unload+0x16: movl 0x10(%eax),%eax
I have enable crash dumps (I think) but when booting I have savecore:
no dumps found. I think the problem is that i have 1.5Gb of memory and
only 1Gb of swap.
Well, I will add this info to the message I sent on [EMAIL PROTECTED]
Phil.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: gmirror over ggate{d,c}
Hi Pawel! On Sat, 05 Mar 2005, Pawel Jakub Dawidek wrote: First of all, can you increase buffers: net.inet.tcp.sendspace=4194304 net.inet.tcp.recvspace=4194304 kern.ipc.maxsockbuf=2097152 And run ggated and ggatec with '-R 1048576 -S 1048576'? $ sudo sysctl net.inet.tcp.sendspace=4194304 net.inet.tcp.sendspace: 32768 - 4194304 $ sudo sysctl net.inet.tcp.recvspace=4194304 net.inet.tcp.recvspace: 65536 - 4194304 $ sudo sysctl kern.ipc.maxsockbuf=2097152 kern.ipc.maxsockbuf: 262144 - 2097152 $ sudo ggated -R 1048576 -S 1048576 And get messages on console: clh1 ggated: Can't open stream socket: No buffer space available. Mar 9 18:43:17 clh1 ggated: Exiting. By. Dmitriy ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
from 5.4-PRERELEASE - 5.3-RELEASE-p5 error?
Hello, i was wondering just right after the downgrade been facing some issues such as: 1. server# /usr/local/bin/strace -f ps PIOCSFL: Inappropriate ioctl for device trouble opening proc file 2. mounting ext2fs partition doesn't work unless i specify -ro or it will give operation not permitted. any idea what might be causing this? Thanks, ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Continued instability with 5.3-STABLE
I have a dual Opteron upon which seems to only stay up approximately two weeks at a time then spontaneously reboots. It's colocated so I can't ever see panic messages, and I don't have another system colocated at the same place I can use to gather debugging info. I've never managed to get the system to generate a crash dump either. It has a 1GB swap partition and 2GB of physical RAM but through the last few reboots I've been setting hw.physmem to 896M as the only custom parameter in loader.conf. The swap partition is labeled as follows: twed0s1b swap 1024MB SWAP And dumpdev is set in rc.conf as follows: dumpdev=/dev/twed0s1b /var/crash/minfree is set to 2048 Lately I built a kernel from GENERIC using the latest RELENG_5 sources and without SMP support and experienced a reboot after approximately 16 days uptime, roughly equivalent to how long it took the system to crash with SMP enabled. No core file was generated. The kernel was built using source checked out from RELENG_5 on February 18th. I'm not sure if any Opteron specific fixes have been applied to the branch since then. Are there any other means of gathering debugging data that would work in my situation? As is I'm still unsure if my problems are hardware or software related as I've still never seen a panic message from the system (hardware is a Tyan K8S motherboard in a Tyan Transport system) Should I look into using KTR ALQ to log KTR data to the swap partition, and if it fills up will it wrap over to the beginning? I've never used that feature before... Tony Arcieri ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xSeries346 and FreeBSD 5.3
pck wrote: On Wed, 9 Mar 2005 19:22:09 +0800, Rong-En Fan [EMAIL PROTECTED] wrote: On Wed, 9 Mar 2005 12:10:09 +0100, pck [EMAIL PROTECTED] wrote: Welcome, I've just bought IBM xSeries346 server. There was no problem with installing FreeBSD 5.3, but problem is with LAN card - BCM5721 (I think, reseller told me this name). Is there any possibility to run this card? You have to install a 5-STABLE or manually get following files src/sys/dev/bge/* src/sys/dev/mii/miidevs src/sys/dev/mii/brgphy.c and recompile kernel. without those two mii files, you can only run 100-baseTX. From where i must download these files? I've just made cvsup on my workstation (*default release=cvs tag=RELENG_5) and got: So you updated your source to 5-STABLE. saucepan# pwd /usr/src/sys/dev/bge saucepan# ls -al total 186 drwxr-xr-x2 root wheel 512 Mar 9 12:51 . drwxr-xr-x 155 root wheel2560 Mar 9 12:53 .. -rw-r--r--1 root wheel 101313 Mar 2 21:29 if_bge.c -rw-r--r--1 root wheel 81011 Mar 2 11:08 if_bgereg.h saucepan# Looks like what I have here. Follow the directions near the bottom of /usr/src/UPDATING to update the system from source: To rebuild everything and install it on the current system. When you're done you should be running 5-STABLE (currently 5.4-PRERELEASE). Jon ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Floppy problems in 5.3
Sirs: I'm having a problem doing newfs to a floppy on a new installation (5.3-stable). I tried changing to a new floppy and get the same thing. # fdformat -f 1440 /dev/fd0 Format 1440K floppy `/dev/fd0'? (y/n): y Processing done. # bsdlabel -B -w /dev/fd0 fd1440 # newfs /dev/fd0 newfs: wtfs: 512 bytes at sector 2879: Input/output error --or-- # newfs_msdos /dev/fd0 /dev/fd0: 2840 sectors in 355 FAT12 clusters (4096 bytes/cluster) bps=512 spc=8 res=1 nft=2 rde=512 sec=2880 mid=0xf0 spf=2 spt=18 hds=2 hid=0 newfs_msdos: /dev/fd0: Input/output error # If I take a linux formatted floppy, mount it, then ls on the mount point, I can get the dir listing. Or if I less a file on the floppy I can read the contents. Any attempt to use vi or to write to the floppy fails with another Input/Output error. Of course, the same drives and floppies mount, read, and write under Minix, Slackware-10.0 and FreeBSD 4.11. # uname -a FreeBSD 5.3-RELEASE FreeBSD 5.3-RELEASE #0: Fri Nov 5 04:19:18 UTC 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 # devfs.conf contains... # allow fd0 [devfsrules_fd0=10] add path fd0 add path fd0 mode 0660 and rc.conf contains... #devfs_system_ruleset=devfsrules_fd0 I noticed in UPDATING that floppy under pci was broken at one point. Is that still the case and am I seeintg that broken-ness? Can you help? TIA. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
ath0 as AP: station already associated
Hi. I have a Netgear WG311T (5212, I believe) that I've been using as a wireless access point in a linux box using madwifi for a while now. I moved it to my freebsd box, and I can't seem to get it to work properly. I can see its ssid when scanning with my other card (a netgear WG511), under both linux and windows. However, any attempt to associate seems to just do nothing. With ifconfig ath0 debug, I can see that that dmesg contains a lot of lines like the following: ath0: received assoc_req from 00:09:5b:ec:c8:1d rssi 63 ath0: sending assoc_resp to 00:09:5b:ec:c8:1d on channel 3 ath0: station already 00:09:5b:ec:c8:1d associated ath0: received assoc_req from 00:09:5b:ec:c8:1d rssi 63 ath0: sending assoc_resp to 00:09:5b:ec:c8:1d on channel 3 ath0: station already 00:09:5b:ec:c8:1d associated ath0: received assoc_req from 00:09:5b:ec:c8:1d rssi 62 ath0: sending assoc_resp to 00:09:5b:ec:c8:1d on channel 3 ath0: station already 00:09:5b:ec:c8:1d associated There is a huge flurry of these every time the client tries to connect. The rssi varies. the MAC address listed is the client's. No pings or similar data travels between the two. # ifconfig ath0 ath0: flags=8847UP,BROADCAST,DEBUG,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet6 fe80::20f:b5ff:fe5c:7562%ath0 prefixlen 64 scopeid 0x2 inet 192.168.5.3 netmask 0xff00 broadcast 192.168.5.255 ether 00:0f:b5:5c:75:62 media: IEEE 802.11 Wireless Ethernet autoselect mode 11b hostap status: associated ssid my_ap 1:my_ap channel 3 authmode OPEN powersavemode OFF powersavesleep 100 rtsthreshold 2312 protmode CTS wepmode OFF weptxkey 1 I've tried a variety of modes. I've copied the lines directly out of the man page for 'create an 802.11g access point' (ifconfig ath0 inet 192.168.5.3 netmask 0xff00 ssid my_ap mode 11g mediaopt hostap) and 'create a host-based wireless bridge' (ifconfig ath0 inet up ssid my_ap media DS/11Mbps mediaopt hostap). Even an ad-hoc setup doesn't seem to work. My goal is to use this as a bridge, but obviously this cannot be done until I can get the card to behave. # uname -a FreeBSD cassiopeia 5.4-PRERELEASE FreeBSD 5.4-PRERELEASE #0: Wed Mar 9 00:35:01 CST 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/CASSIOPEIA i386 I just cvsupped to stable two days ago from a fresh install of 5.3-RELEASE. I built the kernel with device ath and device ath_hal. Any suggestions? Have I made a stupid mistake somewhere? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Floppy problems in 5.3
On Thu, 10 Mar 2005 06:32, [EMAIL PROTECTED] wrote: # bsdlabel -B -w /dev/fd0 fd1440 # newfs /dev/fd0 newfs: wtfs: 512 bytes at sector 2879: Input/output error ... # newfs_msdos /dev/fd0 /dev/fd0: 2840 sectors in 355 FAT12 clusters (4096 bytes/cluster) bps=512 spc=8 res=1 nft=2 rde=512 sec=2880 mid=0xf0 spf=2 spt=18 hds=2 hid=0 newfs_msdos: /dev/fd0: Input/output error # Do you get anything in dmesg from these? If I take a linux formatted floppy, mount it, then ls on the mount point, I can get the dir listing. Or if I less a file on the floppy I can read the contents. Any attempt to use vi or to write to the floppy fails with another Input/Output error. Of course, the same drives and floppies mount, read, and write under Minix, Slackware-10.0 and FreeBSD 4.11. Tried that floppy drive with a different OS, or tried a different drive with FreeBSD? -- 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 - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C pgp7a1HhFMe7C.pgp Description: PGP signature
Re: UPDATE 5.3-STABLE was Re: Possible problems with BroadcomBCM5704C 10/100/1000 on TyanThunder K8S pro S2882 twin Operteron
On Mon, 7 Mar 2005, Alan Jay wrote: Well after upgrading to the latest -STABLE via cvsup and makeworld makekernel etc we have been doing some more tests over the weekend. When did you run this cvsup? One of our databases ran fine all weekend so we took the plunge on Sunday to try our big heavily accessed database. It ran fine until 7.45 Monday morning - when I checked at 7.30am it was using around 6 of the 8Gb of RAM the server then logged: Mar 7 07:42:47 flappy kernel: bge1: discard frame w/o leading ethernet header (len 4294967292 pkt len 4294967292) Hm, unsigned -1. That message is printed by ether_input() if it get handed a bum mbuf. Followed by: Mar 7 07:42:47 flappy kernel: Fatal trap 12: pag Unfortunately this is not useful. We need the entire panic messsage and ideally a backtrace and crashdump. Can you connect a serial console to this system and log the output? Subsequently to that it has crashed a number of times and on a couple of occasions has reported: kernel: fxp0: can't map mbuf (error 12) Error 12 is ENOMEM and thats coming from bus_dmamap_load_mbuf(). That can be returned if you're running out of space for bounce buffers, or kmem in general. scottl has been working on busdma issues in HEAD and recently committed a fix for i386 for bounce page allocation issues. kmem depletion would be more insidious. Have you been getting other message that indicates failure to allocate memory or error 12? By the way over the weekend the latest -STABLE which is marked 5.4-PRERELEASE 2 seemed much better than 5.3 had and the initial problems took much longer to appear. Though once the problems started to appear, they repeated themselves rebooting every 1-2hrs until we removed the tests data. That behavior sounds a lot like thermal issues. It takes a while to warm up to the critcal point and once it hits that point it really starts to malfunction. Unless the test run starts out slow or something. -- Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: if_bfe/uhci: storm interrupt Fatal trap 12
On Wed, 9 Mar 2005 [EMAIL PROTECTED] wrote:
On 7 Mar, Doug White wrote:
Thanks for the detailed message. I didn't realize that we'd enabled DDB in
the snapshot kernel :)
Anyway this looks like a bug in the bfe driver. It appears to be trying
to free a DMA map that is either unallocated or got spammed. You may want
to repost this to freebsd-current@freebsd.org and use a subject like
Use-after-free in bfe since I think the interrupt storm message is
secondary.
A capture of boot -v might also be useful, or at minumum anything the bfe
driver output during boot ('dmesg | grep bfe' might work with the fixit
disc). A crashdump would be nice too, but you'd likely need to find a
different network adapter.
I have escalated this problem to [EMAIL PROTECTED]
I have also built a STABLE kernel with DDD and KDB options and the line
where the problem occurs is
_bus_dmamap_unload+0x16: movl 0x10(%eax),%eax
That was in the previous trace.
I have enable crash dumps (I think) but when booting I have savecore:
no dumps found. I think the problem is that i have 1.5Gb of memory and
only 1Gb of swap.
Yeah, that will be a problem.
--
Doug White| FreeBSD: The Power to Serve
[EMAIL PROTECTED] | www.FreeBSD.org
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Floppy problems
On Mon, 7 Mar 2005 [EMAIL PROTECTED] wrote: Sirs: I'm having a problem doing newfs to a floppy on a new installation. I tried changing to a new floppy and get the same thing. # fdformat -f 1440 /dev/fd0 Format 1440K floppy `/dev/fd0'? (y/n): y Processing done. # bsdlabel -B -w /dev/fd0 fd1440 # newfs /dev/fd0 newfs: wtfs: 512 bytes at sector 2879: Input/output error Can't say I've ever tried to make a UFS filesystem on a floppy, but sector 2879 is off the end of the disk. newfs probably needs a hint for the disk size. 'newfs -T fd1440 /dev/fd0' may work better. # newfs_msdos /dev/fd0 /dev/fd0: 2840 sectors in 355 FAT12 clusters (4096 bytes/cluster) bps=512 spc=8 res=1 nft=2 rde=512 sec=2880 mid=0xf0 spf=2 spt=18 hds=2 hid=0 newfs_msdos: /dev/fd0: Input/output error The previous newfs proble may have corrupted the floppy. Try fdformat again then newfs_msdos. If you still get an error check the kernel messages (dmesg) for any errors from the fd driver. -- Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Typo in UPDATING for RELENG_5
On Mon, 7 Mar 2005, Andre Guibert de Bruet wrote: Hi I spotted a typo in RELENG_5's 20050302 UPDATING entry. It reads: ... This option has to be specified in addition to IPFIRWALL_FORWARD. ... The option enumerated should be IPFIREWALL_FORWARD. That was fixed 2 days ago, in rev 1.342.2.24. -- Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
[releng_5 tinderbox] failure on sparc64/sparc64
TB --- 2005-03-10 03:12:31 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2005-03-10 03:12:31 - starting RELENG_5 tinderbox run for sparc64/sparc64 TB --- 2005-03-10 03:12:31 - checking out the source tree TB --- 2005-03-10 03:12:31 - cd /home/tinderbox/RELENG_5/sparc64/sparc64 TB --- 2005-03-10 03:12:31 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -rRELENG_5 src TB --- 2005-03-10 03:21:42 - building world (CFLAGS=-O -pipe) TB --- 2005-03-10 03:21:42 - cd /home/tinderbox/RELENG_5/sparc64/sparc64/src TB --- 2005-03-10 03:21:42 - /usr/bin/make -B buildworld Rebuilding the temporary build tree stage 1.1: legacy release compatibility shims stage 1.2: bootstrap tools stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3: cross tools stage 4.1: building includes stage 4.2: building libraries stage 4.3: make dependencies stage 4.4: building everything TB --- 2005-03-10 04:11:57 - building generic kernel (COPTFLAGS=-O -pipe) TB --- 2005-03-10 04:11:57 - cd /home/tinderbox/RELENG_5/sparc64/sparc64/src TB --- 2005-03-10 04:11:57 - /usr/bin/make buildkernel KERNCONF=GENERIC Kernel build for GENERIC started on Thu Mar 10 04:11:57 UTC 2005 stage 1: configuring the kernel stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3.1: making dependencies stage 3.2: building everything [...] cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/tinderbox/RELENG_5/sparc64/sparc64/src/sys -I/tinderbox/RELENG_5/sparc64/sparc64/src/sys/contrib/dev/acpica -I/tinderbox/RELENG_5/sparc64/sparc64/src/sys/contrib/altq -I/tinderbox/RELENG_5/sparc64/sparc64/src/sys/contrib/ipfilter -I/tinderbox/RELENG_5/sparc64/sparc64/src/sys/contrib/pf -I/tinderbox/RELENG_5/sparc64/sparc64/src/sys/contrib/dev/ath -I/tinderbox/RELENG_5/sparc64/sparc64/src/sys/contrib/dev/ath/freebsd -I/tinderbox/RELENG_5/sparc64/sparc64/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -mcmodel=medlow -msoft-float -ffreestanding -Werror /tinderbox/RELENG_5/sparc64/sparc64/src/sys/sparc64/sparc64/vm_machdep.c /tinderbox/RELENG_5/sparc64/sparc64/src/sys/sparc64/sparc64/vm_machdep.c: In function `sf_buf_alloc': /tinderbox/RELENG_5/sparc64/sparc64/src/sys/sparc64/sparc64/vm_machdep.c:380: error: syntax error before break /tinderbox/RELENG_5/sparc64/sparc64/src/sys/sparc64/sparc64/vm_machdep.c: At top level: /tinderbox/RELENG_5/sparc64/sparc64/src/sys/sparc64/sparc64/vm_machdep.c:409: warning: no previous prototype for 'sf_buf_free' /tinderbox/RELENG_5/sparc64/sparc64/src/sys/sparc64/sparc64/vm_machdep.c:422: warning: no previous prototype for 'swi_vm' /tinderbox/RELENG_5/sparc64/sparc64/src/sys/sparc64/sparc64/vm_machdep.c:432: warning: no previous prototype for 'uma_small_alloc' /tinderbox/RELENG_5/sparc64/sparc64/src/sys/sparc64/sparc64/vm_machdep.c:478: warning: no previous prototype for 'uma_small_free' *** Error code 1 Stop in /tinderbox/RELENG_5/sparc64/sparc64/obj/sparc64/tinderbox/RELENG_5/sparc64/sparc64/src/sys/GENERIC. *** Error code 1 Stop in /tinderbox/RELENG_5/sparc64/sparc64/src. *** Error code 1 Stop in /tinderbox/RELENG_5/sparc64/sparc64/src. TB --- 2005-03-10 04:16:24 - WARNING: /usr/bin/make returned exit code 1 TB --- 2005-03-10 04:16:24 - ERROR: failed to build generic kernel TB --- 2005-03-10 04:16:24 - tinderbox aborted ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Can FreeBSD be installed on DellPowerEdge2800 ?
At 09:15 PM 08/03/2005 -0600, David Sze wrote this to All: At 05:55 PM 08/03/2005 -0700, Scott Long wrote this to All: David Sze wrote: On my 2850 the upper 1GB of RAM cannot be addressed without PAE support in the kernel. However, amr in 4.11-RELEASE does indeed seem to have trouble with PAE. The result being that with the option in the kernel, the root device (ufs:/dev/amrd0s1a) cannot be found. I backported scottl's amr PAE fixes from RELENG_5; the diffs applied cleanly (with offsets). I'm happy to report that my 2850 can now address its full 4GB and see its amr volumes. The diff against 4.11-RELEASE is attached, hopefully someone will be willing to commit it to RELENG_4. I don't have the cycles to watch after RELENG_4, so I'll have to take your word that this works. What date is this patch against? I committed some follow-up fixes last week that are required for management apps to work (and yes, LSI is getting ready to support FreeBSD with management apps). The patch is against 4.11-RELEASE, and is just a backport of your commit from Dec. 5th (http://lists.freebsd.org/pipermail/cvs-all/2004-December/094923.html). There haven't been any changes to amr since release, so it should apply directly to RELENG_4 as well. I left out the subsequent ioctl fixes and LSI 320-2E support. They look straightforward, but I don't have the software or hardware to test them. If you'd like them in there before committing to RELENG_4, I can take a stab at it and post a new patch. A new patch is attached to this message that synchronizes the RELENG_4 amr driver with CURRENT, minus the SMPng locking and amd64/ia64 ioctl compatibility stuff. The fixes and their corresponding file revisions are: Greater than 4GB support amr.c 1.55, 1.56, 1.59 amr_cam.c 1.10 amr_pci.c 1.24 amrvar.h1.23 ioctl fixes for LSI management tools amr.c 1.60, 1.61 Fix module unloading amr_cam.c 1.12 amrvar.h1.24 Check for NULL amrd_sc in amrd_dump amr_disk.c 1.32 Support for LSI 320-2E PCI Express controller amr_pci.c 1.27 amrreg.h1.8 amrvar.h1.26 The only part of the patch I've tested is the 4GB support. The rest compiles but I can't vouch for its validity because I don't have the software or hardware to test. amr-4.x-MFC.patch Description: Binary data ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Just a sanity check before I sumbit a buig report
On Tue, 8 Mar 2005, Pete French wrote: The man page for getrusage says that the frequency of the statistics clock is given by sysconf(_SC_CLK_TCK). The source code to /usr/bin/time uses a function 'getstathz' to get the frequency of the statistics clock which is does using sysctl and KERN_CLOCKRATE 'sysctl kern.clockrate' will return this information if you don't want to write a program to do it for you :) On my system the first returns 100Hz and the second 128Hz!!! What are the two machines? stathz is 128 on i386, 100 on sparc64, and 130 on amd64. Or thats the defaults at least. -- Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.3-Stable Dual Opteron with 12GB memory!
On Tue, 8 Mar 2005, Martin Nilsson wrote: Anybody running a recent 5.3-stable amd64 on a box with lots of memory, and does it work? From very brief testing a Dual Opteron with 12GB memory just reboots when the kenel probes devices. SATA disks on built in SiL 3114 controller. 5.3-stable from yesterday compiled with -O, the system works with 8GB memory. Have anybody else got a similar system working? There was a known problem with 5.3-RELEASE and 4GB RAM. As you found, 5.3-stable has the fix, as well as 5.3-RELEASE-p5. -- Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Promise FastTrak Tx4200 FreeBSD 5.3
Dropping cc: back to -stable. Don't crosspost lists, thanks. On Wed, 9 Mar 2005, Simon Litchfield wrote: Hi folks Anyone have any ideas on the Promise PDC20319 (Fasttrak S150 TX4)? We intend to run 5.3 release on this machine. Whats the question? -- Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ad0 errors on FBSD 4.11-RELEASE
On Wed, 9 Mar 2005, Jim C. Nasby wrote: Since moving my machine, I've been having all kinds of issues with ad0. Here's one example: Mar 9 06:26:23 flake /kernel: ad0: READ command timeout tag=0 serv=1 - resetting Mar 9 06:26:23 flake /kernel: ad0: invalidating queued requests Mar 9 06:26:23 flake /kernel: ata0: resetting devices .. ad0: invalidating queued requests Mar 9 06:26:23 flake /kernel: done Mar 9 06:26:23 flake /kernel: ad0: timeout waiting for READY Mar 9 06:26:23 flake /kernel: ad0: invalidating queued requests Mar 9 06:26:23 flake /kernel: ad0: timeout sending command=00 s=d0 e=04 Mar 9 06:26:23 flake /kernel: ad0: flush queue failed Mar 9 06:26:23 flake /kernel: - resetting Mar 9 06:26:23 flake /kernel: ata0: resetting devices .. ad0: invalidating queued requests Mar 9 06:26:23 flake /kernel: done Mar 9 06:26:23 flake /kernel: ad0: READ command timeout tag=0 serv=1 - resetting Mar 9 06:26:23 flake /kernel: ad0: invalidating queued requests Mar 9 06:26:23 flake /kernel: ata0: resetting devices .. ad0: invalidating queued requests Mar 9 06:26:23 flake /kernel: done Mar 9 06:26:23 flake /kernel: ad0: WRITE command timeout tag=1 serv=0 - resetting Mar 9 06:26:23 flake /kernel: ad0: invalidating queued requests Mar 9 06:26:23 flake /kernel: ad0: timeout waiting for READY Mar 9 06:26:23 flake /kernel: ad0: invalidating queued requests Mar 9 06:26:23 flake /kernel: - resetting Mar 9 06:26:23 flake /kernel: ata0: resetting devices .. ad0: invalidating queued requests Mar 9 06:26:23 flake /kernel: done Mar 9 06:26:23 flake /kernel: ata0: resetting devices .. ad0: invalidating queued requests Mar 9 06:26:23 flake /kernel: done These issues have been resulting in spontaneous reboots; presumably from kernel panics. FreeBSD version in use and ATA hardware description would be nice. If this is 4.x it looks like you have tagged queueing on; try turning it off. -- Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: from 5.4-PRERELEASE - 5.3-RELEASE-p5 error?
On Wed, 9 Mar 2005, Bashar wrote: Hello, i was wondering just right after the downgrade been facing some issues such as: 1. server# /usr/local/bin/strace -f ps PIOCSFL: Inappropriate ioctl for device trouble opening proc file 2. mounting ext2fs partition doesn't work unless i specify -ro or it will give operation not permitted. any idea what might be causing this? How did you perform the downgrade? The strace error looks like you're still running the 5.3-STABLE binary. -- Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Continued instability with 5.3-STABLE
On Wed, 9 Mar 2005, Tony Arcieri wrote: I have a dual Opteron upon which seems to only stay up approximately two weeks at a time then spontaneously reboots. It's colocated so I can't ever see panic messages, and I don't have another system colocated at the same place I can use to gather debugging info. You may want to consider finding a small system with a free serial port to serve as a temporary serial console. Without output from the crash its impossible to tell what went wrong. I've never managed to get the system to generate a crash dump either. It has a 1GB swap partition and 2GB of physical RAM but through the last few reboots I've been setting hw.physmem to 896M as the only custom parameter in loader.conf. The swap partition is labeled as follows: twed0s1b swap 1024MB SWAP And dumpdev is set in rc.conf as follows: dumpdev=/dev/twed0s1b /var/crash/minfree is set to 2048 Lately I built a kernel from GENERIC using the latest RELENG_5 sources and without SMP support and experienced a reboot after approximately 16 days uptime, roughly equivalent to how long it took the system to crash with SMP enabled. No core file was generated. The kernel was built using source checked out from RELENG_5 on February 18th. I'm not sure if any Opteron specific fixes have been applied to the branch since then. Make sure you're actually running this kernel since crashdump support for twe was added 2/12, in rev 1.22.2.1 of src/sys/dev/twe/twe.c. Are there any other means of gathering debugging data that would work in my situation? As is I'm still unsure if my problems are hardware or software related as I've still never seen a panic message from the system (hardware is a Tyan K8S motherboard in a Tyan Transport system) You really, really want a serial console. Should I look into using KTR ALQ to log KTR data to the swap partition, and if it fills up will it wrap over to the beginning? I've never used that feature before... If you don't have a serial console to manipulate ddb from or crashdumps then there is no way to retrieve the ktr data. -- Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
