From owner-freebsd-current@FreeBSD.ORG Sun Jul 11 03:20:24 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4EFBB16A508 for ; Sun, 11 Jul 2004 03:20:24 +0000 (GMT) Received: from hrothgar.unconceived.net (rrcs-se-24-73-170-14.biz.rr.com [24.73.170.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 906DC43D3F for ; Sun, 11 Jul 2004 03:20:21 +0000 (GMT) (envelope-from jhandvil@tampabay.rr.com) Received: from localhost (localhost [IPv6:::1])i6B3GqCN050067 for ; Sat, 10 Jul 2004 23:16:52 -0400 (EDT) (envelope-from jhandvil@tampabay.rr.com) From: jhandvil To: freebsd-current@freebsd.org Date: Sat, 10 Jul 2004 23:16:52 -0400 User-Agent: KMail/1.5.4 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200407102316.52182.jhandvil@tampabay.rr.com> Subject: 5.2.1 p9 --> 5.2 current 20040709 upgrade ATA_IDENTIFY no interrupt X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: jhandvil@tampabay.rr.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Jul 2004 03:20:24 -0000 Just upgraded from 5.2.1 p9 to 5.2-current (20040709). While test booting the new kernel, I received the following error. Unfortunately, I was unable to save the dmesg. Here is the error copied by hand, please excuse typo's: ata0-master: FAILURE - ATA_IDENTIFY no interrupt ata0-master: FAILURE - ATA_IDENTIFY no interrupt Mounting root from ufs:/dev/ad0s1a setrootbyname failed ffs_mountroot: can't find rootvp Root mount failed: 6 System info - AMD Athlon 1.33 266MHZ DDR (133MHZ FSB). 1024MB ram DDR PC2100 IDE HD as Master 0, Sony DVD+/- RW as Master 1 (disabled -- see below) NVIDIA GeForce 3 AGP Sound Blaster live VIA 8233 UDMA100 controller ad0: 152627MB [310101/16/63] at ata0-master UDMA100 Let me know if there is any additional information needed. Cursory google search and scan of UPDATING found only two encounters with this problem, both of which used a DVD RW drive. Thinking this might be the culprit, I disabled (read unplugged) my Sony DVD+/-RW drive and rebooted to no avail. I attempted to boot w/ disabled ACPI, but I get the same message. For now I have failed over to the 5.2.1 kernel which works with the -current world. I am interested in testing the new KSE and the changes to the boem gc library. Any suggestions for bootstrapping the -current kernel? Thanks, Justin From owner-freebsd-current@FreeBSD.ORG Sun Jul 11 03:20:24 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5B1F316A509 for ; Sun, 11 Jul 2004 03:20:24 +0000 (GMT) Received: from hrothgar.unconceived.net (rrcs-se-24-73-170-14.biz.rr.com [24.73.170.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8FA4E43D1D for ; Sun, 11 Jul 2004 03:20:21 +0000 (GMT) (envelope-from jhandvil@tampabay.rr.com) Received: from localhost.unconceived.net (localhost.unconceived.net [127.0.0.1])i690WA2J000727 for ; Thu, 8 Jul 2004 20:32:10 -0400 (EDT) (envelope-from jhandvil@tampabay.rr.com) From: jhandvil To: freebsd-current@freebsd.org Date: Thu, 8 Jul 2004 20:32:10 -0400 User-Agent: KMail/1.5.4 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200407082032.10210.jhandvil@tampabay.rr.com> Subject: 5.2.1 p9 --> 5.2 current 20040708 upgrade ATA_IDENTIFY no interrupt X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: jhandvil@tampabay.rr.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Jul 2004 03:20:24 -0000 Just upgraded from 5.2.1 p9 to 5.2-current. Received the following error during boot (copied by hand, please excuse typo's): ata0-master: FAILURE - ATA_IDENTIFY no interrupt ata0-master: FAILURE - ATA_IDENTIFY no interrupt Mounting root from ufs:/dev/ad0s1a setrootbyname failed ffs_mountroot: can't find rootvp Root mount failed: 6 System info - AMD Athlon 1.33 266MHZ DDR (133MHZ FSB). 1024MB ram DDR PC2100 IDE HD as Master 0, Sony DVD+/- RW as Master 1 (disabled -- see below) NVIDIA GeForce 3 AGP Sound Blaster LIVE (from 5.2.1 p9 kernel dmesg) atapci0: port 0xff00-0xff0f at device 17.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata0: [MPSAFE] ata1: at 0x170 irq 15 on atapci0 ata1: [MPSAFE] ad0: 152627MB [310101/16/63] at ata0-master UDMA100 Cursory google search and scan of UPDATING found only two encounters with this problem, both of which used a DVD RW drive. Thinking this might be the culprit, I disabled (read unplugged) my Sony DVD+/-RW drive and rebooted to no avail. I attempted to boot w/ disabled ACPI, but I get the same message. For now I have failed over to the 5.2.1 kernel which appears to work in some broken manner with the -current world (enough to run X). Any suggestions for bootstrapping the -current kernel? Thanks, Justin From owner-freebsd-current@FreeBSD.ORG Sun Jul 11 04:51:50 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 960DF16A4CE; Sun, 11 Jul 2004 04:51:50 +0000 (GMT) Received: from ns1.xcllnt.net (209-128-86-226.BAYAREA.NET [209.128.86.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3FFD243D53; Sun, 11 Jul 2004 04:51:50 +0000 (GMT) (envelope-from marcel@xcllnt.net) Received: from dhcp50.pn.xcllnt.net (dhcp50.pn.xcllnt.net [192.168.4.250]) by ns1.xcllnt.net (8.12.11/8.12.11) with ESMTP id i6B4po9x079412; Sat, 10 Jul 2004 21:51:50 -0700 (PDT) (envelope-from marcel@piii.pn.xcllnt.net) Received: from dhcp50.pn.xcllnt.net (localhost [127.0.0.1]) i6B4pj45040523; Sat, 10 Jul 2004 21:51:46 -0700 (PDT) (envelope-from marcel@dhcp50.pn.xcllnt.net) Received: (from marcel@localhost) by dhcp50.pn.xcllnt.net (8.12.11/8.12.11/Submit) id i6B4pjd0040522; Sat, 10 Jul 2004 21:51:45 -0700 (PDT) (envelope-from marcel) Date: Sat, 10 Jul 2004 21:51:45 -0700 From: Marcel Moolenaar To: alpha@FreeBSD.org, current@FreeBSD.org Message-ID: <20040711045145.GA40508@dhcp50.pn.xcllnt.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Subject: HEADSUP [alpha]: New console initialization X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Jul 2004 04:51:50 -0000 Gang, The console initialization on alpha has been reworked to not require the many alpha specific kluges in the various drivers (gfb, sio and syscons). Consequently, one now needs the well-known hints that one needs on other platforms for things to work. In particular, you might want to add: hint.sio.0.flags="0x10" hint.sio.1.flags="0x80" Without these hints you won't have a serial console. FYI, -- Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net From owner-freebsd-current@FreeBSD.ORG Sun Jul 11 04:57:29 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B5D5916A4CE; Sun, 11 Jul 2004 04:57:29 +0000 (GMT) Received: from ns1.xcllnt.net (209-128-86-226.BAYAREA.NET [209.128.86.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7C52C43D3F; Sun, 11 Jul 2004 04:57:29 +0000 (GMT) (envelope-from marcel@xcllnt.net) Received: from dhcp50.pn.xcllnt.net (dhcp50.pn.xcllnt.net [192.168.4.250]) by ns1.xcllnt.net (8.12.11/8.12.11) with ESMTP id i6B4vTVT079435; Sat, 10 Jul 2004 21:57:29 -0700 (PDT) (envelope-from marcel@piii.pn.xcllnt.net) Received: from dhcp50.pn.xcllnt.net (localhost [127.0.0.1]) i6B4vTlX040546; Sat, 10 Jul 2004 21:57:29 -0700 (PDT) (envelope-from marcel@dhcp50.pn.xcllnt.net) Received: (from marcel@localhost) by dhcp50.pn.xcllnt.net (8.12.11/8.12.11/Submit) id i6B4vSlx040545; Sat, 10 Jul 2004 21:57:28 -0700 (PDT) (envelope-from marcel) Date: Sat, 10 Jul 2004 21:57:28 -0700 From: Marcel Moolenaar To: amd64@FreeBSD.org, current@FreeBSD.org Message-ID: <20040711045728.GB40508@dhcp50.pn.xcllnt.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Subject: HEADSUP [amd64]: New KDB framework untested. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Jul 2004 04:57:29 -0000 Gang, Since I don't have an amd64 box myself, I could not test the new KDB framework. So, I pretty much made sure it compiled and since amd64 is in many ways very similar to i386, there's a good chance I got it right. But obviously when it's not tested there's a big chance it contains bugs or is just plain broken. You might want to pay special attention to it... FYI, -- Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net From owner-freebsd-current@FreeBSD.ORG Sun Jul 11 05:18:43 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2738316A4CE for ; Sun, 11 Jul 2004 05:18:43 +0000 (GMT) Received: from ns1.xcllnt.net (209-128-86-226.BAYAREA.NET [209.128.86.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id EECD043D1F for ; Sun, 11 Jul 2004 05:18:42 +0000 (GMT) (envelope-from marcel@xcllnt.net) Received: from dhcp50.pn.xcllnt.net (dhcp50.pn.xcllnt.net [192.168.4.250]) by ns1.xcllnt.net (8.12.11/8.12.11) with ESMTP id i6B5IgVu079480 for ; Sat, 10 Jul 2004 22:18:42 -0700 (PDT) (envelope-from marcel@piii.pn.xcllnt.net) Received: from dhcp50.pn.xcllnt.net (localhost [127.0.0.1]) by dhcp50.pn.xcllnt.net (8.12.11/8.12.11) with ESMTP id i6B5IgUk040600 for ; Sat, 10 Jul 2004 22:18:42 -0700 (PDT) (envelope-from marcel@dhcp50.pn.xcllnt.net) Received: (from marcel@localhost) by dhcp50.pn.xcllnt.net (8.12.11/8.12.11/Submit) id i6B5Igmo040599 for current@FreeBSD.org; Sat, 10 Jul 2004 22:18:42 -0700 (PDT) (envelope-from marcel) Date: Sat, 10 Jul 2004 22:18:42 -0700 From: Marcel Moolenaar To: current@FreeBSD.org Message-ID: <20040711051842.GC40508@dhcp50.pn.xcllnt.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Subject: HEADSUP: KDB framework X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Jul 2004 05:18:43 -0000 Gang, A new debugging framework has been committed. Besides adding support for kernel threads to both DDB and remote GDB and other nice features, there are some kernel configuration changes one needs to be aware of: o The DDB option is not to be used for conditional compilation of debugging related code or checks. The option is now controls the inclusion of the DDB debugger backend only. A new option, KDB, has been added for the conditional compilation of debugging code. Note that the KDB option does *not* affect the KDB frontend code. That code is non-conditional so that it can be used by modules without having to worry about it's presence. o The WITNESS_DDB, DDB_TRACE and DDB_UNATTENDED options have been renamed to WITNESS_KDB, KDB_TRACE and KDB_UNATTENDED as per the previous bullet. The options have no relation to the DDB backend. o There's no seperate option to use the symbols in the kernel image for symbol lookups instead of the kernel linker in DDB. Both are supported at the same time. o Support for remote GDB has been removed from DDB and added as a seperate debugger backend. Use option GDB to enable it. o The GDB debugger backend exports a simple interface to device so that they can register themselves as debug ports. Remote debugging is now possible using a more richer set of devices. The sio(4) driver has been converted, but the dcons(4) driver is a victim. Someone with the necessary firewire links needs to help out here. There's probably more, but I've had enough for today :-) -- Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net From owner-freebsd-current@FreeBSD.ORG Sun Jul 11 09:13:36 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1500C16A4CE for ; Sun, 11 Jul 2004 09:13:36 +0000 (GMT) Received: from pimout2-ext.prodigy.net (pimout2-ext.prodigy.net [207.115.63.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 93DA343D46 for ; Sun, 11 Jul 2004 09:13:35 +0000 (GMT) (envelope-from julian@elischer.org) Received: from elischer.org (adsl-68-121-219-69.dsl.snfc21.pacbell.net [68.121.219.69])i6B9DOUK086094; Sun, 11 Jul 2004 05:13:25 -0400 Message-ID: <40F104B4.2070000@elischer.org> Date: Sun, 11 Jul 2004 02:13:24 -0700 From: Julian Elischer User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.4b) Gecko/20030524 X-Accept-Language: en, hu MIME-Version: 1.0 To: ticso@cicely.de References: <20040707.232916.126914893.imp@bsdimp.com> <20040708084650.GW12877@cicely12.cicely.de> <20040708093145.GX12877@cicely12.cicely.de> In-Reply-To: <20040708093145.GX12877@cicely12.cicely.de> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: phk@phk.freebsd.dk cc: mycroft@netbsd.org cc: current@FreeBSD.org cc: "M. Warner Losh" Subject: Re: speeding up ugen by an order of magnitude. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Jul 2004 09:13:36 -0000 Bernd Walter wrote: > On Thu, Jul 08, 2004 at 10:46:51AM +0200, Bernd Walter wrote: > >>On Thu, Jul 08, 2004 at 01:16:24AM -0700, Julian Elischer wrote: > > OK - It looks like you are absolutely right. > It seems that the controller sweeps trough the request queues on a > per frame basis - we can only get per frame what we have set. > What we havn't set at that time won't make it onto the bus until the > next frame. > Not surprising after rethinking, because the priority calculation > is done on a per frame base. > > If we just have a single 1k xfer then 1k is all we can ever get per ms. > If we have two 8k xfers or a single 16k xfer then that's what we can > get per ms at maximum. > I havn't calculated the maximum size per frame yet, but if it's 60k > then we really have to push xfers for 60k into the pipe in parallel > and we are required to have setup the next xfers in time for the next > frame. > > Say you are doing 128k and you get 60k per frame. > Then you get 60k in the first ms, 60k in the second and only 8k in > the third - then you setup the next one and get 60k again. > If the bus is loaded with other requests then the splitting is > different. > Interleaving two 64k requests would get us 4k of the first request and > 56k of the second request during the second ms. > Well - that theoretical so far... > > Can we do interleaving with physio? Sorry to not get back to you but my mail server dropped off the net and I was remote from it.. Yes you can do multiple IOs with physio but as charles pointed out we need to be very careful about allignment requirements. As Matt pointed out, it may be just easier to do the copying.. Note, you can get an interrupt from ehci every uframe instead of every frame by changing an config register. We could also use the "interrupt on end of transfer interrupt. Async transfers just use up "whatever is left over" so I thin that priority calculations are not so important for them.. anyhow I've got my mail system going again so hopefully I can get to look at something else tomorrow.. maybe even the ehci drive again :-) BTW in answer to your question "how many interrupts per second?" the answer was 1000 exactly :-) -- +------------------------------------+ ______ _ __ | __--_|\ Julian Elischer | \ U \/ / hard at work in | / \ julian@elischer.org +------>x USA \ a very strange | ( OZ ) \___ ___ | country ! +- X_.---._/ presently in San Francisco \_/ \\ v From owner-freebsd-current@FreeBSD.ORG Sun Jul 11 10:06:02 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E2EAF16A4CE; Sun, 11 Jul 2004 10:06:01 +0000 (GMT) Received: from tuminfo2.informatik.tu-muenchen.de (tuminfo2.informatik.tu-muenchen.de [131.159.0.81]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0CC8043D45; Sun, 11 Jul 2004 10:06:01 +0000 (GMT) (envelope-from langd@informatik.tu-muenchen.de) Date: Sun, 11 Jul 2004 12:05:53 +0200 From: Daniel Lang To: Don Lewis Message-ID: <20040711100553.GA64553@atrbg11.informatik.tu-muenchen.de> References: <200407102324.i6ANOlEs015698@gw.catspoiler.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200407102324.i6ANOlEs015698@gw.catspoiler.org> X-Geek: GCS/CC d-- s: a- C++$ UBS++++$ P+++$ L- E-(---) W+++(--) N++ o K w--- O? M? V? PS+(++) PE--(+) Y+ PGP+ t++ 5+++ X R+(-) tv+ b+ DI++ D++ G++ e+++ h---(-) r+++ y+ User-Agent: Mutt/1.5.6i X-Virus-Scanned: by amavisd-new at informatik.tu-muenchen.de cc: ps@FreeBSD.org cc: rwatson@FreeBSD.org cc: current@FreeBSD.org Subject: Re: panic: m_copym, length > size of mbuf chain X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Jul 2004 10:06:02 -0000 Hi Don, referring to your first answer, the 'len' parameter in the tcp_output.c frame is 1460, offset is 737. The sum is obviously greater than 975, the value of so->so_snd.sb_cc. So the suggested assertion from Robert would have been triggered. I consider now adding the SOCKBUF_DEBUG value. However, with SACK disabled, the machine is still up and running now. Don Lewis wrote on Sat, Jul 10, 2004 at 04:24:47PM -0700: [..] > > (2) Try adding some assertions just before the copy to m_copy() in > > tcp_output(). I'd suggest something like the following: > > I'm very suspicious of the SACK code. In the non-SACK case, len gets > set here: > > if (!sack_rxmit) > len = ((long)ulmin(so->so_snd.sb_cc, sendwin) - off); > > but when the system panics len+off > sb_cc. Yes. > It would be interesting to look at *tp and *p in the tcp_output stack > frame. > > If I had to guess, I'd say that either tp->snd_recover-tp->snd_una or > p->end-tp->snd_una is greater than so->so_snd.sb_cc. (kgdb) p *tp $4 = {t_segq = {lh_first = 0x0}, t_segqlen = 0, t_dupacks = 16, unused = 0x0, tt_rexmt = 0xc3f50148, tt_persist = 0xc3f50160, tt_keep = 0xc3f50178, tt_2msl = 0xc3f50190, tt_delack = 0xc3f501a8, t_inpcb = 0xc4d592d0, t_state = 5, t_flags = 1049092, t_force = 0, snd_una = 2644477935, snd_max = 2644478910, snd_nxt = 2644478910, snd_up = 2644477935, snd_wl1 = 465530853, snd_wl2 = 2644477935, iss = 2644477934, irs = 465530852, rcv_nxt = 465530854, rcv_adv = 465596389, rcv_wnd = 65700, rcv_up = 465530854, snd_wnd = 17520, snd_cwnd = 26280, snd_bwnd = 1073725440, snd_ssthresh = 2920, snd_bandwidth = 3498991, snd_recover = 2644478412, t_maxopd = 1460, t_rcvtime = 333934, t_starttime = 330457, t_rtttime = 333904, t_rtseq = 2644478412, t_bw_rtttime = 330457, t_bw_rtseq = 0, t_rxtcur = 145, t_maxseg = 1460, t_srtt = 717, t_rttvar = 72, t_rxtshift = 0, t_rttmin = 3, t_rttbest = 749, t_rttupdated = 0, max_sndwnd = 17520, t_softerror = 0, t_oobflags = 0 '\0', t_iobc = 0 '\0', snd_scale = 0 '\0', rcv_scale = 0 '\0', request_r_scale = 0 '\0', requested_s_scale = 0 '\0', ts_recent = 0, ts_recent_age = 0, last_ack_sent = 465530854, cc_send = 0, cc_recv = 0, snd_cwnd_prev = 0, snd_ssthresh_prev = 0, snd_recover_prev = 0, t_badrxtwin = 0, snd_limited = 0 '\0', rcv_second = 0, rcv_pps = 0, rcv_byps = 0, sack_enable = 1, snd_numholes = 4, snd_holes = 0xc4280be0, rcv_laststart = 465530854, rcv_lastend = 465530854, rcv_lastsack = 2644478693, rcv_numsacks = 0, sackblks = {{start = 0, end = 0}, {start = 0, end = 0}, {start = 0, end = 0}, {start = 0, end = 0}, {start = 0, end = 0}, {start = 0, end = 0}}} So snd_recover - snd_una = 2644478412 - 2644477935 = 477, this is less than so->so_snd.sb_cc = 975. (kgdb) p *p $6 = {start = 2644478672, end = 2644478686, rxmit = 2644478672, next = 0x0} p->end - snd_una = 2644478686 - 2644477935 = 751, again less. Hmmm, I inspected the code in tcp_output.c about occurences of 'len', I stumbled across this code: [..] /* * NOTE! on localhost connections an 'ack' from the remote * end may occur synchronously with the output and cause * us to flush a buffer queued with moretocome. XXX * * note: the len + off check is almost certainly unnecessary. */ if (!(tp->t_flags & TF_MORETOCOME) && /* normal case */ (idle || (tp->t_flags & TF_NODELAY)) && len + off >= so->so_snd.sb_cc && (tp->t_flags & TF_NOPUSH) == 0) { goto send; [..] So here there is actually a check, but it does not seem to be a big problem, as later the length is adjusted if len + optlen + ipoptlen > tp->t_maxopd And as above confirmed, the len is 1460 throughout this frame.... Best regards, Daniel -- IRCnet: Mr-Spock - My name is Pentium of Borg, division is futile, you will be approximated. - Daniel Lang * dl@leo.org * +49 89 289 18532 * http://www.leo.org/~dl/ From owner-freebsd-current@FreeBSD.ORG Sun Jul 11 11:55:47 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EF7FD16A4CE for ; Sun, 11 Jul 2004 11:55:47 +0000 (GMT) Received: from slimy.rodal.no (16.80-202-60.nextgentel.com [80.202.60.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7867843D2F for ; Sun, 11 Jul 2004 11:55:46 +0000 (GMT) (envelope-from morten@rodal.no) Received: from atlantis.rodal.no (atlantis.rodal.no [192.168.20.62]) by slimy.rodal.no (8.12.11/8.12.11) with ESMTP id i6BBtieh015676; Sun, 11 Jul 2004 13:55:44 +0200 (CEST) (envelope-from morten@rodal.no) Received: from localhost (localhost [[UNIX: localhost]]) by atlantis.rodal.no (8.12.11/8.12.11/Submit) id i6BBthxp000826; Sun, 11 Jul 2004 13:55:43 +0200 (CEST) (envelope-from morten) From: Morten Rodal To: freebsd-current@freebsd.org Date: Sun, 11 Jul 2004 13:55:35 +0200 User-Agent: KMail/1.6.2 References: <20040711051842.GC40508@dhcp50.pn.xcllnt.net> In-Reply-To: <20040711051842.GC40508@dhcp50.pn.xcllnt.net> MIME-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="Boundary-02=_/qS8AcX4Sl4JWQB"; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200407111355.43043.morten@rodal.no> X-Virus-Scanned: by amavisd-new cc: Marcel Moolenaar Subject: Re: HEADSUP: KDB framework X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Jul 2004 11:55:48 -0000 --Boundary-02=_/qS8AcX4Sl4JWQB Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Sunday 11 July 2004 07:18, Marcel Moolenaar wrote: > Gang, > > A new debugging framework has been committed. Besides adding support > for kernel threads to both DDB and remote GDB and other nice features, > there are some kernel configuration changes one needs to be aware of: > =46ollowing this commit my computer panics right after going to multiuser=20 with the following: Mounting root from ufs:/dev/ad0s1a Pre-seeding PRNG: =46atal trap 12: page fault while in kernel mode cpuid =3D 0; apic id =3D 00 fault virtual address =3D 0x0 fault code =3D supervisor read, page not present instruction pointer =3D 0x8:0xc04ccc89 stack pointer =3D 0x10:0xcc417b9c frame pointer =3D 0x10:0xcc417bc8 code segment =3D base 0x0, limit 0xfffff, type 0x1b =3D DPL 0, pres 1, def32 1, gran 1 processors eflags =3D interrupt enabled, resume, IOPL =3D 0 current process =3D 70 (sysctl) trap number =3D 12 panic: page fault cpuid =3D 0; syncing disks, buffers remaining... 188 188 0 188 188 188 188 188 0 188=20 188 0 188 188 188 0 188 0 188 188 0 188 0 188 0 188 188 0 188 0 giving up on 163 buffers Uptime: 16s burton# addr2line -e /usr/obj/usr/src/sys/burton/kernel.debug 0xc04ccc89 /usr/src/sys/kern/subr_kdb.c:107 I think it was becase I replaced "options DDB" with "options KDB" instead=20 of adding "options KDB". This results in no debuggers being registered=20 (and thus the null pointer)? Perhaps some checks should be added to make=20 sure there really are any debuggers available before using them? =2D-=20 Morten Rodal "A supercomputer is a device for turning compute-bound problems into I/O bound problems." -- Ken Batcher (Goodyear Aerospace) --Boundary-02=_/qS8AcX4Sl4JWQB Content-Type: application/pgp-signature Content-Description: signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQBA8Sq+bWe1Cy11WVsRAnuRAKC9diLTAWFFZLUU9NRbo+OITV2zsACfbcSt psiA81Az6JBq0i22XSRk3MQ= =WmjN -----END PGP SIGNATURE----- --Boundary-02=_/qS8AcX4Sl4JWQB-- From owner-freebsd-current@FreeBSD.ORG Sun Jul 11 12:17:44 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E388A16A4CE; Sun, 11 Jul 2004 12:17:44 +0000 (GMT) Received: from mailout1.pacific.net.au (mailout1.pacific.net.au [61.8.0.84]) by mx1.FreeBSD.org (Postfix) with ESMTP id 48C9143D4C; Sun, 11 Jul 2004 12:17:44 +0000 (GMT) (envelope-from bde@zeta.org.au) Received: from mailproxy2.pacific.net.au (mailproxy2.pacific.net.au [61.8.0.87])i6BCHd4u006028; Sun, 11 Jul 2004 22:17:39 +1000 Received: from epsplex.bde.org (katana.zip.com.au [61.8.7.246]) i6BCHRnl004786; Sun, 11 Jul 2004 22:17:36 +1000 Date: Sun, 11 Jul 2004 22:17:26 +1000 (EST) From: Bruce Evans X-X-Sender: bde@epsplex.bde.org To: Scott Long In-Reply-To: <40EFDCEC.6080307@samsco.org> Message-ID: <20040711215816.T1987@epsplex.bde.org> References: <200407091314.07506.jhb@FreeBSD.org> <40EFDCEC.6080307@samsco.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-current@freebsd.org cc: Gerrit Nagelhout cc: Julian Elischer Subject: Re: STI, HLT in acpi_cpu_idle_c1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Jul 2004 12:17:45 -0000 On Sat, 10 Jul 2004, Scott Long wrote: > John Baldwin wrote: > > Once the EOI is sent to the APIC, the processor will except other interrupts. > > However, most of the interrupt code also runs with interrupts disabled. The > > exception is in ast(), meaning that another interrupt can come in and nest > > during an ast(), but ast() is not called during nested returns, so it won't > > nest infinitely. iret doesn't do any sort of EOI magic, all it does is popf > > followed by ret. The popf usually enables interrupts when it restores the > > interrupt flag's state. It might still be a hardware problem in the chipset, > > esp. since it always happens on a logical CPU. The fact that no other boxes > > in the field besides the two identical boxes you have have demonstrated this > > problem makes me very suspicious with respect to the hardware. > > > > Well, the real question is what happens in when the interrupt context > has to contest on the proc lock in ast(). What goes to sleep, and how This never happens, because ast() is never called in interrupt context. > it wake up? Does the interrupt context have a real process/thread > associated with it, or does it pretend to be curthread, or what? Since > the whole point of ithreads was to allow sleep locks in interrupt > handlers, isn't this a major violation? ast() is only called on return to user mode. This implies that curthread is a user thread (the one returning to user mode). It can never be an ithread. Most ast()s are on return from syscalls. Some are on return from interrupts, but these are best thought of as being in process context too. The interrupt has been completely handled (*) except for the final return from it. As an implementation detail, ast() is called directly before returning. I believe entry to ast() was originally in hardware on VAXes. There was a hardware instruction to schedule an additional trap on return. We could still do this in hardware on i386's at least by scheduling a trace trap, but a direct call is better. The SMP case still needs hardware (an IPI) for non-current CPUs. (*) Except possibly for magic and bugs. E.g., the iret after an NMI is special on at least some i386's, but is not handled right. Bruce From owner-freebsd-current@FreeBSD.ORG Sat Jul 10 15:01:10 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 83B2016A4CE for ; Sat, 10 Jul 2004 15:01:10 +0000 (GMT) Received: from mta6.adelphia.net (mta6.adelphia.net [68.168.78.190]) by mx1.FreeBSD.org (Postfix) with ESMTP id 36B7D43D53 for ; Sat, 10 Jul 2004 15:01:10 +0000 (GMT) (envelope-from rneese@adelphia.net) Received: from developer.no-ip.com ([69.160.7.248]) by mta13.adelphia.net (InterMail vM.6.01.03.02 201-2131-111-104-20040324) with ESMTP id <20040710150044.FPVW14365.mta13.adelphia.net@developer.no-ip.com> for ; Sat, 10 Jul 2004 11:00:44 -0400 From: Richard Neese To: current@freebsd.org Date: Sat, 10 Jul 2004 11:01:05 -0400 User-Agent: KMail/1.6.2 MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <200407101101.05080.rneese@adelphia.net> X-Mailman-Approved-At: Sun, 11 Jul 2004 12:33:06 +0000 Subject: full duplex sound card dirve X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Jul 2004 15:01:10 -0000 is anyone working on full duplex drivered for fbsd and soundcards. half the apps I use say the sound is only half duplex. like kphone wich we are porting and cpphone and a few other including asterisk0 pbx look at te sound card and report it as half duplex. I just think its time we get uptodate with full duplex drivers. I my self am new to c/c++ I will help where I can but have no idea where to start.. RIch From owner-freebsd-current@FreeBSD.ORG Sat Jul 10 18:12:33 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3839216A4CE for ; Sat, 10 Jul 2004 18:12:33 +0000 (GMT) Received: from web21327.mail.yahoo.com (web21327.mail.yahoo.com [216.136.175.216]) by mx1.FreeBSD.org (Postfix) with SMTP id 1980F43D45 for ; Sat, 10 Jul 2004 18:12:33 +0000 (GMT) (envelope-from brueggma@yahoo.com) Message-ID: <20040710181232.95705.qmail@web21327.mail.yahoo.com> Received: from [24.15.98.46] by web21327.mail.yahoo.com via HTTP; Sat, 10 Jul 2004 11:12:32 PDT Date: Sat, 10 Jul 2004 11:12:32 -0700 (PDT) From: asfdqwer xzcvdsf To: freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailman-Approved-At: Sun, 11 Jul 2004 12:33:06 +0000 Subject: current/perl/spamassassin X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Jul 2004 18:12:33 -0000 Greetings, Spamassassin seems to be using a HUDGE amount of memory while just sitting idle. On other boxes it uses about a 1/4 of the amount of ram. Is this something I should ask in the spamassassin mailing lists or is this the right place? Should I just look for another filter that uses less resources? Like dspam? (Which I don't think has a milter) athlon1# pkg_info | egrep "spam|perl" p5-Mail-SpamAssassin-2.63_2 A highly efficient mail filter for identifying spam perl-threaded-5.8.4 Practical Extraction and Report Language razor-agents-2.61 A distributed, collaborative, spam detection and filtering spamass-milter-0.2.0_4 Sendmail Milter (mail filter) for SpamAssassin athlon1# ps axuww | grep spam root 3493 0.0 0.1 3088 2056 ?? Ss 6:43PM 0:01.31 /usr/local/sbin/spamass-milter -f -p /var/run/spamass-milter.sock root 34350 0.0 1.2 26140 25700 ?? Is 6:43PM 0:00.87 /usr/local/bin/spamd -a -c -d -r /var/run/spamd.pid (perl5.8.4) athlon1# Thank you for any assistance, Eric athlon1# ls -la /etc/malloc.conf lrwxr-xr-x 1 root wheel 2 Jun 13 18:22 /etc/malloc.conf@ -> aj athlon1# uname -a FreeBSD athlon1.bsdnut.org 5.2-CURRENT FreeBSD 5.2-CURRENT #1: Fri Jul 2 15:46:11 CDT 2004 root@athlon1.bsdnut.org:/usr/obj/usr/src/sys/ATHLON i386 __________________________________ Do you Yahoo!? Yahoo! Mail Address AutoComplete - You start. We finish. http://promotions.yahoo.com/new_mail From owner-freebsd-current@FreeBSD.ORG Sat Jul 10 21:51:01 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9727F16A4CE for ; Sat, 10 Jul 2004 21:51:01 +0000 (GMT) Received: from jkh-gw.queasyweasel.com (adsl-64-173-3-158.dsl.sntc01.pacbell.net [64.173.3.158]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1DDDE43D3F for ; Sat, 10 Jul 2004 21:51:01 +0000 (GMT) (envelope-from jkh@queasyweasel.com) Received: from [64.173.15.98] (IDENT:15684-ident-is-a-completely-pointless-protocol-that-offers-no-security-or-traceability-at-all-so-ta@adsl-64-173-15-98.dsl.sntc01.pacbell.net [64.173.15.98])i6ALsrJx000695 for ; Sat, 10 Jul 2004 14:54:53 -0700 (PDT) (envelope-from jkh@queasyweasel.com) Mime-Version: 1.0 (Apple Message framework v618) Content-Transfer-Encoding: 7bit Message-Id: <49011D34-D2BB-11D8-81E2-000393BB9222@queasyweasel.com> Content-Type: text/plain; charset=US-ASCII; format=flowed To: freebsd-current@freebsd.org From: "Jordan K. Hubbard" Date: Sat, 10 Jul 2004 14:51:23 -0700 X-Mailer: Apple Mail (2.618) X-Mailman-Approved-At: Sun, 11 Jul 2004 12:33:06 +0000 Subject: ahc driver now borked in -current? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Jul 2004 21:51:01 -0000 OK, this is going to be a little hard to give all the right information for given that the symptoms I'm reporting don't even allow the box in question to get up far enough to generate useful debugging info, but I'll give it my best shot anyway. In short, this is an older dual PIII box with the on-board Adaptec Ultra/Wide controller (one of the older ASUS motherboards we all used to covet when they cost $600 a pop). Plugged into that controller are two IBM LVD drives, a CDROM drive and an iomega Jaz drive (remember those? :). Running a -current kernel from May 1st, the box works just fine albeit with one warning when it tries to probe the Jaz drive, which has no media in it. If you like, I can try stuffing a Jaz disk in there for giggles, but the error in question is benign in any case (see below). Using a kernel compiled on July 6th, however, I can't get any farther than the "Waiting 2 seconds for SCSI devices to settle" message you see below, then there's a long delay followed by a dump of the card state (sadly, to the screen rather than some non-perishable medium) and lots of whining about the number of SCBs which were just aborted. It continues looping in that way, resetting the controller and whining, forever. Unfortunately, the only other machine in this room is a Mac and those are notorious for not having serial cards, so it's not even going to be easy to wire up a serial console to this baby, but I can always give it a shot if someone thinks that data will be really helpful - I'll have to go get a USB serial adaptor or something. Anyway, here's the relevant boot messages from a *functioning* (May 1st) kernel. That's the last time the ahc driver worked on my system. Like I said, with the non-functioning kernel, we don't get any further than waiting for the SCSI devices to settle and then abort/looping: ahc0: port 0xb000-0xb0ff mem 0xdd800000 -0xdd800fff irq 14 at device 6.0 on pci0 ahc0: Reserved 0x100 bytes for rid 0x10 type 4 at 0xb000 ahc0: [GIANT-LOCKED] aic7890/91: Ultra2 Wide Channel A, SCSI Id=7, 32/253 SCBs ... Waiting 2 seconds for SCSI devices to settle SMP: AP CPU #1 Launched! da2 at ahc0 bus 0 target 5 lun 0 da2: Removable Direct Access SCSI-2 device da2: 20.000MB/s transfers (20.000MHz, offset 15) da2: Attempt to query device size failed: NOT READY, Medium not present cd0 at ahc0 bus 0 target 4 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 20.000MB/s transfers (20.000MHz, offset 16) cd0: Attempt to query device size failed: NOT READY, Medium not present da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 80.000MB/s transfers (40.000MHz, offset 15, 16bit), Tagged Queueing Enabled da0: 8715MB (17850000 512 byte sectors: 255H 63S/T 1111C) da1 at ahc0 bus 0 target 2 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 80.000MB/s transfers (40.000MHz, offset 15, 16bit), Tagged Queueing Enabled da1: 8715MB (17850000 512 byte sectors: 255H 63S/T 1111C) (da2:ahc0:0:5:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da2:ahc0:0:5:0): CAM Status: SCSI Status Error (da2:ahc0:0:5:0): SCSI Status: Check Condition (da2:ahc0:0:5:0): NOT READY asc:3a,0 (da2:ahc0:0:5:0): Medium not present (da2:ahc0:0:5:0): Unretryable error Opened disk da2 -> 6 (da2:ahc0:0:5:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da2:ahc0:0:5:0): CAM Status: SCSI Status Error (da2:ahc0:0:5:0): SCSI Status: Check Condition (da2:ahc0:0:5:0): NOT READY asc:3a,0 (da2:ahc0:0:5:0): Medium not present (da2:ahc0:0:5:0): Unretryable error Opened disk da2 -> 6 Mounting root from ufs:/dev/da0s1a -- Jordan K. Hubbard Engineering Manager, BSD technology group Apple Computer From owner-freebsd-current@FreeBSD.ORG Sun Jul 11 00:05:30 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AC96416A4CE for ; Sun, 11 Jul 2004 00:05:30 +0000 (GMT) Received: from mirapoint1.tis.cwru.edu (mirapoint1.TIS.CWRU.Edu [129.22.104.46]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6992843D45 for ; Sun, 11 Jul 2004 00:05:30 +0000 (GMT) (envelope-from jrh29@po.cwru.edu) Received: from [90.0.0.12] (pcp06937376pcs.nrockv01.md.comcast.net [69.138.13.44]) by mirapoint1.tis.cwru.edu (MOS 3.4.3-CR) with ESMTP id BYS69726 (AUTH jrh29); Sat, 10 Jul 2004 20:05:27 -0400 (EDT) Mime-Version: 1.0 (Apple Message framework v618) To: freebsd-current@freebsd.org Message-Id: Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="Apple-Mail-2--472033982" From: Justin Hibbits Date: Sat, 10 Jul 2004 20:05:15 -0400 Content-Transfer-Encoding: 7bit X-Pgp-Agent: GPGMail 1.0.2 X-Mailer: Apple Mail (2.618) X-Mailman-Approved-At: Sun, 11 Jul 2004 12:33:06 +0000 Subject: DVD/CD reading issues with -CURRENT from 2004-06-27 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Jul 2004 00:05:30 -0000 --Apple-Mail-2--472033982 Content-Type: multipart/mixed; boundary=Apple-Mail-1--472034003 --Apple-Mail-1--472034003 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; format=flowed Hi, I updated to -CURRENT a couple weeks ago, for various reasons, from 5.2.1, but now DVD and CD reading is flaking out. When trying to play DVDs with mplayer, they stop after a random amount of time, probably after reading a complete buffer. With 'dd', trying to create iso images of CDs, it stops after a random amount of data is copied. Attached is the backtrace of a 'dd' run. Specs of the system: 5.2-CURRENT as of 2004-06-27 Athlon XP 1800+ ASUS A7V266-E/A motherboard (VIA KT-266 chipset) The 2 drives I tested are: iomega Zip-CD CD-RW drive (acd0) Toshiba DVD-ROM (acd1) Any more info required, just ask. Additional, I'm not on the list, so if you could CC me, that'd be great, otherwise, I'll just check the archives. -Justin --Apple-Mail-1--472034003 Content-Transfer-Encoding: 7bit Content-Type: application/octet-stream; x-unix-mode=0644; name="trace.bad" Content-Disposition: attachment; filename=trace.bad db> trace 66932 sched_switch(c28c86e0) at sched_switch+0xac mi_switch(1) at mi_switch+0x212 sleepq_switch(ceb05ec8,e3438b20,c05f2b9a,ceb05ec8,0) at sleepq_switch+0xda sleepq_wait(ceb05ec8,0,0,0,c07d4940) at sleepq_wait+0xb msleep(ceb05ec8,c08b6e60,4c,c07cdb1d,0) at msleep+0x38e bwait(ceb05ec8,4c,c07cdb1d) at bwait+0x47 physio(c2602c00,e3438c88,7f0000,c0823c80,800) at physio+0x21d spec_read(e3438bec,e3438c38,c0642215,e3438bec,e3438c88) at spec_read+0x124 spec_vnoperate(e3438bec) at spec_vnoperate+0x13 vn_read(c263850c,e3438c88,c4108300,0,c28c86e0) at vn_read+0x17d dofileread(c28c86e0,c263850c,6,8050000,800) at dofileread+0xb0 read(c28c86e0,e3438d14,3,127,296) at read+0x3b syscall(2f,2f,2f,bfbfec14,bfbfec28) at syscall+0x217 Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (3, FreeBSD ELF32, read), eip = 0x280bd1d3, esp = 0xbfbfeb9c, ebp = 0xbfbfebb8 --- --Apple-Mail-1--472034003 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; format=flowed -- "One World, One Web, One Program" - Microsoft Promo Ad "Ein Volk, Ein Reich, Ein Fuhrer" - Adolf Hitler --Apple-Mail-1--472034003-- --Apple-Mail-2--472033982 content-type: application/pgp-signature; x-mac-type=70674453; name=PGP.sig content-description: This is a digitally signed message part content-disposition: inline; filename=PGP.sig content-transfer-encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (Darwin) iD8DBQFA8IRDqt29EJDZlM4RAg5RAJ9/4r9gkMUAENN2QCq7ReaGVfxAIACdHLAT G+s26wM6gG/klM39HJm9l9w= =kpqV -----END PGP SIGNATURE----- --Apple-Mail-2--472033982-- From owner-freebsd-current@FreeBSD.ORG Sun Jul 11 11:52:33 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 90DA216A4CE for ; Sun, 11 Jul 2004 11:52:33 +0000 (GMT) Received: from mout2.freenet.de (mout2.freenet.de [194.97.50.155]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6014D43D31 for ; Sun, 11 Jul 2004 11:52:33 +0000 (GMT) (envelope-from garyj@jennejohn.org) Received: from [194.97.55.190] (helo=mx6.freenet.de) by mout2.freenet.de with asmtp (Exim 4.390) id 1Bjcsg-0003Nw-4h; Sun, 11 Jul 2004 13:52:30 +0200 Received: from dff3b.d.pppool.de ([80.184.255.59] helo=peedub.jennejohn.org) by mx6.freenet.de with esmtp (TLSv1:AES256-SHA:256) (Exim 4.34 #3) id 1Bjcsf-0001yk-JR; Sun, 11 Jul 2004 13:52:30 +0200 Received: from peedub.jennejohn.org (localhost [127.0.0.1]) by peedub.jennejohn.org (8.12.11/8.11.6) with ESMTP id i6BBqRdd015659; Sun, 11 Jul 2004 13:52:27 +0200 (CEST) (envelope-from garyj@peedub.jennejohn.org) Message-Id: <200407111152.i6BBqRdd015659@peedub.jennejohn.org> X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4 To: sos@DeepCore.dk In-Reply-To: Message from =?ISO-8859-1?Q?S=F8ren_Schmidt?= of "Sat, 10 Jul 2004 12:05:39 +0200." <40EFBF73.9080904@DeepCore.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 11 Jul 2004 13:52:27 +0200 From: Gary Jennejohn X-Mailman-Approved-At: Sun, 11 Jul 2004 12:33:06 +0000 cc: Ion-Mihai Tetcu cc: Divacky Roman cc: current@FreeBSD.org Subject: Re: via 8237 and above-udma33 problems X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Jul 2004 11:52:33 -0000 =?ISO-8859-1?Q?S=F8ren_Schmidt?= writes: > Divacky Roman wrote: > >>>2) if not - how may I tell fbsd to initialize this drive (resp. the > >>>channel the drive is attached to) to udma33 instead of the default mode. > >>>I want to boot from that drive so I cannot use atacontrol or whatever > >>>since it would have hanged before I'd enter user-space system > >>>initialization > >> > >>Put hw.ata.ata_dma=0 > >>/boot/loader.conf > > > > > > I WANT dma! just not udma100 but udma33... so this is not what I want > > I think there should be some > > device.hints:dev.ata.adX.mode=blah > > You can just specify no dma in loader.conf and then use atacontrol to > set the wanted mode on each device later on in rc.local or whatever you > prefer... > Just a data point: On my amd64 system in 64-bit mode I had to define a bash alias to turn on DMA. Doing it in rc.local often resulted in so many DMA errors that the system hung. Probably due to the intense disk activity which happens during startup. Strangely enough, the same disk exhibits absolutely no DMA errors when I boot a 32-bit FreeBSD system. --- Gary Jennejohn / garyj[at]jennejohn.org gj[at]freebsd.org gj[at]denx.de From owner-freebsd-current@FreeBSD.ORG Sun Jul 11 13:13:00 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 91CAE16A4CE for ; Sun, 11 Jul 2004 13:13:00 +0000 (GMT) Received: from alpha.siliconlandmark.com (alpha.siliconlandmark.com [209.69.98.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 43B2443D3F for ; Sun, 11 Jul 2004 13:13:00 +0000 (GMT) (envelope-from andy@siliconlandmark.com) Received: from alpha.siliconlandmark.com (andy@localhost [127.0.0.1]) i6BDCwLT013465 for ; Sun, 11 Jul 2004 09:12:58 -0400 (EDT) (envelope-from andy@siliconlandmark.com) Received: from localhost (andy@localhost)i6BDCvOb013462 for ; Sun, 11 Jul 2004 09:12:58 -0400 (EDT) (envelope-from andy@siliconlandmark.com) X-Authentication-Warning: alpha.siliconlandmark.com: andy owned process doing -bs Date: Sun, 11 Jul 2004 09:12:57 -0400 (EDT) From: Andre Guibert de Bruet To: current@freebsd.org Message-ID: <20040711091153.F2496@alpha.siliconlandmark.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-MailScanner-Information: Please contact the ISP for more information X-MailScanner: Found to be clean Subject: Typo in UPDATING X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Jul 2004 13:13:00 -0000 Hi, I spotted the following this morning: 20040702: The native preemption has been added to the kernel scheduler. There is some report that ULE scheduler was broken in some machines and we encourage users using ULE schedluer either ^^^^^^^^^ stick with an known good kernel, or temporary switch to 4BSD scheduler as a workaround. Regards, > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/ > From owner-freebsd-current@FreeBSD.ORG Sun Jul 11 13:27:26 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B5BD216A4CE for ; Sun, 11 Jul 2004 13:27:26 +0000 (GMT) Received: from zaphod.nitro.dk (port324.ds1-khk.adsl.cybercity.dk [212.242.113.79]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3A25643D3F for ; Sun, 11 Jul 2004 13:27:26 +0000 (GMT) (envelope-from simon@zaphod.nitro.dk) Received: by zaphod.nitro.dk (Postfix, from userid 3000) id CDE9F119B1; Sun, 11 Jul 2004 15:27:24 +0200 (CEST) Date: Sun, 11 Jul 2004 15:27:24 +0200 From: "Simon L. Nielsen" To: Andre Guibert de Bruet Message-ID: <20040711132724.GA761@zaphod.nitro.dk> References: <20040711091153.F2496@alpha.siliconlandmark.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="FL5UXtIhxfXey3p5" Content-Disposition: inline In-Reply-To: <20040711091153.F2496@alpha.siliconlandmark.com> User-Agent: Mutt/1.5.6i cc: current@freebsd.org Subject: Re: Typo in UPDATING X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Jul 2004 13:27:26 -0000 --FL5UXtIhxfXey3p5 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2004.07.11 09:12:57 -0400, Andre Guibert de Bruet wrote: > I spotted the following this morning: >=20 > 20040702: > The native preemption has been added to the kernel scheduler. > There is some report that ULE scheduler was broken in some > machines and we encourage users using ULE schedluer either > ^^^^^^^^^ > stick with an known good kernel, or temporary switch to 4BSD > scheduler as a workaround. Fixed, thanks! --=20 Simon L. Nielsen FreeBSD Documentation Team --FL5UXtIhxfXey3p5 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFA8UA8h9pcDSc1mlERApbcAKCNrxLQsm1EpoxqnnMDNUGhhWJQkACfaLx9 vSs2exY9r0jWLRu89qRD4qU= =2D0o -----END PGP SIGNATURE----- --FL5UXtIhxfXey3p5-- From owner-freebsd-current@FreeBSD.ORG Sun Jul 11 14:16:54 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1C49E16A4CE for ; Sun, 11 Jul 2004 14:16:54 +0000 (GMT) Received: from alpha.siliconlandmark.com (alpha.siliconlandmark.com [209.69.98.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8987043D31 for ; Sun, 11 Jul 2004 14:16:53 +0000 (GMT) (envelope-from andy@siliconlandmark.com) Received: from alpha.siliconlandmark.com (andy@localhost [127.0.0.1]) i6BEGpIm013764; Sun, 11 Jul 2004 10:16:51 -0400 (EDT) (envelope-from andy@siliconlandmark.com) Received: from localhost (andy@localhost)i6BEGphK013761; Sun, 11 Jul 2004 10:16:51 -0400 (EDT) (envelope-from andy@siliconlandmark.com) X-Authentication-Warning: alpha.siliconlandmark.com: andy owned process doing -bs Date: Sun, 11 Jul 2004 10:16:51 -0400 (EDT) From: Andre Guibert de Bruet To: "Jordan K. Hubbard" In-Reply-To: <49011D34-D2BB-11D8-81E2-000393BB9222@queasyweasel.com> Message-ID: <20040711101340.Y2496@alpha.siliconlandmark.com> References: <49011D34-D2BB-11D8-81E2-000393BB9222@queasyweasel.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-MailScanner-Information: Please contact the ISP for more information X-MailScanner: Found to be clean cc: freebsd-current@freebsd.org Subject: Re: ahc driver now borked in -current? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Jul 2004 14:16:54 -0000 Jordan, I have seen something similar on one of my systems just a few days ago. ACPI turned out to be the culprit. It would boot with it disabled, and wouldn't with until I upgraded the BIOS. Since you have all of this "vintage" hardware around, you still have one of those pesky 3.5" floppy drives, right? ;-) Regards, Andy > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/ > On Sat, 10 Jul 2004, Jordan K. Hubbard wrote: > OK, this is going to be a little hard to give all the right information for > given that the symptoms I'm reporting don't even allow the box in question to > get up far enough to generate useful debugging info, but I'll give it my best > shot anyway. > > In short, this is an older dual PIII box with the on-board Adaptec Ultra/Wide > controller (one of the older ASUS motherboards we all used to covet when they > cost $600 a pop). Plugged into that controller are two IBM LVD drives, a > CDROM drive and an iomega Jaz drive (remember those? :). > > Running a -current kernel from May 1st, the box works just fine albeit with > one warning when it tries to probe the Jaz drive, which has no media in it. > If you like, I can try stuffing a Jaz disk in there for giggles, but the > error in question is benign in any case (see below). Using a kernel compiled > on July 6th, however, I can't get any farther than the "Waiting 2 seconds for > SCSI devices to settle" message you see below, then there's a long delay > followed by a dump of the card state (sadly, to the screen rather than some > non-perishable medium) and lots of whining about the number of SCBs which > were just aborted. It continues looping in that way, resetting the > controller and whining, forever. > > Unfortunately, the only other machine in this room is a Mac and those are > notorious for not having serial cards, so it's not even going to be easy to > wire up a serial console to this baby, but I can always give it a shot if > someone thinks that data will be really helpful - I'll have to go get a USB > serial adaptor or something. > > Anyway, here's the relevant boot messages from a *functioning* (May 1st) > kernel. That's the last time the ahc driver worked on my system. Like I > said, with the non-functioning kernel, we don't get any further than waiting > for the SCSI devices to settle and then abort/looping: > > ahc0: port 0xb000-0xb0ff mem > 0xdd800000 > -0xdd800fff irq 14 at device 6.0 on pci0 > ahc0: Reserved 0x100 bytes for rid 0x10 type 4 at 0xb000 > ahc0: [GIANT-LOCKED] > aic7890/91: Ultra2 Wide Channel A, SCSI Id=7, 32/253 SCBs > ... > Waiting 2 seconds for SCSI devices to settle > SMP: AP CPU #1 Launched! > da2 at ahc0 bus 0 target 5 lun 0 > da2: Removable Direct Access SCSI-2 device > da2: 20.000MB/s transfers (20.000MHz, offset 15) > da2: Attempt to query device size failed: NOT READY, Medium not present > cd0 at ahc0 bus 0 target 4 lun 0 > cd0: Removable CD-ROM SCSI-2 device > cd0: 20.000MB/s transfers (20.000MHz, offset 16) > cd0: Attempt to query device size failed: NOT READY, Medium not present > da0 at ahc0 bus 0 target 0 lun 0 > da0: Fixed Direct Access SCSI-2 device > da0: 80.000MB/s transfers (40.000MHz, offset 15, 16bit), Tagged Queueing > Enabled > da0: 8715MB (17850000 512 byte sectors: 255H 63S/T 1111C) > da1 at ahc0 bus 0 target 2 lun 0 > da1: Fixed Direct Access SCSI-2 device > da1: 80.000MB/s transfers (40.000MHz, offset 15, 16bit), Tagged Queueing > Enabled > da1: 8715MB (17850000 512 byte sectors: 255H 63S/T 1111C) > (da2:ahc0:0:5:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 > (da2:ahc0:0:5:0): CAM Status: SCSI Status Error > (da2:ahc0:0:5:0): SCSI Status: Check Condition > (da2:ahc0:0:5:0): NOT READY asc:3a,0 > (da2:ahc0:0:5:0): Medium not present > (da2:ahc0:0:5:0): Unretryable error > Opened disk da2 -> 6 > (da2:ahc0:0:5:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 > (da2:ahc0:0:5:0): CAM Status: SCSI Status Error > (da2:ahc0:0:5:0): SCSI Status: Check Condition > (da2:ahc0:0:5:0): NOT READY asc:3a,0 > (da2:ahc0:0:5:0): Medium not present > (da2:ahc0:0:5:0): Unretryable error > Opened disk da2 -> 6 > Mounting root from ufs:/dev/da0s1a > > -- > Jordan K. Hubbard > Engineering Manager, BSD technology group > Apple Computer From owner-freebsd-current@FreeBSD.ORG Sun Jul 11 14:32:07 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 287A616A4CE for ; Sun, 11 Jul 2004 14:32:07 +0000 (GMT) Received: from hrothgar.unconceived.net (rrcs-se-24-73-170-14.biz.rr.com [24.73.170.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6CD0243D1D for ; Sun, 11 Jul 2004 14:32:04 +0000 (GMT) (envelope-from jhandvil@tampabay.rr.com) Received: from localhost (localhost [IPv6:::1])i6BEhLWm000653; Sun, 11 Jul 2004 10:43:22 -0400 (EDT) (envelope-from jhandvil@tampabay.rr.com) From: jhandvil To: Ivan Voras Date: Sun, 11 Jul 2004 10:43:21 -0400 User-Agent: KMail/1.5.4 References: <200407082032.10210.jhandvil@tampabay.rr.com> <40F125BB.6030603@fer.hr> In-Reply-To: <40F125BB.6030603@fer.hr> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200407111043.21173.jhandvil@tampabay.rr.com> cc: freebsd-current@freebsd.org Subject: Re: 5.2.1 p9 --> 5.2 current 20040708 upgrade ATA_IDENTIFY no interrupt X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: jhandvil@tampabay.rr.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Jul 2004 14:32:07 -0000 On Sunday 11 July 2004 07:34 am, Ivan Voras wrote: > jhandvil wrote: > > Just upgraded from 5.2.1 p9 to 5.2-current. Received the following error > > during boot (copied by hand, please excuse typo's): > > > > ata0-master: FAILURE - ATA_IDENTIFY no interrupt > > ata0-master: FAILURE - ATA_IDENTIFY no interrupt > > Mounting root from ufs:/dev/ad0s1a > > setrootbyname failed > > ffs_mountroot: can't find rootvp > > Root mount failed: 6 > > I have a very similar situation at my machine. Could you try toggling > WITNESS in the kernel config and report to the list if there are any > changes? Thanks for the fast response. I toggled turned off WITNESS (and turned on DDB), and I got the same response. I tried digging some more. I know that there was an issue earlier with the via 8237 and dma, so I tried disabling dma (hw.ata.ata_dma=0). This had no effect. I'll attempt to dig around in the PCI driver and the ata driver a little more and see if I can add some traces around the interrupt assignment. Any additional suggestions would be much appreciated. Great Cthulu sig. I'm a bit of a H.P. Lovecraft fan myself. Thanks, Justin From owner-freebsd-current@FreeBSD.ORG Sun Jul 11 14:39:56 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1485B16A4CE for ; Sun, 11 Jul 2004 14:39:56 +0000 (GMT) Received: from web50703.mail.yahoo.com (web50703.mail.yahoo.com [206.190.38.101]) by mx1.FreeBSD.org (Postfix) with SMTP id CDD2843D1D for ; Sun, 11 Jul 2004 14:39:55 +0000 (GMT) (envelope-from w8hdkim@yahoo.com) Message-ID: <20040711143955.54447.qmail@web50703.mail.yahoo.com> Received: from [68.40.135.37] by web50703.mail.yahoo.com via HTTP; Sun, 11 Jul 2004 07:39:55 PDT Date: Sun, 11 Jul 2004 07:39:55 -0700 (PDT) From: Kim Culhan To: freebsd-current@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: -current kernel panics at boot X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Jul 2004 14:39:56 -0000 Is this a known situation? Can provide more details if they would be useful tnx -kim __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From owner-freebsd-current@FreeBSD.ORG Sun Jul 11 15:08:13 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1C3B916A4CE for ; Sun, 11 Jul 2004 15:08:13 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id A5C4143D46 for ; Sun, 11 Jul 2004 15:08:12 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.0.11] (junior-wifi.samsco.home [192.168.0.11]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id i6BFDMhi019023; Sun, 11 Jul 2004 09:13:22 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <40F157C2.8010400@samsco.org> Date: Sun, 11 Jul 2004 09:07:46 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7) Gecko/20040702 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Jordan K. Hubbard" References: <49011D34-D2BB-11D8-81E2-000393BB9222@queasyweasel.com> In-Reply-To: <49011D34-D2BB-11D8-81E2-000393BB9222@queasyweasel.com> X-Enigmail-Version: 0.84.2.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: freebsd-current@freebsd.org Subject: Re: ahc driver now borked in -current? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Jul 2004 15:08:13 -0000 Jordan, Having the dump card state message will be really useful. You might want to examine the message and see if mentions anything about interrupts not working, or 'SCB already completed'. BTW, sending problem reports like this to freebsd-scsi@ or directly to myself of Justin will improve your chances of getting noticed =-) Scott Jordan K. Hubbard wrote: > OK, this is going to be a little hard to give all the right information > for given that the symptoms I'm reporting don't even allow the box in > question to get up far enough to generate useful debugging info, but > I'll give it my best shot anyway. > > In short, this is an older dual PIII box with the on-board Adaptec > Ultra/Wide controller (one of the older ASUS motherboards we all used to > covet when they cost $600 a pop). Plugged into that controller are two > IBM LVD drives, a CDROM drive and an iomega Jaz drive (remember those? :). > > Running a -current kernel from May 1st, the box works just fine albeit > with one warning when it tries to probe the Jaz drive, which has no > media in it. If you like, I can try stuffing a Jaz disk in there for > giggles, but the error in question is benign in any case (see below). > Using a kernel compiled on July 6th, however, I can't get any farther > than the "Waiting 2 seconds for SCSI devices to settle" message you see > below, then there's a long delay followed by a dump of the card state > (sadly, to the screen rather than some non-perishable medium) and lots > of whining about the number of SCBs which were just aborted. It > continues looping in that way, resetting the controller and whining, > forever. > > Unfortunately, the only other machine in this room is a Mac and those > are notorious for not having serial cards, so it's not even going to be > easy to wire up a serial console to this baby, but I can always give it > a shot if someone thinks that data will be really helpful - I'll have to > go get a USB serial adaptor or something. > > Anyway, here's the relevant boot messages from a *functioning* (May 1st) > kernel. That's the last time the ahc driver worked on my system. > Like I said, with the non-functioning kernel, we don't get any further > than waiting for the SCSI devices to settle and then abort/looping: > > ahc0: port 0xb000-0xb0ff mem > 0xdd800000 > -0xdd800fff irq 14 at device 6.0 on pci0 > ahc0: Reserved 0x100 bytes for rid 0x10 type 4 at 0xb000 > ahc0: [GIANT-LOCKED] > aic7890/91: Ultra2 Wide Channel A, SCSI Id=7, 32/253 SCBs > ... > Waiting 2 seconds for SCSI devices to settle > SMP: AP CPU #1 Launched! > da2 at ahc0 bus 0 target 5 lun 0 > da2: Removable Direct Access SCSI-2 device > da2: 20.000MB/s transfers (20.000MHz, offset 15) > da2: Attempt to query device size failed: NOT READY, Medium not present > cd0 at ahc0 bus 0 target 4 lun 0 > cd0: Removable CD-ROM SCSI-2 device > cd0: 20.000MB/s transfers (20.000MHz, offset 16) > cd0: Attempt to query device size failed: NOT READY, Medium not present > da0 at ahc0 bus 0 target 0 lun 0 > da0: Fixed Direct Access SCSI-2 device > da0: 80.000MB/s transfers (40.000MHz, offset 15, 16bit), Tagged Queueing > Enabled > da0: 8715MB (17850000 512 byte sectors: 255H 63S/T 1111C) > da1 at ahc0 bus 0 target 2 lun 0 > da1: Fixed Direct Access SCSI-2 device > da1: 80.000MB/s transfers (40.000MHz, offset 15, 16bit), Tagged Queueing > Enabled > da1: 8715MB (17850000 512 byte sectors: 255H 63S/T 1111C) > (da2:ahc0:0:5:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 > (da2:ahc0:0:5:0): CAM Status: SCSI Status Error > (da2:ahc0:0:5:0): SCSI Status: Check Condition > (da2:ahc0:0:5:0): NOT READY asc:3a,0 > (da2:ahc0:0:5:0): Medium not present > (da2:ahc0:0:5:0): Unretryable error > Opened disk da2 -> 6 > (da2:ahc0:0:5:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 > (da2:ahc0:0:5:0): CAM Status: SCSI Status Error > (da2:ahc0:0:5:0): SCSI Status: Check Condition > (da2:ahc0:0:5:0): NOT READY asc:3a,0 > (da2:ahc0:0:5:0): Medium not present > (da2:ahc0:0:5:0): Unretryable error > Opened disk da2 -> 6 > Mounting root from ufs:/dev/da0s1a > > -- > Jordan K. Hubbard > Engineering Manager, BSD technology group > Apple Computer > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Sun Jul 11 15:14:19 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2643416A4CE for ; Sun, 11 Jul 2004 15:14:19 +0000 (GMT) Received: from av5-2-sn1.fre.skanova.net (av5-2-sn1.fre.skanova.net [81.228.11.112]) by mx1.FreeBSD.org (Postfix) with ESMTP id 355BE43D2F for ; Sun, 11 Jul 2004 15:14:18 +0000 (GMT) (envelope-from daniel_k_eriksson@telia.com) Received: by av5-2-sn1.fre.skanova.net (Postfix, from userid 502) id 8AB6A37E5B; Sun, 11 Jul 2004 17:14:17 +0200 (CEST) Received: from smtp3-2-sn1.fre.skanova.net (smtp3-2-sn1.fre.skanova.net [81.228.11.164]) by av5-2-sn1.fre.skanova.net (Postfix) with ESMTP id 7B30137E51 for ; Sun, 11 Jul 2004 17:14:17 +0200 (CEST) Received: from gadget (h130n1fls11o822.telia.com [213.64.66.130]) by smtp3-2-sn1.fre.skanova.net (Postfix) with ESMTP id 55F8837E4C for ; Sun, 11 Jul 2004 17:14:17 +0200 (CEST) From: "Daniel Eriksson" To: Date: Sun, 11 Jul 2004 17:14:31 +0200 Organization: Home Message-ID: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_0018_01C4676A.8ABF1770" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 In-Reply-To: <49011D34-D2BB-11D8-81E2-000393BB9222@queasyweasel.com> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 Importance: Normal Subject: RE: ahc driver now borked in -current? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Jul 2004 15:14:19 -0000 This is a multi-part message in MIME format. ------=_NextPart_000_0018_01C4676A.8ABF1770 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Jordan K. Hubbard wrote: > OK, this is going to be a little hard to give all the right=20 > information=20 > for given that the symptoms I'm reporting don't even allow the box in=20 > question to get up far enough to generate useful debugging info, but=20 > I'll give it my best shot anyway. Here's a me-too report with a slight twist: Hardware: --------- ASUS P2B-DS motherboard with 2 x 700MHz P3 and 1GB ECC memory 2 x 3COM 3c905C-TX NICs (xl driver) 1 x Intel 82559 Pro/100 NIC (fxp driver) 1 x HighPoint 1540 SATA card (HPT374 chipset, default ata driver) - no SCSI devices connected to the onboard Adaptec aic7890/91 Ultra2 = SCSI controller - 9GB ATA disc hooked up to the onboard Intel PIIX4 UDMA33 controller = (boot disc) - 4 x 120GB Maxtor SATA discs hooked up to the HighPoint card (vinum = RAID-5 array) Software, semi-working configuration: ------------------------------------- FreeBSD 5-CURRENT, 2004.06.29.09.00.00 SHED_4BSD, SMP+apic, CPUTYPE?=3Dp3 (but no custom CFLAGS/COPTFLAGS) ACPI enabled This combination seems pretty stable. I have never been able to boot = with the SATA discs connected (machine hangs hard just before the discs = should be listed/probed), but booting with no SATA discs and then plugging them in after boot and running "atacontrol reinit X" works fine. Software, non-working configuration: ------------------------------------ FreeBSD 5-CURRENT, 2004.07.09.00.00.00 SHED_4BSD, SMP+apic, CPUTYPE?=3Dp3 (but no custom CFLAGS/COPTFLAGS) - With ACPI enabled the machine reboots as soon as it starts to probe = for devices/cards (very early in the boot message). I don't have a serial console so I don't know exactly what scrolls by, but it looks like a = panic message during interrupt routing followed immediately by a reboot. - With ACPI disabled the machine boots (provided no SATA discs are connected, see above), but hangs with some message about "IPI stuck" = during heavy load (sorry, I wasn't around to take down the exact message). Attached is the dmesg from the semi-working configuration. /Daniel Eriksson ------=_NextPart_000_0018_01C4676A.8ABF1770 Content-Type: text/plain; name="dmesg.txt" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="dmesg.txt" 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: Tue Jun 29 19:11:13 CEST 2004 root@sentinel.lokalen.zapto.org:/usr/obj/usr/src/sys/SENTINEL Preloaded elf kernel "/boot/kernel/kernel" at 0xc08b6000. Preloaded elf module "/boot/kernel/acpi.ko" at 0xc08b6244. ACPI APIC Table: Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel Pentium III (701.59-MHz 686-class CPU) Origin =3D "GenuineIntel" Id =3D 0x681 Stepping =3D 1 = Features=3D0x383fbff real memory =3D 1073729536 (1023 MB) avail memory =3D 1041281024 (993 MB) FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 1 cpu1 (AP): APIC ID: 0 ioapic0 irqs 0-23 on motherboard random: Pentium Pro MTRR support enabled npx0: [FAST] npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard acpi0: Overriding SCI Interrupt from IRQ 9 to IRQ 20 acpi0: [GIANT-LOCKED] pcibios: BIOS version 2.10 acpi0: Power Button (fixed) Timecounter "ACPI-safe" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0xe408-0xe40b on acpi0 cpu0: on acpi0 cpu1: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 agp0: mem = 0xe6000000-0xe7ffffff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pcib1: slot 0 INTA is routed to irq 16 pci1: at device 0.0 (no driver attached) isab0: at device 4.0 on pci0 isa0: on isab0 atapci0: port = 0xb800-0xb80f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 4.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: port 0xb400-0xb41f at = device 4.2 on pci0 uhci0: [GIANT-LOCKED] 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 pci0: at device 4.3 (no driver attached) ahc0: port 0xb000-0xb0ff mem = 0xe3000000-0xe3000fff irq 19 at device 6.0 on pci0 ahc0: [GIANT-LOCKED] aic7890/91: Ultra2 Wide Channel A, SCSI Id=3D15, 32/253 SCBs atapci1: port = 0x9400-0x94ff,0x9800-0x9803,0xa000-0xa007,0xa400-0xa403,0xa800-0xa807 = irq 19 at=20 device 9.0 on pci0 ata2: at 0xa800 on atapci1 ata3: at 0xa000 on atapci1 atapci2: port = 0x7800-0x78ff,0x8000-0x8003,0x8400-0x8407,0x8800-0x8803,0x9000-0x9007 = irq 19 at=20 device 9.1 on pci0 ata4: at 0x9000 on atapci2 ata5: at 0x8400 on atapci2 xl0: <3Com 3c905C-TX Fast Etherlink XL> port 0x7400-0x747f mem = 0xe2800000-0xe280007f irq 18 at device 10.0 on pci0 miibus0: on xl0 xlphy0: <3c905C 10/100 internal PHY> on miibus0 xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto xl0: Ethernet address: 00:01:02:73:f4:f5 xl0: [GIANT-LOCKED] xl1: <3Com 3c905C-TX Fast Etherlink XL> port 0x7000-0x707f mem = 0xe2000000-0xe200007f irq 17 at device 11.0 on pci0 miibus1: on xl1 xlphy1: <3c905C 10/100 internal PHY> on miibus1 xlphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto xl1: Ethernet address: 00:50:da:8d:d2:af xl1: [GIANT-LOCKED] fxp0: port 0x6800-0x683f mem = 0xe1000000-0xe10fffff,0xe1800000-0xe1800fff irq 16 at device 12.0 on = pci0 miibus2: on fxp0 inphy0: on miibus2 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp0: Ethernet address: 00:03:47:09:6f:51 fxp0: [GIANT-LOCKED] fdc0: port = 0x3f7,0x3f2-0x3f5 irq 6 drq 2 on acpi0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model Generic PS/2 mouse, device ID 0 orm0: