FreeBSD 5.5-STABLE, HP DC7600CMT : bge0 and irq issues
I am having a problem that I have now come to believe is specific only to HP DC7600 CMT PC, of which I have several pieces running FreeBSD 5.5-STABLE (all updated via CVSUP). When these PCs boot, I see the following messages on the console: Interrupt storm detected on irq19: atapci1; throttling interrupt source bge0: firmware handshake timed out Now gw# grep irq /var/run/dmesg.boot ioapic0 Version 2.0 irqs 0-23 on motherboard pcib2: MPTable PCI-PCI bridge irq 17 at device 28.1 on pci0 bge0: Broadcom BCM5752 Gigabit Ethernet, ASIC rev. 0x6001 mem 0xe050-0xe050 irq 17 at device 0.0 on pci63 uhci0: UHCI (generic) USB controller port 0x2000-0x201f irq 20 at device 29.0 on pci0 uhci1: UHCI (generic) USB controller port 0x2020-0x203f irq 18 at device 29.1 on pci0 uhci2: UHCI (generic) USB controller port 0x2040-0x205f irq 21 at device 29.2 on pci0 uhci3: UHCI (generic) USB controller port 0x2060-0x207f irq 22 at device 29.3 on pci0 ehci0: EHCI (generic) USB 2.0 controller mem 0xe04c4000-0xe04c43ff irq 20 at device 29.7 on pci0 xl0: 3Com 3c905-TX Fast Etherlink XL port 0x1000-0x103f irq 16 at device 4.0 on pci5 atapci0: GENERIC ATA controller port 0x20a0-0x20af,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 irq 17 at device 31.1 on pci0 atapci1: GENERIC ATA controller port 0x20b0-0x20bf,0x20f4-0x20f7,0x20e0-0x20e7,0x20f0-0x20f3,0x20d8-0x20df irq 19 at device 31.2 on pci0 atkbd0: AT Keyboard irq 1 on atkbdc0 fdc0: Enhanced floppy controller at port 0x3f0-0x3f5 irq 6 drq 2 on isa0 ppc0: Parallel port at port 0x378-0x37f irq 7 on isa0 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio1: configured irq 3 not in bitmap of probed irqs 0 Interrupt storm detected on irq19: atapci1; throttling interrupt source irq 19 is assigned atapci1 from the above messages. I have tried google, but perhaps with the wrong keywords, as happens sometimes! Q1. Why I am getting Interrupt storm? Q2. Is there a particular problem with the bge0 drivers? (but why only on this PC, because I haven't seen this on other PCs havnng bge cards) Thank you 4 any insights.. -Wash http://www.netmeister.org/news/learn2quote.html DISCLAIMER: See http://www.wananchi.com/bms/terms.php -- +==+ |\ _,,,---,,_ | Odhiambo Washington[EMAIL PROTECTED] Zzz /,`.-'`'-. ;-;;,_ | Wananchi Online Ltd. www.wananchi.com |,4- ) )-,_. ,\ ( `'-'| Tel: +254 20 313985-9 +254 20 313922 '---''(_/--' `-'\_) | GSM: +254 722 743223 +254 733 744121 +==+ Just once, I wish we would encounter an alien menace that wasn't immune to bullets -- The Brigader, Dr. Who ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
6.2 RELEASE - READ_DMA timed out
I have a router running NanoBSD on a CF-card, 512MB SanDisk and
yesterday when installed 6.2-RELEASE I encountered some problems.
The systems seems to boot properly but when it tries to mount the
filesystem I get errors like this:
ad0: FAILURE - READ_DMA timed out LBA=1000941
When I try to boot without acpi I get the same problem but when I boot
in Safe Mode it boots properly and I haven't encountered any problems
at all.
I have'nt compiled any modules, and the acpi.ko is missing, could that
be the problem? It worked fine i 6.1-RELEASE though.
What could be the problem? If there is no quick solution to this, are
there any way to make Safe Mode the default option at boot?
I've attached my kernconf and configuration for the NanoBSD-build.
#!/bin/sh
# Copyright (c) 2005 Poul-Henning Kamp.
#
# See /usr/share/examples/etc/bsd-style-copyright for license terms.
#
# $FreeBSD: src/tools/tools/nanobsd/nanobsd.sh,v 1.1 2005/07/26 18:52:50 phk
Exp $
#
# Name of this NanoBSD build. (Used to construct workdir names)
NANO_NAME=uchman
NANO_SRC=/usr/src
NANO_PMAKE=make -j 4
# Options to put in make.conf during buildworld only
CONF_BUILD='
NO_HESIOD_LIBC=YES
NO_KLDLOAD=YES
NO_NETGRAPH=YES
NO_PAM=YES
PPP_NO_NETGRAPH=YES
PPP_NO_RADIOS=YES
'
# Options to put in make.conf during installworld only
CONF_INSTALL='
NO_ACPI=YES
NO_BLUETOOTH=YES
NO_CVS=YES
NO_CXX=YES
NO_DICT=YES
NO_FORTRAN=YES
NO_GCOV=YES
NO_GDB=YES
NO_HTML=YES
NO_LPR=YES
NO_MAN=YES
NO_OBJC=YES
NO_P1003_1B=YES
NO_PROFILE=YES
NO_SENDMAIL=YES
NO_SHAREDOCS=YES
NO_TOOLCHAIN=YES
NO_EXAMPLES=YES
NO_INSTALLLIB=YES
NO_CALENDAR=YES
NO_MISC=YES
#NO_SHARE=YES
NO_MAKE=YES
'
# Options to put in make.conf during both build- installworld.
CONF_WORLD='
NO_ATM=YES
NO_I4B=YES
NO_BIND=YES
NO_MODULES=YES
NO_IPFILTER=YES
NO_KERBEROS=YES
NO_NIS=YES
NO_RCMDS=YES
NO_GAMES=YES
NO_RESCUE=YES
PPP_NO_NETGRAPH=YES
PPP_NO_RADIUS=YES
NO_LOCALES=YES
NO_SYSCONS=YES
NO_GROFF=YES
NO_NLS=YES
NO_PCVT=YES
NO_IPX=YES
NO_INFO=YES
'
NANO_KERNEL=GW
FlashDevice Sandisk 512MB
NANO_IMAGES=2
NANO_CODESIZE=0
NANO_CONFSIZE=20480
NANO_DATASIZE=0
#customize_cmd cust_comconsole
customize_cmd cust_allow_ssh_root
customize_cmd cust_install_files
customize_cmd phk_pkg
phk_pkg () (
mkdir -p ${NANO_WORLDDIR}/Pkg
cp /usr/src/tools/tools/nanobsd/Pkg/* ${NANO_WORLDDIR}/Pkg
chroot ${NANO_WORLDDIR} sh -c 'pkg_add -v Pkg/*'
rm -rf ${NANO_WORLDDIR}/Pkg
)
machine i386
cpu I686_CPU
ident GW
# To statically compile in device wiring instead of /boot/device.hints
#hints GENERIC.hints # Default places to look for devices.
makeoptions DEBUG=-g# Build kernel with gdb(1) debug symbols
device pf
device pflog
device pfsync
device fdescfs
options ALTQ
options ALTQ_CBQ# Class Bases Queuing (CBQ)
options ALTQ_RED# Random Early Detection (RED)
options ALTQ_RIO# RED In/Out
options ALTQ_HFSC # Hierarchical Packet Scheduler (HFSC)
options ALTQ_PRIQ # Priority Queuing (PRIQ)
options ALTQ_NOPCC # Required for SMP build
#optionsSCHED_ULE # ULE scheduler
options SCHED_4BSD # 4BSD scheduler
options PREEMPTION # Enable kernel thread preemption
options INET# InterNETworking
options INET6 # IPv6 communications protocols
options FFS # Berkeley Fast Filesystem
options SOFTUPDATES # Enable FFS soft updates support
options UFS_ACL # Support for access control lists
options UFS_DIRHASH # Improve performance on big directories
options MD_ROOT # MD is a potential root device
options NFSCLIENT # Network Filesystem Client
options NFSSERVER # Network Filesystem Server
options NFS_ROOT# NFS usable as /, requires NFSCLIENT
options MSDOSFS # MSDOS Filesystem
options CD9660 # ISO 9660 Filesystem
options PROCFS # Process filesystem (requires PSEUDOFS)
options PSEUDOFS# Pseudo-filesystem framework
options GEOM_GPT# GUID Partition Tables.
options COMPAT_43 # Compatible with BSD 4.3 [KEEP THIS!]
options COMPAT_FREEBSD4 # Compatible with FreeBSD4
options COMPAT_FREEBSD5 # Compatible with FreeBSD5
options KTRACE # ktrace(1) support
options SYSVSHM # SYSV-style shared memory
options SYSVMSG # SYSV-style message queues
options SYSVSEM # SYSV-style semaphores
options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time
extensions
options KBD_INSTALL_CDEV# install
Re: 6.2 RELEASE - READ_DMA timed out
Pietro Cerutti wrote: On 1/14/07, Peter Ankerstål [EMAIL PROTECTED] wrote: ad0: FAILURE - READ_DMA timed out LBA=1000941 This kind of errors usually denote a hardware problem, either at the disk or at the controller level. Check sysutils/smartmontools in the ports. But there was no problem at all before the upgrade, and it works without any problem in safe mode and I have done fscks on the CF-card without any errors. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 6.2 RELEASE - READ_DMA timed out
On 1/14/07, Peter Ankerstål [EMAIL PROTECTED] wrote: ad0: FAILURE - READ_DMA timed out LBA=1000941 This kind of errors usually denote a hardware problem, either at the disk or at the controller level. Check sysutils/smartmontools in the ports. -- Pietro Cerutti ICQ: 117293691 PGP: 0x9571F78E - ASCII Ribbon Campaign - against HTML e-mail and proprietary attachments www.asciiribbon.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 6.2 RELEASE - READ_DMA timed out
On Sunday, 14. January 2007 16:27, Pietro Cerutti wrote: On 1/14/07, Peter Ankerstål [EMAIL PROTECTED] wrote: ad0: FAILURE - READ_DMA timed out LBA=1000941 This kind of errors usually denote a hardware problem, either at the disk or at the controller level. Check sysutils/smartmontools in the ports. This is not a hardware problem, this is Flash cards limitation- most of flash cards don't work with DMA at all. You should turn off DMA on every Flash card that is connected directly to IDE channel to boot up any operating system. I know there is some IDE2Flash adapters that can work with DMA but they are twice or even more expensive than el cheapo adapters most devices got. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 6.2 RELEASE - READ_DMA timed out
Peter Ankerstål wrote: Pietro Cerutti wrote: On 1/14/07, Peter Ankerstål [EMAIL PROTECTED] wrote: ad0: FAILURE - READ_DMA timed out LBA=1000941 This kind of errors usually denote a hardware problem, either at the disk or at the controller level. Check sysutils/smartmontools in the ports. But there was no problem at all before the upgrade, and it works without any problem in safe mode and I have done fscks on the CF-card without any errors. The reason it works in safe mode is that DMA is not used there. Are you sure it worked with DMA before ? DMA access on CF cards needs signal lines to the CF slot thats not always implemented, fx on older soekris boards. -Søren ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 6.2 RELEASE - READ_DMA timed out
The reason it works in safe mode is that DMA is not used there. Are you sure it worked with DMA before ? I cant be sure, I never looked it up. But it worked just fine before. The _only_ difference is the soruce-code i compiled NanoBSD from. I was RELENG_6_1 before and now it is RELENG_6_2 I'm using a IDE to CF-card adapter in a ordinary PC if that could be any help. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Dell 1955 Blade - Broadcom NIC not detected (BCM5708S)
Hello Dave ! Wed Nov 1 18:54:19 UTC 2006 Yes, the Linux bnx2 driver does support SerDes. I don't have the bandwidth to tackle this feature until after the first of the year, though a few other people have also considered looking into adding the support. Any news or status report regarding support for this new network interface in FreeBSD ? -- Med vennlig hilsen / Regards; Roar Pettersen Universitetet i Bergen - The University of Bergen Nygardsgt. 5 - N-5020 BERGEN - Norway Tlf: +47 55 58 40 55 VIP: 81503 fax: +47 55 58 40 70 [EMAIL PROTECTED] - IT-Avd, UiB - http://www.uib.no ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DRM disabled?
On Sun, 14 Jan 2007, Larry Rosenman wrote: Greetings, I finally have FreeBSD back on my HP ZE5700US Laptop. I was wondering if anyone knew why the DRM is being disabled. I have the agp device static in the kernel, and have attached a dmesg, as well as the X log, and also the full kernel config. kern/100958 has a patch that fixes this. I've sent a tickler to GNATS asking for an MFC. -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: ler@lerctr.org US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Source MAC addresses when bridge(4) used
On Sun, Jan 07, 2007 at 08:02:11AM +1100, Peter Jeremy wrote: I've just noticed an number of unpexected IP address changed MAC messages on one of the hosts in my network. It is connected via a FreeBSD bridge to the rest of my network (there aren't enuf network ports in my son's bedroom). The configuration looks like: +-+ +-+ | | | | | laptop1 |-| desktop |-- Rest of network | |dc0 tl0| |rl0 via dumb switch +-+ +-+ Chiming in late here after a nice holiday. Both hosts are running 6.1-STABLE: laptop1: FreeBSD laptop1.vk2pj.dyndns.org 6.1-STABLE FreeBSD 6.1-STABLE #0: Wed Nov 15 18:40:00 EST 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/laptop i386 desktop: FreeBSD jashank.vk2pj.dyndns.org 6.1-STABLE FreeBSD 6.1-STABLE #15: Wed Aug 2 18:35:57 EST 2006 ^^ This is actually fixed now in r1.84 and MFC'd early nov. The laptop would have been fine but the bridging was done on the desktop which was an older stable. The reason is that the arp reply when bridging sends the mac address of the nic where the request came in, so laptop1 will get the mac of tl0. The other problem that was fixed in r1.84 was that locally destined packets to the bridge were always broadcast when they shouldn't. Anything on the rest of the network arping for the rl0 address would cause the arp reply to also be sent to laptop1 (with rl0's address), hence the logged 'address moved' warnings. Some people pointed out that the address should be assigned to the bridge interface which is correct, but they way you had it still works and now that warning is now fixed. cheers, Andrew ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Firefox won't start on SPARC64
Hello all! I'm having a few problems with Firefox here on this box. As you can see, Thunderbird seems to work fine. But Firfox just exits with segmentation fault (Exit 139) - before anything is ever displayed. Is this a known problem or do I have to go looking by myself? I am currently running this: FreeBSD sunny.rz1.convenimus.net 6.2-PRERELEASE FreeBSD 6.2-PRERELEASE #0: Sat Jan 13 17:39:47 CET 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SUNNY sparc64 Has anyone else had this problem? Regards Chris ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DRM disabled?
On Sun, 14 Jan 2007 11:56:43 -0600 (CST) Larry Rosenman ler@lerctr.org mentioned: Greetings, I finally have FreeBSD back on my HP ZE5700US Laptop. I was wondering if anyone knew why the DRM is being disabled. I have the agp device static in the kernel, and have attached a dmesg, as well as the X log, and also the full kernel config. Ideas? For dri to work you should install recent Xorg (7.1 - 7.2) as drm on your card will not work with 6.9. You can find instructions how to obtain Xorg 7.2 featured ports tree on http://wiki.freebsd.org/. However, you might want to wait until Xorg modular will be committed into the tree. Hopefully, that will be done soon. -- Stanislav Sedov ST4096-RIPE pgpOLCgHBCfQr.pgp Description: PGP signature
Re: DRM disabled?
On Mon, 15 Jan 2007, Stanislav Sedov wrote: On Sun, 14 Jan 2007 11:56:43 -0600 (CST) Larry Rosenman ler@lerctr.org mentioned: Greetings, I finally have FreeBSD back on my HP ZE5700US Laptop. I was wondering if anyone knew why the DRM is being disabled. I have the agp device static in the kernel, and have attached a dmesg, as well as the X log, and also the full kernel config. Ideas? For dri to work you should install recent Xorg (7.1 - 7.2) as drm on your card will not work with 6.9. You can find instructions how to obtain Xorg 7.2 featured ports tree on http://wiki.freebsd.org/. However, you might want to wait until Xorg modular will be committed into the tree. Hopefully, that will be done soon. Actually, PR kern/100958 fixes the agpgart issue, and then the DRI stuff attaches and seems(!) to work. Can we get that PR commited? -- Stanislav Sedov ST4096-RIPE -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: ler@lerctr.org US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kernel panic on 6.2-RC2 with GENERIC.
On Mon, Jan 08, 2007 at 08:03:50AM +1030, Ian West wrote: On Sun, Jan 07, 2007 at 02:25:02PM -0500, Mike Tancsa wrote: At 11:43 AM 1/7/2007, Craig Rodrigues wrote: On Fri, Jan 05, 2007 at 06:59:10PM +0200, Nikolay Pavlov wrote: snip I have seen this identical fault with the new areca driver, my machine is opteron hardware, but running a regular i386/SMP kernel/world. With everything at 6.2RC2 (as of 29th of December) except the areca driver the machine is rock solid, with the 29th of december version of the areca driver the box will crash on extract of a large tar file, removal of a large directory structure, or pretty much anything that does a lot of disk io to different files/locations. There is no error log prior to seeing the following messages.. Dec 29 14:26:44 aleph kernel: g_vfs_done():da0s1g[WRITE(offset=433078272, length=8192)]error = 5 Dec 29 14:26:44 aleph kernel: g_vfs_done():da0s1g[WRITE(offset=433111040, length=16384)]error = 5 Dec 29 14:26:44 aleph kernel: g_vfs_done():da0s1g[WRITE(offset=433209344, length=16384)]error = 5 Dec 29 14:26:44 aleph kernel: g_vfs_done():da0s1g[WRITE(offset=433242112, length=32768)]error = 5 Dec 29 14:26:44 aleph kernel: g_vfs_done():da0s1g[WRITE(offset=437612544, length=4096)]error = 5 Dec 29 14:26:44 aleph kernel: g_vfs_done():da0s1g[WRITE(offset=437616640, length=12288)]error = 5 Dec 29 14:26:44 aleph kernel: g_vfs_done():da0s1g[WRITE(offset=437633024, length=6144)]error = 5 Dec 29 14:26:44 aleph kernel: g_vfs_done():da0s1g[WRITE(offset=437639168, length=2048)]error = 5 Dec 29 14:26:44 aleph kernel: g_vfs_done():da0s1g[WRITE(offset=437641216, length=6144)]error = 5 There are a string of these, followed by a crash and reboot. The file system state can be left very dirty to the point where background fsck seems unable to recover it. The areca card in question is running the latest firmware/boot and has shown no problems either before, or since backing out the areca driver. The volume is ran the tests on was a 250G on a raid6 raid set. I've had exactly the same issue on my arcmsr in a i386/SMP box. The card is in a 64bit/66Mhz slot running the lastest firmware and the kernel is recent. I triggered it by creating a large number of files (~10^3 to 10^4) using Samba. This caused similar errors on two volumes on a ~800GB RAID5 array. Turning off soft-updates cured the crash, but not the write errors. --Geoff ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
6.2 nvidia x11 driver: weird 16bpp/24bpp colorspace damage
Hi! I've just upgraded to 6.2 and found terrible bugs with nvidia x11 driver. Everything works (i.e. X starts, opengl works, no errors), but all colors are damaged terribly. It feels like graphics card is in 16 bpp mode, but X server thinks that it's in 24/32 bpp mode. Thus, value of blue channel is completely ignored. I use same driver version that I've used on 6.1, and I've recompiled driver with new kernel. I've also tried to recompile everything several time, tried bot nvidia and FreeBSD agp drivers, but nothing helped. nv driver shows correct colors, btw. Here's some additional info: # uname -a FreeBSD hades.panopticon 6.2-RELEASE FreeBSD 6.2-RELEASE #1: Mon Jan 15 04:59:29 MSK 2007 # pkg_info | grep nvidia-driver nvidia-driver-1.0.9631_1 (I can't try latest 97xx driver, as it says my GPU is no longer supported and I should stay with 96xx) # dmesg | grep nvidia nvidia0: GeForce3 mem 0xf200-0xf2ff,0xf400-0xf7ff,0xf380-0xf387 irq 16 at device 0.0 on pci1 nvidia0: [GIANT-LOCKED] From xorg.conf: Section Monitor Identifier Monitor0 VendorName RoverScan ModelNameMaxima Pro Black HorizSync31-80 VertRefresh 50-75 ModeLine 1280x1024_108 108.0 1280 1328 1440 1688 1024 1025 1028 1066 -hsync -vsync ModeLine 1280x1024_135 135.0 1280 1296 1440 1688 1024 1025 1028 1066 -hsync -vsync EndSection Section Device Identifier Card0 Driver nvidia VendorName nVidia Corporation BoardName NV20 [GeForce3] BusID PCI:1:0:0 Option RenderAccel true EndSection Section Screen Identifier Screen0 Device Card0 MonitorMonitor0 DefaultDepth 24 SubSection Display Depth 24 Modes 1280x1024_135 1280x1024_108 1024x768 800x600 640x480 640x400 EndSubSection EndSection -- Best regards, Dmitry Marakasov mailto:[EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD 6.2 Released
The FreeBSD Release Engineering Team is pleased to announce the availability of FreeBSD 6.2-RELEASE. This release continues the development of the 6-STABLE branch providing performance and stability improvements, many bug fixes and new features. Some of the highlights: - freebsd-update(8) provides officially supported binary updates for security fixes and errata patches - Experimental support for CAPP security event auditing - OpenBSM audit command line tool suite and library - KDE updated to 3.5.4, GNOME updated to 2.16.1 - csup(1) integrated cvsup client now included - Disk integrity protection and authentication added to geli(4) - New amdsmb(4), enc(4) ipmi(4), nfsmb(4), stge(4) drivers - IPFW(4) packet tagging - Linux emulation support for sysfs - BIND updated to 9.3.3 - Many driver updates including em(4), arcmsr(4), ath(4), bce(4), ata(4), and iwi(4) For a complete list of new features and known problems, please see the online release notes and errata list, available at: http://www.FreeBSD.org/releases/6.2R/relnotes.html http://www.FreeBSD.org/releases/6.2R/errata.html For more information about FreeBSD release engineering activities, please see: http://www.FreeBSD.org/releng/ Availability - FreeBSD 6.2-RELEASE is now available for the alpha, amd64, i386, ia64, pc98, powerpc, and sparc64 architectures. It can be installed from bootable ISO images or over the network; the required files can be downloaded via FTP or BitTorrent as described in the sections below. While some of the smaller FTP mirrors may not carry all architectures, they will all generally contain the more common ones, such as i386 and amd64. MD5 and SHA256 hashes for the release ISO images are included at the bottom of this message. The contents of the ISO images provided as part of the release has changed for most of the architectures. Using the i386 architecture as an example, there are ISO images named bootonly, disc1, disc2, and docs. The bootonly image is suitable for booting a machine to do a network based installation using FTP or NFS. The disc1 and disc2 images are used to do a full installation that includes a basic set of packages and does not require network access to an FTP or NFS server during the installation. In addition, disc1 supports booting into a live CD-based filesystem and system rescue mode. The docs image has all of the documentation for all supported languages. Most people will find that disc1 and disc2 are all that are needed. FreeBSD 6.2-RELEASE can also be purchased on CD-ROM from several vendors. Two of the vendors that will be offering FreeBSD 6.2-based products are: ~ FreeBSD Mall, Inc.http://www.freebsdmall.com/ ~ Daemonnews, Inc. http://www.bsdmall.com/freebsd1.html BitTorrent -- 6.2-RELEASE ISOs are available via BitTorrent. A collection of torrent files to download the images is available at: http://torrents.freebsd.org:8080/ FTP --- At the time of this announcement the following FTP sites have FreeBSD 6.2-RELEASE available. ftp://ftp.FreeBSD.org/pub/FreeBSD/ ftp://ftp3.FreeBSD.org/pub/FreeBSD/ ftp://ftp5.FreeBSD.org/pub/FreeBSD/ ftp://ftp7.FreeBSD.org/pub/FreeBSD/ ftp://ftp.at.FreeBSD.org/pub/FreeBSD/ ftp://ftp2.ch.FreeBSD.org/pub/FreeBSD/ ftp://ftp.cn.FreeBSD.org/pub/FreeBSD/ ftp://ftp.cz.FreeBSD.org/pub/FreeBSD/ ftp://ftp.ee.FreeBSD.org/pub/FreeBSD/ ftp://ftp2.fr.FreeBSD.org/pub/FreeBSD/ ftp://ftp2.ie.FreeBSD.org/pub/FreeBSD/ ftp://ftp2.ru.FreeBSD.org/pub/FreeBSD/ ftp://ftp.se.FreeBSD.org/pub/FreeBSD/ ftp://ftp1.tw.FreeBSD.org/pub/FreeBSD/ ftp://ftp2.uk.FreeBSD.org/pub/FreeBSD/ ftp://ftp5.us.FreeBSD.org/pub/FreeBSD/ ftp://ftp13.us.FreeBSD.org/pub/FreeBSD/ FreeBSD is also available via anonymous FTP from mirror sites in the following countries and territories: Argentina, Australia, Brazil, Bulgaria, Canada, China, Czech Republic, Denmark, Estonia, Finland, France, Germany, Hong Kong, Hungary, Iceland, Ireland, Israel, Japan, Korea, Latvia, Lithuania, the Netherlands, New Zealand, Poland, Portugal, Romania, Russia, Saudi Arabia, South Africa, Slovak Republic, Slovenia, Spain, Sweden, Taiwan, Thailand, Ukraine, and the United Kingdom. Before trying the central FTP site, please check your regional mirror(s) first by going to: ftp://ftp.yourdomain.FreeBSD.org/pub/FreeBSD Any additional mirror sites will be labeled ftp2, ftp3 and so on. More information about FreeBSD mirror sites can be found at: http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/mirrors-ftp.html For instructions on installing FreeBSD, please see Chapter 2 of The FreeBSD Handbook. It provides a complete installation walk-through for users new to FreeBSD, and can be found online at: http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/install.html
Re: FreeBSD 6.2 Released
Ken, At this moment newvers.h of RELENG_6: TYPE=FreeBSD REVISION=6.2 BRANCH=PRERELEASE Is that being corrected? Jack - Original Message - From: Ken Smith [EMAIL PROTECTED] To: freebsd-stable@freebsd.org Sent: Monday, January 15, 2007 6:26 AM Subject: FreeBSD 6.2 Released ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 6.2 Released
On Mon, 2007-01-15 at 06:54 +0100, Jack Raats wrote: Ken, At this moment newvers.h of RELENG_6: TYPE=FreeBSD REVISION=6.2 BRANCH=PRERELEASE Is that being corrected? Jack All set. -- Ken Smith - From there to here, from here to | [EMAIL PROTECTED] there, funny things are everywhere. | - Theodore Geisel | signature.asc Description: This is a digitally signed message part
Re: FreeBSD 6.2 Released
On Mon, Jan 15, 2007 at 06:54:06AM +0100, Jack Raats wrote: Ken, At this moment newvers.h of RELENG_6: TYPE=FreeBSD REVISION=6.2 BRANCH=PRERELEASE Is that being corrected? Jack I just did a cvsup against our local mirror, we pull from cvsup8.FreeBSD.org, and I got the correct file. It could be that you pulled from a repository that has not yet caught up. Try again. Josef -- Josef Grosch | Another day closer to a | FreeBSD 6.2 [EMAIL PROTECTED] | Micro$oft free world | Berkeley, Ca. pgpTFkLNXoqJw.pgp Description: PGP signature
