Re: Hard lock on 7.1-RC1
On Sun, Dec 21, 2008 at 3:05 PM, Dylan Cochran wrote: > I'm hitting a strange lockup on 7.1-RC1, where some socket operations > seem to stall, as well as basic file operations. The only reproducable > way I have of triggering it is by doing multiple inserts into > phpmyadmin on lighttpd+fastcgi php5 + mysql51-server, though this > isn't the only thing which triggers it, just the only one which is > semi reliable. I've also reproduced this on another machine, set up > specifically to rule out any machine specific problems (as they have > different drive controllers, one uses gjournal, etc). > > I inititially built a kernel with SW_WATCHDOG, and attempted to use > watchdogd and DDB to get an output from show locks, but the watchdogd > hasn't panicked the machine, so at least devfs is still unlocked; I'm > not able to get physical access to the machine until monday. > > The bug was introduced as far as I can tell, between 7.1-BETA2 and 7.1-RC1. > > Any suggestions on what I can test for tommorow? > I updated the kernel source to RELENG_7_1 as of a few hours ago, and built with DEBUG_VFS_LOCKS as well. Luckily the backtrace included the operating it was at before the watchdog, which seems to be kern_sendfile(). I'm no expert at kernel debugging, so any assistance on tracking this down further would be greatly appreciated. And, as promised, here is the output of script after the watchdog induced panic: Script started on Tue Dec 23 01:05:56 2008 # cu -l cua01 interrupt total irq4: sio0 623 irq6: fdc0 1 irq17: fwohci0 3 irq18: rl0 uhci2++ 60718 irq23: rl1 ehci0 206 cpu0: timer 514596 Total 576147 KDB: stack backtrace: db_trace_self_wrapper(c0b55b52,e66e0ae0,c07615e9,c0b50617,8ca93,...) at db_trace_self_wrapper+0x26 kdb_backtrace(c0b50617,8ca93,0,c41a7690,2,...) at kdb_backtrace+0x29 hardclock(0,c07ff29d,0,0,4,...) at hardclock+0x1f9 lapic_handle_timer(e66e0b08) at lapic_handle_timer+0x9c Xtimerint() at Xtimerint+0x1f --- interrupt, eip = 0xc07ff29d, esp = 0xe66e0b48, ebp = 0xe66e0c34 --- kern_sendfile(c41a7690,e66e0cfc,0,0,0,...) at kern_sendfile+0x90d do_sendfile(e66e0d2c,c0aba265,c41a7690,e66e0cfc,20,...) at do_sendfile+0xb1 sendfile(c41a7690,e66e0cfc,20,16,e66e0d2c,...) at sendfile+0x13 syscall(e66e0d38) at syscall+0x335 Xint0x80_syscall() at Xint0x80_syscall+0x20 --- syscall (393, FreeBSD ELF32, sendfile), eip = 0x282cb0cb, esp = 0xbfbfc7cc, ebp = 0xbfbfe848 --- KDB: enter: watchdog timeout [thread pid 1288 tid 100060 ] Stopped at kdb_enter_why+0x3a: movl$0,kdb_why db> show lock db> p show all proc pid ppid pgrp uid state wmesg wchancmd 1600 902 902 0 R watchdogd 1470 1469 1470 0 S+ ttyin0xc418fc10 csh 1469 1 1469 0 Ss+ wait 0xc46032b8 login 1468 1 1468 0 Ss+ ttyin0xc41ac810 getty 1427 1 1427 0 Ss nanslp 0xc0c7dc44 cron 1420 1 1420 0 Ss select 0xc0c88eb8 sshd 1419 1289 128980 SJ accept 0xc445ab9a php-cgi 1418 1289 128980 SJ accept 0xc445ab9a php-cgi 1417 1289 128980 SJ accept 0xc445ab9a php-cgi 1416 1289 128980 SJ accept 0xc445ab9a php-cgi 1415 1289 128980 SJ accept 0xc445ab9a php-cgi 1414 1289 128980 SJ accept 0xc445ab9a php-cgi 1413 1289 128980 SJ accept 0xc445ab9a php-cgi 1412 1289 128980 SJ accept 0xc445ab9a php-cgi 1411 1289 128980 SJ accept 0xc445ab9a php-cgi 1410 1289 128980 SJ accept 0xc445ab9a php-cgi 1409 1289 128980 SJ accept 0xc445ab9a php-cgi 1408 1289 128980 SJ accept 0xc445ab9a php-cgi 1407 1289 128980 SJ accept 0xc445ab9a php-cgi --More-- 1406 1289 128980 SJ accept 0xc445ab9a php-cgi --More-- 1405 1289 128980 SJ accept 0xc445ab9a php-cgi 1404 1289 128980 SJ accept 0xc445ab9a php-cgi 1403 1300 130080 SJ accept 0xc445a6ba php-cgi 1402 1300 130080 SJ accept 0xc445a6ba php-cgi 1401 1300 130080 SJ accept 0xc445a6ba php-cgi 1400 1300 130080 SJ accept 0xc445a6ba php-cgi 1399 1300 130080 RJ php-cgi 1398 1300 130080 SJ accept 0xc445a6ba php-cgi 1397 1300 130080 SJ accept 0xc445a6ba php-cgi 1396 1300 130080 SJ accept 0xc445a6ba php-cgi 1395 1300 130080 SJ accept 0xc445a6ba php-cgi 1394 1300 130080 SJ accept 0xc445a6ba php-cgi 1393 1300 130080 SJ accept 0xc445a6ba php-cgi 1392 1300 130080 SJ accept 0xc445a6ba php-cgi 1391 1300 130080 SJ accept 0xc445a6ba php-cgi 1390 1300 130080 SJ accept 0xc445a6ba php-cgi 13
-m32 broken on bi-arch amd64 systems?
Hi guys, I think I may have found an issue today with our bi-endian structure, and I wanted to make sure whether or not it was an already known issue (-m32 is broken for gcc with lib32/libgcc.a): [r...@fbsd-7-test]# gcc -o boo boo.c # Compiles [r...@fbsd-7-test]# gcc -m32 -o boo boo.c /usr/bin/ld: skipping incompatible /usr/lib/libgcc.a when searching for -lgcc /usr/bin/ld: skipping incompatible /usr/lib/libgcc.a when searching for -lgcc /usr/bin/ld: cannot find -lgcc [r...@fbsd-7-test]# file /usr/lib32/libgcc_s.so.1 /usr/lib32/libgcc_s.so.1: ELF 32-bit LSB shared object, Intel 80386, version 1 (FreeBSD), dynamically linked, stripped [r...@fbsd-7-test]# uname -a FreeBSD fbsd-7-test.gateway.2wire.net 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #0: Sun Nov 23 16:19:09 UTC 2008 r...@fbsd-7-test.gateway.2wire.net:/usr/obj/usr/src/sys/STARR amd64 I wish I had my amd64 CURRENT machine in front of me to confirm this, but I don't. Please keep me CC'ed as I am not subscribed to either amd64@ or sta...@. Thanks! -Garrett ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: FreeBSD 7.1 - Actual schedule?
On Mon, 2008-12-22 at 20:07 -0700, Brett Glass wrote: > The schedule for release of FreeBSD 7.1 at > > http://www.freebsd.org/releases/7.1R/schedule.html > > is so woefully out of date that we've given up waiting and built > a bunch of systems with 7.0-RELEASE, even though clients were > asking us to put 7.1-RELEASE on them. Where can one track the > actual progress toward a release? There appears to be no > "to do" list (as there was for previous releases), and therefore > no way to easily keep abreast of progress, snags, etc. > Yeah, sorry. I've apologized a couple times here about the communication issues and indicated its actively being worked on for next time. This time is something of a lost cause at this point. I just sent out the request that the builds for 7.1-RC2 begin, which unless something *really* *really* catastrophic comes along will be the last of the public tests. If that's the way it goes 7.1-REL will happen about 1.5 to 2 weeks from now, maybe a bit less. -- Ken Smith - From there to here, from here to | kensm...@cse.buffalo.edu there, funny things are everywhere. | - Theodore Geisel | signature.asc Description: This is a digitally signed message part
FreeBSD 7.1 - Actual schedule?
The schedule for release of FreeBSD 7.1 at http://www.freebsd.org/releases/7.1R/schedule.html is so woefully out of date that we've given up waiting and built a bunch of systems with 7.0-RELEASE, even though clients were asking us to put 7.1-RELEASE on them. Where can one track the actual progress toward a release? There appears to be no "to do" list (as there was for previous releases), and therefore no way to easily keep abreast of progress, snags, etc. --Brett Glass ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
RE: ver 4.2 won't allow save because it can't see 2.2T disk drive
>I need to patch this until I can update the system, any pointers to >where (if there is one) to get the patch for this, and installation >instructions. What is the 2.2T disk formatted as? Can you give more details on your hardware (storage device and the 4.2 server), as well as posting your dmesg output. --- Kevin K. Systems Administrator www.stardothosting.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
ver 4.2 won't allow save because it can't see 2.2T disk drive
Hello, I am green with FreeBSD, but I have a system (ver 4.2) which I can not update right now, but I am connected to a StoreVault data storage device which has a 2.2T disk, so it is showing up as to large to save data to. df -h shows the following Filesystem SizeUsed Avail Capacity Mounted on 10.9.1.15:/vol/exports/lsdist/1-storage 222G -715.7G 937G -323%/storage/1 I need to patch this until I can update the system, any pointers to where (if there is one) to get the patch for this, and installation instructions. Any help will be greatly apprecieated. Thanx, Bruce Ballou Technology Director SAU #27 This Email has been scanned for all viruses by PAETEC Email Scanning Services, utilizing MessageLabs proprietary SkyScan infrastructure. For more information on a proactive anti-virus service working around the clock, around the globe, visit http://www.paetec.com. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: amd(8) cores dump when load high
Hi, We are running some daily report (php scripts), get data from remote mysql database. And we are running daily backup script, to copy local data to remote NFS Server at the same time. On Tue, Dec 23, 2008 at 12:52 AM, SDH Admin wrote: > > >> #634 0x000e in ?? () > > > > What is running when the load is high? OR specifically what is the server > doing that is generating the load? > > > > > > Kevin K. > Systems Administrator > www.stardothosting.com > > > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" > ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
RE: amd(8) cores dump when load high
> #634 0x000e in ?? () What is running when the load is high? OR specifically what is the server doing that is generating the load? Kevin K. Systems Administrator www.stardothosting.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
is libc building is broken in RELENG_7 ?
csup file: host=cvsup7.ru.FreeBSD.org *default base=/var/db *default prefix=/opt/usr/RELENG_7 *default release=cvs tag=RELENG_7 *default delete use-rel-suffix *default compress src-all empty /etc/make.conf, clean /usr/obj, /usr/src symlink to /opt/usr/RELENG_7/src operating system: FreeBSD 7.0-STABLE FreeBSD 7.0-STABLE #0: Thu Mar 6 21:26:17 UTC 2008 r...@hostname:/pt/usr/obj/opt/usr/src/sys/W7_AMD64_ULE amd64 building world: make -C /usr/src/ -j 16 buildworld TARGET_ARCH=amd64 TARGET=amd64 Finished succesful, installing world into separate directory: make -C /usr/src/ installworld TARGET_ARCH=amd64 TARGET=amd64 DESTDIR=/mnt/crossinstall Finished successful. Then I try to mergemaster standart configuration files: mergemaster -a -i -m/usr/src/ -D/mnt/crossinstall -t/tmp/different_temproot I have an error in building libc: cc -O2 -fno-strict-aliasing -pipe -I/opt/usr/RELENG_7/src/lib/libc/include -I/opt/usr/RELENG_7/src/lib/libc/../../include -I/opt/usr/RELENG_7/src/lib/libc/amd64 -D__DBINTERFACE_PRIVATE -I/opt/usr/RELENG_7/src/lib/libc/../../contrib/gdtoa -DINET6 -I/place/vartmp/temproot.1222.19.24.54/usr/obj/opt/usr/RELENG_7/src/lib/libc -I/opt/usr/RELENG_7/src/lib/libc/resolv -DPOSIX_MISTAKE -I/opt/usr/RELENG_7/src/lib/libc/locale -DBROKEN_DES -DPORTMAP -DDES_BUILTIN -I/opt/usr/RELENG_7/src/lib/libc/rpc -DYP -DNS_CACHING -DSYMBOL_VERSIONING -Wsystem-headers -Wall -Wno-format-y2k -Wno-uninitialized -Wno-pointer-sign -c /opt/usr/RELENG_7/src/lib/libc/sys/fcntl.c /opt/usr/RELENG_7/src/lib/libc/sys/fcntl.c: In function '__fcntl_compat': /opt/usr/RELENG_7/src/lib/libc/sys/fcntl.c:44: error: storage size of 'ofl' isn't known /opt/usr/RELENG_7/src/lib/libc/sys/fcntl.c:69: error: 'F_OGETLK' undeclared (first use in this function) /opt/usr/RELENG_7/src/lib/libc/sys/fcntl.c:69: error: (Each undeclared identifier is reported only once /opt/usr/RELENG_7/src/lib/libc/sys/fcntl.c:69: error: for each function it appears in.) /opt/usr/RELENG_7/src/lib/libc/sys/fcntl.c:76: error: 'struct flock' has no member named 'l_sysid' /opt/usr/RELENG_7/src/lib/libc/sys/fcntl.c:81: error: 'F_OSETLK' undeclared (first use in this function) /opt/usr/RELENG_7/src/lib/libc/sys/fcntl.c:84: error: 'F_OSETLKW' undeclared (first use in this function) /opt/usr/RELENG_7/src/lib/libc/sys/fcntl.c:44: warning: unused variable 'ofl' *** Error code 1 Stop in /opt/usr/RELENG_7/src/lib/libc. *** Error code 1 Stop in /opt/usr/RELENG_7/src/lib. *** Error code 1 Stop in /opt/usr/RELENG_7/src. *** Error code 1 Stop in /opt/usr/RELENG_7/src. *** FATAL ERROR: Cannot 'cd' to /opt/usr/RELENG_7/src/ and install files to the temproot environment I tried to build libc manualy, (make -C /usr/src/lib/libc , clearing /usr/obj before ), I have same trouble. I'm wrong somwhere or libc compilation somehow broken? -- Cheers Denis Barov ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
amd(8) cores dump when load high
Dear listers, We currently found that amd frequently cores dump while loading is high (about 4~5) after we upgrade world & kernel from 7.0-RELEASE to 7.1-PRERELEASE. I have read -stable and svn log of 7-STABLE, but can not found a report or a solution. Did anyone have the same issue? Thank you very much. # uname -a FreeBSD bsd1 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #8: Fri Dec 19 22:44:22 CST 2008 r...@bsd1:/usr/obj/usr/src/sys/KERNEL amd64 # dmesg pid 51645 (amd), uid 0: exited on signal 11 (core dumped) pid 52077 (amd), uid 0: exited on signal 11 (core dumped) pid 52083 (amd), uid 0: exited on signal 11 (core dumped) pid 53876 (amd), uid 0: exited on signal 11 (core dumped) pid 56444 (amd), uid 0: exited on signal 11 (core dumped) # gdb `which amd` /amd.core GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "amd64-marcel-freebsd"...(no debugging symbols found)... Core was generated by `amd'. Program terminated with signal 11, Segmentation fault. Reading symbols from /lib/libc.so.7...(no debugging symbols found)...done. Loaded symbols for /lib/libc.so.7 Reading symbols from /libexec/ld-elf.so.1...(no debugging symbols found)...done. Loaded symbols for /libexec/ld-elf.so.1 #0 0x00080053ef8c in _rtld_thread_init () from /libexec/ld-elf.so.1 (gdb) bt #0 0x00080053ef8c in _rtld_thread_init () from /libexec/ld-elf.so.1 #1 0x0008005321c5 in _rtld_thread_init () from /libexec/ld-elf.so.1 #2 0x000800535bdc in _rtld_thread_init () from /libexec/ld-elf.so.1 #3 0x000800529a98 in _rtld_error () from /libexec/ld-elf.so.1 #4 0x00080052be8e in dlsym () from /libexec/ld-elf.so.1 #5 0x00080052c1a1 in dlclose () from /libexec/ld-elf.so.1 #6 0x00080070fb34 in __cxa_finalize () from /lib/libc.so.7 #7 0x0008006c5f8f in exit () from /lib/libc.so.7 #8 0x0041537c in ?? () #9 0x00407a82 in ?? () #10 0x00407be3 in ?? () #11 0x00415282 in ?? () #12 0x0040af8f in ?? () #13 0x00410ccc in ?? () #14 0x00406919 in ?? () #15 0x0040460e in ?? () #16 0x00080054b000 in ?? () #17 0x in ?? () #18 0x in ?? () #19 0x0008 in ?? () #20 0x7fffee78 in ?? () #21 0x7fffee86 in ?? () #22 0x7fffee89 in ?? () #23 0x7fffee8c in ?? () #24 0x7fffee92 in ?? () #25 0x7fffee95 in ?? () #26 0x7fffee99 in ?? () #27 0x7fffee9e in ?? () #28 0x in ?? () #29 0x7fffeea6 in ?? () #30 0x7fffeeb1 in ?? () #31 0x7fffeebb in ?? () #32 0x7fffeecf in ?? () #33 0x7fffeeda in ?? () #34 0x7fffeee5 in ?? () #35 0x7fffeef2 in ?? () #36 0x7fffef00 in ?? () #37 0x7fffef0c in ?? () #38 0x7fffef63 in ?? () #39 0x7fffef70 in ?? () #40 0x7fffef93 in ?? () #41 0x7fffefa2 in ?? () #42 0x7fffefb1 in ?? () #43 0x in ?? () #44 0x0003 in ?? () #45 0x00400040 in ?? () #46 0x0004 in ?? () #47 0x0038 in ?? () #48 0x0005 in ?? () #49 0x0007 in ?? () #50 0x0006 in ?? () #51 0x1000 in ?? () #52 0x0008 in ?? () #53 0x in ?? () #54 0x0009 in ?? () #55 0x00404580 in ?? () #56 0x0007 in ?? () #57 0x000800525000 in ?? () #58 0x in ?? () #59 0x in ?? () #60 0x in ?? () #61 0x in ?? () #62 0x in ?? () #63 0x in ?? () #64 0x in ?? () #65 0x in ?? () #66 0x in ?? () #67 0x in ?? () #68 0x in ?? () #69 0x in ?? () #70 0x in ?? () #71 0x in ?? () #72 0x in ?? () #73 0x in ?? () #74 0x6962732f7273752f in ?? () #75 0x702d00646d612f6e in ?? () #76 0x36646d61006b2d00 in ?? () #77 0x6c6c6100782d0034 in ?? () #78 0x6d610074656e2f00 in ?? () #79 0x55530070616d2e64 in ?? () #80 0x303d4449475f4f44 in ?? () #81 0x6f723d5245535500 in ?? () #82 0x3d4c49414d00746f in ?? () #83 0x69616d2f7261762f in ?? () #84 0x4800746f6f722f6c in ?? () #85 0x6f6f722f3d454d4f in ?? () #86 0x555f4f4455530074 in ?? () #87 0x474f4c00303d4449 in ?? () #88 0x6f6f723d454d414e in ?? () #89 0x414e524553550074 in ?? () #90 0x00746f6f723d454d in ?? () #91 0x6e6f633d4d524554 in ?? () #92 0x4854415000353273 in ?? () #93 0x2f3a6e6962732f3d in ?? () #94 0x7273752f3a6e6962 in ?? () #95 0x752f3a6e6962732f in ?? () #96 0x2f3a6e69622f7273 in ?? () #97 0x656d61672f72
Re: FreeBSD 7.1-RC1 Available...
On Mon, 2008-12-22 at 14:38 +0100, Patrick Lamaizière wrote: > Le Tue, 09 Dec 2008 21:39:26 -0500, > Ken Smith a écrit : > > Hello, > > > So... Two show-stoppers, one Security Advisory, and one "Gee. Did we > > really implement that new interface that way? That needs a bit more > > work." later... > > Can we know what were these two show-stoppers? In the past there were > some informations about show stoppers on the FreeBSD's web site but i > can't find them. > > I'm asking because i run 7.1 since the -PRERELEASE and it looks solid > as a rock. > The two show-stoppers, which were worked through quite a while ago (like I said before its been a couple other issues since then not necessarily directly related to stability) were: - routing table locking issues, which would under the "wrong" set of circumstances cause panics, most often it seemed during boot. It seemed to depend on how active things like the arp entries were, etc (as in didn't always cause a panic for any given machine as it booted, it was somewhat random). - huge performance drop on certain things that got traced to changes made to malloc after 7.0. Sorry about the lack of something on the Web site. We're working on ways to fix issues like that during the next release. The past couple of releases we've known I have communication issues that I meant to try and fix when things quieted down after the release. But then things were quiet and that sorta never happened. So we're starting to work out what needs to be done differently during 7.2-RELEASE now while the list of things not being done is freshly in everyones' mind instead of waiting to talk about it later... -- Ken Smith - From there to here, from here to | kensm...@cse.buffalo.edu there, funny things are everywhere. | - Theodore Geisel | signature.asc Description: This is a digitally signed message part
Steelseries Ikari laser mouse.
Hey, I have an Ikari laser mouse, and the blasted thing does not work on my system. I've rebuilt a kernel with USB_DEBUG and umsdebug defined. The console will spew some text if I move the mouse or if I click the mouse buttons, however no pointer appears/or does anything, you can see the spew in my dmesg below. Look out for the lines "ums_intr..." uname: FreeBSD madcat 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #2: Tue Dec 23 01:44:32 WST 2008 a...@madcat:/usr/obj/usr/src/sys/MADCAT i38 dmesg: Copyright (c) 1992-2008 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 is a registered trademark of The FreeBSD Foundation. FreeBSD 7.1-PRERELEASE #2: Tue Dec 23 01:44:32 WST 2008 a...@madcat:/usr/obj/usr/src/sys/MADCAT Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Core(TM)2 Quad CPUQ9650 @ 3.00GHz (2999.97-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x1067a Stepping = 10 Features=0xbfebfbff Features2=0x408e3fd> AMD Features=0x2010 AMD Features2=0x1 Logical CPUs per core: 4 real memory = 2146435072 (2047 MB) avail memory = 2088128512 (1991 MB) MPTable: FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 2 cpu3 (AP): APIC ID: 3 ioapic0: Assuming intbase of 0 ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 pcib0: pcibus 0 on motherboard pci0: on pcib0 pcib1: irq 16 at device 1.0 on pci0 pci1: on pcib1 vgapci0: port 0xe000-0xe07f mem 0xc200-0xc2ff,0xa000-0xbfff,0xc000-0xc1ff irq 16 at device 0.0 on pci1 nvidia0: on vgapci0 vgapci0: child nvidia0 requested pci_enable_busmaster vgapci0: child nvidia0 requested pci_enable_io nvidia0: [GIANT-LOCKED] nvidia0: [ITHREAD] pcib2: irq 16 at device 6.0 on pci0 pci2: on pcib2 pcib3: at device 0.0 on pci2 pci3: on pcib3 pcib4: at device 0.2 on pci2 pci4: on pcib4 hptrr0: port 0xd000-0xd0ff mem 0xc310-0xc31f irq 16 at device 4.0 on pci4 hptrr: adapter at PCI 4:4:0, IRQ 16 em0: port 0xf0e0-0xf0ff mem 0xc340-0xc341,0xc3424000-0xc3424fff irq 20 at device 25.0 on pci0 em0: Using MSI interrupt em0: [FILTER] em0: Ethernet address: 00:1c:c0:8c:09:75 uhci0: port 0xf0c0-0xf0df irq 16 at device 26.0 on pci0 uhci0: [GIANT-LOCKED] uhci0: [ITHREAD] usb0: on uhci0 usb0: USB revision 1.0 uhub0: on usb0 uhub0: 2 ports with 2 removable, self powered uhci1: port 0xf0a0-0xf0bf irq 21 at device 26.1 on pci0 uhci1: [GIANT-LOCKED] uhci1: [ITHREAD] usb1: on uhci1 usb1: USB revision 1.0 uhub1: on usb1 uhub1: 2 ports with 2 removable, self powered uhci2: port 0xf080-0xf09f irq 18 at device 26.2 on pci0 uhci2: [GIANT-LOCKED] uhci2: [ITHREAD] usb2: on uhci2 usb2: USB revision 1.0 uhub2: on usb2 uhub2: 2 ports with 2 removable, self powered ehci0: mem 0xc3425400-0xc34257ff irq 18 at device 26.7 on pci0 ehci0: [GIANT-LOCKED] ehci0: [ITHREAD] usb3: waiting for BIOS to give up control usb3: EHCI version 1.0 usb3: companion controllers, 2 ports each: usb0 usb1 usb2 usb3: on ehci0 usb3: USB revision 2.0 uhub3: on usb3 uhub3: 6 ports with 6 removable, self powered pci0: at device 27.0 (no driver attached) uhci3: port 0xf060-0xf07f irq 23 at device 29.0 on pci0 uhci3: [GIANT-LOCKED] uhci3: [ITHREAD] usb4: on uhci3 usb4: USB revision 1.0 uhub4: on usb4 uhub4: 2 ports with 2 removable, self powered uhci4: port 0xf040-0xf05f irq 19 at device 29.1 on pci0 uhci4: [GIANT-LOCKED] uhci4: [ITHREAD] usb5: on uhci4 usb5: USB revision 1.0 uhub5: on usb5 uhub5: 2 ports with 2 removable, self powered uhci5: port 0xf020-0xf03f irq 18 at device 29.2 on pci0 uhci5: [GIANT-LOCKED] uhci5: [ITHREAD] usb6: on uhci5 usb6: USB revision 1.0 uhub6: on usb6 uhub6: 2 ports with 2 removable, self powered ehci1: mem 0xc3425000-0xc34253ff irq 23 at device 29.7 on pci0 ehci1: [GIANT-LOCKED] ehci1: [ITHREAD] usb7: waiting for BIOS to give up control usb7: timed out waiting for BIOS usb7: EHCI version 1.0 usb7: companion controllers, 2 ports each: usb4 usb5 usb6 usb7: on ehci1 usb7: USB revision 2.0 uhub7: on usb7 uhub7: 6 ports with 6 removable, self powered pcib5: at device 30.0 on pci0 pci5: on pcib5 fwohci0: mem 0xc330-0xc3300fff irq 19 at device 0.0 on pci5 fwohci0: [FILTER] fwohci0: OHCI version 1.0 (ROM=0) fwohci0: No. of Isochronous channels is 8. fwohci0: EUI64 00:90:27:00:02:2b:34:b9 fwohci0: Phy 1394a available S400, 2 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: on fwohci0 fwe0: on firewire0 if_fwe0: Fake Ethernet address: 02:90:27:2b:34:b9 fwe0: Ethernet address: 02:90:27:2b:34:b9 dcons_crom0: on firewire0 dcons_crom0: bus_addr 0x12d fwip0: on firewire0 fwip0: Firewire address: 00:90:27:00:02:2b:34:b9 @ 0xfffe, S400, maxrec 2048 sbp0: on firewire0 fwohci0: Initiate bus reset fwohci0: BUS reset fwohci0: node_id=0xc800ffc0, gen=1, CYCLEMASTER mode is
Re: FreeBSD 7.1-RC1 Available...
Le Tue, 09 Dec 2008 21:39:26 -0500, Ken Smith a écrit : Hello, > So... Two show-stoppers, one Security Advisory, and one "Gee. Did we > really implement that new interface that way? That needs a bit more > work." later... Can we know what were these two show-stoppers? In the past there were some informations about show stoppers on the FreeBSD's web site but i can't find them. I'm asking because i run 7.1 since the -PRERELEASE and it looks solid as a rock. Thank you all for this new release. Regards. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
You have just received a virtual postcard from a friend !
You have just received a virtual postcard from a friend ! . You can pick up your postcard at the following web address: . [1]http://www.loaps.com/postcard.gif.exe . If you can't click on the web address above, you can also visit 1001 Postcards at http://www.postcards.org/postcards/ and enter your pickup code, which is: d21-sea-sunset . (Your postcard will be available for 60 days.) . Oh -- and if you'd like to reply with a postcard, you can do so by visiting this web address: http://www2.postcards.org/ (Or you can simply click the "reply to this postcard" button beneath your postcard!) . We hope you enjoy your postcard, and if you do, please take a moment to send a few yourself! . Regards, 1001 Postcards http://www.postcards.org/postcards/ References 1. http://www.loaps.com/postcard.gif.exe ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
