From owner-freebsd-bugs@FreeBSD.ORG Sun Mar 7 01:36:30 2004 Return-Path: Delivered-To: freebsd-bugs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 12AC516A4CE; Sun, 7 Mar 2004 01:36:30 -0800 (PST) Received: from tog.net (tog.net [216.89.226.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id E0DE743D2F; Sun, 7 Mar 2004 01:36:29 -0800 (PST) (envelope-from ender@tog.net) Received: by tog.net (Postfix, from userid 96) id 4E84129B620; Sun, 7 Mar 2004 04:36:29 -0500 (EST) Received: from tog.net (host-216-89-225-139.terranova.net [216.89.225.139]) by tog.net (Postfix) with ESMTP id 85F0629B61B; Sun, 7 Mar 2004 04:36:27 -0500 (EST) Message-ID: <404AEE63.8030602@tog.net> Date: Sun, 07 Mar 2004 04:41:55 -0500 From: Ender User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6b) Gecko/20031205 Thunderbird/0.4 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-security@freebsd.org, freebsd-bugs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 2.63-terranovanet_v5 (2004-01-11) on spamslapper.terranova.net X-Spam-Level: X-Spam-Status: No, hits=0.1 required=7.5 tests=AWL autolearn=no version=2.63-terranovanet_v5 Subject: strace hard lock X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Mar 2004 09:36:30 -0000 Topic: strace casues hardlock. no kernel panic. userland tool Category: kernel Program: strace Affects: FreeBSD releases 5.x and later. problem: When a normal user (or root user) users strace on certain binarys, the system will hardlock up, with no kernel panic. (numlock doesnt turn on and off, no ssh or console access). Im using strace from the ports collection. The crash seemed to occure when exiting strace from a running program, Also the crash would not happen 100% of the time leaving a program, but it never took more than 3 times to casue the crash. Repeatable: i repeated this bug on 2 different systems both were SMP. 2 procs. I have not been able to test on a UP system yet. The main program i am running, also the easyest to casue the crash can be found at the following links: http://www.pvpgn.de/files.aspx?file=pvpgn-1.6.0beta.tar.bz2 http://www.pvpgn.de/files.aspx?file=pvpgn-1.6.0beta.tar.gz From owner-freebsd-bugs@FreeBSD.ORG Sun Mar 7 01:39:38 2004 Return-Path: Delivered-To: freebsd-bugs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BFE0016A4CE for ; Sun, 7 Mar 2004 01:39:38 -0800 (PST) Received: from tog.net (tog.net [216.89.226.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9959D43D1F for ; Sun, 7 Mar 2004 01:39:38 -0800 (PST) (envelope-from ender@tog.net) Received: by tog.net (Postfix, from userid 96) id 4CA0C29B620; Sun, 7 Mar 2004 04:39:38 -0500 (EST) Received: from tog.net (host-216-89-225-139.terranova.net [216.89.225.139]) by tog.net (Postfix) with ESMTP id A334829B60F for ; Sun, 7 Mar 2004 04:39:36 -0500 (EST) Message-ID: <404AEF20.7090506@tog.net> Date: Sun, 07 Mar 2004 04:45:04 -0500 From: Ender User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6b) Gecko/20031205 Thunderbird/0.4 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-bugs@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 2.63-terranovanet_v5 (2004-01-11) on spamslapper.terranova.net X-Spam-Level: X-Spam-Status: No, hits=0.1 required=7.5 tests=AWL,BAYES_50 autolearn=no version=2.63-terranovanet_v5 Subject: bad syntax in ipfw casues kernel panic. X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Mar 2004 09:39:38 -0000 ipfw queue 1 config pipe 1 weight 140 queue 1024Kbytes using the above command to make a weighted queue using a number higher than 100 causes a kernel panic. effect: freebsd 5.2.1 maybe more From owner-freebsd-bugs@FreeBSD.ORG Sun Mar 7 02:05:54 2004 Return-Path: Delivered-To: freebsd-bugs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 15F3916A4CE for ; Sun, 7 Mar 2004 02:05:54 -0800 (PST) Received: from amsfep12-int.chello.nl (amsfep12-int.chello.nl [213.46.243.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2716743D31 for ; Sun, 7 Mar 2004 02:05:51 -0800 (PST) (envelope-from dodell@sitetronics.com) Received: from sitetronics.com ([213.46.139.145]) by amsfep12-int.chello.nl (InterMail vM.6.00.05.02 201-2115-109-103-20031105) with ESMTP id <20040307100549.CRNF8729.amsfep12-int.chello.nl@sitetronics.com>; Sun, 7 Mar 2004 11:05:49 +0100 Message-ID: <404AF34B.7000506@sitetronics.com> Date: Sun, 07 Mar 2004 11:02:51 +0100 From: "Devon H. O'Dell" User-Agent: Mozilla Thunderbird 0.5 (Windows/20040207) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ender References: <404AEF20.7090506@tog.net> In-Reply-To: <404AEF20.7090506@tog.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-bugs@freebsd.org Subject: Re: bad syntax in ipfw casues kernel panic. X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Mar 2004 10:05:54 -0000 Ender wrote: > ipfw queue 1 config pipe 1 weight 140 queue 1024Kbytes > > using the above command to make a weighted queue using a number higher > than 100 causes a kernel panic. > > effect: freebsd 5.2.1 maybe more > _______________________________________________ > freebsd-bugs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-bugs > To unsubscribe, send any mail to "freebsd-bugs-unsubscribe@freebsd.org" > root@freebsd0 :~# ipfw queue 1 config pipe 1 weight 140 queue 1024Kbytes ipfw: weight must be <= 100 I cannot reproduce this bug. --Devon From owner-freebsd-bugs@FreeBSD.ORG Sun Mar 7 02:28:34 2004 Return-Path: Delivered-To: freebsd-bugs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1C9C416A4CE for ; Sun, 7 Mar 2004 02:28:34 -0800 (PST) Received: from tog.net (tog.net [216.89.226.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id EB9FF43D1D for ; Sun, 7 Mar 2004 02:28:33 -0800 (PST) (envelope-from ender@tog.net) Received: by tog.net (Postfix, from userid 96) id 88C1029B60F; Sun, 7 Mar 2004 05:28:33 -0500 (EST) Received: from tog.net (host-216-89-225-139.terranova.net [216.89.225.139]) by tog.net (Postfix) with ESMTP id BF5DF29B5D5; Sun, 7 Mar 2004 05:28:31 -0500 (EST) Message-ID: <404AFA96.5070507@tog.net> Date: Sun, 07 Mar 2004 05:33:58 -0500 From: Ender User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6b) Gecko/20031205 Thunderbird/0.4 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Devon H. O'Dell" References: <404AEF20.7090506@tog.net> <404AF34B.7000506@sitetronics.com> In-Reply-To: <404AF34B.7000506@sitetronics.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 2.63-terranovanet_v5 (2004-01-11) on spamsmacker.terranova.net X-Spam-Status: No, hits=0.7 required=7.5 tests=AWL,BAYES_50 autolearn=no version=2.63-terranovanet_v5 X-Spam-Level: cc: freebsd-bugs@freebsd.org Subject: Re: bad syntax in ipfw casues kernel panic. X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Mar 2004 10:28:34 -0000 Devon H. O'Dell wrote: > Ender wrote: > >> ipfw queue 1 config pipe 1 weight 140 queue 1024Kbytes >> >> using the above command to make a weighted queue using a number >> higher than 100 causes a kernel panic. >> >> effect: freebsd 5.2.1 maybe more >> _______________________________________________ >> freebsd-bugs@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-bugs >> To unsubscribe, send any mail to "freebsd-bugs-unsubscribe@freebsd.org" >> > root@freebsd0 :~# ipfw queue 1 config pipe 1 weight 140 queue 1024Kbytes > ipfw: weight must be <= 100 > > I cannot reproduce this bug. > > --Devon > _______________________________________________ > freebsd-bugs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-bugs > To unsubscribe, send any mail to "freebsd-bugs-unsubscribe@freebsd.org" > try these rules ipfw pipe 1 config bw 800Kbyte/s queue 1024Kbytes ; ipfw queue 1 config pipe 1 weight 100 queue 1024Kbytes ; ipfw queue 2 config pipe 1 weight 90 queue 1024Kbytes ; ipfw queue 3 config pipe 1 weight 2 queue 1024Kbytes ; ipfw queue 4 config pipe 1 weight 1 queue 1024Kbytes ; ipfw add 1 queue 1 udp from 216.89.228.18 27015 to any out ; ipfw add 2 queue 2 tcp from 216.89.228.18 6112 to 216.89.228.60 out ; ipfw add 3 queue 3 ip from 216.89.228.18 6112 to any out ; ipfw add 4 queue 4 ip from 216.89.228.18 to any out ; then remove : ipfw del 1 then remove ipfw queue del 1 then add ipfw queue 1 config pipe 1 weight 140 queue 1024Kbytes i also have ALOT of traffic when i do this, i repeated it. If there is any other configs i have that could be relevent let me know. kern.ipc.somaxconn=16384 kern.ipc.nmbclusters=131072 net.inet.tcp.tcbhashsize=4096 #firewall options HZ=1000 options IPFIREWALL options IPFIREWALL_DEFAULT_TO_ACCEPT options DUMMYNET From owner-freebsd-bugs@FreeBSD.ORG Sun Mar 7 02:34:59 2004 Return-Path: Delivered-To: freebsd-bugs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A634B16A4CE for ; Sun, 7 Mar 2004 02:34:59 -0800 (PST) Received: from amsfep13-int.chello.nl (amsfep13-int.chello.nl [213.46.243.24]) by mx1.FreeBSD.org (Postfix) with ESMTP id D104443D2D for ; Sun, 7 Mar 2004 02:34:58 -0800 (PST) (envelope-from dodell@sitetronics.com) Received: from sitetronics.com ([213.46.139.145]) by amsfep13-int.chello.nl (InterMail vM.6.00.05.02 201-2115-109-103-20031105) with ESMTP id <20040307103457.MZDF8266.amsfep13-int.chello.nl@sitetronics.com>; Sun, 7 Mar 2004 11:34:57 +0100 Message-ID: <404AFA1F.20307@sitetronics.com> Date: Sun, 07 Mar 2004 11:31:59 +0100 From: "Devon H. O'Dell" User-Agent: Mozilla Thunderbird 0.5 (Windows/20040207) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ender , freebsd-bugs@freebsd.org References: <404AEF20.7090506@tog.net> <404AF34B.7000506@sitetronics.com> <404AFA96.5070507@tog.net> In-Reply-To: <404AFA96.5070507@tog.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: bad syntax in ipfw casues kernel panic. X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Mar 2004 10:34:59 -0000 Ender wrote: > try these rules > > ipfw pipe 1 config bw 800Kbyte/s queue 1024Kbytes ; > ipfw queue 1 config pipe 1 weight 100 queue 1024Kbytes ; > ipfw queue 2 config pipe 1 weight 90 queue 1024Kbytes ; > ipfw queue 3 config pipe 1 weight 2 queue 1024Kbytes ; > ipfw queue 4 config pipe 1 weight 1 queue 1024Kbytes ; > ipfw add 1 queue 1 udp from 216.89.228.18 27015 to any out ; > ipfw add 2 queue 2 tcp from 216.89.228.18 6112 to 216.89.228.60 out ; > ipfw add 3 queue 3 ip from 216.89.228.18 6112 to any out ; > ipfw add 4 queue 4 ip from 216.89.228.18 to any out ; > > then remove : ipfw del 1 > then remove ipfw queue del 1 > then add ipfw queue 1 config pipe 1 weight 140 queue 1024Kbytes When I add these rules, and hit the final one, I receive: root@freebsd0 :~# ipfw queue 1 config pipe 1 weight 140 queue 1024Kbytes ipfw: weight must be <= 100 Before you question my system: FreeBSD freebsd0.sitetronics.com 5.2.1-RELEASE-p1 FreeBSD 5.2.1-RELEASE-p1 #2: Wed Mar 3 09:25:48 PST 2004 root@freebsd0.sitetronics.com:/usr/obj/usr/src/sys/SITETRONICS i386 > > i also have ALOT of traffic when i do this, i repeated it. If there is > any other configs i have that could be relevent let me know. What's ``A LOT'' of traffic? The system I'm on is pushing approximately 10Mbit at this time. > kern.ipc.somaxconn=16384 > kern.ipc.nmbclusters=131072 > net.inet.tcp.tcbhashsize=4096 > > > #firewall > options HZ=1000 > options IPFIREWALL > options IPFIREWALL_DEFAULT_TO_ACCEPT > options DUMMYNET These all look decent to me. --Devon From owner-freebsd-bugs@FreeBSD.ORG Sun Mar 7 02:44:35 2004 Return-Path: Delivered-To: freebsd-bugs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 90FB816A4CE; Sun, 7 Mar 2004 02:44:35 -0800 (PST) Received: from pengo.systems.pipex.net (pengo.systems.pipex.net [62.241.160.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id 950AD43D31; Sun, 7 Mar 2004 02:44:34 -0800 (PST) (envelope-from mark.cullen@dsl.pipex.com) Received: from ape (81-178-207-121.dsl.pipex.com [81.178.207.121]) by pengo.systems.pipex.net (Postfix) with SMTP id 3D99E4C00063; Sun, 7 Mar 2004 10:44:32 +0000 (GMT) Message-ID: <000d01c40431$2d6b93b0$f700000a@ape> From: "Markie" To: , , , Date: Sun, 7 Mar 2004 10:44:32 -0000 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.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Subject: Yet another panic... using /dev/speaker this time X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Mar 2004 10:44:36 -0000 Well I think I have worked around my other panic that I posted a few days ago by updating the modems firmware, atleast it doesn't panic under the situation it did last time. I still believe the bug exists somewhere though and i'm sure I could still reproduce it if anyone is interested. Just now I was playing about with /dev/speaker for a script I want to beep. I did an `echo a > /dev/speaker` and it worked, but I decided I wanted it longer or some kind of pattern. I followed this by an `echo aaa > /dev/speaker` and it worked :o) I then went on to read the man page and found out about raising and lowering octaves and pauses, so next I tried `echo aPa > /dev/speaker` and indeed there was a pause. However, when I tried `echo aP>a > /dev/speaker` (which I think is wrong anyhow but never mind) my SSH session froze and I knew something had gone wrong. Unfortuantly the monitor had become unplugged from when I was fiddling about so I didn't get to see anything on screen, but I did get a coredump for what it's worth. It isn't from a debugging kernel either, if need be I can load a debugging kernel and see if I can reproduce it. ( I am beginning to think I never should have upgraded :o) ) Anyway, here goes nothing: --- IdlePTD at phsyical address 0x00361000 initial pcb at physical address 0x002bb620 panicstr: getnewbuf: locked buf panic messages: --- panic: lockmgr: pid 8486, not exclusive lock holder 7018 unlocking syncing disks... panic: getnewbuf: locked buf Uptime: 3d13h40m34s dumping to dev #ad/0x20001, offset 65664 dump ata0: resetting devices .. done 95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 --- #0 0xc015bea2 in dumpsys () (kgdb) bt #0 0xc015bea2 in dumpsys () #1 0xc015bc6c in boot () #2 0xc015c0a0 in poweroff_wait () #3 0xc0183d4f in getnewbuf () #4 0xc01849cf in geteblk () #5 0xc0182b8d in bwrite () #6 0xc018869f in vop_stdbwrite () #7 0xc01884b5 in vop_defaultop () #8 0xc0183006 in bawrite () #9 0xc01965b0 in spec_fsync () #10 0xc0214d48 in ffs_sync () #11 0xc018d74b in sync () #12 0xc015ba06 in boot () #13 0xc015c0a0 in poweroff_wait () #14 0xc0155e48 in lockmgr () #15 0xc0183698 in brelse () #16 0xc0260bea in spkrclose () #17 0xc019687f in spec_close () #18 0xc021cb06 in ufsspec_close () #19 0xc021d101 in ufs_vnoperatespec () #20 0xc01921a7 in vn_close () #21 0xc0192afe in vn_closefile () #22 0xc0150eb8 in fdrop () ---Type to continue, or q to quit--- #23 0xc0150dfc in closef () #24 0xc0150931 in fdfree () #25 0xc015381a in exit1 () #26 0xc015368d in sys_exit () #27 0xc0255361 in syscall2 () #28 0xc02466f5 in Xint0x80_syscall () #29 0x28084887 in ?? () #30 0x28082185 in ?? () #31 0x2808182f in ?? () #32 0x280812bf in ?? () #33 0x2808101a in ?? () #34 0x280940e3 in ?? () #35 0x28096958 in ?? () #36 0x8048502 in ?? () #37 0x8048442 in ?? () (kgdb) --- I'm not sure if this should goto hackers or current or bugs or... what, so i'll send it to all of them (although I am not subscribed to hackers and current or bugs anymore). It's a 4.9-R-p3 machine... sorry if I am annoying you all :o) From owner-freebsd-bugs@FreeBSD.ORG Sun Mar 7 08:48:11 2004 Return-Path: Delivered-To: freebsd-bugs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 590DF16A4CE; Sun, 7 Mar 2004 08:48:11 -0800 (PST) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id EFCDC43D3F; Sun, 7 Mar 2004 08:48:10 -0800 (PST) (envelope-from jan.muenther@nruns.com) Received: from [212.227.126.155] (helo=mrelayng.kundenserver.de) by moutng.kundenserver.de with esmtp (Exim 3.35 #1) id 1B01Rh-0001jP-00; Sun, 07 Mar 2004 17:48:09 +0100 Received: from [212.202.171.90] (helo=ergo.nruns.com) by mrelayng.kundenserver.de with asmtp (Exim 3.35 #1) id 1B01Rh-0004kb-00; Sun, 07 Mar 2004 17:48:09 +0100 Received: by ergo.nruns.com (Postfix, from userid 1001) id 5466B119; Sun, 7 Mar 2004 17:44:30 +0100 (CET) Date: Sun, 7 Mar 2004 17:44:28 +0100 From: jan.muenther@nruns.com To: Ender Message-ID: <20040307164428.GA763@ergo.nruns.com> References: <404AEE63.8030602@tog.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <404AEE63.8030602@tog.net> User-Agent: Mutt/1.4i X-Provags-ID: kundenserver.de abuse@kundenserver.de auth:9a8a46f2b40f7808f7699def63624ac2 cc: freebsd-security@freebsd.org cc: freebsd-bugs@freebsd.org Subject: Re: strace hard lock X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Mar 2004 16:48:11 -0000 Hm, hm. Well, normally, one would use truss or ktrace, since strace isn't part of the base system. Also, are you sure you're not simply running out of system resources, like forkbombing or something? Tried the same thing with a restricted user? I couldn't reproduce it over here, on a single CPU 5.2.1 box. From owner-freebsd-bugs@FreeBSD.ORG Sun Mar 7 08:50:25 2004 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8C32416A4CE for ; Sun, 7 Mar 2004 08:50:25 -0800 (PST) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7C9CB43D31 for ; Sun, 7 Mar 2004 08:50:25 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) i27GoPbv013497 for ; Sun, 7 Mar 2004 08:50:25 -0800 (PST) (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.10/8.12.10/Submit) id i27GoPSi013496; Sun, 7 Mar 2004 08:50:25 -0800 (PST) (envelope-from gnats) Date: Sun, 7 Mar 2004 08:50:25 -0800 (PST) Message-Id: <200403071650.i27GoPSi013496@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Antti Louko Subject: Re: misc/62440: ATA problems X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Antti Louko List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Mar 2004 16:50:25 -0000 The following reply was made to PR misc/62440; it has been noted by GNATS. From: Antti Louko To: freebsd-gnats-submit@FreeBSD.org, manlix@demonized.net Cc: Subject: Re: misc/62440: ATA problems Date: Sun, 07 Mar 2004 18:40:23 +0200 I decided to report my findings with this (I assume it is the same) bug. For me it happens only when I have a SATA drive attached to its controller. What is more interesting, if I reboot the machine, detach the SATA drive without switching power off, timeouts and failures keep appearing (they appear on one particular ATA drive, not the SATA one) until I make a proper power down/up sequence without the SATA drive attached. I have tried with both 5.2.1 kernel and -CURRENT. APIC is disabled (or is it?): /boot/device.hints: hint.apic.0.disabled="1" and in the -CURRENT kernel the apic is commented out. Here is the kernel printf: Copyright (c) 1992-2004 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.2-CURRENT #0: Sat Mar 6 19:56:32 EET 2004 alo@alo99.louko.com:/u4/alo/FreeBSD/sys-src-current/src/sys/i386/compile/ALOIFP2 Preloaded elf kernel "/boot/kernel/kernel" at 0xc0a4a000. Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) 4 CPU 2.40GHz (2400.09-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf27 Stepping = 7 Features=0xbfebfbff real memory = 1073725440 (1023 MB) avail memory = 1041203200 (992 MB) Pentium Pro MTRR support enabled npx0: [FAST] npx0: on motherboard npx0: INT 16 interface pcibios: BIOS version 2.10 Found $PIR table, 11 entries at 0xc00f2320 pcib0: at pcibus 0 on motherboard pci0: on pcib0 $PIR: 0:29 INTA routed to irq 11 $PIR: ROUTE_INTERRUPT failed. $PIR: ROUTE_INTERRUPT failed. $PIR: ROUTE_INTERRUPT failed. $PIR: ROUTE_INTERRUPT failed. $PIR: ROUTE_INTERRUPT failed. agp0: mem 0xf0000000-0xf3ffffff at device 0.0 on pci0 pcib1: mem 0xe8000000-0xebffffff at device 1.0 on pci0 pci1: on pcib1 $PIR: 1:0 INTA routed to irq 11 pci1: at device 0.0 (no driver attached) uhci0: port 0xd800-0xd81f irq 11 at device 29.0 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered ums0: Logitech USB Receiver, rev 1.10/9.10, addr 2, iclass 3/1 ums0: 5 buttons and Z dir. uhci1: port 0xd400-0xd41f irq 9 at device 29.1 on pci0 usb1: on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2: port 0xd000-0xd01f irq 9 at device 29.2 on pci0 usb2: on uhci2 usb2: USB revision 1.0 uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered pci0: at device 29.7 (no driver attached) pcib2: at device 30.0 on pci0 pci2: on pcib2 $PIR: 2:2 INTA routed to irq 9 $PIR: 2:3 INTA routed to irq 5 $PIR: 2:4 INTA routed to irq 9 $PIR: 2:5 INTA routed to irq 9 fxp0: port 0xb800-0xb83f mem 0xe3000000-0xe301ffff,0xe3800000-0xe3800fff irq 9 at device 2.0 on pci2 fxp0: Ethernet address 00:02:b3:c0:ca:3d miibus0: on fxp0 inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fwohci0: mem 0xe2000000-0xe2003fff,0xe2800000-0xe28007ff irq 5 at device 3.0 on pci2 fwohci0: OHCI version 1.10 (ROM=1) fwohci0: No. of Isochronous channel is 4. fwohci0: EUI64 00:e0:18:00:00:15:a2:bb fwohci0: Phy 1394a available S400, 2 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: on fwohci0 fwe0: on firewire0 if_fwe0: Fake Ethernet address: 02:e0:18:15:a2:bb sbp0: on firewire0 fwohci0: Initiate bus reset fwohci0: node_id=0xc800ffc0, gen=1, CYCLEMASTER mode firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me) firewire0: bus manager 0 (me) atapci0: port 0xa000-0xa00f,0xa400-0xa403,0xa800-0xa807,0xb000-0xb003,0xb400-0xb407 mem 0xe1800000-0xe18001ff irq 9 at device 4.0 on pci2 atapci0: [MPSAFE] ata2: at 0xe1800000 on atapci0 ata2: [MPSAFE] ata3: at 0xe1800000 on atapci0 ata3: [MPSAFE] bge0: mem 0xe1000000-0xe100ffff irq 9 at device 5.0 on pci2 bge0: Ethernet address: 00:0c:6e:0d:dc:e4 miibus1: on bge0 brgphy0: on miibus1 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto isab0: at device 31.0 on pci0 isa0: on isab0 atapci1: port 0xf000-0xf00f,0-0x3,0-0x7,0-0x3,0-0x7 irq 9 at device 31.1 on pci0 ata0: at 0x1f0 irq 14 on atapci1 ata0: [MPSAFE] ata1: at 0x170 irq 15 on atapci1 ata1: [MPSAFE] pci0: at device 31.5 (no driver attached) orm0: