From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 7 07:11:01 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org 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 8942816A41F for ; Wed, 7 Dec 2005 07:11:01 +0000 (GMT) (envelope-from ilovefd@topaz.plala.or.jp) Received: from mvs5.plala.or.jp (c158133.vh.plala.or.jp [210.150.158.133]) by mx1.FreeBSD.org (Postfix) with ESMTP id ADF5943D46 for ; Wed, 7 Dec 2005 07:10:59 +0000 (GMT) (envelope-from ilovefd@topaz.plala.or.jp) Received: from ilovefd533 ([150.29.122.91]) by mvs5.plala.or.jp with SMTP id <20051207071058.DGLG5652.mvs5.plala.or.jp@ilovefd533> for ; Wed, 7 Dec 2005 16:10:58 +0900 Message-ID: <017b01c5fafd$a5f9d250$1400a8c0@ilovefd533> From: "gama" To: References: <20051130020734.GA6577@nowhere> <20051206015129.GA34415@nowhere><20051206035228.GA34979@nowhere> <200512061520.31168.jhb@freebsd.org> Date: Wed, 7 Dec 2005 16:12:56 +0900 MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1506 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506 Subject: twm doesn"t start with vnc server on FreeBSD l5.4/amd64 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Dec 2005 07:11:01 -0000 I am using FreeBSD5.4/amd5.4 but any windows manager doesn"t start with vnc server. FreeBSD5.4/amd64 has any troubles with X windows? FreeBSD5.4/i386 workede well with vnc and twm. ----- Original Message ----- From: "John Baldwin" To: "Craig Boston" Cc: Sent: Wednesday, December 07, 2005 5:20 AM Subject: Re: Weird PCI interrupt delivery problem > On Monday 05 December 2005 10:52 pm, Craig Boston wrote: > > On Mon, Dec 05, 2005 at 07:51:29PM -0600, Craig Boston wrote: > > > With the ACPI timer disabled (debug.acpi.disabled=timer), the ACPI+APIC > > > case now behaves the same as the plain APIC case. Each IRQ gets > > > anywhere from 10,000-500,000 interrupts before it simply stops working. > > > > And to follow up to myself yet again, the i8254 timecounter is also bad > > news for APIC. Switching to it, with or without ACPI, causes things to > > stop working really fast. > > > > Just a stab in the dark, but it sounds like there may be something > > screwy going on in the interconnect between the I/O APIC and the 8259s. > > I'm pretty familiar with old-style (ISA) design, but somewhat fuzzy on > > exactly how those two normally coexist, especially when everything is > > integrated together on a bridge chip somewhere. > > > > IIRC there used to be some mixed-mode hacks that have been cleaned up in > > 6.0. Might Windows still be doing something similar and that's why it > > works? > > No, Windows doesn't use mixed mode. That stuff only had to do with routing > IRQ0 anyways. We use the lapic timer instead of IRQ0 now (as does Windows). > > -- > John Baldwin <>< http://www.FreeBSD.org/~jhb/ > "Power Users Use the Power to Serve" = http://www.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" >