From olli@lurza.secnetix.de  Thu Oct 13 09:35:15 2005
Return-Path: <olli@lurza.secnetix.de>
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 1ACC816A41F
	for <FreeBSD-gnats-submit@freebsd.org>; Thu, 13 Oct 2005 09:35:15 +0000 (GMT)
	(envelope-from olli@lurza.secnetix.de)
Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 8C2E943D49
	for <FreeBSD-gnats-submit@freebsd.org>; Thu, 13 Oct 2005 09:35:14 +0000 (GMT)
	(envelope-from olli@lurza.secnetix.de)
Received: from lurza.secnetix.de (chobmt@localhost [127.0.0.1])
	by lurza.secnetix.de (8.13.1/8.13.1) with ESMTP id j9D9ZC0n029570;
	Thu, 13 Oct 2005 11:35:13 +0200 (CEST)
	(envelope-from oliver.fromme@secnetix.de)
Received: (from olli@localhost)
	by lurza.secnetix.de (8.13.1/8.13.1/Submit) id j9D9ZCH2029569;
	Thu, 13 Oct 2005 11:35:12 +0200 (CEST)
	(envelope-from olli)
Message-Id: <200510130935.j9D9ZCH2029569@lurza.secnetix.de>
Date: Thu, 13 Oct 2005 11:35:12 +0200 (CEST)
From: Oliver Fromme <olli@secnetix.de>
Reply-To: Oliver Fromme <olli@secnetix.de>
To: FreeBSD-gnats-submit@freebsd.org
Cc: Oliver Fromme <olli@secnetix.de>
Subject: viapm(4) breaks PCI-ISA bridge --> no sc(4) --> console freezes
X-Send-Pr-Version: 3.113
X-GNATS-Notify:

>Number:         87363
>Category:       kern
>Synopsis:       [viapm] viapm(4) breaks PCI-ISA bridge --> no sc(4) --> console freezes
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    jhb
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Oct 13 09:40:15 GMT 2005
>Closed-Date:    Tue Nov 08 15:58:47 GMT 2005
>Last-Modified:  Tue Nov 08 15:58:47 GMT 2005
>Originator:     Oliver Fromme
>Release:        FreeBSD 6.0-RC1 i386
>Organization:
secnetix GmbH & Co. KG, Munich, Germany
>Environment:
System: FreeBSD epia.fromme.com 6.0-RC1 FreeBSD 6.0-RC1 #0: Wed Oct 12 17:21:20 CEST 2005 olli@epia.fromme.com:/usr/src/sys/i386/compile/EPIA i386

This is a VIA EPIA PD-10000 mainboard with VIA VT8233 / VT8235
south bridge.  I believe that all systems with those south
bridges are affected by the problem.

>Description:

When you put "device viapm" in your kernel configuration,
the VGA console (syscons) freezes upon boot as soon as the
kernel detects the viapropm0 device.  Freeze means:  The
output from the boot process stops, no keyboard input is
possible.  Meanwhile, the system boots up normally, login
via ssh is possible.  Only the console I/O is dead.

The following is a diff of dmesg between a kernel without
viapm and with viapm.  From the diff output it is clear
that the PCI-ISA bridge is not detected anymore.  My guess
is that the viapm(4) driver somehow "swallows" the device,
so the isab driver doesn't get a chance anymore to attach
to it.

Here's the diff:

--- /var/run/dmesg.previous	Wed Oct 12 16:39:06 2005
+++ /var/run/dmesg.boot	Thu Oct 13 08:06:05 2005
@@ -60,8 +60,12 @@
 usb3: USB revision 2.0
 uhub3: VIA EHCI root hub, class 9/0, rev 2.00/1.00, addr 1
 uhub3: 6 ports with 6 removable, self powered
-isab0: <PCI-ISA bridge> at device 17.0 on pci0
-isa0: <ISA bus> on isab0
+viapropm0: SMBus I/O base at 0x500
+viapropm0: SMBus I/O base at 0x500
+viapropm0: <VIA VT8233/8235 Power Management Unit> port 0x500-0x50f at device 17.0 on pci0
+viapropm0: SMBus revision code 0x0
+smbus0: <System Management Bus> on viapropm0
+smb0: <SMBus generic I/O> on smbus0
 atapci0: <VIA 8235 UDMA133 controller> port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xe000-0xe00f at device 17.1 on pci0
 ata0: <ATA channel 0> on atapci0
 ata1: <ATA channel 1> on atapci0
@@ -94,11 +98,6 @@
 sio2: type 16550A
 sio3: <16550A-compatible COM port> port 0x2e8-0x2ef irq 10 on acpi0
 sio3: type 16550A
-pmtimer0 on isa0
-orm0: <ISA Option ROM> at iomem 0xc0000-0xcdfff on isa0
-sc0: <System console> at flags 0x100 on isa0
-sc0: VGA <16 virtual consoles, flags=0x300>
-vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
 Timecounter "TSC" frequency 1002280476 Hz quality 800
 Timecounters tick every 1.000 msec
 ipfw2 (+ipv6) initialized, divert loadable, rule-based forwarding disabled, default to accept, logging disabled

Complete output from "dmesg", "pciconf -lv" and "sysctl dev hw"
can be found here:

http://www.secnetix.de/~olli/dmesg/epia/

>How-To-Repeat:

Enable "device viapm" on a system with VIA VT8233 / VT8235,
reboot, and watch the VGA console freezing.

>Fix:

Unfortunately, I'm not a kernel hacker.  I can only guess
that the viapm(4) driver is occupying the device so the
isab driver can't attach to it anymore.  It should be
possible to resolve this so both drivers can attach.
Sadly, I'm not an expert, so I have no idea how to do that.

If anyone needs any further information, I'm happy to
provide anything I can.

>Release-Note:
>Audit-Trail:

From: Oliver Fromme <olli@lurza.secnetix.de>
To: bug-followup@FreeBSD.org, olli@secnetix.de
Cc:  
Subject: Re: kern/87363: viapm(4) breaks PCI-ISA bridge --> no sc(4) --> console freezes
Date: Thu, 13 Oct 2005 12:12:35 +0200 (CEST)

 Two more pieces of information:
 
 PR kern/45574 (closed) describes exactly the same problem.
 That PR has been closed without fixing the problem.
 
 PR kern/62438 (open) contains a trivial patch to support
 the VIA VT8235 south bridge in addition to the VT8233
 which is already supported by FreeBSD.  The PR mentions
 the same problem described in this PR and in PR kern/45574.
 In the audit trail, Fujimoto Kou also mentions that the
 problem is caused by the isab (PCI-ISA bridge) not being
 probed when viapm(4) is enabled.
 
Responsible-Changed-From-To: freebsd-bugs->jhb 
Responsible-Changed-By: glebius 
Responsible-Changed-When: Mon Oct 17 11:47:40 GMT 2005 
Responsible-Changed-Why:  
John has a WIP patch for this. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=87363 

From: Gleb Smirnoff <glebius@FreeBSD.org>
To: Oliver Fromme <olli@secnetix.de>
Cc: jhb@FreeBSD.org, FreeBSD-gnats-submit@FreeBSD.org
Subject: Re: kern/87363: viapm(4) breaks PCI-ISA bridge --> no sc(4) --> console freezes
Date: Mon, 17 Oct 2005 15:47:22 +0400

   Oliver,
 
   jhb has a WIP patch for this problem:
 
 	http://people.freebsd.org/~jhb/patches/via_isab.patch
 
   He promised to commit it after I test it. Unfortunately, the problematic
 is remote and not under my control. I have managed to test it with
 ACPI, but it is required to test it without ACPI.
 
 Please test this patch on your mainboard both with and without ACPI and
 report to John. If everything is ok, he will commit it.
 
 P.S. Here is my original problem report:
 
 	http://lists.freebsd.org/pipermail/freebsd-acpi/2005-September/001939.html
 
 -- 
 Totus tuus, Glebius.
 GLEBIUS-RIPN GLEB-RIPE

