From owner-freebsd-hackers@FreeBSD.ORG Sat Sep 20 22:20:55 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3230F16A4BF for ; Sat, 20 Sep 2003 22:20:55 -0700 (PDT) Received: from ns1.unixmexico.net (ns1.unixmexico.net [69.10.138.161]) by mx1.FreeBSD.org (Postfix) with ESMTP id A7DC043F75 for ; Sat, 20 Sep 2003 22:20:51 -0700 (PDT) (envelope-from nbari@unixmexico.com) Received: (qmail 12015 invoked by uid 85); 21 Sep 2003 05:20:51 -0000 Received: from nbari@unixmexico.com by ns1.unixmexico.net by uid 82 with qmail-scanner-1.16 (hbedv: 6.20.0.1/6.20.0.36. Clear:. Processed in 0.30441 secs); 21 Sep 2003 05:20:51 -0000 Received: from ns1.unixmexico.net (HELO mail.unixmexico.com) ([69.10.138.161]) (envelope-sender ) by ns1.unixmexico.net (qmail-ldap-1.03) with SMTP for ; 21 Sep 2003 05:20:51 -0000 Received: from 148.243.211.1 (SquirrelMail authenticated user nbari@unixmexico.com) by mail.unixmexico.com with HTTP; Sun, 21 Sep 2003 00:20:51 -0500 (CDT) Message-ID: <45984.148.243.211.1.1064121651.squirrel@mail.unixmexico.com> Date: Sun, 21 Sep 2003 00:20:51 -0500 (CDT) From: nbari@unixmexico.com To: freebsd-isp@freebsd.org User-Agent: SquirrelMail/1.4.1 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 Importance: Normal X-Mailman-Approved-At: Sun, 21 Sep 2003 05:05:51 -0700 Subject: server rebooted X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Sep 2003 05:20:55 -0000 Hello. I have a dedicated server the one was up for more than 84 days but this Friday 19, suddenly the server was rebooted. this is the output of the "last" command # last | grep reboot reboot ~ vie 19 sep 13:55 I already have check the logs but i can't found any hint that could help me to know why the server as was rebooted. Any idea on what to check or how to know what makes the server to reboot? thanks. From owner-freebsd-hackers@FreeBSD.ORG Sun Sep 21 05:53:11 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 829CE16A4B3; Sun, 21 Sep 2003 05:53:11 -0700 (PDT) Received: from unbreakable.homeunix.org (a213-22-54-44.netcabo.pt [213.22.54.44]) by mx1.FreeBSD.org (Postfix) with ESMTP id 912DF43FE3; Sun, 21 Sep 2003 05:53:10 -0700 (PDT) (envelope-from sub_0@netcabo.pt) Received: from [192.168.1.2] (unknown [192.168.1.2]) by unbreakable.homeunix.org (unknown) with ESMTP id 6437313CAE; Sun, 21 Sep 2003 13:53:08 +0100 (WEST) From: Mario Freitas To: freebsd-ipfw@freebsd.org Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-V4jJ/eJUIauNTyrxyjUh" Message-Id: <1064148796.973.50.camel@suzy.unbreakable.homeunix.org> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.4 Date: Sun, 21 Sep 2003 13:53:16 +0100 cc: freebsd-hackers@freebsd.org Subject: jails & ipfw + nat X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: sub_0@netcabo.pt List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Sep 2003 12:53:11 -0000 --=-V4jJ/eJUIauNTyrxyjUh Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: quoted-printable Hi, I recently configured a jail on a FreeBSD gateway doing nat for the interface alias (the jail address, say 192.168.J.J). I tried with natd and ipnat too. However there are some problems I still do not understand. First when I added "nameserver 192.168.X.X" (the nameserver running outside the jail environment) to the jail, every query to the name server is made via the loopback interface instead of the internal interface, or $intif (where I have 192.168.X.X plus 192.168.J.J). Shouldn't the packet travel(virtually) via the $intif interface (as if the request was coming from any machine on the LAN)? Also, the packets are travelling through the loopback interface, where bind _is not_ listening :) (another weird behaviour?) Second, I've tried using, unsuccessfully, many ipfw rules so any user inside the jail environment can establish statefully any tcp connection to the internet. What I do not understand is why the request does not (virtually) come through $intif (192.168.J.J). Inside the jail, after executing telnet www.google.com 80, tcpdump -i $intif(outside the jail) shows nothing, but tcpdump -i $extif(also outside) shows packets coming from www.google.com:80 to $extip, both in natd and ipnat cases: ipfw logs the packet being denied tcp from www.google.com:80 to $extip in via $extif (keep-state is not triggered). Any clarification would be appreciated. Sincerely, --=20 M=E1rio Freitas (sub_0@netcabo.pt) N=FAcleo Portugu=EAs de FreeBSD (NPF) --=-V4jJ/eJUIauNTyrxyjUh Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQA/bZ88mOO46MB/5oURAoXfAKCE9LWe65Ne4t7LpWQ1uUdi0hS5YwCgsr5y vp8WuM/g18zTFsy9O57gsuc= =tUx2 -----END PGP SIGNATURE----- --=-V4jJ/eJUIauNTyrxyjUh-- From owner-freebsd-hackers@FreeBSD.ORG Sun Sep 21 14:08:36 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6B0A716A4E9 for ; Sun, 21 Sep 2003 14:08:36 -0700 (PDT) Received: from mail.yazzy.org (yazzy.org [217.8.140.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id CC2C843FF3 for ; Sun, 21 Sep 2003 14:08:34 -0700 (PDT) (envelope-from masta@wifibsd.org) Received: from localhost (localhost [127.0.0.1]) by mail.yazzy.org (Postfix) with ESMTP id 550203980F; Sun, 21 Sep 2003 23:08:27 +0200 (CEST) Received: from mail.yazzy.org ([127.0.0.1]) by localhost (urukhai.yazzy.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 50592-09; Sun, 21 Sep 2003 23:07:56 +0200 (CEST) Received: from wifibsd.org (localhost [127.0.0.1]) by mail.yazzy.org (Postfix) with SMTP id 43C4039812; Sun, 21 Sep 2003 23:07:53 +0200 (CEST) Received: from 12-238-113-137.client.attbi.com ([12.238.113.137]) (SquirrelMail authenticated user masta@wifibsd.org) by mail.yazzy.org with HTTP; Sun, 21 Sep 2003 16:07:54 -0500 (CDT) Message-ID: <1132.12.238.113.137.1064178474.squirrel@mail.yazzy.org> Date: Sun, 21 Sep 2003 16:07:54 -0500 (CDT) From: "masta" To: X-Priority: 3 Importance: Normal X-Mailer: SquirrelMail (version 1.2.11) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit cc: freebsd-hackers@freebsd.org Subject: X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: masta@wifibsd.org List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Sep 2003 21:08:36 -0000 Mario Freitas wrote: > Hi, > I recently configured a jail on a FreeBSD gateway doing nat for the > interface alias (the jail address, say 192.168.J.J). I tried with natd > and ipnat too. > However there are some problems I still do not understand. First > when I added "nameserver 192.168.X.X" (the nameserver running outside > the jail environment) to the jail, every query to the name server is > made via the loopback interface instead of the internal interface, or > $intif (where I have 192.168.X.X plus 192.168.J.J). Shouldn't the packet > travel(virtually) via the $intif interface (as if the request was coming > from any machine on the LAN)? Also, the packets are travelling through > the loopback interface, where bind _is not_ listening :) (another weird > behaviour?) This is normal. Jails use the loopback interface. You should alter your configuration accordingly. > Second, I've tried using, unsuccessfully, many ipfw rules so any user > inside the jail environment can establish statefully any tcp connection > to the internet. What I do not understand is why the request does not > (virtually) come through $intif (192.168.J.J). Because the jail(8) uses the loopback interface. [snip] I seem to recall some old discussion about the roadmap for jail(8), and somebody mentioned the consideration of a set of patches to virtualize the entire freebsd network stack to facilitate the type of feature you thought jail's have, but don't. __ __ _ | \/ | __ _ ___| |_ __ _ | |\/| |/ _` / __| __/ _` | | | | | (_| \__ \ || (_| | |_| |_|\__,_|___/\__\__,_| masta@wifibsd.org http://wifibsd.org From owner-freebsd-hackers@FreeBSD.ORG Sun Sep 21 15:55:58 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5E54B16A4B3 for ; Sun, 21 Sep 2003 15:55:58 -0700 (PDT) Received: from mail.rdstm.ro (mail.rdstm.ro [193.231.233.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id C11FB43F75 for ; Sun, 21 Sep 2003 15:55:55 -0700 (PDT) (envelope-from aanton@reversedhell.net) Received: from reversedhell.net (casa_auto [81.196.32.25]) by mail.rdstm.ro (8.12.10/8.12.1) with ESMTP id h8LMtom6004786; Mon, 22 Sep 2003 01:55:50 +0300 Message-ID: <3F6E2DCD.9080704@reversedhell.net> Date: Mon, 22 Sep 2003 02:01:33 +0300 From: Alin-Adrian Anton User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.5b) Gecko/20030906 Thunderbird/0.2 X-Accept-Language: en-us, en MIME-Version: 1.0 To: nbari@unixmexico.com, freebsd-hackers@freebsd.org References: <45984.148.243.211.1.1064121651.squirrel@mail.unixmexico.com> In-Reply-To: <45984.148.243.211.1.1064121651.squirrel@mail.unixmexico.com> Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms020704030209060100030201" Subject: Re: server rebooted X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Sep 2003 22:55:58 -0000 This is a cryptographically signed message in MIME format. --------------ms020704030209060100030201 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit nbari@unixmexico.com wrote: >Hello. > >I have a dedicated server the one was up for more than 84 days but this >Friday 19, suddenly the server was rebooted. > >this is the output of the "last" command > ># last | grep reboot >reboot ~ vie 19 sep 13:55 > > >I already have check the logs but i can't found any hint that could help >me to know why the server as was rebooted. > > >Any idea on what to check or how to know what makes the server to reboot? > >thanks. > >_______________________________________________ >freebsd-hackers@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-hackers >To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > > > > Check all the logs, not only the lastlog. Start with /var/log/messages, and continue there. See behaviour of all the installed daemons and what did they log. If the kernel is not debug-enabled, there are chances you won't find out certain crashes. A power-off problem will be noticed because of disrupted timestamps in the logs, and no shutting down messages from the daemons and the kernel. And if you don't CAREFULLY and PATIENTLY find anything in the logs, check them for intrusion, if you have some other logging device in the network check that one too for weird traffic etc. But I think I'm paranoid :PpPp Alin. --------------ms020704030209060100030201 Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIJATCC AtswggJEoAMCAQICAwqocjANBgkqhkiG9w0BAQQFADBiMQswCQYDVQQGEwJaQTElMCMGA1UE ChMcVGhhd3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNv bmFsIEZyZWVtYWlsIElzc3VpbmcgQ0EwHhcNMDMwOTAxMjI1NzE3WhcNMDQwODMxMjI1NzE3 WjBJMR8wHQYDVQQDExZUaGF3dGUgRnJlZW1haWwgTWVtYmVyMSYwJAYJKoZIhvcNAQkBFhdh YW50b25AcmV2ZXJzZWRoZWxsLm5ldDCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEB AOFQIPsz6GsCqBulxVsYpJ2I0jfIBLPuNsNpkK4qh1TxzVVJ3dOd3giojIFX2Vnhm7s1RdTm 0bPJ720UVqdsxuLtQ0hIBbg+oK492I8Vd8rAH7ByDE++L8dRaAP6IcUGZQh2/7GnjCdrnmta vFJ02oya/5RMqcvUIe3ggFlzpSw0nDuRbTOKfRJAUP4wI56SY63E9gUQL0IBqzEKzcJQTAnk G0/C8MKTMpFBZ89pwNvFaOuPXLCIPIiPPy/luxEOgjYz9mwEzDShznISwDg327swWmNXEcDF ZRnpnQya41RPAGJiw8e6xirvPpn3Evd07UVEovGsP2CHoPfA/JvdK3UCAwEAAaM0MDIwIgYD VR0RBBswGYEXYWFudG9uQHJldmVyc2VkaGVsbC5uZXQwDAYDVR0TAQH/BAIwADANBgkqhkiG 9w0BAQQFAAOBgQAsf0Fs94uUNfAA2GC/CXQaccTiQJm7rRwhe+ttblOD0PH9jSUauQAKP7sh BNBEhJ+j5JU8GlTEi/ZKCBGqFTJm2pvbvy7QdQUe2J3VQwmCGYiJTu/m1iAVwhhRVtzZVC/u 1EnXDzel2vnkJ5wOP5en2N8wd1wpAii1A1K3ck7q0TCCAtswggJEoAMCAQICAwqocjANBgkq hkiG9w0BAQQFADBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMcVGhhd3RlIENvbnN1bHRpbmcg KFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWlsIElzc3Vpbmcg Q0EwHhcNMDMwOTAxMjI1NzE3WhcNMDQwODMxMjI1NzE3WjBJMR8wHQYDVQQDExZUaGF3dGUg RnJlZW1haWwgTWVtYmVyMSYwJAYJKoZIhvcNAQkBFhdhYW50b25AcmV2ZXJzZWRoZWxsLm5l dDCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAOFQIPsz6GsCqBulxVsYpJ2I0jfI BLPuNsNpkK4qh1TxzVVJ3dOd3giojIFX2Vnhm7s1RdTm0bPJ720UVqdsxuLtQ0hIBbg+oK49 2I8Vd8rAH7ByDE++L8dRaAP6IcUGZQh2/7GnjCdrnmtavFJ02oya/5RMqcvUIe3ggFlzpSw0 nDuRbTOKfRJAUP4wI56SY63E9gUQL0IBqzEKzcJQTAnkG0/C8MKTMpFBZ89pwNvFaOuPXLCI PIiPPy/luxEOgjYz9mwEzDShznISwDg327swWmNXEcDFZRnpnQya41RPAGJiw8e6xirvPpn3 Evd07UVEovGsP2CHoPfA/JvdK3UCAwEAAaM0MDIwIgYDVR0RBBswGYEXYWFudG9uQHJldmVy c2VkaGVsbC5uZXQwDAYDVR0TAQH/BAIwADANBgkqhkiG9w0BAQQFAAOBgQAsf0Fs94uUNfAA 2GC/CXQaccTiQJm7rRwhe+ttblOD0PH9jSUauQAKP7shBNBEhJ+j5JU8GlTEi/ZKCBGqFTJm 2pvbvy7QdQUe2J3VQwmCGYiJTu/m1iAVwhhRVtzZVC/u1EnXDzel2vnkJ5wOP5en2N8wd1wp Aii1A1K3ck7q0TCCAz8wggKooAMCAQICAQ0wDQYJKoZIhvcNAQEFBQAwgdExCzAJBgNVBAYT AlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUgVG93bjEaMBgGA1UE ChMRVGhhd3RlIENvbnN1bHRpbmcxKDAmBgNVBAsTH0NlcnRpZmljYXRpb24gU2VydmljZXMg RGl2aXNpb24xJDAiBgNVBAMTG1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBDQTErMCkGCSqG SIb3DQEJARYccGVyc29uYWwtZnJlZW1haWxAdGhhd3RlLmNvbTAeFw0wMzA3MTcwMDAwMDBa Fw0xMzA3MTYyMzU5NTlaMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3Vs dGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNz dWluZyBDQTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAxKY8VXNV+065yplaHmjAdQRw nd/p/6Me7L3N9VvyGna9fww6YfK/Uc4B1OVQCjDXAmNaLIkVcI7dyfArhVqqP3FWy688Cwfn 8R+RNiQqE88r1fOCdz0Dviv+uxg+B79AgAJk16emu59l0cUqVIUPSAR/p7bRPGEEQB5kGXJg t/sCAwEAAaOBlDCBkTASBgNVHRMBAf8ECDAGAQH/AgEAMEMGA1UdHwQ8MDowOKA2oDSGMmh0 dHA6Ly9jcmwudGhhd3RlLmNvbS9UaGF3dGVQZXJzb25hbEZyZWVtYWlsQ0EuY3JsMAsGA1Ud DwQEAwIBBjApBgNVHREEIjAgpB4wHDEaMBgGA1UEAxMRUHJpdmF0ZUxhYmVsMi0xMzgwDQYJ KoZIhvcNAQEFBQADgYEASIzRUIPqCy7MDaNmrGcPf6+svsIXoUOWlJ1/TCG4+DYfqi2fNi/A 9BxQIJNwPP2t4WFiw9k6GX6EsZkbAMUaC4J0niVQlGLH2ydxVyWN3amcOY6MIE9lX5Xa9/eH 1sYITq726jTlEBpbNU1341YheILcIRk13iSx0x1G/11fZU8xggM7MIIDNwIBATBpMGIxCzAJ BgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYD VQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQQIDCqhyMAkGBSsOAwIa BQCgggGnMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTAzMDky MTIzMDEzM1owIwYJKoZIhvcNAQkEMRYEFJ1x+jdS9IMde+7FobDNAu3JVwUnMFIGCSqGSIb3 DQEJDzFFMEMwCgYIKoZIhvcNAwcwDgYIKoZIhvcNAwICAgCAMA0GCCqGSIb3DQMCAgFAMAcG BSsOAwIHMA0GCCqGSIb3DQMCAgEoMHgGCSsGAQQBgjcQBDFrMGkwYjELMAkGA1UEBhMCWkEx JTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0 ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBAgMKqHIwegYLKoZIhvcNAQkQAgsxa6Bp MGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQu MSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQQIDCqhyMA0G CSqGSIb3DQEBAQUABIIBAF9tm+rTpjpTVoAjfSH+dEbzQTXjZoCtAe4mXP34E5AJndHFDxxQ i19hfbGhgFv1U43dZYED6mF9+ANcUhI7o+gz0rX1L+X4HglTt6R6cAgAl3Un3IU9NBH3KCxa S6eptlJplOw8HzG8va8MOT3Hn9RdESlPhgO1N6gRtOcRZBo6lMX+RdCcrj7jNQLvROriAcXq 0VYGTDUXofMPDWyjLPTecLGdsUTdIl39Mu1Jy7u5bduGi5Vqz9HJHQg4S1Cwk8sCQonm4pej x98l7i6MqNUa6ZH0dDGKK0WKB6KKc3jjJCU0ufkj5ve0/Vp3+pIyeGNdBsb/UF5bcfgj0lLh LisAAAAAAAA= --------------ms020704030209060100030201-- From owner-freebsd-hackers@FreeBSD.ORG Mon Sep 22 05:24:08 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3727D16A4B3 for ; Mon, 22 Sep 2003 05:24:08 -0700 (PDT) Received: from relay1.softcomca.com (relay1.softcomca.com [168.144.1.67]) by mx1.FreeBSD.org (Postfix) with ESMTP id 63CD543F3F for ; Mon, 22 Sep 2003 05:24:07 -0700 (PDT) (envelope-from dodell@sitetronics.com) Received: from M2W073.mail2web.com ([168.144.251.183]) by relay1.softcomca.com with Microsoft SMTPSVC(5.0.2195.6713); Mon, 22 Sep 2003 08:24:06 -0400 Message-ID: <410-22003912212246171@M2W073.mail2web.com> X-Priority: 3 X-Originating-IP: 81.69.92.101 X-URL: http://mail2web.com/ From: "dodell@sitetronics.com" To: freebsd-hackers@freebsd.org Date: Mon, 22 Sep 2003 08:24:06 -0400 MIME-Version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-OriginalArrivalTime: 22 Sep 2003 12:24:06.0262 (UTC) FILETIME=[6A783160:01C38104] Subject: SimpleTech USB HDD driver X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: dodell@sitetronics.com List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Sep 2003 12:24:08 -0000 I just bought a 120GB SimpleTech USB harddrive and I want to use it with FreeBSD 4=2E8 (the=20 HDD is part number STI-U2F35/120)=2E AFAIK, 4=2E8 doesn't support USB HDDs= =2E Why is this? If it is possible to write the drivers for this, I've got a couple of questions:=20 Who does the USB mass storage drivers? Where in the kernel do I need to look for information on writing them? Is the drive supported in 5=2E1 (I'm not sure what chipset it's using)? If= so, how hard would it be=20 to backport (or should I forget it and just upgrade to 5=2E1 with my lazy ass)? How badly am I going to screw up the HDD when my driver doesn't work? ;) Hope there're some ideas out there :) Thanks! Devon -------------------------------------------------------------------- mail2web - Check your email from the web at http://mail2web=2Ecom/ =2E From owner-freebsd-hackers@FreeBSD.ORG Mon Sep 22 06:05:09 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8FDD416A4B3 for ; Mon, 22 Sep 2003 06:05:09 -0700 (PDT) Received: from mta05-svc.ntlworld.com (mta05-svc.ntlworld.com [62.253.162.45]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7146343FE3 for ; Mon, 22 Sep 2003 06:05:08 -0700 (PDT) (envelope-from scott@fishballoon.org) Received: from llama.fishballoon.org ([81.104.195.124]) by mta05-svc.ntlworld.comESMTP <20030922123750.SIUO13360.mta05-svc.ntlworld.com@llama.fishballoon.org>; Mon, 22 Sep 2003 13:37:50 +0100 Received: from scott by llama.fishballoon.org with local (Exim 4.20) id 1A1Pw7-000I1A-V1; Mon, 22 Sep 2003 13:37:03 +0100 Date: Mon, 22 Sep 2003 13:37:03 +0100 From: Scott Mitchell To: "dodell@sitetronics.com" Message-ID: <20030922123703.GB66910@llama.fishballoon.org> References: <410-22003912212246171@M2W073.mail2web.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <410-22003912212246171@M2W073.mail2web.com> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 4.8-RELEASE i386 Sender: Scott Mitchell cc: freebsd-hackers@freebsd.org Subject: Re: SimpleTech USB HDD driver X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Sep 2003 13:05:09 -0000 On Mon, Sep 22, 2003 at 08:24:06AM -0400, dodell@sitetronics.com wrote: > I just bought a 120GB SimpleTech USB harddrive and I want to use it with > FreeBSD 4.8 (the > HDD is part number STI-U2F35/120). AFAIK, 4.8 doesn't support USB HDDs. Why > is this? Did you try plugging it in? If it really is a USB mass storage device, it is supported and should just work. All the necessary drivers are already there in the GENERIC kernel. Some devices might require 'quirks' to be added to the kernel to get them to work with 4.8 or earlier, but I think even this requirement has mostly gone away in 4.9. You might want to take a look at Dan Pelleg's DaemonNews article: http://ezine.daemonnews.org/200305/cfmount.html. It talks about CF devices but the part dealing with USB should also apply to disks. Scott From owner-freebsd-hackers@FreeBSD.ORG Mon Sep 22 06:12:52 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0725016A4B3 for ; Mon, 22 Sep 2003 06:12:52 -0700 (PDT) Received: from relay3.softcomca.com (relay3.softcomca.com [168.144.1.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id 386A443F93 for ; Mon, 22 Sep 2003 06:12:51 -0700 (PDT) (envelope-from dodell@sitetronics.com) Received: from M2W063.mail2web.com ([168.144.251.171]) by relay3.softcomca.com with Microsoft SMTPSVC(5.0.2195.6713); Mon, 22 Sep 2003 09:12:50 -0400 Message-ID: <410-220039122131250707@M2W063.mail2web.com> X-Priority: 3 X-Originating-IP: 81.69.92.101 X-URL: http://mail2web.com/ From: "dodell@sitetronics.com" To: scott+freebsd@fishballoon.org, dodell@sitetronics.com, freebsd-hackers@freebsd.org Date: Mon, 22 Sep 2003 09:12:50 -0400 MIME-Version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-OriginalArrivalTime: 22 Sep 2003 13:12:50.0555 (UTC) FILETIME=[397BE4B0:01C3810B] Subject: Re: SimpleTech USB HDD driver X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: dodell@sitetronics.com List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Sep 2003 13:12:52 -0000 Original Message: ----------------- From: Scott Mitchell scott+freebsd@fishballoon=2Eorg Date: Mon, 22 Sep 2003 13:37:03 +0100 To: dodell@sitetronics=2Ecom, freebsd-hackers@freebsd=2Eorg Subject: Re: SimpleTech USB HDD driver On Mon, Sep 22, 2003 at 08:24:06AM -0400, dodell@sitetronics=2Ecom wrote: > I just bought a 120GB SimpleTech USB harddrive and I want to use it with= > FreeBSD 4=2E8 (the=20 > HDD is part number STI-U2F35/120)=2E AFAIK, 4=2E8 doesn't support USB HD= Ds=2E Why > is this? Did you try plugging it in? If it really is a USB mass storage device, it= is supported and should just work=2E All the necessary drivers are alread= y there in the GENERIC kernel=2E Some devices might require 'quirks' to be added to the kernel to get them to work with 4=2E8 or earlier, but I think even this requirement has mostl= y gone away in 4=2E9=2E You might want to take a look at Dan Pelleg's DaemonNews article: http://ezine=2Edaemonnews=2Eorg/200305/cfmount=2Ehtml=2E It talks about C= F devices but the part dealing with USB should also apply to disks=2E =09Scott -------------------------- Hey Scott, I just bought the thing and I'm at work, so I haven't had a chance to try it out yet=2E I've sent a=20 message to the SimpleTech support people=2E=2E=2E hopefully they're OSS fr= iendly=2E I'll give more=20 information as I have it=2E I was under the impression though that USB HDD= s were unsupported=20 in RELENG_4; I may be totally off base, in which case I apologize for sending unnecessary=20 emails to the list=2E Thanks for the link to the article; I'll let you know about my sucesses/failures=2E --Devon -------------------------------------------------------------------- mail2web - Check your email from the web at http://mail2web=2Ecom/ =2E From owner-freebsd-hackers@FreeBSD.ORG Mon Sep 22 06:44:38 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BB11C16A4E1 for ; Mon, 22 Sep 2003 06:44:38 -0700 (PDT) Received: from mta06-svc.ntlworld.com (mta06-svc.ntlworld.com [62.253.162.46]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9996443FE5 for ; Mon, 22 Sep 2003 06:44:37 -0700 (PDT) (envelope-from scott@fishballoon.org) Received: from llama.fishballoon.org ([81.104.195.124]) by mta06-svc.ntlworld.comESMTP <20030922132709.XJFV2405.mta06-svc.ntlworld.com@llama.fishballoon.org>; Mon, 22 Sep 2003 14:27:09 +0100 Received: from scott by llama.fishballoon.org with local (Exim 4.20) id 1A1QhQ-000IBo-L1; Mon, 22 Sep 2003 14:25:56 +0100 Date: Mon, 22 Sep 2003 14:25:56 +0100 From: Scott Mitchell To: "dodell@sitetronics.com" Message-ID: <20030922132556.GC66910@llama.fishballoon.org> References: <410-220039122131250707@M2W063.mail2web.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <410-220039122131250707@M2W063.mail2web.com> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 4.8-RELEASE i386 Sender: Scott Mitchell cc: freebsd-hackers@freebsd.org Subject: Re: SimpleTech USB HDD driver X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Sep 2003 13:44:38 -0000 On Mon, Sep 22, 2003 at 09:12:50AM -0400, dodell@sitetronics.com wrote: > Hey Scott, > > I just bought the thing and I'm at work, so I haven't had a chance to try > it out yet. I've sent a > message to the SimpleTech support people... hopefully they're OSS friendly. > I'll give more > information as I have it. I was under the impression though that USB HDDs > were unsupported > in RELENG_4; I may be totally off base, in which case I apologize for > sending unnecessary > emails to the list. > > Thanks for the link to the article; I'll let you know about my > sucesses/failures. > > --Devon No worries - it's what the lists are for. AFAIK all USB mass storage devices should be supported by the umass driver, but some devices will have issues. I use various flash cards and 'pen drives' all the time - a real hard disk should look the same to the driver. Bear in mind that 4.x only supports USB 1.1, so even if you have USB 2.0 ports on your machine, and a USB 2.0 drive, the most you'll get out of it is somewhere in the region of 1 MB/s. Look forward to hearing of your success - good luck! Scott From owner-freebsd-hackers@FreeBSD.ORG Mon Sep 22 07:50:06 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 125E216A4B3 for ; Mon, 22 Sep 2003 07:50:06 -0700 (PDT) Received: from amsfep14-int.chello.nl (amsfep14-int.chello.nl [213.46.243.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 260B243FE3 for ; Mon, 22 Sep 2003 07:49:59 -0700 (PDT) (envelope-from dodell@sitetronics.com) Received: from sitetronics.com ([213.46.142.207]) by amsfep14-int.chello.nl (InterMail vM.5.01.05.17 201-253-122-126-117-20021021) with ESMTP id <20030922144957.PWEJ161.amsfep14-int.chello.nl@sitetronics.com>; Mon, 22 Sep 2003 16:49:57 +0200 Message-ID: <3F6F0BB0.9020506@sitetronics.com> Date: Mon, 22 Sep 2003 16:48:16 +0200 From: "Devon H. O'Dell" User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.4) Gecko/20030820 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Scott Mitchell References: <410-220039122131250707@M2W063.mail2web.com> <20030922132556.GC66910@llama.fishballoon.org> In-Reply-To: <20030922132556.GC66910@llama.fishballoon.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-hackers@freebsd.org Subject: Re: SimpleTech USB HDD driver X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Sep 2003 14:50:06 -0000 Scott Mitchell wrote: >On Mon, Sep 22, 2003 at 09:12:50AM -0400, dodell@sitetronics.com wrote: > > >No worries - it's what the lists are for. > >AFAIK all USB mass storage devices should be supported by the umass driver, >but some devices will have issues. I use various flash cards and 'pen drives' >all the time - a real hard disk should look the same to the driver. > >Bear in mind that 4.x only supports USB 1.1, so even if you have USB 2.0 ports >on your machine, and a USB 2.0 drive, the most you'll get out of it is >somewhere in the region of 1 MB/s. > >Look forward to hearing of your success - good luck! > > Scott > Well, what do you know, a quick mount_msdos /dev/da0s1 worked just fine ;). Something to add to the hardware compatibility list I guess. Here's the dmesg entry: umass0: In-System Design USB Storage Adapter, rev 2.00/11.01, addr 2 da0 at umass-sim0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-0 device da0: 650KB/s transfers da0: 117800MB (241254720 512 byte sectors: 64H 32S/T 52264C) I did get the below message, but it does not seem to goof up anything. (da0:umass-sim0:0:0:0): READ(6)/WRITE(6) not supported, increasing minimum_cmd_size to 10. My laptop only has USB 1.1 anyway (it's an old Latitude L400 -- don't think it has 2.0 anyway). 650KB/s is fine. I'm just using it to back up my *cough*VERY LEGAL*cough* mp3s ;) Thanks for setting my head straight about this. I think this should be listed on the web page. The reason I asked in the first place is because there are no mailing list articles about this (that Google could find with about 31899821498 different queries, anyway ;) and the webpage gives me the idea that it doesn't support larger devices. --Devon From owner-freebsd-hackers@FreeBSD.ORG Mon Sep 22 09:26:10 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 82D9816A4B3 for ; Mon, 22 Sep 2003 09:26:10 -0700 (PDT) Received: from gatekeeper.syskonnect.de (gatekeeper.syskonnect.de [213.144.13.149]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3318D43FE1 for ; Mon, 22 Sep 2003 09:26:09 -0700 (PDT) (envelope-from gheinig@syskonnect.de) Received: from syskonnect.de (spock [10.9.15.1])h8MGQIcp017562 for ; Mon, 22 Sep 2003 18:26:18 +0200 (MET DST) Received: from syskonnect.de (localhost [127.0.0.1]) by syskonnect.de (8.12.9/8.12.9) with ESMTP id h8MGQ6xj017057 for ; Mon, 22 Sep 2003 18:26:06 +0200 (MET DST) X-Authentication-Warning: spock.skd.de: iscan owned process doing -bs Sender: gheinig@syskonnect.de Message-ID: <3F6F1F0E.F2DBF47C@syskonnect.de> Date: Mon, 22 Sep 2003 18:10:54 +0200 From: Gerald Heinig Organization: SysKonnect GmbH X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.18 i686) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Using kernel mod instead of built-in driver X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Sep 2003 16:26:10 -0000 Hi all, I'm currently developing a kernel module for a device for which there is already a driver present in the GENERIC kernel. Is there any other mechanism apart from device.hints by which I can turn off the in-kernel driver and only use my module? It doesn't seem to work with device.hints. Is something like this at all possible? Cheers, Gerald -- S y s K o n n e c t G m b H A Marvell Company Siemensstr. 23 D-76275 Ettlingen, Germany --------------------------------- Gerald Heinig Software Engineer ------------------------------------- phone: + 49 (0) 7243 502 354 fax: +49 (0) 7243 502 364 email: gheinig@syskonnect.de http://www.syskonnect.com From owner-freebsd-hackers@FreeBSD.ORG Mon Sep 22 10:05:39 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9628116A4C0 for ; Mon, 22 Sep 2003 10:05:39 -0700 (PDT) Received: from mail.redlinenetworks.com (mail.redlinenetworks.com [216.136.145.172]) by mx1.FreeBSD.org (Postfix) with ESMTP id BFDBA43FE3 for ; Mon, 22 Sep 2003 10:05:33 -0700 (PDT) (envelope-from sreekanth@redlinenetworks.com) Received: from SREELAPTOP (dhcp-174.redlinenetworks.com [192.168.40.174]) h8MH5XD39035; Mon, 22 Sep 2003 10:05:33 -0700 (PDT) (envelope-from sreekanth@redlinenetworks.com) From: "Sreekanth" To: "'Gerald Heinig'" , Date: Mon, 22 Sep 2003 10:05:33 -0700 Message-ID: <000901c3812b$bc57e6c0$ae28a8c0@SREELAPTOP> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2616 Importance: Normal In-Reply-To: <3F6F1F0E.F2DBF47C@syskonnect.de> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Subject: RE: Using kernel mod instead of built-in driver X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Sep 2003 17:05:39 -0000 If the native driver is built into the kernel there is no way you can force it out.What you can do is to build a GENERIC kernel without the native driver and load either your driver or the native driver by using kldload. Sreekanth > -----Original Message----- > From: owner-freebsd-hackers@freebsd.org > [mailto:owner-freebsd-hackers@freebsd.org] On Behalf Of Gerald Heinig > Sent: Monday, September 22, 2003 9:11 AM > To: freebsd-hackers@freebsd.org > Subject: Using kernel mod instead of built-in driver > > > Hi all, > > I'm currently developing a kernel module for a device for > which there is already a driver present in the GENERIC > kernel. Is there any other mechanism apart from device.hints > by which I can turn off the in-kernel driver and only use my > module? It doesn't seem to work with device.hints. Is > something like this at all possible? > > Cheers, > > Gerald > -- > S y s K o n n e c t G m b H > A Marvell Company > Siemensstr. 23 > D-76275 Ettlingen, Germany > --------------------------------- > Gerald Heinig > Software Engineer > ------------------------------------- > phone: + 49 (0) 7243 502 354 > fax: +49 (0) 7243 502 364 > email: gheinig@syskonnect.de > http://www.syskonnect.com > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/free> bsd-hackers > To > unsubscribe, send any mail to > "freebsd-hackers-unsubscribe@freebsd.org" > > --- > Incoming mail is certified Virus Free. > Checked by AVG anti-virus system (http://www.grisoft.com). > Version: 6.0.516 / Virus Database: 313 - Release Date: 9/1/2003 > > From owner-freebsd-hackers@FreeBSD.ORG Mon Sep 22 11:07:29 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BF2BE16A4B3 for ; Mon, 22 Sep 2003 11:07:29 -0700 (PDT) Received: from mailout02.sul.t-online.com (mailout02.sul.t-online.com [194.25.134.17]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0884243FBD for ; Mon, 22 Sep 2003 11:07:29 -0700 (PDT) (envelope-from u.klann@t-online.de) Received: from fwd00.aul.t-online.de by mailout02.sul.t-online.com with smtp id 1A1V5r-0006hU-04; Mon, 22 Sep 2003 20:07:27 +0200 Received: from london (rxT+5kZUQeAWmXS7Ywx+OxAV+0I5U8mxywVcqJ0ZqJAPqNUNICuJQR@[217.80.251.251]) by fwd00.sul.t-online.com with smtp id 1A1V5d-09RzDk0; Mon, 22 Sep 2003 20:07:13 +0200 From: u.klann@t-online.de (Uwe Klann) To: Date: Mon, 22 Sep 2003 20:07:13 +0200 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-Seen: false X-ID: rxT+5kZUQeAWmXS7Ywx+OxAV+0I5U8mxywVcqJ0ZqJAPqNUNICuJQR Subject: IPFW2 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: u.klann@t-online.de List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Sep 2003 18:07:29 -0000 Hi All, >From the Log file IPFW:- "Sep 22 00:24:13 muc /kernel: ipfw: 3300 Accept TCP 217.10.213.30:4418 217.9.121.209:21 in via fxp0" How can I extend on FreeBSD 4.8 (ipfw2) the log contens to see the tranfered data File and the amount of bytes went out? Thank you in advance for your help. Cheers, Uwe Uwe Klann Isensteinstr. 3 80634 Munich Germany Mail: u.klann@t-online.de From owner-freebsd-hackers@FreeBSD.ORG Mon Sep 22 11:43:42 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AEFD916A4B3 for ; Mon, 22 Sep 2003 11:43:42 -0700 (PDT) Received: from relay3.softcomca.com (relay3.softcomca.com [168.144.1.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id B8CE643FE1 for ; Mon, 22 Sep 2003 11:43:41 -0700 (PDT) (envelope-from akanwar@digitarchy.com) Received: from M2W048.mail2web.com ([168.144.251.155]) by relay3.softcomca.com with Microsoft SMTPSVC(5.0.2195.6713); Mon, 22 Sep 2003 14:43:40 -0400 Message-ID: <63340-220039122184340901@M2W048.mail2web.com> X-Priority: 3 X-Originating-IP: 68.111.37.3 X-URL: http://mail2web.com/ From: "akanwar@digitarchy.com" To: freebsd-hackers@freebsd.org Date: Mon, 22 Sep 2003 14:43:40 -0400 MIME-Version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-OriginalArrivalTime: 22 Sep 2003 18:43:40.0901 (UTC) FILETIME=[71365150:01C38139] Subject: HZ = 1000 slows down application X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: akanwar@digitarchy.com List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Sep 2003 18:43:42 -0000 Hi all, =20 I am expertmenting with kernel device polling on a 4=2E8-RELEASE system=2E= =20 The application I am running is a traffic pumping application that sits in= an infinite while loop=2E At the time of this test it was doing 6Mbps in a= nd 5Mbps out traffic=2E CPU usage is 40% without polling enabled, typical CPU= usage is roughly 1/3 user, 1/3 system and 1/3 interrupt=2E I am using the = fxp driver=2E I customized my kernel with HZ=3D1000 and enabled polling via sysctl=2E=2E= =2ECPU usage dropped from 40% to 30%=2E Great so far=2E But now I noticed that my application is occassionally doing slower iterations=2E Average iteration time used to be 0=2E2 ms without polling enabled=2E With the device polling changes, the average time is still arou= nd the same, but once every few minutes the application sees iterations that are 3=2E3 seconds (*seconds*, not a typo) long=2E=20 This seems to happen as soon as I use the kernel with HZ=3D1000=2E Enablin= g or disabling device polling does not seem to make any difference to this behavior=2E I am trying to understand why there seem to be a few really lo= ng iterations=2E Could it happen that the application does not get any CPU fo= r that long? Seems very counter intuitive that higher HZ should cause this=2E= =20 Could anyone shed any light on what is happening ? Thanks, -ansh -------------------------------------------------------------------- mail2web - Check your email from the web at http://mail2web=2Ecom/ =2E From owner-freebsd-hackers@FreeBSD.ORG Mon Sep 22 13:45:32 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7469416A4BF for ; Mon, 22 Sep 2003 13:45:32 -0700 (PDT) Received: from xorpc.icir.org (xorpc.icir.org [192.150.187.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id A39F543FF2 for ; Mon, 22 Sep 2003 13:45:31 -0700 (PDT) (envelope-from rizzo@xorpc.icir.org) Received: from xorpc.icir.org (localhost [127.0.0.1]) by xorpc.icir.org (8.12.9p1/8.12.3) with ESMTP id h8MKjVsd045069; Mon, 22 Sep 2003 13:45:31 -0700 (PDT) (envelope-from rizzo@xorpc.icir.org) Received: (from rizzo@localhost) by xorpc.icir.org (8.12.9p1/8.12.3/Submit) id h8MKjVWT045068; Mon, 22 Sep 2003 13:45:31 -0700 (PDT) (envelope-from rizzo) Date: Mon, 22 Sep 2003 13:45:31 -0700 From: Luigi Rizzo To: Uwe Klann Message-ID: <20030922134531.A44366@xorpc.icir.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: ; from u.klann@t-online.de on Mon, Sep 22, 2003 at 08:07:13PM +0200 cc: freebsd-hackers@freebsd.org Subject: Re: IPFW2 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Sep 2003 20:45:32 -0000 On Mon, Sep 22, 2003 at 08:07:13PM +0200, Uwe Klann wrote: > Hi All, > > >From the Log file IPFW:- > "Sep 22 00:24:13 muc /kernel: ipfw: 3300 Accept TCP 217.10.213.30:4418 > 217.9.121.209:21 in via fxp0" > > How can I extend on FreeBSD 4.8 (ipfw2) the log contens to see the tranfered > data File and the amount of bytes went out? Thank you in advance for your you can count the traffic with dynamic rules (but this does not go to the logfile), not sure what you mean by 'see the transfered data file' luigi > > Uwe > > Uwe Klann > Isensteinstr. 3 > 80634 Munich > Germany > Mail: u.klann@t-online.de > > > > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" From owner-freebsd-hackers@FreeBSD.ORG Mon Sep 22 13:54:01 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 430A016A4B3 for ; Mon, 22 Sep 2003 13:54:01 -0700 (PDT) Received: from mta03-svc.ntlworld.com (mta03-svc.ntlworld.com [62.253.162.43]) by mx1.FreeBSD.org (Postfix) with ESMTP id C908B43FDF for ; Mon, 22 Sep 2003 13:53:59 -0700 (PDT) (envelope-from scott@fishballoon.org) Received: from llama.fishballoon.org ([81.104.195.124]) by mta03-svc.ntlworld.comESMTP <20030922205354.WVYC11416.mta03-svc.ntlworld.com@llama.fishballoon.org>; Mon, 22 Sep 2003 21:53:54 +0100 Received: from scott by llama.fishballoon.org with local (Exim 4.20) id 1A1Xfe-000JwM-2j; Mon, 22 Sep 2003 21:52:34 +0100 Date: Mon, 22 Sep 2003 21:52:34 +0100 From: Scott Mitchell To: "Devon H. O'Dell" Message-ID: <20030922205234.GB75844@llama.fishballoon.org> References: <410-220039122131250707@M2W063.mail2web.com> <20030922132556.GC66910@llama.fishballoon.org> <3F6F0BB0.9020506@sitetronics.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3F6F0BB0.9020506@sitetronics.com> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 4.8-RELEASE i386 Sender: Scott Mitchell cc: freebsd-hackers@freebsd.org Subject: Re: SimpleTech USB HDD driver X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Sep 2003 20:54:01 -0000 On Mon, Sep 22, 2003 at 04:48:16PM +0200, Devon H. O'Dell wrote: > Well, what do you know, a quick mount_msdos /dev/da0s1 worked just fine > ;). Something to add to the hardware compatibility list I guess. Here's > the dmesg entry: > > umass0: In-System Design USB Storage Adapter, rev 2.00/11.01, addr 2 > da0 at umass-sim0 bus 0 target 0 lun 0 > da0: Fixed Direct Access SCSI-0 device > da0: 650KB/s transfers > da0: 117800MB (241254720 512 byte sectors: 64H 32S/T 52264C) > > I did get the below message, but it does not seem to goof up anything. > > (da0:umass-sim0:0:0:0): READ(6)/WRITE(6) not supported, increasing > minimum_cmd_size to 10. This is fine - just an informational message rather than anything actually wrong. > Thanks for setting my head straight about this. I think this should be > listed on the web page. The reason I asked in the first place is because > there are no mailing list articles about this (that Google could find > with about 31899821498 different queries, anyway ;) and the webpage > gives me the idea that it doesn't support larger devices. Indeed... the docs should probably just list the classes of device that should work, rather than specific instances. I did once start updating the umass(4) manpage to say this, but got discouraged by a flurry of list messages complaining that XYZ device didn't work - didn't feel up to documenting the intricacies of the quirking mechanism. Now that this is less of a problem, I should probably pick that up again. Anyway, glad you got it working. Cheers, Scott From owner-freebsd-hackers@FreeBSD.ORG Mon Sep 22 14:22:06 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EDB3416A4B3 for ; Mon, 22 Sep 2003 14:22:06 -0700 (PDT) Received: from xorpc.icir.org (xorpc.icir.org [192.150.187.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id BF3E343F93 for ; Mon, 22 Sep 2003 14:22:05 -0700 (PDT) (envelope-from rizzo@xorpc.icir.org) Received: from xorpc.icir.org (localhost [127.0.0.1]) by xorpc.icir.org (8.12.9p1/8.12.3) with ESMTP id h8MLM2sd056154; Mon, 22 Sep 2003 14:22:02 -0700 (PDT) (envelope-from rizzo@xorpc.icir.org) Received: (from rizzo@localhost) by xorpc.icir.org (8.12.9p1/8.12.3/Submit) id h8MLM2OD056149; Mon, 22 Sep 2003 14:22:02 -0700 (PDT) (envelope-from rizzo) Date: Mon, 22 Sep 2003 14:22:02 -0700 From: Luigi Rizzo To: "akanwar@digitarchy.com" Message-ID: <20030922142202.A46421@xorpc.icir.org> References: <63340-220039122184340901@M2W048.mail2web.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <63340-220039122184340901@M2W048.mail2web.com>; from akanwar@digitarchy.com on Mon, Sep 22, 2003 at 02:43:40PM -0400 cc: freebsd-hackers@freebsd.org Subject: Re: HZ = 1000 slows down application X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Sep 2003 21:22:07 -0000 On Mon, Sep 22, 2003 at 02:43:40PM -0400, akanwar@digitarchy.com wrote: ... > But now I noticed that my application is occassionally doing slower > iterations. Average iteration time used to be 0.2 ms without polling > enabled. With the device polling changes, the average time is still around > the same, but once every few minutes the application sees iterations that > are 3.3 seconds (*seconds*, not a typo) long. most likely your application makes some assumptions on the duration of a clock tick and then it gets confused when, say, a select returns quicker, or some time difference becomes negative, etc. etc. because of the finer granularity. very common type of bug. cheers luigi > This seems to happen as soon as I use the kernel with HZ=1000. Enabling or > disabling device polling does not seem to make any difference to this > behavior. I am trying to understand why there seem to be a few really long > iterations. Could it happen that the application does not get any CPU for > that long? Seems very counter intuitive that higher HZ should cause this. > > Could anyone shed any light on what is happening ? > > Thanks, > -ansh > > -------------------------------------------------------------------- > mail2web - Check your email from the web at > http://mail2web.com/ . > > > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > From owner-freebsd-hackers@FreeBSD.ORG Mon Sep 22 17:22:11 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0CDD716A4B3 for ; Mon, 22 Sep 2003 17:22:11 -0700 (PDT) Received: from mail.forko.com (forko.com [206.14.189.156]) by mx1.FreeBSD.org (Postfix) with ESMTP id 85A8643F93 for ; Mon, 22 Sep 2003 17:22:10 -0700 (PDT) (envelope-from matt@mail.forko.com) Received: (qmail 6464 invoked by uid 1000); 22 Sep 2003 17:18:27 -0700 Date: Mon, 22 Sep 2003 17:18:27 -0700 From: Matt Peterson To: freebsd-hackers@freebsd.org Message-ID: <20030923001827.GA11677@forko.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i Subject: percent support in sysinstall slice editor X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Sep 2003 00:22:11 -0000 Howdy, Would it be possible to add disk percentage support in the sysinstall slice editor? That is, instead of building slice based on a fixed size (ie: 5Gb) use percentage of the total disk size (ie: 25%). I ask this for automated PXE installs using unknown hard drive/compantflash sizes. From owner-freebsd-hackers@FreeBSD.ORG Mon Sep 22 20:09:33 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EC1E216A4B3 for ; Mon, 22 Sep 2003 20:09:33 -0700 (PDT) Received: from athenas.yan.com.br (athenas.yan.com.br [200.202.253.9]) by mx1.FreeBSD.org (Postfix) with SMTP id 0CF8C43FF9 for ; Mon, 22 Sep 2003 20:09:32 -0700 (PDT) (envelope-from ddg@yan.com.br) Received: (qmail 12087 invoked by uid 1023); 23 Sep 2003 00:08:12 -0300 Received: from unknown (HELO pegasus) (ddg@200.202.253.166) by athenas.yan.com.br with SMTP; 23 Sep 2003 00:08:12 -0300 Date: Mon, 22 Sep 2003 22:34:46 -0300 From: Daniel Dias Goncalves To: freebsd-net@freebsd.org Message-Id: <20030922223446.5232286a.ddg@yan.com.br> X-Mailer: Sylpheed version 0.8.11claws (GTK+ 1.2.10; i386--netbsdelf) Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable cc: freebsd-hackers@freebsd.org Subject: SMC 2602W PCI Wireless X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Sep 2003 03:09:34 -0000 The device SMC 2602W PCI works in the FreeBSD? # uname -rs FreeBSD 5.1-RELEASE # pciconf -l -v ... none2@pci0:10:0: class=3D0x028000 card=3D0x260210b8 chip=3D0x8201131= 7 rev=3D0x11 hdr=3D0x00 vendor =3D 'Admtek Inc' class =3D network ... # kernel configuration: device cbb # cardbus (yenta) bridge device pcic # ExCA ISA and PCI bridges=20 device pccard # PC Card (16-bit) bus device cardbus # CardBus (32-bit) bus =20 device wlan # 802.11 support device wi # WaveLAN/Intersil/Symbol 802.11 wireless NICs. wi* not work Any idea ? []s Daniel Dias Gon=E7alves f22@netbsd.com.br From owner-freebsd-hackers@FreeBSD.ORG Mon Sep 22 22:05:19 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BACA316A4B3; Mon, 22 Sep 2003 22:05:19 -0700 (PDT) Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id CFC3B43FEC; Mon, 22 Sep 2003 22:05:18 -0700 (PDT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.9p1/8.12.3) with ESMTP id h8N55EGA051344; Mon, 22 Sep 2003 23:05:16 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Mon, 22 Sep 2003 23:05:15 -0600 (MDT) Message-Id: <20030922.230515.112077084.imp@bsdimp.com> To: ddg@yan.com.br From: "M. Warner Losh" In-Reply-To: <20030922223446.5232286a.ddg@yan.com.br> References: <20030922223446.5232286a.ddg@yan.com.br> X-Mailer: Mew version 2.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-net@freebsd.org cc: freebsd-hackers@freebsd.org Subject: Re: SMC 2602W PCI Wireless X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Sep 2003 05:05:19 -0000 In message: <20030922223446.5232286a.ddg@yan.com.br> Daniel Dias Goncalves writes: : The device SMC 2602W PCI works in the FreeBSD? : vendor = 'Admtek Inc' unlikely. The adm wireless driver is still being ported. Warner From owner-freebsd-hackers@FreeBSD.ORG Mon Sep 22 22:37:15 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C9E3816A4B3; Mon, 22 Sep 2003 22:37:15 -0700 (PDT) Received: from mailhub.webcraft99.com (prwire.bernama.com [202.188.124.52]) by mx1.FreeBSD.org (Postfix) with ESMTP id C188E43FFB; Mon, 22 Sep 2003 22:37:09 -0700 (PDT) (envelope-from afu-subscribed-list@aeefyu.net) Received: from localhost (beta.webcraft99.com [127.0.0.1]) by mailhub.webcraft99.com (Postfix) with ESMTP id 0EB1519312; Tue, 23 Sep 2003 13:37:08 +0800 (MYT) Received: from mailhub.webcraft99.com ([127.0.0.1]) by localhost (beta.webcraft99.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 89448-09; Tue, 23 Sep 2003 13:36:59 +0800 (MYT) Received: from aeefyu.net (unknown [218.208.9.226]) by mailhub.webcraft99.com (Postfix) with ESMTP id 4180F19307; Tue, 23 Sep 2003 13:36:59 +0800 (MYT) Message-ID: <3F6FD8E9.9060102@aeefyu.net> Date: Tue, 23 Sep 2003 13:23:53 +0800 From: Aeefyu User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.4) Gecko/20030815 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org, freebsd-mobile@freebsd.org, freebsd-questions@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at mailhub.webcraft99.com Subject: USB Ethernet (Billionton) not Recognised X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Sep 2003 05:37:15 -0000 Hello to all I have with me a USB 10/100 Ethernet which is currently not being recognised by my FreeBSD-4.8_RELEASE-p5 The packaging name is Billionton, however it doesnt match any of the device listed in sys/dev/usd/usbdevs. My kernel is compiled with all the USB Ethernet device drivers - aue, kue, cue Booting my box with the device attached, however, merely results in it being attached the device name ugen0. Output of usbdevs -vd is as follows: ------------------------------------------------- Controller /dev/usb0: addr 1: self powered, config 1, UHCI root hub(0x0000), Intel(0x0000), rev 1.00 uhub0 port 1 addr 2: power 120 mA, config 1, USB 10/100 LAN(0x8150), USBKR100(0x0bda), rev 1.00 ugen0 port 2 powered Relevant dmesg: ------------------------ uhci0: port 0xbf80-0xbf9f irq 11 at device 29.0 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered ugen0: USBKR100 USB 10/100 LAN, rev 1.10/1.00, addr 2 Anyone can guide me in making this device work? I have tried mucking around with sys/dev/usb/usbdevs, usbdevs.h, usbdevs_data.h and if_aue.c - cd ../../modules/aue && make && make install but this results in my boot-up being stuck during probe of the device Any pointers is very much appreciated. -- Feisal Webcraft Solutions - http://www.webcraftsolutions.com -------------------------------------- In Tulsa, Oklahoma, it is against the law to open a soda bottle without the supervision of a licensed engineer. From owner-freebsd-hackers@FreeBSD.ORG Mon Sep 22 23:06:22 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DB9BF16A4B3 for ; Mon, 22 Sep 2003 23:06:22 -0700 (PDT) Received: from mail012.syd.optusnet.com.au (mail012.syd.optusnet.com.au [211.29.132.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 69C6D43FE0 for ; Mon, 22 Sep 2003 23:06:20 -0700 (PDT) (envelope-from callumgibson@optusnet.com.au) Received: from omma.nsw.optusnet.com.au (c211-28-36-208.rivrw1.nsw.optusnet.com.au [211.28.36.208]) h8N66IE15528 for ; Tue, 23 Sep 2003 16:06:18 +1000 Received: (qmail 42599 invoked by uid 107); 23 Sep 2003 06:06:18 -0000 Date: Tue, 23 Sep 2003 16:06:18 +1000 From: Callum Gibson To: freebsd-hackers@freebsd.org Message-ID: <20030923060618.GA42533@omma.nsw.optushome.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4i Subject: MSG_OOB for unix/local domain sockets X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Sep 2003 06:06:23 -0000 Hi all, I have an application which uses MSG_OOB and it works fine on Solaris and FreeBSD with PF_INET type sockets. I noticed (through observation, not documentation) that out of band doesn't seem to be supported by FreeBSD's PF_LOCAL (PF_UNIX), although it is on Solaris (from 2.6 at least). Has anyone else noticed this? Is it on anyone's list of things to fix (I can't find a PR in for it)? -- Callum @ home From owner-freebsd-hackers@FreeBSD.ORG Mon Sep 22 23:46:13 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E6FFB16A4B3 for ; Mon, 22 Sep 2003 23:46:13 -0700 (PDT) Received: from amsfep15-int.chello.nl (amsfep15-int.chello.nl [213.46.243.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1D26F43FD7 for ; Mon, 22 Sep 2003 23:46:10 -0700 (PDT) (envelope-from dodell@sitetronics.com) Received: from sitetronics.com ([213.46.142.207]) by amsfep15-int.chello.nl (InterMail vM.5.01.05.17 201-253-122-126-117-20021021) with ESMTP id <20030923063435.GXRZ6169.amsfep15-int.chello.nl@sitetronics.com>; Tue, 23 Sep 2003 08:34:35 +0200 Message-ID: <3F6FE92B.5040906@sitetronics.com> Date: Tue, 23 Sep 2003 08:33:15 +0200 From: "Devon H. O'Dell" User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.4) Gecko/20030820 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Scott Mitchell References: <410-220039122131250707@M2W063.mail2web.com> <20030922132556.GC66910@llama.fishballoon.org> <3F6F0BB0.9020506@sitetronics.com> <20030922205234.GB75844@llama.fishballoon.org> In-Reply-To: <20030922205234.GB75844@llama.fishballoon.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-hackers@freebsd.org Subject: Re: SimpleTech USB HDD driver X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Sep 2003 06:46:14 -0000 Scott Mitchell wrote: >This is fine - just an informational message rather than anything >actually wrong. > > Out of curiosity, what does that indicate (or where can I find comments in the source)? >Indeed... the docs should probably just list the classes of device that >should work, rather than specific instances. I did once start updating >the umass(4) manpage to say this, but got discouraged by a flurry of >list messages complaining that XYZ device didn't work - didn't feel up >to documenting the intricacies of the quirking mechanism. Now that this >is less of a problem, I should probably pick that up again. > >Anyway, glad you got it working. > > Yes, I also got an email from the product manager of the SimpleDrive asking me what sort of documentation I was looking for. This seems like an open-source friendly company; just so that we can keep this in mind in case there are portable storage device/hard drive issues in the future. It looks like Firewire is also taken care of, but you never know what else there might be in the future. --Devon From owner-freebsd-hackers@FreeBSD.ORG Tue Sep 23 02:13:21 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 52CFC16A4B3 for ; Tue, 23 Sep 2003 02:13:21 -0700 (PDT) Received: from ipnet.ru (relay.ipnet.ru [62.16.100.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id CE44943FF5 for ; Tue, 23 Sep 2003 02:13:18 -0700 (PDT) (envelope-from tsypa@post.spbip.net) Received: from [127.0.0.1] (HELO post.spbip.net) by ipnet.ru (CommuniGate Pro SMTP 4.0.5) with ESMTP-TLS id 2542659 for freebsd-hackers@freebsd.org; Tue, 23 Sep 2003 09:12:58 +0000 Received: (from tsypa@localhost) by post.spbip.net (8.12.8p1/8.12.8/Submit) id h8N9Cvb4034186 for freebsd-hackers@freebsd.org; Tue, 23 Sep 2003 09:12:57 GMT Date: Tue, 23 Sep 2003 09:12:57 +0000 From: Igor Tseglevsky To: freebsd-hackers@freebsd.org Message-ID: <20030923091257.GF88647@ipnet.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline User-Agent: Mutt/1.4i Subject: raid (atacontrol) problems X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Sep 2003 09:13:21 -0000 Strange problems with RAID. If disks are located on different controllers after rebooting one of disks disappears. Disks on one controller coexist in RAID normally. Any ideas? Please, help! cf# atacontrol status 0 atacontrol: ioctl(ATARAIDSTATUS): Device not configured cf# atacontrol create mirror ad1 ad4 ar0 created cf# atacontrol status 0 ar0: ATA RAID1 subdisks: ad1 ad4 status: READY cf# fastboot cf# atacontrol status 0 ar0: ATA RAID1 subdisks: ad1 DOWN status: DEGRADED In dmesg: ad0: 76319MB [155061/16/63] at ata0-master UDMA66 ad1: 76319MB [155061/16/63] at ata0-slave UDMA66 ad2: DMA limited to UDMA33, non-ATA66 cable or device ad2: 76319MB [155061/16/63] at ata1-master UDMA33 ad4: 76319MB [155061/16/63] at ata2-master UDMA100 ad6: 76319MB [155061/16/63] at ata3-master UDMA100 ar0: WARNING - mirror lost ar0: 76319MB [9729/255/63] status: DEGRADED subdisks: disk0 READY on ad1 at ata0-slave disk1 DOWN no device found for this disk Similarly for ad2 and ad6. Other situation with same controller: cf# atacontrol status 0 atacontrol: ioctl(ATARAIDSTATUS): Device not configured cf# atacontrol create mirror ad1 ad2 ar0 created cf# atacontrol status 0 ar0: ATA RAID1 subdisks: ad1 ad2 status: READY cf# fastboot cf# atacontrol status 0 ar0: ATA RAID1 subdisks: ad1 ad2 status: READY Similarly for ad4 and ad6. cf# uname -a FreeBSD cf 5.1-RELEASE-p5 FreeBSD 5.1-RELEASE-p5 #0: Mon Sep 22 07:46:00 GMT 2003 tsypa@cf:/usr/obj/usr/src/sys/GENERIC i386 cf# Some dmesg about controllers: atapci0: port 0xdf90-0xdf9f,0xdfe0-0xdfe3,0xdfa8-0xdfaf,0xdfe4-0xdfe7,0xdff0-0xdff7 mem 0xfeafc000-0xfeafffff irq 11 at device 8.0 on pci2 ata2: at 0xdff0 on atapci0 ata3: at 0xdfa8 on atapci0 atapci1: port 0xffa0-0xffaf at device 31.1 on pci0 ata0: at 0x1f0 irq 14 on atapci1 ata1: at 0x170 irq 15 on atapci1 Igor. From owner-freebsd-hackers@FreeBSD.ORG Tue Sep 23 08:49:55 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0BF6D16A4B3 for ; Tue, 23 Sep 2003 08:49:55 -0700 (PDT) Received: from spider.deepcore.dk (cpe.atm2-0-56339.0x50c6aa0a.abnxx2.customer.tele.dk [80.198.170.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9A1B443FDF for ; Tue, 23 Sep 2003 08:49:50 -0700 (PDT) (envelope-from sos@spider.deepcore.dk) Received: from spider.deepcore.dk (localhost [127.0.0.1]) by spider.deepcore.dk (8.12.9/8.12.9) with ESMTP id h8NFnlKg021879; Tue, 23 Sep 2003 17:49:47 +0200 (CEST) (envelope-from sos@spider.deepcore.dk) Received: (from sos@localhost) by spider.deepcore.dk (8.12.9/8.12.9/Submit) id h8NFnhYY021877; Tue, 23 Sep 2003 17:49:43 +0200 (CEST) From: Soren Schmidt Message-Id: <200309231549.h8NFnhYY021877@spider.deepcore.dk> In-Reply-To: <20030923091257.GF88647@ipnet.ru> To: Igor Tseglevsky Date: Tue, 23 Sep 2003 17:49:42 +0200 (CEST) X-Mailer: ELM [version 2.4ME+ PL99f (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=ISO-8859-1 X-mail-scanned: by DeepCore Virus & Spam killer v1.3 cc: freebsd-hackers@FreeBSD.ORG Subject: Re: raid (atacontrol) problems X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Sep 2003 15:49:55 -0000 It seems Igor Tseglevsky wrote: [ Charset KOI8-R unsupported, converting... ] > Strange problems with RAID. If disks are located on different controllers > after rebooting one of disks disappears. Disks on one controller coexist in > RAID normally. Is that Promise controller a fasttrak ie with a RAID BIOS ? In that case you cant span controllers, that only works on generic ATA controllers (ie those without any RAID). > Any ideas? Please, help! > > > cf# atacontrol status 0 > atacontrol: ioctl(ATARAIDSTATUS): Device not configured > cf# atacontrol create mirror ad1 ad4 > ar0 created > cf# atacontrol status 0 > ar0: ATA RAID1 subdisks: ad1 ad4 status: READY > cf# fastboot > > cf# atacontrol status 0 > ar0: ATA RAID1 subdisks: ad1 DOWN status: DEGRADED > > In dmesg: > > ad0: 76319MB [155061/16/63] at ata0-master UDMA66 > ad1: 76319MB [155061/16/63] at ata0-slave UDMA66 > ad2: DMA limited to UDMA33, non-ATA66 cable or device > ad2: 76319MB [155061/16/63] at ata1-master UDMA33 > ad4: 76319MB [155061/16/63] at ata2-master UDMA100 > ad6: 76319MB [155061/16/63] at ata3-master UDMA100 > ar0: WARNING - mirror lost > ar0: 76319MB [9729/255/63] status: DEGRADED subdisks: > disk0 READY on ad1 at ata0-slave > disk1 DOWN no device found for this disk > > Similarly for ad2 and ad6. > > Other situation with same controller: > > cf# atacontrol status 0 > atacontrol: ioctl(ATARAIDSTATUS): Device not configured > cf# atacontrol create mirror ad1 ad2 > ar0 created > cf# atacontrol status 0 > ar0: ATA RAID1 subdisks: ad1 ad2 status: READY > cf# fastboot > > cf# atacontrol status 0 > ar0: ATA RAID1 subdisks: ad1 ad2 status: READY > > Similarly for ad4 and ad6. > > cf# uname -a > FreeBSD cf 5.1-RELEASE-p5 FreeBSD 5.1-RELEASE-p5 #0: Mon Sep 22 07:46:00 GMT 2003 tsypa@cf:/usr/obj/usr/src/sys/GENERIC i386 > cf# > > Some dmesg about controllers: > > atapci0: port 0xdf90-0xdf9f,0xdfe0-0xdfe3,0xdfa8-0xdfaf,0xdfe4-0xdfe7,0xdff0-0xdff7 mem 0xfeafc000-0xfeafffff irq 11 at device 8.0 on pci2 > ata2: at 0xdff0 on atapci0 > ata3: at 0xdfa8 on atapci0 > > atapci1: port 0xffa0-0xffaf at device 31.1 on pci0 > ata0: at 0x1f0 irq 14 on atapci1 > ata1: at 0x170 irq 15 on atapci1 > > Igor. > > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > -Søren From owner-freebsd-hackers@FreeBSD.ORG Tue Sep 23 09:28:31 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EDC7C16A4B3 for ; Tue, 23 Sep 2003 09:28:31 -0700 (PDT) Received: from mail.secureworks.net (mail.secureworks.net [209.101.212.155]) by mx1.FreeBSD.org (Postfix) with SMTP id BF0D043FEA for ; Tue, 23 Sep 2003 09:28:29 -0700 (PDT) (envelope-from mdg@secureworks.net) Received: (qmail 38081 invoked from network); 23 Sep 2003 16:25:58 -0000 Received: from unknown (HELO HOST-192-168-17-31.internal.secureworks.net) (63.239.86.253) by mail.secureworks.net with SMTP; 23 Sep 2003 16:25:58 -0000 Date: Tue, 23 Sep 2003 12:28:07 -0400 (EDT) From: Matthew George X-X-Sender: mdg@localhost To: Luigi Rizzo In-Reply-To: <20030922134531.A44366@xorpc.icir.org> Message-ID: <20030923122509.S87821@localhost> References: <20030922134531.A44366@xorpc.icir.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-hackers@freebsd.org cc: Uwe Klann Subject: Re: IPFW2 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Sep 2003 16:28:32 -0000 On Mon, 22 Sep 2003, Luigi Rizzo wrote: > On Mon, Sep 22, 2003 at 08:07:13PM +0200, Uwe Klann wrote: > > Hi All, > > > > >From the Log file IPFW:- > > "Sep 22 00:24:13 muc /kernel: ipfw: 3300 Accept TCP 217.10.213.30:4418 > > 217.9.121.209:21 in via fxp0" > > > > How can I extend on FreeBSD 4.8 (ipfw2) the log contens to see the tranfered > > data File and the amount of bytes went out? Thank you in advance for your > > you can count the traffic with dynamic rules (but this does not go > to the logfile), not sure what you mean by 'see the transfered data file' from ipf(5): LOGGING When a packet is logged, with either the log action or option, the headers of the packet are written to the ipl packet logging psuedo- device. Immediately following the log keyword, the following qualifiers may be used (in order): body indicates that the first 128 bytes of the packet contents will be logged after the headers. I don't believe there is a comparable ipfw option ... > > luigi > > > > > > Uwe > > > > Uwe Klann > > Isensteinstr. 3 > > 80634 Munich > > Germany > > Mail: u.klann@t-online.de > > > > > > > > _______________________________________________ > > freebsd-hackers@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > -- Matthew George SecureWorks Technical Operations From owner-freebsd-hackers@FreeBSD.ORG Tue Sep 23 10:16:13 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B07C516A4B3 for ; Tue, 23 Sep 2003 10:16:13 -0700 (PDT) Received: from kientzle.com (h-66-166-149-50.SNVACAID.covad.net [66.166.149.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 12A2744001 for ; Tue, 23 Sep 2003 10:16:12 -0700 (PDT) (envelope-from kientzle@acm.org) Received: from acm.org ([66.166.149.54]) by kientzle.com (8.12.9/8.12.9) with ESMTP id h8NHGBkX083622; Tue, 23 Sep 2003 10:16:11 -0700 (PDT) (envelope-from kientzle@acm.org) Message-ID: <3F707FDB.4060600@acm.org> Date: Tue, 23 Sep 2003 10:16:11 -0700 From: Tim Kientzle User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3.1) Gecko/20030524 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Uwe Klann References: <20030922134531.A44366@xorpc.icir.org> <20030923122509.S87821@localhost> In-Reply-To: <20030923122509.S87821@localhost> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-hackers@freebsd.org Subject: Re: IPFW2 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: kientzle@acm.org List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Sep 2003 17:16:13 -0000 >>On Mon, Sep 22, 2003 at 08:07:13PM +0200, Uwe Klann wrote: >>> >>>>From the Log file IPFW:- >>>"Sep 22 00:24:13 muc /kernel: ipfw: 3300 Accept TCP 217.10.213.30:4418 >>>217.9.121.209:21 in via fxp0" >>> >>>How can I extend on FreeBSD 4.8 (ipfw2) the log contens to see the tranfered >>>data File and the amount of bytes went out? Thank you in advance for your tcpdump can be used to capture the full contents of particular packets. Use -w to write captured packets to a file, -r to read that file and examine the captured packets. Design your tcpdump capture expression carefully unless you have a lot of disk space. Port 21 is FTP, so I presume you're trying to monitor FTP activity. If you're using FreeBSD's ftpd, look at the -l and -S options (which provide fairly detailed logging of FTP activity). In particular, specifying -l twice claims to provide detailed logging of each transfer. Tim Kientzle From owner-freebsd-hackers@FreeBSD.ORG Tue Sep 23 11:31:30 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2778616A4B3 for ; Tue, 23 Sep 2003 11:31:30 -0700 (PDT) Received: from xorpc.icir.org (xorpc.icir.org [192.150.187.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 45C0E44005 for ; Tue, 23 Sep 2003 11:31:29 -0700 (PDT) (envelope-from rizzo@xorpc.icir.org) Received: from xorpc.icir.org (localhost [127.0.0.1]) by xorpc.icir.org (8.12.9p1/8.12.3) with ESMTP id h8NIVSsd024814; Tue, 23 Sep 2003 11:31:29 -0700 (PDT) (envelope-from rizzo@xorpc.icir.org) Received: (from rizzo@localhost) by xorpc.icir.org (8.12.9p1/8.12.3/Submit) id h8NIVQjd024813; Tue, 23 Sep 2003 11:31:26 -0700 (PDT) (envelope-from rizzo) Date: Tue, 23 Sep 2003 11:31:26 -0700 From: Luigi Rizzo To: Matthew George Message-ID: <20030923113126.A24717@xorpc.icir.org> References: <20030922134531.A44366@xorpc.icir.org> <20030923122509.S87821@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20030923122509.S87821@localhost>; from mdg@secureworks.net on Tue, Sep 23, 2003 at 12:28:07PM -0400 cc: freebsd-hackers@freebsd.org cc: Uwe Klann Subject: Re: IPFW2 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Sep 2003 18:31:30 -0000 On Tue, Sep 23, 2003 at 12:28:07PM -0400, Matthew George wrote: ... > > you can count the traffic with dynamic rules (but this does not go > > to the logfile), not sure what you mean by 'see the transfered data file' > > from ipf(5): > > LOGGING > When a packet is logged, with either the log action or option, the > headers of the packet are written to the ipl packet logging psuedo- > device. Immediately following the log keyword, the following qualifiers > may be used (in order): > > body indicates that the first 128 bytes of the packet contents will > be logged after the headers. > > I don't believe there is a comparable ipfw option ... no, there isn't. However the attached patch lets you run any bpf-based application on the packets which match an ipfw rule with 'log' specifier when net.inet.ip.fw.verbose=0, thus achieving a very similar if not a lot more powerful effect. Just use sysctl net.inet.ip.fw.verbose=0 ipfw add count log ... tcpdump -i ipfw0 ... cheers luigi Index: sys/netinet/ip_fw2.c =================================================================== RCS file: /home/ncvs/src/sys/netinet/ip_fw2.c,v retrieving revision 1.6.2.16 diff -u -r1.6.2.16 ip_fw2.c --- sys/netinet/ip_fw2.c 17 Jul 2003 06:03:39 -0000 1.6.2.16 +++ sys/netinet/ip_fw2.c 22 Sep 2003 22:21:38 -0000 @@ -51,10 +51,12 @@ #include #include #include +#include /* for SIOC* */ #include #include #include #include +#include /* for BPF */ #include #include #include @@ -225,9 +227,14 @@ &dyn_short_lifetime, 0, "Lifetime of dyn. rules for other situations"); SYSCTL_INT(_net_inet_ip_fw, OID_AUTO, dyn_keepalive, CTLFLAG_RW, &dyn_keepalive, 0, "Enable keepalives for dyn. rules"); +static int fw_bpf_info = 1; +SYSCTL_INT(_net_inet_ip_fw, OID_AUTO, bpf_info, + CTLFLAG_RW, + &fw_bpf_info, 0, "Add info in mac hdr"); #endif /* SYSCTL_NODE */ +static struct ifnet ifn; /* dummy ifnet to attach to bpf */ static ip_fw_chk_t ipfw_chk; @@ -1812,6 +1819,44 @@ case O_LOG: if (fw_verbose) ipfw_log(f, hlen, args->eh, m, oif); + else if (ifn.if_bpf != NULL) { + /* + * Prepend a (readonly) header, fill it + * with the real MAC header, or a dummy + * one if not available. In this case + * (layer3 packets) also restore the + * byte ordering of some fields, and put + * them back after bpf_mtap. + * If requested, the first two bytes + * of the src mac are replaced by the + * rule number for userland filtering. + */ + struct m_hdr mh; + struct ether_header my_eh; + char *h; + + mh.mh_next = m; + mh.mh_len = ETHER_HDR_LEN; + mh.mh_data = (char *)&my_eh; + if (args->eh) /* layer2, complete */ + h = (char *)args->eh; + else { + h = "DDDDDDSSSSSS\x08\x00"; + ip->ip_off = ntohs(ip->ip_off); + ip->ip_len = ntohs(ip->ip_len); + } + bcopy(h, &my_eh, ETHER_HDR_LEN); + if (fw_bpf_info) { + mh.mh_data[0] = f->rulenum >> 8; + mh.mh_data[1] = f->rulenum & 0xff; + } + bpf_mtap(&ifn, (struct mbuf *)&mh); + if (args->eh == NULL) { + /* restore IP format */ + ip->ip_off = htons(ip->ip_off); + ip->ip_len = htons(ip->ip_len); + } + } match = 1; break; @@ -2767,11 +2833,34 @@ ipfw_timeout_h = timeout(ipfw_tick, NULL, dyn_keepalive_period*hz); } +static int +ipfw_ifnet_ioctl(struct ifnet *ifp, u_long cmd, caddr_t addr) +{ + int error = 0; + + switch (cmd) { + default: + error = EINVAL; + break; + + case SIOCSIFADDR: + case SIOCGIFADDR: + case SIOCSIFFLAGS: + break; + } + return error; +} + static void ipfw_init(void) { struct ip_fw default_rule; + ifn.if_name = "ipfw"; + ifn.if_flags = IFF_UP | IFF_SIMPLEX | IFF_MULTICAST; + ifn.if_ioctl = ipfw_ifnet_ioctl; /* getaddr */ + ether_ifattach(&ifn, ETHER_BPF_SUPPORTED); + ip_fw_chk_ptr = ipfw_chk; ip_fw_ctl_ptr = ipfw_ctl; layer3_chain = NULL; @@ -2844,6 +2933,7 @@ err = EBUSY; #else s = splimp(); + ether_ifdetach(&ifn, 1 /* we want bpf */); untimeout(ipfw_tick, NULL, ipfw_timeout_h); ip_fw_chk_ptr = NULL; ip_fw_ctl_ptr = NULL; From owner-freebsd-hackers@FreeBSD.ORG Tue Sep 23 11:47:03 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6E88116A4B3 for ; Tue, 23 Sep 2003 11:47:03 -0700 (PDT) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7FC4943F93 for ; Tue, 23 Sep 2003 11:47:02 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mail.pcnet.com (8.12.10/8.12.1) with ESMTP id h8NIl1gG002067 for ; Tue, 23 Sep 2003 14:47:01 -0400 (EDT) Date: Tue, 23 Sep 2003 14:47:01 -0400 (EDT) From: Daniel Eischen X-Sender: eischen@pcnet5.pcnet.com To: hackers@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Wireless Embedded monitoring X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: deischen@freebsd.org List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Sep 2003 18:47:03 -0000 Anyone have any experience with PC/104 or other really small footprint platorms and FreeBSD? We need to build a small box for equipment monitoring (temperature, pressure diff., vibration, indication). Just a few discrete inputs/outputs, and analog inputs would be good enough. The hard part may be sampling an A/D signal at up to 30KHz, so having the I/O card do the sampling and buffer it would probably be necessary. The box would also need to have a supported wireless or a spare PCCard slot. Deployment would be in a shipyard in the Northeast, so being able to handle -30F to 100F would be necessary. Maintenance engineers would walk around on a daily or weekly basis and download sensor data from the monitors with a laptop (or some other handheld PC) for analysis (looking for equipment failures). Any ideas on hardware (SBC, I/O board)? -- Dan Eischen From owner-freebsd-hackers@FreeBSD.ORG Tue Sep 23 14:07:00 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0238A16A4B3; Tue, 23 Sep 2003 14:07:00 -0700 (PDT) Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5D3F843F3F; Tue, 23 Sep 2003 14:06:58 -0700 (PDT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.9p1/8.12.3) with ESMTP id h8NL6uGA067746; Tue, 23 Sep 2003 15:06:57 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Tue, 23 Sep 2003 15:06:57 -0600 (MDT) Message-Id: <20030923.150657.131323048.imp@bsdimp.com> To: deischen@freebsd.org, eischen@vigrid.com From: "M. Warner Losh" In-Reply-To: References: X-Mailer: Mew version 2.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: hackers@freebsd.org Subject: Re: Wireless Embedded monitoring X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Sep 2003 21:07:00 -0000 In message: Daniel Eischen writes: : Anyone have any experience with PC/104 or other really small : footprint platorms and FreeBSD? Yes. Works great. We've used FreeBSD on about two dozen different single board computers. : We need to build a small box for equipment monitoring (temperature, : pressure diff., vibration, indication). Just a few discrete : inputs/outputs, and analog inputs would be good enough. The : hard part may be sampling an A/D signal at up to 30KHz, so : having the I/O card do the sampling and buffer it would : probably be necessary. I'd recommend one of the Soekris boxes. : Any ideas on hardware (SBC, I/O board)? http://www.soekris.com is great. Warner From owner-freebsd-hackers@FreeBSD.ORG Tue Sep 23 15:03:26 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 81ABF16A4B3 for ; Tue, 23 Sep 2003 15:03:26 -0700 (PDT) Received: from smtp.omnis.com (smtp.omnis.com [216.239.128.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id EAB2443FD7 for ; Tue, 23 Sep 2003 15:03:24 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from salty.rapid.stbernard.com (corp-2.ipinc.com [199.245.188.2]) by smtp-relay.omnis.com (Postfix) with ESMTP id 0E9E15B690; Tue, 23 Sep 2003 15:03:24 -0700 (PDT) From: Wes Peters Organization: Softweyr.com To: Matt Peterson , freebsd-hackers@freebsd.org Date: Tue, 23 Sep 2003 15:03:23 -0700 User-Agent: KMail/1.5.2 References: <20030923001827.GA11677@forko.com> In-Reply-To: <20030923001827.GA11677@forko.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200309231503.23880.wes@softweyr.com> Subject: Re: percent support in sysinstall slice editor X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Sep 2003 22:03:26 -0000 On Monday 22 September 2003 17:18, Matt Peterson wrote: > Howdy, > > Would it be possible to add disk percentage support in the sysinstall > slice editor? That is, instead of building slice based on a fixed > size (ie: 5Gb) use percentage of the total disk size (ie: 25%). Yeah, that's a great idea! Where's your patch? ;^) -- "Where am I, and what am I doing in this handbasket?" Wes Peters wes@softweyr.com From owner-freebsd-hackers@FreeBSD.ORG Tue Sep 23 15:55:38 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8A32D16A4BF for ; Tue, 23 Sep 2003 15:55:38 -0700 (PDT) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id AA44443FEC for ; Tue, 23 Sep 2003 15:55:35 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mail.pcnet.com (8.12.10/8.12.1) with ESMTP id h8NMtUgG019259; Tue, 23 Sep 2003 18:55:30 -0400 (EDT) Date: Tue, 23 Sep 2003 18:55:30 -0400 (EDT) From: Daniel Eischen X-Sender: eischen@pcnet5.pcnet.com To: "M. Warner Losh" In-Reply-To: <20030923.150657.131323048.imp@bsdimp.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: hackers@freebsd.org Subject: Re: Wireless Embedded monitoring X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Sep 2003 22:55:38 -0000 On Tue, 23 Sep 2003, M. Warner Losh wrote: > In message: > Daniel Eischen writes: > : Anyone have any experience with PC/104 or other really small > : footprint platorms and FreeBSD? > > Yes. Works great. We've used FreeBSD on about two dozen different > single board computers. > > : We need to build a small box for equipment monitoring (temperature, > : pressure diff., vibration, indication). Just a few discrete > : inputs/outputs, and analog inputs would be good enough. The > : hard part may be sampling an A/D signal at up to 30KHz, so > : having the I/O card do the sampling and buffer it would > : probably be necessary. > > I'd recommend one of the Soekris boxes. > > : Any ideas on hardware (SBC, I/O board)? > > http://www.soekris.com is great. Yes, it looks nice. The form factor is just a bit larger than PC/104, especially with a PCCard plugged into its side. We'd also need some sort of general purpose I/O card which are fairly easy to find in PC/104 stacking modules. -- Dan Eischen From owner-freebsd-hackers@FreeBSD.ORG Tue Sep 23 15:56:37 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 63E6016A4B3 for ; Tue, 23 Sep 2003 15:56:37 -0700 (PDT) Received: from mail.praemunio.com (mail.praemunio.com [66.179.47.216]) by mx1.FreeBSD.org (Postfix) with SMTP id 6084743FE0 for ; Tue, 23 Sep 2003 15:56:36 -0700 (PDT) (envelope-from frank@knobbe.us) Received: from pcp563961pcs.rthfrd01.tn.comcast.net (HELO mail.knobbe.us) (68.53.41.27) by mail.praemunio.com with SMTP; 23 Sep 2003 17:56:35 -0500 Received: from localhost (HELO frankslaptop) by localhost with SMTP; 23 Sep 2003 17:56:34 -0500 Received: from localhost (HELO ??) by localhost with SMTP; 23 Sep 2003 17:56:28 -0500 From: Frank Knobbe To: freebsd-hackers@freebsd.org Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-JhX/Uv6tBaKSymIK3RyX" Message-Id: <1064357787.1067.77.camel@localhost> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.4 Date: Tue, 23 Sep 2003 17:56:28 -0500 Subject: FreeBSD on Cobalt Raq 4 (AMD) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Sep 2003 22:56:37 -0000 --=-JhX/Uv6tBaKSymIK3RyX Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Greetings, I've got a Cobalt Raq 4 here which is AMD (K6) based and has Linux installed. Instead of using it as a foot stool, I'd like to put FBSD on it and put it to real use. I'm aware of the NetBSD-on-Raq CD stuff which only works on non Intel Raqs.=20 The boot process seems to be the only hurdle. The box has Grub in the ROM and uses it to boot /boot/vmlinux. So BSD boot sector won't fly. My assembler is a bit rusty (no Intel hacking, only 65xx and 68xxx, and that quite some time ago :) If someone would like to assist in customizing the boot loader to boot BSD on that thing, please let me know. The rest of the box should be no problem for BSD (I2C bus, PCI bus, IDE and SCSI i/f, Dual Intel EtherExpress Pro). I tried to hack together a custom version of boot1.s and boot2.c so that Grub loads it (in place of vmlinux), and the loader then relocates, creates the boot environment and then loads the BSD kernel. I've gotten as far as it getting loaded and then faulting :/ I'm probably not relocating the code right or don't init the registers correctly or something. Any help here is appreciated. The idea is to have an executable (which grub will load to 0x100000) that relocates, created the boot environment and then loads the BSD kernel to 0x100000. Is -Hackers the right list or should this be moved to -Hardware? I'm more than happy to host a small list myself if there is interest in developing a loader for that Raq. I believe there are others out there that want to put FBSD on a Cobalt Raq 4.... Please me know if you are interested. Thanks, Frank --=-JhX/Uv6tBaKSymIK3RyX Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQA/cM+bpo+MRgtrF98RAg5zAJ9TzyF8HTmmF3oNbYuZ+B/yVlw3OACeKP7c w1yHqv9GhaBCalxVbdrXr08= =PTWM -----END PGP SIGNATURE----- --=-JhX/Uv6tBaKSymIK3RyX-- From owner-freebsd-hackers@FreeBSD.ORG Tue Sep 23 16:13:59 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A3D5716A4B3 for ; Tue, 23 Sep 2003 16:13:59 -0700 (PDT) Received: from mail.pacang.com (adsl-63-193-245-242.dsl.snfc21.pacbell.net [63.193.245.242]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0D9CF43FFD for ; Tue, 23 Sep 2003 16:13:59 -0700 (PDT) (envelope-from bservies@pacang.com) Received: by mail.pacang.com (Postfix, from userid 1000) id A6EF1292C1; Tue, 23 Sep 2003 16:13:58 -0700 (PDT) Date: Tue, 23 Sep 2003 16:13:58 -0700 From: Byron Servies To: Frank Knobbe Message-ID: <20030923231358.GB1613@owl.central> References: <1064357787.1067.77.camel@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1064357787.1067.77.camel@localhost> User-Agent: Mutt/1.4.1i cc: freebsd-hackers@freebsd.org Subject: Re: FreeBSD on Cobalt Raq 4 (AMD) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Sep 2003 23:13:59 -0000 On September 23, 2003 at 17:56, Frank Knobbe wrote: > Greetings, > > I've got a Cobalt Raq 4 here which is AMD (K6) based and has Linux > installed. Instead of using it as a foot stool, I'd like to put FBSD on > it and put it to real use. I'm aware of the NetBSD-on-Raq CD stuff which > only works on non Intel Raqs. > > The boot process seems to be the only hurdle. The box has Grub in the > ROM and uses it to boot /boot/vmlinux. So BSD boot sector won't fly. Take a look at: and see if the newer roms help out. There is a bsd boot option, but I don't know if it works or not. Byron From owner-freebsd-hackers@FreeBSD.ORG Tue Sep 23 19:12:23 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DB4A316A4B3 for ; Tue, 23 Sep 2003 19:12:23 -0700 (PDT) Received: from pixies.tirloni.org (pixies.tirloni.org [200.203.183.37]) by mx1.FreeBSD.org (Postfix) with ESMTP id CD23C43FBD for ; Tue, 23 Sep 2003 19:12:22 -0700 (PDT) (envelope-from tirloni@tirloni.org) Received: from localhost (pixies [200.203.183.37]) by pixies.tirloni.org (Postfix) with ESMTP id 5C4201E146F for ; Tue, 23 Sep 2003 23:12:20 -0300 (BRT) Received: from pixies.tirloni.org ([200.203.183.37]) by localhost (pixies.tirloni.org [200.203.183.37]) (amavisd-new, port 10024) with ESMTP id 63486-10 for ; Tue, 23 Sep 2003 23:12:19 -0300 (BRT) Received: by pixies.tirloni.org (Postfix, from userid 1000) id B731E1E1426; Tue, 23 Sep 2003 23:12:19 -0300 (BRT) Date: Tue, 23 Sep 2003 23:12:19 -0300 From: "Giovanni P. Tirloni" To: freebsd-hackers@freebsd.org Message-ID: <20030924021219.GV34641@pixies.tirloni.org> Mail-Followup-To: freebsd-hackers@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline User-Agent: Mutt/1.5.4i X-Virus-Scanned: by amavisd-new at tirloni.org Subject: mbuf doubts X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Sep 2003 02:12:24 -0000 Hi, I have been reading the D&I chapter about IPC, specially the mbuf section and *many* doubts were raised by my mind. I sending them here in the hope that someone can clarify some bits for me so I can proceed. Reading sys/param.h and sys/mbuf.h I came to the conclusion that there are four types of mbufs regarding it's allocation of memory for data. Is the listing below correct? struct mbuf *m; 1. Normal mbuf using m->M_databuf 2. Normal mbuf with external storage (cluster?) in m->m_hdr->mh_data 3. Header mbuf using m->m_pktdat; 4. Header mbuf with ext. storage (cluster?) in m->m_ext->ext_buf Other questions: 1. When using ext. storage is the space allocated by M_databuf wasted? 2. How the system decides 256 bytes for each mbuf isn't enough and it needs a mbuf cluster? Isn't chaining useful there? 3. How does changing MSIZE affects the whole thing? 4. What about MCLBYTES? Sorry to make so many questions at once but I find it very interesting and I'm really willing to learn how the building blocks of the network stack work. Perhaps my questions are out of reality.. it's risk. Thanks, -- Giovanni P. Tirloni Fingerprint: 8C3F BEC5 79BD 3E9B EDB8 72F4 16E8 BA5E D031 5C26 From owner-freebsd-hackers@FreeBSD.ORG Tue Sep 23 20:15:18 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B5A1716A4B3 for ; Tue, 23 Sep 2003 20:15:18 -0700 (PDT) Received: from srv1.cosmo-project.de (srv1.cosmo-project.de [213.83.6.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id DBE9D43FF9 for ; Tue, 23 Sep 2003 20:15:16 -0700 (PDT) (envelope-from andreas@klemm.apsfilter.org) Received: from srv1.cosmo-project.de (localhost [IPv6:::1]) h8O3FBFs058309 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 24 Sep 2003 05:15:14 +0200 (CEST) (envelope-from andreas@klemm.apsfilter.org) Received: (from uucp@localhost)h8O3FBZg058308; Wed, 24 Sep 2003 05:15:11 +0200 (CEST) (envelope-from andreas@klemm.apsfilter.org) Received: from titan.klemm.apsfilter.org (localhost.klemm.apsfilter.org [127.0.0.1]) by klemm.apsfilter.org (8.12.10/8.12.9) with ESMTP id h8O3CPMf013291; Wed, 24 Sep 2003 05:12:25 +0200 (CEST) (envelope-from andreas@titan.klemm.apsfilter.org) Received: (from andreas@localhost)h8O3CKje013290; Wed, 24 Sep 2003 05:12:20 +0200 (CEST) Date: Wed, 24 Sep 2003 05:12:20 +0200 From: Andreas Klemm To: Martin Nilsson Message-ID: <20030924031220.GA13256@titan.klemm.apsfilter.org> References: <000e01c36821$a78f9440$ae28a8c0@SREELAPTOP> <3F4644F1.9060306@gneto.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3F4644F1.9060306@gneto.com> X-Operating-System: FreeBSD 5.1-CURRENT X-Disclaimer: A free society is one where it is safe to be unpopular User-Agent: Mutt/1.5.4i cc: freebsd-hackers@freebsd.org Subject: Re: Intel and Broadcom NICs X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Sep 2003 03:15:18 -0000 On Fri, Aug 22, 2003 at 06:29:37PM +0200, Martin Nilsson wrote: > Sreekanth wrote: > > >The intel nic is a fxp interface.Device ID 1050("Intel 82801BA (D865) > >Pro/100 VE Ethernet")You probably need to use the latest driver from > >current.To make sure you have the driver check if you have this line > > { 0x1050, -1, "Intel 82801BA (D865) Pro/100 VE Ethernet" }, in > >if_fxp.c > > Wouldn't it be a good idea to MFC this in time for the 4.9 release, the > intel 865 chipset is rather common in new machines these days. Yes good idea, my next Laptop, a Dell Dimension 600 or 700 (don't remember) will have a 10/100/1000 broadcom adapter. Andreas /// -- Andreas Klemm - Powered by FreeBSD 5.1-CURRENT Need a magic printfilter today ? -> http://www.apsfilter.org/ From owner-freebsd-hackers@FreeBSD.ORG Tue Sep 23 20:20:24 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3DDA716A4B3 for ; Tue, 23 Sep 2003 20:20:24 -0700 (PDT) Received: from srv1.cosmo-project.de (srv1.cosmo-project.de [213.83.6.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id D072343FF3 for ; Tue, 23 Sep 2003 20:20:22 -0700 (PDT) (envelope-from andreas@klemm.apsfilter.org) Received: from srv1.cosmo-project.de (localhost [IPv6:::1]) h8O3KGFs058351 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 24 Sep 2003 05:20:19 +0200 (CEST) (envelope-from andreas@klemm.apsfilter.org) Received: (from uucp@localhost)h8O3KEoX058350; Wed, 24 Sep 2003 05:20:15 +0200 (CEST) (envelope-from andreas@klemm.apsfilter.org) Received: from titan.klemm.apsfilter.org (localhost.klemm.apsfilter.org [127.0.0.1]) by klemm.apsfilter.org (8.12.10/8.12.9) with ESMTP id h8O3GTMf013430; Wed, 24 Sep 2003 05:16:29 +0200 (CEST) (envelope-from andreas@titan.klemm.apsfilter.org) Received: (from andreas@localhost)h8O3GSrK013429; Wed, 24 Sep 2003 05:16:28 +0200 (CEST) Date: Wed, 24 Sep 2003 05:16:28 +0200 From: Andreas Klemm To: Charles Howse Message-ID: <20030924031628.GB13256@titan.klemm.apsfilter.org> References: <001c01c36a7f$7856a140$04fea8c0@moe> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <001c01c36a7f$7856a140$04fea8c0@moe> X-Operating-System: FreeBSD 5.1-CURRENT X-Disclaimer: A free society is one where it is safe to be unpopular User-Agent: Mutt/1.5.4i cc: freebsd-hackers@freebsd.org Subject: Re: Looking for detailed documentation: Install to existing filesystem X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Sep 2003 03:20:24 -0000 read the damn handbook ;-) this lookup of information costed me 1 minute. http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/install-media.html Place the files that you find on the FreeBSD installation CD-ROM into a DOS or UFS filesystem. Then install from that. Andreas /// -- Andreas Klemm - Powered by FreeBSD 5.1-CURRENT Need a magic printfilter today ? -> http://www.apsfilter.org/ From owner-freebsd-hackers@FreeBSD.ORG Tue Sep 23 20:54:05 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 343D016A4B3 for ; Tue, 23 Sep 2003 20:54:05 -0700 (PDT) Received: from smtpout.mac.com (A17-250-248-87.apple.com [17.250.248.87]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7A2E543FE1 for ; Tue, 23 Sep 2003 20:54:03 -0700 (PDT) (envelope-from justin@mac.com) Received: from mac.com (smtpin07-en2 [10.13.10.152]) by smtpout.mac.com (Xserve/MantshX 2.0) with ESMTP id h8O3s30Q011049 for ; Tue, 23 Sep 2003 20:54:03 -0700 (PDT) Received: from mac.com (12-210-49-211.client.attbi.com [12.210.49.211]) (authenticated bits=0) by mac.com (Xserve/smtpin07/MantshX 3.0) with ESMTP id h8O3s1A2003638 (version=TLSv1/SSLv3 cipher=DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 23 Sep 2003 20:54:02 -0700 (PDT) Date: Tue, 23 Sep 2003 20:54:01 -0700 Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v552) From: "Justin C. Walker" To: freebsd-hackers@freebsd.org Content-Transfer-Encoding: 7bit In-Reply-To: <20030924021219.GV34641@pixies.tirloni.org> Message-Id: X-Mailer: Apple Mail (2.552) Subject: Re: mbuf doubts X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Sep 2003 03:54:05 -0000 I'm not an expert on all BSD-derived stacks and the way mbufs are defined and used in each, but: On Tuesday, September 23, 2003, at 07:12 PM, Giovanni P. Tirloni wrote: > struct mbuf *m; > > 1. Normal mbuf using m->M_databuf M_databuf is the beginning of the data area in an mbuf > 2. Normal mbuf with external storage (cluster?) in m->m_hdr->mh_data mh_data *always* points to the beginning of valid data or available space. The bit M_EXT indicates whether mh_data points into the external storage, or into the area beginning at M_databuf. > 3. Header mbuf using m->m_pktdat; This is used to access the data in an mbuf when the M_PKTHDR bit is set in the m_flags word. This is because extra space in this lead mbuf is taken up with local information pertaining to the packet and its handling. I'm not entirely clear on how it's used. > 4. Header mbuf with ext. storage (cluster?) in m->m_ext->ext_buf This points to the external storage buffer. It can be a cluster, or it can be other data areas. I believe the distinction is made based on the field ext_free in the m_ext structure (if non-null, it points to a routine to free data, and thus the external storage is *not* a cluster). > Other questions: > 1. When using ext. storage is the space allocated by M_databuf > wasted? Yes. > 2. How the system decides 256 bytes for each mbuf isn't enough and it > needs a mbuf cluster? Isn't chaining useful there? There is a constant (MINCLSIZE) that the system uses to decide when to allocate a cluster, and when to use a chain of normal mbufs. If the size is greater than MINCLSIZE, it opts for a cluster. Note that you can sometimes notice the effect of MINCLSIZE on the performance of both the system and the network, so the choice of this value can be important. It is normally set to a value that goes to clusters when two mbufs won't suffice. > 3. How does changing MSIZE affects the whole thing? Significantly :-}. This is a gnarly subject. You have to balance wasted space, time, and other subtle details (typical packet sizes vs. mbuf size; time spent dealing with chains vs. time spent dealing with clusters; ...). At one point, for example, packet sizes on the internet were strongly "bi-modal" (small packets for telnet; max-sized packets for ftp). More recently, I suspect that this has changed, but I don't know what the distribution looks like now. > 4. What about MCLBYTES? Same set of issues. AIX, for example, has a "power-of-2" collection of mbuf pools, and tries to allocate from the best pool for the requested size, bumping up at most two levels to fill empty pools. Other BSDs stick with a single size, generally 2048 bytes; this makes jumbo ethernet packets kind of expensive. Check out Wright/Stevens, "TCP/IP Illustrated, V.2", Addison Wesley, 1995. Ch. 2 is a fairly in-depth discussion of the above. It deals with a long-dead version of BSD, but the fundamentals have not changed that much. In addition, the book is a very well-done code walkthrough of the networking code in BSD (again, from long ago, but the "bones" are good). Regards, Justin -- Justin C. Walker, Curmudgeon-At-Large * Institute for General Semantics | It's not whether you win or lose... | It's whether *I* win or lose. *--------------------------------------*-------------------------------* From owner-freebsd-hackers@FreeBSD.ORG Wed Sep 24 08:22:05 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C749D16A4B3 for ; Wed, 24 Sep 2003 08:22:05 -0700 (PDT) Received: from pony1pub.arc.nasa.gov (pony1pub.arc.nasa.gov [128.102.31.41]) by mx1.FreeBSD.org (Postfix) with ESMTP id 107B944015 for ; Wed, 24 Sep 2003 08:22:01 -0700 (PDT) (envelope-from jtoung@arc.nasa.gov) Received: from nren-194.arc.nasa.gov ([128.102.196.194] verified) by pony1pub.arc.nasa.gov (CommuniGate Pro SMTP 4.1.3) with ESMTP id 3481345; Wed, 24 Sep 2003 08:22:00 -0700 Content-Type: text/plain; charset="iso-8859-1" From: Jerry Toung To: "Giovanni P. Tirloni" , freebsd-hackers@freebsd.org Date: Wed, 24 Sep 2003 08:21:26 -0700 User-Agent: KMail/1.4.3 References: <20030924021219.GV34641@pixies.tirloni.org> In-Reply-To: <20030924021219.GV34641@pixies.tirloni.org> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Message-Id: <200309240821.26331.jtoung@arc.nasa.gov> Subject: Re: mbuf doubts X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: jtoung@arc.nasa.gov List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Sep 2003 15:22:05 -0000 Giovani, you will find the answer to your question in "tcp/ip illustrated, volume = 2:=20 the implementation" in chapter 2. But to briefly answer your question, yes, there are 4 different types of=20 mbufs, depending on the m_flags value. 1) m_flags =3D 0 and mbuf contains only data up to 108 bytes. 2) m_flags =3D M_PKTHDR to designate a packet header. 3)m_flags =3D M_EXT. In a situation where a user process write() in a buf= fer >=20 256 bytes, the system allocates a cluster to hold that data. 4) m_flags =3D M_EXT|M_PKTHDR and yes when using clusters, the memory in the mbuf is unsed. hop that helped. Jerry On Tuesday 23 September 2003 07:12 pm, Giovanni P. Tirloni wrote: > Hi, > > I have been reading the D&I chapter about IPC, specially the mbuf > section and *many* doubts were raised by my mind. I sending them here > in the hope that someone can clarify some bits for me so I can proceed= =2E > > Reading sys/param.h and sys/mbuf.h I came to the conclusion that there > are four types of mbufs regarding it's allocation of memory for data. > Is the listing below correct? > > struct mbuf *m; > > 1. Normal mbuf using m->M_databuf > 2. Normal mbuf with external storage (cluster?) in m->m_hdr->mh_data > 3. Header mbuf using m->m_pktdat; > 4. Header mbuf with ext. storage (cluster?) in m->m_ext->ext_buf > > Other questions: > > 1. When using ext. storage is the space allocated by M_databuf wasted= ? > > 2. How the system decides 256 bytes for each mbuf isn't enough and it > needs a mbuf cluster? Isn't chaining useful there? > > 3. How does changing MSIZE affects the whole thing? > > 4. What about MCLBYTES? > > Sorry to make so many questions at once but I find it very interesting > and I'm really willing to learn how the building blocks of the network > stack work. Perhaps my questions are out of reality.. it's risk. > > Thanks, > > -- > Giovanni P. Tirloni > Fingerprint: 8C3F BEC5 79BD 3E9B EDB8 72F4 16E8 BA5E D031 5C26 From owner-freebsd-hackers@FreeBSD.ORG Wed Sep 24 09:33:59 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1955616A4BF for ; Wed, 24 Sep 2003 09:33:59 -0700 (PDT) Received: from dastardly.newsbastards.org.72.27.172.IN-addr.ARPA.NOSPAM.dyndns.dk (B76a1.pppool.de [213.7.118.161]) by mx1.FreeBSD.org (Postfix) with ESMTP id 991D844014 for ; Wed, 24 Sep 2003 09:33:20 -0700 (PDT) (envelope-from bounce@NOSPAM.dyndns.dk) Received: from Mail.NOSPAM.DynDNS.dK (ipv6.NOSPAM.dyndns.dk [2002:d507:76a1:0:220:afff:fed4:dbcb]) (8.11.6/8.11.6-SPAMMERS-DeLiGHt) with ESMTP id h8OGWg402771 verified NO) for ; Wed, 24 Sep 2003 18:32:58 +0200 (CEST) (envelope-from bounce@NOSPAM.dyndns.dk) Received: (from beer@localhost) by Mail.NOSPAM.DynDNS.dK (8.11.6/FNORD) id h8OGWgs02770; Wed, 24 Sep 2003 18:32:42 +0200 (CEST) (envelope-from bounce@NOSPAM.dyndns.dk) Date: Wed, 24 Sep 2003 18:32:42 +0200 (CEST) Message-Id: <200309241632.h8OGWgs02770@Mail.NOSPAM.DynDNS.dK> X-Authentication-Warning: localhost.newsbastards.org.72.27.172.IN-addr.A: beer set sender to bounce@NOSPAM.dyndns.dk using -f X-Authentication-Warning: localhost.newsbastards.org.72.27.172.IN-addr.A: Processed from queue /tmp X-Authentication-Warning: localhost.newsbastards.org.72.27.172.IN-addr.A: Processed by beer with -C /etc/mail/sendmail.cf-LOCAL From: Barry Bouwsma To: FreeBSD Hacking Group Subject: USB card overcurrent problems... X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Sep 2003 16:33:59 -0000 [Drop hostname part of IPv6-only address above to obtain IPv4-capable e-mail, or just drop me from the recipients and I'll catch up from the archives] Hello every last one of you, First, before I spout off in the wrong forum, is there a better or preferred location for USB-hardware-related questions like that which follows, akin to the firewire list? Okay, the question: I have two cards with USB2.0 awareness, used for their USB 1.x capability under FreeBSD 4.x. One of them, a UHCI card, works just fine, but the other one, an OHCI card, out-of-the-box exhibits problems. Chipset is identified in dmesg as NEC uPD 9210 USB controller. What happens, when I put it in a machine that it doesn't promptly wedge at boot or soon afterwards, is that the uhub/ohci USB codes from 4.5-RC up to 4.7 of last December (and now even recent 4.9-prerelease codes; haven't tried the NetBSD codes they originate from) result in the internal hub going dead (being disabled) when a bus-powered external USB2 hub device is connected to it -- the other card (UHCI) has no problems with repeated attach/detaches of this external hub. There is no obvious problem when connecting a self-powered device like that external hub with wall wart, or an external hard drive. Observation of the power indicator on the external hub shows that at time of attachment, it lights very briefly and then immediately goes out, and repeated unplug/re-plugging of the USB cable results in no further activity. Adding copious debuggery to the kernel indicates that at time of connecting the hub, the status of the internal port changes to unpowered and the change variable has the overcurrent bit set. Assuming that I don't have a truly wimpy piece of hardware (I haven't tried it under any non-*BSD OSen), it should durn well be able to power this hub, but perhaps the power-on surge of current into the filter capacitors is triggering this (temporary?) overcurrent indication. In fact, I was able to get the power indicator to come on and stay lit on the external hub by checking for an overcurrent condition in uhub.c, and then clearing the bit and re-applying power. Not 100% reliably, but later hacking (this evening) seems to have improved that, at the risk of ignoring a Real Overcurrent indication. What would be the proper changes to the code, after testing for such an overcurrent condition, in order to safely reapply power until such condition clears? Adding a delay somewhere? Limiting the number of times I try to re-apply power before bailing? (This last boot took some 5 or 6 tries until it came up okay in a tight loop) (There are comments in the source, imported from NetBSD, that some work- arounds for an overcurrent problem have been applied, but those did not seem to make any difference to me. Also, as noted, I haven't yet tried NetBSD from which these workarounds came, to see if there may be any not- yet-imported fixes that make my device work.) Also, I found that when applying the power within the test for overcurrent, that clearing the overcurrent change did not necessarily re-enable the interrupts, so I added that test to the routine that applies power, if that's safe to do. I'm probably not describing things well, but I'm positive my hacks aren't at all proper, so I'd rather learn the right way to handle this case before explaining where I run into problems. And, I'll have more USB-related questions later, so pointers to the proper place for those would be appreciated, if this list isn't it. Thanks, Barry Bouwsma From owner-freebsd-hackers@FreeBSD.ORG Wed Sep 24 09:34:55 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 13FA516A4B3 for ; Wed, 24 Sep 2003 09:34:55 -0700 (PDT) Received: from dastardly.newsbastards.org.72.27.172.IN-addr.ARPA.NOSPAM.dyndns.dk (B76a1.pppool.de [213.7.118.161]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0FCD143FE3 for ; Wed, 24 Sep 2003 09:34:04 -0700 (PDT) (envelope-from bounce@NOSPAM.dyndns.dk) Received: from Mail.NOSPAM.DynDNS.dK (ipv6.NOSPAM.dyndns.dk [2002:d507:76a1:0:220:afff:fed4:dbcb]) (8.11.6/8.11.6-SPAMMERS-DeLiGHt) with ESMTP id h8OGXn402783 verified NO) for ; Wed, 24 Sep 2003 18:33:50 +0200 (CEST) (envelope-from bounce@NOSPAM.dyndns.dk) Received: (from beer@localhost) by Mail.NOSPAM.DynDNS.dK (8.11.6/FNORD) id h8OGXnT02782; Wed, 24 Sep 2003 18:33:49 +0200 (CEST) (envelope-from bounce@NOSPAM.dyndns.dk) Date: Wed, 24 Sep 2003 18:33:49 +0200 (CEST) Message-Id: <200309241633.h8OGXnT02782@Mail.NOSPAM.DynDNS.dK> X-Authentication-Warning: localhost.newsbastards.org.72.27.172.IN-addr.A: beer set sender to bounce@NOSPAM.dyndns.dk using -f X-Authentication-Warning: localhost.newsbastards.org.72.27.172.IN-addr.A: Processed from queue /tmp X-Authentication-Warning: localhost.newsbastards.org.72.27.172.IN-addr.A: Processed by beer with -C /etc/mail/sendmail.cf-LOCAL From: Barry Bouwsma To: FreeBSD Hacking Group Subject: Kernel module problems/questions X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Sep 2003 16:34:55 -0000 [You know the drill: drop my hostname from the above IPv6-only address to get an IPv4-capable address; drop me entirely to avoid bounces and I'll catch the archives before your mail might reach me if it doesn't bounce] Some stupid kernel module questions. Kernel source from a few days ago, RELENG_4. First, why would USB-related modules whose source explicitly declares a DEPEND on the usb.ko module, fail to auto-load the usb module when they're kldload'ed? They fail with various undefined symbol errors, and there's no trace of any attempt to load the usb module. Second, why do some USB devices declare a module dependency on usb, while others (say, umass) do not? Ignoring that the usb auto-load fails for now. Third, if I load the usb.ko module by hand, everything works, except that I can't unload the usb.ko module. The error is `Device not configured.' To make this a question, I'll add: Why is this? Fourth, after boot, if I load, say, sbp.ko, it auto-loads firewire.ko, and attempts to unload firewire are denied so long as sbp.ko remains loaded. But if at boot, I've mangled the loader.conf to load sbp.ko, which then auto-loads firewire.ko, I *am* able to unload firewire.ko later by hand. Then unloading sbp.ko promptly results in a kernel panic. So, why can I unload modules auto-loaded at boot, when I'm denied unloading the same modules auto-loaded after boot? The desired behaviour would be *not* to be able to unload any auto-loaded modules, regardless. Fifth, I've run out of questions for now. Tune in again later. Thanks, Barry Bouwsma From owner-freebsd-hackers@FreeBSD.ORG Wed Sep 24 09:38:51 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B852416A4B3 for ; Wed, 24 Sep 2003 09:38:51 -0700 (PDT) Received: from dastardly.newsbastards.org.72.27.172.IN-addr.ARPA.NOSPAM.dyndns.dk (B76a1.pppool.de [213.7.118.161]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8D81D44008 for ; Wed, 24 Sep 2003 09:36:16 -0700 (PDT) (envelope-from bounce@NOSPAM.dyndns.dk) Received: from Mail.NOSPAM.DynDNS.dK (ipv6.NOSPAM.dyndns.dk [2002:d507:76a1:0:220:afff:fed4:dbcb]) (8.11.6/8.11.6-SPAMMERS-DeLiGHt) with ESMTP id h8OGYB402796 verified NO) for ; Wed, 24 Sep 2003 18:34:13 +0200 (CEST) (envelope-from bounce@NOSPAM.dyndns.dk) Received: (from beer@localhost) by Mail.NOSPAM.DynDNS.dK (8.11.6/FNORD) id h8OGYBr02795; Wed, 24 Sep 2003 18:34:11 +0200 (CEST) (envelope-from bounce@NOSPAM.dyndns.dk) Date: Wed, 24 Sep 2003 18:34:11 +0200 (CEST) Message-Id: <200309241634.h8OGYBr02795@Mail.NOSPAM.DynDNS.dK> X-Authentication-Warning: localhost.newsbastards.org.72.27.172.IN-addr.A: beer set sender to bounce@NOSPAM.dyndns.dk using -f X-Authentication-Warning: localhost.newsbastards.org.72.27.172.IN-addr.A: Processed from queue /tmp X-Authentication-Warning: localhost.newsbastards.org.72.27.172.IN-addr.A: Processed by beer with -C /etc/mail/sendmail.cf-LOCAL From: Barry Bouwsma References: <200309152127.h8FLRrv71220@Mail.NOSPAM.DynDNS.dK> <200309180455.h8I4tBK58276@Mail.NOSPAM.DynDNS.dK> <3F697DBF.9CE6E9C@mindspring.com> To: FreeBSD List of Hackers Subject: Re: Machine wedges solid after one serial-port source-lineaddition... X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Sep 2003 16:38:51 -0000 [Drop hostname part of IPv6-only address above to obtain IPv4-capable e-mail, or just drop me from the recipients and I'll catch up from the archives] Terry Lambert writes: > I remember wakeup() being bad. Taking any time to do anything > at all more than just queueing data and going away is probably > bad. Then that's probably why it worked fine for some hours, then failed miserably. Thanks! > If it were my project, I'd mirror the values out to a status > structure that's only written at interrupt, and read and reset > at software interrupt, and then use the soft interrupt handler > to raise the signals/send the wakeup/whatever and then resets > the flags bits to zero via a call down that synchronizes like Maybe I'll turn back to this, when I'm older and wiser. But also, serial ports are a scarcity for me, so I'm wondering what else I can use to get precise timing information, to free up the serial port for something else. I wrote earlier (from an invalid address that probably most list readers rejected as spam) that I had a problem accessing the parallel port nACK as /dev/pps for the precise timing already present in the kernel source, and simultaneously as /dev/ppi for coarse timing via polling from which I'd determine the time that the PPS signal refers to. I tried adding printf()s to various parallel-port kernel code to see if there might be an interrupt I could jump onto for each transition of the nACK status line, but I suspect my lack of success with both swings of the signal has to do with not doing it right. So I'll ask a basic question here, forgive my ignorance: Can the lines of the parallel port be used to generate interrupts that I can use, in the same way that I've been able to use the four serial port status lines, or is this right out? And another question, I see three unused joystick connectors on the three sound cards in my machine, that are less likely to be used than the so-far- unused parallel port. Would it be possible to get interrupts from the sound card's joystick connector, when interfaced with suitable hardware to the radio clock output, that I would also theoretically be able to use? Or is this also something I'd need to poll the status of the switch(es), so only coarse precision would be possible? Please excuse my basic ignorance of fundamental PC hardware principles, and I'll welcome pointers to sources of more knowledge. Thanks, Barry Bouwsma From owner-freebsd-hackers@FreeBSD.ORG Wed Sep 24 09:39:06 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 34AE016A4B3 for ; Wed, 24 Sep 2003 09:39:06 -0700 (PDT) Received: from dastardly.newsbastards.org.72.27.172.IN-addr.ARPA.NOSPAM.dyndns.dk (B76a1.pppool.de [213.7.118.161]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0A54B43FAF for ; Wed, 24 Sep 2003 09:38:48 -0700 (PDT) (envelope-from bounce@NOSPAM.dyndns.dk) Received: from Mail.NOSPAM.DynDNS.dK (ipv6.NOSPAM.dyndns.dk [2002:d507:76a1:0:220:afff:fed4:dbcb]) (8.11.6/8.11.6-SPAMMERS-DeLiGHt) with ESMTP id h8OGY2402789 verified NO) for ; Wed, 24 Sep 2003 18:34:04 +0200 (CEST) (envelope-from bounce@NOSPAM.dyndns.dk) Received: (from beer@localhost) by Mail.NOSPAM.DynDNS.dK (8.11.6/FNORD) id h8OGY2D02788; Wed, 24 Sep 2003 18:34:02 +0200 (CEST) (envelope-from bounce@NOSPAM.dyndns.dk) Date: Wed, 24 Sep 2003 18:34:02 +0200 (CEST) Message-Id: <200309241634.h8OGY2D02788@Mail.NOSPAM.DynDNS.dK> X-Authentication-Warning: localhost.newsbastards.org.72.27.172.IN-addr.A: beer set sender to bounce@NOSPAM.dyndns.dk using -f X-Authentication-Warning: localhost.newsbastards.org.72.27.172.IN-addr.A: Processed from queue /tmp X-Authentication-Warning: localhost.newsbastards.org.72.27.172.IN-addr.A: Processed by beer with -C /etc/mail/sendmail.cf-LOCAL From: Barry Bouwsma References: <20030916102356.A11571@lava.net> <20030919100922.GV79731@freepuppy.bellavista.cz> To: freebsd-hackers@freebsd.org Subject: Re: Any workarounds for Verisign .com/.net highjacking? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Sep 2003 16:39:06 -0000 [obligatory From: address is IPv6-only; to obtain IPv4-mailable address, remove hostname part. Even then no guarantee mail won't bounce -- I follow the list archives in my copious offline time] > > > In the meantime I'm trying to figure out if there's some > > >simple hack to disregard these wildcard A records, short of > > I have no idea of how well either of these work. Use your > > own discretion at applying them. > djbdns-1.05-ignoreip2.patch seems to work very well here, on three A stupid question, no less, since I see this being discussed here -- is it correct that the ISC BIND patch does not work with a nameserver that's set up as a forward-only box? I've applied the patch to a random BIND successfully, but I'm configured as forward-only for the domains I don't dish out, being on the unpleasant end of a PPP dial-in and trying to do my part to keep the root nameservers' load down. I nab the ISP-provided DNS addresses during the PPP handshake, configure them as forwarders (plus one or two backups) and restart named, but still I was able to resolve a made-up com domain to the Usual Address. This tells me I need to use the DNS machines of an ISP with Clue as static forwarder addresses, not those provided by ISP-of-the-day (and the last ISP seemed to give horribly broken machines anyway), if this reaches a point where I actually want to do something about these wildcards. Provided the ISP allows outgoing DNS queries too. Thanks, Barry Bouwsma From owner-freebsd-hackers@FreeBSD.ORG Wed Sep 24 09:55:42 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8D75216A4C3 for ; Wed, 24 Sep 2003 09:55:42 -0700 (PDT) Received: from pixies.tirloni.org (pixies.tirloni.org [200.203.183.37]) by mx1.FreeBSD.org (Postfix) with ESMTP id D54E943FD7 for ; Wed, 24 Sep 2003 09:55:38 -0700 (PDT) (envelope-from tirloni@tirloni.org) Received: from localhost (pixies [200.203.183.37]) by pixies.tirloni.org (Postfix) with ESMTP id 1133C1E146F; Wed, 24 Sep 2003 13:55:37 -0300 (BRT) Received: from pixies.tirloni.org ([200.203.183.37]) by localhost (pixies.tirloni.org [200.203.183.37]) (amavisd-new, port 10024) with ESMTP id 32613-08; Wed, 24 Sep 2003 13:55:35 -0300 (BRT) Received: by pixies.tirloni.org (Postfix, from userid 1000) id 9B9E81E1426; Wed, 24 Sep 2003 13:55:35 -0300 (BRT) Date: Wed, 24 Sep 2003 13:55:35 -0300 From: "Giovanni P. Tirloni" To: freebsd-hackers@freebsd.org Message-ID: <20030924165535.GA79874@pixies.tirloni.org> Mail-Followup-To: freebsd-hackers@freebsd.org, jtoung@arc.nasa.gov, justin@mac.com References: <20030924021219.GV34641@pixies.tirloni.org> <200309240821.26331.jtoung@arc.nasa.gov> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline In-Reply-To: <200309240821.26331.jtoung@arc.nasa.gov> X-Info: http://www.tirloni.org User-Agent: Mutt/1.5.4i X-Virus-Scanned: by amavisd-new at tirloni.org cc: jtoung@arc.nasa.gov Subject: Re: mbuf doubts X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Sep 2003 16:55:42 -0000 * Jerry Toung (jtoung@arc.nasa.gov) wrote: > Giovani, > > you will find the answer to your question in "tcp/ip illustrated, volume 2: > the implementation" in chapter 2. > > But to briefly answer your question, yes, there are 4 different types of > mbufs, depending on the m_flags value. > 1) m_flags = 0 and mbuf contains only data up to 108 bytes. > 2) m_flags = M_PKTHDR to designate a packet header. > 3)m_flags = M_EXT. In a situation where a user process write() in a buffer > > 256 bytes, the system allocates a cluster to hold that data. > 4) m_flags = M_EXT|M_PKTHDR > > and yes when using clusters, the memory in the mbuf is unsed. > > hop that helped. Thank you very much Justin and Jerry for the answers. They were very helpful. I'm already getting my copy of Steven's :-) -- Giovanni P. Tirloni Fingerprint: 8C3F BEC5 79BD 3E9B EDB8 72F4 16E8 BA5E D031 5C26 From owner-freebsd-hackers@FreeBSD.ORG Wed Sep 24 12:19:36 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A6F9F16A4B3 for ; Wed, 24 Sep 2003 12:19:36 -0700 (PDT) Received: from srv1.cosmo-project.de (srv1.cosmo-project.de [213.83.6.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id ADC1A43FE0 for ; Wed, 24 Sep 2003 12:19:08 -0700 (PDT) (envelope-from ticso@cicely12.cicely.de) Received: from cicely5.cicely.de (cicely5.cicely.de [IPv6:3ffe:400:8d0:301:200:92ff:fe9b:20e7]) (authenticated bits=0) h8OJHfFs079114 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=OK) for ; Wed, 24 Sep 2003 21:17:44 +0200 (CEST) (envelope-from ticso@cicely12.cicely.de) Received: from cicely12.cicely.de (cicely12.cicely.de [IPv6:3ffe:400:8d0:301::12]) by cicely5.cicely.de (8.12.10/8.12.10) with ESMTP id h8OJDdWZ037811 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 24 Sep 2003 21:13:40 +0200 (CEST) (envelope-from ticso@cicely12.cicely.de) Received: from cicely12.cicely.de (localhost [127.0.0.1]) by cicely12.cicely.de (8.12.9/8.12.9) with ESMTP id h8OJDdrY090163 for ; Wed, 24 Sep 2003 21:13:39 +0200 (CEST) (envelope-from ticso@cicely12.cicely.de) Received: (from ticso@localhost) by cicely12.cicely.de (8.12.9/8.12.9/Submit) id h8OJCIY3090146; Wed, 24 Sep 2003 21:12:18 +0200 (CEST) Date: Wed, 24 Sep 2003 21:12:18 +0200 From: Bernd Walter To: Barry Bouwsma Message-ID: <20030924191217.GZ21665@cicely12.cicely.de> References: <200309241632.h8OGWgs02770@Mail.NOSPAM.DynDNS.dK> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200309241632.h8OGWgs02770@Mail.NOSPAM.DynDNS.dK> X-Operating-System: FreeBSD cicely12.cicely.de 5.1-CURRENT alpha User-Agent: Mutt/1.5.4i cc: FreeBSD Hacking Group Subject: Re: USB card overcurrent problems... X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: ticso@cicely.de List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Sep 2003 19:19:36 -0000 On Wed, Sep 24, 2003 at 06:32:42PM +0200, Barry Bouwsma wrote: > [Drop hostname part of IPv6-only address above to obtain IPv4-capable e-mail, > or just drop me from the recipients and I'll catch up from the archives] > > > Hello every last one of you, > > First, before I spout off in the wrong forum, is there a better or preferred > location for USB-hardware-related questions like that which follows, akin to > the firewire list? > > > Okay, the question: I have two cards with USB2.0 awareness, used for their > USB 1.x capability under FreeBSD 4.x. One of them, a UHCI card, works just > fine, but the other one, an OHCI card, out-of-the-box exhibits problems. > Chipset is identified in dmesg as NEC uPD 9210 USB controller. Current protection and limiting is completely up to the card designer. The best that FreeBSD can do is getting informed if the card design allows it, but I almost never saw a card doing this. Many cards just have some kind of self healing or melting fuses, some very bad designed cards don't even have this. Either your hubs really use more power then it is allowed to or you have a broken controller card. -- B.Walter BWCT http://www.bwct.de ticso@bwct.de info@bwct.de From owner-freebsd-hackers@FreeBSD.ORG Wed Sep 24 12:26:17 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A56A816A4B3 for ; Wed, 24 Sep 2003 12:26:17 -0700 (PDT) Received: from wattres.Watt.COM (wattres.watt.com [66.93.133.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id 19D6543FAF for ; Wed, 24 Sep 2003 12:26:15 -0700 (PDT) (envelope-from steve@Watt.COM) Received: (from steve@localhost) by wattres.Watt.COM (8.12.9/8.12.9) id h8OJQEl0029131 for hackers@freebsd.org; Wed, 24 Sep 2003 12:26:14 -0700 (PDT) (envelope-from steve) Message-Id: <200309241926.h8OJQEl0029131@wattres.Watt.COM> From: steve@Watt.COM (Steve Watt) Date: Wed, 24 Sep 2003 12:26:14 -0700 X-Mailer: Mail User's Shell (7.2.6 beta(5) jp(8) 11/23/00) To: hackers@freebsd.org Subject: PCI bridges & interrupts X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Sep 2003 19:26:17 -0000 [ Too advanced for -questions? Trying again. ] I'm having a strange problem with interrupts, PCI bridges, and FreeBSD 4-STABLE (cvsupped from a few months ago). The motherboard is a Supermicro X5DL8-GG, dual-Xeon capable (only one is populated). The BIOS is AMIBIOS 7.00.00. The BIOS settings have PnP OS set to NO, ACPI OS is YES ('cause FreeBSD-CURRENT was once installed), and power management is all disabled. The company I'm working for has a rather complex PCI board that is much larger than a normal card, and has its own power. The board can be plugged directly into a slot in the motherboard, but for physical and electrical (PCI 66) reasons wants to be attached via a bridge riser card that we have also developed. Everything on the board works when directly connected to the host, except that we can't go 66MHz and we can't close the case. With the riser card, *almost* everything works, except for interrupts. I can see the interrupt line low *on the card edge connector on the motherboard*, but it's not acknowledged, and our driver's ISR doesn't run. We've throttled the riser card to 33MHz to eliminate that possibility. What follows is the verbose dmesg from the boot up without the riser (bridge), followed by diffs when booted with the riser. I'm looking for clues. It's about >< that far from working right, and this almost looks like a FreeBSD issue. Buddy, can you spare a clue? Why isn't the ISR running? - - - 8< - - - dmesg.without-bridge 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 4.8-STABLE #35: Fri Aug 22 16:16:01 PDT 2003 root@stevedev.asicdesigners.com:/usr/src/sys/compile/CATP Calibrating clock(s) ... TSC clock: 2399054672 Hz, i8254 clock: 1193051 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz CLK_USE_TSC_CALIBRATION not specified - using old calibration method CPU: Intel(R) Xeon(TM) CPU 2.40GHz (2399.33-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf27 Stepping = 7 Features=0xbfebfbff real memory = 1073676288 (1048512K bytes) Physical memory chunk(s): 0x00001000 - 0x0009efff, 647168 bytes (158 pages) 0x005ac000 - 0x3ffe7fff, 1067696128 bytes (260668 pages) avail memory = 1038774272 (1014428K bytes) bios32: Found BIOS32 Service Directory header at 0xc00fdb20 bios32: Entry = 0xfdb30 (c00fdb30) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xdb51 pnpbios: Found PnP BIOS data at 0xc00f4280 pnpbios: Entry = f0000:32c4 Rev = 1.0 Other BIOS signatures found: ACPI: 000ff900 Preloaded elf kernel "kernel" at 0xc0585000. Pentium Pro MTRR support enabled Creating DISK md0 md0: Malloc disk Math emulator present pci_open(1): mode 1 addr port (0x0cf8) is 0x80041900 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=80] is there (id=00141166) Using $PIR table, 11 entries at 0xc00f4880 pcib-: pcib0 exists, using next available unit number pcib-: pcib0 exists, using next available unit number pcib-: pcib0 exists, using next available unit number pcib-: pcib1 exists, using next available unit number pcib-: pcib2 exists, using next available unit number pcib-: pcib3 exists, using next available unit number pcib-: pcib4 exists, using next available unit number npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard found-> vendor=0x1166, dev=0x0014, revid=0x31 class=06-00-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 found-> vendor=0x1166, dev=0x0014, revid=0x00 class=06-00-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 found-> vendor=0x1166, dev=0x0014, revid=0x00 class=06-00-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 found-> vendor=0x1002, dev=0x4752, revid=0x27 class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=0 map[10]: type 1, range 32, base fd000000, size 24 map[14]: type 1, range 32, base 00008800, size 8 map[18]: type 1, range 32, base fe5ff000, size 12 found-> vendor=0x8086, dev=0x100e, revid=0x02 class=02-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=9 map[10]: type 1, range 32, base fe5a0000, size 17 map[18]: type 1, range 32, base 00008400, size 6 found-> vendor=0x1166, dev=0x0201, revid=0x93 class=06-01-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 found-> vendor=0x1166, dev=0x0212, revid=0x93 class=01-01-8a, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 map[10]: type 1, range 32, base 000001f0, size 3 map[14]: type 1, range 32, base 000003f4, size 2 map[18]: type 1, range 32, base 00000170, size 3 map[1c]: type 1, range 32, base 00000374, size 2 map[20]: type 1, range 32, base 0000ffa0, size 4 found-> vendor=0x1166, dev=0x0220, revid=0x05 class=0c-03-10, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 intpin=a, irq=10 map[10]: type 1, range 32, base fe5fe000, size 12 found-> vendor=0x1166, dev=0x0225, revid=0x00 class=06-00-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 found-> vendor=0x1166, dev=0x0101, revid=0x03 class=06-00-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 found-> vendor=0x1166, dev=0x0101, revid=0x03 class=06-00-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 found-> vendor=0x1166, dev=0x0101, revid=0x03 class=06-00-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 found-> vendor=0x1166, dev=0x0101, revid=0x03 class=06-00-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 pci0: on pcib0 pci0: (vendor=0x1002, dev=0x4752) at 2.0 irq 0 em0: port 0x8400-0x843f mem 0xfe5a0000-0xfe5bffff irq 9 at device 4.0 on pci0 bpf: em0 attached em0: Speed:100 Mbps Duplex:Full isab0: at device 15.0 on pci0 isa0: on isab0 atapci0: port 0xffa0-0xffaf,0x374-0x377,0x170-0x177,0x3f4-0x3f7,0x1f0-0x1f7 at device 15.1 on pci0 ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0xffa0 ata0: mask=03 ostat0=50 ostat2=00 ata0-master: ATAPI 00 00 ata0-slave: ATAPI 00 00 ata0: mask=03 stat0=50 stat1=00 ata0-master: ATA 01 a5 ata0: devices=01 ata0: at 0x1f0 irq 14 on atapci0 ata1: iobase=0x0170 altiobase=0x0376 bmaddr=0xffa8 ata1: mask=01 ostat0=50 ostat2=ff ata1-master: ATAPI 14 eb ata1: mask=01 stat0=00 stat1=00 ata1: devices=04 ata1: at 0x170 irq 15 on atapci0 ohci0: mem 0xfe5fe000-0xfe5fefff irq 10 at device 15.2 on pci0 ohci0: (New OHCI DeviceId=0x02201166) usb0: OHCI version 1.0, legacy support usb0: SMM does not respond, resetting usb0: on ohci0 usb0: USB revision 1.0 uhub0: (0x1166) OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 4 ports with 4 removable, self powered pcib1: on motherboard found-> vendor=0x14e4, dev=0x16a7, revid=0x02 class=02-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=5 map[10]: type 1, range 64, base fe6f0000, size 16 pci1: on pcib1 bge0: mem 0xfe6f0000-0xfe6fffff irq 5 at device 3.0 on pci1 bge0: Ethernet address: 00:30:48:52:4b:95 miibus0: on bge0 brgphy0: on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bpf: bge0 attached pcib2: on motherboard pci2: on pcib2 pcib3: on motherboard found-> vendor=0x1425, dev=0x0005, revid=0x00 class=02-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=11 map[10]: type 1, range 64, base fe8ff000, size 12 pci3: on pcib3 PE PROBE: Found a { company board } device_id(5) device_subid(0) pe0 mem 0xfe8ff000-0xfe8fffff irq 11 at device 2.0 on pci3 {company}(0): All subsystems successfully initialized. bpf: pe0 attached cat_ifnet_register: port 0, 1 interfaces {company}(0): Registered ifp(0xc51a3800) pcib4: on motherboard found-> vendor=0x9005, dev=0x801f, revid=0x03 class=01-00-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 intpin=a, irq=11 map[10]: type 1, range 32, base 0000e000, size 8 map[14]: type 1, range 64, base febfc000, size 13 map[1c]: type 1, range 32, base 0000d800, size 8 found-> vendor=0x9005, dev=0x801f, revid=0x03 class=01-00-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 intpin=b, irq=11 map[10]: type 1, range 32, base 0000e800, size 8 map[14]: type 1, range 64, base febfe000, size 13 map[1c]: type 1, range 32, base 0000e400, size 8 pci4: on pcib4 ahd0: port 0xd800-0xd8ff,0xe000-0xe0ff mem 0xfebfc000-0xfebfdfff irq 11 at device 3.0 on pci4 ahd0: Defaulting to MEMIO on ahd0: Reading VPD from SEEPROM...ahd0: VPD parsing successful ahd0: Reading SEEPROM...done. ahd0: STPWLEVEL is on ahd0: Manual Primary Termination ahd0: Manual Secondary Termination ahd0: Primary High byte termination Enabled ahd0: Primary Low byte termination Enabled ahd0: Secondary High byte termination Disabled ahd0: Secondary Low byte termination Disabled ahd0: Downloading Sequencer Program... 710 instructions downloaded ahd0: Features 0x101, Bugs 0x8fffff, Flags 0x43f1 using shared irq11. aic7902: Ultra320 Wide Channel A, SCSI Id=7, PCI-X 67-100Mhz, 512 SCBs ahd1: port 0xe400-0xe4ff,0xe800-0xe8ff mem 0xfebfe000-0xfebfffff irq 11 at device 3.1 on pci4 ahd1: Defaulting to MEMIO on ahd1: Reading VPD from SEEPROM...ahd1: VPD parsing successful ahd1: Reading SEEPROM...done. ahd1: STPWLEVEL is on ahd1: Manual Primary Termination ahd1: Manual Secondary Termination ahd1: Primary High byte termination Enabled ahd1: Primary Low byte termination Enabled ahd1: Secondary High byte termination Disabled ahd1: Secondary Low byte termination Disabled ahd1: Downloading Sequencer Program... 710 instructions downloaded ahd1: Features 0x101, Bugs 0x8fffff, Flags 0x43f0 aic7902: Ultra320 Wide Channel B, SCSI Id=7, PCI-X 67-100Mhz, 512 SCBs pcib5: on motherboard pci5: on pcib5 pcib6: on motherboard pci6: on pcib6 pcib7: on motherboard pci7: on pcib7 ex_isa_identify() ata-: ata0 exists, using next available unit number ata-: ata1 exists, using next available unit number Trying Read_Port at 203 Trying Read_Port at 243 Trying Read_Port at 283 Trying Read_Port at 2c3 Trying Read_Port at 303 Trying Read_Port at 343 Trying Read_Port at 383 Trying Read_Port at 3c3 isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices orm0: