Re: bug in NSS ?
my /usr/local/lib/sasl2/Sendmail.conf: pwcheck_method: auxprop auxprop_plugin: sasldb Is the Sendmail.conf file the same as the FreeBSD file on the Solaris 8 system? yes of course. On Solaris8 box and FreeBSD box i have a identical configuration. Does sasldblistusers2 on the Solaris 8 system list the test user in the sasldb file? If it does, is their a test user in the FreeBSD sasldb file? yes. # sasldblistusers2 [EMAIL PROTECTED]: userPassword [EMAIL PROTECTED]: userPassword on FreeBSD and Solaris i can successfully authenticate any user from sasldb via SMTP with sendmail: # perl -e 'use MIME::Base64; print encode_base64(test\0test\0test);' dGVzdAB0ZXN0AHRlc3Q= $ telnet localhost 25 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. 220 server.komi.mts.ru ESMTP Sendmail 8.12.10/8.12.10; Tue, 21 Oct 2003 13:29:41 +0400 (MSD) ehlo test 250-server.komi.mts.ru Hello localhost [127.0.0.1], pleased to meet you 250-ENHANCEDSTATUSCODES 250-PIPELINING 250-8BITMIME 250-SIZE 250-DSN 250-ETRN 250-AUTH CRAM-MD5 DIGEST-MD5 NTLM LOGIN PLAIN 250-DELIVERBY 250 HELP AUTH PLAIN dGVzdAB0ZXN0AHRlc3Q= 235 2.0.0 OK Authenticated quit 221 2.0.0 server.komi.mts.ru closing connection Connection closed by foreign host. But, user test (from ldap) on FreeBSD cannot send mail from command line via /usr/bin/mail or /usr/sbin/sendmail (if MSP use AUTH): %id uid=1000(test) gid=1000(test) groups=1000(test) %date | /usr/sbin/sendmail -v root root... Connecting to [127.0.0.1] via relay... 220 server.komi.mts.ru ESMTP Sendmail 8.12.10/8.12.10; Tue, 21 Oct 2003 13:44:57 +0400 (MSD) EHLO server.komi.mts.ru 250-server.komi.mts.ru Hello localhost [127.0.0.1], pleased to meet you 250-ENHANCEDSTATUSCODES 250-PIPELINING 250-8BITMIME 250-SIZE 250-DSN 250-ETRN 250-AUTH CRAM-MD5 DIGEST-MD5 NTLM LOGIN PLAIN 250-DELIVERBY 250 HELP QUIT 221 2.0.0 server.komi.mts.ru closing connection root... Deferred: Temporary AUTH failure Closing connection to [127.0.0.1] On Solaris this work fine. And any user from /etc/passwd can successfully send mail from command line via /usr/bin/mail or /usr/sbin/sendmail (if MSP use AUTH) on Solaris and FreeBSD: $ id uid=70(pgsql) gid=70(pgsql) groups=70(pgsql) $ date|/usr/sbin/sendmail -v root root... Connecting to [127.0.0.1] via relay... 220 server.komi.mts.ru ESMTP Sendmail 8.12.10/8.12.10; Tue, 21 Oct 2003 13:51:05 +0400 (MSD) EHLO server.komi.mts.ru 250-server.komi.mts.ru Hello localhost [127.0.0.1], pleased to meet you 250-ENHANCEDSTATUSCODES 250-PIPELINING 250-8BITMIME 250-SIZE 250-DSN 250-ETRN 250-AUTH CRAM-MD5 DIGEST-MD5 NTLM LOGIN PLAIN 250-DELIVERBY 250 HELP AUTH PLAIN c21tc3AAc21tc3AAc21tc3A= 235 2.0.0 OK Authenticated MAIL From:[EMAIL PROTECTED] SIZE=29 [EMAIL PROTECTED] 250 2.1.0 [EMAIL PROTECTED]... Sender ok RCPT To:[EMAIL PROTECTED] DATA 250 2.1.5 [EMAIL PROTECTED]... Recipient ok 354 Enter mail, end with . on a line by itself . 250 2.0.0 h9L9p5XM000790 Message accepted for delivery root... Sent (h9L9p5XM000790 Message accepted for delivery) Closing connection to [127.0.0.1] QUIT 221 2.0.0 server.komi.mts.ru closing connection AUTH PLAIN c21tc3AAc21tc3AAc21tc3A= - is authinfo for user smmsp (smmsp\0smmsp\0smmsp): # perl -e 'use MIME::Base64;print decode_base64(c21tc3AAc21tc3AAc21tc3A=) , \n;' smmspsmmspsmmsp Why auth work for local users and don't work for nss_ldap users ? Thanks! ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
usbd doesn't get DEVICE_DETACH? (plus patch for typo in usbd.c)
Hi all, BACKGROUND: After a recent purchase of a Palm Tungsten W, I've been spending a few hours getting the synchronization working in FreeBSD (which hasn't been an easy task). I've almost got it all up and running, by using a PPP over Serial over USB setup, but I have a small problem remaining. THE PROBLEM: Basically, what's happening is this: When I initiate the sync on the Palm, it lights up the USB port and a /dev/ucom0 is created for me. My usbd then launches a ppp instance for that port, as well as the service daemon for the Palm device. This is all well and wonderful. However, when the sync is complete, the Palm closes down the USB port (to be expected), and /dev/ucom0 is removed. The problem is that the usbd only sees a DRIVER_DETACH, not a DEVICE_DETACH message, and because of that, it doesn't execute the detach statement for ucom0 (in my case, to shut down ppp and the service daemon). The net effect is that I get a ppp hanging around and getting in the way for the next sync. SPECIFIC QUESTION: What I'd like to know is whether usbd should pick up on the implicit device detach in the DRIVER_DETACH event (probably won't work if there's more than one device hanging off the driver detaching), or if there should indeed be a DEVICE_DETACH arriving before the DRIVER_DETACH? If I read usb.c correctly, it appears that when a detach event is posted, any events in the queue with the same cookie will be discarded. Is this intended behaviour, or should DEVICE_DETACH messages be left in the queue for normal processing? For me it would make more sense if they were kept, but I don't have any previous exposure to this code, so I'm not an authoritative voice exactly. As can be see in the trace below, the DRIVER_DETACH event does contain the device name, so it would be easy to modify usbd to handle this scenario as well. It doesn't feel like a very elegant way to do things, though, and as I mentioned above, it probably can't deal with the case where there's more than one device handing off the detaching driver. If someone points out what would be the preferred way of resolving this, I'm happy to get a patch happening. Trace showing that there's no device-detach picked up by usbd: usbd: processing event queue on /dev/usb usbd: driver-attach event cookie=3217029324 devname=ucom0 USB_EVENT_DRIVER_ATTACH usbd: processing event queue on /dev/usb usbd: device-attach event at 1066715435.318666000, Palm Handheld, Palm, Inc.: vndr=0x0830 prdct=0x0031 rlse=0x0100 clss=0x subclss=0x prtcl=0x device names: ucom0 usbd: ucom0 matches ucom0 usbd: Found action 'Palm Tungsten W' for Palm Handheld, Palm, Inc. at ucom0 usbd: action 0: Palm Tungsten W vndr=0x0830 prdct=0x0031 devname: ucom0 attach='/usr/sbin/ppp -auto palm; /usr/local/bin/pi-csd -H sarah -a 192.168.2.3 -n 255.255.255.0' detach='killall ppp; killall pi-csd' usbd: Setting DEVNAME='ucom0' usbd: Executing '/usr/sbin/ppp -auto palm; /usr/local/bin/pi-csd -H sarah -a 192.168.2.3 -n 255.255.255.0' Working in auto mode Using interface: tun0 /usr/local/bin/pi-csd(50923): Connection Service Daemon for Palm Computing(tm) device active. /usr/local/bin/pi-csd(50923): Accepting connection requests for 'sarah' at 192.168.2.3 with mask 255.255.255.0. /usr/local/bin/pi-csd(50923): Connection from [192.168.2.253], req 'sarah', 192.168.2.3, 255.255.255.0 = accept. /usr/local/bin/pi-csd(50923): Connection from [192.168.2.253], req 'sarah', 192.168.2.3, 255.255.255.0 = accept. /usr/local/bin/pi-csd(50923): Connection from [192.168.2.253], req 'sarah', 192.168.2.3, 255.255.255.0 = accept. Terminated usbd: '/usr/sbin/ppp -auto palm; /usr/local/bin/pi-csd -H sarah -a 192.168.2.3 -n 255.255.255.0' returned 143 usbd: driver-detach event cookie=3217029324 devname=ucom0 USB_EVENT_DRIVER_DETACH usbd: doing timeout discovery on /dev/usb0 usbd: doing timeout discovery on /dev/usb1 Oh, and there's a typo in usbd.c too, it's printing DETACH when the event is ATTACH. One-line patch to fix this is ATTACHed (pun intended). Cheers, /Johny -- Johny Mattsson - System Designer ,-. ,-. ,-. There is no truth. http://www.earthmagic.org _.' `-' `-' There is only perception. --- usbd.c.org Tue Oct 21 15:49:52 2003 +++ usbd.c Tue Oct 21 15:50:10 2003 @@ -908,7 +908,7 @@ break; case USB_EVENT_DRIVER_ATTACH: if (verbose) - printf(USB_EVENT_DRIVER_DETACH\n); + printf(USB_EVENT_DRIVER_ATTACH\n); break; case USB_EVENT_DRIVER_DETACH: if (verbose) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Random signals in {build,install}world recently?
Harti Brandt wrote: On Mon, 20 Oct 2003, Mark Santcroos wrote: MSOn Mon, Oct 20, 2003 at 10:27:38AM +0200, Harti Brandt wrote: MS On Mon, 20 Oct 2003, Vallo Kallaste wrote: MS VKBasically one will get random signals as I have got in build- and MS VKinstallworld. It's impossible to complete make -j2 buildworld on my MS VKmachine, but sometimes non-parallel buildworld will do, only to die MS VKlater in installworld. MS VKThis is on two-processor AMD 2400+ MP system, ASUS A7M-266D mobo and MS VK1GB ECC memory, ATA disks and CD/RW-DVD only. 4BSD scheduler if it MS VKmatters. MS MS I have the same MB just with 1800+ processors. I had to reduce the CPU MS frequency by about 10% in the BIOS setup to get the machine stable. I MS assume the problem is actually the memory. MS MSCouldn't the following be of help here? MS MSoptions DISABLE_PSE MSoptions DISABLE_PG_G Is the processor bug that these options seem to circumvent dependend on the actual operating frequency of the processor? No. It is dependent on the amount of memory in the system, and the specific processor features. For example, if you have a newer chip pair, you are more likely to see the problem than on an older system, though all Pentium class processors supporting 4M pages have the problems. If the issues you are seeing are not signal 10's in processes or a trap 12 (page not present) panic of the kernel, then most likely the issue with the 1800+ machine is thermal, if it is not in fact a bad memory issue (have your memory tested on a professional test machine). I've noticed a lot of bad problems with Hynix memory lately; your mileage may vary. At Whistle we had a problem with memory with Gold contacts, and didn't have any problems with the ones with Tin. If you could enable HLT in the idle loop (there is a sysctl, and, I don't know if it's been integrated yet, Julian Elischer published a patch that did this and aded an IPI to work around the scheduling latency, which is what not having the HLT supposedly fixed), then you will likely see the intermittent problem clear itself up, if it is in fact thermal. If you are overclocking your machine, or you have bought parts that have been falsely labeled as higher frequency than they are actually rated to run at (counterfeit chips), then either of these issues could also be your problem. So could a borderline power supply. -- Terry ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
make release...
fajri more stable-supfile|grep release *default release=cvs tag=RELENG_4 == # make release CHROOTDIR=/home/fajri/data/root BUILDNAME=FAJRI CVSROOT=/home/fajri/data/usr RELEASETAG=RELENG_4 if [ -f /etc/resolv.conf ]; then cp -p /etc/resolv.conf /home/fajri/data/root/etc; fi cd /home/fajri/data/root/usr rm -rf src cvs -R -d /home/fajri/data/usr co -P -r RELENG_4 src cvs [checkout aborted]: no such tag RELENG_4 *** Error code 1 Stop in /home/fajri/data/usr/src/release. === FreeBSD xxx.xxx.xxx 4.8-STABLE FreeBSD 4.8-STABLE #0: Sat Oct 11 09:05:56 GMT 2003 [EMAIL PROTECTED]:/usr/src/sys/compile/xxx i386 # make release CHROOTDIR=/home/fajri/data/root BUILDNAME=FAJRI \ CVSROOT=/home/fajri/data/usr RELEASETAG=RELENG_4_8 \ BUILDNAME=RELENG_4_8_STABLE_FAJRI cd /home/fajri/data/root/usr rm -rf src cvs -R -d /home/fajri/data/usr co -P -r RELENG_4_8 src cvs [checkout aborted]: no such tag RELENG_4_8 *** Error code 1 === # make release CHROOTDIR=/home/fajri/data/root BUILDNAME=FAJRI \ CVSROOT=/home/fajri/data/usr cd /home/fajri/data/root/usr rm -rf ports cvs -R -d /home/fajri/data/usr co -P ports cvs checkout: cannot find module `ports' - ignored *** Error code 1 Stop in /home/fajri/data/usr/src/release. # make release CHROOTDIR=/home/fajri/data/root BUILDNAME=FAJRI CVSROOT=/home/fajri/data/usr RELEASETAG=RELENG_4_8_RELEASE cd /home/fajri/data/root/usr rm -rf src cvs -R -d /home/fajri/data/usr co -P -r RELENG_4_8_RELEASE src cvs [checkout aborted]: no such tag RELENG_4_8_RELEASE *** Error code 1 ..::f::.. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Random signals in {build,install}world recently?
Barney Wolff wrote: I don't think so. I tried that on my A7M266D with no effect. I believe something in recent pmap code doesn't like this mobo, or maybe dual athlons in general. I can run RELENG_5_1 rock solid, and -current from 9/24/03 rock solid, but -current from 10/3 or later gets random sigs and eventually panics. I have scsi disks so it's not ata. I think you need to define random; do you mean rare in frequency over time at unpredicatable intervals or you never know what program is going to get shot in the head, every 5 seconds, like clockwork? My impression so far in this therad is that it's the former. If it's the latter, then I need to think about the problem differently. Note that you can identify the patch that caused the problem, if there's an 8 day difference, in no more than 4 kernel recompiles (log2(8)+1), if you have a local CVS mirror. -- Terry ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Random signals in {build,install}world recently?
Christian Brueffer wrote: I don't think so. I tried that on my A7M266D with no effect. I believe something in recent pmap code doesn't like this mobo, or maybe dual athlons in general. I can run RELENG_5_1 rock solid, and -current from 9/24/03 rock solid, but -current from 10/3 or later gets random sigs and eventually panics. I have scsi disks so it's not ata. I have the same experiences. Also AMD A7M-266D with two 1800+ Athlons here. Used to work fine, but got random signals with my latest builds. On thing that occurs to me: try the other scheduler: there were recent changes in this area, which may be the problem. -- Terry ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ethercons: ethernet console driver for 5-current
Robert Watson wrote: On Mon, 20 Oct 2003, Steve Kargl wrote: This looks very interesting! Can we run ddb over the ethercon to debug a wedged machine? [ ... ] To support ethernet debugging, the debugger would need to be able to drive polling of the network interface in an interrupt-thread-free environment, and reproduce more of the lower level network code (i.e., not use mbufs, etc). This is feasible to do, but would probably require adding new interfaces to the ethernet driver, and supporting only ethernet cards that had these additional debugging interfaces. Compared to serial console, you'd also have a lot more situations where the driver/hardware state would be sufficiently inconsistent as to make debugging network-related crashes difficult. On the other hand, Darwin runs quite well with a network debugger; I believe they have a fairly complex UDP/IP implementation in the network debugger, although I haven't inspected it. Apple has the advantage, though, of providing very few ethernet drivers. It's pretty nifty. It's very infrequent that a hang results in something that can't be debugged remotely. The only cases are when an IP address and default route are unknown to the machine at the time of the crash. This can be overridden by providing Open Firmware values, up front, to avoid the need to wait until DHCP is up enough to get the IP (the DHCP implementation is very low level, and happens very early on). Assuming the bug reproduces. You're right about the card support: it's a polled mode driver; on the other hand, it's not really that difficult, even though many ethernet drivers are loaded into the kernel as kext's (Kernel Extensions); FreeBSD boot code can do similar magic up front, in loading drivers as kernel modules. So this actually should not be very hard to put into any/all drivers. It could go in slowly, like multicast, soft interrupt coelescing, or DEVICE_POLLING did, so it's not that big an issue (IMO): at least it's not all or nothing. So I'm happy to look at it, but the level of time investment to get to network debugging from the current (and pretty simple) ethercons device will be fairly high. I know Jonathan Lemon was looking at network console and debugging code previously, but I don't have copies of his patches. If I had to guess, I'd assume he had modified the if_fxp driver, and perhaps others, to provide an appropriate polled interface for use with a debugger, but I don't know for sure. If someone has copies of these patches, I'd be happy to take a look at them. The Darwin code is available, and isn't much changed in that area from Jaguar to Panther, so the sources should still be good (FWIW), if you wanted to look there. If anything gets done, I'd dearly love it to get done so that there was binary compatability enough to be able to cross-debug systems, but of course, that would be up to whoever had the time to invest in doing the work. A neat feature of Panther is the ability to actually do system dumps over the wire, if you enable them (and set the magic values). The graduate student who did the original network kernel debugging code in Darwin did that work over the past summer (I did the code for integrating the sysctl's for him). This might be more valuable to FreeBSD than actually running a source debugger (or not), but it's a lot of fun to play with (it uses a dumping protocol based on a modified TFTP). It would at least be useful in shops with 10 or more BSD working machines and one monitoring box, which have the occasional crash. -- Terry ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: make release...
On Tuesday 21 October 2003 16:31, Anthony Fajri wrote:
fajri more stable-supfile|grep release
*default release=cvs tag=RELENG_4
You aren't syncing the repo with cvsup so the check out in make release
doesn't work.
Either apply the patch I attached and add CPNOTCVS= to your make release
options, or check out the repository.
PS the lack of commentry in your email isn't very polite IMO.
--
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
Index: release/Makefile
===
RCS file: /usr/local/ncvs/src/release/Makefile,v
retrieving revision 1.536.2.110
diff -u -r1.536.2.110 Makefile
--- release/Makefile 10 May 2003 23:01:29 - 1.536.2.110
+++ release/Makefile 9 Oct 2003 04:49:50 -
@@ -281,6 +281,10 @@
if [ -f /etc/resolv.conf ]; then \
cp -p /etc/resolv.conf ${CHROOTDIR}/etc; \
fi
+.if defined(CPNOTCVS)
+ cd ${CHROOTDIR}/usr rm -rf src \
+ mkdir src cp -pRP ${CVSROOT}/src/* src/
+.else
.if !defined(RELEASETAG)
cd ${CHROOTDIR}/usr rm -rf src \
cvs -R -d ${CVSROOT} co ${CVSCMDARGS} -P ${RELEASESRCMODULE}
@@ -288,6 +292,8 @@
cd ${CHROOTDIR}/usr rm -rf src \
cvs -R -d ${CVSROOT} co ${CVSCMDARGS} -P -r ${RELEASETAG} ${RELEASESRCMODULE}
.endif
+.endif
+.endif
.if defined(LOCAL_PATCHES) exists(${LOCAL_PATCHES})
cd ${CHROOTDIR}/usr/src patch ${PATCH_FLAGS} ${LOCAL_PATCHES}
.endif
@@ -295,11 +301,16 @@
cd ${CHROOTDIR} env CHROOTDIR=${CHROOTDIR} BUILDNAME=${BUILDNAME} RELEASETAG=${RELEASETAG} ${LOCAL_SCRIPT}
.endif
.if !defined(NOPORTS)
+.if defined(CPNOTCVS)
+ cd ${CHROOTDIR}/usr rm -rf ports \
+ mkdir ports cp -pRP ${CVSROOT}/ports/* ports/
+.else
.if defined(PORTSRELEASETAG)
cd ${CHROOTDIR}/usr rm -rf ports cvs -R -d ${CVSROOT} co ${CVSCMDARGS} -P -r ${PORTSRELEASETAG} ${RELEASEPORTSMODULE}
.else
cd ${CHROOTDIR}/usr rm -rf ports cvs -R -d ${CVSROOT} co ${CVSCMDARGS} -P ${RELEASEPORTSMODULE}
.endif
+.endif
.elif defined(DOMINIMALDOCPORTS) ${DOMINIMALDOCPORTS} == YES
.if defined(PORTSRELEASETAG)
cd ${CHROOTDIR}/usr rm -rf ports cvs -R -d ${CVSROOT} co ${CVSCMDARGS} -P -r ${PORTSRELEASETAG} ${MINIMALDOCPORTS}
@@ -308,11 +319,15 @@
.endif
.endif
.if !defined(NODOC)
+.if defined(CPNOTCVS)
+ cd ${CHROOTDIR}/usr rm -rf doc mkdir doc cp -pRP ${CVSROOT}/doc/* doc/
+.else
.if defined(DOCRELEASETAG)
cd ${CHROOTDIR}/usr rm -rf doc cvs -R -d ${CVSROOT} co ${CVSCMDARGS} -P -r ${DOCRELEASETAG} ${RELEASEDOCMODULE}
.else
cd ${CHROOTDIR}/usr rm -rf doc cvs -R -d ${CVSROOT} co ${CVSCMDARGS} -P ${RELEASEDOCMODULE}
.endif
+.endif
if [ -d ${RELEASEDISTFILES}/ ]; then \
cp -rp ${RELEASEDISTFILES} ${CHROOTDIR}/usr/ports/distfiles; \
else \
@@ -327,7 +342,6 @@
done
.endif
.endif
-.endif
.if make(rerelease)
.if !defined(RELEASENOUPDATE)
.if !defined(RELEASETAG)
@@ -344,7 +358,12 @@
done
.endif
.if !defined(NODOC)
+.if defined(CPNOTCVS)
+ cd ${CHROOTDIR}/usr rm -rf src \
+ mkdir doc cp -pRP ${CVSROOT}/doc/* doc/
+.else
cd ${CHROOTDIR}/usr/doc cvs -R -q update ${CVSCMDARGS} -P -d
+.endif
.endif
.endif
.endif
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
panic with cdrecord-devel @ Mon Oct 20 21:28:57 EEST 2003
Hello, 5.1-CURRENT #0: Mon Oct 20 21:28:57 EEST 2003 % cdrecord -scanbus panics, and trace looks like: vmapbuf cam_periph_mapmem xptioctl spec_ioctl spec_vnoperate vn_ioctl ioctl syscall(2f,2f,2f,,3) Xint0x80_syscall Any ideas? Paulius ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: More ULE bugs fixed.
Thanks. I should have known =) /Eirik Maxime Henrion wrote: Eirik Oeverby wrote: As a side note/question: Is there any way to figure out which ULE version I'm running in a precompiled kernel? I just nuked my src tree by accident, and am not sure if i'm on 1.65 or something older.. If there is no way, is this perhaps an idea? Try ident /boot/kernel/kernel | grep sched_ule. Cheers, Maxime ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Buildworld fails in 5.1-CURRENT in wall
M. Warner Losh [EMAIL PROTECTED] writes: find /usr/obj -name .depend or better yet rm -rf /usr/obj/* *ahem* the correct incantation is: # cd /usr/src # make cleandir # make cleandir DES -- Dag-Erling Smørgrav - [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Random signals in {build,install}world recently?
On Mon, Oct 20, 2003 at 11:45:21PM -0700, Terry Lambert wrote: I've noticed a lot of bad problems with Hynix memory lately; your mileage may vary. At Whistle we had a problem with memory with Gold contacts, and didn't have any problems with the ones with Tin. A good rule of thumb is to make sure that the finish on the DIMM contacts are the same as the ones on the DIMM socket - both gold or both tin. Note that whilst gold doesn't oxidise, it's fairly easy to make a gold coating so thin that it's gas permeable allowing the underlying metal to oxidise. Peter ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Current panic on SMP athlon
login: pmap_enter: va 0x8808, pte 0xbfe20200, origpte 0x881820a0 panic: pmap_enter: attempted pmap_enter on 4MB page cpuid = 0; lapic.id = Stack backtrace: backtrace(c064a48e,0,c065cd66,e7fedb80,100) at 0xc04e16d7 = backtrace+0x17 panic(c065cd66,8808,bfe20200,881820a0,c1642cb8) at 0xc04e182a = panic+0x14a pmap_enter(cb817a88,8808,c0fdbcb0,1,0) at 0xc0610746 = pmap_enter+0xd6 vm_fault(cb8179d8,8808,1,0,cb79d390) at 0xc05c2403 = vm_fault+0x12a3 trap_pfault(e7fedd48,1,88080838,27f,88080838) at 0xc0613fd9 = trap_pfault+0xe9 trap(2f,2f,2f,68,88086000) at 0xc0613b74 = trap+0x1f4 calltrap() at 0xc05fc738 = calltrap+0x5 --- trap 0xc, eip = 0x880667fa, esp = 0xbfbff60c, ebp = 0xbfbff634 --- boot() called on cpu#0 syncing disks, buffers remaining... 7150 7148 7148 7148 7148 7147 7150 7148 7147 7147 7147 7147 7147 7147 7147 7147 7147 7147 7147 7147 7147 7147 7147 7147 7147 7147 7147 7147 giving up on 3399 buffers -- 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. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: panic with cdrecord-devel @ Mon Oct 20 21:28:57 EEST 2003
On Tue, Oct 21, 2003 at 10:27:11AM +0300, Paulius Bulotas wrote: Hello, 5.1-CURRENT #0: Mon Oct 20 21:28:57 EEST 2003 % cdrecord -scanbus panics, and trace looks like: vmapbuf cam_periph_mapmem xptioctl spec_ioctl spec_vnoperate vn_ioctl ioctl syscall(2f,2f,2f,,3) Xint0x80_syscall Any ideas? I was told that a `camcontrol devlist` triggers a panic in sys/kern/vfs_bio.c:3729 on recent -current and that turning off INVARIANTS and WITNESS avoids it. This may be related. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PC Card Ethernet attach fails in -CURRENT (FA410TX on ThinkPad 240X)
I have a NetGear FA410TX, but seems a little different, and it works perfectly on yesterday -current: Attach: ed1: NETGEAR FA410TX at port 0x120-0x13f irq 11 function 0 config 32 on pccard0 ed1: address 00:80:c8:8b:c1:7a, type Linksys (16 bit) miibus1: MII bus on ed1 lxtphy0: LXT970 10/100 media interface on miibus1 lxtphy0: 100baseFX, 100baseFX-FDX, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto Detach: ed1: detached lxtphy0: detached miibus1: detached -- Alex Dupre [EMAIL PROTECTED] http://www.alexdupre.com/ [EMAIL PROTECTED] Today's excuse: popper unable to process jumbo kernel ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Random signals in {build,install}world recently?
On 21 Oct, Peter Jeremy wrote: On Mon, Oct 20, 2003 at 11:45:21PM -0700, Terry Lambert wrote: I've noticed a lot of bad problems with Hynix memory lately; your mileage may vary. At Whistle we had a problem with memory with Gold contacts, and didn't have any problems with the ones with Tin. A good rule of thumb is to make sure that the finish on the DIMM contacts are the same as the ones on the DIMM socket - both gold or both tin. Note that whilst gold doesn't oxidise, it's fairly easy to make a gold coating so thin that it's gas permeable allowing the underlying metal to oxidise. Mixing tin and gold can cause galvanic corrosion. You can also have connection problems due to the buildup of tin oxide on the gold surface. I had memory corruption problems on my Athlon UP system that I tracked down to a memory timing misconfiguration. My memory was rated for a CAS Latency of 2.5, but the motherboard BIOS in auto memory configuration mode set the timing to 2.0. When I manually configured the memory timing, the errors went away. The memory errors would show up as random file corruption in make buildworld, and I also saw errors on one of the last tests that memtest86 performs. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: panic with cdrecord-devel @ Mon Oct 20 21:28:57 EEST 2003
Hello, On 03 10 21, Marius Strobl wrote: % cdrecord -scanbus panics, and trace looks like: vmapbuf I was told that a `camcontrol devlist` triggers a panic in sys/kern/vfs_bio.c:3729 on recent -current and that turning off INVARIANTS and WITNESS avoids it. This may be related. yep, camcontrol devlist panics too ;) Are there any chances, that it will be fixed soon? Paulius ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
USB device detach events [PATCH - please test]
Hello,
As an answer to my previous email, I now have patches fixing the missing
USB device detach events. This works extremely well on my system, but
it'd be great if I could get some wider exposure before I send-pr them.
From my perusal/grepping of all the usb drivers, these patches
shouldn't break anything, only allow usbd to receive DEVICE_DETACH
events for all devices.
When I continued chasing my original problem, I discovered that the
usbd_add_dev_event(USB_EVENT_DEVICE_DETACH, dev) call in usb_subr.c was
commented out. Bringing it back into play brought me a nice solid system
freeze, followed by a reboot shortly thereafter. I figure that must be
why it was commented out in the first place.
As it turns out, the placement of that call is really bad. The 'dev' it
hands out is in an inconsistent state if any subdevs existed (if there
were no subdevs, everything works fine). I say existed, because at the
original location of the add event call, the subdevs have already been
detached. The usbd_add_dev_event function however calls the
usbd_fill_deviceinfo, which wants to fiddle with the subdevs as well,
resulting in Bad Things happening. My patch to usb_subr.c simply moves
the usbd_add_dev_event call to just before the subdevs are disconnected.
Also, the patch to usb.c guarantees (I believe) that if a DRIVER_DETACH
event is added to the queue before the DEVICE_DETACH event has been
processed, the DEVICE_DETACH is kept on the queue, resulting in expected
behaviour by usbd.
Comments are welcome. If I don't hear anything from anyone, I'll send-pr
in a couple of days.
Cheers,
/Johny
--
Johny Mattsson - System Designer ,-. ,-. ,-. There is no truth.
http://www.earthmagic.org _.' `-' `-' There is only perception.
--- usb_subr.c.org Tue Oct 21 17:44:48 2003
+++ usb_subr.c Tue Oct 21 19:40:44 2003
@@ -1353,6 +1353,8 @@
}
#endif
+ usbd_add_dev_event(USB_EVENT_DEVICE_DETACH, dev);
+
if (dev-subdevs != NULL) {
DPRINTFN(3,(usb_disconnect_port: disconnect subdevs\n));
for (i = 0; dev-subdevs[i]; i++) {
@@ -1365,7 +1367,6 @@
}
}
- /*usbd_add_dev_event(USB_EVENT_DEVICE_DETACH, dev);*/
dev-bus-devices[dev-address] = NULL;
up-device = NULL;
usb_free_device(dev);
--- usb.c.org Tue Oct 21 16:51:25 2003
+++ usb.c Tue Oct 21 19:42:00 2003
@@ -781,7 +781,8 @@
for (ueqi = TAILQ_FIRST(usb_events); ueqi; ueqi = ueqi_next) {
ueqi_next = TAILQ_NEXT(ueqi, next);
if (ueqi-ue.u.ue_driver.ue_cookie.cookie ==
- uep-u.ue_device.udi_cookie.cookie) {
+ uep-u.ue_device.udi_cookie.cookie
+ !USB_EVENT_IS_DETACH(ueqi-ue.ue_type)) {
TAILQ_REMOVE(usb_events, ueqi, next);
free(ueqi, M_USBDEV);
usb_nevents--;
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
today panic
cvsup'd 21 oct 2003 morning (jakarta time)
ipv6# uname -a
FreeBSD ipv6.ppk.itb.ac.id 5.1-CURRENT FreeBSD 5.1-CURRENT #5: Tue Oct 21 20:25:
00 WIT 2003 root@:/usr/obj/usr/src/sys/PPK i386
panic messages:
---
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0xdeadc0de
fault code = supervisor read, page not present
instruction pointer = 0x8:0xc0564638
stack pointer = 0x10:0xcfe1f6e8
frame pointer = 0x10:0xcfe1f6e8
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 = 12 (swi1: net)
trap number = 12
panic: page fault
Uptime: 1h15m8s
Dumping 255 MB
16 32 48 64 80 96 112 128 144 160 176 192 208 224 240
---
Reading symbols from /usr/obj/usr/src/sys/PPK/modules/usr/src/sys/modules/acpi/a
cpi.ko.debug...done.
Loaded symbols for /usr/obj/usr/src/sys/PPK/modules/usr/src/sys/modules/acpi/acp
i.ko.debug
Reading symbols from /boot/kernel/daemon_saver.ko...done.
Loaded symbols for /boot/kernel/daemon_saver.ko
Reading symbols from /usr/obj/usr/src/sys/PPK/modules/usr/src/sys/modules/linux/
linux.ko.debug...done.
Loaded symbols for /usr/obj/usr/src/sys/PPK/modules/usr/src/sys/modules/linux/li
nux.ko.debug
#0 doadump () at /usr/src/sys/kern/kern_shutdown.c:240
240 dumping++;
(kgdb)
#0 doadump () at /usr/src/sys/kern/kern_shutdown.c:240
#1 0xc04fc96c in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:372
#2 0xc04fccf7 in panic () at /usr/src/sys/kern/kern_shutdown.c:550
#3 0xc0683b66 in trap_fatal (frame=0xcfe1f6a8, eva=0)
at /usr/src/sys/i386/i386/trap.c:820
#4 0xc0683802 in trap_pfault (frame=0xcfe1f6a8, usermode=0, eva=3735929054)
at /usr/src/sys/i386/i386/trap.c:734
#5 0xc06833bd in trap (frame=
{tf_fs = -1049690088, tf_es = -807337968, tf_ds = -807337968, tf_edi = -10
66651587, tf_esi = -559038242, tf_ebp = -807274776, tf_isp = -807274796, tf_ebx
= -807274548, tf_edx = -559038242, tf_ecx = 0, tf_eax = -559038242, tf_trapno =
12, tf_err = 0, tf_eip = -1068087752, tf_cs = 8, tf_eflags = 66118, tf_esp = -80
7274576, tf_ss = -1068378335}) at /usr/src/sys/i386/i386/trap.c:419
#6 0xc06740c8 in calltrap () at {standard input}:102
#7 0xc051d721 in kvprintf (fmt=0xc06c303d @ %s:%d,
func=0xc051d0c0 snprintf_func, arg=0xcfe1f7cc, radix=10,
ap=0xcfe1f818 -ÆlÀ£\004) at /usr/src/sys/kern/subr_prf.c:669
#8 0xc051d03e in vsnprintf (str=0xc072f040 mtx_lock() of spin mutex ,
size=0, format=0x0, ap=0x0) at /usr/src/sys/kern/subr_prf.c:414
#9 0xc04fcc11 in panic (fmt=0xc06c3022 mtx_lock() of spin mutex %s @ %s:%d)
at /usr/src/sys/kern/kern_shutdown.c:511
#10 0xc04f2d66 in _mtx_lock_flags (m=0xc4378c90, opts=0,
file=0xc06cc62d /usr/src/sys/net/route.c, line=1187)
at /usr/src/sys/kern/kern_mutex.c:332
#11 0xc057968f in rt_check (lrt=0x0, lrt0=0xcfe1f8cc, dst=0x0)
at /usr/src/sys/net/route.c:1187
#12 0xc056a9d0 in ether_output (ifp=0xc41d6000, m=0xc16f8f00, dst=0xc41ce2b0,
rt0=0xc43d6b00) at /usr/src/sys/net/if_ethersubr.c:162
#13 0xc0593024 in ip_output (m0=0x32, opt=0xc41d6000, ro=0xc41ce2b0, flags=1,
imo=0x0, inp=0x0) at /usr/src/sys/netinet/ip_output.c:1025
#14 0xc058cc8b in ip_forward (m=0xc16f8f00, ro=0xcfe1fc38, srcrt=0,
next_hop=0x0) at /usr/src/sys/netinet/ip_input.c:1944
#15 0xc058b8a6 in ip_input (m=0xc16f8f00)
at /usr/src/sys/netinet/ip_input.c:772
#16 0xc05739ce in netisr_processqueue (ni=0xc0755a50)
at /usr/src/sys/net/netisr.c:140
#17 0xc0573e08 in swi_net (dummy=0x0) at /usr/src/sys/net/netisr.c:246
#18 0xc04e8f72 in ithread_loop (arg=0xc16c1d00)
at /usr/src/sys/kern/kern_intr.c:534
#19 0xc04e7f6f in fork_exit (callout=0xc04e8de0 ithread_loop, arg=0x0,
frame=0x0) at /usr/src/sys/kern/kern_fork.c:796
-dikshie-
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: USB Keyboard questions
Doesnt look like my Abit KD7 has a legacy support, I can choose BIOS support or OS support for the USB keyboard and mouse. The keyboard works perfectly under winxp and under win200. I dont see the behavior with the letters there and this is using the standard drivers for a HID keyboard as win2000 finds it. I had the keyboard pluged into a USB hub, when I moved it to a USB2 port I didnt experiense the behavior with the letters, but I was still unable to to use the keyboard to install the keyboard using the USB ports. When I use the USB - PS/2 converter that came with the keyboard it works though. So I think the letter problem was due to my CNet USB 4 way hub. And I dont know why am unable to use the keyboard pluged into the USB port when I install FreeBSD 5.1 but it works when I install FreeBSD 4.8. Thanks for the help and comments on this. :) Peter - Original Message - From: Andre Guibert de Bruet [EMAIL PROTECTED] To: Peter [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Tuesday, October 21, 2003 5:58 AM Subject: Re: USB Keyboard questions On Mon, 20 Oct 2003, Peter wrote: I have been reading that page and I have the keyboard working, but I fail to see how this will help a user that only has a USB Keyboard that wants to use FreeBSD5.1 and is unable to install it due to the lack of USB support from the start. Some BIOSes offer a USB legacy support option which allows the use of a usb keyboard as if it were a PS2 keyboard during system startup. And I still would like to know if its my keyboard that is out of sync with the USB spec since it will add letters when I write like . This should read like this but can end up like Thisi should reaed likek this Does this keyboard exhibit the same behavior when it's plugged into a Windows machine? It's a little early to speculate what the issue could be, as there are a number of links in this chain but it's very possible that you simply have a wonky keyboard on your hands. Regards, Andre Guibert de Bruet | Enterprise Software Consultant Silicon Landmark, LLC. | http://siliconlandmark.com/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Problems with NFS (client) under 5.1.
I'm trying to set a FreeBSD 5.1 machine up as an NFS client. The server is on an SGI box. Things are strange: phoenix# uname -a FreeBSD phoenix.mydomain 5.1-CURRENT FreeBSD 5.1-CURRENT #0: Thu Sep 18 15:20:19 GMT 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 phoenix# ls -ld /mnt drwxr-xr-x 2 root wheel 512 Jun 5 01:53 /mnt phoenix# mount rebus:/rebus/home /mnt phoenix# ls -ld /mnt ls: /mnt: Permission denied phoenix# ls -ld /* | grep mnt phoenix# umount /mnt phoenix# ls -ld /* | grep mnt drwxr-xr-x 2 root wheel 512 Jun 5 01:53 /mnt What's going on here? Is it a bug or something that I'm doing wrong? phoenix# grep nfs /etc/rc.conf nfs_client_enable=YES # This host is an NFS client (or NO). The NFS server is: IRIX64 rebus 6.5 04101930 IP35 mips Joe -- Josef Karthauser ([EMAIL PROTECTED]) http://www.josef-k.net/ FreeBSD (cvs meister, admin and hacker) http://www.uk.FreeBSD.org/ Physics Particle Theory (student) http://www.pact.cpes.sussex.ac.uk/ An eclectic mix of fact and theory. = pgp0.pgp Description: PGP signature
Re: Problems with NFS (client) under 5.1.
On Tue, Oct 21, 2003 at 01:09:18PM +0100, Josef Karthauser wrote: I'm trying to set a FreeBSD 5.1 machine up as an NFS client. The server is on an SGI box. Things are strange: phoenix# uname -a FreeBSD phoenix.mydomain 5.1-CURRENT FreeBSD 5.1-CURRENT #0: Thu Sep 18 15:20:19 GMT 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 phoenix# ls -ld /mnt drwxr-xr-x 2 root wheel 512 Jun 5 01:53 /mnt phoenix# mount rebus:/rebus/home /mnt phoenix# ls -ld /mnt ls: /mnt: Permission denied phoenix# ls -ld /* | grep mnt phoenix# umount /mnt phoenix# ls -ld /* | grep mnt drwxr-xr-x 2 root wheel 512 Jun 5 01:53 /mnt You are root - and root is often mapped to nobody on the server. Are you shure that nobody is allowed to see? The ls -ld /mnt case is strange, but /mnt is already on the server namespace. -- B.Walter BWCThttp://www.bwct.de [EMAIL PROTECTED] [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
em0: invalid EEPROM checksum
Hi there, I just found that the em0 interface in one of my boxes stopped working after an upgrade from 5.1-RELEASE to 5.1-CURRENT, this is what the kernel spits out: $ dmesg | grep em0 em0: Intel(R) PRO/1000 Network Connection, Version - 1.7.16 port 0xb000-0xb03f mem 0xe200-0xe201 irq 12 at device 5.0 on pci2 em0: [MPSAFE] em0: The EEPROM Checksum Is Not Valid em0: Unable to initialize the hardware device_probe_and_attach: em0 attach returned 5 regards, le -- Lukas Ertl eMail: [EMAIL PROTECTED] UNIX Systemadministrator Tel.: (+43 1) 4277-14073 Vienna University Computer Center Fax.: (+43 1) 4277-9140 University of Vienna http://mailbox.univie.ac.at/~le/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Random signals in {build,install}world recently?
On Mon, Oct 20, 2003 at 11:57:48PM -0700, Terry Lambert wrote: Barney Wolff wrote: I don't think so. I tried that on my A7M266D with no effect. I believe something in recent pmap code doesn't like this mobo, or maybe dual athlons in general. I can run RELENG_5_1 rock solid, and -current from 9/24/03 rock solid, but -current from 10/3 or later gets random sigs and eventually panics. I have scsi disks so it's not ata. I think you need to define random; do you mean rare in frequency over time at unpredicatable intervals or you never know what program is going to get shot in the head, every 5 seconds, like clockwork? The latter, with the interval being more like a very few minutes rather than seconds. The system would sit fine when idle, but never make it all the way through buildworld, or buildkernel, or building a port. In one notorious instance, the -current kernel didn't even make it through installworld without a sig. grep, sed, awk, sh have all gotten sigs, not just cc. My impression so far in this therad is that it's the former. If it's the latter, then I need to think about the problem differently. Note that you can identify the patch that caused the problem, if there's an 8 day difference, in no more than 4 kernel recompiles (log2(8)+1), if you have a local CVS mirror. The frequency of patches to pmap was quite high, and that was not the only file patched. But yes, I can do a binary search. I haven't, because the changes to pmap were architectural; we're not talking about a typo here. Of course it's just my assumption that it's pmap because the eventual panic is there. btw, I use sched_bsd so _ule is not a suspect. -- Barney Wolff http://www.databus.com/bwresume.pdf I'm available by contract or FT, in the NYC metro area or via the 'Net. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems with NFS (client) under 5.1.
On Tue, Oct 21, 2003 at 03:33:37PM +0200, Bernd Walter wrote: You are root - and root is often mapped to nobody on the server. Are you shure that nobody is allowed to see? The ls -ld /mnt case is strange, but /mnt is already on the server namespace. The linux boxes on the network don't appear to have any problems. Either way why is the /mnt entry disappearing? phoenix# mount rebus:/rebus/home /mnt phoenix# suspend [1] + Suspended (signal) su $ id uid=1001(joe) gid=1001(joe) groups=1001(joe), 0(wheel) $ ls /mnt ls: /mnt: Permission denied $ ls -l / ls: mnt: Permission denied total 45 -r--r--r-- 1 root wheel 4735 Jun 5 01:57 COPYRIGHT drwxr-xr-x 2 root wheel 1024 Sep 17 19:31 bin drwxr-xr-x 6 root wheel 512 Sep 18 17:04 boot drwxr-xr-x 2 root wheel 512 Jul 2 17:32 cdrom lrwxr-xr-x 1 root wheel10 Jul 2 17:49 compat - usr/compat dr-xr-xr-x 4 root wheel 512 Oct 21 12:09 dev drwxr-xr-x 2 root wheel 512 Jul 2 17:32 dist -rw--- 1 root wheel 4096 Sep 17 11:28 entropy drwxr-xr-x 16 root wheel 2048 Oct 21 12:21 etc lrwxr-xr-x 1 root wheel 9 Sep 17 12:10 home - /usr/home drwxr-xr-x 2 root wheel 1024 Sep 17 19:33 lib drwxr-xr-x 2 root wheel 512 Sep 17 19:33 libexec lrwxr-xr-x 1 root wheel10 Sep 23 11:40 local - /usr/local dr-xr-xr-x 2 root wheel 512 Jun 5 01:53 proc drwxr-xr-x 2 root wheel 2560 Sep 17 19:33 rescue drwxr-xr-x 3 root wheel 512 Sep 29 13:01 root drwxr-xr-x 2 root wheel 2560 Sep 17 19:33 sbin drwxr-xr-x 4 root wheel 1024 Jul 2 17:32 stand lrwxr-xr-x 1 root wheel11 Sep 17 19:30 sys - usr/src/sys drwxrwxrwt 4 root wheel 512 Oct 21 15:27 tmp drwxr-xr-x 18 root wheel 512 Oct 16 11:48 usr drwxr-xr-x 20 root wheel 512 Oct 16 11:53 var $ fg su phoenix# umount /mnt phoenix# ls -l / total 51 -rw-r--r-- 2 root wheel 797 Jun 5 01:57 .cshrc -rw-r--r-- 2 root wheel 251 Jun 5 01:57 .profile -r--r--r-- 1 root wheel 4735 Jun 5 01:57 COPYRIGHT drwxr-xr-x 2 root wheel 1024 Sep 17 19:31 bin drwxr-xr-x 6 root wheel 512 Sep 18 17:04 boot drwxr-xr-x 2 root wheel 512 Jul 2 17:32 cdrom lrwxr-xr-x 1 root wheel10 Jul 2 17:49 compat - usr/compat dr-xr-xr-x 4 root wheel 512 Oct 21 12:09 dev drwxr-xr-x 2 root wheel 512 Jul 2 17:32 dist -rw--- 1 root wheel 4096 Sep 17 11:28 entropy drwxr-xr-x 16 root wheel 2048 Oct 21 12:21 etc lrwxr-xr-x 1 root wheel 9 Sep 17 12:10 home - /usr/home drwxr-xr-x 2 root wheel 1024 Sep 17 19:33 lib drwxr-xr-x 2 root wheel 512 Sep 17 19:33 libexec lrwxr-xr-x 1 root wheel10 Sep 23 11:40 local - /usr/local drwxr-xr-x 2 root wheel 512 Jun 5 01:53 mnt dr-xr-xr-x 2 root wheel 512 Jun 5 01:53 proc drwxr-xr-x 2 root wheel 2560 Sep 17 19:33 rescue drwxr-xr-x 3 root wheel 512 Sep 29 13:01 root drwxr-xr-x 2 root wheel 2560 Sep 17 19:33 sbin drwxr-xr-x 4 root wheel 1024 Jul 2 17:32 stand lrwxr-xr-x 1 root wheel11 Sep 17 19:30 sys - usr/src/sys drwxrwxrwt 4 root wheel 512 Oct 21 15:27 tmp drwxr-xr-x 18 root wheel 512 Oct 16 11:48 usr drwxr-xr-x 20 root wheel 512 Oct 16 11:53 var Joe -- Josef Karthauser ([EMAIL PROTECTED]) http://www.josef-k.net/ FreeBSD (cvs meister, admin and hacker) http://www.uk.FreeBSD.org/ Physics Particle Theory (student) http://www.pact.cpes.sussex.ac.uk/ An eclectic mix of fact and theory. = pgp0.pgp Description: PGP signature
Re: Random signals in {build,install}world recently?
On Mon, Oct 20, 2003 at 04:38:32PM +0300, Vallo Kallaste [EMAIL PROTECTED] wrote: [snip all] Ok, following up my own email.. I went back to last known good kernel/world combination, which is from September 16. The next and problematic kernel/world pair is from September 30. So the problem was introduced between these dates. I've built world and kernel from Sep 16 sources 00:00:00 UTC and my system is solid again, it's the fourth make -j4 buildworld in a row now and the problem (signals and ICE's in buildworld, not pmap_enter) is gone. My cents towards resolving this problem.. -- Vallo Kallaste ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ethercons: ethernet console driver for 5-current
FYI, for those who expressed interest, the URL has changed slightly, and I've posted some minor bugfixes and updates: http://www.watson.org/~robert/freebsd/ethercons/ I'm also investigating the MOPRC protocol, and alternative ethernet address choices. I did take a look at the Panasas ipgdb patches for FreeBSD, but it looks like they wouldn't apply well in 5.x without substantial modification (and a bit of evolution of our MP-handling in device drivers). Robert N M Watson FreeBSD Core Team, TrustedBSD Projects [EMAIL PROTECTED] Network Associates Laboratories ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Sleeping on isp_mboxwaiting with the following non-sleepablelocks held:
This happened to me just now on alpha: (da0:isp0:0:0:0): Retrying Command (per Sense Data) (da0:isp0:0:0:0): READ(06). CDB: 8 5 f 30 10 0 (da0:isp0:0:0:0): CAM Status: SCSI Status Error (da0:isp0:0:0:0): SCSI Status: Check Condition (da0:isp0:0:0:0): MEDIUM ERROR info:50f30 asc:11,0 (da0:isp0:0:0:0): Unrecovered read error field replaceable unit: e4 actual retry count: 257 (da0:isp0:0:0:0): Retrying Command (per Sense Data) swap_pager: indefinite wait buffer: device: da0b, blkno: 331568, size: 8192 (da0:isp0:0:0:0): READ(06). CDB: 8 5 f 30 10 0 (da0:isp0:0:0:0): CAM Status: SCSI Status Error (da0:isp0:0:0:0): SCSI Status: Check Condition (da0:isp0:0:0:0): MEDIUM ERROR info:50f30 asc:11,0 (da0:isp0:0:0:0): Unrecovered read error field replaceable unit: e4 actual retry count: 257 (da0:isp0:0:0:0): Retries Exhausted swap_pager: I/O error - pagein failed; blkno 331568,size 8192, error 5 vm_fault: pager read error, pid 90537 (aspell) Sleeping on isp_mboxwaiting with the following non-sleepablelocks held: exclusive sleep mutex g_xdown r = 0 (0xfe0006bfdc78) locked @ /a/asami/portbuild/alpha/src-client/sys/geom/geom_io.c:345 witness_warn Stopped at Debugger+0x38: zapnot v0,#0xf,v0 v0=0x0 db trace Debugger() at Debugger+0x38 witness_warn() at witness_warn+0x284 msleep() at msleep+0xa8 isp_mbox_wait_complete() at isp_mbox_wait_complete+0x94 isp_mboxcmd() at isp_mboxcmd+0x258 isp_update_bus() at isp_update_bus+0x2f0 isp_update() at isp_update+0x54 isp_start() at isp_start+0x208 isp_action() at isp_action+0x1bc xpt_run_dev_sendq() at xpt_run_dev_sendq+0x23c xpt_action() at xpt_action+0x2a0 dastart() at dastart+0x220 xpt_run_dev_allocq() at xpt_run_dev_allocq+0xf0 xpt_schedule() at xpt_schedule+0xc0 dastrategy() at dastrategy+0x70 g_disk_start() at g_disk_start+0x1ec g_io_schedule_down() at g_io_schedule_down+0x234 g_down_procbody() at g_down_procbody+0x5c fork_exit() at fork_exit+0x100 exception_return() at exception_return --- root of call graph --- Kris pgp0.pgp Description: PGP signature
Re: USB Keyboard questions
Was to quick there, the problem with the letters still exist. But when I run it with the convertet it works. Peter - Original Message - From: Peter [EMAIL PROTECTED] To: Andre Guibert de Bruet [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Tuesday, October 21, 2003 12:25 PM Subject: Re: USB Keyboard questions Doesnt look like my Abit KD7 has a legacy support, I can choose BIOS support or OS support for the USB keyboard and mouse. The keyboard works perfectly under winxp and under win200. I dont see the behavior with the letters there and this is using the standard drivers for a HID keyboard as win2000 finds it. I had the keyboard pluged into a USB hub, when I moved it to a USB2 port I didnt experiense the behavior with the letters, but I was still unable to to use the keyboard to install the keyboard using the USB ports. When I use the USB - PS/2 converter that came with the keyboard it works though. So I think the letter problem was due to my CNet USB 4 way hub. And I dont know why am unable to use the keyboard pluged into the USB port when I install FreeBSD 5.1 but it works when I install FreeBSD 4.8. Thanks for the help and comments on this. :) Peter - Original Message - From: Andre Guibert de Bruet [EMAIL PROTECTED] To: Peter [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Tuesday, October 21, 2003 5:58 AM Subject: Re: USB Keyboard questions On Mon, 20 Oct 2003, Peter wrote: I have been reading that page and I have the keyboard working, but I fail to see how this will help a user that only has a USB Keyboard that wants to use FreeBSD5.1 and is unable to install it due to the lack of USB support from the start. Some BIOSes offer a USB legacy support option which allows the use of a usb keyboard as if it were a PS2 keyboard during system startup. And I still would like to know if its my keyboard that is out of sync with the USB spec since it will add letters when I write like . This should read like this but can end up like Thisi should reaed likek this Does this keyboard exhibit the same behavior when it's plugged into a Windows machine? It's a little early to speculate what the issue could be, as there are a number of links in this chain but it's very possible that you simply have a wonky keyboard on your hands. Regards, Andre Guibert de Bruet | Enterprise Software Consultant Silicon Landmark, LLC. | http://siliconlandmark.com/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems with NFS (client) under 5.1.
* Josef Karthauser [EMAIL PROTECTED] [031021 08:24] wrote: On Tue, Oct 21, 2003 at 03:33:37PM +0200, Bernd Walter wrote: You are root - and root is often mapped to nobody on the server. Are you shure that nobody is allowed to see? The ls -ld /mnt case is strange, but /mnt is already on the server namespace. The linux boxes on the network don't appear to have any problems. Either way why is the /mnt entry disappearing? I saw this before with QNX server and FreeBSD client as well. Same behavior, root ok, other users not. I was nearly a year ago, but I haven't seen a fix go by either so... -Alfred ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems with NFS (client) under 5.1.
On Tue, Oct 21, 2003 at 12:32:12PM -0400, Robert Watson wrote: On Tue, 21 Oct 2003, Josef Karthauser wrote: I'm trying to set a FreeBSD 5.1 machine up as an NFS client. The server is on an SGI box. Things are strange: Any chance you could grab a copy of ethereal and do a bit of on-the-wire inspection of the RPCs? It would be interesting to know which of the requests are serviced out of the client cache, and which make it to the server. It would also be interesting to see if you can see failures in the wire protocol, or if they're purely an artifact of the client. Also, can you confirm the Linux and FreeBSD clients are both using the same version of NFS with similar protocol settings (i.e., NFSv3 over UDP). Does Linux do NFSv3 yet? I thought that at least until recently there were stability issues and it was recommended it not be used. Kris pgp0.pgp Description: PGP signature
20031021 snapshot install has glitches
You cannot set the root password as passwd dumps core on a signal 12. I cannot mount any live filesystem CDROM since neither acd0 as acd1 seem to satisfy the installer, they both fail with a file not found error, most likely a device node. -- Jeroen Ruigrok van der Werven asmodai(at)wxs.nl / asmodai / kita no mono PGP fingerprint: 2D92 980E 45FE 2C28 9DB7 9D88 97E6 839B 2EAC 625B http://www.tendra.org/ | http://www.in-nomine.org/~asmodai/diary/ Hope and fear cannot alter the seasons... ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems with NFS (client) under 5.1.
hi. Does Linux do NFSv3 yet? I thought that at least until recently there were stability issues and it was recommended it not be used. I had some problems with stale NFS handle when NFS-mounting two FreeBSD 5.1 client (one with the frozen 5.1 and one as of Oct. 10'th) to a Linux server with ReiserFS. When I mounted with ver. 2 the problems went away on the FreeBSD with source from Oct. 10'th and have less stale NFS handles with the frozen 5.1. regards Claus Yahoo! Mail (http://dk.mail.yahoo.com) - Gratis: 6 MB lagerplads, spamfilter og virusscan ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: USB Keyboard questions
On Tue, 21 Oct 2003, Peter wrote: Doesnt look like my Abit KD7 has a legacy support, I can choose BIOS support or OS support for the USB keyboard and mouse. The keyboard works perfectly under winxp and under win200. I dont see the behavior with the letters there and this is using the standard drivers for a HID keyboard as win2000 finds it. I bet BIOS support is the right option. So I think the letter problem was due to my CNet USB 4 way hub. And I dont know why am unable to use the keyboard pluged into the USB port when I install FreeBSD 5.1 but it works when I install FreeBSD 4.8. What kind of usb controller is it? ohci? Also, the Macintosh forums have been complaining about the poor quality of most USB hubs and the problems they cause with printers, etc. Its too bad since hubs should be really easy to build. -- Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ip stack broken?
On Sat, 18 Oct 2003, mjoyner wrote: It works fine with a 5.1 kernel. What version is your userland? Doug White wrote: On Fri, 17 Oct 2003, mjoyner wrote: When I use a current kernel, my system will obtain an ip address via dhclient, but thereafter, it cannot see the network. I have tried switching ethernet cards. (used both a dc0 and an fxp0) Am currently using a 5.1-RELEASE kernel to have network access. Advice? Perhaps your DHCP server is handing out bogus info? -- Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: still panic
On Sun, 19 Oct 2003, Dikshie wrote: cvsup'd 19 Oct 2003 in the morning (jakarta time), uname -a FreeBSD ipv6.ppk.itb.ac.id 5.1-CURRENT FreeBSD 5.1-CURRENT #3: Sun Oct 19 21:25: 57 WIT 2003 root@:/usr/obj/usr/src/sys/PPK i386 Fatal trap 12: page fault while in kernel mode fault virtual address = 0xdeadc0de Well this is an interesting one. The trap 12 came from a previous panic trying to print the panic string on what appears to be free'd memory with INVARIANTS enabled. Digging through the trace, it appears there was a problem in the ip forwarding code. Sam Leffler is aware of this problem and is working on it. Thanks very much for your complete report! -- Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: USB Keyboard questions
On Tue, 21 Oct 2003, Peter wrote: Was to quick there, the problem with the letters still exist. But when I run it with the convertet it works. Under Windows or with the USB2 card (or both)? Andre Guibert de Bruet | Enterprise Software Consultant Silicon Landmark, LLC. | http://siliconlandmark.com/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: make release...
On Tue, Oct 21, 2003 at 04:51:22PM +0930, Daniel O'Connor wrote: [...] Either apply the patch I attached and add CPNOTCVS= to your make release options, or check out the repository. In HEAD, a similar functionality is already provided through the use of the EXTSRCDIR variable. JFYI. Cheers, -- Ruslan Ermilov Sysadmin and DBA, [EMAIL PROTECTED] Sunbay Software Ltd, [EMAIL PROTECTED] FreeBSD committer pgp0.pgp Description: PGP signature
MBR zapped when panicking?
Hi, Today I had a -CURRENT machine panic on me with a page fault, and something happened that I have seen before: the machine refused to come up afterwards. Closer inspection revealed that the MBR on the boot disk was totally zapped, filled with seemingly random characters. Luckily the disk label was still intact, allowing me to recover the machine reasonably easy. The MBRs on the other disks (see attached dmesg.txt for more info) wasn't touched by the panic. Note that all disks in this machine are Dangerously Dedicated (see attached fdisk-ad[023].txt). I hope that's not totally unsupported, but what I do observe is that all these DD partitions seem to start at offset 0 instead of 1, thereby making the MBR actually part of the partition itself. Could this be a reason for something (GEOM?) stomping over the MBR when the box panics? Btw, this panic was a page fault, and I got the nice 'giving up on xxx buffers' message too... :( It seems to have panicked somewhere in the IPv6 stack (see panic.txt for more info), I think I read somewhere that this has been fixed already? If so, I'll just cvsup and hope it doesn't happen again... Anyhow, I'll be keeping some extra spare backups of all my bootsectors and disklabels. :) Cheers, Dimitry 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.1-CURRENT #0: Fri Oct 17 13:39:52 CEST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/TENSOR Preloaded elf kernel /boot/kernel/kernel at 0xc075e000. Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Pentium/P54C (150.00-MHz 586-class CPU) Origin = GenuineIntel Id = 0x52c Stepping = 12 Features=0x1bfFPU,VME,DE,PSE,TSC,MSR,MCE,CX8 real memory = 67108864 (64 MB) avail memory = 59912192 (57 MB) Intel Pentium detected, installing workaround for F00F bug netsmb_dev: loaded npx0: [FAST] npx0: math processor on motherboard npx0: INT 16 interface pcibios: BIOS version 2.10 Using $PIR table, 5 entries at 0xc00fdae0 pcib0: Host to PCI bridge at pcibus 0 on motherboard pci0: PCI bus on pcib0 pci_cfgintr: 0:15 INTA BIOS irq 11 pci_cfgintr: 0:16 INTA BIOS irq 10 pci_cfgintr: 0:17 INTA BIOS irq 9 isab0: PCI-ISA bridge at device 7.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel PIIX3 WDMA2 controller port 0xf000-0xf00f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata0: [MPSAFE] ata1: at 0x170 irq 15 on atapci0 ata1: [MPSAFE] pci0: display, VGA at device 15.0 (no driver attached) fxp0: Intel 82559 Pro/100 Ethernet port 0x6100-0x613f mem 0xe400-0xe40f,0xe4201000-0xe4201fff irq 10 at device 16.0 on pci0 fxp0: Ethernet address 00:d0:b7:a0:8c:26 miibus0: MII bus on fxp0 inphy0: i82555 10/100 media interface on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp1: Intel 82559 Pro/100 Ethernet port 0x6200-0x623f mem 0xe410-0xe41f,0xe420-0xe4200fff irq 9 at device 17.0 on pci0 fxp1: Ethernet address 00:d0:b7:a0:8b:0a miibus1: MII bus on fxp1 inphy1: i82555 10/100 media interface on miibus1 inphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto orm0: Option ROM at iomem 0xc-0xc7fff on isa0 atkbdc0: Keyboard controller (i8042) at port 0x64,0x60 on isa0 atkbd0: AT Keyboard irq 1 on atkbdc0 kbd0 at atkbd0 fdc0: Enhanced floppy controller (i82077, NE72065 or clone) at port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: 1440-KB 3.5 drive on fdc0 drive 0 ppc0: Parallel port at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/16 bytes threshold ppbus0: Parallel port bus on ppc0 lpt0: Printer on ppbus0 lpt0: Interrupt-driven port sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x100 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A, console sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 unknown: PNP0303 can't assign resources (port) unknown: PNP0501 can't assign resources (port) unknown: PNP0700 can't assign resources (port) unknown: PNP0401 can't assign resources (port) unknown: PNP0501 can't assign resources (port) Timecounter TSC frequency 15888 Hz quality 800 Timecounters tick every 10.000 msec IPsec: Initialized Security Association Processing. IP Filter: v3.4.31 initialized. Default = block all, Logging = enabled GEOM: create disk ad0 dp=0xc1607d70 ad0: 9787MB QUANTUM FIREBALL lct10 10.2A [19885/16/63] at ata0-master WDMA2 GEOM: create disk ad2 dp=0xc1607b70 ad2: 6149MB QUANTUM FIREBALL CR6.4A [13328/15/63] at ata1-master WDMA2 GEOM: create disk ad3 dp=0xc1607a70 ad3: 4028MB QUANTUM FIREBALL CR4.2A [8184/16/63] at ata1-slave WDMA2 Mounting root from ufs:/dev/ad0s1a fxp0: Microcode loaded, int_delay: 1000 usec bundle_max: 6 fxp0: Microcode loaded, int_delay: 1000 usec bundle_max: 6 fxp1: Microcode
Re: MBR zapped when panicking?
In message [EMAIL PROTECTED], Dimitry Andric writes: Note that all disks in this machine are Dangerously Dedicated (see attached fdisk-ad[023].txt). I hope that's not totally unsupported, but what I do observe is that all these DD partitions seem to start at offset 0 instead of 1, thereby making the MBR actually part of the partition itself. Could this be a reason for something (GEOM?) stomping over the MBR when the box panics? Well, GEOM is no more likely to stomp on anything than your average filesystem. Less in fact because GEOM does not originate I/O request, only pass them through. -- 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. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Current GBDE Problems
I upgraded source on the current branch a few days ago and havn't been able to get GBDE to work nicely since. I'm running two separate GBDE devices, one 8MB memory disk, and one 1.2TB hardware raid 5 array, neither of which can I now get to mount. When I initialize a new disk on startup for the memory disk, and then mount and newfs the disk, I get a cg 0: bad magic number error. When I try to attach my existing raid 5 array using gbde attach /dev/twed0 -l I get success but then upon mount /dev/twed0.bde I receive the error: mount: dev/twed0.bde: Input/output error Furthermore, when I tried to fsck -t UFS /dev/twed0.bde I recieved: ** /dev/twed0.bde CANNOT SEEK BLK: XX CONTINUE? [yn] n Anyone have any ideas? I can't figure out what could be wrong. -John ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Current GBDE Problems
In message [EMAIL PROTECTED], John Stockdale writes: I upgraded source on the current branch a few days ago and havn't been able to get GBDE to work nicely since. I'm running two separate GBDE devices, one 8MB memory disk, and one 1.2TB hardware raid 5 array, neither of which can I now get to mount. This problem hsould already be fixed, it was caused by a change in the rijndael/AES code in the kernel. -- 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. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: pcm exclusive sleep mutex with Oct19 CURRENT
Hello Paolo,
See below.
On Oct 20, Paolo Pisati wrote:
from my dmesg:
[snip]
exclusive sleep mutex pcm0:mixer (pcm mixer) r = 0 (0xc2d34540) locked @
/usr/src/sys/dev/sound/pcm/mixer.c:322
Could you try deleting the snd_mtxlock and snd_mtxunlock in
mixer_hwvol_init() in mixer.c? I think it's uneeded as the function
is only called in particular device instance creation and no-one
should be able touch it yet.
acquiring duplicate lock of same type: pcm channel
1st pcm0:record:0 @ /usr/src/sys/dev/sound/pcm/sound.c:195
2nd pcm0:play:0 @ /usr/src/sys/dev/sound/pcm/sound.c:195
Stack backtrace:
Please try my wild guess patch that is attached. I tried to
re-arrange the routine to only hold one locked channel at a time. I
suppose another option would be flag the lock type as having
duplicates ok.
--Mat
--
If you optimize everything, you will always be unhappy.
- Don Knuth
--- dspold.cSun Sep 14 17:49:38 2003
+++ dsp.c Tue Oct 21 14:38:44 2003
@@ -174,6 +174,8 @@
intrmask_t s;
u_int32_t fmt;
int devtype;
+ int rdref;
+ int error;
s = spltty();
d = dsp_get_info(i_dev);
@@ -209,6 +211,8 @@
panic(impossible devtype %d, devtype);
}
+ rdref = 0;
+
/* lock snddev so nobody else can monkey with it */
pcm_lock(d);
@@ -251,67 +255,66 @@
return EBUSY;
}
/* got a channel, already locked for us */
- }
-
- if (flags FWRITE) {
- /* open for write */
- wrch = pcm_chnalloc(d, PCMDIR_PLAY, td-td_proc-p_pid, -1);
- if (!wrch) {
- /* no channel available */
- if (flags FREAD) {
- /* just opened a read channel, release it */
- pcm_chnrelease(rdch);
- }
- /* exit */
- pcm_unlock(d);
- splx(s);
- return EBUSY;
- }
- /* got a channel, already locked for us */
- }
-
- i_dev-si_drv1 = rdch;
- i_dev-si_drv2 = wrch;
-
- /* Bump refcounts, reset and unlock any channels that we just opened,
-* and then release device lock.
-*/
- if (flags FREAD) {
if (chn_reset(rdch, fmt)) {
pcm_chnrelease(rdch);
i_dev-si_drv1 = NULL;
- if (wrch (flags FWRITE)) {
- pcm_chnrelease(wrch);
- i_dev-si_drv2 = NULL;
- }
pcm_unlock(d);
splx(s);
return ENODEV;
}
+
if (flags O_NONBLOCK)
rdch-flags |= CHN_F_NBIO;
pcm_chnref(rdch, 1);
CHN_UNLOCK(rdch);
+ rdref = 1;
+ /*
+* Record channel created, ref'ed and unlocked
+*/
}
+
if (flags FWRITE) {
- if (chn_reset(wrch, fmt)) {
- pcm_chnrelease(wrch);
- i_dev-si_drv2 = NULL;
- if (flags FREAD) {
- CHN_LOCK(rdch);
- pcm_chnref(rdch, -1);
- pcm_chnrelease(rdch);
- i_dev-si_drv1 = NULL;
- }
- pcm_unlock(d);
- splx(s);
- return ENODEV;
+ /* open for write */
+ wrch = pcm_chnalloc(d, PCMDIR_PLAY, td-td_proc-p_pid, -1);
+ error = 0;
+
+ if (!wrch)
+ error = EBUSY; /* XXX Right return code? */
+ else if (chn_reset(wrch, fmt))
+ error = ENODEV;
+
+ if (error != 0) {
+ if (wrch) {
+ /*
+* Free play channel
+*/
+ pcm_chnrelease(wrch);
+ i_dev-si_drv2 = NULL;
}
- if (flags O_NONBLOCK)
- wrch-flags |= CHN_F_NBIO;
- pcm_chnref(wrch, 1);
- CHN_UNLOCK(wrch);
+ if (rdref) {
+ /*
+* Lock, deref and release previously created record channel
+*/
+ CHN_LOCK(rdch);
+ pcm_chnref(rdch, -1);
+ pcm_chnrelease(rdch);
+ i_dev-si_drv1 = NULL;
+ }
+
+ pcm_unlock(d);
+ splx(s);
+ return error;
+ }
+
+ if (flags O_NONBLOCK)
+ wrch-flags |= CHN_F_NBIO;
+ pcm_chnref(wrch,
Yet another LOR: vm object/system map
This particular LOR happened upon getting out of swap. My knowledge is insufficient to tell if it's a sign of a real problem or just a false positive. swap_pager: out of swap space swap_pager_getswapspace(16): failed lock order reversal 1st 0xc2e17d4c vm object (vm object) @ /usr/src/sys/vm/vnode_pager.c:1120 2nd 0xc0c2f110 system map (system map) @ /usr/src/sys/vm/vm_kern.c:328 Stack backtrace: backtrace(c05ca039,c0c2f110,c05d4ecc,c05d4ecc,c05d4d63) at backtrace+0x17 witness_lock(c0c2f110,8,c05d4d63,148,1263) at witness_lock+0x672 _mtx_lock_flags(c0c2f110,0,c05d4d63,148,3) at _mtx_lock_flags+0xba _vm_map_lock(c0c2f0b0,c05d4d63,148,2b4,c061eec0) at _vm_map_lock+0x36 kmem_malloc(c0c2f0b0,1000,101,cc3e7ac8,c056cd93) at kmem_malloc+0x3a page_alloc(c0c3a3c0,1000,cc3e7abb,101,c0618978) at page_alloc+0x27 slab_zalloc(c0c3a3c0,1,c05d66bc,68c,0) at slab_zalloc+0xb3 uma_zone_slab(c0c3a3c0,1,c05d66bc,68c,0) at uma_zone_slab+0xd6 uma_zalloc_internal(c0c3a3c0,0,1,0,c0c212f0) at uma_zalloc_internal+0x3e bucket_alloc(80,1,c05d66bc,70b,0) at bucket_alloc+0x65 uma_zfree_arg(c0c21240,cbd31000,0,7b6,8000) at uma_zfree_arg+0x2c6 swp_pager_meta_ctl(c2e17d4c,0,0,2,cc3e7cbc) at swp_pager_meta_ctl+0x10f swap_pager_unswapped(c0c49a90,1,c05c0291,bd,cc3e7c54) at swap_pager_unswapped+0x 2a vm_fault(c1135ccc,80f3000,2,8,c249b980) at vm_fault+0x1217 trap_pfault(cc3e7d48,1,80f30f4,27f,80f30f4) at trap_pfault+0x109 trap(2f,2f,2f,52ed,80f30f0) at trap+0x1fc calltrap() at calltrap+0x5 --- trap 0xc, eip = 0x80561e0, esp = 0xbfbff650, ebp = 0xbfbff668 --- -- Yar ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Yet another LOR: vm object/system map
On Tue, Oct 21, 2003 at 10:46:12PM +0400, Yar Tikhiy wrote: This particular LOR happened upon getting out of swap. My knowledge is insufficient to tell if it's a sign of a real problem or just a false positive. See my message from a few days ago where I posted a mail from alc showing how to tell whether these are real or not. Kris pgp0.pgp Description: PGP signature
Re: 20031021 snapshot install has glitches
On Tue, Oct 21, 2003 at 07:10:30PM +0200, Jeroen Ruigrok/asmodai wrote: You cannot set the root password as passwd dumps core on a signal 12. This indicates you're not running the right kernel. I cannot mount any live filesystem CDROM since neither acd0 as acd1 seem to satisfy the installer, they both fail with a file not found error, most likely a device node. This could also be because you're not running the right kernel. Kris pgp0.pgp Description: PGP signature
Re: MBR zapped when panicking?
* Dimitry Andric [Di, 21 Okt 2003 at 20:19 GMT]: Today I had a -CURRENT machine panic on me with a page fault, and something happened that I have seen before: the machine refused to come up afterwards. Closer inspection revealed that the MBR on the boot disk was totally zapped, filled with seemingly random characters. Luckily the disk label was still intact, allowing me to recover the machine reasonably easy. The MBRs on the other disks (see attached dmesg.txt for more info) wasn't touched by the panic. Same happened to me last week, It is a known problem, see 3. point on http://www.freebsd.org/releases/5.2R/todo.html regards tilman ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: MBR zapped when panicking?
On Tue, Oct 21, 2003 at 08:17:24PM +0200, Dimitry Andric wrote: Hi, Today I had a -CURRENT machine panic on me with a page fault, and something happened that I have seen before: the machine refused to come up afterwards. Closer inspection revealed that the MBR on the boot disk was totally zapped, filled with seemingly random characters. This is a known bug in the ATA driver. Tor Egge provided a workaround patch here a few weeks ago. I didn't try it because I can't afford to trash my disks like that again. Kris pgp0.pgp Description: PGP signature
Re: panic with cdrecord-devel @ Mon Oct 20 21:28:57 EEST 2003
On Tuesday 21 October 2003 11:27, Paulius Bulotas wrote: Hello, Any ideas? Paulius my -curret crashes during writing process... ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
ATA boot hang
After I did a buildworld (10/13), I'm getting a hang on boot on a Compaq DeskPro Workstation: ata1: spurious interrupt - status=0x00 error=0x01 ata0-master: pio=0x0c wdma=0x22 udma=0x45 cable=80pin ad0: setting UDMA100 on Intel ICH4 chip GEOM: create disk ad0 dp=0xc62c5570 ad0: Maxtor 57040H4/TAH71DPO ATA-6 disk at ata0-master ad0: 38166MB (78165360 sectors), 77545 C, 16 H, 63 S, 512 B ad0: 16 secs/int, 1 depth queue, UDMA100 GEOM: new disk ad0 ata1-slave: pio=0x0c wdma=0x22 udma=0x cable=40pin ata1-master: WARNING - ATA_IDENTITY soft error (ECC corrected)[0] f:80 typ:165 s(CHS):0/1/1 e(CHS):1023/254/63 s:63 l:78156162 [1] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [2] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [3] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 GEOM: Configure ad0s1, start 32256 length 40015954944 end 40015987199 GEOM: Configure ad0s1a, start 0 length 268435456 end 268435455 GEOM: Configure ad0s1b, start 268435455 length 1588903936 end 1857339391 GEOM: Configure ad0s1c, start 0 length 40015954944 end 40015954943 GEOM: Configure ad0s1d, start 1857339391 length 268435456 end 2125774847 GEOM: Configure ad0s1e, start 2125774847 length 268435456 end 2394210303 GEOM: Configure ad0s1f, start 2394210304 length 27621744640 end 40015954943 I tried to set hw.ata.ata_dma=0 and hw.ata.atapi_dma=0, thinking it might be related. It's not, or at least it still hangs: ata1: spurious interrupt - status=0x00 error=0x01 ata0-master: pio=0x0c wdma=0x22 udma=0x45 cable=80pin ad0: setting PIO4 on Intel ICH4 chip GEOM: create disk ad0 dp=0xc62c5570 ad0: Maxtor 57040H4/TAH71DPO ATA-6 disk at ata0-master ad0: 38166MB (78165360 sectors), 77545 C, 16 H, 63 S, 512 B ad0: 16 secs/int, 1 depth queue, PIO4 GEOM: new disk ad0 ata1-slave: pio=0x0c wdma=0x22 udma=0x cable=40pin ata1-master: WARNING - ATA_IDENTITY soft error (ECC corrected)[0] f:80 typ:165 s(CHS):0/1/1 e(CHS):1023/254/63 s:63 l:78156162 [1] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [2] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [3] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 GEOM: Configure ad0s1, start 32256 length 40015954944 end 40015987199 GEOM: Configure ad0s1a, start 0 length 268435456 end 268435455 GEOM: Configure ad0s1b, start 268435455 length 1588903936 end 1857339391 GEOM: Configure ad0s1c, start 0 length 40015954944 end 40015954943 GEOM: Configure ad0s1d, start 1857339391 length 268435456 end 2125774847 GEOM: Configure ad0s1e, start 2125774847 length 268435456 end 2394210303 GEOM: Configure ad0s1f, start 2394210304 length 27621744640 end 40015954943 And it hangs there. Takes a hard reset to start back up. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ip stack broken?
I removed CPU=athlon from my /etc/make.conf as well as removing -O0 and now it works. I am going to try both one then the other flag to see if it is just one or the other causing the problem, or a combination of both. Doug White wrote: On Sat, 18 Oct 2003, mjoyner wrote: It works fine with a 5.1 kernel. What version is your userland? Doug White wrote: On Fri, 17 Oct 2003, mjoyner wrote: When I use a current kernel, my system will obtain an ip address via dhclient, but thereafter, it cannot see the network. I have tried switching ethernet cards. (used both a dc0 and an fxp0) Am currently using a 5.1-RELEASE kernel to have network access. Advice? Perhaps your DHCP server is handing out bogus info? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ethercons: ethernet console driver for 5-current
On Mon, Oct 20, 2003 at 12:13:27PM -0400, Robert Watson wrote: After reading a FREENIX paper this summer on a Linux ethernet console driver, I took a pass at implementing ethernet console support for FreeBSD. A very worthy cause. I'm sure this has come up before but I think you're the first person to produce actual code. Something that you don't seem to address is security - which surprised me. This driver is similar to the Linux driver, although not binary-compatible on the wire, ... As with the Linux driver, communication happens at the ethernet link layer, using protocol number 0x0666 (entertaining choice). If Linux is using 0x0666, we should probably pick a different number since we're not wire compatible. Though coming up with a common protocol would be even better. In general, the wire protocol is probably the weakest part of the endeavor, but I'm having trouble finding documentation for a decent wire console protocol that doesn't come with an entire network stack attached. MOP (as you point out later) or LAT have the advantage of being more standard, but I'm not sure how well documented they are. A series of tunables and sysctls is available to tune the behavior of ethercons: kern.ethercons.ifnet_raise kern.ethercons.interface_preference kern.ethercons.target Is there any way to specify ifconfig options? media and mediaopts in particular may need to be specified to get the interface to talk to the associated switch. I presume kern.ethercons.target only specifies the MAC address inserted into transmitted packets. Is there any way to restrict the src address(es) of received packets? Does ethercons have any concept of a current session or will it accept incoming packets from anywhere at any time? The latter case would seem undesirable as (IMHO) it makes it too easy to accidently send a command to the wrong system Peter ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ethercons: ethernet console driver for 5-current
Date: Wed, 22 Oct 2003 06:26:18 +1000 From: Peter Jeremy [EMAIL PROTECTED] Sender: [EMAIL PROTECTED] MOP (as you point out later) or LAT have the advantage of being more standard, but I'm not sure how well documented they are. MOP is well documented. It is actually two protocols, one for download (MOP/DL similar to bootp) and one for remote console (MOP/RC). Both are very well and openly documented, but I left all of my documentation at a former job thinking that I was unlikely to ever care about MOP again. But I'm sure some of my old DECnet buddies still have it. (Note that while MOP was included under the DECnet umberella, it is really totally separate from anything else in DECnet and I think pre-existed DECnet Phase II. LAT was officially a proprietary protocol and, while quite efficient, makes several assumptions about network characteristics that make it poorly suited to general use. (I assume HP now owns LAT.) I'd vote for MOP/RC as a simple protocol that is designed for exactly this purpose. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
[PATCH] connect bluetooth configs and examples to the build
Hi Guys, i'd like to commit attached patch. the purpose is to connect etc/bluetooth and share/examples/netgraph/bluetooth to the build. please review and let me know if i missed anything. thanks, max __ Do you Yahoo!? The New Yahoo! Shopping - with improved product search http://shopping.yahoo.com bluetooth.etc.examples.diff Description: bluetooth.etc.examples.diff ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [PATCH] connect bluetooth configs and examples to the build
This looks good to me. It is small enough that I'm afraid I can't add much value here :-) Warner ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: USB Keyboard questions
Ok I will try and get the information down :) from the dmesg uhci0: VIA 83C572 USB controller port 0xc400-0xc41f irq 10 at device 16.0 on pci0 usb0: VIA 83C572 USB controller on uhci0 usb0: USB revision 1.0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered ukbd0: Logitech USB Receiver, rev 1.10/17.00, addr 2, iclass 3/1 kbd0 at ukbd0 ums0: Logitech USB Receiver, rev 1.10/17.00, addr 2, iclass 3/1 ums0: 7 buttons and Z dir. uhub1: Texas Instruments TUSB2046 hub, class 9/0, rev 1.10/1.25, addr 3 uhub1: 4 ports with 4 removable, bus powered ugen0: Logitech Camera, rev 1.00/1.00, addr 4 ugen1: vendor 0x0f4d product 0x1000, rev 1.10/4.01, addr 5 uhci1: VIA 83C572 USB controller port 0xc800-0xc81f irq 11 at device 16.1 on pci0 usb1: VIA 83C572 USB controller on uhci1 usb1: USB revision 1.0 uhub2: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered uhci2: VIA 83C572 USB controller port 0xcc00-0xcc1f irq 7 at device 16.2 on pci0 usb2: VIA 83C572 USB controller on uhci2 usb2: USB revision 1.0 uhub3: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub3: 2 ports with 2 removable, self powered From what I can see the USB used is UHCI, doesnt say in the manual what they use. When I run WinXP It doesnt matter where I plug in the keyboard. In the USB1, USB2 or with the USB-PS/2 convert in the PS/2 port there are no glitches at all. It types like I do. So no added letters in the text im writing. When I run FreeBSD 4.8 I can install it using the keyboard in the USB port, this I cant do with FreeBSD 5.1. When I write text in FreeBSD * when pluged into the USB* ports I get added letters like this should be the text thisi shohuld be the textx (just example). How the letters are added seems random but it happens more often the faster I type. When I run with the USB-PS/2 Converter to plug the keyboard into the PS/2 Port it works without any problems at all in both WinXP and FreeBSD 5.1. I can install FreeBSD 5.1 and can type without any problem. So from my point of view as a user I can see three problems. A) the usb support on my motherboard is bad to worse B) something isn´t right in FreeBSDs USB support. C) A and B in combination. Or im totaly wrong :) and that happens from time to time. I hope this info helps. Peter - Original Message - From: Doug White [EMAIL PROTECTED] To: Peter [EMAIL PROTECTED] Cc: Andre Guibert de Bruet [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Tuesday, October 21, 2003 7:22 PM Subject: Re: USB Keyboard questions On Tue, 21 Oct 2003, Peter wrote: Doesnt look like my Abit KD7 has a legacy support, I can choose BIOS support or OS support for the USB keyboard and mouse. The keyboard works perfectly under winxp and under win200. I dont see the behavior with the letters there and this is using the standard drivers for a HID keyboard as win2000 finds it. I bet BIOS support is the right option. So I think the letter problem was due to my CNet USB 4 way hub. And I dont know why am unable to use the keyboard pluged into the USB port when I install FreeBSD 5.1 but it works when I install FreeBSD 4.8. What kind of usb controller is it? ohci? Also, the Macintosh forums have been complaining about the poor quality of most USB hubs and the problems they cause with printers, etc. Its too bad since hubs should be really easy to build. -- Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Page faults with today's current
On Thursday 16 October 2003 23:00, Jeff Roberson wrote: On Thu, 16 Oct 2003, Arjan van Leeuwen wrote: I just cvsupped and installed a new world and kernel (previous kernel was from October 13), and now my machine gets a page fault when I try to run any GTK2 application (Firebird, Gnome 2). Are others seeing this as well? Arjan If you're running ULE and KSE I just fixed a bug with that. If not, pleae provide a stack trace. You can manually transcribe one by starting a gtk2 application from a console with your DISPLAY variable set appropriately. Thanks, Jeff I just want to mention that this problem is now fixed, with version 1.66 of sched_ule.c. Not only is this problem fixed, SCHED_ULE seems better than ever! The previously reported problem when logging out of GNOME is also fixed, and I also no longer have a lagging mouse when doing buildworlds. Thanks! Arjan ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] !DSPAM:3f8f078a976291302114656 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Sleeping on isp_mboxwaiting with the following non-sleepablelocks held:
So? How about some details and context? I thought was told that being able to use locks in HBAs is fine. I had them on for a while, and then had them off. I turned them on again over a month ago. I'm somewhat surprised to see that a problem shows up now. *I* do the right thing with locks, IMO. I hold them in my module when I enter and release them if/when I leave. Seeing a lock held by some random caller causing me to blow up to me seems to be a hole in the architecture, but I'd be the first to admit that I hardly am up to date on what the rules of the road are now so such an opinion is ill-informed. Comment out ISP_SMPLOCK in isp_freebsd.h. If the problem goes away, we'll make the change back again. -matt p.s.: you have *way* more issues here than locking- you've a bad disk. Anyway, isn't alpha desupported? -Original Message- From: Kris Kennaway [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 21, 2003 9:06 AM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Sleeping on isp_mboxwaiting with the following non-sleepablelocks held: This happened to me just now on alpha: (da0:isp0:0:0:0): Retrying Command (per Sense Data) (da0:isp0:0:0:0): READ(06). CDB: 8 5 f 30 10 0 (da0:isp0:0:0:0): CAM Status: SCSI Status Error (da0:isp0:0:0:0): SCSI Status: Check Condition (da0:isp0:0:0:0): MEDIUM ERROR info:50f30 asc:11,0 (da0:isp0:0:0:0): Unrecovered read error field replaceable unit: e4 actual retry count: 257 (da0:isp0:0:0:0): Retrying Command (per Sense Data) swap_pager: indefinite wait buffer: device: da0b, blkno: 331568, size: 8192 (da0:isp0:0:0:0): READ(06). CDB: 8 5 f 30 10 0 (da0:isp0:0:0:0): CAM Status: SCSI Status Error (da0:isp0:0:0:0): SCSI Status: Check Condition (da0:isp0:0:0:0): MEDIUM ERROR info:50f30 asc:11,0 (da0:isp0:0:0:0): Unrecovered read error field replaceable unit: e4 actual retry count: 257 (da0:isp0:0:0:0): Retries Exhausted swap_pager: I/O error - pagein failed; blkno 331568,size 8192, error 5 vm_fault: pager read error, pid 90537 (aspell) Sleeping on isp_mboxwaiting with the following non-sleepablelocks held: exclusive sleep mutex g_xdown r = 0 (0xfe0006bfdc78) locked @ /a/asami/portbuild/alpha/src-client/sys/geom/geom_io.c:345 witness_warn Stopped at Debugger+0x38: zapnot v0,#0xf,v0 v0=0x0 db trace Debugger() at Debugger+0x38 witness_warn() at witness_warn+0x284 msleep() at msleep+0xa8 isp_mbox_wait_complete() at isp_mbox_wait_complete+0x94 isp_mboxcmd() at isp_mboxcmd+0x258 isp_update_bus() at isp_update_bus+0x2f0 isp_update() at isp_update+0x54 isp_start() at isp_start+0x208 isp_action() at isp_action+0x1bc xpt_run_dev_sendq() at xpt_run_dev_sendq+0x23c xpt_action() at xpt_action+0x2a0 dastart() at dastart+0x220 xpt_run_dev_allocq() at xpt_run_dev_allocq+0xf0 xpt_schedule() at xpt_schedule+0xc0 dastrategy() at dastrategy+0x70 g_disk_start() at g_disk_start+0x1ec g_io_schedule_down() at g_io_schedule_down+0x234 g_down_procbody() at g_down_procbody+0x5c fork_exit() at fork_exit+0x100 exception_return() at exception_return --- root of call graph --- Kris ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Sleeping on isp_mboxwaiting with the following non-sleepablelocks held:
In message [EMAIL PROTECTED], Matthew Jacob writes: So? How about some details and context? I thought was told that being able to use locks in HBAs is fine. I had them on for a while, and then had them off. I turned them on again over a month ago. I'm somewhat surprised to see that a problem shows up now. *I* do the right thing with locks, IMO. I hold them in my module when I enter and release them if/when I leave. Seeing a lock held by some random caller causing me to blow up to me seems to be a hole in the architecture, but I'd be the first to admit that I hardly am up to date on what the rules of the road are now so such an opinion is ill-informed. The lock held in this case, is not some random caller, that is a mutex held specifically to expose device drivers which try to sleep in their -strategy() function. You cannot sleep in the strategy() function because that would hold op I/O, and therefore likely lead to deadlock. -- 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. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
PCI domains?
Is there any concept of PCI domains in the kernel? This is for the DRM, while dealing with a complaint from Linus recently: Please fix the fact that modern PCI is _not_ enumerated with just bus, slot, function. A lot of machines are starting to have a domain number, which allows fro multiple independent PCI subsystems in the same machine. On linux, you can use pci_name(pdev) to get a truly unique descriptor of the device (within the PCI subsystem). It will look something like :00:02.0 for domain 0, bus 0, device 2, function 0. -- Eric Anholt[EMAIL PROTECTED] http://people.freebsd.org/~anholt/ [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 20031021 snapshot install has glitches
-On [20031021 20:52], Kris Kennaway ([EMAIL PROTECTED]) wrote: On Tue, Oct 21, 2003 at 07:10:30PM +0200, Jeroen Ruigrok/asmodai wrote: You cannot set the root password as passwd dumps core on a signal 12. This indicates you're not running the right kernel. It's the kernel on the floppy images provided by the snapshot server, so if it is not the right kernel then that might be a problem on the snapshot server then. Or were you hinting at something else? -- Jeroen Ruigrok van der Werven asmodai(at)wxs.nl / asmodai / kita no mono PGP fingerprint: 2D92 980E 45FE 2C28 9DB7 9D88 97E6 839B 2EAC 625B http://www.tendra.org/ | http://www.in-nomine.org/~asmodai/diary/ How are the mighty fallen... ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Sleeping on isp_mboxwaiting with the following non-sleepablelocks held:
Well, I don't agree with the design here, but it is what it is. I'll make the change that you've added a requirement for. -Original Message- From: Poul-Henning Kamp [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 21, 2003 2:46 PM To: [EMAIL PROTECTED] Cc: 'Kris Kennaway'; [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: Sleeping on isp_mboxwaiting with the following non-sleepablelocks held: In message [EMAIL PROTECTED], Matthew Jacob writes: So? How about some details and context? I thought was told that being able to use locks in HBAs is fine. I had them on for a while, and then had them off. I turned them on again over a month ago. I'm somewhat surprised to see that a problem shows up now. *I* do the right thing with locks, IMO. I hold them in my module when I enter and release them if/when I leave. Seeing a lock held by some random caller causing me to blow up to me seems to be a hole in the architecture, but I'd be the first to admit that I hardly am up to date on what the rules of the road are now so such an opinion is ill-informed. The lock held in this case, is not some random caller, that is a mutex held specifically to expose device drivers which try to sleep in their -strategy() function. You cannot sleep in the strategy() function because that would hold op I/O, and therefore likely lead to deadlock. -- 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. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Sleeping on isp_mboxwaiting with the following non-sleepablelocks held:
On Tue, Oct 21, 2003 at 02:30:21PM -0700, Matthew Jacob wrote: So? How about some details and context? Um, what more details and context do you need? I provided the log of the system activity (specifically, media errors and swap read failure) leading up to the panic, and the ddb backtrace. I thought was told that being able to use locks in HBAs is fine. I had them on for a while, and then had them off. I turned them on again over a month ago. I'm somewhat surprised to see that a problem shows up now. This was apparently triggered by the disk failure, which is not a commonly exercised code path. *I* do the right thing with locks, IMO. I hold them in my module when I enter and release them if/when I leave. Seeing a lock held by some random caller causing me to blow up to me seems to be a hole in the architecture, but I'd be the first to admit that I hardly am up to date on what the rules of the road are now so such an opinion is ill-informed. Comment out ISP_SMPLOCK in isp_freebsd.h. If the problem goes away, we'll make the change back again. I'll do what I can. -matt p.s.: you have *way* more issues here than locking- you've a bad disk. I know, but the system shouldn't blow up with a lock assertion in this failure mode. Anyway, isn't alpha desupported? No. Kris pgp0.pgp Description: PGP signature
Re: 20031021 snapshot install has glitches
On Tue, Oct 21, 2003 at 11:47:32PM +0200, Jeroen Ruigrok/asmodai wrote: -On [20031021 20:52], Kris Kennaway ([EMAIL PROTECTED]) wrote: On Tue, Oct 21, 2003 at 07:10:30PM +0200, Jeroen Ruigrok/asmodai wrote: You cannot set the root password as passwd dumps core on a signal 12. This indicates you're not running the right kernel. It's the kernel on the floppy images provided by the snapshot server, so if it is not the right kernel then that might be a problem on the snapshot server then. Or were you hinting at something else? Can you provide more details, e.g. a copy of the kernel boot messages? Signal 12 is syscall not supported, which means something is badly wrong with the kernel that was booted on the machine (e.g. it is a 4.x kernel). Kris pgp0.pgp Description: PGP signature
Re: [PATCH] connect bluetooth configs and examples to the build
On 2003.10.21 13:47:16 -0700, Maksim Yevmenkin wrote:
i'd like to commit attached patch. the purpose is to connect etc/bluetooth
and share/examples/netgraph/bluetooth to the build. please review and let
me know if i missed anything.
Index: src/etc/bluetooth/Makefile
===
RCS file: src/etc/bluetooth/Makefile
diff -N src/etc/bluetooth/Makefile
--- /dev/null 1 Jan 1970 00:00:00 -
+++ src/etc/bluetooth/Makefile21 Oct 2003 20:20:03 -
@@ -0,0 +1,10 @@
+# $Id: Makefile,v 1.1 2003/10/20 16:48:45 max Exp $
+# $FreeBSD$
+
+FILESDIR=${DESTDIR}/etc/bluetooth
I'm rather sure that you shouldn't include DESTDIR, since bsd.files.mk
does that. Also you should probably use the style from
style.Makefile(5) for new Makefile's.
--
Simon L. Nielsen
FreeBSD Documentation Team
pgp0.pgp
Description: PGP signature
RE: PCI domains?
On 21-Oct-2003 Eric Anholt wrote: Is there any concept of PCI domains in the kernel? This is for the DRM, while dealing with a complaint from Linus recently: Alpha has support for hoses which sounds like the same thing, but that's about it. Please fix the fact that modern PCI is _not_ enumerated with just bus, slot, function. A lot of machines are starting to have a domain number, which allows fro multiple independent PCI subsystems in the same machine. On linux, you can use pci_name(pdev) to get a truly unique descriptor of the device (within the PCI subsystem). It will look something like :00:02.0 for domain 0, bus 0, device 2, function 0. -- Eric Anholt[EMAIL PROTECTED] http://people.freebsd.org/~anholt/ [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] -- John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/ Power Users Use the Power to Serve! - http://www.FreeBSD.org/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PCI domains?
Eric Anholt wrote: Is there any concept of PCI domains in the kernel? This is for the DRM, while dealing with a complaint from Linus recently: Please fix the fact that modern PCI is _not_ enumerated with just bus, slot, function. A lot of machines are starting to have a domain number, which allows fro multiple independent PCI subsystems in the same machine. On linux, you can use pci_name(pdev) to get a truly unique descriptor of the device (within the PCI subsystem). It will look something like :00:02.0 for domain 0, bus 0, device 2, function 0. We don't have much of a concept of this (except possibly Alpha like John mentioned, but I really cannot comment on that). Supporting it wouldn't be terribly magical on our end until we fix busdma to support device-device transfers. Since I don't know much context on the DRM side, what exactly is Linus asking to change, and do we need to worry about it? Scott ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PCI domains?
On Tue, 2003-10-21 at 15:42, Scott Long wrote: Eric Anholt wrote: Is there any concept of PCI domains in the kernel? This is for the DRM, while dealing with a complaint from Linus recently: Please fix the fact that modern PCI is _not_ enumerated with just bus, slot, function. A lot of machines are starting to have a domain number, which allows fro multiple independent PCI subsystems in the same machine. On linux, you can use pci_name(pdev) to get a truly unique descriptor of the device (within the PCI subsystem). It will look something like :00:02.0 for domain 0, bus 0, device 2, function 0. We don't have much of a concept of this (except possibly Alpha like John mentioned, but I really cannot comment on that). Supporting it wouldn't be terribly magical on our end until we fix busdma to support device-device transfers. Since I don't know much context on the DRM side, what exactly is Linus asking to change, and do we need to worry about it? The DRM historically doesn't attach to specific devices itself. The X Server opens a /dev/dri/cardX, sees if it fits its criteria (driver name matches, no unique value currently set), then sets the unique. The unique is a Bus ID in the form PCI:x:y:z. This unique is passed through the XF86DRI protocol to the clients, who iterate over the /dev/dri/cardX looking for one with that unique when they want to open it. Because of this whole system, the DRM also doesn't associate with framebuffer, mmio registers, or other device-specific things by itself -- it's all done by the X Server through things like the addmap ioctl. This makes using bus_space difficult. I'm working on a change so that the DRM attaches to a specific device, and thus has the unique set before the X Server gets to it (well, it's not that way due to backwards compatibility gymnastics, but that's the goal). It was prompted by another developer who's working on standalone DRI, which doesn't use the X Server at all. When the issue of the unique came up, Linus said the quote above. It looks like the hose on alpha is equivalent to a domain, from the linux code. For now I'm just using a domain of 0 on FreeBSD, but if the hoses have numbers that match XFree86's scheme, whatever that is, I'll use that. -- Eric Anholt[EMAIL PROTECTED] http://people.freebsd.org/~anholt/ [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ethercons: ethernet console driver for 5-current
On Wed, 22 Oct 2003, Peter Jeremy wrote: On Mon, Oct 20, 2003 at 12:13:27PM -0400, Robert Watson wrote: After reading a FREENIX paper this summer on a Linux ethernet console driver, I took a pass at implementing ethernet console support for FreeBSD. A very worthy cause. I'm sure this has come up before but I think you're the first person to produce actual code. Something that you don't seem to address is security - which surprised me. Well, in a sense I did: the environment I use the ethernet console in is one of trust of the link layer. I use DHCP, PXE, and NFS roots on the boxes in question. That said, I should have more carefully documented the security assumptions: that there will be no malicious attackers on the wire, and because it's a link layer protocol, there will be no routing of the packets in question from untrusted segments. I did look at introducing cryptographic protections, but there are a number of problems with this: (1) I wanted to minimize the amount of transient protocol state. The current implementation does not make any reliable transmission guarantees. In order to prevent replay attacks, we would need to rely on reliable timestamps or sequence numbers. In order to establish sequence number legitimacy, we'd need to have a protocol component that establishes freshness. (2) It introduces the issue of key management. In my environment, since the system configuration is shipped in the clear anyway, the keying material would also get transfered in the clear, which would make the whole arrangement somewhat moot. The minimalist solution would introduce just keyed integrity, perhaps using HMAC-MD5 and a shared secret. The problem does come back to sequencing: if you assume the LAN is subject to replay and monitoring, timestamps aren't sufficient, you actually need sequencing and freshness. This means doing a Needham-Schroeder shared key exchange or a related notion to get a session key. This requires the client and server to detect and handle reboots, for example. I am willing to do the implementation, but without a wire protocol worth committing to yet, I was unwilling to invest the time. This driver is similar to the Linux driver, although not binary-compatible on the wire, ... As with the Linux driver, communication happens at the ethernet link layer, using protocol number 0x0666 (entertaining choice). If Linux is using 0x0666, we should probably pick a different number since we're not wire compatible. Though coming up with a common protocol would be even better. The problem with the Linux protocol was that it had no concept of direction. I'm still hopeful I'll find a better wire protocol to model the implementation on. In general, the wire protocol is probably the weakest part of the endeavor, but I'm having trouble finding documentation for a decent wire console protocol that doesn't come with an entire network stack attached. MOP (as you point out later) or LAT have the advantage of being more standard, but I'm not sure how well documented they are. I have found some documentation of MOP and LAT, although it's not clear to me there's enough information to do an independent implementation without referencing an existing one. There is a Linux implementation, so I'll take a look at that. One of my concerns here is that it could be these protocols require a fairly deep DECnet stack, and I'm not all that interested in building big protocol stacks. However, until I'm done with the reading, I can't commit myself either way :-). A series of tunables and sysctls is available to tune the behavior of ethercons: kern.ethercons.ifnet_raise kern.ethercons.interface_preference kern.ethercons.target Is there any way to specify ifconfig options? media and mediaopts in particular may need to be specified to get the interface to talk to the associated switch. Currently, no. If we do want to add this sort of infrastructure, we might want to provide common infrastructure for both the diskless booting environment, which also attempts to raise the interface before getting to the userland configuration. I presume kern.ethercons.target only specifies the MAC address inserted into transmitted packets. Is there any way to restrict the src address(es) of received packets? Does ethercons have any concept of a current session or will it accept incoming packets from anywhere at any time? The latter case would seem undesirable as (IMHO) it makes it too easy to accidently send a command to the wrong system Right now, ethercons defaults to a broadcast for outgoing, and accepts any locally destined packet on the inbound. There is no notion of session. This is both an upside and a downside: I've actually taken advantage of this behavior to monitor using a common monitoring host, and then used an interactive session simultaenously from another host. However, my hosts all have fairly different
Re: [PATCH] connect bluetooth configs and examples to the build
Simon,
i'd like to commit attached patch. the purpose is to connect etc/bluetooth
and share/examples/netgraph/bluetooth to the build. please review and let
me know if i missed anything.
Index: src/etc/bluetooth/Makefile
===
RCS file: src/etc/bluetooth/Makefile
diff -N src/etc/bluetooth/Makefile
--- /dev/null 1 Jan 1970 00:00:00 -
+++ src/etc/bluetooth/Makefile 21 Oct 2003 20:20:03 -
@@ -0,0 +1,10 @@
+# $Id: Makefile,v 1.1 2003/10/20 16:48:45 max Exp $
+# $FreeBSD$
+
+FILESDIR= ${DESTDIR}/etc/bluetooth
I'm rather sure that you shouldn't include DESTDIR, since bsd.files.mk
does that.
got it. thanks for noticing this :)
Also you should probably use the style from
style.Makefile(5) for new Makefile's.
could you please be more specific? i took a quick look at style.Makefile(5)
page and could not find anything related to my case.
thanks,
max
__
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search
http://shopping.yahoo.com
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [PATCH] connect bluetooth configs and examples to the build
On 2003.10.21 16:40:57 -0700, Maksim Yevmenkin wrote: Also you should probably use the style from style.Makefile(5) for new Makefile's. could you please be more specific? i took a quick look at style.Makefile(5) page and could not find anything related to my case. Sorry, I should have been more specific. I was thinking about the whitespace part: o Typically, there is one ASCII tab between VAR= and the value in order to start the value in column 9. An ASCII space is allowed for vari- able names that extend beyond column 9. A lack of whitespace is also allowed for very long variable names. I don't say that you must to follow that (I'm just a doc guy), I just want to point out that it's there :-). -- Simon L. Nielsen FreeBSD Documentation Team pgp0.pgp Description: PGP signature
Re: make release...
On Tue, Oct 21, 2003 at 04:51:22PM +0930, Daniel O'Connor wrote: [...] Either apply the patch I attached and add CPNOTCVS= to your make release options, or check out the repository. In HEAD, a similar functionality is already provided through the use of the EXTSRCDIR variable. JFYI. Ahh interesting.. My patch overrides all of the checkouts (src, port doc) though. --- 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 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: MBR zapped when panicking?
On Tuesday 21 October 2003 20:54, Kris Kennaway wrote: On Tue, Oct 21, 2003 at 08:17:24PM +0200, Dimitry Andric wrote: Hi, Today I had a -CURRENT machine panic on me with a page fault, and something happened that I have seen before: the machine refused to come up afterwards. Closer inspection revealed that the MBR on the boot disk was totally zapped, filled with seemingly random characters. This is a known bug in the ATA driver. Tor Egge provided a workaround patch here a few weeks ago. I didn't try it because I can't afford to trash my disks like that again. Uhmm, at least a confirmation! Some weeks ago (03/09/18) I wrote the attached mail. Thanks, -Harry Kris From [EMAIL PROTECTED] Thu Sep 18 04:25:08 2003 From: Harald Schmalzbauer [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: 5.1-rel deleted it's own MBR Date: Thu, 18 Sep 2003 04:25:08 +0200 User-Agent: KMail/1.5.3 X-Birthday: 06 Oktober 1972 X-Name: Harald Schmalzbauer X-Phone1: +49 (0) 163 555 3237 X-Phone2: +49 (0) 89 18947781 X-Address: Munich, 80686 X-Country: Germany MIME-Version: 1.0 Content-Type: multipart/signed; protocol=application/pgp-signature; micalg=pgp-sha1; boundary=Boundary-02=_LeRa/eu3n+wIObY; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Message-Id: [EMAIL PROTECTED] Status: RO X-Status: S X-KMail-EncryptionState: X-KMail-SignatureState: --Boundary-02=_LeRa/eu3n+wIObY Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: quoted-printable Content-Description: signed data Content-Disposition: inline Hi all, big mysterious bug is lingering somwhere. (Machine: C3, 256MB, 2x 30GB 2,5= =20 IDE, SIL0680 controller) One of my drives failed with the following recovered from messages: Sep 16 01:47:44 tek kernel: ad4: WRITE command timeout tag=3D0 serv=3D0 -=20 resetting Sep 16 01:47:45 tek kernel: ata2: resetting devices .. Sep 16 01:47:45 tek kernel: ad4: removed from configuration Sep 16 01:47:45 tek kernel: ar0: WARNING - mirror lost Sep 16 01:47:45 tek kernel: ad4: deleted from ar0 disk0 Sep 16 01:47:45 tek kernel: done This was at 1:47 but the machine ran until about 5:30. Then it died (no=20 message!) When I tried to reboot, BIOS complained about missing MBR. And indeed, when= I=20 opened the server and connected the drives to another box, BOTH drives had = no=20 partition table I got a correct bsdlabel from both, ad6 and ad6s1. How can this happen? Bug in ata? Bug in GEOM? Nobody was loged in and also nobody can log in so the machine deleted it.=20 That's really sure! My fix was to use the fixit CD and wrote a new one with: fdisk -I -B -b /boot/boot1 ar0 fdisk -u ar0 (to change the starting sector from 63 to 0) fsck found a few errors but the server is up and running again. S=F8ren: I remember you're planning better RAID management support. Will it= be=20 possible to control the ar0 by the controller's BIOS in the future? When I rebuilt the array with the BIOS (which took 6 hours!) FreeBSD still= =20 reported a degraded RAID1! This was really annoying Thanks, =2DHarry --Boundary-02=_LeRa/eu3n+wIObY Content-Type: application/pgp-signature Content-Description: signature -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQA/aReLBylq0S4AzzwRAluJAJsFpTckdf4fiDhXELfIVvwInZNU5ACePNOH P7m44UKfnXxw7ioN/IGXDmg= =fh+e -END PGP SIGNATURE- --Boundary-02=_LeRa/eu3n+wIObY-- pgp0.pgp Description: signature
Ath0 Crash the PC
I have a Atheros card running as Ap in the last version of Freebsd 5.1 current, with the last Ath drivers files, the problem start when I make a simple ftp with more than maybe 5mb the card crash and crash the computer, the screen say ath0:timeout and i need reset it to make it work again. to make it crash doesn't take longer than 2min. I tried too make a troughput test with ftp traffic in both ways and is worse crash after 40 sec Troughput test logs: http://202.49.92.224/atheros/TESTFAst.html my settings: ifconfig ath0 inet up ssid mynet media OFDM/54Mbps mode 11a mediaopt hostap mediaopt turbo sysctl net.link.ether.bridge.enable=1 sysctl net.link.ether.bridge_cfg=ath0 rl0 sysctl net.link.ether.bridge_ipfw=1 sysctl net.inet.ip.forwarding=1 thanks -- Marcos Biscaysaqu Systems Administrator ThePacific.Net Ltd. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 20031021 snapshot install has glitches
asmodai You cannot set the root password as passwd dumps core on a signal 12. % pwd /usr/src % echo **/*(.)|xargs grep 'You cannot set the root password' % It should not be an message of passwd(1) or other sources, so it would be hard to reproduce (if we can) what you've seen. What you've tried and got an error? -- - Makoto `MAR' Matsushita ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Buildworld fails in 5.1-CURRENT in wall- SOLVED
Dag-Erling Smørgrav wrote: M. Warner Losh [EMAIL PROTECTED] writes: find /usr/obj -name .depend or better yet rm -rf /usr/obj/* *ahem* the correct incantation is: # cd /usr/src # make cleandir # make cleandir DES Removing the /usr/obj/* tree worked, back in business. Will have to take a closer look at the 'master' Makefile, as I didn't see the cleandir target at first glance, so had been using 'make clean make buildworld' for previous builds- I take it this is NOT needed as the build process does a 'make clean' prior to building? Thanks to all... Scott ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ath0 Crash the PC
I using a pentium III 350Mghz 256 MB RAM , uniprocessor, PCI Atheros Card Netgear WAG311 a/b/g atheros chipset AR5212, same thing with a DLINK PCI AR5212, the last update of my source was yesterday, anyway I have the same problem with older versions. I trying now with a diferent PC to see what happend. I hope this infromation help, pls tell me if you need more information this is my dmeg; SAM# dmesg 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.1-CURRENT #5: Tue Oct 21 13:53:07 NZDT 2003 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/IPFW Preloaded elf kernel /boot/kernel/kernel at 0xc0971000. Preloaded elf module /boot/kernel/acpi.ko at 0xc0971244. Timecounter i8254 frequency 1193182 Hz quality 0 CPU: AMD Duron(tm) (959.45-MHz 686-class CPU) Origin = AuthenticAMD Id = 0x631 Stepping = 1 Features=0x183fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR AMD Features=0xc044RSVD,AMIE,DSP,3DNow! real memory = 369033216 (351 MB) avail memory = 348774400 (332 MB) Pentium Pro MTRR support enabled npx0: [FAST] npx0: math processor on motherboard npx0: INT 16 interface acpi0: AMIINT VIA_K7 on motherboard pcibios: BIOS version 2.10 Using $PIR table, 9 entries at 0xc00f7e00 acpi0: Power Button (fixed) Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x808-0x80b on acpi0 acpi_cpu0: CPU on acpi0 acpi_button0: Power Button on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 pcib0: slot 9 INTA is routed to irq 10 pcib0: slot 19 INTA is routed to irq 12 agp0: VIA Generic host to PCI bridge mem 0xe000-0xe3ff at device 0.0 on pci0 pcib1: PCI-PCI bridge at device 1.0 on pci0 pci1: PCI bus on pcib1 pcib0: slot 1 INTA is routed to irq 11 pcib1: slot 0 INTA is routed to irq 11 pci1: display, VGA at device 0.0 (no driver attached) ath0: Atheros 5212 mem 0xdfff-0xdfff irq 10 at device 9.0 on pci0 ath0: [MPSAFE] ath0: 11a rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps ath0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps ath0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps ath0: turbo rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps ath0: 802.11 address: 00:09:5b:92:41:e2 isab0: PCI-ISA bridge at device 17.0 on pci0 isa0: ISA bus on isab0 atapci0: VIA 8233A UDMA133 controller port 0xfc00-0xfc0f at device 17.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata0: [MPSAFE] ata1: at 0x170 irq 15 on atapci0 ata1: [MPSAFE] rl0: RealTek 8139 10/100BaseTX port 0xec00-0xecff mem 0xdffeff00-0xdffe irq 12 at device 19.0 on pci0 rl0: Ethernet address: 00:20:ed:2d:8b:a2 miibus0: MII bus on rl0 rlphy0: RealTek internal media interface on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fdc0: cmd 3 failed at out byte 1 of 3 sio0 port 0x3f8-0x3ff irq 4 on acpi0 sio0: type 16550A atkbdc0: Keyboard controller (i8042) port 0x64,0x60 irq 1 on acpi0 atkbd0: AT Keyboard flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 fdc0: cmd 3 failed at out byte 1 of 3 orm0: Option ROM at iomem 0xc-0xcbfff on isa0 pmtimer0 on isa0 fdc0: cannot reserve I/O port range (6 ports) ppc0: parallel port not found. sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x300 sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 Timecounter TSC frequency 959452732 Hz quality 800 Timecounters tick every 10.000 msec ipfw2 initialized, divert enabled, rule-based forwarding enabled, default to accept, logging disabled acpi_cpu: throttling enabled, 16 steps (100% to 6.2%), currently 100.0% GEOM: create disk ad0 dp=0xc377c070 ad0: 19130MB SAMSUNG SV0221H [38869/16/63] at ata0-master UDMA100 Mounting root from ufs:/dev/ad0s1a WARNING: / was not properly dismounted WARNING: /tmp was not properly dismounted WARNING: /usr was not properly dismounted WARNING: /var was not properly dismounted ath0: promiscuous mode enabled rl0: promiscuous mode enabled This show the screen when crash: fatal 12 : page fault while in kernel mode fault virtual address : 0x3aaba fault code = supervisor read, page not present 0x8 : 0xc063678 stack pointer = 0x10 : 0xd16e2c2c frame pointer = 0x10 : 0xd16e2c30 code segment = base 0x0, limit 0xf, type 0x1b = DPL0, pres 1, def32 1, gran 1 Processor eflags = interrupt enabled, resume, IOLP=0 Current process = 21 (swi7 : task queue) trap number = 12 panic : page fault syncing disk .. 2385 2385 2385 2385 2385 2385 2385 2385 2385 ath0: device timeout ad0: Warring - FLUSHCACHE recovered from missing interrupt ad0: Warring - WRITE_DMA recovered
Question on freeBSD (5.1-CURRENT) portupgrade of Perl 5.8 andlibiconv 1.9.1_3
Hey all. In doing a portupgrade -RvN for windowmaker, Perl and libiconv were recompiled. I saved the log output and noticed several oddities I was wondering if anyone can explain? 1..several settings come up as undefined during the Perl build, namely: $i_malloc $d_setegid $d_seteuid $i_iconv These don't look troubling by themselves dur to 'autoconf magic,' but the next one for libiconv is more bothersome: From libiconv 1.9.1_3 configure: checking if libtool supports shared libraries... yes *** Warning: the command libtool uses to detect shared libraries, *** /usr/bin/file, produces output that libtool cannot recognize. *** The result is that libtool may fail to recognize shared libraries *** as such. This will affect the creation of libtool libraries that *** depend on shared libraries, but programs linked with such libtool *** libraries will work regardless of this problem. Nevertheless, you *** may want to report the problem to your system manager and/or to *** [EMAIL PROTECTED] Any ideas? Also, is there a way to pass configure options to portupgrade, or should I run make clean ./configure for each port in an 'upgrade chain' and then force portupgrade to not make clean prior to building/installing? Thanks, Scott ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Question on freeBSD (5.1-CURRENT) portupgrade of Perl 5.8 andlibiconv 1.9.1_3
On Wed, 2003-10-22 at 01:14, Scott W wrote: Hey all. In doing a portupgrade -RvN for windowmaker, Perl and libiconv were recompiled. I saved the log output and noticed several oddities I was wondering if anyone can explain? 1..several settings come up as undefined during the Perl build, namely: $i_malloc $d_setegid $d_seteuid $i_iconv These don't look troubling by themselves dur to 'autoconf magic,' but the next one for libiconv is more bothersome: From libiconv 1.9.1_3 configure: checking if libtool supports shared libraries... yes *** Warning: the command libtool uses to detect shared libraries, *** /usr/bin/file, produces output that libtool cannot recognize. *** The result is that libtool may fail to recognize shared libraries *** as such. This will affect the creation of libtool libraries that *** depend on shared libraries, but programs linked with such libtool *** libraries will work regardless of this problem. Nevertheless, you *** may want to report the problem to your system manager and/or to *** [EMAIL PROTECTED] Any ideas? This is a byproduct of the new dynamic root layout in -CURRENT. Basically, older versions of libtool try to do file on /usr/lib/libc.so. Recent versions of -CURRENT put libc.so in /lib. Therefore, this fails. I haven't noticed any real problems because of this, but I have reported it to the libtool maintainer, [EMAIL PROTECTED] Also, is there a way to pass configure options to portupgrade, or should I run make clean ./configure for each port in an 'upgrade chain' and then force portupgrade to not make clean prior to building/installing? Configure arguments? No. However, you can use the -m option to pass make arguments (e.g. -DWITH_FOO). To pass configure arguments, you'd have to edit the port Makefiles directly. Joe Thanks, Scott ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED] -- PGP Key : http://www.marcuscom.com/pgp.asc signature.asc Description: This is a digitally signed message part
Re: Question on freeBSD (5.1-CURRENT) portupgrade of Perl 5.8andlibiconv 1.9.1_3
Joe Marcus Clarke wrote: On Wed, 2003-10-22 at 01:14, Scott W wrote: Hey all. In doing a portupgrade -RvN for windowmaker, Perl and libiconv were recompiled. I saved the log output and noticed several oddities I was wondering if anyone can explain? 1..several settings come up as undefined during the Perl build, namely: $i_malloc $d_setegid $d_seteuid $i_iconv These don't look troubling by themselves dur to 'autoconf magic,' but the next one for libiconv is more bothersome: From libiconv 1.9.1_3 configure: checking if libtool supports shared libraries... yes *** Warning: the command libtool uses to detect shared libraries, *** /usr/bin/file, produces output that libtool cannot recognize. *** The result is that libtool may fail to recognize shared libraries *** as such. This will affect the creation of libtool libraries that *** depend on shared libraries, but programs linked with such libtool *** libraries will work regardless of this problem. Nevertheless, you *** may want to report the problem to your system manager and/or to *** [EMAIL PROTECTED] Any ideas? This is a byproduct of the new dynamic root layout in -CURRENT. Basically, older versions of libtool try to do file on /usr/lib/libc.so. Recent versions of -CURRENT put libc.so in /lib. Therefore, this fails. I haven't noticed any real problems because of this, but I have reported it to the libtool maintainer, [EMAIL PROTECTED] Great. That makes sense, as file will return symbolic link rather than an ELF executable, should be a minor adjustment by the maintainer. Also makes sense on libc in /lib - always disturbs me when I see 'important' system binaries mounted on the /usr filesystem! Also, is there a way to pass configure options to portupgrade, or should I run make clean ./configure for each port in an 'upgrade chain' and then force portupgrade to not make clean prior to building/installing? Configure arguments? No. However, you can use the -m option to pass make arguments (e.g. -DWITH_FOO). To pass configure arguments, you'd have to edit the port Makefiles directly. Joe Actually, it _looks_ like there's somewhat of a standard in place within the port Makefiles defining CONFIGURE_ARGS, but I haven't searched through all of them- anyone know if this is a 'freeBSD Makefile standard' that can (generally) be counted on? If so, at least for specific ports builds, you should be able to define it on the command line to make (as Joe stated) or via passing the parameter to make for portupgradealthough that change doesn't get saved anywhere and will be clobbered by the next cvsup- any clean way to avoid this? I need to build apache for this system at some point, and somehow I'm not just seeing the defaults as likely to 'fit everyone' on that one? Thanks again, Scott Thanks, Scott ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