From: Oliver Fromme <olli@lurza.secnetix.de>
To: glebius@FreeBSD.org (Gleb Smirnoff)
Cc: olli@secnetix.de (Oliver Fromme), jhb@FreeBSD.org,
        FreeBSD-gnats-submit@FreeBSD.org
Subject: Re: kern/87363: viapm(4) breaks PCI-ISA bridge --> no sc(4) --> console freezes
Date: Tue, 18 Oct 2005 14:10:21 +0200 (CEST)

 Gleb Smirnoff wrote:
  > 
  >   jhb has a WIP patch for this problem:
  > 
  > 	http://people.freebsd.org/~jhb/patches/via_isab.patch
  > 
  >   He promised to commit it after I test it. Unfortunately, the problematic
  > is remote and not under my control. I have managed to test it with
  > ACPI, but it is required to test it without ACPI.
  > 
  > Please test this patch on your mainboard both with and without ACPI and
  > report to John. If everything is ok, he will commit it.
 
 It's 75% OK.  :-)
 
 With ACPI enabled, everything is perfect.  Now isa0 attaches
 to viapropm0 (instead of isab0), and all child devices work
 without any problems.  The console (syscons) is functional.
 
 viapropm0: SMBus I/O base at 0x500
 viapropm0: <VIA VT8233/8235 Power Management Unit> port 0x500-0x50f at device 17.0 on pci0
 viapropm0: SMBus revision code 0x0
 smbus0: <System Management Bus> on viapropm0
 isa0: <ISA bus> on viapropm0
 pmtimer0 on isa0
 sc0: <System console> at flags 0x100 on isa0
 vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
 
 However ...  With ACPI disabled, all devices that formerly
 attached to acpi0 are gone.  Most importantly, the keyboard
 stops working.  With ACPI enabled, it's there:
 
 atkbdc0: <Keyboard controller (i8042)> port 0x60,0x64 irq 1 on acpi0
 
 With ACPI disabled, it attaches to isa0 on an unpatched
 system:
 
 atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0
 
 With ACPI disabled _and_ the patch applied, atkbdc0 is
 gone away.  The effect is, of course, that no keyboard
 input is possible on the console.  Output is working.
 I guess that console input would work fine using a USB
 keyboard, but unfortunately I had only a PS/2 keyboard
 available for testing.
 
 Beside atkbdc0, some other devices also disappeared,
 including the serial ports (sio<X> and speaker0, and the
 parallel printer port only gave this error message:
 
 ppc0: cannot reserve I/O port range
 
 Personally, I wouldn't mind if this patch gets committed,
 because I always enable ACPI anyway.  :-)  If the problem
 with non-ACPI mode could be fixed, that would be even
 better, of course.
 
 I have put all dmesg output on the following URL.  Please
 let me know if you need any further information or further
 testing.  The machine is not in production yet, so I can
 play and experiment freely.
 
 http://www.secnetix.de/~olli/dmesg/viapm/
 
 Best regards
    Oliver
 
 -- 
 Oliver Fromme,  secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing
 Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd
 Any opinions expressed in this message may be personal to the author
 and may not necessarily reflect the opinions of secnetix in any way.
 
 "Python is an experiment in how much freedom programmers need.
 Too much freedom and nobody can read another's code; too little
 and expressiveness is endangered."
         -- Guido van Rossum

From: John Baldwin <jhb@freebsd.org>
To: Oliver Fromme <olli@secnetix.de>
Cc: Gleb Smirnoff <glebius@freebsd.org>,
 FreeBSD-gnats-submit@freebsd.org
Subject: Re: kern/87363: viapm(4) breaks PCI-ISA bridge --> no sc(4) --> console freezes
Date: Tue, 18 Oct 2005 12:33:52 -0400

 On Tuesday 18 October 2005 08:10 am, Oliver Fromme wrote:
 > Gleb Smirnoff wrote:
 >  >   jhb has a WIP patch for this problem:
 >  >
 >  > 	http://people.freebsd.org/~jhb/patches/via_isab.patch
 >  >
 >  >   He promised to commit it after I test it. Unfortunately, the
 >  > problematic is remote and not under my control. I have managed to test
 >  > it with ACPI, but it is required to test it without ACPI.
 >  >
 >  > Please test this patch on your mainboard both with and without ACPI and
 >  > report to John. If everything is ok, he will commit it.
 >
 > It's 75% OK.  :-)
 >
 > With ACPI enabled, everything is perfect.  Now isa0 attaches
 > to viapropm0 (instead of isab0), and all child devices work
 > without any problems.  The console (syscons) is functional.
 >
 > viapropm0: SMBus I/O base at 0x500
 > viapropm0: <VIA VT8233/8235 Power Management Unit> port 0x500-0x50f at
 > device 17.0 on pci0 viapropm0: SMBus revision code 0x0
 > smbus0: <System Management Bus> on viapropm0
 > isa0: <ISA bus> on viapropm0
 > pmtimer0 on isa0
 > sc0: <System console> at flags 0x100 on isa0
 > vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
 >
 > However ...  With ACPI disabled, all devices that formerly
 > attached to acpi0 are gone.  Most importantly, the keyboard
 > stops working.  With ACPI enabled, it's there:
 >
 > atkbdc0: <Keyboard controller (i8042)> port 0x60,0x64 irq 1 on acpi0
 >
 > With ACPI disabled, it attaches to isa0 on an unpatched
 > system:
 >
 > atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0
 >
 > With ACPI disabled _and_ the patch applied, atkbdc0 is
 > gone away.  The effect is, of course, that no keyboard
 > input is possible on the console.  Output is working.
 > I guess that console input would work fine using a USB
 > keyboard, but unfortunately I had only a PS/2 keyboard
 > available for testing.
 >
 > Beside atkbdc0, some other devices also disappeared,
 > including the serial ports (sio<X> and speaker0, and the
 > parallel printer port only gave this error message:
 >
 > ppc0: cannot reserve I/O port range
 >
 > Personally, I wouldn't mind if this patch gets committed,
 > because I always enable ACPI anyway.  :-)  If the problem
 > with non-ACPI mode could be fixed, that would be even
 > better, of course.
 >
 > I have put all dmesg output on the following URL.  Please
 > let me know if you need any further information or further
 > testing.  The machine is not in production yet, so I can
 > play and experiment freely.
 >
 > http://www.secnetix.de/~olli/dmesg/viapm/
 >
 > Best regards
 >    Oliver
 
 Erm, in your non-ACPI non-patched case you don't have viapm in your kernel, as 
 isab(4) attaches:
 
 isab0: <PCI-ISA bridge> at device 17.0 on pci0
 isa0: <ISA bus> on isab0
 
 Note that in your patched case, you do have viapm in your kernel:
 
 viapropm0: SMBus I/O base at 0x500
 viapropm0: SMBus I/O base at 0x500
 viapropm0: <VIA VT8233/8235 Power Management Unit> port 0x500-0x50f at device 
 17.0 on pci0
 viapropm0: SMBus revision code 0x0
 smbus0: <System Management Bus> on viapropm0
 smb0: <SMBus generic I/O> on smbus0
 isa0: <ISA bus> on viapropm0
 
 Can you try the non-patched kernel with viapm in it to see how it fares?  
 Perhaps the viapm(4) driver has done something to break the ISA bus?
 
 -- 
 John Baldwin <jhb@FreeBSD.org>  <><  http://www.FreeBSD.org/~jhb/
 "Power Users Use the Power to Serve"  =  http://www.FreeBSD.org

From: Oliver Fromme <olli@lurza.secnetix.de>
To: jhb@freebsd.org (John Baldwin)
Cc: olli@secnetix.de (Oliver Fromme), glebius@freebsd.org (Gleb Smirnoff),
        FreeBSD-gnats-submit@freebsd.org
Subject: Re: kern/87363: viapm(4) breaks PCI-ISA bridge --> no sc(4) --> console freezes
Date: Wed, 19 Oct 2005 11:39:46 +0200 (CEST)

 John Baldwin wrote:
  > Erm, in your non-ACPI non-patched case you don't have viapm in your kernel, as 
  > isab(4) attaches:
  > 
  > isab0: <PCI-ISA bridge> at device 17.0 on pci0
  > isa0: <ISA bus> on isab0
 
 I'm sorry for the confusion.  I _do_ always have viapm in
 the kernel, but the VIA VT8235 isn't recognized with an
 unpatched viapm.c file.  So, when I wrote "patched", I
 actually meant two patches:  the patch from kern/62438
 (enabling recognition ov the VT8235), and your patch.
 
 When I have _only_ the VT8235 patch in the kernel (but
 not your patch), the system behaves exactly like described
 in kern/87363, see the dmesg diff at the top of that PR:
 There is neither isab0 nor isa0, and none of the devices
 on them are attached, including sc0, so the console is
 completely dead.
 
 Again:  I'm sorry for the confusion.  My description should
 have been more clear.
 
  > Can you try the non-patched kernel with viapm in it to see how it fares?
 
 See above, and see the dmesg diff at the top of kern/87363.
 
 I haven't tried that without ACPI, though.  I can give that
 I try, but not before tomorrow, because my time is too
 limited today.  (Obviously, I can only test it when sitting
 at the console.)
 
 However, I'm sure that it'll behave exactly the same as
 with ACPI enabled, i.e. the console will be dead because
 there's no isab0 or isa0.
 
 Best regards
    Oliver
 
 -- 
 Oliver Fromme,  secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing
 Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd
 Any opinions expressed in this message may be personal to the author
 and may not necessarily reflect the opinions of secnetix in any way.
 
 Perl is worse than Python because people wanted it worse.
         -- Larry Wall

From: John Baldwin <jhb@freebsd.org>
To: Oliver Fromme <olli@lurza.secnetix.de>
Cc: Gleb Smirnoff <glebius@freebsd.org>,
 FreeBSD-gnats-submit@freebsd.org
Subject: Re: kern/87363: viapm(4) breaks PCI-ISA bridge --> no sc(4) --> console freezes
Date: Wed, 19 Oct 2005 11:30:20 -0400

 On Wednesday 19 October 2005 05:39 am, Oliver Fromme wrote:
 > John Baldwin wrote:
 >  > Can you try the non-patched kernel with viapm in it to see how it fares?
 >
 > See above, and see the dmesg diff at the top of kern/87363.
 >
 > I haven't tried that without ACPI, though.  I can give that
 > I try, but not before tomorrow, because my time is too
 > limited today.  (Obviously, I can only test it when sitting
 > at the console.)
 >
 > However, I'm sure that it'll behave exactly the same as
 > with ACPI enabled, i.e. the console will be dead because
 > there's no isab0 or isa0.
 
 Not quite true because when we don't use ACPI, the legacy0 device always adds 
 an isa0 child if there isn't one already added after all the PCI devices 
 probe.  However, what your dmesg's show is that in the case of no-ACPI plus 
 my patch, your isa0 device is somehow busted, so what I'm curious is the case 
 of no-ACPI plus the other patch to see if the isa0 that legacy0 adds is 
 similarly busted, in which case my patch doesn't make things worse.  To be 
 honest, I'm really not sure how my patch could cause the breakage in the 
 non-ACPI case that you are seeing since isa0 doesn't really care what it's 
 parent device is.
 
 -- 
 John Baldwin <jhb@FreeBSD.org>  <><  http://www.FreeBSD.org/~jhb/
 "Power Users Use the Power to Serve"  =  http://www.FreeBSD.org

