From owner-freebsd-new-bus Mon Jun 26 20:21:24 2000 Delivered-To: freebsd-new-bus@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 53E2D37B526 for ; Mon, 26 Jun 2000 20:21:21 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id VAA71687 for ; Mon, 26 Jun 2000 21:21:17 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id VAA30126 for ; Mon, 26 Jun 2000 21:19:27 -0600 (MDT) Message-Id: <200006270319.VAA30126@harmony.village.org> To: new-bus@freebsd.org Subject: Why can't I have.. Date: Mon, 26 Jun 2000 21:19:27 -0600 From: Warner Losh Sender: owner-freebsd-new-bus@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ... a INTR_TYPE_FAST | INTR_TYPE_MISC? It gives me: panic("still using grody create_intr interface"); What's the deal? It is easy enough to fix the problem, but I was wondering why the code is still there... This is, admittedly, in -stable. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-new-bus" in the body of the message From owner-freebsd-new-bus Mon Jun 26 20:24: 6 2000 Delivered-To: freebsd-new-bus@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 2187937B6FA for ; Mon, 26 Jun 2000 20:24:04 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id VAA71695 for ; Mon, 26 Jun 2000 21:24:02 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id VAA30153 for ; Mon, 26 Jun 2000 21:22:12 -0600 (MDT) Message-Id: <200006270322.VAA30153@harmony.village.org> To: new-bus@freebsd.org Subject: Debugger vs panic Date: Mon, 26 Jun 2000 21:22:12 -0600 From: Warner Losh Sender: owner-freebsd-new-bus@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG There's lots of places in newbus that programming errors trigger a panic. This can make it very difficult to debug the probe/attach routines. Is there any way that this can just dump you into the debugger and then return out failing the call? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-new-bus" in the body of the message From owner-freebsd-new-bus Mon Jun 26 23:12:17 2000 Delivered-To: freebsd-new-bus@freebsd.org Received: from anchor-post-33.mail.demon.net (anchor-post-33.mail.demon.net [194.217.242.91]) by hub.freebsd.org (Postfix) with ESMTP id 015B737B6D8 for ; Mon, 26 Jun 2000 23:12:14 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from nlsys.demon.co.uk ([158.152.125.33] helo=herring.nlsystems.com) by anchor-post-33.mail.demon.net with esmtp (Exim 2.12 #1) id 136obU-0008P4-0X; Tue, 27 Jun 2000 07:12:12 +0100 Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id HAA09068; Tue, 27 Jun 2000 07:12:35 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Tue, 27 Jun 2000 07:16:24 +0100 (BST) From: Doug Rabson To: Warner Losh Cc: new-bus@freebsd.org Subject: Re: Why can't I have.. In-Reply-To: <200006270319.VAA30126@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-new-bus@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 26 Jun 2000, Warner Losh wrote: > > ... a INTR_TYPE_FAST | INTR_TYPE_MISC? > > It gives me: > panic("still using grody create_intr interface"); > > What's the deal? It is easy enough to fix the problem, but I was > wondering why the code is still there... > > This is, admittedly, in -stable. Hmm. I thought Peter had fixed that ages ago. If you can generate patches, I would appreciate it. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 20 8442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-new-bus" in the body of the message From owner-freebsd-new-bus Mon Jun 26 23:21:32 2000 Delivered-To: freebsd-new-bus@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id A7ADF37BE15 for ; Mon, 26 Jun 2000 23:21:29 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id AAA72423; Tue, 27 Jun 2000 00:21:28 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id AAA31901; Tue, 27 Jun 2000 00:19:37 -0600 (MDT) Message-Id: <200006270619.AAA31901@harmony.village.org> To: Doug Rabson Subject: Re: Why can't I have.. Cc: new-bus@freebsd.org In-reply-to: Your message of "Tue, 27 Jun 2000 07:16:24 BST." References: Date: Tue, 27 Jun 2000 00:19:37 -0600 From: Warner Losh Sender: owner-freebsd-new-bus@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Doug Rabson writes: : On Mon, 26 Jun 2000, Warner Losh wrote: : : > : > ... a INTR_TYPE_FAST | INTR_TYPE_MISC? : > : > It gives me: : > panic("still using grody create_intr interface"); : > : > What's the deal? It is easy enough to fix the problem, but I was : > wondering why the code is still there... : > : > This is, admittedly, in -stable. : : Hmm. I thought Peter had fixed that ages ago. If you can generate patches, : I would appreciate it. Here's what I have. Tell me how it is wrong and I'll fix it :-). Fast interrupts make a *HUGE* difference for some hardware that I'm writing a driver for hire fore. This hardware generates an interrupt on the first write to a FIFO. In the ISR the you set the DMA parameters of the card, and you have only until the FIFO fills up to set the DMA. Once the DMA is set, the fifo drains (as well as data that is fed through it) and your hunk of data is complete. The normal interrupts had too much of a latency to make them work. Minor rework of the driver for fast interrupts seems to have solved the latency problem at the cost that each of these cards must have their own interrupt. Major rework of the driver could make it possible for interrupt sharing with other cards of this type with one ISR handling all of them. Anyway, enough about my oddball hardware. Here's the patch. Warner Index: nexus.c =================================================================== RCS file: /home/imp/FreeBSD/CVS/src/sys/i386/i386/nexus.c,v retrieving revision 1.26.2.2 diff -u -r1.26.2.2 nexus.c --- nexus.c 2000/04/23 09:59:11 1.26.2.2 +++ nexus.c 2000/06/27 03:15:03 @@ -437,6 +437,9 @@ case INTR_TYPE_CAM: mask = &cam_imask; break; + case INTR_TYPE_MISC | INTR_TYPE_FAST: + icflags |= INTR_FAST; + /* FALLTHROUGH */ case INTR_TYPE_MISC: mask = 0; break; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-new-bus" in the body of the message From owner-freebsd-new-bus Tue Jun 27 0:14:47 2000 Delivered-To: freebsd-new-bus@freebsd.org Received: from tele-post-20.mail.demon.net (tele-post-20.mail.demon.net [194.217.242.20]) by hub.freebsd.org (Postfix) with ESMTP id BB8A137B604 for ; Tue, 27 Jun 2000 00:14:43 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from nlsys.demon.co.uk ([158.152.125.33] helo=herring.nlsystems.com) by tele-post-20.mail.demon.net with esmtp (Exim 2.12 #2) id 136pZx-0003sy-0K; Tue, 27 Jun 2000 07:14:42 +0000 Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id IAA09246; Tue, 27 Jun 2000 08:14:35 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Tue, 27 Jun 2000 08:18:23 +0100 (BST) From: Doug Rabson To: Warner Losh Cc: new-bus@freebsd.org Subject: Re: Why can't I have.. In-Reply-To: <200006270619.AAA31901@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-new-bus@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 27 Jun 2000, Warner Losh wrote: > In message Doug Rabson writes: > : On Mon, 26 Jun 2000, Warner Losh wrote: > : > : > > : > ... a INTR_TYPE_FAST | INTR_TYPE_MISC? > : > > : > It gives me: > : > panic("still using grody create_intr interface"); > : > > : > What's the deal? It is easy enough to fix the problem, but I was > : > wondering why the code is still there... > : > > : > This is, admittedly, in -stable. > : > : Hmm. I thought Peter had fixed that ages ago. If you can generate patches, > : I would appreciate it. > > Here's what I have. Tell me how it is wrong and I'll fix it :-). > > Fast interrupts make a *HUGE* difference for some hardware that I'm > writing a driver for hire fore. This hardware generates an interrupt > on the first write to a FIFO. In the ISR the you set the DMA > parameters of the card, and you have only until the FIFO fills up to > set the DMA. Once the DMA is set, the fifo drains (as well as data > that is fed through it) and your hunk of data is complete. The normal > interrupts had too much of a latency to make them work. Minor rework > of the driver for fast interrupts seems to have solved the latency > problem at the cost that each of these cards must have their own > interrupt. Major rework of the driver could make it possible for > interrupt sharing with other cards of this type with one ISR handling > all of them. > > Anyway, enough about my oddball hardware. Here's the patch. This looks correct for your purposes but I think we should be able to specify more than one interrupt type in the mask (e.g CAM|NET). Its not worth fixing that though since spls will be disappearing soon. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 20 8442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-new-bus" in the body of the message From owner-freebsd-new-bus Tue Jun 27 0:18:29 2000 Delivered-To: freebsd-new-bus@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 1CF2E37BDE0 for ; Tue, 27 Jun 2000 00:18:16 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id BAA72823; Tue, 27 Jun 2000 01:18:12 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id BAA32770; Tue, 27 Jun 2000 01:16:20 -0600 (MDT) Message-Id: <200006270716.BAA32770@harmony.village.org> To: Doug Rabson Subject: Re: Why can't I have.. Cc: new-bus@freebsd.org In-reply-to: Your message of "Tue, 27 Jun 2000 08:18:23 BST." References: Date: Tue, 27 Jun 2000 01:16:20 -0600 From: Warner Losh Sender: owner-freebsd-new-bus@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Doug Rabson writes: : This looks correct for your purposes but I think we should be able to : specify more than one interrupt type in the mask (e.g CAM|NET). Its not : worth fixing that though since spls will be disappearing soon. Agreed. That's why I hacked it the way that I did :-) A cleaner fix would be to mask out INTR_TYPE_FAST from the switch statement and use it to set the bits differently. Add an interlock to make sure that no interrupt sharing is possible maybe. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-new-bus" in the body of the message From owner-freebsd-new-bus Tue Jun 27 3:11:54 2000 Delivered-To: freebsd-new-bus@freebsd.org Received: from gidora.zeta.org.au (gidora.zeta.org.au [203.26.10.25]) by hub.freebsd.org (Postfix) with SMTP id 6D99637BEFE for ; Tue, 27 Jun 2000 03:11:42 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: (qmail 22845 invoked from network); 27 Jun 2000 10:11:35 -0000 Received: from unknown (HELO bde.zeta.org.au) (203.2.228.102) by gidora.zeta.org.au with SMTP; 27 Jun 2000 10:11:35 -0000 Date: Tue, 27 Jun 2000 20:11:32 +1000 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Doug Rabson Cc: Warner Losh , new-bus@FreeBSD.ORG Subject: Re: Why can't I have.. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-new-bus@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 27 Jun 2000, Doug Rabson wrote: > On Mon, 26 Jun 2000, Warner Losh wrote: > > > > > ... a INTR_TYPE_FAST | INTR_TYPE_MISC? > > > > It gives me: > > panic("still using grody create_intr interface"); > > > > What's the deal? It is easy enough to fix the problem, but I was > > wondering why the code is still there... > > > > This is, admittedly, in -stable. > > Hmm. I thought Peter had fixed that ages ago. If you can generate patches, > I would appreciate it. I seem to have fixed it locally ages ago. diff -c2 nexus.c~ nexus.c *** nexus.c~ Mon Jun 26 17:57:09 2000 --- nexus.c Mon Jun 26 17:57:11 2000 *************** *** 399,403 **** { intrmask_t *mask; - driver_t *driver; int error, icflags; --- 411,414 ---- *************** *** 411,423 **** else icflags = INTR_EXCL; ! ! driver = device_get_driver(child); ! switch (flags) { case INTR_TYPE_TTY: mask = &tty_imask; - break; - case (INTR_TYPE_TTY | INTR_TYPE_FAST): - mask = &tty_imask; - icflags |= INTR_FAST; break; case INTR_TYPE_BIO: --- 422,430 ---- else icflags = INTR_EXCL; ! if (flags & INTR_TYPE_FAST) ! icflags |= INTR_FAST; ! switch (flags & ~INTR_TYPE_FAST) { case INTR_TYPE_TTY: mask = &tty_imask; break; case INTR_TYPE_BIO: Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-new-bus" in the body of the message From owner-freebsd-new-bus Tue Jun 27 3:50:54 2000 Delivered-To: freebsd-new-bus@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id D195437B7E3 for ; Tue, 27 Jun 2000 03:50:49 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id UAA00083; Tue, 27 Jun 2000 20:50:33 +1000 Date: Tue, 27 Jun 2000 20:50:30 +1000 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Warner Losh Cc: new-bus@FreeBSD.ORG Subject: Re: Debugger vs panic In-Reply-To: <200006270322.VAA30153@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-new-bus@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 26 Jun 2000, Warner Losh wrote: > There's lots of places in newbus that programming errors trigger a > panic. This can make it very difficult to debug the probe/attach > routines. Is there any way that this can just dump you into the > debugger and then return out failing the call? Not in general. Code that calls panic() is generally not prepared for panic() to return. Apart from that, you can add a call to Debugger() near the start of panic(), and sometimes return from panic(). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-new-bus" in the body of the message From owner-freebsd-new-bus Tue Jun 27 4: 6: 7 2000 Delivered-To: freebsd-new-bus@freebsd.org Received: from anchor-post-34.mail.demon.net (anchor-post-34.mail.demon.net [194.217.242.92]) by hub.freebsd.org (Postfix) with ESMTP id 77B6537BF6B for ; Tue, 27 Jun 2000 04:05:55 -0700 (PDT) (envelope-from n_hibma@qubesoft.com) Received: from calcaphon.demon.co.uk ([193.237.19.5] helo=bluebottle.qubesoft.com) by anchor-post-34.mail.demon.net with esmtp (Exim 2.12 #1) id 136tBf-000Eal-0Y; Tue, 27 Jun 2000 12:05:51 +0100 Received: from henny.webweaving.org (henny.qubesoft.com [192.168.1.5]) by bluebottle.qubesoft.com (8.9.3/8.9.1) with ESMTP id MAA41881; Tue, 27 Jun 2000 12:07:33 +0100 (BST) (envelope-from n_hibma@qubesoft.com) Received: from localhost (localhost [127.0.0.1]) by henny.webweaving.org (8.9.3/8.9.3) with ESMTP id LAA13243; Tue, 27 Jun 2000 11:59:41 +0100 (BST) (envelope-from n_hibma@qubesoft.com) Date: Tue, 27 Jun 2000 11:59:41 +0100 (BST) From: Nick Hibma X-Sender: n_hibma@localhost Reply-To: Nick Hibma To: Warner Losh Cc: new-bus@FreeBSD.ORG Subject: Re: Debugger vs panic In-Reply-To: <200006270322.VAA30153@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-new-bus@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've made this exact same comment to dfr about 1.5 years ago, to replace the panics with appropriate empty returns, returning NULL or false in most cases. He was quite persistent in his opinion that it was a bug in the code and could only lead to faults later in the code. He'd rather have the problem pointed out right where it occurs. And I agree with him to the extent that if there is a problem it should go pop as early as possible in the appropriate place, and not at a later stage where you will have to trace back to the place where the value was last written, which might be complicated to say the least. However, this also means that you will have to do more checking in your code before you call any function, eventhough the error value might sufficient (for example calling device_busy before the device is attached). One of the reasons I like Perl is that it allows you to make mistakes and fix them up later in the code. Nick > There's lots of places in newbus that programming errors trigger a > panic. This can make it very difficult to debug the probe/attach > routines. Is there any way that this can just dump you into the > debugger and then return out failing the call? > > Warner > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-new-bus" in the body of the message > -- n_hibma@webweaving.org n_hibma@freebsd.org USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-new-bus" in the body of the message From owner-freebsd-new-bus Tue Jun 27 12:18:48 2000 Delivered-To: freebsd-new-bus@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 4DD9437B70B for ; Tue, 27 Jun 2000 12:18:38 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id NAA75542; Tue, 27 Jun 2000 13:18:36 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id NAA48317; Tue, 27 Jun 2000 13:16:44 -0600 (MDT) Message-Id: <200006271916.NAA48317@harmony.village.org> To: Nick Hibma Subject: Re: Debugger vs panic Cc: new-bus@FreeBSD.ORG In-reply-to: Your message of "Tue, 27 Jun 2000 11:59:41 BST." References: Date: Tue, 27 Jun 2000 13:16:44 -0600 From: Warner Losh Sender: owner-freebsd-new-bus@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Nick Hibma writes: : He was quite persistent in his opinion that it was a bug in the code and : could only lead to faults later in the code. He'd rather have the : problem pointed out right where it occurs. And I agree with him to the : extent that if there is a problem it should go pop as early as possible : in the appropriate place, and not at a later stage where you will have : to trace back to the place where the value was last written, which might : be complicated to say the least. I'd rather have a #define that I can give to have it fail out rather than panic. Why? I don't like rebuildnig my disks. When I'm debugging new drivers, I tend to make bonehead mistakes, especially in the bridge driver I'm working on. I've wasted lots and lots of time because of these panics. It would be nicer if I could #define way the panic when I want. For most people, they will want to keep the panics. For me, and other ard core developers the panics do negative good. I guess I want a "debugging expert" flag that says that I'll fix anything that causes a kernel printf and to please just print and fail exit rather than do a full panic for silly things. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-new-bus" in the body of the message From owner-freebsd-new-bus Wed Jun 28 3:30:33 2000 Delivered-To: freebsd-new-bus@freebsd.org Received: from anchor-post-30.mail.demon.net (anchor-post-30.mail.demon.net [194.217.242.88]) by hub.freebsd.org (Postfix) with ESMTP id 62A8C37BEBB for ; Wed, 28 Jun 2000 03:30:31 -0700 (PDT) (envelope-from n_hibma@qubesoft.com) Received: from calcaphon.demon.co.uk ([193.237.19.5] helo=bluebottle.qubesoft.com) by anchor-post-30.mail.demon.net with esmtp (Exim 2.12 #1) id 137F6z-0002da-0U; Wed, 28 Jun 2000 11:30:29 +0100 Received: from henny.webweaving.org (henny.qubesoft.com [192.168.1.5]) by bluebottle.qubesoft.com (8.9.3/8.9.1) with ESMTP id LAA25691; Wed, 28 Jun 2000 11:30:28 +0100 (BST) (envelope-from n_hibma@qubesoft.com) Received: from localhost (localhost [127.0.0.1]) by henny.webweaving.org (8.9.3/8.9.3) with ESMTP id LAA16396; Wed, 28 Jun 2000 11:17:24 +0100 (BST) (envelope-from n_hibma@qubesoft.com) Date: Wed, 28 Jun 2000 11:17:24 +0100 (BST) From: Nick Hibma X-Sender: n_hibma@localhost Reply-To: Nick Hibma To: Warner Losh Cc: new-bus@freebsd.org Subject: Re: Debugger vs panic In-Reply-To: <200006271916.NAA48317@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-new-bus@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I guess I want a "debugging expert" flag that says that I'll fix > anything that causes a kernel printf and to please just print and fail > exit rather than do a full panic for silly things. There is a number of places where you can't do this in any case. You can't solve all those fat-finger panics. Nick -- n_hibma@webweaving.org n_hibma@freebsd.org USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-new-bus" in the body of the message From owner-freebsd-new-bus Wed Jun 28 9:34:53 2000 Delivered-To: freebsd-new-bus@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 6754237BD5D for ; Wed, 28 Jun 2000 09:34:50 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id KAA80225; Wed, 28 Jun 2000 10:34:48 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id KAA56222; Wed, 28 Jun 2000 10:34:46 -0600 (MDT) Message-Id: <200006281634.KAA56222@harmony.village.org> To: Nick Hibma Subject: Re: Debugger vs panic Cc: new-bus@freebsd.org In-reply-to: Your message of "Wed, 28 Jun 2000 11:17:24 BST." References: Date: Wed, 28 Jun 2000 10:34:46 -0600 From: Warner Losh Sender: owner-freebsd-new-bus@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Nick Hibma writes: : > I guess I want a "debugging expert" flag that says that I'll fix : > anything that causes a kernel printf and to please just print and fail : > exit rather than do a full panic for silly things. : : There is a number of places where you can't do this in any case. You : can't solve all those fat-finger panics. Yes, but you can solve a whole lot of them. The resource already in use one is the one that kept biting me. For that, you just return a failure. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-new-bus" in the body of the message From owner-freebsd-new-bus Thu Jun 29 2:32:31 2000 Delivered-To: freebsd-new-bus@freebsd.org Received: from anchor-post-32.mail.demon.net (anchor-post-32.mail.demon.net [194.217.242.90]) by hub.freebsd.org (Postfix) with ESMTP id 8324437B52D for ; Thu, 29 Jun 2000 02:32:25 -0700 (PDT) (envelope-from n_hibma@qubesoft.com) Received: from calcaphon.demon.co.uk ([193.237.19.5] helo=bluebottle.qubesoft.com) by anchor-post-32.mail.demon.net with esmtp (Exim 2.12 #1) id 137agC-000Ks1-0W; Thu, 29 Jun 2000 10:32:16 +0100 Received: from henny.webweaving.org (henny.qubesoft.com [192.168.1.5]) by bluebottle.qubesoft.com (8.9.3/8.9.1) with ESMTP id KAA70323; Thu, 29 Jun 2000 10:32:11 +0100 (BST) (envelope-from n_hibma@qubesoft.com) Received: from localhost (localhost [127.0.0.1]) by henny.webweaving.org (8.9.3/8.9.3) with ESMTP id UAA17924; Wed, 28 Jun 2000 20:32:43 +0100 (BST) (envelope-from n_hibma@qubesoft.com) Date: Wed, 28 Jun 2000 20:32:43 +0100 (BST) From: Nick Hibma X-Sender: n_hibma@localhost Reply-To: Nick Hibma To: Warner Losh Cc: new-bus@freebsd.org Subject: Re: Debugger vs panic In-Reply-To: <200006281634.KAA56222@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-new-bus@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Feel free to come up with patches. I am sure that the silence from camp dfr means that he is open to suggestions. :) Nick > : > I guess I want a "debugging expert" flag that says that I'll fix > : > anything that causes a kernel printf and to please just print and fail > : > exit rather than do a full panic for silly things. > : > : There is a number of places where you can't do this in any case. You > : can't solve all those fat-finger panics. > > Yes, but you can solve a whole lot of them. The resource already in > use one is the one that kept biting me. For that, you just return a > failure. > > Warner > -- n_hibma@webweaving.org n_hibma@freebsd.org USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-new-bus" in the body of the message