From owner-freebsd-amd64@FreeBSD.ORG Sun Sep 14 14:34:22 2008 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 35A251065671; Sun, 14 Sep 2008 14:34:22 +0000 (UTC) (envelope-from kamikaze@bsdforen.de) Received: from mail.bsdforen.de (bsdforen.de [212.204.60.79]) by mx1.freebsd.org (Postfix) with ESMTP id EF02C8FC08; Sun, 14 Sep 2008 14:34:21 +0000 (UTC) (envelope-from kamikaze@bsdforen.de) Received: from mobileKamikaze.norad (unknown [92.117.250.173]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.bsdforen.de (Postfix) with ESMTP id 6FFAF8A0141; Sun, 14 Sep 2008 16:33:56 +0200 (CEST) Message-ID: <48CD20CB.3040706@bsdforen.de> Date: Sun, 14 Sep 2008 16:33:47 +0200 From: Dominic Fandrey User-Agent: Thunderbird 2.0.0.16 (X11/20080810) MIME-Version: 1.0 To: John Baldwin References: <200809111640.m8BGe4PX012172@freefall.freebsd.org> <200809111637.54863.jhb@freebsd.org> In-Reply-To: <200809111637.54863.jhb@freebsd.org> X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Sun, 14 Sep 2008 14:53:05 +0000 Cc: freebsd-amd64@freebsd.org Subject: Re: amd64/127276: ldd invokes linux yes X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Sep 2008 14:34:22 -0000 John Baldwin wrote: > FreeBSD binaries from various releases have been branded in different ways. I > would consider it more of a user error to run ldd on a Linux binary. :) You > could maybe add a "IMPLEMENTATION NOTES" section to the manpage that explains > how it works and why it will execute any binary using a different runtime > linker. > Well, documenting it is much better than the current state. Though in my opinion it doesn't matter to the user how it works, but what one expects the program to do. And the current behaviour is not what I expected. Would you instead accept a patch from me that does a compatibility check and bails out if the binary does not use the FreeBSD linker? The "IMPLEMENTATION NOTES" would still be nice to have, though. It's always a nice read to get an idea on how something works. And I find code much easier to decipher if I already know how it's supposed to do something. At least much easier than the opposite way, trying to glimpse how something works from the code. Regards From owner-freebsd-amd64@FreeBSD.ORG Sun Sep 14 15:56:28 2008 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 379BA106564A for ; Sun, 14 Sep 2008 15:56:28 +0000 (UTC) (envelope-from freebsd@abv.bg) Received: from smtp-out.abv.bg (smtp-out.abv.bg [194.153.145.99]) by mx1.freebsd.org (Postfix) with ESMTP id D87E28FC1A for ; Sun, 14 Sep 2008 15:56:27 +0000 (UTC) (envelope-from freebsd@abv.bg) Received: from mail51.abv.bg (mail51.ni.bg [192.168.151.12]) by smtp-out.abv.bg (Postfix) with ESMTP id B95E73FC26 for ; Sun, 14 Sep 2008 18:39:50 +0300 (EEST) DomainKey-Signature: a=rsa-sha1; s=smtp-out; d=abv.bg; c=simple; q=dns; b=KxEFNPnR92b+q+6mWz5iTJN86GwLzTHwjTWJTiWPk35EBaAoYRqz7a/29nmIUeClv qQxihFBJyfdQROsNLUBL2GxZy9on98oT3j5S2/Po0aKRve6aApEgeWRSKZkx44LQXmL eFCWdMNf2WJOOl3ENRR9JccDi2cx8c7iZ/bg/sI= DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=abv.bg; s=smtp-out; t=1221406790; bh=DVqO4wRtLSUJZfb8Ua8IDpCD360iPFL1m2VQBQPJFZY=; h=Date:From:To:Message-ID:Subject:MIME-Version:Content-Type: Content-Transfer-Encoding:DKIM; b=OUKgH/ctvN8Ms9cW3p+24eIWIQyZ4TMx kiZAb04sTzuJsaoDx3VhH0jYTJM40/TQen6izHTkbTRvFAN1c/GsV6TtjfhOzD4eoNp nNeCXA6FePA1KJZyxWiN8ix7SyWkVHKLNmF8mG70gN0Jv+j6KoEDSbtsFK5PJjvDEHb 5vFRI= Received: from mail51.abv.bg (mail51.abv.bg [127.0.0.1]) by mail51.abv.bg (Postfix) with ESMTP id 6A02A12DF24 for ; Sun, 14 Sep 2008 18:40:29 +0300 (EEST) Date: Sun, 14 Sep 2008 18:40:29 +0300 (EEST) From: Mario Pavlov To: freebsd-amd64@freebsd.org Message-ID: <1947694103.82294.1221406829431.JavaMail.apache@mail51.abv.bg> MIME-Version: 1.0 Content-Type: text/plain; charset="windows-1251" Content-Transfer-Encoding: 8bit X-Priority: 3 X-Mailer: AbvMail 1.0 X-Originating-IP: 78.128.21.208 Subject: g_vfs_done() error = 6 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Sep 2008 15:56:28 -0000 Hi list, I was running my FreeBSD-amd64 7 stable for quite some time without any problems until suddenly it started to spit out those: ad10: detached g_vfs_done(): ad10s2a[READ(offset=412188672, length=16384)]error = 6 g_vfs_done(): ad10s2a[READ(offset=412188672, length=16384)]error = 6 vm_fault: pager read error, pid 698 (devd) g_vfs_done(): ad10s2a[READ(offset=98304, length=16384)]error = 6 g_vfs_done(): ad10s2a[READ(offset=578027520, length=16384)]error = 6 g_vfs_done(): ad10s2a[READ(offset=1348599808, length=16384)]error = 6 ... ... ... panic: vinvalbuf: dirty bufs cpuid = 0 KDB: enter: panic [thread pid 960 tid 100057] Stopped at kdb_enter+0x3d: movq $0,0x431b24(%rip) then I'm in the db> "prompt" and after a few minutes I get this: panic: knlist not locked, but should be cpuid = 0 Cannot dump, no dump device defined Automatic reboot in 15 seconds... what I want to find out is whether this is caused by hardware failure or it's software problem I upgraded to 8-CURRENT just to try if it will be the same and it is do you think this is hardware problem or not ? thank you Regards MGP From owner-freebsd-amd64@FreeBSD.ORG Mon Sep 15 04:25:08 2008 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 81213106566B for ; Mon, 15 Sep 2008 04:25:08 +0000 (UTC) (envelope-from xxjack12xx@gmail.com) Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.233]) by mx1.freebsd.org (Postfix) with ESMTP id 378988FC19 for ; Mon, 15 Sep 2008 04:25:08 +0000 (UTC) (envelope-from xxjack12xx@gmail.com) Received: by wx-out-0506.google.com with SMTP id s17so813399wxc.7 for ; Sun, 14 Sep 2008 21:25:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=ksGeevj6ALOb8W8iyPS2QxhxQrnv35cqKg8/JKjj9yY=; b=qXZK5xTmxcJ1xV6r+Fy3cLeLxfw6TvfzPp3TBxV5BQV+Pb3+BdaZCldRHtpki6urht j6a6l+MHLRi1UMxhKvhQKbfBfTdQoFOYrz06OWFGp8QLzCYlIgmA/tzncltyzpYR1DNf PSf8upZhzlht9dX/2vK69IApPPY9/v9cP2S+w= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=Wizx/G5vSDIAOZQmBzJGNKbdybiZzqImBjBh8oTm3ZG9MUTyfmDtapBCgFZ4WxSyXF uwInIHQPBF5M8kasIn1WgwTr+EquY1kixQXX6dWkDPLV0vJm1U3a4iQfK0IvCnuMKjML OKXP/GaghwgprxMlydLKAMN0Ec1TVu656SB2A= Received: by 10.70.16.8 with SMTP id 8mr8691703wxp.65.1221452707466; Sun, 14 Sep 2008 21:25:07 -0700 (PDT) Received: by 10.70.37.4 with HTTP; Sun, 14 Sep 2008 21:25:07 -0700 (PDT) Message-ID: Date: Sun, 14 Sep 2008 21:25:07 -0700 From: "Jack L." To: "Mario Pavlov" In-Reply-To: <1947694103.82294.1221406829431.JavaMail.apache@mail51.abv.bg> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <1947694103.82294.1221406829431.JavaMail.apache@mail51.abv.bg> Cc: freebsd-amd64@freebsd.org Subject: Re: g_vfs_done() error = 6 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Sep 2008 04:25:08 -0000 On Sun, Sep 14, 2008 at 8:40 AM, Mario Pavlov wrote: > Hi list, > I was running my FreeBSD-amd64 7 stable for quite some time without any problems until suddenly it started to spit out those: > > ad10: detached > g_vfs_done(): ad10s2a[READ(offset=412188672, length=16384)]error = 6 > g_vfs_done(): ad10s2a[READ(offset=412188672, length=16384)]error = 6 > vm_fault: pager read error, pid 698 (devd) > g_vfs_done(): ad10s2a[READ(offset=98304, length=16384)]error = 6 > g_vfs_done(): ad10s2a[READ(offset=578027520, length=16384)]error = 6 > g_vfs_done(): ad10s2a[READ(offset=1348599808, length=16384)]error = 6 > ... > ... > ... > panic: vinvalbuf: dirty bufs > cpuid = 0 > KDB: enter: panic > [thread pid 960 tid 100057] > Stopped at kdb_enter+0x3d: movq $0,0x431b24(%rip) > > then I'm in the db> "prompt" > and after a few minutes I get this: > > panic: knlist not locked, but should be > cpuid = 0 > Cannot dump, no dump device defined > Automatic reboot in 15 seconds... > > what I want to find out is whether this is caused by hardware failure or it's software problem > I upgraded to 8-CURRENT just to try if it will be the same and it is > > do you think this is hardware problem or not ? > thank you > Sounds like a dead hard drive or a drive going bad. From owner-freebsd-amd64@FreeBSD.ORG Mon Sep 15 05:19:24 2008 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 413C51065675 for ; Mon, 15 Sep 2008 05:19:24 +0000 (UTC) (envelope-from freebsd@abv.bg) Received: from smtp-out.abv.bg (smtp-out.abv.bg [194.153.145.99]) by mx1.freebsd.org (Postfix) with ESMTP id BE0148FC15 for ; Mon, 15 Sep 2008 05:19:23 +0000 (UTC) (envelope-from freebsd@abv.bg) Received: from mail52.abv.bg (mail52.ni.bg [192.168.151.19]) by smtp-out.abv.bg (Postfix) with ESMTP id 716A63FAC4; Mon, 15 Sep 2008 08:18:41 +0300 (EEST) DomainKey-Signature: a=rsa-sha1; s=smtp-out; d=abv.bg; c=simple; q=dns; b=S3pBBXq/zZvhmto3hSqlzRnNpFPmXZh3SaauqGdI8Irc0c60UceFvVraak556NXZS ll3Q2JLHlt1Hofz+7152OZML51kpR+jMVlRsT4OwsB5ipv7MbCNwZQ6Y0ku4J0pu7wD 3BFZitvA7wSlTfl0Bqn6pFuOIIbZI7/Op6188aU= DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=abv.bg; s=smtp-out; t=1221455921; bh=N13rBIwHf9I39Mk0seMo0YGkY6zrhk3H4xD6Np06ZGQ=; h=Date:From:To:Cc:Message-ID:Subject:MIME-Version:Content-Type: Content-Transfer-Encoding:DKIM; b=MgZVs9RVfPqMh/FTZ2KBCYGFwtpVzw8G X1qR2PjrX780ioXZ5j+g71vSQUnjKy3UfbJ49NBVqltvJP1fZ3a72qI4Jrsz8stHcTj Csb+FrHBdKpIl1VN933chzSgfx0g1ctuYX4BuV+GtKvOrFrTrVf/yqttmTgEygOvXGC xY2XQ= Received: from mail52.abv.bg (mail52.abv.bg [127.0.0.1]) by mail52.abv.bg (Postfix) with ESMTP id 20FA71ACA60; Mon, 15 Sep 2008 08:19:22 +0300 (EEST) Date: Mon, 15 Sep 2008 08:19:22 +0300 (EEST) From: Mario Pavlov To: "Jack L." Message-ID: <1616142420.85642.1221455962133.JavaMail.apache@mail52.abv.bg> MIME-Version: 1.0 Content-Type: text/plain; charset="windows-1251" Content-Transfer-Encoding: 8bit X-Priority: 3 X-Mailer: AbvMail 1.0 X-Originating-IP: 78.128.21.208 Cc: freebsd-amd64@freebsd.org Subject: Re: Re: g_vfs_done() error = 6 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Sep 2008 05:19:24 -0000 >> Hi list, >> I was running my FreeBSD-amd64 7 stable for quite some time without any problems until suddenly it started to spit out those: >> >> ad10: detached >> g_vfs_done(): ad10s2a[READ(offset=412188672, length=16384)]error = 6 >> g_vfs_done(): ad10s2a[READ(offset=412188672, length=16384)]error = 6 >> vm_fault: pager read error, pid 698 (devd) >> g_vfs_done(): ad10s2a[READ(offset=98304, length=16384)]error = 6 >> g_vfs_done(): ad10s2a[READ(offset=578027520, length=16384)]error = 6 >> g_vfs_done(): ad10s2a[READ(offset=1348599808, length=16384)]error = 6 >> ... >> ... >> ... >> panic: vinvalbuf: dirty bufs >> cpuid = 0 >> KDB: enter: panic >> [thread pid 960 tid 100057] >> Stopped at kdb_enter+0x3d: movq $0,0x431b24(%rip) >> >> then I'm in the db> "prompt" >> and after a few minutes I get this: >> >> panic: knlist not locked, but should be >> cpuid = 0 >> Cannot dump, no dump device defined >> Automatic reboot in 15 seconds... >> >> what I want to find out is whether this is caused by hardware failure or it's software problem >> I upgraded to 8-CURRENT just to try if it will be the same and it is >> >> do you think this is hardware problem or not ? >> thank you >> >Sounds like a dead hard drive or a drive going bad. Hi I was thinking the same and I decided to try with another OS just in case I'm running windows xp for almost all day and it works...no HDD failure... my HDD is 500GB Seagate ST3500320AS SATA2 and I was running it in AHCI mode but I had to set it to IDE mode in order to run windows since windows can't run on AHCI so I'm a little bit confused...it works ok with windows and IDE but crashes on FreeBSD and AHCI... I'll stay with the windows several more hours and try FreeBSD and IDE thank you regards MGP From owner-freebsd-amd64@FreeBSD.ORG Mon Sep 15 15:18:44 2008 Return-Path: Delivered-To: freebsd-amd64@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 852761065682 for ; Mon, 15 Sep 2008 15:18:44 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 73AF58FC1C for ; Mon, 15 Sep 2008 15:18:44 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m8FFIior018805 for ; Mon, 15 Sep 2008 15:18:44 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m8FFIh1N018801 for freebsd-amd64@FreeBSD.org; Mon, 15 Sep 2008 15:18:43 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 15 Sep 2008 15:18:43 GMT Message-Id: <200809151518.m8FFIh1N018801@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-amd64@FreeBSD.org X-Mailman-Approved-At: Mon, 15 Sep 2008 15:35:56 +0000 Cc: Subject: Current problem reports assigned to freebsd-amd64@FreeBSD.org X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Sep 2008 15:18:44 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o amd64/127276 amd64 ldd(1) invokes linux yes o amd64/127275 amd64 ldd(1) produces uncatchable output o amd64/127129 amd64 mdconfig(8) is core dumping with Segmentation Fault 11 f amd64/125943 amd64 Serial Consoles do not work on amd64 freebsd o amd64/125873 amd64 [smbd] [panic] Repeated kernel panics, trap 12 page fa o amd64/125820 amd64 [k8temp] [patch] sysctl dev.k8temp.*.sensor1.* are inv o amd64/125002 amd64 [install] amd64, SATA hard disks not detected o amd64/124432 amd64 [panic] 7.0-STABLE panic: invalbuf: dirty bufs o amd64/124134 amd64 [kernel] The kernel doesn't follow the calling convent o amd64/123562 amd64 [install] FreeBSD amd64 not installs o amd64/123520 amd64 [ahd] unable to boot from net while using ahd o amd64/123456 amd64 fstat(1): /usr/bin/fstat shows error messages and hang f amd64/123275 amd64 [cbb] [pcmcia] cbb/pcmcia drivers on amd64 failure [re o kern/122782 amd64 [modules] accf_http.ko kernel module is not loadable o amd64/122695 amd64 [cpufreq] Lack of cpufreq control using amd64 eith cor o amd64/122624 amd64 unusable minimal installation of FreeBSD-7.0 o amd64/122549 amd64 7.0-RELEASE-amd64-bootonly.iso doesn't work w/ serial o amd64/122468 amd64 Compile problems after upgrading to 7.0 o amd64/122174 amd64 [panic] 7.0 no longer includes "device atpic" so fails o amd64/121590 amd64 [est] [p4tcc] [acpi_perf] setting dev.cpu.0.freq somet o amd64/121439 amd64 [boot] Installation of FreeBSD 7.0 fails: ACPI problem o amd64/120202 amd64 [amd64] [patch] [panic] kernel panic at start_all_aps, o amd64/119936 amd64 [install] FreeBSD 7.0-RC1 amd64 and i386 installer dis o amd64/119591 amd64 [amd64] [patch] time_t on 64-bit architecture o amd64/117418 amd64 [hang] FreeBSD 6.2 crash on amd64 4400+ with ssh o amd64/117316 amd64 [acpi] ACPI lockups on SuperMicro motherboard o amd64/117296 amd64 [ata] I don`t see second SATA IDE on VIA VT8237A a amd64/117186 amd64 [modules] kldload Unsupported file type on STABLE amd6 s amd64/116689 amd64 [request] support for MSI K9MM-V f amd64/116670 amd64 [ata] onboard SATA RAID1 controllers not supported for o amd64/116620 amd64 [hang] ifconfig spins when creating carp(4) device on f amd64/116457 amd64 [install] can't install freebsd on dv9420us o amd64/116322 amd64 [panic] At start fsck on current, the system panics o amd64/116159 amd64 [panic] Panic while debugging on CURRENT s amd64/115815 amd64 [ata] [request] Gigabyte GA-M61P-S3 Motherboard unsupp o amd64/115581 amd64 [Makefile] [patch] -mfancy-math-387 has no effect o amd64/115194 amd64 LCD screen remains blank after Dell XPS M1210 lid is c o amd64/114270 amd64 [cpufreq] cpufreq doesnt work when compiled in to kern o amd64/114111 amd64 [nfs] System crashes while writing on NFS-mounted shar f amd64/113021 amd64 [re] ASUS M2A-VM onboard NIC does not work o amd64/112222 amd64 [libc] 32-bit libc incorrectly converts some FP number f amd64/111992 amd64 [boot] BTX failed - HP Laptop dv2315nr o amd64/110655 amd64 [threads] 32 bit threaded applications crash on amd64 o amd64/110599 amd64 [geli] geli attach to gmirror device hangs and cannot a amd64/109584 amd64 zdump(8) doesn't work s amd64/108861 amd64 [nve] nve(4) driver on FreeBSD 6.2 AMD64 does not work o amd64/106186 amd64 [panic] panic in swap_pager_swap_init (amd64/smp/6.2-p f amd64/105629 amd64 [re] TrendNet TEG-BUSR 10/100/1000 disables itself on f amd64/105531 amd64 [ata] gigabyte GA-M51GM-S2G / nVidia nForce 430 - does f amd64/105514 amd64 [boot] FreeBSD/amd64 - Fails to boot on HP Pavilion dv f amd64/103259 amd64 [ar] Cannot use ataraid on nvidia nForce4+amd64 o amd64/102716 amd64 ex with no argument in an xterm gets SIGSEGV o amd64/97337 amd64 [dri] xorg reboots system if dri module is enabled o amd64/95888 amd64 [ata] kernel: ad2: TIMEOUT - WRITE_DMA retrying on HP f amd64/94989 amd64 [boot] BTX Halts on Sun Fire X2100 w/6.1-BETA4 (amd64) o amd64/94677 amd64 [panic] panic in amd64 install at non-root user creati o amd64/93961 amd64 [busdma] Problem in bounce buffer handling in sys/amd6 o amd64/92337 amd64 [em] FreeBSD 6.0 Release Intel Pro 1000 MT em1 no buff f amd64/91492 amd64 [boot] BTX halted o amd64/91405 amd64 [asr] [panic] Kernel panic caused by asr on 6.0-amd64 o amd64/89501 amd64 [install] System crashes on install using ftp on local o amd64/88790 amd64 [panic] kernel panic on first boot (after the FreeBSD o amd64/88568 amd64 [panic] 6.0-RELEASE install cd does not boot with usb o amd64/87977 amd64 [busdma] [panic] amd64 busdma dflt_lock called (by ata o amd64/87689 amd64 [powerd] [hang] powerd hangs SMP Opteron 244 5-STABLE o amd64/87316 amd64 [vge] "vge0 attach returned 6" on FreeBSD 6.0-RC1 amd6 o amd64/87305 amd64 [smp] Dual Opteron / FreeBSD 5 & 6 / powerd results in f amd64/87258 amd64 [smp] [boot] cannot boot with SMP and Areca ARC-1160 r f amd64/86080 amd64 [radeon] [hang] radeon DRI causes system hang on amd64 s amd64/85273 amd64 [install] FreeBSD (NetBSD or OpenBSD) not install on l o amd64/78406 amd64 [panic]AMD64 w/ SCSI: issue 'rm -r /usr/ports' and sys o amd64/76136 amd64 [hang] system halts before reboot o amd64/74747 amd64 [panic] System panic on shutdown when process will not o amd64/73322 amd64 [msdosfs] [hang] unarchiving /etc to msdosfs locks up 74 problems total. From owner-freebsd-amd64@FreeBSD.ORG Mon Sep 15 18:00:08 2008 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5889D1065673 for ; Mon, 15 Sep 2008 18:00:08 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 3E3AB8FC17 for ; Mon, 15 Sep 2008 18:00:08 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m8FI08bi034679 for ; Mon, 15 Sep 2008 18:00:08 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m8FI08uS034678; Mon, 15 Sep 2008 18:00:08 GMT (envelope-from gnats) Date: Mon, 15 Sep 2008 18:00:08 GMT Message-Id: <200809151800.m8FI08uS034678@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: Dominic Fandrey X-Mailman-Approved-At: Mon, 15 Sep 2008 18:03:55 +0000 Cc: Subject: Re: amd64/127275: ldd(1) produces uncatchable output X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Dominic Fandrey List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Sep 2008 18:00:08 -0000 The following reply was made to PR amd64/127275; it has been noted by GNATS. From: Dominic Fandrey To: bug-followup@FreeBSD.org, kamikaze@bsdforen.de Cc: Subject: Re: amd64/127275: ldd(1) produces uncatchable output Date: Mon, 15 Sep 2008 19:51:14 +0200 This can be closed, because what I thought were two distinct problems has turned out to have the same cause. So this can be considered a duplicate of amd64/127276. Ldd invokes the binary and in case of a nonsensical elf-brand the kernel (at least that is my suspect) posts a message on the terminal. The workaround is to only run ldd on FreeBSD binaries. The safe solution, would in my opinion, be a check weather the binary uses the FreeBSD linker, but this discussion can remain in amd64/127276. From owner-freebsd-amd64@FreeBSD.ORG Mon Sep 15 19:28:07 2008 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 511F01065671 for ; Mon, 15 Sep 2008 19:28:07 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (bigknife-pt.tunnel.tserv9.chi1.ipv6.he.net [IPv6:2001:470:1f10:75::2]) by mx1.freebsd.org (Postfix) with ESMTP id ADD558FC20 for ; Mon, 15 Sep 2008 19:28:06 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from localhost.corp.yahoo.com (john@localhost [IPv6:::1]) (authenticated bits=0) by server.baldwin.cx (8.14.2/8.14.2) with ESMTP id m8FJRe5X082601; Mon, 15 Sep 2008 15:27:41 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: Dominic Fandrey Date: Mon, 15 Sep 2008 10:47:12 -0400 User-Agent: KMail/1.9.7 References: <200809111640.m8BGe4PX012172@freefall.freebsd.org> <200809111637.54863.jhb@freebsd.org> <48CD20CB.3040706@bsdforen.de> In-Reply-To: <48CD20CB.3040706@bsdforen.de> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200809151047.12396.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [IPv6:::1]); Mon, 15 Sep 2008 15:27:41 -0400 (EDT) X-Virus-Scanned: ClamAV 0.93.1/8249/Mon Sep 15 12:31:36 2008 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.1 required=4.2 tests=BAYES_00, DATE_IN_PAST_03_06, NO_RELAYS autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: freebsd-amd64@freebsd.org Subject: Re: amd64/127276: ldd invokes linux yes X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Sep 2008 19:28:07 -0000 On Sunday 14 September 2008 10:33:47 am Dominic Fandrey wrote: > John Baldwin wrote: > > FreeBSD binaries from various releases have been branded in different ways. I > > would consider it more of a user error to run ldd on a Linux binary. :) You > > could maybe add a "IMPLEMENTATION NOTES" section to the manpage that explains > > how it works and why it will execute any binary using a different runtime > > linker. > > > > Well, documenting it is much better than the current state. Though in my > opinion it doesn't matter to the user how it works, but what one expects the > program to do. And the current behaviour is not what I expected. > > Would you instead accept a patch from me that does a compatibility check and > bails out if the binary does not use the FreeBSD linker? It can be hard to determine that. What happens is that each ELF binary includes a path to its interpreter (i.e. the runtime linker). For FreeBSD binaries this can be either /usr/libexec/ld-elf.so.1 or /libexec/ld-elf.so.1 or the a.out paths (/usr/libexec/ld.so.1 I think). In the kernel, ABI modules hook into exec and when they see a binary they can handle, they can choose to overwrite the interpreter path to point it to somewhere else (e.g. the Linux ABI uses a path under /compat/linux instead, and the 'freebsd32' ABI on amd64 uses /libexec/ld-elf32.so.1). Any ELF binary that uses one of the two ld-elf.so.1 (or ld-elf32.so.1) paths will use the FreeBSD runtime linker, regardless of which "OS" the binary is targeted for. You could maybe hardcode the list of interpreter strings to check for, but that wouldn't be completely foolproof. You could have an ABI that is fine with using the FreeBSD linker even though its native "OS" uses a different interpreter path (though that is unlikely). In that case the kernel module would be rewriting the interpreter path to be the FreeBSD ld-elf, but ldd would have no clue. > The "IMPLEMENTATION NOTES" would still be nice to have, though. It's always > a nice read to get an idea on how something works. And I find code much > easier to decipher if I already know how it's supposed to do something. At > least much easier than the opposite way, trying to glimpse how something > works from the code. > > Regards > -- John Baldwin From owner-freebsd-amd64@FreeBSD.ORG Mon Sep 15 19:52:36 2008 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 05BBE106564A; Mon, 15 Sep 2008 19:52:36 +0000 (UTC) (envelope-from kamikaze@bsdforen.de) Received: from mail.bsdforen.de (bsdforen.de [212.204.60.79]) by mx1.freebsd.org (Postfix) with ESMTP id B42378FC12; Mon, 15 Sep 2008 19:52:35 +0000 (UTC) (envelope-from kamikaze@bsdforen.de) Received: from mobileKamikaze.norad (unknown [92.116.180.83]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.bsdforen.de (Postfix) with ESMTP id 213BD8A0129; Mon, 15 Sep 2008 21:52:12 +0200 (CEST) Message-ID: <48CEBCE4.5070204@bsdforen.de> Date: Mon, 15 Sep 2008 21:52:04 +0200 From: Dominic Fandrey User-Agent: Thunderbird 2.0.0.16 (X11/20080810) MIME-Version: 1.0 To: John Baldwin References: <200809111640.m8BGe4PX012172@freefall.freebsd.org> <200809111637.54863.jhb@freebsd.org> <48CD20CB.3040706@bsdforen.de> <200809151047.12396.jhb@freebsd.org> In-Reply-To: <200809151047.12396.jhb@freebsd.org> X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Mon, 15 Sep 2008 20:09:55 +0000 Cc: freebsd-amd64@freebsd.org Subject: Re: amd64/127276: ldd invokes linux yes X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Sep 2008 19:52:36 -0000 John Baldwin wrote: > On Sunday 14 September 2008 10:33:47 am Dominic Fandrey wrote: >> John Baldwin wrote: >>> FreeBSD binaries from various releases have been branded in different > ways. I >>> would consider it more of a user error to run ldd on a Linux binary. :) > You >>> could maybe add a "IMPLEMENTATION NOTES" section to the manpage that > explains >>> how it works and why it will execute any binary using a different runtime >>> linker. >>> >> Well, documenting it is much better than the current state. Though in my >> opinion it doesn't matter to the user how it works, but what one expects the >> program to do. And the current behaviour is not what I expected. >> >> Would you instead accept a patch from me that does a compatibility check and >> bails out if the binary does not use the FreeBSD linker? > > It can be hard to determine that. What happens is that each ELF binary > includes a path to its interpreter (i.e. the runtime linker). For FreeBSD > binaries this can be either /usr/libexec/ld-elf.so.1 or /libexec/ld-elf.so.1 > or the a.out paths (/usr/libexec/ld.so.1 I think). In the kernel, ABI > modules hook into exec and when they see a binary they can handle, they can > choose to overwrite the interpreter path to point it to somewhere else (e.g. > the Linux ABI uses a path under /compat/linux instead, and the 'freebsd32' > ABI on amd64 uses /libexec/ld-elf32.so.1). Any ELF binary that uses one of > the two ld-elf.so.1 (or ld-elf32.so.1) paths will use the FreeBSD runtime > linker, regardless of which "OS" the binary is targeted for. You could maybe > hardcode the list of interpreter strings to check for, but that wouldn't be > completely foolproof. You could have an ABI that is fine with using the > FreeBSD linker even though its native "OS" uses a different interpreter path > (though that is unlikely). In that case the kernel module would be rewriting > the interpreter path to be the FreeBSD ld-elf, but ldd would have no clue. > I wanted to look into the file and readelf tools to check how they do it. I'm using readelf to avoid calling ldd when inappropriate and I think it's reliable, so there aught to be a way. I'm kinda stressed, but I'm going to look into it in a couple of weeks. If it doesn't pay off. Well, I'm all for the implementation notes. From owner-freebsd-amd64@FreeBSD.ORG Mon Sep 15 21:45:20 2008 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 77F761065679; Mon, 15 Sep 2008 21:45:20 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 4C7838FC12; Mon, 15 Sep 2008 21:45:20 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m8FLjKOR078381; Mon, 15 Sep 2008 21:45:20 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m8FLjKek078377; Mon, 15 Sep 2008 21:45:20 GMT (envelope-from linimon) Date: Mon, 15 Sep 2008 21:45:20 GMT Message-Id: <200809152145.m8FLjKek078377@freefall.freebsd.org> To: kamikaze@bsdforen.de, linimon@FreeBSD.org, freebsd-amd64@FreeBSD.org From: linimon@FreeBSD.org X-Mailman-Approved-At: Mon, 15 Sep 2008 22:33:01 +0000 Cc: Subject: Re: amd64/127275: ldd(1) produces uncatchable output X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Sep 2008 21:45:20 -0000 Synopsis: ldd(1) produces uncatchable output State-Changed-From-To: open->closed State-Changed-By: linimon State-Changed-When: Mon Sep 15 21:45:01 UTC 2008 State-Changed-Why: See amd64/127276. http://www.freebsd.org/cgi/query-pr.cgi?pr=127275 From owner-freebsd-amd64@FreeBSD.ORG Tue Sep 16 02:54:16 2008 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5E99D106567D; Tue, 16 Sep 2008 02:54:16 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 356D88FC08; Tue, 16 Sep 2008 02:54:16 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m8G2sGRP006778; Tue, 16 Sep 2008 02:54:16 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m8G2sGnk006774; Tue, 16 Sep 2008 02:54:16 GMT (envelope-from linimon) Date: Tue, 16 Sep 2008 02:54:16 GMT Message-Id: <200809160254.m8G2sGnk006774@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-amd64@FreeBSD.org From: linimon@FreeBSD.org X-Mailman-Approved-At: Tue, 16 Sep 2008 03:00:02 +0000 Cc: Subject: Re: amd64/127397: [amd64] 32bit application on FreeBSD-6.3 amd64 gets SIGBUS X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Sep 2008 02:54:16 -0000 Old Synopsis: 32bit application on FreeBSD-6.3 amd64 gets SIGBUS New Synopsis: [amd64] 32bit application on FreeBSD-6.3 amd64 gets SIGBUS Responsible-Changed-From-To: freebsd-bugs->freebsd-amd64 Responsible-Changed-By: linimon Responsible-Changed-When: Tue Sep 16 02:53:06 UTC 2008 Responsible-Changed-Why: With a little bit of hesitation, move this one over to the amd64 category, in hopes that it will be a little more high-profile there. http://www.freebsd.org/cgi/query-pr.cgi?pr=127397 From owner-freebsd-amd64@FreeBSD.ORG Tue Sep 16 02:56:38 2008 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2F534106566C; Tue, 16 Sep 2008 02:56:38 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 065948FC0A; Tue, 16 Sep 2008 02:56:38 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m8G2ubqh006852; Tue, 16 Sep 2008 02:56:37 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m8G2ub2b006848; Tue, 16 Sep 2008 02:56:37 GMT (envelope-from linimon) Date: Tue, 16 Sep 2008 02:56:37 GMT Message-Id: <200809160256.m8G2ub2b006848@freefall.freebsd.org> To: kamikaze@bsdforen.de, linimon@FreeBSD.org, freebsd-amd64@FreeBSD.org From: linimon@FreeBSD.org X-Mailman-Approved-At: Tue, 16 Sep 2008 03:13:09 +0000 Cc: Subject: Re: amd64/127276: ldd(1) invokes linux yes X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Sep 2008 02:56:38 -0000 Synopsis: ldd(1) invokes linux yes State-Changed-From-To: open->suspended State-Changed-By: linimon State-Changed-When: Tue Sep 16 02:55:49 UTC 2008 State-Changed-Why: As noted in the feedback trail, the fix is not as obvious as it first might appear. Mark this as 'suspended' for now to note that although we understand the problem, it is going to need more research. http://www.freebsd.org/cgi/query-pr.cgi?pr=127276 From owner-freebsd-amd64@FreeBSD.ORG Tue Sep 16 06:23:15 2008 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 998171065672 for ; Tue, 16 Sep 2008 06:23:15 +0000 (UTC) (envelope-from scott.gasch@gmail.com) Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.227]) by mx1.freebsd.org (Postfix) with ESMTP id 476CB8FC26 for ; Tue, 16 Sep 2008 06:23:15 +0000 (UTC) (envelope-from scott.gasch@gmail.com) Received: by wx-out-0506.google.com with SMTP id s17so1051768wxc.7 for ; Mon, 15 Sep 2008 23:23:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type; bh=ZFtP6xYGD3DDa/pYNremOsW1HNyXmqCp09waKHGe9V8=; b=l6KcTlVo6Ee0HarGrhmy6J1RgrYKezaisieTZamYRgCM5oQO08Vi08BaCtp6E1FONQ Ynzos0iOp4YudlB8gcup3ya2o2n6g/TzqQ/DYhYMtocxPdqXm8Xdr9VHRRu2vjGIsujM YLeZ2fFXTU0Pgo15gGukszPCOPfKuSmVZZLOg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=P3Lu2JsQtGvXHv+Q0CAfVcu1SsLBL/8DBU8wb3WpYyJBvOyqfLWej3pZS6lxFsF6Up F+q2/SvQwJJr72WZD599BCsSbrPK1o4BeXaYL22w+fNfC/iBa86FEl4BjcgbleUh+cLe ZaqTp6uQqkMmhkpApOAWCr0uZoNDHpzKRVlJ8= Received: by 10.70.26.8 with SMTP id 8mr719709wxz.13.1221544658054; Mon, 15 Sep 2008 22:57:38 -0700 (PDT) Received: by 10.70.60.3 with HTTP; Mon, 15 Sep 2008 22:57:38 -0700 (PDT) Message-ID: Date: Mon, 15 Sep 2008 22:57:38 -0700 From: "Scott Gasch" To: freebsd-amd64@freebsd.org MIME-Version: 1.0 X-Mailman-Approved-At: Tue, 16 Sep 2008 11:27:24 +0000 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: irq19 interrupt storm? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Sep 2008 06:23:15 -0000 Hi, I'm running freebsd 7.0-RELEASE-p4 on a 4-core amd64 box. Nearly 100% of 1 cpu is constantly being used handling irq19: uhci4 interrupts. This seems to happen both with and without any USB devices plugged in: vmstat -i interrupt total rate irq1: atkbd0 5 0 irq6: fdc0 1 0 irq17: mskc0 dc0 1180547 18 irq18: skc0 uhci2* 163250699 2512 irq19: uhci4++ 3187989508 49072 irq23: uhci3 ehci1 31 0 cpu0: timer 129208570 1988 cpu1: timer 129208457 1988 cpu2: timer 125750147 1935 cpu3: timer 125750122 1935 Total 3862338087 59452 dmesg uhci4: port 0xa400-0xa41f irq 19 at device 29.1 on pci0 uhci4: [GIANT-LOCKED] uhci4: [ITHREAD] The box runs my own kernel... but a very similar problem happens with GENERIC. The same irq (19) is firing too often and consuming nearly all of one core. But the driver that is associated with the interrupt is different -- it's fwohci0 this time: vmstat -i interrupt total rate irq6: fdc0 1 0 irq17: mskc0 dc0 313242 13 irq18: skc0 uhci2* 124475451 5540 irq19: fwohci0+++ 957875379 42638 irq23: uhci3 ehci1 1145 0 cpu0: timer 44458513 1979 cpu1: timer 44448875 1978 cpu3: timer 43393901 1931 cpu2: timer 43393921 1931 Total 1258360428 56014 This makes me start to wonder if this is not a problem with irq19 (the PIC?) and not one particular device / driver. I'm not sure how to make dig deeper here, any help greatly appreciated. I posted this to questions a while back and no one replied ;) Thx, Scott From owner-freebsd-amd64@FreeBSD.ORG Tue Sep 16 14:12:26 2008 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2F17F106566B for ; Tue, 16 Sep 2008 14:12:26 +0000 (UTC) (envelope-from gary.jennejohn@freenet.de) Received: from mout1.freenet.de (mout1.freenet.de [IPv6:2001:748:100:40::2:3]) by mx1.freebsd.org (Postfix) with ESMTP id BD3828FC14 for ; Tue, 16 Sep 2008 14:12:25 +0000 (UTC) (envelope-from gary.jennejohn@freenet.de) Received: from [195.4.92.17] (helo=7.mx.freenet.de) by mout1.freenet.de with esmtpa (ID gary.jennejohn@freenet.de) (port 25) (Exim 4.69 #65) id 1KfbHz-000813-RE; Tue, 16 Sep 2008 16:12:23 +0200 Received: from m9078.m.pppool.de ([89.49.144.120]:11142 helo=peedub.jennejohn.org) by 7.mx.freenet.de with esmtpa (ID gary.jennejohn@freenet.de) (port 25) (Exim 4.69 #65) id 1KfbHz-0005jI-JB; Tue, 16 Sep 2008 16:12:23 +0200 Date: Tue, 16 Sep 2008 16:12:22 +0200 From: Gary Jennejohn To: "Scott Gasch" Message-ID: <20080916161222.125d15f5@peedub.jennejohn.org> In-Reply-To: References: X-Mailer: Claws Mail 3.5.0 (GTK+ 2.10.14; amd64-portbld-freebsd8.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-amd64@freebsd.org Subject: Re: irq19 interrupt storm? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: gary.jennejohn@freenet.de List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Sep 2008 14:12:26 -0000 On Mon, 15 Sep 2008 22:57:38 -0700 "Scott Gasch" wrote: > Hi, > > I'm running freebsd 7.0-RELEASE-p4 on a 4-core amd64 box. Nearly 100% of > 1 cpu is constantly being used handling irq19: uhci4 interrupts. This > seems to happen both with and without any USB devices plugged in: > > vmstat -i > interrupt total rate > irq1: atkbd0 5 0 > irq6: fdc0 1 0 > irq17: mskc0 dc0 1180547 18 > irq18: skc0 uhci2* 163250699 2512 > irq19: uhci4++ 3187989508 49072 I think the ++ here indicates that two or more devices are sharing this interrupt. Try doing "grep irq.*19 /var/run/dmesg.boot" to see which ones. One of these devices could be the culprit. --- Gary Jennejohn From owner-freebsd-amd64@FreeBSD.ORG Tue Sep 16 15:04:41 2008 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 975BE106566C for ; Tue, 16 Sep 2008 15:04:41 +0000 (UTC) (envelope-from pfgshield-freebsd@yahoo.com) Received: from web32708.mail.mud.yahoo.com (web32708.mail.mud.yahoo.com [68.142.207.252]) by mx1.freebsd.org (Postfix) with SMTP id 5955F8FC16 for ; Tue, 16 Sep 2008 15:04:41 +0000 (UTC) (envelope-from pfgshield-freebsd@yahoo.com) Received: (qmail 8820 invoked by uid 60001); 16 Sep 2008 14:38:01 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=fy2tb0X4a3z4HMGdfbzmpFW8/QY2JRNvnhHywl2zk/2XCRxoVK5aTPvqLl0BS1OZyJKlkLJ7hOIJEt7d2sfINQJNF5VzqBCyhmFYJtz+w1J0IMrOqwopgZRfxsqrlGDiOhY7A/tjatwsKDLgKbPYWh8e7/UYleI0ndgiejfIzZw=; X-YMail-OSG: KsT8RakVM1l6hkTAvtzhoLN7hQ06SawP8y1Cf7Vns3X6tXPZoDBgNLYTDoQE_1PpKL0TFxUMrrta4xE.k_PLfNTxp9ogqzHr0tSlW.rQBAgbSQm5sjoVLe3.moD6.1zGAfOjwKRwnO7B6aFErNtiEdo- Received: from [190.158.44.173] by web32708.mail.mud.yahoo.com via HTTP; Tue, 16 Sep 2008 07:38:01 PDT X-Mailer: YahooMailWebService/0.7.218.2 Date: Tue, 16 Sep 2008 07:38:01 -0700 (PDT) From: Pedro Giffuni To: Peter Jeremy , freebsd-amd64@freebsd.org In-Reply-To: <20080916074657.GF15376@server.vk2pj.dyndns.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Message-ID: <790198.8149.qm@web32708.mail.mud.yahoo.com> X-Mailman-Approved-At: Tue, 16 Sep 2008 16:16:29 +0000 Cc: Oliver Fromme Subject: Re: Why VESA and DPMS are available only for i386? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pfgshield-freebsd@yahoo.com List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Sep 2008 15:04:41 -0000 (moved from -current to -amd64) --- Mar 16/9/08, Peter Jeremy ha scritto: ... > On 2008-Sep-15 13:43:31 -0700, Pedro Giffuni > wrote: > >I can't find any reference, but according to the > Wikipedia, even in long mode AMD64 is able to run 16-bit (or > 80286) protected mode applications: >=20 > AMD64 Architecture Programmer's Manual, Volume 1: > Application > Programming - No. 24592 states: > "Compatibility mode - the second submode of long mode > - allows 64-bit > operating systems to run existing 16-bit and 32-bit x86 > applications. These legacy applications run in > compatibility mode > without recompilation." >=20 Thanks! The precise link is here (sorry for the broken link): http://www.amd.com/us-en/assets/content_type/white_papers_and_tech_docs/245= 92.pdf in section 1.2.3. I guess having bios16() and bios32() would be useful for virtualized enviro= nments too. Pedro.=0A=0A__________________________________________________=0ADo You Yah= oo!?=0APoco spazio e tanto spam? Yahoo! Mail ti protegge dallo spam e ti da= tanto spazio gratuito per i tuoi file e i messaggi =0Ahttp://mail.yahoo.it= From owner-freebsd-amd64@FreeBSD.ORG Tue Sep 16 17:39:25 2008 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6214B106566B; Tue, 16 Sep 2008 17:39:25 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from fallbackmx08.syd.optusnet.com.au (fallbackmx08.syd.optusnet.com.au [211.29.132.10]) by mx1.freebsd.org (Postfix) with ESMTP id CF1A08FC0A; Tue, 16 Sep 2008 17:39:24 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail15.syd.optusnet.com.au (mail15.syd.optusnet.com.au [211.29.132.196]) by fallbackmx08.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id m8G8Kmwr007509; Tue, 16 Sep 2008 18:20:48 +1000 Received: from server.vk2pj.dyndns.org (c122-106-215-175.belrs3.nsw.optusnet.com.au [122.106.215.175]) by mail15.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id m8G8KegT013834 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 16 Sep 2008 18:20:41 +1000 X-Bogosity: Ham, spamicity=0.000000 Received: from server.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by server.vk2pj.dyndns.org (8.14.2/8.14.2) with ESMTP id m8G8Kee4045766; Tue, 16 Sep 2008 18:20:40 +1000 (EST) (envelope-from peter@server.vk2pj.dyndns.org) Received: (from peter@localhost) by server.vk2pj.dyndns.org (8.14.2/8.14.2/Submit) id m8G8KdiF045765; Tue, 16 Sep 2008 18:20:39 +1000 (EST) (envelope-from peter) Date: Tue, 16 Sep 2008 18:20:39 +1000 From: Peter Jeremy To: Chitti Nimmagadda Message-ID: <20080916082039.GX15376@server.vk2pj.dyndns.org> References: <200809160254.m8G2sGnk006774@freefall.freebsd.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="tuYRN1zEaS85jg/Y" Content-Disposition: inline In-Reply-To: <200809160254.m8G2sGnk006774@freefall.freebsd.org> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.18 (2008-05-17) Cc: freebsd-bugs@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: amd64/127397: [amd64] 32bit application on FreeBSD-6.3 amd64 gets SIGBUS X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Sep 2008 17:39:25 -0000 --tuYRN1zEaS85jg/Y Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable I can't quickly reproduce this on a roughly week old 6.4-PRERELEASE with a Turion64x2, though that system has been up for nearly 4 days. What else, if anything, is running on the system when it fails or doesn't fail? Does running lots of (especially large) processes before running your test reduce the likelihood of the failure occurring? Off the top of my head this looks like a race condition in the code that migrates i386 processes between CPUs - possibly a missing or misplaced memory barrier. Actually tracking this down is likely to be difficult. --=20 Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. --tuYRN1zEaS85jg/Y Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkjPbFcACgkQ/opHv/APuIdVtgCgwngCoUtqn0eo+eMwky6q2Xud 9IkAn2/CFsOf6j1cAe6QDIYD2Ch/X+ru =Jht8 -----END PGP SIGNATURE----- --tuYRN1zEaS85jg/Y-- From owner-freebsd-amd64@FreeBSD.ORG Tue Sep 16 23:05:03 2008 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E22701065675 for ; Tue, 16 Sep 2008 23:05:03 +0000 (UTC) (envelope-from gofda-freebsd-amd64@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.freebsd.org (Postfix) with ESMTP id 982C98FC24 for ; Tue, 16 Sep 2008 23:05:03 +0000 (UTC) (envelope-from gofda-freebsd-amd64@m.gmane.org) Received: from root by ciao.gmane.org with local (Exim 4.43) id 1KfiVl-0006Ey-S4 for freebsd-amd64@freebsd.org; Tue, 16 Sep 2008 21:55:05 +0000 Received: from www.ebasoft.com.pl ([85.237.185.105]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 16 Sep 2008 21:55:05 +0000 Received: from artur by www.ebasoft.com.pl with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 16 Sep 2008 21:55:05 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-amd64@freebsd.org From: Artur Bac Date: Tue, 16 Sep 2008 23:52:34 +0200 Organization: EBASOft Lines: 11 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7Bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: www.ebasoft.com.pl User-Agent: KNode/0.10.5 Sender: news X-Mailman-Approved-At: Tue, 16 Sep 2008 23:40:02 +0000 Subject: BSD7 MCP55 SATA AMD64 Data Corruption X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Sep 2008 23:05:04 -0000 Hello since first prerelease of BSD7 i got on disks atached to MCP55 SATA controler data corruption. One thing that is strange is that this controller works ok with 6.3 but not with 7.0 PRE, 7.0 STAB. or 7.1 PRE I tryed both schedulers without success. I got AMD64 X2 6000+ 6GB RAM and ATA and SATA 150 and 300 discs. Can anyone help ? A. From owner-freebsd-amd64@FreeBSD.ORG Wed Sep 17 07:00:06 2008 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0606A106564A for ; Wed, 17 Sep 2008 07:00:05 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id E28918FC0A for ; Wed, 17 Sep 2008 07:00:05 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m8H705u9023584 for ; Wed, 17 Sep 2008 07:00:05 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m8H705Sk023583; Wed, 17 Sep 2008 07:00:05 GMT (envelope-from gnats) Date: Wed, 17 Sep 2008 07:00:05 GMT Message-Id: <200809170700.m8H705Sk023583@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: Edwin Groothuis X-Mailman-Approved-At: Wed, 17 Sep 2008 11:22:08 +0000 Cc: Subject: Re: amd64/109584: zdump(8) doesn't work X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Edwin Groothuis List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Sep 2008 07:00:06 -0000 The following reply was made to PR amd64/109584; it has been noted by GNATS. From: Edwin Groothuis To: bug-followup@FreeBSD.org, dcrandall@simplestar.com Cc: Subject: Re: amd64/109584: zdump(8) doesn't work Date: Wed, 17 Sep 2008 16:53:17 +1000 Try Index: zdump.c =================================================================== --- zdump.c (revision 183065) +++ zdump.c (working copy) @@ -151,7 +151,9 @@ time_t hibit; struct tm tm; struct tm newtm; + int cpu32; + cpu32 = (sizeof(NULL) == 4); INITIALIZE(cuttime); #if HAVE_GETTEXT - 0 (void) setlocale(LC_MESSAGES, ""); @@ -222,9 +224,16 @@ /* ** Get lowest value of t. */ - t = hibit; - if (t > 0) /* time_t is unsigned */ - t = 0; + if (cpu32) { + t = hibit; + if (t > 0) /* time_t is unsigned */ + t = 0; + } else { + t = -2209024800; /* 1 January 1900 00:00:00 */ + cuttime = 4000000000; + cutoff = "2099"; + } + show(argv[i], t, TRUE); t += SECSPERHOUR * HOURSPERDAY; show(argv[i], t, TRUE); It won't resolve the issue, only mask it for now. The problem is that the time after 2037 is still not shown . -- Edwin Groothuis edwin@freebsd.org http://www.mavetju.org From owner-freebsd-amd64@FreeBSD.ORG Wed Sep 17 13:10:06 2008 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D15651065670 for ; Wed, 17 Sep 2008 13:10:06 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id BD11F8FC13 for ; Wed, 17 Sep 2008 13:10:06 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m8HDA60X077421 for ; Wed, 17 Sep 2008 13:10:06 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m8HDA6qh077420; Wed, 17 Sep 2008 13:10:06 GMT (envelope-from gnats) Date: Wed, 17 Sep 2008 13:10:06 GMT Message-Id: <200809171310.m8HDA6qh077420@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: Edwin Groothuis X-Mailman-Approved-At: Wed, 17 Sep 2008 14:02:52 +0000 Cc: Subject: Re: amd64/109584: [patch] zdump(8) doesn't work X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Edwin Groothuis List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Sep 2008 13:10:06 -0000 The following reply was made to PR amd64/109584; it has been noted by GNATS. From: Edwin Groothuis To: bug-followup@FreeBSD.org, dcrandall@simplestar.com Cc: Subject: Re: amd64/109584: [patch] zdump(8) doesn't work Date: Wed, 17 Sep 2008 23:01:55 +1000 Forgot the last data to be displayed. Index: zdump.c =================================================================== --- zdump.c (revision 183065) +++ zdump.c (working copy) @@ -96,6 +96,10 @@ #endif /* !defined GNUC_or_lint */ #endif /* !defined INITIALIZE */ +/* For architectures >32 bit, start at 1900 and go to 2100 */ +#define EPOCH1900 -2209024800 /* Mon Jan 1 00:00:00 EST 1900 */ +#define EPOCH2100 4102405200 /* Fri Jan 1 00:00:00 EST 2100 */ + /* ** For the benefit of GNU folk... ** `_(MSGID)' uses the current locale's message library string for MSGID. @@ -151,7 +155,9 @@ time_t hibit; struct tm tm; struct tm newtm; + int cpu32; + cpu32 = (sizeof(NULL) == 4); INITIALIZE(cuttime); #if HAVE_GETTEXT - 0 (void) setlocale(LC_MESSAGES, ""); @@ -222,9 +228,18 @@ /* ** Get lowest value of t. */ - t = hibit; - if (t > 0) /* time_t is unsigned */ - t = 0; + if (cpu32) { + t = hibit; + if (t > 0) /* time_t is unsigned */ + t = 0; + } else { + t = EPOCH1900; /* 1 January 1900 00:00:00 */ + if (cutoff == NULL) { + cuttime = EPOCH2100; + cutoff = "2099"; + } + } + show(argv[i], t, TRUE); t += SECSPERHOUR * HOURSPERDAY; show(argv[i], t, TRUE); @@ -253,9 +268,13 @@ /* ** Get highest value of t. */ - t = ~((time_t) 0); - if (t < 0) /* time_t is signed */ - t &= ~hibit; + if (cpu32) { + t = ~((time_t) 0); + if (t < 0) /* time_t is signed */ + t &= ~hibit; + } else { + t = EPOCH2100 - 1; + } t -= SECSPERHOUR * HOURSPERDAY; show(argv[i], t, TRUE); t += SECSPERHOUR * HOURSPERDAY; -- Edwin Groothuis | Personal website: http://www.mavetju.org edwin@mavetju.org | Weblog: http://www.mavetju.org/weblog/ From owner-freebsd-amd64@FreeBSD.ORG Wed Sep 17 15:00:26 2008 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CE2551065683 for ; Wed, 17 Sep 2008 15:00:26 +0000 (UTC) (envelope-from scott.gasch@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.178]) by mx1.freebsd.org (Postfix) with ESMTP id 83DCA8FC0C for ; Wed, 17 Sep 2008 15:00:26 +0000 (UTC) (envelope-from scott.gasch@gmail.com) Received: by py-out-1112.google.com with SMTP id p76so2433920pyb.10 for ; Wed, 17 Sep 2008 08:00:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type:references; bh=+aF19ViSmHUfXLh5p5AmGSznVKU2rEzaQwAq7UPEqD0=; b=JL4mCqjzvzmUMFawli7iq8ggMC7UM9lSdubIL0/Kuwzqvmkua47OdZrNrG2aBcZPeY P8sHtAErSEx6WOT12wOhMJCIricwdTXs2dFqX2buIi8PlyhyRZrkkoU0XRY4yNt2HkgQ miMlC14BZJc7ol2RhC+2d+2wSGJ/jMn3bsN8E= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:references; b=s7TWMo/daz5BazSr+k27lEjrgZzcYJIsGzCpsnCP5fbNXNUTNQIB4O6OUSg9+QrI8h +4T+vWqboBzic91+VC9aSbaWFJ9P66KJjAHu55vpx7hmtzn8cmaTN+SkdR2kocWveXRi gFK5cqno5HUOpsEmVG3U8yPb2cLzxihpZaznc= Received: by 10.114.149.2 with SMTP id w2mr2181720wad.92.1221663624638; Wed, 17 Sep 2008 08:00:24 -0700 (PDT) Received: by 10.70.60.3 with HTTP; Wed, 17 Sep 2008 08:00:24 -0700 (PDT) Message-ID: Date: Wed, 17 Sep 2008 08:00:24 -0700 From: "Scott Gasch" To: gary.jennejohn@freenet.de In-Reply-To: <20080916161222.125d15f5@peedub.jennejohn.org> MIME-Version: 1.0 References: <20080916161222.125d15f5@peedub.jennejohn.org> X-Mailman-Approved-At: Wed, 17 Sep 2008 15:27:24 +0000 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: questions@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: irq19 interrupt storm? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Sep 2008 15:00:27 -0000 You're right: atapci1, atapci2, fwohci0 and uhci4 are all sharing the same irq (19) while irqs 20, 21, 22 at least seem completely unused. Here's a dumb question: how do I fix it? I tried setting "plug and play OS" in the BIOS and then using device.hints to push different devices to different irqs. But every time I tried a new hint it seemed to be ignored. I was trying stuff like: set hint.atapci.1.irq="20" set hint ata.4.irq="20" (ata4 is a channel on atapci1) set hint fwhco.0.irq="20" etc... I also tried to move the dc driver to a new irq as a test. This was also seemingly ignored. I then tried turning "plug and play OS" off in the BIOS but I don't see anywhere to set the IRQs of the onboard SATA controllers via the menus. I'm looking for a BIOS upgrade now... any other advice? Thx, Scott On Tue, Sep 16, 2008 at 7:12 AM, Gary Jennejohn wrote: > On Mon, 15 Sep 2008 22:57:38 -0700 > "Scott Gasch" wrote: > > > Hi, > > > > I'm running freebsd 7.0-RELEASE-p4 on a 4-core amd64 box. Nearly 100% of > > 1 cpu is constantly being used handling irq19: uhci4 interrupts. This > > seems to happen both with and without any USB devices plugged in: > > > > vmstat -i > > interrupt total rate > > irq1: atkbd0 5 0 > > irq6: fdc0 1 0 > > irq17: mskc0 dc0 1180547 18 > > irq18: skc0 uhci2* 163250699 2512 > > irq19: uhci4++ 3187989508 49072 > > I think the ++ here indicates that two or more devices are sharing this > interrupt. Try doing "grep irq.*19 /var/run/dmesg.boot" to see which > ones. One of these devices could be the culprit. > > --- > Gary Jennejohn > From owner-freebsd-amd64@FreeBSD.ORG Wed Sep 17 21:18:51 2008 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C69311065680; Wed, 17 Sep 2008 21:18:51 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (bigknife-pt.tunnel.tserv9.chi1.ipv6.he.net [IPv6:2001:470:1f10:75::2]) by mx1.freebsd.org (Postfix) with ESMTP id 592C58FC1D; Wed, 17 Sep 2008 21:18:51 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from localhost.corp.yahoo.com (john@localhost [IPv6:::1]) (authenticated bits=0) by server.baldwin.cx (8.14.2/8.14.2) with ESMTP id m8HLILA0009566; Wed, 17 Sep 2008 17:18:45 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-amd64@freebsd.org Date: Wed, 17 Sep 2008 17:17:27 -0400 User-Agent: KMail/1.9.7 References: <20080916161222.125d15f5@peedub.jennejohn.org> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200809171717.27570.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [IPv6:::1]); Wed, 17 Sep 2008 17:18:45 -0400 (EDT) X-Virus-Scanned: ClamAV 0.93.1/8271/Wed Sep 17 12:58:50 2008 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.6 required=4.2 tests=AWL,BAYES_00,NO_RELAYS autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: questions@freebsd.org, Scott Gasch Subject: Re: irq19 interrupt storm? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Sep 2008 21:18:51 -0000 On Wednesday 17 September 2008 11:00:24 am Scott Gasch wrote: > You're right: atapci1, atapci2, fwohci0 and uhci4 are all sharing the same > irq (19) while irqs 20, 21, 22 at least seem completely unused. Here's a > dumb question: how do I fix it? I tried setting "plug and play OS" in the > BIOS and then using device.hints to push different devices to different > irqs. But every time I tried a new hint it seemed to be ignored. I was > trying stuff like: > > set hint.atapci.1.irq="20" > set hint ata.4.irq="20" (ata4 is a channel on atapci1) > set hint fwhco.0.irq="20" > etc... > > > I also tried to move the dc driver to a new irq as a test. This was also > seemingly ignored. > > I then tried turning "plug and play OS" off in the BIOS but I don't see > anywhere to set the IRQs of the onboard SATA controllers via the menus. I'm > looking for a BIOS upgrade now... any other advice? Unfortunately you can't really move PCI IRQs around. You can read about more of the gritty details here: http://people.freebsd.org/~jhb/papers/bsdcan/2007/ You might be able to shuffle some IRQs around using 'hw.pciX.Y.INTA.irq' tunables. Probably you have a device driver whose interrupt handler isn't handling some condition. I would suspect ata as it's interrupt handler is rather simplistic with no chipset-specific hooks, and I've seen several reports of interrupt storms with ata(4) recently. > Thx, > Scott > > > On Tue, Sep 16, 2008 at 7:12 AM, Gary Jennejohn > wrote: > > > On Mon, 15 Sep 2008 22:57:38 -0700 > > "Scott Gasch" wrote: > > > > > Hi, > > > > > > I'm running freebsd 7.0-RELEASE-p4 on a 4-core amd64 box. Nearly 100% of > > > 1 cpu is constantly being used handling irq19: uhci4 interrupts. This > > > seems to happen both with and without any USB devices plugged in: > > > > > > vmstat -i > > > interrupt total rate > > > irq1: atkbd0 5 0 > > > irq6: fdc0 1 0 > > > irq17: mskc0 dc0 1180547 18 > > > irq18: skc0 uhci2* 163250699 2512 > > > irq19: uhci4++ 3187989508 49072 > > > > I think the ++ here indicates that two or more devices are sharing this > > interrupt. Try doing "grep irq.*19 /var/run/dmesg.boot" to see which > > ones. One of these devices could be the culprit. > > > > --- > > Gary Jennejohn > > > _______________________________________________ > freebsd-amd64@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 > To unsubscribe, send any mail to "freebsd-amd64-unsubscribe@freebsd.org" > -- John Baldwin From owner-freebsd-amd64@FreeBSD.ORG Wed Sep 17 21:50:02 2008 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 376CA1065689 for ; Wed, 17 Sep 2008 21:50:02 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 13CDD8FC24 for ; Wed, 17 Sep 2008 21:50:02 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m8HLo1eH020658 for ; Wed, 17 Sep 2008 21:50:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m8HLo1de020657; Wed, 17 Sep 2008 21:50:01 GMT (envelope-from gnats) Resent-Date: Wed, 17 Sep 2008 21:50:01 GMT Resent-Message-Id: <200809172150.m8HLo1de020657@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-amd64@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Miks Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E4114106567B for ; Wed, 17 Sep 2008 21:46:26 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (www.freebsd.org [IPv6:2001:4f8:fff6::21]) by mx1.freebsd.org (Postfix) with ESMTP id D27A18FC24 for ; Wed, 17 Sep 2008 21:46:26 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.14.2/8.14.2) with ESMTP id m8HLkPbB049542 for ; Wed, 17 Sep 2008 21:46:25 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.14.2/8.14.1/Submit) id m8HLkPmJ049541; Wed, 17 Sep 2008 21:46:25 GMT (envelope-from nobody) Message-Id: <200809172146.m8HLkPmJ049541@www.freebsd.org> Date: Wed, 17 Sep 2008 21:46:25 GMT From: Miks To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.1 X-Mailman-Approved-At: Wed, 17 Sep 2008 23:08:51 +0000 Cc: Subject: amd64/127451: incorrect load on quad core X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Sep 2008 21:50:02 -0000 >Number: 127451 >Category: amd64 >Synopsis: incorrect load on quad core >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Wed Sep 17 21:50:01 UTC 2008 >Closed-Date: >Last-Modified: >Originator: Miks >Release: 7.0 release amd64 >Organization: skynet >Environment: FreeBSD sun 7.0-RELEASE-p4 FreeBSD 7.0-RELEASE-p4 #4: Thu Sep 11 22:08:16 EEST 2008 miks@sun:/usr/obj/usr/src/sys/SUN amd64 >Description: I got load average around 0.5, and top show something like this "1021 processes: 1 running, 1020 sleeping CPU states: 4.9% user, 0.0% nice, 3.6% system, 0.9% interrupt, 90.6% idle" - this all is ok. then once in 2-5 minutes, there for 2-3 seconds are: "1020 processes:67 running, 912 sleeping, 1 zombie, 40 lock CPU states: 3.0% user, 0.0% nice, 96.7% system, 0.3% interrupt, 0.0% idle" - this is the problem. after this load average is 20-30 and dropping in 2-3min to 0.5. during this time system is very slow. even ssh session is freezing. most of processes are fastcgi/php, so there is not one big resource hungry process. found similar problem here: http://unix.derkeiler.com/Mailing-Lists/FreeBSD/stable/2007-11/msg00551.html >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-amd64@FreeBSD.ORG Thu Sep 18 19:10:06 2008 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9C3D01065681 for ; Thu, 18 Sep 2008 19:10:06 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 8AA858FC14 for ; Thu, 18 Sep 2008 19:10:06 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m8IJA4Wi059244 for ; Thu, 18 Sep 2008 19:10:04 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m8IJA4OQ059243; Thu, 18 Sep 2008 19:10:04 GMT (envelope-from gnats) Date: Thu, 18 Sep 2008 19:10:04 GMT Message-Id: <200809181910.m8IJA4OQ059243@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: miks@skynet.lv X-Mailman-Approved-At: Thu, 18 Sep 2008 19:38:42 +0000 Cc: Subject: Re: amd64/127451: top(1): incorrect load shown on quad core X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: miks@skynet.lv List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Sep 2008 19:10:06 -0000 The following reply was made to PR amd64/127451; it has been noted by GNATS. From: miks@skynet.lv To: bug-followup@FreeBSD.org, miks@skynet.lv Cc: Subject: Re: amd64/127451: top(1): incorrect load shown on quad core Date: Thu, 18 Sep 2008 21:50:06 +0300 problem name is not correct - "top(1): incorrect load shown on quad core" I believe with top command there everything is ok. Problem is that after 2 or 3 minutes system suddenly got ~60 running proceses, ~40 locks and cpu is ~90% busy system, not user. system is unusable. old dual core system was faster and more stable than brand new dual quad-core cpu with 16gb ram. So problem by the fact is totally different, and I can't figure where and what is responsible for new, powerful server acting as low-budget desktop computer. From owner-freebsd-amd64@FreeBSD.ORG Thu Sep 18 19:30:04 2008 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3B7D5106564A for ; Thu, 18 Sep 2008 19:30:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 11AA88FC1F for ; Thu, 18 Sep 2008 19:30:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m8IJU3RT061197 for ; Thu, 18 Sep 2008 19:30:03 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m8IJU3vm061196; Thu, 18 Sep 2008 19:30:03 GMT (envelope-from gnats) Date: Thu, 18 Sep 2008 19:30:03 GMT Message-Id: <200809181930.m8IJU3vm061196@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: miks@skynet.lv X-Mailman-Approved-At: Thu, 18 Sep 2008 19:44:01 +0000 Cc: Subject: Re: amd64/127451: top(1): incorrect load shown on quad core X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: miks@skynet.lv List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Sep 2008 19:30:04 -0000 The following reply was made to PR amd64/127451; it has been noted by GNATS. From: miks@skynet.lv To: bug-followup@FreeBSD.org, miks@skynet.lv Cc: Subject: Re: amd64/127451: top(1): incorrect load shown on quad core Date: Thu, 18 Sep 2008 22:22:56 +0300 to understand better, this happen once in 2-3 minutes: " last pid: 98618; load averages: 29.81, 17.28, 15.03 up 6+23:13:22 22:15:50 1234 processes:159 running, 986 sleeping, 64 zombie, 25 lock CPU states: 1.1% user, 0.0% nice, 98.8% system, 0.0% interrupt, 0.0% idle " before 3 sec in this situation there was only 1 process running and load average was around 1. is it somehow related with lockmgr? From owner-freebsd-amd64@FreeBSD.ORG Thu Sep 18 21:40:01 2008 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DA59C106564A for ; Thu, 18 Sep 2008 21:40:01 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id B579A8FC1C for ; Thu, 18 Sep 2008 21:40:01 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m8ILe1K8072779 for ; Thu, 18 Sep 2008 21:40:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m8ILe1Mg072778; Thu, 18 Sep 2008 21:40:01 GMT (envelope-from gnats) Resent-Date: Thu, 18 Sep 2008 21:40:01 GMT Resent-Message-Id: <200809182140.m8ILe1Mg072778@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-amd64@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Torbjorn Granlund Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B2720106567D for ; Thu, 18 Sep 2008 21:38:07 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (www.freebsd.org [IPv6:2001:4f8:fff6::21]) by mx1.freebsd.org (Postfix) with ESMTP id A01A88FC1C for ; Thu, 18 Sep 2008 21:38:07 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.14.2/8.14.2) with ESMTP id m8ILc7Pa083869 for ; Thu, 18 Sep 2008 21:38:07 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.14.2/8.14.1/Submit) id m8ILc75d083868; Thu, 18 Sep 2008 21:38:07 GMT (envelope-from nobody) Message-Id: <200809182138.m8ILc75d083868@www.freebsd.org> Date: Thu, 18 Sep 2008 21:38:07 GMT From: Torbjorn Granlund To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.1 X-Mailman-Approved-At: Thu, 18 Sep 2008 21:45:10 +0000 Cc: Subject: amd64/127484: Drift problem with FreeBSD 7.0 and 7.1 PRERELEASE X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Sep 2008 21:40:02 -0000 >Number: 127484 >Category: amd64 >Synopsis: Drift problem with FreeBSD 7.0 and 7.1 PRERELEASE >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Sep 18 21:40:01 UTC 2008 >Closed-Date: >Last-Modified: >Originator: Torbjorn Granlund >Release: 7.0, 7.1 PRERELEASE >Organization: >Environment: FreeBSD carlos.gmplib.org 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #0: Tue Sep 16 22:32:59 CEST 2008 root@carlos.gmplib.org:/usr/src/sys/amd64/compile/GENERIC amd64 >Description: The clock on this system goes several percent too slowly. I have tried all available timecounters (the default HPET, as well as ACPI-safe and i8254. TSC strangely says (-100) which might suggest it is not reliable on this system. The clock drift problem seems to be exactly the same with all timecounters. I have also tried setting kern.hz to 100 (in /boot/loader.conf) without any improvements. kern.timecounter.choice: TSC(-100) HPET(900) ACPI-safe(850) i8254(0) dummy(-1000000) Motherboard: ASUS M3A78-EMH HDMI CPU: AMD Phenom 9750 (2.4 GHz x 4) I have run FreeBSD for 13 years on countless systems and have never experienced clock drift problems with it. Could this be a hardware problem? >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-amd64@FreeBSD.ORG Thu Sep 18 22:36:25 2008 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E5E481065678; Thu, 18 Sep 2008 22:36:25 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (bigknife-pt.tunnel.tserv9.chi1.ipv6.he.net [IPv6:2001:470:1f10:75::2]) by mx1.freebsd.org (Postfix) with ESMTP id 669018FC21; Thu, 18 Sep 2008 22:36:25 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from localhost.corp.yahoo.com (john@localhost [IPv6:::1]) (authenticated bits=0) by server.baldwin.cx (8.14.2/8.14.2) with ESMTP id m8IMaI7L021218; Thu, 18 Sep 2008 18:36:19 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-amd64@freebsd.org Date: Thu, 18 Sep 2008 17:48:39 -0400 User-Agent: KMail/1.9.7 References: <200809171717.27570.jhb@freebsd.org> In-Reply-To: <200809171717.27570.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200809181748.40142.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [IPv6:::1]); Thu, 18 Sep 2008 18:36:19 -0400 (EDT) X-Virus-Scanned: ClamAV 0.93.1/8284/Thu Sep 18 17:54:57 2008 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.5 required=4.2 tests=AWL,BAYES_00,NO_RELAYS autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: questions@freebsd.org, Scott Gasch Subject: Re: irq19 interrupt storm? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Sep 2008 22:36:26 -0000 On Wednesday 17 September 2008 05:17:27 pm John Baldwin wrote: > On Wednesday 17 September 2008 11:00:24 am Scott Gasch wrote: > > You're right: atapci1, atapci2, fwohci0 and uhci4 are all sharing the same > > irq (19) while irqs 20, 21, 22 at least seem completely unused. Here's a > > dumb question: how do I fix it? I tried setting "plug and play OS" in the > > BIOS and then using device.hints to push different devices to different > > irqs. But every time I tried a new hint it seemed to be ignored. I was > > trying stuff like: > > > > set hint.atapci.1.irq="20" > > set hint ata.4.irq="20" (ata4 is a channel on atapci1) > > set hint fwhco.0.irq="20" > > etc... > > > > > > I also tried to move the dc driver to a new irq as a test. This was also > > seemingly ignored. > > > > I then tried turning "plug and play OS" off in the BIOS but I don't see > > anywhere to set the IRQs of the onboard SATA controllers via the menus. I'm > > looking for a BIOS upgrade now... any other advice? > > Unfortunately you can't really move PCI IRQs around. You can read about more > of the gritty details here: > > http://people.freebsd.org/~jhb/papers/bsdcan/2007/ > > You might be able to shuffle some IRQs around using 'hw.pciX.Y.INTA.irq' > tunables. Gah, wrong tunables. These devices are on PCI link devices, so you'd need to do something like 'hw.pci.LNKA.irq' (where LNKA is the name of the link device in the ACPI namespace). Verbose boot messages (boot -v) can tell you which link device you PCI devices are using. -- John Baldwin From owner-freebsd-amd64@FreeBSD.ORG Fri Sep 19 01:58:52 2008 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A6836106564A; Fri, 19 Sep 2008 01:58:52 +0000 (UTC) (envelope-from edwin@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 7C0318FC12; Fri, 19 Sep 2008 01:58:52 +0000 (UTC) (envelope-from edwin@FreeBSD.org) Received: from freefall.freebsd.org (edwin@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m8J1wqpO092587; Fri, 19 Sep 2008 01:58:52 GMT (envelope-from edwin@freefall.freebsd.org) Received: (from edwin@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m8J1wqon092583; Fri, 19 Sep 2008 01:58:52 GMT (envelope-from edwin) Date: Fri, 19 Sep 2008 01:58:52 GMT Message-Id: <200809190158.m8J1wqon092583@freefall.freebsd.org> To: edwin@FreeBSD.org, freebsd-amd64@FreeBSD.org, edwin@FreeBSD.org From: edwin@FreeBSD.org X-Mailman-Approved-At: Fri, 19 Sep 2008 05:07:40 +0000 Cc: Subject: Re: amd64/109584: [patch] zdump(8) doesn't work X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Sep 2008 01:58:52 -0000 Synopsis: [patch] zdump(8) doesn't work Responsible-Changed-From-To: freebsd-amd64->edwin Responsible-Changed-By: edwin Responsible-Changed-When: Fri Sep 19 01:58:38 UTC 2008 Responsible-Changed-Why: Grab for handling with mentor. http://www.freebsd.org/cgi/query-pr.cgi?pr=109584 From owner-freebsd-amd64@FreeBSD.ORG Fri Sep 19 06:30:01 2008 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6990F106566B for ; Fri, 19 Sep 2008 06:30:01 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 44AC48FC16 for ; Fri, 19 Sep 2008 06:30:01 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m8J6U1eM019777 for ; Fri, 19 Sep 2008 06:30:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m8J6U1Gp019776; Fri, 19 Sep 2008 06:30:01 GMT (envelope-from gnats) Resent-Date: Fri, 19 Sep 2008 06:30:01 GMT Resent-Message-Id: <200809190630.m8J6U1Gp019776@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-amd64@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Alex Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E29D0106564A for ; Fri, 19 Sep 2008 06:26:17 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (www.freebsd.org [IPv6:2001:4f8:fff6::21]) by mx1.freebsd.org (Postfix) with ESMTP id D03408FC0A for ; Fri, 19 Sep 2008 06:26:17 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.14.2/8.14.2) with ESMTP id m8J6QHM6020603 for ; Fri, 19 Sep 2008 06:26:17 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.14.2/8.14.1/Submit) id m8J6QGfp020602; Fri, 19 Sep 2008 06:26:16 GMT (envelope-from nobody) Message-Id: <200809190626.m8J6QGfp020602@www.freebsd.org> Date: Fri, 19 Sep 2008 06:26:16 GMT From: Alex To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.1 X-Mailman-Approved-At: Fri, 19 Sep 2008 11:21:28 +0000 Cc: Subject: amd64/127492: System hang on ZFS input-output X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Sep 2008 06:30:01 -0000 >Number: 127492 >Category: amd64 >Synopsis: System hang on ZFS input-output >Confidential: no >Severity: critical >Priority: high >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Sep 19 06:30:00 UTC 2008 >Closed-Date: >Last-Modified: >Originator: Alex >Release: 7.1 >Organization: JSC "P.T.T." >Environment: FreeBSD x6.line1.ru 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #1: Mon Sep 15 11:27:50 MSD 2008 root@x6.line1.ru:/usr/obj/usr/src/sys/KMIST amd64 >Description: We use RAID controller Smart Array P400 (driver ciss)in our system. Five hardware stripe arrays was combined into raidz (zfs). #df -h coolpool 6.7T 1.7T 5.0T 25% /www /www - used by proftpd and httpd daemons System is working properly during some period of time(day-week), but processes which are accessing to the ZFS volume turn into "D uninterruptible wait" state and hang on. www 86576 0.0 0.5 121560 19556 ?? D 7:37AM 0:00.00 /usr/local/sbin/httpd -DNOHTTPACCEPT www 86577 0.0 0.5 121560 19556 ?? D 7:37AM 0:00.00 /usr/local/sbin/httpd -DNOHTTPACCEPT www 86578 0.0 0.5 121560 19556 ?? D 7:38AM 0:00.00 /usr/local/sbin/httpd -DNOHTTPACCEPT Any requests to the ZFS volume cause the process hang. "Reboot"-command is executed normally up to the moment when the system produce "syncing disks" and hang also. P.S. 7.0 - release is working in the same way. >How-To-Repeat: We don't know. Possible high disc load. >Fix: Hardware reset. O_o >Release-Note: >Audit-Trail: >Unformatted: