From owner-freebsd-drivers@FreeBSD.ORG Mon Nov 13 20:49:04 2006 Return-Path: X-Original-To: freebsd-drivers@freebsd.org Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6E84016A417 for ; Mon, 13 Nov 2006 20:49:04 +0000 (UTC) (envelope-from wes@uia.net) Received: from smtp3.uia.net (smtp3.uia.net [66.146.0.43]) by mx1.FreeBSD.org (Postfix) with ESMTP id A4FEA43D7B for ; Mon, 13 Nov 2006 20:48:13 +0000 (GMT) (envelope-from wes@uia.net) Received: from [10.50.0.123] (fw1.uia.net [66.146.1.4]) by smtp3.uia.net (8.13.6/8.11.6/2.1) with ESMTP id kADKm09U085729 for ; Mon, 13 Nov 2006 12:48:04 -0800 (PST) Mime-Version: 1.0 (Apple Message framework v752.2) Content-Transfer-Encoding: 7bit Message-Id: Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: freebsd-drivers@freebsd.org From: Wes Zuber Date: Mon, 13 Nov 2006 12:47:58 -0800 X-Mailer: Apple Mail (2.752.2) Subject: Re: Dell SC440 and Broadcom 5787 X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Nov 2006 20:49:04 -0000 Folks, is there someway that I could help this along? It is still broken and we have many of these Dells here and arriving shortly. Could someone recommend a consultant or driver coder? Perhaps someone is already working on it.. but I don't see anything on the list thus far. Happy to donate hardware or $$ as needed. Thanks, --Wes From owner-freebsd-drivers@FreeBSD.ORG Tue Nov 14 09:26:01 2006 Return-Path: X-Original-To: freebsd-drivers@freebsd.org Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A4DF916A416 for ; Tue, 14 Nov 2006 09:26:01 +0000 (UTC) (envelope-from bounces@nabble.com) Received: from talk.nabble.com (www.nabble.com [72.21.53.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id D417D43D7B for ; Tue, 14 Nov 2006 09:26:00 +0000 (GMT) (envelope-from bounces@nabble.com) Received: from [72.21.53.38] (helo=jubjub.nabble.com) by talk.nabble.com with esmtp (Exim 4.50) id 1GjuYJ-0002aq-SW for freebsd-drivers@freebsd.org; Tue, 14 Nov 2006 01:25:59 -0800 Message-ID: <7334054.post@talk.nabble.com> Date: Tue, 14 Nov 2006 01:25:59 -0800 (PST) From: deepuuuu To: freebsd-drivers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: nallimallip@yahoo.com Subject: Need help , system crashes when doing ping flood X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Nov 2006 09:26:01 -0000 Hi, When i m doing ping flood , i m getting crash after 15 mins. The debug messages are like this: NU gdb 5.18 (FreeBSD) Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-unknown-freebsd"... IdlePTD at physical address 0x00579000 initial pcb at physical address 0x004a58a0 panicstr: page fault panic messages: --- Fatal trap 12: page fault while in kernel mode fault virtual address = 0x50a10800 fault code = supervisor read, page not present instruction pointer = 0x8:0xc1b177a9 stack pointer = 0x10:0xcd6ccc64 frame pointer = 0x10:0xcd6ccccc code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 1088 (ping) interrupt mask = net tty trap number = 12 panic: page fault syncing disks... done Uptime: 10m15s dumping to dev #ad/0x20011, offset 1558871 #0 0xc023d9da in dumpsys () (kgdb) where #0 0xc023d9da in dumpsys () #1 0xc023d7ab in boot () #2 0xc023dbd0 in poweroff_wait () #3 0xc03addfa in trap_fatal () #4 0xc03adacd in trap_pfault () #5 0xc03ad68b in trap () #6 0xc1b177a9 in ?? () #7 0xc0283006 in ether_output_frame (ifp=0xc1b1a840, m=0xc0c03900) at ../../net/if_var.h:290 #8 0xc0282d36 in ether_output (ifp=0xc1b1a840, m=0xc0c03900, dst=0xcd07ff00, rt0=0xc1b1ee00) at ../../net/if_ethersubr.c:370 #9 0xc029769d in ip_output (m0=0xc0c03900, opt=0x0, ro=0xcd07fefc, flags=32, imo=0x0, inp=0xcd07fec0) at ../../netinet/ip_output.c:1004 #10 0xc0298f3a in rip_output (m=0xc0c03900, so=0xcca53340, dst=34212362) at ../../netinet/raw_ip.c:299 #11 0xc02993e3 in rip_send (so=0xcca53340, flags=0, m=0xc0c03900, nam=0xc134a770, control=0x0, p=0xcc04b220) at ../../netinet/raw_ip.c:630 #12 0xc025cc6b in sosend () #13 0xc026022f in sendit () #14 0xc0260332 in sendto () #15 0xc03ae0a9 in syscall2 () #16 0xc039f0c5 in Xint0x80_syscall () #17 0x80492e1 in ?? () I feel my start() function is having problem. Could anyone tell me the reason behind this?? Thanks, pradeep -- View this message in context: http://www.nabble.com/Need-help-%2C-system-crashes-when-doing-ping-flood-tf2628209.html#a7334054 Sent from the freebsd-drivers mailing list archive at Nabble.com. From owner-freebsd-drivers@FreeBSD.ORG Tue Nov 14 14:28:33 2006 Return-Path: X-Original-To: freebsd-drivers@freebsd.org Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A49ED16A403 for ; Tue, 14 Nov 2006 14:28:33 +0000 (UTC) (envelope-from wes@uia.net) Received: from smtp3.uia.net (smtp3.uia.net [66.146.0.43]) by mx1.FreeBSD.org (Postfix) with ESMTP id 584FF43D6B for ; Tue, 14 Nov 2006 14:28:33 +0000 (GMT) (envelope-from wes@uia.net) Received: from [172.16.2.254] (243.1.ultimate-int.uia.net [66.146.1.243]) by smtp3.uia.net (8.13.6/8.11.6/2.1) with ESMTP id kAEESSBQ041107 for ; Tue, 14 Nov 2006 06:28:33 -0800 (PST) Mime-Version: 1.0 (Apple Message framework v752.2) Content-Transfer-Encoding: 7bit Message-Id: <5DBD9D59-765D-46CA-8D0F-22A62A91C0F2@uia.net> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: freebsd-drivers@freebsd.org From: "Wes L. Zuber" Date: Tue, 14 Nov 2006 06:28:24 -0800 X-Mailer: Apple Mail (2.752.2) Subject: Re: Dell SC440 and Broadcom 5787 X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Nov 2006 14:28:33 -0000 When I look at the chip itself it says it is a 5754.. but it probes as a 5787. Could that be an issue? thanks, --Wes From owner-freebsd-drivers@FreeBSD.ORG Thu Nov 16 16:25:27 2006 Return-Path: X-Original-To: freebsd-drivers@freebsd.org Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A7B0E16A403 for ; Thu, 16 Nov 2006 16:25:27 +0000 (UTC) (envelope-from jackie7691@yahoo.com.mx) Received: from web56013.mail.re3.yahoo.com (web56013.mail.re3.yahoo.com [216.252.110.192]) by mx1.FreeBSD.org (Postfix) with SMTP id 214C043D99 for ; Thu, 16 Nov 2006 16:24:34 +0000 (GMT) (envelope-from jackie7691@yahoo.com.mx) Received: (qmail 63610 invoked by uid 60001); 16 Nov 2006 16:24:34 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com.mx; h=X-YMail-OSG:Received:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=RqBjVq9OKkN7sN3+81GYDbVL7lvxX/xZhqHPydrpD/F+qgA6Q+O/wmzneN6LPVsk5Rlx59ouitMjSn4mKo6VHf9GtnBSZGxw5b1wRFWu8iy9tg+2x9jRXHUd4NVKQWiO5nat7W7B6mtE2M82rCQfh1tRTyrC2y5A80m4jZcy53U=; X-YMail-OSG: YIMPeb4VM1li2Sn6AdNLiRDeosXLlxWXyjtcyHXWE9UXQ_iYXdpBat.F8bO6.8EpnkKQPtsv9wpnSyTZ.wjq36kkRfbk2RXV8dUjIChkP_ZHDPK_vhHTfLO3lTwoJxgxtsEpF43n7eGQ0fM- Received: from [83.64.77.210] by web56013.mail.re3.yahoo.com via HTTP; Thu, 16 Nov 2006 10:24:34 CST Date: Thu, 16 Nov 2006 10:24:34 -0600 (CST) From: Jacqueline P To: Attilio Rao , Warner Losh In-Reply-To: <3bbf2fe10611081130i1e34ab2end66bf238117cfcf8@mail.gmail.com> MIME-Version: 1.0 Message-ID: <331679.63275.qm@web56013.mail.re3.yahoo.com> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-drivers@freebsd.org, jackie7691@yahoo.com.mx Subject: Re: PCCARD - interruptible sleep X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Nov 2006 16:25:27 -0000 Hi so what can I do to get my driver running ? Actually I have no idea. Jacqueline Attilio Rao escribió: 2006/11/8, Warner Losh : > From: "Attilio Rao" > Subject: Re: PCCARD - interruptible sleep > Date: Wed, 8 Nov 2006 14:43:59 +0100 > > > 2006/11/8, Jacqueline P : > > > Hi all > > > > > > how can I implement an interruptible sleep within my pccard smart card reader driver like ? > > > For Linux I do this the following way > > > > > > // interruptible_pause() > > > static inline void ipause(unsigned long amount) { > > > set_current_state(TASK_INTERRUPTIBLE); > > > schedule_timeout(amount); > > > } > > > > > > and within my driver I use the function DELAY which does a busy wait. > > > > > > The problem is, that the driver does not recognize when the pccard is detached during a read / write operation. > > > > > > Does the kernel update the struct device_t, so that the driver can use the function device_is_attached() to determine that the device is detached ? > > > > You can implement a 'dying' flag in your softc structure (and > > subsequent macro in order to handle). > > But that won't tell you if the hardware has disappeared. Experience > has shown that dying isn't such a good idea in many cases and tends to > cause more races than it solves. Nothing that can't be solved with a softc lock? Give an example please. Attilio -- Peace can only be achieved by understanding - A. Einstein _______________________________________________ freebsd-drivers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-drivers To unsubscribe, send any mail to "freebsd-drivers-unsubscribe@freebsd.org" --------------------------------- Do You Yahoo!? La mejor conexión a Internet y 2GB extra a tu correo por $100 al mes. http://net.yahoo.com.mx From owner-freebsd-drivers@FreeBSD.ORG Thu Nov 16 17:34:36 2006 Return-Path: X-Original-To: freebsd-drivers@freebsd.org Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 581C716A403 for ; Thu, 16 Nov 2006 17:34:36 +0000 (UTC) (envelope-from wes@uia.net) Received: from smtp2.uia.net (smtp2.uia.net [66.146.0.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id C4B6843D5D for ; Thu, 16 Nov 2006 17:34:35 +0000 (GMT) (envelope-from wes@uia.net) Received: from [10.50.0.123] (fw1.uia.net [66.146.1.4]) by smtp2.uia.net (8.13.6/8.11.6/2.1) with ESMTP id kAGHYH9Q072570 for ; Thu, 16 Nov 2006 09:34:21 -0800 (PST) Mime-Version: 1.0 (Apple Message framework v752.2) Content-Transfer-Encoding: 7bit Message-Id: <41E18955-A5F8-49BB-801B-874C6EAAB00E@uia.net> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: freebsd-drivers@freebsd.org From: Wes Zuber Date: Thu, 16 Nov 2006 09:34:16 -0800 X-Mailer: Apple Mail (2.752.2) Subject: Re: Dell SC440 and Broadcom 5787 consulting? X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Nov 2006 17:34:36 -0000 Hi there folks, Can someone recommend a coder to fix this? We are happy to contribute to this fix but hiring a programmer to get this going. Thanks, --Wes From owner-freebsd-drivers@FreeBSD.ORG Thu Nov 16 20:02:33 2006 Return-Path: X-Original-To: freebsd-drivers@freebsd.org Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 378BC16A40F; Thu, 16 Nov 2006 20:02:33 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 624E843D9F; Thu, 16 Nov 2006 20:02:31 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.13.4/8.13.4) with ESMTP id kAGK11hF016256; Thu, 16 Nov 2006 13:01:02 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Thu, 16 Nov 2006 13:01:41 -0700 (MST) Message-Id: <20061116.130141.228973534.imp@bsdimp.com> To: jackie7691@yahoo.com.mx From: "M. Warner Losh" In-Reply-To: <331679.63275.qm@web56013.mail.re3.yahoo.com> References: <3bbf2fe10611081130i1e34ab2end66bf238117cfcf8@mail.gmail.com> <331679.63275.qm@web56013.mail.re3.yahoo.com> X-Mailer: Mew version 4.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Thu, 16 Nov 2006 13:01:02 -0700 (MST) Cc: attilio@freebsd.org, freebsd-drivers@freebsd.org Subject: Re: PCCARD - interruptible sleep X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Nov 2006 20:02:33 -0000 In message: <331679.63275.qm@web56013.mail.re3.yahoo.com> Jacqueline P writes: : so what can I do to get my driver running ? : Actually I have no idea. Make sure that your ISR doesn't loop. You can do this by calling bus_child_present() if you think you'd want to loop. Warner : Attilio Rao escribi=F3: : 2006/11/8, Warner Losh : : > From: "Attilio Rao" = : > Subject: Re: PCCARD - interruptible sleep : > Date: Wed, 8 Nov 2006 14:43:59 +0100 : > : > > 2006/11/8, Jacqueline P : : > > > Hi all : > > > : > > > how can I implement an interruptible sleep within my pccard sma= rt card reader driver like ? : > > > For Linux I do this the following way : > > > : > > > // interruptible_pause() : > > > static inline void ipause(unsigned long amount) { : > > > set_current_state(TASK_INTERRUPTIBLE); : > > > schedule_timeout(amount); : > > > } : > > > : > > > and within my driver I use the function DELAY which does a busy= wait. : > > > : > > > The problem is, that the driver does not recognize when the pcc= ard is detached during a read / write operation. : > > > : > > > Does the kernel update the struct device_t, so that the driver = can use the function device_is_attached() to determine that the device = is detached ? : > > : > > You can implement a 'dying' flag in your softc structure (and : > > subsequent macro in order to handle). : > : > But that won't tell you if the hardware has disappeared. Experience= : > has shown that dying isn't such a good idea in many cases and tends= to : > cause more races than it solves. : = : Nothing that can't be solved with a softc lock? : Give an example please. : = : Attilio : = : = : -- = : Peace can only be achieved by understanding - A. Einstein : _______________________________________________ : freebsd-drivers@freebsd.org mailing list : http://lists.freebsd.org/mailman/listinfo/freebsd-drivers : To unsubscribe, send any mail to "freebsd-drivers-unsubscribe@freebsd= .org" : = : = : = : --------------------------------- : Do You Yahoo!? La mejor conexi=F3n a Internet y 2GB extra a tu corr= eo por $100 al mes. http://net.yahoo.com.mx = From owner-freebsd-drivers@FreeBSD.ORG Fri Nov 17 18:52:04 2006 Return-Path: X-Original-To: freebsd-drivers@freebsd.org Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 13AAE16A407 for ; Fri, 17 Nov 2006 18:52:04 +0000 (UTC) (envelope-from wyt168@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.172]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7482243D45 for ; Fri, 17 Nov 2006 18:52:03 +0000 (GMT) (envelope-from wyt168@gmail.com) Received: by ug-out-1314.google.com with SMTP id o2so703624uge for ; Fri, 17 Nov 2006 10:52:02 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=npXCxcbO4IPyevBVvBqU6+Jz3vIM99x2bvau/hGFpO7Gs+9bPaA2HlOFH2YUUJI8qZ/eKXcPEpoGKhIivSvVqZXiDL0gxFkP8hEAVkOTCwxO1HBMur6Jb8VMKp+dl0jd2D5bhkHvozS8ejDd2vRNlcJE9C1EDGVbAldXgk3Uelc= Received: by 10.66.216.20 with SMTP id o20mr1537475ugg.1163789522070; Fri, 17 Nov 2006 10:52:02 -0800 (PST) Received: by 10.67.87.1 with HTTP; Fri, 17 Nov 2006 10:52:01 -0800 (PST) Message-ID: <3dcda0520611171052ne15e503k7ded10a2e5c48ff9@mail.gmail.com> Date: Fri, 17 Nov 2006 10:52:01 -0800 From: Winston To: freebsd-drivers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: How to break into kernel debugger X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Nov 2006 18:52:04 -0000 I've set up kgdb for remote debugging over serial lines (null modem) between two machines. I can get into the debugger when I boot the target machine with "boot -d" and from the debugging machine with the command "target remote /dev/cuad1". However, once I let the debugger go with "continue" command, I can't break into the debugger anymore. If I hit ctl-c once on the debugging machine, there is no response. Hit it again, I got: ^C Interrupted while waiting for the program. Give up (and stop debugging it)? (y or n) n The gdb doc mentioned this and stated: "Whenever gdb is waiting for the remote program, if you type the interrupt character (often Ctrl-c), gdb attempts to stop the program. This may or may not succeed, depending in part on the hardware and the serial drivers the remote system uses." However, it doesn't offer a suggestion as to how to make it work. I tried to set remotebreak to on with: set remotebreak on; But it still doesn't work. Any suggestions?