From: Oliver Fromme <olli@lurza.secnetix.de>
To: jhb@freebsd.org (John Baldwin)
Cc: glebius@freebsd.org (Gleb Smirnoff), FreeBSD-gnats-submit@freebsd.org
Subject: Re: kern/87363: viapm(4) breaks PCI-ISA bridge --> no sc(4) --> console freezes
Date: Thu, 20 Oct 2005 12:37:39 +0200 (CEST)

 John Baldwin wrote:
  > On Wednesday 19 October 2005 05:39 am, Oliver Fromme wrote:
  > > John Baldwin wrote:
  > > > Can you try the non-patched kernel with viapm in it to see how it fares?
  > > 
  > > See above, and see the dmesg diff at the top of kern/87363.
  > > 
  > > I haven't tried that without ACPI, though.  I can give that
  > > I try, but not before tomorrow, because my time is too
  > > limited today.  (Obviously, I can only test it when sitting
  > > at the console.)
  > > 
  > > However, I'm sure that it'll behave exactly the same as
  > > with ACPI enabled, i.e. the console will be dead because
  > > there's no isab0 or isa0.
  > 
  > Not quite true because when we don't use ACPI, the legacy0 device always adds 
  > an isa0 child if there isn't one already added after all the PCI devices 
  > probe.
 
 You are absolutely right.  I tried the kernel with viapm
 but without your patch, and the result was not quite what
 I expected:  Without ACPI, the console works perfectly
 fine.  With ACPI enabled, there is no sc0 or vga0, so the
 console is dead (as described in my PR kern/87363).
 
 I have updated my dmesg matrix at this URL:
 
 http://www.secnetix.de/~olli/dmesg/viapm/
 
  > However, what your dmesg's show is that in the case of no-ACPI plus 
  > my patch, your isa0 device is somehow busted, so what I'm curious is the case 
  > of no-ACPI plus the other patch to see if the isa0 that legacy0 adds is 
  > similarly busted, in which case my patch doesn't make things worse.
 
 I'm afraid it seems to work fine without your patch (and
 ACPI disabled).  So, indeed your patch makes things worse
 in the no-ACPI case, but improves things in the ACPI case.
 
 Tomorrow I will have a look at the BIOS setup.  Maybe there
 are ACPI-related or keyboard-related settings that I can
 try to play with.
 
 Best regards
    Oliver
 
 -- 
 Oliver Fromme,  secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing
 Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd
 Any opinions expressed in this message may be personal to the author
 and may not necessarily reflect the opinions of secnetix in any way.
 
 "If you think C++ is not overly complicated, just what is a protected
 abstract virtual base pure virtual private destructor, and when was the
 last time you needed one?"
         -- Tom Cargil, C++ Journal

From: Oliver Fromme <olli@lurza.secnetix.de>
To: jhb@freebsd.org (John Baldwin)
Cc: bug-followup@freebsd.org
Subject: Re: kern/87363: viapm(4) breaks PCI-ISA bridge --> no sc(4) --> console freezes
Date: Mon, 31 Oct 2005 10:47:44 +0100 (CET)

 John Baldwin wrote:
  > Ok, I think I figured out the issue.  The viapm drivers weren't implementing 
  > the bus interface for resource allocation, etc. so I think all the calls to 
  > bus_alloc_resource() by the ISA device drivers were failing.  I've updated 
  > the patch and refreshed it at 
  > http://www.freebsd.org/~jhb/patches/via_isab.patch  Please give it another go 
  > and let me know if it works.  Thanks!
 
 YESSS!!!  It works perfectly now, with and without ACPI!
 Thank you very, very much!
 
 Please commit this patch, along with the patch from PR
 kern/62438 which adds the PCI ID of the VIA VT8235.
 
 As usual, I've updated the dmesg output matrix here:
 http://www.secnetix.de/~olli/dmesg/viapm/
 
 Best regards
    Oliver
 
 -- 
 Oliver Fromme,  secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing
 Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd
 Any opinions expressed in this message may be personal to the author
 and may not necessarily reflect the opinions of secnetix in any way.
 
 "And believe me, as a C++ programmer, I don't hesitate to question
 the decisions of language designers.  After a decent amount of C++
 exposure, Python's flaws seem ridiculously small." -- Ville Vainio
State-Changed-From-To: open->patched 
State-Changed-By: jhb 
State-Changed-When: Mon Oct 31 18:31:30 GMT 2005 
State-Changed-Why:  
Patch committed to HEAD. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=87363 
State-Changed-From-To: patched->closed 
State-Changed-By: jhb 
State-Changed-When: Tue Nov 8 15:57:59 GMT 2005 
State-Changed-Why:  
Merged to 5.x and 6.x. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=87363 
>Unformatted:
