From owner-freebsd-current@FreeBSD.ORG Sun Jan 4 00:29: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 3BBCA16A4CE for ; Sun, 4 Jan 2004 00:29:24 -0800 (PST) Received: from alpha.siliconlandmark.com (alpha.siliconlandmark.com [209.69.98.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id CCED543D46 for ; Sun, 4 Jan 2004 00:29:22 -0800 (PST) (envelope-from andy@siliconlandmark.com) Received: from alpha.siliconlandmark.com (localhost [127.0.0.1]) i048TKZV024128; Sun, 4 Jan 2004 03:29:20 -0500 (EST) (envelope-from andy@siliconlandmark.com) Received: from localhost (andy@localhost)i048TJqr024125; Sun, 4 Jan 2004 03:29:20 -0500 (EST) (envelope-from andy@siliconlandmark.com) X-Authentication-Warning: alpha.siliconlandmark.com: andy owned process doing -bs Date: Sun, 4 Jan 2004 03:29:19 -0500 (EST) From: Andre Guibert de Bruet To: Vaidas Damosevicius In-Reply-To: <20040103184643.95BC03AE91@mail.if.lt> Message-ID: <20040104022559.W9356@alpha.siliconlandmark.com> References: <20040103184643.95BC03AE91@mail.if.lt> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-MailScanner-Information: Please contact the ISP for more information X-MailScanner: Found to be clean cc: freebsd-current@freebsd.org Subject: Re: ACPI panic 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, 04 Jan 2004 08:29:24 -0000 On Sat, 3 Jan 2004, Vaidas Damosevicius wrote: > 5.2-CURRENT (I made cvsup/kernel few minutes ago) panics on HP > Compaq nx7000 with ACPI. Without ACPI everything works fine. > > kernel trap 12 with interrupts disabled > > Fatal trap 12: page fault while in kernel mode > cpuid = 0; apic id = 00 > fault virtual address = 0x6c > fault code = supervisor read, page not present > instruction pointer = 0x8:0xc0654f3d > stack pointer = 0x10:0xdfa587ec > frame pointer = 0x10:0xdfa587f0 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags = resume, IOPL = 0 > current process = 7 (acpi_task1) > trap number = 12 > panic: page fault > cpuid = 0; > > syncing disks, buffers remaining... > done > Uptime: 1s > Shutting down ACPI You'll need to provide more information than this for a proper diagnosis: - Kernel config is GENERIC? Custom? - Can you reproduce this panic with kernel debugging options turned on? - SMP system? - Stack trace? - Crash dump? - dmesg? - Contents of /boot/loader.conf? Regards, > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/ > From owner-freebsd-current@FreeBSD.ORG Sun Jan 4 00:59:39 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 1737316A4CE for ; Sun, 4 Jan 2004 00:59:39 -0800 (PST) Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 52C9B43D46 for ; Sun, 4 Jan 2004 00:59:37 -0800 (PST) (envelope-from truckman@FreeBSD.org) Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.12.9p2/8.12.9) with ESMTP id i048xR7E008500; Sun, 4 Jan 2004 00:59:32 -0800 (PST) (envelope-from truckman@FreeBSD.org) Message-Id: <200401040859.i048xR7E008500@gw.catspoiler.org> Date: Sun, 4 Jan 2004 00:59:27 -0800 (PST) From: Don Lewis To: dejan.lesjak@ijs.si In-Reply-To: <200401040717.42334.dejan.lesjak@ijs.si> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii cc: ryans@gamersimpact.com cc: silby@silby.com cc: freebsd-current@FreeBSD.org Subject: Re: 5.2-RC oerrs and collisions on dc0 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, 04 Jan 2004 08:59:39 -0000 On 4 Jan, Dejan Lesjak wrote: > On Sunday 04 of January 2004 06:33, Don Lewis wrote: >> On 4 Jan, Dejan Lesjak wrote: >> > Hello again, >> > With this line commented out, I still get both errors and collisions, >> > twice as much collisions as errors. On another occasion, I also added two >> > printf lines in here: >> > if (txstat & DC_TXSTAT_EXCESSCOLL) >> > ifp->if_collisions++; >> > printf("EXCESSCOLL\n"); >> > if (txstat & DC_TXSTAT_LATECOLL) >> > ifp->if_collisions++; >> > printf("LATECOLL\n"); >> > and I constantly get both of those, so this would be where counters go up >> > if this helps in any way. >> >> The driver might be less verbose if you added some braces here. > > Hm.. Yes I did that, however I was writing mail relying on memory which seems > to have failed me. When errors occur in full duplex mode, you might want to print the value of CSR_READ_4(sc, DC_NETCFG) to verify that the full duplex bit is actually set. From owner-freebsd-current@FreeBSD.ORG Sun Jan 4 01:49:20 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 571C116A4CE for ; Sun, 4 Jan 2004 01:49:20 -0800 (PST) Received: from mail.cruzio.com (mail.cruzio.com [63.249.95.37]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6B67B43D2F for ; Sun, 4 Jan 2004 01:49:19 -0800 (PST) (envelope-from slazar@cruzio.com) Received: from seano (dsl3-63-249-68-90.cruzio.com [63.249.68.90]) by mail.cruzio.com with SMTP id i049nJNg092280 for ; Sun, 4 Jan 2004 01:49:19 -0800 (PST) Message-ID: <001b01c3d2a8$0e952560$6401a8c0@seano> From: "Sean Lazar" To: Date: Sun, 4 Jan 2004 01:49:28 -0800 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: ACPI and Gateway 400sd4 laptop 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, 04 Jan 2004 09:49:20 -0000 I have a Gateway 400SD4 laptop that I am having thermal issues with in FreeBSD-CURRENT. The two-speed fan dosen't seem to come on. With ACPI on, after the system has been running a little while and has warmed up, if I turn off acpi with "acpiconf -d" the fan will kick on immediately. After that the fan appears to behave normally, turning on and off when necessary. If the laptop boots warm with the fan on, it will shut off when it gets cool but it won't come back on again. There is a second fan on this model that seems to work fine, but it dosen't do enough to cool down the system. My original asl file can be found here: http://members.cruzio.com/~slazar/gw400sd4/gw400sd4.asl. I tried editing it and removing the OS-dependent areas and if statements in the TZ section and using a custom dsdt file with acpi_dsdt_load="YES" and acpi_dsdt_name="/boot/DSDT.asl" in my /boot/loader.conf. I also tried hw.acpi.os_name="Microsoft Windows NT" in /boot/loader.conf and other OS names as well. I also tried debug.acpi.disable="thermal". What else can I try? Any ACPI patches out there? Or perhaps I can sucessfully edit this file with some hints :) I've read the Intel ACPI spec and I am starting to understand the format... My boot messages can be found here: http://members.cruzio.com/~slazar/gw400sd4/messages Yes it is from 5.2-RC2 but I get the same messages in -CURRENT Cheers, Sean From owner-freebsd-current@FreeBSD.ORG Sun Jan 4 02:15: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 AC00F16A4CE; Sun, 4 Jan 2004 02:15:36 -0800 (PST) Received: from niobe.ijs.si (mail.ijs.si [193.2.4.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5802043D48; Sun, 4 Jan 2004 02:15:33 -0800 (PST) (envelope-from dejan.lesjak@ijs.si) Received: from localhost (localhost.ijs.si [127.0.0.1]) by niobe.ijs.si (Postfix) with ESMTP id 601CC1DE188; Sun, 4 Jan 2004 11:15:32 +0100 (CET) Received: from niobe.ijs.si ([193.2.4.66]) by localhost (niobe.ijs.si [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 99977-02; Sun, 4 Jan 2004 11:15:30 +0100 (CET) Received: from rincewind.ijs.si (rincewind.ijs.si [193.2.4.137]) by niobe.ijs.si (Postfix) with ESMTP id 4D6EE1DE19C; Sun, 4 Jan 2004 11:15:30 +0100 (CET) From: Dejan Lesjak To: Don Lewis Date: Sun, 4 Jan 2004 11:15:29 +0100 User-Agent: KMail/1.5.94 References: <200401040859.i048xR7E008500@gw.catspoiler.org> In-Reply-To: <200401040859.i048xR7E008500@gw.catspoiler.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200401041115.29188.dejan.lesjak@ijs.si> X-Virus-Scanned: by amavisd-new / Sophos+Sophie at ijs.si cc: ryans@gamersimpact.com cc: silby@silby.com cc: freebsd-current@FreeBSD.org Subject: Re: 5.2-RC oerrs and collisions on dc0 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, 04 Jan 2004 10:15:36 -0000 On Sunday 04 of January 2004 09:59, Don Lewis wrote: > When errors occur in full duplex mode, you might want to print the value > of > CSR_READ_4(sc, DC_NETCFG) > to verify that the full duplex bit is actually set. I put this right after if (txstat & DC_TXSTAT_ERRSUM) { ifp->if_oerrors++; it gives me 0x338c2203 and DC_NETCFG_FULLDUPLEX is 0x00000200, so as I understand full-duplex is set. Also none of previous two suggestions made difference. I also found this documentation: ftp://download.intel.com/design/network/manuals/27807401.pdf if it helps. Thanks for the suggestions, i'll try fiddling some more with this a bit later (must get some sleep). Dejan From owner-freebsd-current@FreeBSD.ORG Sun Jan 4 04:31:42 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 4500716A4CF for ; Sun, 4 Jan 2004 04:31:42 -0800 (PST) Received: from s1.vhost.cz (s1.vhost.cz [195.39.16.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7381643D4C for ; Sun, 4 Jan 2004 04:31:40 -0800 (PST) (envelope-from konfer@mikulas.com) Received: (qmail 7490 invoked by uid 89); 4 Jan 2004 13:31:39 +0100 Received: from unknown (HELO mikulas.com) (jiri@mikulas.com@195.122.218.78) by s1.vhost.cz with AES256-SHA encrypted SMTP; 4 Jan 2004 13:31:39 +0100 Message-ID: <3FF807AA.4030106@mikulas.com> Date: Sun, 04 Jan 2004 13:31:38 +0100 From: Jiri Mikulas User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.5) Gecko/20031025 X-Accept-Language: cs, en-us, en MIME-Version: 1.0 To: freebsd-current@freebsd.org X-Enigmail-Version: 0.76.7.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit Subject: PANIC route.c:1310 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, 04 Jan 2004 12:31:42 -0000 Hi, already reported ? FreeBSD 5.2-CURRENT #1: Sat Jan 3 10:50:22 CET 2004 when I'm reloading ARP table about 200 entries /usr/sbin/arp -and /usr/sbin/arp -f /etc/arp.conf it hangs on: panic: lock (sleep mutex) rtentry not locked @ /usr/src/sys/net/route.c:1310 Debugger("panic") Stopped at Debugger+0x54: xchgl %ebx,in_Debugger.0 Jiri From owner-freebsd-current@FreeBSD.ORG Sun Jan 4 00:42: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 5453416A4CE for ; Sun, 4 Jan 2004 00:42:24 -0800 (PST) Received: from anor.ics.muni.cz (anor.ics.muni.cz [147.251.4.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id A96CD43D39 for ; Sun, 4 Jan 2004 00:42:22 -0800 (PST) (envelope-from hopet@ics.muni.cz) Received: from kloboucek (p0155.as-l041.contactel.cz [194.108.232.155]) (user=hopet mech=LOGIN bits=0) by anor.ics.muni.cz (8.12.1/8.12.1) with ESMTP id i048fvpk021903 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Sun, 4 Jan 2004 09:42:11 +0100 From: "Petr Holub" To: "M. Warner Losh" Date: Sun, 4 Jan 2004 09:42:24 +0100 Message-ID: <02f001c3d29e$ad39d4e0$42e86cc2@kloboucek> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 In-Reply-To: <20040103.122837.65494976.imp@bsdimp.com> X-Muni-Spam-TestIP: 194.108.232.155 X-Muni-Virus-Test: Clean X-Mailman-Approved-At: Sun, 04 Jan 2004 05:00:55 -0800 cc: current@freebsd.org Subject: RE: wi0 fails to wake up 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, 04 Jan 2004 08:42:24 -0000 > The cardbus bridge isn't waking up quite right, otherwise you won't > see one of these messages. It is a 'Can't happen' message. OK. Is there anything I can do to help you sort it out? Thanks, Petr From owner-freebsd-current@FreeBSD.ORG Sun Jan 4 05:24:06 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 B67CB16A4CE for ; Sun, 4 Jan 2004 05:24:06 -0800 (PST) Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id DFDD243D1D for ; Sun, 4 Jan 2004 05:24:02 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from gamplex.bde.org (katana.zip.com.au [61.8.7.246]) by mailman.zeta.org.au (8.9.3p2/8.8.7) with ESMTP id AAA03338; Mon, 5 Jan 2004 00:23:47 +1100 Date: Mon, 5 Jan 2004 00:23:46 +1100 (EST) From: Bruce Evans X-X-Sender: bde@gamplex.bde.org To: Doug White In-Reply-To: <20040102113152.V57649@carver.gumbysoft.com> Message-ID: <20040104222635.S631@gamplex.bde.org> References: <20040101205511.GM42542@0lsen.net> <20040102001529.3B0AB5D04@ptavv.es.net> <20040102113152.V57649@carver.gumbysoft.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Clint Olsen cc: freebsd-current@freebsd.org Subject: Re: Installed 5.2RC from CDROM, fails to boot in manager 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, 04 Jan 2004 13:24:06 -0000 On Fri, 2 Jan 2004, Doug White wrote: > On Thu, 1 Jan 2004, Clint Olsen wrote: > > > On Jan 01, Kevin Oberman wrote: > > > > > > Try re-writing the MBR. Use the fixit disk (ISO-2) to bring up th live > > > system. Then enter the command: boot0cfg -o packet -B ad0 > > > > > > There are other options you might want to use, but this should work. > > > (Read the man page.) > > > > Thanks for the suggestion. Incidentally, I did finally get the darn system > > to boot, but I had to allow fdisk to determine the slices itself. I > > checked my old 4.7 machine, and apparently I didn't pay much attention, but > > it also made 2 unused slices at each ends of the disk with the FreeBSD > > slice in the middle. I'd sure like to know why the blank slice is required > > at the end of the disk... A blank slice is not required. Only one slice is required for FreeBSD[1-4] to be able to determine the geometry, but it must end on a cylinder boundary as explained in the next paragraph. (Note that this is a boundary for virtual cylinder except possibly on 10-20 year old drives. The BIOS has its own idea of cylinders, and this is mostly unrelated to both physical cylinders and the manufacturer's virtual cylinders. For me, it's always just whatever I configure the BIOS to.) > Cylinder alignment. > > FreeBSD's fdisk has always had a heck of a time getting disk geometry to > jive with the BIOS. The best way to avoid this sort of problem is to > write the initial partition table with DOS FDISK by creating a dos > partition that you delete in FreeBSD later. Since DOS FDISK is using BIOS > vectors to figure out geometry and such, it get it right as far as the > BIOS is concerned and thats what matters to boot0. This seems to have been "fixed" by GEOM in -current. FreeBSD fdisk now apparently almost always gets the geometry wrong by not even looking at the existing partitions, so creating a partition using DOS FDISK doesn't help. E.g., for fdisk(8): Correct output with a de-GEOMed kernel (same as for a pre-GEOM kernel and a RELENG_4 kernel): % ******* Working on device /dev/ad0 ******* % parameters extracted from in-core disklabel are: % cylinders=784 heads=255 sectors/track=63 (16065 blks/cyl) % % parameters to be used for BIOS calculations are: % cylinders=784 heads=255 sectors/track=63 (16065 blks/cyl) % % Media sector size is 512 % Warning: BIOS sector numbering starts with sector 1 % Information from DOS bootblock is: % The data for partition 1 is: % sysid 11 (0x0b),(DOS or Windows 95 with 32 bit FAT) % start 63, size 2104452 (1027 Meg), flag 0 % beg: cyl 0/ head 1/ sector 1; % end: cyl 130/ head 254/ sector 63 % ... Here "heads=255" and "sectors/track=63" in the "parameters extracted from in-core disklabel" are the firmware number of heads and sectors/track adjusted to match the numbers in the partition table. For current model ATA drives, the firmware numbers are always heads=16 and sectors/track=63 (this is from a standardisation of manufacturers's virtual cylinders). The above is for an old 6.4GB drive. The drive is still new enough to have H=16 and S=63. However, it was partitioned when virtual cylinders with H=255 and S=63 was the most common BIOS configuration and the partitioning uses this. This is reflected in the ending head and sector values for the partition shown (and other partitions, but they all have the same ending head and sector values, as they must to avoid ambiguity). The kernel essentially just converts 'head 254 / sector 63" to H=255 S=63. The "parameters to be used for BIOS calculations" are just copies of the "parameters extracted from in-core disklabel". The parameters actually have nothing to do with the in-core disk label except that they were stored there in FreeBSD[1-4]. Now they aren't even extracted from there, except as a fallback in my version of fdisk(8). They are determined using the DIOCGFWHEADS and DIOCFWSECTORS ioctls. My version falls back to reading the disk label if these ioctls fail, so that it works with old kernels. Broken output with a -current kernel: % ******* Working on device /dev/ad0 ******* % parameters extracted from in-core disklabel are: % cylinders=13328 heads=15 sectors/track=63 (945 blks/cyl) % % Figures below won't work with BIOS for partitions not in cyl 1 % parameters to be used for BIOS calculations are: % cylinders=13328 heads=15 sectors/track=63 (945 blks/cyl) % % Media sector size is 512 % Warning: BIOS sector numbering starts with sector 1 % Information from DOS bootblock is: % The data for partition 1 is: % sysid 11 (0x0b),(DOS or Windows 95 with 32 bit FAT) % start 63, size 2104452 (1027 Meg), flag 0 % beg: cyl 0/ head 1/ sector 1; % end: cyl 130/ head 254/ sector 63 In -current/GEOM the DIOCGFWHEADS and DIOCFWSECTORS ioctls apparently return the actual FW (firmware) values. These are not useful in fdisk, and fdisk doesn't know how to find correct ones, so the geometry is just wrong. If there are no partitions, then fdisk has no way to determine the geometry (you have to type it in or risk using the firmware geometry). If there is a partition that ends on a cylinder boundary according to the BIOS's idea of the geometry, then fdisk could determine the geometry in they same way that the kernel used to, but it shouldn't have to. The code for this was intentionally put in the kernel so that all fdisk-like programs don't need to duplicate it. I don't use sysinstall(8), so I don't know exactly what its internal fdisk does, but it seems to be even more broken in this area. E.g., in disks.c: % static void % print_chunks(Disk *d, int u) % { % int row; % int i; % int sz; % char *szstr; % % szstr = (u == UNIT_GIG ? "GB" : (u == UNIT_MEG ? "MB" : % (u == UNIT_KILO ? "KB" : "ST"))); % % for (i = Total = 0; chunk_info[i]; i++) % Total += chunk_info[i]->size; % #ifdef PC98 % if (d->bios_cyl >= 65536 || d->bios_hd > 16 || d->bios_sect >= 256) { % #else % if (d->bios_cyl > 65536 || d->bios_hd > 256 || d->bios_sect >= 64) { % #endif This sanity check is completely insane. It is guaranteed not to be satisfied by any drive larger than 33 disk-manufacturers-GB in the !PC98 case, and by any drive larger than 137 d-m-GB in the PC98 case. Thus it is guaranteed not to be satisfied by any new drive that you can reasonbly buy in the !PC98 case, and by 160GB+ drives in the PC98 case. In RELENG_4, not accepting d_bios_hd values up to 255 is a bug since the kernel-determined geometry will often have such values. In -current, a "firmware" value of 16 for d_bios_hd would maje the d_bios_hd check pass but ensure that the d_bios_cyl check fails for all current model drives. A limit of 65536 on d_bios_cyl is just wrong for drives larger than 137GB. (137GB was a hardware limit for ATA drives until recently. I don't know how BIOSes support drives larger than this.) % dialog_clear_norefresh(); % msgConfirm("WARNING: A geometry of %lu/%lu/%lu for %s is incorrect. Using\n" % "a more likely geometry. If this geometry is incorrect or you\n" % "are unsure as to whether or not it's correct, please consult\n" % "the Hardware Guide in the Documentation submenu or use the\n" % "(G)eometry command to change it now.\n\n" % "Remember: you need to enter whatever your BIOS thinks the\n" % "geometry is! For IDE, it's what you were told in the BIOS\n" % "setup. For SCSI, it's the translation mode your controller is\n" % "using. Do NOT use a ``physical geometry''.", % d->bios_cyl, d->bios_hd, d->bios_sect, d->name); Since the sanity check is insane, the user is almost always presented with the above alarming message. % Sanitize_Bios_Geom(d); This function is mostly insane, but ends up doing something reasonable for large drives (it almost always considers the geometry to be insane, then adjusts it to a sane geometry (but one that is insane according to the above check): C = (size / H / S) (sure to be > 65536 if the drive is larger than 137GN) (but C is mostly irrelevant for fdisk) H = 255 S = initial value (usually 63) % } I usually have no problems with this stuff, but recently created some bad partition tables by swapping disks into a new system. The disks had been partitioned with H=255/C=63 and the BIOS configuration was "AUTO" for both motherboards. The first motherboard (ASUS A7V266-E) got this right, but the second motherboard (ASUS A7N8X-E) somehow got a geometry of H=240/C=63. Creating partitions using WinXP actually used the BIOS geometry and made a mess. The second motherboard had to be changed to something like "Large" mode to get H=255. The first motherboard has a very nice set of options for configuring geometries: { LBA, Large, Normal, Match Partition Table, Manual }. ("Manual" gives the old configuration method where you can set everything. "Match Partition Table" gives exactly what FreeBSD fdisk used to do. Many disk BIOSes do this, but I haven't seen an option to configure it before.) The second motherboard had a not so nice set of options for configuring geometries IIRC. Bruce From owner-freebsd-current@FreeBSD.ORG Sun Jan 4 05:48: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 2DD3016A4CE; Sun, 4 Jan 2004 05:48:44 -0800 (PST) Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6DF5043D5A; Sun, 4 Jan 2004 05:48:42 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from gamplex.bde.org (katana.zip.com.au [61.8.7.246]) by mailman.zeta.org.au (8.9.3p2/8.8.7) with ESMTP id AAA05480; Mon, 5 Jan 2004 00:48:40 +1100 Date: Mon, 5 Jan 2004 00:48:38 +1100 (EST) From: Bruce Evans X-X-Sender: bde@gamplex.bde.org To: Don Lewis In-Reply-To: <200401030401.i0341O7E003439@gw.catspoiler.org> Message-ID: <20040105003929.Y631@gamplex.bde.org> References: <200401030401.i0341O7E003439@gw.catspoiler.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@FreeBSD.org cc: shoesoft@gmx.net Subject: Re: page fault panic tracked down (selwakeuppri()) 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, 04 Jan 2004 13:48:44 -0000 On Fri, 2 Jan 2004, Don Lewis wrote: > On 2 Jan, Stefan Ehmann wrote: > > dsp as sole cause is also unlikely because I've been listening for > > longer times from cdrom/ufs2 without panics. > > I wouldn't rule out the dsp, since you audio player software may be > calling select() on the fd for the audio device. You might want to back > out Bruce's quick hack and change the second argument to selwakeuppri() > to -1 in chn_wakeup() in dev/sound/pcm/channel.c. > ... My not seeing any problems is consistent with my not using any sound drivers. Did you rule out an invalid file system? I just tested -current and was reminded that it doesn't reboot cleanly if ext2fs is mounted. The unclean reboot doesn't affect r/o mounts of ext2fs. OTOH, r/o mounts of dirty file systems are permitted and there is no easy way to fsck ext2fs file systems under FreeBSD. (I use fsck.ext2fs from the e2fsprogs port, but it still needs a block device or filesystem image to work correctly so it hasn't been easy to use since block devices were axed. I sometimes copy file systems to regular files to use it.) Bruce From owner-freebsd-current@FreeBSD.ORG Sun Jan 4 06:37: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 4FCF316A4CE for ; Sun, 4 Jan 2004 06:37:29 -0800 (PST) Received: from deliver.epitech.net (deliver.epitech.net [163.5.0.25]) by mx1.FreeBSD.org (Postfix) with SMTP id 87E9C43D1F for ; Sun, 4 Jan 2004 06:37:23 -0800 (PST) (envelope-from le-hen_j@epita.fr) Received: from epita.fr ([10.42.1.60]) by deliver.epitech.net (SAVSMTP 3.1.2.35) with SMTP id M2004010415360910443 for ; Sun, 04 Jan 2004 15:36:09 +0100 Received: from carpediem (carpediem.epita.fr [10.42.42.5]) by epita.fr id i04EbJM06116 for current@FreeBSD.org EPITA Paris France Sun, 4 Jan 2004 15:37:19 +0100 (CET) Date: Sun, 4 Jan 2004 15:37:19 +0100 From: Jeremie LE HEN To: current@FreeBSD.org Message-ID: <20040104143719.GB537@carpediem.epita.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4i Subject: Boot error after upgrade from 4.9 to 5.2 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, 04 Jan 2004 14:37:29 -0000 Hi, I have just upgraded my system from a RELENG_4 to a RELENG_5_2. I made everything adviced in src/UPDATING, including buildworld, buildkernel, installkernel, reboot, installworld and when I finally rebooted to get a runnable box, it failed between the second and the third stage of the boot sequence : F1 FreeBSD Default: F1 Disk error 0x4 (lba=0x95b1c1f3) Invalid format >> FreeBSD/i386 BOOT Default: 0:ad(0,a)/kernel boot: Disk error 0x4 (lba=0x1e27f153) Invalid format >> FreeBSD/i386 BOOT Default: 0:ad(0,a)/kernel boot: After reading boot(8) manual page, I saw that error 0x4 means "Sector not found", but I don't understand which sector it could not find, since it has worked very well for a long time with 4-stable. Advices are welcome. Thanks in advance. Regards, -- Jeremie LE HEN aka TtZ/TataZ jeremie.le-hen@epita.fr ttz@epita.fr Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! From owner-freebsd-current@FreeBSD.ORG Sun Jan 4 06:43:58 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 ADAA716A4CE for ; Sun, 4 Jan 2004 06:43:58 -0800 (PST) Received: from tx3.oucs.ox.ac.uk (tx3.oucs.ox.ac.uk [163.1.2.167]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9CC3343D3F for ; Sun, 4 Jan 2004 06:43:56 -0800 (PST) (envelope-from colin.percival@wadham.ox.ac.uk) Received: from scan3.oucs.ox.ac.uk ([163.1.2.166] helo=localhost) by tx3.oucs.ox.ac.uk with esmtp (Exim 4.20) id 1Ad9Tv-00055C-NF for current@freebsd.org; Sun, 04 Jan 2004 14:43:55 +0000 Received: from rx3.oucs.ox.ac.uk ([163.1.2.165]) by localhost (scan3.oucs.ox.ac.uk [163.1.2.166]) (amavisd-new, port 25) with ESMTP id 19092-08 for ; Sun, 4 Jan 2004 14:43:54 +0000 (GMT) Received: from gateway.wadham.ox.ac.uk ([163.1.161.253]) by rx3.oucs.ox.ac.uk with smtp (Exim 4.20) id 1Ad9Tu-00054j-CZ for current@freebsd.org; Sun, 04 Jan 2004 14:43:54 +0000 Received: (qmail 14265 invoked by uid 0); 4 Jan 2004 14:43:54 -0000 Received: from colin.percival@wadham.ox.ac.uk by gateway by uid 71 with qmail-scanner-1.16 (sweep: 2.14/3.71. spamassassin: 2.53. Clear:. Processed in 1.503914 secs); 04 Jan 2004 14:43:54 -0000 X-Qmail-Scanner-Mail-From: colin.percival@wadham.ox.ac.uk via gateway X-Qmail-Scanner: 1.16 (Clear:. Processed in 1.503914 secs) Received: from dhcp1131.wadham.ox.ac.uk (HELO piii600.wadham.ox.ac.uk) (163.1.161.131) by gateway.wadham.ox.ac.uk with SMTP; 4 Jan 2004 14:43:53 -0000 Message-Id: <6.0.1.1.1.20040104144302.02be7478@imap.sfu.ca> X-Sender: cperciva@imap.sfu.ca (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1 Date: Sun, 04 Jan 2004 14:43:49 +0000 To: Jeremie LE HEN From: Colin Percival In-Reply-To: <20040104143719.GB537@carpediem.epita.fr> References: <20040104143719.GB537@carpediem.epita.fr> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed cc: current@freebsd.org Subject: Re: Boot error after upgrade from 4.9 to 5.2 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, 04 Jan 2004 14:43:58 -0000 At 14:37 04/01/2004, Jeremie LE HEN wrote: >I have just upgraded my system from a RELENG_4 to a RELENG_5_2. I made >everything adviced in src/UPDATING, including buildworld, buildkernel, >installkernel, reboot, installworld and when I finally rebooted to get >a runnable box, it failed between the second and the third stage of the >boot sequence I'm not sure about this, but I think you need to install the new boot blocks as well. Colin Percival From owner-freebsd-current@FreeBSD.ORG Sun Jan 4 06:50:21 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 3A58016A4CE for ; Sun, 4 Jan 2004 06:50:21 -0800 (PST) Received: from email02.aon.at (WARSL402PIP7.highway.telekom.at [195.3.96.94]) by mx1.FreeBSD.org (Postfix) with SMTP id C1EDC43D1F for ; Sun, 4 Jan 2004 06:50:18 -0800 (PST) (envelope-from shoesoft@gmx.net) Received: (qmail 29336 invoked from network); 4 Jan 2004 14:50:17 -0000 Received: from n755p030.dipool.highway.telekom.at (HELO ?212.183.104.94?) ([212.183.104.94]) (envelope-sender ) by qmail2rs.highway.telekom.at (qmail-ldap-1.03) with SMTP for ; 4 Jan 2004 14:50:17 -0000 From: Stefan Ehmann To: Don Lewis In-Reply-To: <200401030401.i0341O7E003439@gw.catspoiler.org> References: <200401030401.i0341O7E003439@gw.catspoiler.org> Content-Type: text/plain Message-Id: <1073227819.1764.13.camel@shoeserv.freebsd> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 Date: Sun, 04 Jan 2004 15:50:20 +0100 Content-Transfer-Encoding: 7bit cc: current@FreeBSD.org Subject: Re: page fault panic tracked down (selwakeuppri()) 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, 04 Jan 2004 14:50:21 -0000 On Sat, 2004-01-03 at 05:01, Don Lewis wrote: > I wouldn't rule out the dsp, since you audio player software may be > calling select() on the fd for the audio device. You might want to back > out Bruce's quick hack and change the second argument to selwakeuppri() > to -1 in chn_wakeup() in dev/sound/pcm/channel.c. > > Is your kernel compiled with the INVARIANTS and INVARIANTS_SUPPORT > options? > > Something else that I noticed is that the CHN_LOCKASSERT macro has an > empty definition in dev/sound/pcm/channel.h. You might want to try > defining it as > mtx_assert((struct mtx *)((c)->lock), MA_OWNED) > > I still don't see any obvious cause for this problem. I took out the debug options because it was just too slow. Put back INVARIANTS (but no WITNESS) now and speed is nice again. Applied your suggested changes which resulted in a panic. No assertations were triggered though. From owner-freebsd-current@FreeBSD.ORG Sun Jan 4 07:04:34 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 880D016A4CE for ; Sun, 4 Jan 2004 07:04:34 -0800 (PST) Received: from email03.aon.at (WARSL402PIP6.highway.telekom.at [195.3.96.93]) by mx1.FreeBSD.org (Postfix) with SMTP id CB43A43D45 for ; Sun, 4 Jan 2004 07:04:32 -0800 (PST) (envelope-from shoesoft@gmx.net) Received: (qmail 171888 invoked from network); 4 Jan 2004 15:04:31 -0000 Received: from n755p030.dipool.highway.telekom.at (HELO ?212.183.104.94?) ([212.183.104.94]) (envelope-sender ) by qmail3rs.highway.telekom.at (qmail-ldap-1.03) with SMTP for ; 4 Jan 2004 15:04:31 -0000 From: Stefan Ehmann To: Bruce Evans In-Reply-To: <20040105003929.Y631@gamplex.bde.org> References: <200401030401.i0341O7E003439@gw.catspoiler.org> <20040105003929.Y631@gamplex.bde.org> Content-Type: text/plain Message-Id: <1073228674.1764.28.camel@shoeserv.freebsd> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 Date: Sun, 04 Jan 2004 16:04:34 +0100 Content-Transfer-Encoding: 7bit cc: current@FreeBSD.org Subject: Re: page fault panic tracked down (selwakeuppri()) 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, 04 Jan 2004 15:04:34 -0000 On Sun, 2004-01-04 at 14:48, Bruce Evans wrote: > On Fri, 2 Jan 2004, Don Lewis wrote: > My not seeing any problems is consistent with my not using any sound > drivers. > > Did you rule out an invalid file system? I just tested -current and > was reminded that it doesn't reboot cleanly if ext2fs is mounted. > The unclean reboot doesn't affect r/o mounts of ext2fs. OTOH, r/o > mounts of dirty file systems are permitted and there is no easy way > to fsck ext2fs file systems under FreeBSD. (I use fsck.ext2fs from > the e2fsprogs port, but it still needs a block device or filesystem > image to work correctly so it hasn't been easy to use since block > devices were axed. I sometimes copy file systems to regular files > to use it.) I already thought of an invalid file system. But I think it would be very unlikely that it only causes panics with the selwakeuppri() changes. I normally mount it read only and unmount it manually before shutdown to avoid these problems. Last time when I mounted it rw and the system crashed I had big troubles repairing it again. In fact I gave up repairing it under FreeBSD (always complained about wrong superblock - ro mounting was working fine though). Finally repaired it using Knoppix which also had troubles. I only found 1 of about 10 superblock backups working. From owner-freebsd-current@FreeBSD.ORG Sun Jan 4 08:19: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 CA3FC16A4CE for ; Sun, 4 Jan 2004 08:19:47 -0800 (PST) Received: from astra.telenet-ops.be (astra.telenet-ops.be [195.130.132.58]) by mx1.FreeBSD.org (Postfix) with ESMTP id 83D1243D3F for ; Sun, 4 Jan 2004 08:19:45 -0800 (PST) (envelope-from philip@paeps.cx) Received: from localhost (localhost.localdomain [127.0.0.1]) by astra.telenet-ops.be (Postfix) with SMTP id 6F72537F84 for ; Sun, 4 Jan 2004 17:19:44 +0100 (MET) Received: from erda.home.paeps.cx (D576865A.kabel.telenet.be [213.118.134.90]) by astra.telenet-ops.be (Postfix) with ESMTP id E60BB37F7D for ; Sun, 4 Jan 2004 17:19:43 +0100 (MET) Received: from loge.home.paeps.cx (loge.home.paeps.cx [10.0.0.4]) by erda.home.paeps.cx (Postfix) with ESMTP id AF14920A7 for ; Sun, 4 Jan 2004 17:19:43 +0100 (CET) Received: by loge.home.paeps.cx (Postfix, from userid 1001) id EC11D15; Sun, 4 Jan 2004 17:19:42 +0100 (CET) Date: Sun, 4 Jan 2004 17:19:42 +0100 From: Philip Paeps To: David Gilbert Message-ID: <20040104161942.GE3628@loge.home.paeps.cx> References: <16373.49080.401073.12711@canoe.dclg.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <16373.49080.401073.12711@canoe.dclg.ca> X-Date-in-Rome: pridie Nonas Ianuarias MMDCCLVII ab Urbe Condida X-PGP-Fingerprint: FA74 3C27 91A6 79D5 F6D3 FC53 BF4B D0E6 049D B879 X-Message-Flag: Get a proper mailclient! Mutt: User-Agent: Mutt/1.5.5.1i cc: freebsd-current@freebsd.org Subject: Re: new psm patch. 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, 04 Jan 2004 16:19:47 -0000 On 2004-01-02 14:00:08 (-0500), David Gilbert wrote: > I was applying the psm patch posted here recently. Not the one that was for > the Xserver, but the one that was for the moused operation. It didn't apply > cleanly. Included is a patch that applies to current with the same effect. > I would like to see discussion towards including this in -CURRENT as > touchpad support is a hot laptop topic. Very nice :-) > As a note to the origional author, it seems that 'ipacket' is now referenced > by 'pb' rather than 'sc' in the driver. It looks like ipacket was a member > of the sc structure but now is a sub-member. Someone recently added some buffering code to psm, I updated my local patch, but hadn't had time to furture develop it. > + { MOUSE_MODEL_SYNAPTICS, /* Synaptics TouchPad */ > + 0xc0, MOUSE_PS2SYNAP_PACKETSIZE, enable_synaptics, }, This will catch every Synaptics pad on the market, not only the ones with the 'new' absolute packet format, and not all of them support all features :-/ In fact 'older' (not that old) pads will fail spectacularly on some features. > + /* Sanity check for out of sync packets. */ > + if ((pb->ipacket[0] & 0xc8) != 0x80 || (pb->ipacket[3] & 0xc8) != 0xc0) > + continue; There are some other formats of packets that need to be taken into account. I did a check for the different bits in my enable_synaptics function, and then did different sanity checks if different bits were available (following the 'interfacing guide' from Synaptics): /* New packet format with 'W'-bit */ if (sc->flags & PSM_SYN_HAVE_CAPEXT) { if ((pb->ipacket[0] & 0xc8) != 0x80) { printf("psmintr: wanted 0x80 got 0x%02x\n", (pb->ipacket[0] & 0xc8)); continue; } if ((pb->ipacket[3] & 0xc8) != 0xc0) { printf("psmintr: wanted 0xc0 got 0x%02x\n", (pb->ipacket[3] & 0xc8)); continue; } } /* New packet format without 'W'-bit */ else if (sc->flags & PSM_SYN_HAVE_NEWABS) { if ((pb->ipacket[0] & 0xc8) != 0x80) { printf("psmintr: wanted 0x80 got 0x%02x\n", (pb->ipacket[0] & 0xc8)); continue; } if ((pb->ipacket[3] & 0xc8) != 0xc0) { printf("psmintr: wanted 0xc0 got 0x%02x\n", (pb->ipacket[3] & 0xc8)); continue; } if ((pb->ipacket[0] & 0x0f) != (pb->ipacket[3] & 0x0f)) { printf("psmintr: wanted 0x%02x got 0x%02x\n", (pb->ipacket[0] & 0x0f), (pb->ipacket[3] & 0x0f)); continue; } } /* Old (<3.2) packet format */ else { if ((pb->ipacket[0] & 0xc0) != 0xc0) { printf("psmintr: wanted 0xc0 got 0x%02x\n", (pb->ipacket[0] & 0xc0)); continue; } if ((pb->ipacket[1] & 0x60) != 0x00) { printf("psmintr: wanted 0x00 got 0x%02x\n", (pb->ipacket[1] & 0x60)); continue; } if ((pb->ipacket[3] & 0xc0) != 0x80) { printf("psmintr: wanted 0x80 got 0x%02x\n", (pb->ipacket[3] & 0xc0)); continue; } if ((pb->ipacket[4] & 0x60) != 0x00) { printf("psmintr: wanted 0x00 got 0x%02x\n", (pb->ipacket[4] & 0x60)); continue; } } Or something along those lines. > +#define SYN_BIT_ABSOLUTE_MODE 0x80 > +#define SYN_BIT_HIGH_RATE 0x40 > +#define SYN_BIT_SLEEP_MODE 0x08 > +#define SYN_BIT_DISABLE_GESTURE 0x04 > +#define SYN_BIT_W_MODE 0x01 You could use those bits for the check. I'll go test your patch now, and fiddle with it a bit :-) Thanks :-) - Philip -- Philip Paeps Please don't CC me, I am subscribed to the list. BOFH Excuse #283: Lawn mower blade in your fan need sharpening From owner-freebsd-current@FreeBSD.ORG Sun Jan 4 08:41:12 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 74C9316A4CE; Sun, 4 Jan 2004 08:41:12 -0800 (PST) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id BE69C43D62; Sun, 4 Jan 2004 08:41:07 -0800 (PST) (envelope-from phk@phk.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.10/8.12.10) with ESMTP id i04Gf5jl029717; Sun, 4 Jan 2004 17:41:05 +0100 (CET) (envelope-from phk@phk.freebsd.dk) To: current@freebsd.org, net@freebsd.org From: Poul-Henning Kamp Date: Sun, 04 Jan 2004 17:41:05 +0100 Message-ID: <29716.1073234465@critter.freebsd.dk> Subject: REVIEW & TEST: libalias megapatch 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, 04 Jan 2004 16:41:12 -0000 http://phk.freebsd.dk/patch/libalias.patch This patch makes it possible to have multiple packet aliasing instances in a single process. Redefine a new API based on s/PacketAlias/LibAlias/g Add new "instance" argument to all functions in the new API. Put all global variables in the instance structure. Implement old API in terms of the new API. No functional change. No functions removed so there is no need for shlib version bump, only an updating entry and a __FreeBSD_version bump. The intent is to subsequently add a "multilink" facility to natd(8) for people with two xDSL lines to different providers etc. For this we need to run one packet-aliasing engine per line, and in order to not totally toast throughput, this should not result in more context switches then we are used to. (ie: not kern/usr/kern/usr/kern for the second line, but just kern/usr/kern as always). This patch makes it possible for programs like natd to run multiple packet-aliasing engines, this was not previously possible because of the widespread use of global variables in libalias. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-current@FreeBSD.ORG Sun Jan 4 09:43: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 01C0C16A4CE for ; Sun, 4 Jan 2004 09:43:07 -0800 (PST) Received: from 21322530218.direct.eti.at (21322530218.direct.eti.at [213.225.30.218]) by mx1.FreeBSD.org (Postfix) with ESMTP id 39E0443D48 for ; Sun, 4 Jan 2004 09:43:04 -0800 (PST) (envelope-from tilman@arved.de) Received: from huckfinn-xl1.arved.de (localhost [127.0.0.1]) i04Hgwf3086499 for ; Sun, 4 Jan 2004 18:43:00 +0100 (CET) (envelope-from tilman@arved.de) Received: (from tilman@localhost) by huckfinn-xl1.arved.de (8.12.10/8.12.6/Submit) id i04HgvYJ086498 for current@FreeBSD.org; Sun, 4 Jan 2004 18:42:57 +0100 (CET) X-Authentication-Warning: huckfinn-xl1.arved.de: tilman set sender to tilman@arved.de using -f Date: Sun, 4 Jan 2004 18:42:57 +0100 From: Tilman Linneweh To: current@FreeBSD.org Message-ID: <20040104174257.GA13924@huckfinn.arved.de> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ibTvN161/egqYuK8" Content-Disposition: inline User-Agent: Mutt/1.4.1i Subject: X freezes machine 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, 04 Jan 2004 17:43:07 -0000 --ibTvN161/egqYuK8 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi, Anyone seen this? CURRENT from today (Jan 4) on amd64 freezes the machine after 'startx'=20 (beforeswitching to graphical modus). A Kernel from December 15 works fine. regards tilman --ibTvN161/egqYuK8 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQE/+FCffCLDn4B6xToRAh7OAKCJ2HAjvtd0HbLN3LehRc+Jkv9VIwCfRfZV 752tdOo2x7q3dkPLmMshmeE= =Bwcl -----END PGP SIGNATURE----- --ibTvN161/egqYuK8-- From owner-freebsd-current@FreeBSD.ORG Sun Jan 4 09:50: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 7B8AE16A4CE for ; Sun, 4 Jan 2004 09:50:36 -0800 (PST) Received: from sizone.org (mortar.sizone.org [65.126.154.242]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7FFCC43D49 for ; Sun, 4 Jan 2004 09:50:34 -0800 (PST) (envelope-from dgilbert@daveg.ca) Received: by sizone.org (Postfix, from userid 66) id BD59A307D0; Sun, 4 Jan 2004 12:50:33 -0500 (EST) Received: by canoe.dclg.ca (Postfix, from userid 101) id E48C11D1E37; Sun, 4 Jan 2004 12:50:29 -0500 (EST) From: David Gilbert MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16376.21093.774985.305807@canoe.dclg.ca> Date: Sun, 4 Jan 2004 12:50:29 -0500 To: Philip Paeps In-Reply-To: <20040104161942.GE3628@loge.home.paeps.cx> References: <16373.49080.401073.12711@canoe.dclg.ca> <20040104161942.GE3628@loge.home.paeps.cx> X-Mailer: VM 7.17 under 21.4 (patch 14) "Reasonable Discussion" XEmacs Lucid cc: freebsd-current@freebsd.org cc: David Gilbert Subject: Re: new psm patch. 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, 04 Jan 2004 17:50:36 -0000 >>>>> "Philip" == Philip Paeps writes: Philip> On 2004-01-02 14:00:08 (-0500), David Gilbert Philip> wrote: >> I was applying the psm patch posted here recently. Not the one [...] >> As a note to the origional author, it seems that 'ipacket' is now >> referenced by 'pb' rather than 'sc' in the driver. It looks like >> ipacket was a member of the sc structure but now is a sub-member. Philip> Someone recently added some buffering code to psm, I updated Philip> my local patch, but hadn't had time to furture develop it. To some embarrasment, it would seem that I have the 'Glidepoint' pad ... or at least that's what the probe is finding. Sigh. Looking at psm.c, only the 'tapping action' is supported ... and that not very well. I have a touchpad and a small joy stick that appear as one device. I gather that this is made by Glidepoint. Is there any documentation on this? Now that I know I have a different touchpad, I'd like to hack around on it. Dave. -- ============================================================================ |David Gilbert, Independent Contractor. | Two things can only be | |Mail: dave@daveg.ca | equal if and only if they | |http://daveg.ca | are precisely opposite. | =========================================================GLO================ From owner-freebsd-current@FreeBSD.ORG Sun Jan 4 08:05: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 266F716A4CE; Sun, 4 Jan 2004 08:05:24 -0800 (PST) Received: from sally.dts-online.net (sally.dts-online.net [212.62.68.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9541043D45; Sun, 4 Jan 2004 08:05:22 -0800 (PST) (envelope-from lkoeller@koellers.net) Received: from door.koellers.net (212-62-83-185.teleos-web.de [212.62.83.185]) by sally.dts-online.net (Postfix) with ESMTP id E86784DEAB9; Sun, 4 Jan 2004 17:05:20 +0100 (CET) Received: from odie.koellers.net (root@odie.koellers.net [192.168.4.2]) by door.koellers.net (8.12.9p2/8.12.8) with ESMTP id i04DU9YR099328; Sun, 4 Jan 2004 14:30:09 +0100 (CET) (envelope-from lkoeller@koellers.net) Received: from odie.koellers.net (lkoeller@localhost [127.0.0.1]) by odie.koellers.net (8.12.9p2/8.12.9) with ESMTP id i04DU9Jx032255; Sun, 4 Jan 2004 14:30:09 +0100 (CET) (envelope-from lkoeller@odie.koellers.net) Message-Id: <200401041330.i04DU9Jx032255@odie.koellers.net> X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4 From: Lars =?iso-8859-1?Q?K=F6ller?= To: dwhite@FreeBSD.org X-Face: eCcoCV}FjV*O{6>[1$XP/e%]TJhEw2MF33dFh)^HM7Gfd=[/(4+0a$~ List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Jan 2004 16:05:24 -0000 -------- Dear Doug, I wish you a happy new year. I'm an old FreeBSD user and we have = several rack mounted servers (Fujitsu Siemens) in our university = computing center for mail virus scanning, www caching, etc. All these boards support IPMI, and it would be nice to have an FreeBSD = interface/user tools for it. I notice that you have started to work on it, but it stopped since Aug. = 2002. Are there any plans to integrate this in 5.X releases? For enterprise usage of FreeBSD I think it is really important to have = such an interface working for better management. Best regards Lars -- = Lars K=F6ller E-Mail: lars@koellers.net (LKoeller@FreeBSD.ORG) -------- FreeBSD, was sonst? ---- http://www.de.freebsd.org -------- From owner-freebsd-current@FreeBSD.ORG Sun Jan 4 10:31:27 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 7E34116A4CE for ; Sun, 4 Jan 2004 10:31:27 -0800 (PST) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id D427943D1F for ; Sun, 4 Jan 2004 10:31:24 -0800 (PST) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (localhost [127.0.0.1]) by transport.cksoft.de (Postfix) with ESMTP id DB62A1FF91D for ; Sun, 4 Jan 2004 19:31:22 +0100 (CET) Received: by transport.cksoft.de (Postfix, from userid 66) id 3DB1F1FF90C; Sun, 4 Jan 2004 19:31:21 +0100 (CET) Received: by mail.int.zabbadoz.net (Postfix, from userid 1060) id 652AB1539D; Sun, 4 Jan 2004 18:30:35 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mail.int.zabbadoz.net (Postfix) with ESMTP id 62A6315384 for ; Sun, 4 Jan 2004 18:30:35 +0000 (UTC) Date: Sun, 4 Jan 2004 18:30:35 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@e0-0.zab2.int.zabbadoz.net To: current@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS cksoft-s20020300-20031204bz on transport.cksoft.de Subject: Expensive timeout(9) function ? 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, 04 Jan 2004 18:31:27 -0000 Hi, what reports do you expect with the "Expensive timeout(9) function" message ? Why do we see it ? I have seen multiple of those but I am unsure if and what to report ? the last I found grepping my log have been: Expensive timeout(9) function: 0xc04885a0(0) 1.024846430 s [1] Expensive timeout(9) function: 0xc04885a0(0) 1.024846430 s [1] Expensive timeout(9) function: 0xc04b3940(0) 0.008629758 s [2] Expensive timeout(9) function: 0xc04b39a0(0) 0.004333781 s [2] Expensive timeout(9) function: 0xc04f71f0(0) 0.027004551 s [3] Expensive timeout(9) function: 0xc04f71f0(0) 0.027004551 s [3] Expensive timeout(9) function: 0xc04f71f0(0) 0.027004551 s [3] [1] sys/kern/kern_synch.c:loadav() [2] sys/kern/uipc_domain.c:pfslowtimo() [3] sys/netinet/ip_fw2.c:ipfw_tick() -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT 56 69 73 69 74 http://www.zabbadoz.net/ From owner-freebsd-current@FreeBSD.ORG Sun Jan 4 10:40:41 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 6D4A716A4CE for ; Sun, 4 Jan 2004 10:40:41 -0800 (PST) Received: from elpis.telenet-ops.be (elpis.telenet-ops.be [195.130.132.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id 73C0343D54 for ; Sun, 4 Jan 2004 10:40:38 -0800 (PST) (envelope-from philip@paeps.cx) Received: from localhost (adicia.telenet-ops.be [195.130.132.56]) by elpis.telenet-ops.be (Postfix) with SMTP id B22C237EFC for ; Sun, 4 Jan 2004 19:40:37 +0100 (MET) Received: from erda.home.paeps.cx (D576865A.kabel.telenet.be [213.118.134.90]) by adicia.telenet-ops.be (Postfix) with ESMTP id 6445E37EC8 for ; Sun, 4 Jan 2004 19:40:37 +0100 (MET) Received: from loge.home.paeps.cx (loge.home.paeps.cx [10.0.0.4]) by erda.home.paeps.cx (Postfix) with ESMTP id 104D920EB for ; Sun, 4 Jan 2004 19:40:37 +0100 (CET) Received: by loge.home.paeps.cx (Postfix, from userid 1001) id 717C23C; Sun, 4 Jan 2004 19:40:36 +0100 (CET) Date: Sun, 4 Jan 2004 19:40:36 +0100 From: Philip Paeps To: David Gilbert Message-ID: <20040104184036.GD646@loge.home.paeps.cx> References: <16373.49080.401073.12711@canoe.dclg.ca> <20040104161942.GE3628@loge.home.paeps.cx> <16376.21093.774985.305807@canoe.dclg.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <16376.21093.774985.305807@canoe.dclg.ca> X-Date-in-Rome: pridie Nonas Ianuarias MMDCCLVII ab Urbe Condida X-PGP-Fingerprint: FA74 3C27 91A6 79D5 F6D3 FC53 BF4B D0E6 049D B879 X-Message-Flag: Get a proper mailclient! Mutt: User-Agent: Mutt/1.5.5.1i cc: freebsd-current@freebsd.org Subject: Re: new psm patch. 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, 04 Jan 2004 18:40:41 -0000 On 2004-01-04 12:50:29 (-0500), David Gilbert wrote: > >>>>> "Philip" == Philip Paeps writes: > > Philip> On 2004-01-02 14:00:08 (-0500), David Gilbert > Philip> wrote: > > >> I was applying the psm patch posted here recently. Not the one > > [...] > > >> As a note to the origional author, it seems that 'ipacket' is now > >> referenced by 'pb' rather than 'sc' in the driver. It looks like > >> ipacket was a member of the sc structure but now is a sub-member. > > Philip> Someone recently added some buffering code to psm, I updated > Philip> my local patch, but hadn't had time to furture develop it. > > To some embarrasment, it would seem that I have the 'Glidepoint' pad > ... or at least that's what the probe is finding. Whoops :-) Well, nice of you to work on the Synaptics *grin*, it's a reminder to me to get a move on an finish that code. It's been on my todo-list since early last year. I've been working on getting 'gesture' code like on Linux (taps, corner taps, multi-finger taps and all that in there). > Sigh. Looking at psm.c, only the 'tapping action' is supported ... and that > not very well. I have a touchpad and a small joy stick that appear as one > device. I gather that this is made by Glidepoint. Is there any > documentation on this? Now that I know I have a different touchpad, I'd > like to hack around on it. Maybe the Synaptics guide is a reference? I've been using the algorithms used by GPM in Linux as an inspiration for my Synaptics code but it's a lot of work translating them to work in the kernel as opposed to userspace as in Linux (floats all over the shop and not particularly efficient here and there). - Philip -- Philip Paeps Please don't CC me, I am subscribed to the list. BOFH Excuse #300: Digital Manipulator exceeding velocity parameters From owner-freebsd-current@FreeBSD.ORG Sun Jan 4 11:55:28 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 46A7516A4CE for ; Sun, 4 Jan 2004 11:55:28 -0800 (PST) Received: from ion.gank.org (ion.gank.org [69.55.238.164]) by mx1.FreeBSD.org (Postfix) with ESMTP id C281443D48 for ; Sun, 4 Jan 2004 11:55:25 -0800 (PST) (envelope-from craig@xfoil.gank.org) Received: from localhost (ion.gank.org [69.55.238.164]) by ion.gank.org (mail) with ESMTP id 787882B54F; Sun, 4 Jan 2004 13:55:25 -0600 (CST) Received: from ion.gank.org ([69.55.238.164]) by localhost (ion.gank.org [69.55.238.164]) (amavisd-new, port 10024) with LMTP id 99205-07; Sun, 4 Jan 2004 13:55:24 -0600 (CST) Received: from aldaris.auir.gank.org (arbiter.gank.org [64.81.113.221]) by ion.gank.org (mail) with ESMTP id D914F2B3C6; Sun, 4 Jan 2004 13:55:23 -0600 (CST) From: Craig Boston To: David Gilbert Date: Sun, 4 Jan 2004 13:55:18 -0600 User-Agent: KMail/1.5.4 References: <20031229164130.GA797@pp.htv.fi> <20031231152453.G1441@bo.vpnaa.bet> <16371.23746.824760.637381@canoe.dclg.ca> In-Reply-To: <16371.23746.824760.637381@canoe.dclg.ca> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200401041355.18610.craig@xfoil.gank.org> X-Virus-Scanned: by amavisd-new at gank.org cc: current@freebsd.org Subject: Re: 5.1-R-p11 unable to "sync disks" when shutting down 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, 04 Jan 2004 19:55:28 -0000 On Wednesday 31 December 2003 05:33 pm, David Gilbert wrote: > True, but faced with a machine that can't be upgraded (swap to vinum > not supported in 5.2) What I ended up doing so that I could run 5.2 on a couple of my "all RAID5 all the time" servers was this: 1. Create a UFS filesystem on the "swap" partition and mount it noatime,sync 2. Use dd to create the biggest file possible on the new filesystem 3. Use swapfile="/swap/bigfile" in rc.conf, which uses an md device with vnode backing and enables swapping on it. It's a massive hack and there is probably a performance hit, but it seems to work... Craig From owner-freebsd-current@FreeBSD.ORG Sun Jan 4 12:02: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 9AE2716A4CE for ; Sun, 4 Jan 2004 12:02:26 -0800 (PST) Received: from out002.verizon.net (out002pub.verizon.net [206.46.170.141]) by mx1.FreeBSD.org (Postfix) with ESMTP id 971E243D53 for ; Sun, 4 Jan 2004 12:01:43 -0800 (PST) (envelope-from Alex.Kovalenko@verizon.net) Received: from RabbitsDen.RabbitsLawn.verizon.net ([138.89.12.104]) by out002.verizon.netESMTP <20040104200142.YTFU24265.out002.verizon.net@RabbitsDen.RabbitsLawn.verizon.net> for ; Sun, 4 Jan 2004 14:01:42 -0600 Date: Sun, 4 Jan 2004 15:01:40 -0500 From: Alexandre "Sunny" Kovalenko To: freebsd-current@freebsd.org Message-Id: <20040104150140.7d378124.Alex.Kovalenko@verizon.net> In-Reply-To: <001b01c3d2a8$0e952560$6401a8c0@seano> References: <001b01c3d2a8$0e952560$6401a8c0@seano> Organization: Home X-Mailer: Sylpheed version 0.9.7 (GTK+ 1.2.10; i386-portbld-freebsd5.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Authentication-Info: Submitted using SMTP AUTH at out002.verizon.net from [138.89.12.104] at Sun, 4 Jan 2004 14:01:42 -0600 Subject: Re: ACPI and Gateway 400sd4 laptop 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, 04 Jan 2004 20:02:26 -0000 I had similar problem with my machine recently (it is Averatec 4150H) and after walking through the ASL, discovered that _TMP method in thermal zone object always returns same value which was stored away during ACPI initialization. I would suggest you check if 'sysctl hw.acpi.thermal.tzX.temperature' returns something reasonable (or at least changes with machine warming up perceptibly) and if it does not investigate conditional statement you have in _TMP method of the thermal zone object -- at first look it seams to return stored value at least along one of the branches. Please, keep in mind that I by no means claim good knowledge of ACPI and/or ASL and just share suggestion that worked for me. On Sun, 4 Jan 2004 01:49:28 -0800 "Sean Lazar" wrote: > I have a Gateway 400SD4 laptop that I am having thermal issues with in > FreeBSD-CURRENT. The two-speed fan dosen't seem to come on. With ACPI on, > after the system has been running a little while and has warmed up, if I > turn off acpi with "acpiconf -d" the fan will kick on immediately. After > that the fan appears to behave normally, turning on and off when necessary. > If the laptop boots warm with the fan on, it will shut off when it gets cool > but it won't come back on again. > > There is a second fan on this model that seems to work fine, but it dosen't > do enough to cool down the system. My original asl file can be found here: > http://members.cruzio.com/~slazar/gw400sd4/gw400sd4.asl. I tried editing it > and removing the OS-dependent areas and if statements in the TZ section and > using a custom dsdt file with acpi_dsdt_load="YES" and > acpi_dsdt_name="/boot/DSDT.asl" in my /boot/loader.conf. I also tried > hw.acpi.os_name="Microsoft Windows NT" in /boot/loader.conf and other OS > names as well. I also tried debug.acpi.disable="thermal". > > What else can I try? Any ACPI patches out there? Or perhaps I can > sucessfully edit this file with some hints :) I've read the Intel ACPI spec > and I am starting to understand the format... > > My boot messages can be found here: > http://members.cruzio.com/~slazar/gw400sd4/messages Yes it is from 5.2-RC2 > but I get the same messages in -CURRENT > > Cheers, > Sean > > _______________________________________________ > 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" -- Alexandre "Sunny" Kovalenko. From owner-freebsd-current@FreeBSD.ORG Sun Jan 4 12:41:25 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 BF22D16A4CE for ; Sun, 4 Jan 2004 12:41:25 -0800 (PST) Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id C394F43D1D for ; Sun, 4 Jan 2004 12:41:24 -0800 (PST) (envelope-from truckman@FreeBSD.org) Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.12.9p2/8.12.9) with ESMTP id i04KfE7E009622; Sun, 4 Jan 2004 12:41:19 -0800 (PST) (envelope-from truckman@FreeBSD.org) Message-Id: <200401042041.i04KfE7E009622@gw.catspoiler.org> Date: Sun, 4 Jan 2004 12:41:14 -0800 (PST) From: Don Lewis To: dejan.lesjak@ijs.si In-Reply-To: <200401041115.29188.dejan.lesjak@ijs.si> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii cc: ryans@gamersimpact.com cc: silby@silby.com cc: freebsd-current@FreeBSD.org Subject: Re: 5.2-RC oerrs and collisions on dc0 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, 04 Jan 2004 20:41:25 -0000 On 4 Jan, Dejan Lesjak wrote: > On Sunday 04 of January 2004 09:59, Don Lewis wrote: >> When errors occur in full duplex mode, you might want to print the value >> of >> CSR_READ_4(sc, DC_NETCFG) >> to verify that the full duplex bit is actually set. > > I put this right after > if (txstat & DC_TXSTAT_ERRSUM) { > ifp->if_oerrors++; > > it gives me 0x338c2203 and DC_NETCFG_FULLDUPLEX is 0x00000200, so as I > understand full-duplex is set. Also none of previous two suggestions made > difference. I also found this documentation: > ftp://download.intel.com/design/network/manuals/27807401.pdf > if it helps. Interesting, this card appears to use the PCS interface instead of MII (bit 23 is set). Also bit 28 is set. The 21143 documentation says this is unused, but my copy of the 21140A documentation says this bit must be zero. From owner-freebsd-current@FreeBSD.ORG Sun Jan 4 13:08: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 7517C16A4CE for ; Sun, 4 Jan 2004 13:08:47 -0800 (PST) Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5A3F543D2F for ; Sun, 4 Jan 2004 13:08:46 -0800 (PST) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.10/8.12.9) with ESMTP id i04L8jET025148; Sun, 4 Jan 2004 14:08:45 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Sun, 04 Jan 2004 14:08:24 -0700 (MST) Message-Id: <20040104.140824.121437914.imp@bsdimp.com> To: hopet@ics.muni.cz From: "M. Warner Losh" In-Reply-To: <02f001c3d29e$ad39d4e0$42e86cc2@kloboucek> References: <20040103.122837.65494976.imp@bsdimp.com> <02f001c3d29e$ad39d4e0$42e86cc2@kloboucek> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: current@freebsd.org Subject: Re: wi0 fails to wake up 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, 04 Jan 2004 21:08:47 -0000 In message: <02f001c3d29e$ad39d4e0$42e86cc2@kloboucek> "Petr Holub" writes: : > The cardbus bridge isn't waking up quite right, otherwise you won't : > see one of these messages. It is a 'Can't happen' message. : : OK. Is there anything I can do to help you sort it out? That's a good question. I think that I want to get a few more fixes into the 'power patches' and try again. Warner From owner-freebsd-current@FreeBSD.ORG Sun Jan 4 13:13:55 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 F308616A4CE; Sun, 4 Jan 2004 13:13:54 -0800 (PST) Received: from cueball.rtp.FreeBSD.org (cueball.rtp.FreeBSD.org [192.58.184.37]) by mx1.FreeBSD.org (Postfix) with ESMTP id 594F643D2D; Sun, 4 Jan 2004 13:13:52 -0800 (PST) (envelope-from des+tinderbox@freebsd.org) Received: from cueball.rtp.FreeBSD.org (localhost [127.0.0.1]) i04LDpv9056711; Sun, 4 Jan 2004 16:13:51 -0500 (EST) (envelope-from des+tinderbox@freebsd.org) Received: (from des@localhost) by cueball.rtp.FreeBSD.org (8.12.9/8.12.9/Submit) id i04LDpmh056710; Sun, 4 Jan 2004 16:13:51 -0500 (EST) (envelope-from des+tinderbox@freebsd.org) Date: Sun, 4 Jan 2004 16:13:51 -0500 (EST) Message-Id: <200401042113.i04LDpmh056710@cueball.rtp.FreeBSD.org> X-Authentication-Warning: cueball.rtp.FreeBSD.org: des set sender to Tinderbox using -f Sender: Tinderbox From: Tinderbox To: current@freebsd.org, i386@freebsd.org Precedence: bulk Subject: [current tinderbox] failure on i386/i386 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Jan 2004 21:13:55 -0000 TB --- 2004-01-04 19:45:34 - tinderbox 2.2 running on cueball.rtp.FreeBSD.org TB --- 2004-01-04 19:45:34 - starting CURRENT tinderbox run for i386/i386 TB --- 2004-01-04 19:45:34 - checking out the source tree TB --- cd /home/des/tinderbox/CURRENT/i386/i386 TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2004-01-04 19:47:31 - building world TB --- cd /home/des/tinderbox/CURRENT/i386/i386/src TB --- /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything.. TB --- 2004-01-04 20:46:27 - building generic kernel TB --- cd /home/des/tinderbox/CURRENT/i386/i386/src TB --- /usr/bin/make buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Sun Jan 4 20:46:27 GMT 2004 >>> Kernel build for GENERIC completed on Sun Jan 4 21:01:31 GMT 2004 TB --- 2004-01-04 21:01:31 - generating LINT kernel config TB --- cd /home/des/tinderbox/CURRENT/i386/i386/src/sys/i386/conf TB --- /usr/bin/make -B LINT TB --- 2004-01-04 21:01:31 - building LINT kernel TB --- cd /home/des/tinderbox/CURRENT/i386/i386/src TB --- /usr/bin/make buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Sun Jan 4 21:01:31 GMT 2004 [...] /vol/vol1/users/des/tinderbox/CURRENT/i386/i386/src/sys/i386/svr4/svr4_machdep.c:209: error: structure has no member named `p_sigstk' /vol/vol1/users/des/tinderbox/CURRENT/i386/i386/src/sys/i386/svr4/svr4_machdep.c: In function `svr4_sendsig': /vol/vol1/users/des/tinderbox/CURRENT/i386/i386/src/sys/i386/svr4/svr4_machdep.c:440: error: `P_ALTSTACK' undeclared (first use in this function) /vol/vol1/users/des/tinderbox/CURRENT/i386/i386/src/sys/i386/svr4/svr4_machdep.c:440: error: (Each undeclared identifier is reported only once /vol/vol1/users/des/tinderbox/CURRENT/i386/i386/src/sys/i386/svr4/svr4_machdep.c:440: error: for each function it appears in.) /vol/vol1/users/des/tinderbox/CURRENT/i386/i386/src/sys/i386/svr4/svr4_machdep.c:442: error: structure has no member named `p_sigstk' /vol/vol1/users/des/tinderbox/CURRENT/i386/i386/src/sys/i386/svr4/svr4_machdep.c:443: error: structure has no member named `p_sigstk' /vol/vol1/users/des/tinderbox/CURRENT/i386/i386/src/sys/i386/svr4/svr4_machdep.c:444: error: structure has no member named `p_sigstk' *** Error code 1 Stop in /vol/vol1/users/des/tinderbox/CURRENT/i386/i386/obj/vol/vol1/users/des/tinderbox/CURRENT/i386/i386/src/sys/LINT. *** Error code 1 Stop in /vol/vol1/users/des/tinderbox/CURRENT/i386/i386/src. *** Error code 1 Stop in /vol/vol1/users/des/tinderbox/CURRENT/i386/i386/src. TB --- 2004-01-04 21:13:50 - TB --- /usr/bin/make returned exit code 1 TB --- 2004-01-04 21:13:50 - TB --- ERROR: failed to build lint kernel TB --- 2004-01-04 21:13:50 - tinderbox aborted From owner-freebsd-current@FreeBSD.ORG Sun Jan 4 13:51:16 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 C6EBE16A4CE; Sun, 4 Jan 2004 13:51:16 -0800 (PST) Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5884943D4C; Sun, 4 Jan 2004 13:51:15 -0800 (PST) (envelope-from truckman@FreeBSD.org) Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.12.9p2/8.12.9) with ESMTP id i04Lp27E009737; Sun, 4 Jan 2004 13:51:07 -0800 (PST) (envelope-from truckman@FreeBSD.org) Message-Id: <200401042151.i04Lp27E009737@gw.catspoiler.org> Date: Sun, 4 Jan 2004 13:51:02 -0800 (PST) From: Don Lewis To: dejan.lesjak@ijs.si In-Reply-To: <200401041115.29188.dejan.lesjak@ijs.si> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii cc: ryans@gamersimpact.com cc: silby@silby.com cc: freebsd-current@FreeBSD.org cc: wpaul@FreeBSD.org Subject: Re: 5.2-RC oerrs and collisions on dc0 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, 04 Jan 2004 21:51:16 -0000 I just took a closer look at the busdma diff, and this change to dc_txeof() looks very suspicious: @@ -2663,7 +2809,7 @@ if (txstat & DC_TXSTAT_OWN) break; - if (!(cur_tx->dc_ctl & DC_TXCTL_LASTFRAG) || + if (!(cur_tx->dc_ctl & DC_TXCTL_FIRSTFRAG) || cur_tx->dc_ctl & DC_TXCTL_SETUP) { if (cur_tx->dc_ctl & DC_TXCTL_SETUP) { /* The code in the "if" block ends with a "continue" which will cause the error handling code to be skipped if the "if" condition is true. I'm pretty sure that the error status bits are only set in the last descriptor for the frame, so we want to execute the "continue" unless the DC_TXCTL_LASTFRAG bit is set. Try reverting this part of the busdma change. From owner-freebsd-current@FreeBSD.ORG Sun Jan 4 14:21:42 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 92C7F16A4CE for ; Sun, 4 Jan 2004 14:21:42 -0800 (PST) Received: from leviathan.inethouston.com (leviathan.inethouston.com [209.198.171.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7F27743D49 for ; Sun, 4 Jan 2004 14:21:41 -0800 (PST) (envelope-from dwcjr@inethouston.net) Received: by leviathan.inethouston.com (Postfix, from userid 1001) id B5EEA2C906F; Sun, 4 Jan 2004 16:21:31 -0600 (CST) Date: Sun, 4 Jan 2004 16:21:31 -0600 From: "David W. Chapman Jr." To: current@freebsd.org Message-ID: <20040104222131.GA21549@minubian.inethouston.net> Mail-Followup-To: current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 5.1-RELEASE i386 Subject: 5.2RC2 Lockup on boot X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: "David W. Chapman Jr." List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Jan 2004 22:21:42 -0000 I'm trying to install 5.2RC2 on my new laptop, a Mitac 8080, and it locks up during boot while detecting devices. The last line I see is pci_cfgintr: 0:2 INTA BIOS irq 10 and its a hard lock. I've tried booting it in safe mode from the bootloader. Booting with or without ACPI doesn't seem to make a difference -- David W. Chapman Jr. dwcjr@inethouston.net Raintree Network Services, Inc. From owner-freebsd-current@FreeBSD.ORG Sun Jan 4 14:24:34 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 4951516A4CE for ; Sun, 4 Jan 2004 14:24:34 -0800 (PST) Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4DA2343D48 for ; Sun, 4 Jan 2004 14:24:33 -0800 (PST) (envelope-from truckman@FreeBSD.org) Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.12.9p2/8.12.9) with ESMTP id i04MOP7E009799; Sun, 4 Jan 2004 14:24:29 -0800 (PST) (envelope-from truckman@FreeBSD.org) Message-Id: <200401042224.i04MOP7E009799@gw.catspoiler.org> Date: Sun, 4 Jan 2004 14:24:25 -0800 (PST) From: Don Lewis To: shoesoft@gmx.net In-Reply-To: <1073227819.1764.13.camel@shoeserv.freebsd> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii cc: current@FreeBSD.org Subject: Re: page fault panic tracked down (selwakeuppri()) 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, 04 Jan 2004 22:24:34 -0000 On 4 Jan, Stefan Ehmann wrote: > On Sat, 2004-01-03 at 05:01, Don Lewis wrote: >> I wouldn't rule out the dsp, since you audio player software may be >> calling select() on the fd for the audio device. You might want to back >> out Bruce's quick hack and change the second argument to selwakeuppri() >> to -1 in chn_wakeup() in dev/sound/pcm/channel.c. >> >> Is your kernel compiled with the INVARIANTS and INVARIANTS_SUPPORT >> options? >> >> Something else that I noticed is that the CHN_LOCKASSERT macro has an >> empty definition in dev/sound/pcm/channel.h. You might want to try >> defining it as >> mtx_assert((struct mtx *)((c)->lock), MA_OWNED) >> >> I still don't see any obvious cause for this problem. > > I took out the debug options because it was just too slow. Put back > INVARIANTS (but no WITNESS) now and speed is nice again. This problem is more likely to be caught by INVARIANTS than WITNESS. > Applied your suggested changes which resulted in a panic. No > assertations were triggered though. Bummer! From owner-freebsd-current@FreeBSD.ORG Sun Jan 4 14:31:25 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 3C5F716A4CE for ; Sun, 4 Jan 2004 14:31:25 -0800 (PST) Received: from leviathan.inethouston.com (leviathan.inethouston.com [209.198.171.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3D61443D39 for ; Sun, 4 Jan 2004 14:31:24 -0800 (PST) (envelope-from dwcjr@inethouston.net) Received: by leviathan.inethouston.com (Postfix, from userid 1001) id 989C82C906E; Sun, 4 Jan 2004 16:31:14 -0600 (CST) Date: Sun, 4 Jan 2004 16:31:14 -0600 From: "David W. Chapman Jr." To: current@freebsd.org Message-ID: <20040104223114.GB21549@minubian.inethouston.net> Mail-Followup-To: current@freebsd.org References: <20040104222131.GA21549@minubian.inethouston.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040104222131.GA21549@minubian.inethouston.net> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 5.1-RELEASE i386 Subject: Re: 5.2RC2 Lockup on boot X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: "David W. Chapman Jr." List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Jan 2004 22:31:25 -0000 On Sun, Jan 04, 2004 at 04:21:31PM -0600, David W. Chapman Jr. wrote: > I'm trying to install 5.2RC2 on my new laptop, a Mitac 8080, and it > locks up during boot while detecting devices. The last line I see is > pci_cfgintr: 0:2 INTA BIOS irq 10 and its a hard lock. > > I've tried booting it in safe mode from the bootloader. > Booting with or without ACPI doesn't seem to make a difference > I want to note that I just tried 5.1 and it experiences the same problem at the same place. Booting in verbose shows found-> vendor=0x8086, dev=0x3582, revid=0x02 bus=0, slot=2, func=0 class=03-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0007, statreg=0x0090, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=10 powerspec 1 supports D0 D1 D3 current D0 map[10]: type 3, range 32, base 00000000, size 27, memory disabled found-> vendor=0x8086, dev= -- David W. Chapman Jr. dwcjr@inethouston.net Raintree Network Services, Inc. From owner-freebsd-current@FreeBSD.ORG Sun Jan 4 14:37:57 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 75DCC16A4CE; Sun, 4 Jan 2004 14:37:57 -0800 (PST) Received: from cueball.rtp.FreeBSD.org (cueball.rtp.FreeBSD.org [192.58.184.37]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4E1BC43D48; Sun, 4 Jan 2004 14:37:55 -0800 (PST) (envelope-from des+tinderbox@freebsd.org) Received: from cueball.rtp.FreeBSD.org (localhost [127.0.0.1]) i04Mbsv9013753; Sun, 4 Jan 2004 17:37:54 -0500 (EST) (envelope-from des+tinderbox@freebsd.org) Received: (from des@localhost) by cueball.rtp.FreeBSD.org (8.12.9/8.12.9/Submit) id i04Mbsef013752; Sun, 4 Jan 2004 17:37:54 -0500 (EST) (envelope-from des+tinderbox@freebsd.org) Date: Sun, 4 Jan 2004 17:37:54 -0500 (EST) Message-Id: <200401042237.i04Mbsef013752@cueball.rtp.FreeBSD.org> X-Authentication-Warning: cueball.rtp.FreeBSD.org: des set sender to Tinderbox using -f Sender: Tinderbox From: Tinderbox To: current@freebsd.org, i386@freebsd.org Precedence: bulk Subject: [current tinderbox] failure on i386/pc98 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Jan 2004 22:37:57 -0000 TB --- 2004-01-04 21:13:51 - tinderbox 2.2 running on cueball.rtp.FreeBSD.org TB --- 2004-01-04 21:13:51 - starting CURRENT tinderbox run for i386/pc98 TB --- 2004-01-04 21:13:51 - checking out the source tree TB --- cd /home/des/tinderbox/CURRENT/i386/pc98 TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2004-01-04 21:15:49 - building world TB --- cd /home/des/tinderbox/CURRENT/i386/pc98/src TB --- /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything.. TB --- 2004-01-04 22:14:52 - building generic kernel TB --- cd /home/des/tinderbox/CURRENT/i386/pc98/src TB --- /usr/bin/make buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Sun Jan 4 22:14:53 GMT 2004 >>> Kernel build for GENERIC completed on Sun Jan 4 22:27:28 GMT 2004 TB --- 2004-01-04 22:27:28 - generating LINT kernel config TB --- cd /home/des/tinderbox/CURRENT/i386/pc98/src/sys/pc98/conf TB --- /usr/bin/make -B LINT TB --- 2004-01-04 22:27:28 - building LINT kernel TB --- cd /home/des/tinderbox/CURRENT/i386/pc98/src TB --- /usr/bin/make buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Sun Jan 4 22:27:28 GMT 2004 [...] /vol/vol1/users/des/tinderbox/CURRENT/i386/pc98/src/sys/i386/svr4/svr4_machdep.c:209: error: structure has no member named `p_sigstk' /vol/vol1/users/des/tinderbox/CURRENT/i386/pc98/src/sys/i386/svr4/svr4_machdep.c: In function `svr4_sendsig': /vol/vol1/users/des/tinderbox/CURRENT/i386/pc98/src/sys/i386/svr4/svr4_machdep.c:440: error: `P_ALTSTACK' undeclared (first use in this function) /vol/vol1/users/des/tinderbox/CURRENT/i386/pc98/src/sys/i386/svr4/svr4_machdep.c:440: error: (Each undeclared identifier is reported only once /vol/vol1/users/des/tinderbox/CURRENT/i386/pc98/src/sys/i386/svr4/svr4_machdep.c:440: error: for each function it appears in.) /vol/vol1/users/des/tinderbox/CURRENT/i386/pc98/src/sys/i386/svr4/svr4_machdep.c:442: error: structure has no member named `p_sigstk' /vol/vol1/users/des/tinderbox/CURRENT/i386/pc98/src/sys/i386/svr4/svr4_machdep.c:443: error: structure has no member named `p_sigstk' /vol/vol1/users/des/tinderbox/CURRENT/i386/pc98/src/sys/i386/svr4/svr4_machdep.c:444: error: structure has no member named `p_sigstk' *** Error code 1 Stop in /vol/vol1/users/des/tinderbox/CURRENT/i386/pc98/obj/pc98/vol/vol1/users/des/tinderbox/CURRENT/i386/pc98/src/sys/LINT. *** Error code 1 Stop in /vol/vol1/users/des/tinderbox/CURRENT/i386/pc98/src. *** Error code 1 Stop in /vol/vol1/users/des/tinderbox/CURRENT/i386/pc98/src. TB --- 2004-01-04 22:37:54 - TB --- /usr/bin/make returned exit code 1 TB --- 2004-01-04 22:37:54 - TB --- ERROR: failed to build lint kernel TB --- 2004-01-04 22:37:54 - tinderbox aborted From owner-freebsd-current@FreeBSD.ORG Sun Jan 4 14:46:21 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 59FD616A4CE for ; Sun, 4 Jan 2004 14:46:21 -0800 (PST) Received: from email02.aon.at (WARSL402PIP7.highway.telekom.at [195.3.96.94]) by mx1.FreeBSD.org (Postfix) with SMTP id 7AFCD43D45 for ; Sun, 4 Jan 2004 14:46:18 -0800 (PST) (envelope-from shoesoft@gmx.net) Received: (qmail 395536 invoked from network); 4 Jan 2004 22:46:17 -0000 Received: from m093p028.dipool.highway.telekom.at (HELO ?62.46.1.156?) ([62.46.1.156]) (envelope-sender ) by qmail2rs.highway.telekom.at (qmail-ldap-1.03) with SMTP for ; 4 Jan 2004 22:46:17 -0000 From: Stefan Ehmann To: Don Lewis In-Reply-To: <200401042224.i04MOP7E009799@gw.catspoiler.org> References: <200401042224.i04MOP7E009799@gw.catspoiler.org> Content-Type: text/plain Message-Id: <1073256379.801.24.camel@shoeserv.freebsd> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 Date: Sun, 04 Jan 2004 23:46:20 +0100 Content-Transfer-Encoding: 7bit cc: current@FreeBSD.org Subject: Re: page fault panic tracked down (selwakeuppri()) 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, 04 Jan 2004 22:46:21 -0000 On Sun, 2004-01-04 at 23:24, Don Lewis wrote: > On 4 Jan, Stefan Ehmann wrote: > > I took out the debug options because it was just too slow. Put back > > INVARIANTS (but no WITNESS) now and speed is nice again. > > This problem is more likely to be caught by INVARIANTS than WITNESS. > > > Applied your suggested changes which resulted in a panic. No > > assertations were triggered though. > > Bummer! Updated to plain (= no patches/hacks) again, also put in the DEBUG_VFS_LOCKS. For the first time I got a backtrace that ended in the soundcard module - So maybe this is the right direction (on the other hand this might be some newly introduced error) panic: bad bufsize #0 doadump () at /usr/src/sys/kern/kern_shutdown.c:240 #1 0xc04e5198 in boot (howto=256) at /usr/src/sys/kern/kern_shutdown.c:372 #2 0xc04e5527 in panic () at /usr/src/sys/kern/kern_shutdown.c:550 #3 0xc07ec648 in feed_vchan_s16 () from /boot/kernel/snd_pcm.ko #4 0xc07e2c6d in sndbuf_feed () from /boot/kernel/snd_pcm.ko #5 0xc07e3225 in chn_wrfeed () from /boot/kernel/snd_pcm.ko #6 0xc07e327c in chn_wrintr () from /boot/kernel/snd_pcm.ko #7 0xc07e3990 in chn_intr () from /boot/kernel/snd_pcm.ko #8 0xc07fca2f in csa_intr () from /boot/kernel/snd_csa.ko #9 0xc07fb724 in csa_intr () from /boot/kernel/snd_csa.ko #10 0xc04d1692 in ithread_loop (arg=0xc1737b00) at /usr/src/sys/kern/kern_intr.c:544 #11 0xc04d0684 in fork_exit (callout=0xc04d1500 , arg=0x0, frame=0x0) at /usr/src/sys/kern/kern_fork.c:796 Nearly all other panics (I put a collection of ~20 backtraces on http://stud4.tuwien.ac.at/~e0125637/fbsd/ if it's of any interest) ended up in file system code. From owner-freebsd-current@FreeBSD.ORG Sun Jan 4 14:48:18 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 7089016A4CE for ; Sun, 4 Jan 2004 14:48:18 -0800 (PST) Received: from sizone.org (mortar.sizone.org [65.126.154.242]) by mx1.FreeBSD.org (Postfix) with ESMTP id A78A743D31 for ; Sun, 4 Jan 2004 14:48:17 -0800 (PST) (envelope-from dgilbert@daveg.ca) Received: by sizone.org (Postfix, from userid 66) id 1133D307F1; Sun, 4 Jan 2004 17:48:17 -0500 (EST) Received: by canoe.dclg.ca (Postfix, from userid 101) id AC3851D1FFB; Sun, 4 Jan 2004 17:48:10 -0500 (EST) From: David Gilbert MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16376.38954.318620.955362@canoe.dclg.ca> Date: Sun, 4 Jan 2004 17:48:10 -0500 To: freebsd-current@freebsd.org X-Mailer: VM 7.17 under 21.4 (patch 14) "Reasonable Discussion" XEmacs Lucid Subject: Asymetry in the ndis driver. 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, 04 Jan 2004 22:48:18 -0000 It would seem there is some asymitry in the setup on the ndis driver. A few days ago, I reported that the FreeBSD access point had the ndis driver equiped laptop as being online at 2 megabit, but that the laptop itself was getting 11. That was incorrect. Its sending at 11 and receiving at 2. Is there some way I can approach fixing this? Dave. -- ============================================================================ |David Gilbert, Independent Contractor. | Two things can only be | |Mail: dave@daveg.ca | equal if and only if they | |http://daveg.ca | are precisely opposite. | =========================================================GLO================ From owner-freebsd-current@FreeBSD.ORG Sun Jan 4 15:02:25 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 8D57316A4CE; Sun, 4 Jan 2004 15:02:25 -0800 (PST) Received: from niobe.ijs.si (mail.ijs.si [193.2.4.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id A337243D1F; Sun, 4 Jan 2004 15:02:22 -0800 (PST) (envelope-from dejan.lesjak@ijs.si) Received: from localhost (localhost.ijs.si [127.0.0.1]) by niobe.ijs.si (Postfix) with ESMTP id B092C1DDE08; Mon, 5 Jan 2004 00:02:21 +0100 (CET) Received: from niobe.ijs.si ([193.2.4.66]) by localhost (niobe.ijs.si [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 40834-01; Mon, 5 Jan 2004 00:02:19 +0100 (CET) Received: from rincewind.ijs.si (rincewind.ijs.si [193.2.4.137]) by niobe.ijs.si (Postfix) with ESMTP id 3E9B61DDDF3; Mon, 5 Jan 2004 00:02:19 +0100 (CET) From: Dejan Lesjak To: Don Lewis Date: Mon, 5 Jan 2004 00:02:18 +0100 User-Agent: KMail/1.5.94 References: <200401042151.i04Lp27E009737@gw.catspoiler.org> In-Reply-To: <200401042151.i04Lp27E009737@gw.catspoiler.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200401050002.18767.dejan.lesjak@ijs.si> X-Virus-Scanned: by amavisd-new / Sophos+Sophie at ijs.si cc: ryans@gamersimpact.com cc: silby@silby.com cc: freebsd-current@FreeBSD.org cc: wpaul@FreeBSD.org Subject: Re: 5.2-RC oerrs and collisions on dc0 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, 04 Jan 2004 23:02:25 -0000 On Sunday 04 of January 2004 22:51, Don Lewis wrote: > I just took a closer look at the busdma diff, and this change to > dc_txeof() looks very suspicious: > > @@ -2663,7 +2809,7 @@ > if (txstat & DC_TXSTAT_OWN) > break; > > - if (!(cur_tx->dc_ctl & DC_TXCTL_LASTFRAG) || > + if (!(cur_tx->dc_ctl & DC_TXCTL_FIRSTFRAG) || > cur_tx->dc_ctl & DC_TXCTL_SETUP) { > if (cur_tx->dc_ctl & DC_TXCTL_SETUP) { > /* > > The code in the "if" block ends with a "continue" which will cause the > error handling code to be skipped if the "if" condition is true. I'm > pretty sure that the error status bits are only set in the last > descriptor for the frame, so we want to execute the "continue" unless > the DC_TXCTL_LASTFRAG bit is set. > > Try reverting this part of the busdma change. I tried this; although I'm now getting watchdog timeouts, I don't see any collisions and the few output errors probably come from timeouts. So I guess this is in the right direction. Could it be that we still need to do these lines: sc->dc_cdata.dc_tx_cnt--; DC_INC(idx, DC_TX_LIST_CNT); unless DC_TXCTL_FIRSTFRAG is set? I'll try playing with this now and see how it goes... Dejan From owner-freebsd-current@FreeBSD.ORG Sun Jan 4 15:11:12 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 5096616A4CE for ; Sun, 4 Jan 2004 15:11:12 -0800 (PST) Received: from root.org (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id AFCD343D41 for ; Sun, 4 Jan 2004 15:11:09 -0800 (PST) (envelope-from nate@root.org) Received: (qmail 19746 invoked by uid 1000); 4 Jan 2004 23:10:41 -0000 Date: Sun, 4 Jan 2004 15:10:41 -0800 (PST) From: Nate Lawson To: "M. Warner Losh" In-Reply-To: <20040104.003330.54786488.imp@bsdimp.com> Message-ID: <20040104150929.Y19715@root.org> References: <20040103184934.V16815@root.org> <20040103.201530.04738741.imp@bsdimp.com> <20040104.003330.54786488.imp@bsdimp.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org Subject: Re: Serial console only works after reboot? 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, 04 Jan 2004 23:11:12 -0000 On Sun, 4 Jan 2004, M. Warner Losh wrote: > In message: <20040103233044.N17367@root.org> > Nate Lawson writes: > : On Sat, 3 Jan 2004, M. Warner Losh wrote: > : > In message: <20040103184934.V16815@root.org> > : > Nate Lawson writes: > : > : I have a laptop (IBM T23) and use sio0 as my console/gdb port. One thing > : > : I noticed is if I power up the laptop and boot -h, I get garbage out the > : > : serial port. However, if I boot fully and then just warm reboot, the > : > : serial console works fine. I'm only using 9600 bps. Ideas? > : > > : > weird. Is the garbage data at some different rate? > : > : Nope, checked everything from 1200 up to 38400, different garbage but > : always garbage. This is with -current as of 2003/12/30, no patches. > > Try 115200. That works. Now the question is "why". Note that I have no "options CONSPEED" so according to /sys/dev/sio/sioreg.h, it should default to 9600 and indeed does, after a reboot. But not on a cold startup. -Nate From owner-freebsd-current@FreeBSD.ORG Sun Jan 4 15:42:25 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 7B04A16A4F5 for ; Sun, 4 Jan 2004 15:42:24 -0800 (PST) Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id A1CD043D9F for ; Sun, 4 Jan 2004 15:41:44 -0800 (PST) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.10/8.12.9) with ESMTP id i04NfWET027012; Sun, 4 Jan 2004 16:41:32 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Sun, 04 Jan 2004 16:41:03 -0700 (MST) Message-Id: <20040104.164103.03383403.imp@bsdimp.com> To: nate@root.org From: "M. Warner Losh" In-Reply-To: <20040104150929.Y19715@root.org> References: <20040103233044.N17367@root.org> <20040104.003330.54786488.imp@bsdimp.com> <20040104150929.Y19715@root.org> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: current@freebsd.org Subject: Re: Serial console only works after reboot? 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, 04 Jan 2004 23:42:25 -0000 In message: <20040104150929.Y19715@root.org> Nate Lawson writes: : On Sun, 4 Jan 2004, M. Warner Losh wrote: : > In message: <20040103233044.N17367@root.org> : > Nate Lawson writes: : > : On Sat, 3 Jan 2004, M. Warner Losh wrote: : > : > In message: <20040103184934.V16815@root.org> : > : > Nate Lawson writes: : > : > : I have a laptop (IBM T23) and use sio0 as my console/gdb port. One thing : > : > : I noticed is if I power up the laptop and boot -h, I get garbage out the : > : > : serial port. However, if I boot fully and then just warm reboot, the : > : > : serial console works fine. I'm only using 9600 bps. Ideas? : > : > : > : > weird. Is the garbage data at some different rate? : > : : > : Nope, checked everything from 1200 up to 38400, different garbage but : > : always garbage. This is with -current as of 2003/12/30, no patches. : > : > Try 115200. : : That works. Now the question is "why". Note that I have no "options : CONSPEED" so according to /sys/dev/sio/sioreg.h, it should default to 9600 : and indeed does, after a reboot. But not on a cold startup. Somewhere along the way, it gets set to 115200. Maybe it is initialized to 115200 by the boot blocks? I think once there's a divisor programmed into the serial port, the kernel console code doesn't change it. I could be wrong about this, however.... Warner From owner-freebsd-current@FreeBSD.ORG Sun Jan 4 15:44:27 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 5491516A4CE; Sun, 4 Jan 2004 15:44:27 -0800 (PST) Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id CE5FF43D2D; Sun, 4 Jan 2004 15:44:25 -0800 (PST) (envelope-from truckman@FreeBSD.org) Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.12.9p2/8.12.9) with ESMTP id i04NiE7E009973; Sun, 4 Jan 2004 15:44:19 -0800 (PST) (envelope-from truckman@FreeBSD.org) Message-Id: <200401042344.i04NiE7E009973@gw.catspoiler.org> Date: Sun, 4 Jan 2004 15:44:14 -0800 (PST) From: Don Lewis To: dejan.lesjak@ijs.si In-Reply-To: <200401050002.18767.dejan.lesjak@ijs.si> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii cc: ryans@gamersimpact.com cc: silby@silby.com cc: freebsd-current@FreeBSD.org cc: wpaul@FreeBSD.org Subject: Re: 5.2-RC oerrs and collisions on dc0 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, 04 Jan 2004 23:44:27 -0000 On 5 Jan, Dejan Lesjak wrote: > On Sunday 04 of January 2004 22:51, Don Lewis wrote: >> I just took a closer look at the busdma diff, and this change to >> dc_txeof() looks very suspicious: >> >> @@ -2663,7 +2809,7 @@ >> if (txstat & DC_TXSTAT_OWN) >> break; >> >> - if (!(cur_tx->dc_ctl & DC_TXCTL_LASTFRAG) || >> + if (!(cur_tx->dc_ctl & DC_TXCTL_FIRSTFRAG) || >> cur_tx->dc_ctl & DC_TXCTL_SETUP) { >> if (cur_tx->dc_ctl & DC_TXCTL_SETUP) { >> /* >> >> The code in the "if" block ends with a "continue" which will cause the >> error handling code to be skipped if the "if" condition is true. I'm >> pretty sure that the error status bits are only set in the last >> descriptor for the frame, so we want to execute the "continue" unless >> the DC_TXCTL_LASTFRAG bit is set. >> >> Try reverting this part of the busdma change. > > I tried this; although I'm now getting watchdog timeouts, I don't see any > collisions and the few output errors probably come from timeouts. So I guess > this is in the right direction. Could it be that we still need to do these > lines: > sc->dc_cdata.dc_tx_cnt--; > DC_INC(idx, DC_TX_LIST_CNT); > unless DC_TXCTL_FIRSTFRAG is set? I'll try playing with this now and see how > it goes... These two statements need to be executed for each iteration of the outer "while" loop unless DC_TXSTAT_OWN is set. Since these two statements are at the end of the "while" block, they have to be duplicated in the "if" block so that these actions are taken before executing the "continue" statement, which will skip these statements at the end of the "while". I don't know where this particular change came from, but it is not related to the busdma change. BTW, when testing the FIRSTFRAG flag instead of the LASTFRAG flag, you should not see any errors when only sending small packets (that fit in one mbuf). The reason is that in this case both the FIRSTFRAG and LASTFRAG bits will be set at the same time. The other errors might have caused dc_init() to be called frequently enough to mask the cause of the watchdog timeouts. From owner-freebsd-current@FreeBSD.ORG Sun Jan 4 16:38: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 D1B3116A4CF for ; Sun, 4 Jan 2004 16:38:10 -0800 (PST) Received: from arginine.spc.org (arginine.spc.org [195.206.69.236]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9E32743D1D for ; Sun, 4 Jan 2004 16:38:08 -0800 (PST) (envelope-from bms@spc.org) Received: from localhost (localhost [127.0.0.1]) by arginine.spc.org (Postfix) with ESMTP id 7C9C46547E; Mon, 5 Jan 2004 00:38:06 +0000 (GMT) Received: from arginine.spc.org ([127.0.0.1]) by localhost (arginine.spc.org [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 65721-02-15; Mon, 5 Jan 2004 00:38:06 +0000 (GMT) Received: from saboteur.dek.spc.org (unknown [82.147.19.119]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by arginine.spc.org (Postfix) with ESMTP id E9FC365468; Mon, 5 Jan 2004 00:38:04 +0000 (GMT) Received: by saboteur.dek.spc.org (Postfix, from userid 1001) id CDA5B40; Mon, 5 Jan 2004 00:38:03 +0000 (GMT) Date: Mon, 5 Jan 2004 00:38:03 +0000 From: Bruce M Simpson To: "M. Warner Losh" Message-ID: <20040105003803.GB59922@saboteur.dek.spc.org> References: <20040103233044.N17367@root.org> <20040104.003330.54786488.imp@bsdimp.com> <20040104150929.Y19715@root.org> <20040104.164103.03383403.imp@bsdimp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040104.164103.03383403.imp@bsdimp.com> cc: current@freebsd.org cc: nate@root.org Subject: Re: Serial console only works after reboot? 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: Mon, 05 Jan 2004 00:38:10 -0000 On Sun, Jan 04, 2004 at 04:41:03PM -0700, M. Warner Losh wrote: > Somewhere along the way, it gets set to 115200. Maybe it is > initialized to 115200 by the boot blocks? I think once there's a > divisor programmed into the serial port, the kernel console code > doesn't change it. I could be wrong about this, however.... Try installing boot0sio as your boot manager. It specifically requests 9600 8-N-1 via BIOS calls. However this does mean that boot selection has to happen over COM1. BMS From owner-freebsd-current@FreeBSD.ORG Sun Jan 4 17:02:41 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 0161D16A4CE for ; Sun, 4 Jan 2004 17:02:41 -0800 (PST) Received: from out008.verizon.net (out008pub.verizon.net [206.46.170.108]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3E01143D49 for ; Sun, 4 Jan 2004 17:02:28 -0800 (PST) (envelope-from Alex.Kovalenko@verizon.net) Received: from RabbitsDen ([138.89.12.104]) by out008.verizon.net (InterMail vM.5.01.06.06 201-253-122-130-106-20030910) with ESMTP id <20040105010227.VUXE19191.out008.verizon.net@RabbitsDen> for ; Sun, 4 Jan 2004 19:02:27 -0600 Date: Sun, 4 Jan 2004 20:02:25 -0500 From: Alexandre "Sunny" Kovalenko To: freebsd-current@freebsd.org Message-Id: <20040104200225.1478c66f.Alex.Kovalenko@verizon.net> In-Reply-To: <20040104161942.GE3628@loge.home.paeps.cx> References: <16373.49080.401073.12711@canoe.dclg.ca> <20040104161942.GE3628@loge.home.paeps.cx> Organization: Home X-Mailer: Sylpheed version 0.9.7 (GTK+ 1.2.10; i386-portbld-freebsd5.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Authentication-Info: Submitted using SMTP AUTH at out008.verizon.net from [138.89.12.104] at Sun, 4 Jan 2004 19:02:27 -0600 Subject: Undefined symbols in ACPI module 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: Mon, 05 Jan 2004 01:02:41 -0000 I don't know if this was reported yet -- with cvsup of -CURRENT as of 14:40 EST following problem occured while loading ACPI module: Preloaded elf module "/boot/kernel/acpi.ko" at 0xc08a3264. link_elf: symbol AcpiDmDumpMethodInfo undefined KLD file acpi.ko - could not finalize loading symbol seems to be defined in sys/contrib/dev/acpica/dmobject.c but file is not compiled and included into the module. Last known good cvsup was around December 21st. If it is of any use, I can send list of files cvsup had updated immediately prior to the breakage. --- Alexandre "Sunny" Kovalenko. From owner-freebsd-current@FreeBSD.ORG Sun Jan 4 19:25: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 B267616A4CE for ; Sun, 4 Jan 2004 19:25:00 -0800 (PST) Received: from sage.ts.co.nz (sage.tasman.net [202.49.92.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id AA42543D39 for ; Sun, 4 Jan 2004 19:24:57 -0800 (PST) (envelope-from marcos@thepacific.net) Received: from sage.ts.co.nz ([172.16.21.1]) by sage.ts.co.nz (8.12.3/8.12.10) with ESMTP id i053NApi020159 for ; Mon, 5 Jan 2004 16:24:03 +1300 Received: from thepacific.net (gateway-nelson.thepacific.net [202.49.95.33]) by sage.ts.co.nz (8.12.3/8.12.10) with ESMTP id i053LsnU019932 for ; Mon, 5 Jan 2004 16:21:55 +1300 Message-ID: <3FF8D833.8080708@thepacific.net> Date: Mon, 05 Jan 2004 16:21:23 +1300 From: "Marcos Biscaysaqu - ThePacific.net" User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-current@freebsd.org Content-Type: multipart/mixed; boundary="------------080302020002000202010708" X-Content-Filtered-By: Mailman/MimeDel 2.1.1 Subject: Atheros: ath0 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: Mon, 05 Jan 2004 03:25:00 -0000 This is a multi-part message in MIME format. --------------080302020002000202010708 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hi there. I been testing for acouple month the Atheros wireless as AP on BSD, I has the last version driver (1.38) running on my BSD-AP on 11b, I've got no Crashes problem but Im still with problem when I have some more hevy traffic, the wireless interface srtart to create Irrers and Orrers and that make the connections with the clients (I've got 32 clients on the BSD-AP) unstable and very slow with ping times as 1000 ms when normaly should be 2ms, This dosen't happend at all if I use a Prism card or a good commercial AP. I try with lot of differents card with the same final. the speed of the BSD-AP is faster than any commercial AP on 11b but the point-to-point (adhoc) dosen't work yet same to change things like RTS/CTS etc... Please Somebody has this problems??, is possible fix it?? thanks Marcos --------------080302020002000202010708-- From owner-freebsd-current@FreeBSD.ORG Sun Jan 4 19:49:08 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 B049F16A4CE for ; Sun, 4 Jan 2004 19:49:08 -0800 (PST) Received: from www.ambrisko.com (adsl-64-174-51-42.dsl.snfc21.pacbell.net [64.174.51.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 94D0C43D2F for ; Sun, 4 Jan 2004 19:49:07 -0800 (PST) (envelope-from ambrisko@ambrisko.com) Received: from ambrisko.com (localhost [127.0.0.1]) by www.ambrisko.com (8.12.9p2/8.12.9) with ESMTP id i053n7ni036933; Sun, 4 Jan 2004 19:49:07 -0800 (PST) (envelope-from ambrisko@ambrisko.com) Received: (from ambrisko@localhost) by ambrisko.com (8.12.9p2/8.12.9/Submit) id i053n7j0036932; Sun, 4 Jan 2004 19:49:07 -0800 (PST) (envelope-from ambrisko) From: Doug Ambrisko Message-Id: <200401050349.i053n7j0036932@ambrisko.com> In-Reply-To: <20040103184934.V16815@root.org> To: Nate Lawson Date: Sun, 4 Jan 2004 19:49:07 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL94b (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII cc: current@freebsd.org Subject: Re: Serial console only works after reboot? 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: Mon, 05 Jan 2004 03:49:08 -0000 Nate Lawson writes: | I have a laptop (IBM T23) and use sio0 as my console/gdb port. One thing | I noticed is if I power up the laptop and boot -h, I get garbage out the | serial port. However, if I boot fully and then just warm reboot, the | serial console works fine. I'm only using 9600 bps. Ideas? | | sio0 port 0x3f8-0x3ff irq 4 on acpi0 | sio0: type 16550A I use this patch on a lot of systems to force it to CONSPEED and not try to auto-detect what the prior boot-loaders etc. had set it up. In my case a lot of the time nothing ever set the port up and it gets random junk the messes up the speed etc. Index: sio.c =================================================================== RCS file: /cvs/src/sys/dev/sio/sio.c,v retrieving revision 1.417 diff -c -r1.417 sio.c *** sio.c 24 Dec 2003 04:11:10 -0000 1.417 --- sio.c 5 Jan 2004 03:46:27 -0000 *************** *** 2832,2838 **** --- 2832,2841 ---- /* XXX there should be more sanity checking. */ if (divisor == 0) return (CONSPEED); + /* DJA return (rclk / (16UL * divisor)); + */ + return (CONSPEED); } #endif Doug A. From owner-freebsd-current@FreeBSD.ORG Sun Jan 4 20:34:14 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 5ED5B16A4CE; Sun, 4 Jan 2004 20:34:14 -0800 (PST) Received: from srv1.cosmo-project.de (srv1.cosmo-project.de [213.83.6.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id C309B43D2F; Sun, 4 Jan 2004 20:34:07 -0800 (PST) (envelope-from ticso@cicely12.cicely.de) Received: from cicely5.cicely.de (cicely5.cicely.de [IPv6:3ffe:400:8d0:301:200:92ff:fe9b:20e7]) (authenticated bits=0) i054XrN1056155 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=OK); Mon, 5 Jan 2004 05:33:55 +0100 (CET) (envelope-from ticso@cicely12.cicely.de) Received: from cicely12.cicely.de (cicely12.cicely.de [IPv6:3ffe:400:8d0:301::12]) by cicely5.cicely.de (8.12.10/8.12.10) with ESMTP id i054XaMO020244 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 5 Jan 2004 05:33:37 +0100 (CET) (envelope-from ticso@cicely12.cicely.de) Received: from cicely12.cicely.de (localhost [127.0.0.1]) by cicely12.cicely.de (8.12.10/8.12.10) with ESMTP id i054XaBE035922; Mon, 5 Jan 2004 05:33:36 +0100 (CET) (envelope-from ticso@cicely12.cicely.de) Received: (from ticso@localhost) by cicely12.cicely.de (8.12.10/8.12.10/Submit) id i054XZEe035921; Mon, 5 Jan 2004 05:33:35 +0100 (CET) (envelope-from ticso) Date: Mon, 5 Jan 2004 05:33:35 +0100 From: Bernd Walter To: John Baldwin Message-ID: <20040105043334.GB17023@cicely12.cicely.de> References: <20040102195244.GE17023@cicely12.cicely.de> <20040102224015.GI17023@cicely12.cicely.de> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="neYutvxvOLaeuPCA" Content-Disposition: inline In-Reply-To: <20040102224015.GI17023@cicely12.cicely.de> X-Operating-System: FreeBSD cicely12.cicely.de 5.2-CURRENT alpha User-Agent: Mutt/1.5.4i X-Spam-Status: No, hits=-4.9 required=3.0 tests=BAYES_00 autolearn=ham version=2.61 X-Spam-Report: * -4.9 BAYES_00 BODY: Bayesian spam probability is 0 to 1% * [score: 0.0000] X-Spam-Checker-Version: SpamAssassin 2.61 (1.212.2.1-2003-12-09-exp) on cicely5.cicely.de cc: Bernd Walter cc: ticso@cicely.de cc: current@FreeBSD.org Subject: Re: Still IRQ routing problems with bridged devices. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: ticso@cicely.de List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Jan 2004 04:34:14 -0000 --neYutvxvOLaeuPCA Content-Type: text/plain; charset=us-ascii Content-Disposition: inline OK - this is not related to bridges and not to this special board. Today I saw this on an Asus P2B: pcibios: BIOS version 2.10 Using $PIR table, 6 entries at 0xc00f0d10 pcib0: at pcibus 0 on motherboard [...] uhci0: port 0xd400-0xd41f at device 4.2 on pci0 pci_cfgintr: 0:4 INTD routed to irq 4 [...] sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A As the system is currently declared for testing it's much easier to test and debug this on that one. boot -v dmesg attached. -- B.Walter BWCT http://www.bwct.de ticso@bwct.de info@bwct.de --neYutvxvOLaeuPCA Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="dmesg.c13" Copyright (c) 1992-2003 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.1-CURRENT #0: Mon Jan 5 03:50:08 CET 2004 ticso@cicely13.cicely.de:/var/d7/builder/c13-2003-11-22/src/sys/i386/compile/CICELY13-P2B Preloaded elf kernel "/boot/kernel/kernel" at 0xc0750000. Calibrating clock(s) ... i8254 clock: 1193157 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz quality 0 Calibrating TSC clock ... TSC clock: 334093181 Hz CPU: Pentium II/Pentium II Xeon/Celeron (334.09-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x650 Stepping = 0 Features=0x183f9ff real memory = 167759872 (159 MB) Physical memory chunk(s): 0x0000000000001000 - 0x000000000009ffff, 651264 bytes (159 pages) 0x0000000000100000 - 0x00000000003fffff, 3145728 bytes (768 pages) 0x0000000000826000 - 0x0000000009ce6fff, 155979776 bytes (38081 pages) avail memory = 157405184 (150 MB) bios32: Found BIOS32 Service Directory header at 0xc00f9d50 bios32: Entry = 0xf0520 (c00f0520) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xf0000+0x720 pnpbios: Found PnP BIOS data at 0xc00fd1a0 pnpbios: Entry = f0000:d1d0 Rev = 1.0 pnpbios: OEM ID cd041 Other BIOS signatures found: random: mem: Pentium Pro MTRR support enabled null: npx0: [FAST] npx0: on motherboard npx0: INT 16 interface pci_open(1): mode 1 addr port (0x0cf8) is 0x8000005c pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=71908086) pcibios: BIOS version 2.10 Using $PIR table, 6 entries at 0xc00f0d10 PCI-Only Interrupts: none Location Bus Device Pin Link IRQs slot 1 0 12 A 0x60 3 4 5 7 9 10 11 12 slot 1 0 12 B 0x61 3 4 5 7 9 10 11 12 slot 1 0 12 C 0x62 3 4 5 7 9 10 11 12 slot 1 0 12 D 0x63 3 4 5 7 9 10 11 12 slot 2 0 11 A 0x61 3 4 5 7 9 10 11 12 slot 2 0 11 B 0x62 3 4 5 7 9 10 11 12 slot 2 0 11 C 0x63 3 4 5 7 9 10 11 12 slot 2 0 11 D 0x60 3 4 5 7 9 10 11 12 slot 3 0 10 A 0x62 3 4 5 7 9 10 11 12 slot 3 0 10 B 0x63 3 4 5 7 9 10 11 12 slot 3 0 10 C 0x60 3 4 5 7 9 10 11 12 slot 3 0 10 D 0x61 3 4 5 7 9 10 11 12 slot 4 0 9 A 0x63 3 4 5 7 9 10 11 12 slot 4 0 9 B 0x60 3 4 5 7 9 10 11 12 slot 4 0 9 C 0x61 3 4 5 7 9 10 11 12 slot 4 0 9 D 0x62 3 4 5 7 9 10 11 12 embedded 0 4 A 0x60 3 4 5 7 9 10 11 12 embedded 0 4 B 0x61 3 4 5 7 9 10 11 12 embedded 0 4 C 0x62 3 4 5 7 9 10 11 12 embedded 0 4 D 0x63 3 4 5 7 9 10 11 12 embedded 0 1 A 0x60 3 4 5 7 9 10 11 12 embedded 0 1 B 0x61 3 4 5 7 9 10 11 12 embedded 0 1 C 0x62 3 4 5 7 9 10 11 12 embedded 0 1 D 0x63 3 4 5 7 9 10 11 12 pcib0: at pcibus 0 on motherboard pci0: on pcib0 pci0: physical bus=0 map[10]: type 3, range 32, base e4000000, size 26, enabled found-> vendor=0x8086, dev=0x7190, revid=0x03 bus=0, slot=0, func=0 class=06-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0106, statreg=0x2210, cachelnsz=0 (dwords) lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x8086, dev=0x7191, revid=0x03 bus=0, slot=1, func=0 class=06-04-00, hdrtype=0x01, mfdev=0 cmdreg=0x0117, statreg=0x0220, cachelnsz=0 (dwords) lattimer=0x40 (1920 ns), mingnt=0x80 (32000 ns), maxlat=0x00 (0 ns) found-> vendor=0x8086, dev=0x7110, revid=0x02 bus=0, slot=4, func=0 class=06-01-00, hdrtype=0x00, mfdev=1 cmdreg=0x000f, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) map[20]: type 4, range 32, base 0000d800, size 4, enabled found-> vendor=0x8086, dev=0x7111, revid=0x01 bus=0, slot=4, func=1 class=01-01-80, hdrtype=0x00, mfdev=0 cmdreg=0x0005, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x20 (960 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) map[20]: type 4, range 32, base 0000d400, size 5, enabled found-> vendor=0x8086, dev=0x7112, revid=0x01 bus=0, slot=4, func=2 class=0c-03-00, hdrtype=0x00, mfdev=0 cmdreg=0x0005, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x20 (960 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=d, irq=255 map[90]: type 4, range 32, base 0000e800, size 4, enabled found-> vendor=0x8086, dev=0x7113, revid=0x02 bus=0, slot=4, func=3 class=06-80-00, hdrtype=0x00, mfdev=0 cmdreg=0x0003, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) map[10]: type 4, range 32, base 0000d000, size 7, enabled map[14]: type 1, range 32, base e3000000, size 7, enabled pci_cfgintr_valid: BIOS irq 10 is valid pci_cfgintr: 0:10 INTA BIOS irq 10 found-> vendor=0x1011, dev=0x0009, revid=0x20 bus=0, slot=10, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x20 (960 ns), mingnt=0x14 (5000 ns), maxlat=0x28 (10000 ns) intpin=a, irq=10 map[10]: type 1, range 32, base dc000000, size 26, enabled pci_cfgintr_valid: BIOS irq 11 is valid pci_cfgintr: 0:12 INTA BIOS irq 11 found-> vendor=0x5333, dev=0x8901, revid=0x16 bus=0, slot=12, func=0 class=03-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0023, statreg=0x0200, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=11 pcib1: at device 1.0 on pci0 pcib1: secondary bus 1 pcib1: subordinate bus 1 pcib1: I/O decode 0xe000-0xdfff pcib1: memory decode 0xe3f00000-0xe3efffff pcib1: prefetched decode 0xe4000000-0xe3ffffff pci1: on pcib1 pci1: physical bus=1 isab0: at device 4.0 on pci0 isa0: on isab0 atapci0: port 0xd800-0xd80f at device 4.1 on pci0 ata0: reset tp1 mask=03 ostat0=50 ostat1=00 ata0-master: stat=0x50 err=0x01 lsb=0x00 msb=0x00 ata0-slave: stat=0x00 err=0x00 lsb=0x00 msb=0x00 ata0: reset tp2 mask=03 stat0=50 stat1=00 devices=0x1 ata0: at 0x1f0 irq 14 on atapci0 ata0: [MPSAFE] ata1: reset tp1 mask=03 ostat0=00 ostat1=00 ata1-master: stat=0x00 err=0x00 lsb=0x00 msb=0x00 ata1-slave: stat=0x00 err=0x00 lsb=0x00 msb=0x00 ata1: reset tp2 mask=03 stat0=00 stat1=00 devices=0x0 ata1: at 0x170 irq 15 on atapci0 ata1: [MPSAFE] uhci0: port 0xd400-0xd41f at device 4.2 on pci0 pci_cfgintr_virgin: using routable interrupt 4 pci_cfgintr: 0:4 INTD routed to irq 4 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 intpm0: port 0xe800-0xe80f irq 9 at device 4.3 on pci0 intpm0: I/O mapped e800 intpm0: intr IRQ 9 enabled revision 0 intsmb0: on intpm0 smbus0: on intsmb0 smb0: on smbus0 intpm0: PM I/O mapped e400 de0: port 0xd000-0xd07f mem 0xe3000000-0xe300007f irq 10 at device 10.0 on pci0 de0: Cogent 21140A [10-100Mb/s] pass 2.0 de0: address 00:00:92:9b:31:51 de0: bpf attached pci0: at device 12.0 (no driver attached) ata: ata0 already exists; skipping it ata: ata1 already exists; skipping it Trying Read_Port at 203 Trying Read_Port at 243 Trying Read_Port at 283 Trying Read_Port at 2c3 Trying Read_Port at 303 Trying Read_Port at 343 Trying Read_Port at 383 Trying Read_Port at 3c3 pnpbios: 14 devices, largest 114 bytes PNP0400: adding irq mask 0x80 PNP0400: adding io range 0x378-0x37f, size=0x8, align=0 PNP0400: adding io range 0x778-0x77f, size=0x8, align=0 pnpbios: handle 0 device ID PNP0400 (0004d041) PNP0501: adding irq mask 0x10 PNP0501: adding io range 0x3f8-0x3ff, size=0x8, align=0 pnpbios: handle 2 device ID PNP0501 (0105d041) PNP0501: adding irq mask 0x8 PNP0501: adding io range 0x2f8-0x2ff, size=0x8, align=0 pnpbios: handle 3 device ID PNP0501 (0105d041) PNP0700: adding irq mask 0x40 PNP0700: adding dma mask 0x4 PNP0700: adding io range 0x3f2-0x3f5, size=0x4, align=0 pnpbios: handle 4 device ID PNP0700 (0007d041) PNP0c01: adding fixed memory32 range 0-0x9ffff, size=0xa0000 PNP0c01: adding fixed memory32 range 0x100000-0x9ffffff, size=0x9f00000 PNP0c01: adding fixed memory32 range 0xe8000-0xeffff, size=0x8000 PNP0c01: adding fixed memory32 range 0xf0000-0xf3fff, size=0x4000 PNP0c01: adding fixed memory32 range 0xf4000-0xf7fff, size=0x4000 PNP0c01: adding fixed memory32 range 0xf8000-0xfbfff, size=0x4000 PNP0c01: adding fixed memory32 range 0xfc000-0xfffff, size=0x4000 PNP0c01: adding fixed memory32 range 0xfffe0000-0xffffffff, size=0x20000 pnpbios: handle 6 device ID PNP0c01 (010cd041) PNP0100: adding irq mask 0x1 PNP0100: adding io range 0x40-0x43, size=0x4, align=0 pnpbios: handle 8 device ID PNP0100 (0001d041) PNP0b00: adding irq mask 0x100 PNP0b00: adding io range 0x70-0x71, size=0x2, align=0 pnpbios: handle 9 device ID PNP0b00 (000bd041) PNP0303: adding irq mask 0x2 PNP0303: adding io range 0x60-0x60, size=0x1, align=0 PNP0303: adding io range 0x64-0x64, size=0x1, align=0 pnpbios: handle 10 device ID PNP0303 (0303d041) PNP0c04: adding irq mask 0x2000 PNP0c04: adding io range 0xf0-0xf0, size=0x1, align=0 pnpbios: handle 11 device ID PNP0c04 (040cd041) PNP0200: adding dma mask 0x10 PNP0200: adding io range 0-0xf, size=0x10, align=0 PNP0200: adding io range 0x80-0x90, size=0x11, align=0 PNP0200: adding io range 0x94-0x9f, size=0xc, align=0 PNP0200: adding io range 0xc0-0xde, size=0x1f, align=0 pnpbios: handle 12 device ID PNP0200 (0002d041) PNP0800: adding io range 0x61-0x61, size=0x1, align=0x1 pnpbios: handle 13 device ID PNP0800 (0008d041) PNP0a03: adding io range 0xcf8-0xcff, size=0x8, align=0 pnpbios: handle 14 device ID PNP0a03 (030ad041) PNP0c02: adding io range 0x290-0x297, size=0x8, align=0 PNP0c02: adding io range 0xe400-0xe43f, size=0x40, align=0 PNP0c02: adding io range 0xe800-0xe83f, size=0x40, align=0 pnpbios: handle 15 device ID PNP0c02 (020cd041) sc: sc0 already exists; skipping it vga: vga0 already exists; skipping it isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices orm0: