From owner-freebsd-amd64@FreeBSD.ORG Sat Jun 19 23:50:02 2010 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5644E1065676 for ; Sat, 19 Jun 2010 23:50:02 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 1A4E48FC28 for ; Sat, 19 Jun 2010 23:50:02 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o5JNo1c6003485 for ; Sat, 19 Jun 2010 23:50:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o5JNo1Qk003484; Sat, 19 Jun 2010 23:50:01 GMT (envelope-from gnats) Resent-Date: Sat, 19 Jun 2010 23:50:01 GMT Resent-Message-Id: <201006192350.o5JNo1Qk003484@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-amd64@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Mike Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1611E106566C for ; Sat, 19 Jun 2010 23:45:25 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (www.freebsd.org [IPv6:2001:4f8:fff6::21]) by mx1.freebsd.org (Postfix) with ESMTP id 0500C8FC0C for ; Sat, 19 Jun 2010 23:45:25 +0000 (UTC) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.14.3/8.14.3) with ESMTP id o5JNjOZs023427 for ; Sat, 19 Jun 2010 23:45:24 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.14.3/8.14.3/Submit) id o5JNjOpl023426; Sat, 19 Jun 2010 23:45:24 GMT (envelope-from nobody) Message-Id: <201006192345.o5JNjOpl023426@www.freebsd.org> Date: Sat, 19 Jun 2010 23:45:24 GMT From: Mike To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.1 X-Mailman-Approved-At: Sun, 20 Jun 2010 00:51:14 +0000 Cc: Subject: amd64/148002: panic / page fault while booting from install dvd on asrock 939-dual sata X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Jun 2010 23:50:02 -0000 >Number: 148002 >Category: amd64 >Synopsis: panic / page fault while booting from install dvd on asrock 939-dual sata >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sat Jun 19 23:50:01 UTC 2010 >Closed-Date: >Last-Modified: >Originator: Mike >Release: 8.0-Release >Organization: >Environment: unable to do, machine doesn't boot >Description: I downloaded the dvd from one of the ftp mirrors, burned it and tried to boot from it. Right after harddisk detection the kernel panics like this: fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault = virtual address = 0x0 fault code = supervisor read, page not present instruction pointer = 0x20:0x0 stack pointer = 0x28:0xe5b64b68 frame pointer = 0x28:0xe5b64b9c code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor iflags = interrupt enabled, resume, IOPL = 0 current process = 4 (g_down) trap number = 12 panic: page fault cpuid = 0 Uptime: 2s Hardware: Mainboard: ASRock 939Dual-SATA2 CPU: AMD Athlon 64 (2GHz) RAM: 2GBytes DDR400 Video Card: nVida Gefroce 7300GS HDD: 2 Sata150 Disks, connected to the SATA connectors on the board. SATA2 is disabled. Tried to deactivate ACPI, set kern.smp.disabled from loaderprompt, both didn't help. Tried to boot i386 dvd instead of i386-64: didn't work either with the same panic. Tried FreeBSD 7.2/i386: booted cleanly, was able to install. >How-To-Repeat: Get this very hardware, try to boot with FreeBSD 8.0 => crash >Fix: >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-amd64@FreeBSD.ORG Mon Jun 21 11:06:50 2010 Return-Path: Delivered-To: freebsd-amd64@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EBDA01065675 for ; Mon, 21 Jun 2010 11:06:50 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id C00288FC1C for ; Mon, 21 Jun 2010 11:06:50 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o5LB6o8b098179 for ; Mon, 21 Jun 2010 11:06:50 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o5LB6oga098177 for freebsd-amd64@FreeBSD.org; Mon, 21 Jun 2010 11:06:50 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 21 Jun 2010 11:06:50 GMT Message-Id: <201006211106.o5LB6oga098177@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-amd64@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-amd64@FreeBSD.org X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Jun 2010 11:06:51 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o amd64/148002 amd64 [boot] panic / page fault while booting from install d o amd64/147963 amd64 cpu l2 cache error o amd64/147560 amd64 [boot] Booting 8.1-PRERELEASE raidz system take ages o amd64/145991 amd64 [patch] Add a requires line to /sys/amd64/conf/NOTES o amd64/145873 amd64 [build] cannot buildworld 8.0-STABLE o amd64/145761 amd64 [lor] rt2870 lock order reversal hold up system in 8.0 o amd64/145039 amd64 spin lock held too long amd64 mp_machdep.c o amd64/144756 amd64 [panic] Transferring files on samba causes the kernel f amd64/144503 amd64 [boot] 8.0-RELEASE does not boot on DL585 [regression] o amd64/144405 amd64 [build] [patch] include /usr/obj/lib32 in cleanworld t o amd64/144376 amd64 [panic] continuous reboot on motherboards with ATI SB7 f amd64/144151 amd64 [ata] Can not burn CD/DVD with AHCI enabled f amd64/144113 amd64 [ata] 8.0-RELEASE fails to detect SATA hard disks on a o amd64/143992 amd64 [panic] Random reboot o amd64/143854 amd64 [build] error in make world during upgrade from 7 to 8 s amd64/143173 amd64 [ata] Promise FastTrack TX4 + SATA DVD, installer can' o amd64/141413 amd64 [hang] Tyan 2881 m3289 SMDC freeze o amd64/141112 amd64 [ata] [panic] Kernel panic when booting with any sATA o amd64/141060 amd64 [install] Can't install 8.0-RELEASE on the server wher o amd64/140715 amd64 [boot] Dell M600 Blade fails to boot 7.2+ 64 bit o amd64/140596 amd64 [panic] Kernel panic/crash o amd64/140391 amd64 [hang] powerd(8) freezes computer on Phenom II compute o amd64/140145 amd64 [boot] Installation boot sequence freezes o amd64/139998 amd64 [panic] 7.2 amd64 panic in kern_mutex.c:339 o amd64/139924 amd64 [boot] cd or dvd not load o amd64/139614 amd64 [minidump] minidumps fail when many interrupts fire f amd64/138661 amd64 [panic] Kernel Panic after typing "reboot" o amd64/138029 amd64 [panic] periodically kernel panic and reboot o amd64/137942 amd64 [pci] 8.0-BETA2 having problems with Asus M2N-SLI-delu s i386/135447 amd64 [i386] [request] Intel Core i7 and Nehalem-EP new feat o amd64/135265 amd64 [install] Boot from install cd hangs on HP DL160 G5 wi o amd64/135040 amd64 [ata] FreeBSD/amd64 does not (always) detect disk on S o amd64/134978 amd64 [panic] g_up pmap amd64 panic o amd64/134757 amd64 32 bit processes on 64 bit platforms occasionally drop o amd64/133977 amd64 [panic] [ffs] "panic: ffs_blkfree: freeing free block" o amd64/133701 amd64 Recompiling the kernel with k8temp or smbios break GEO o amd64/132574 amd64 [boot] [hang] Freeze on bootstrap loader (CD) using AT f amd64/132019 amd64 [install] kernel trap 12 while installation o amd64/131906 amd64 [ata] SATA data corruption with Promise PDC20378 (amd6 o amd64/131456 amd64 ACPI & ATA problems o amd64/131314 amd64 [modules] [panic] large modules fail to load on amd64 o amd64/131209 amd64 [panic] [bce] 7.1-STABLE amd64 crash - m0 NULL f amd64/130885 amd64 sockstat(1) on amd64 does not work o amd64/130864 amd64 [hang] Problem with copying files to a large partition o amd64/130817 amd64 FreeBSD does not support HP DL160G5 [regression] o amd64/130494 amd64 [boot] netbooting BTX fails on amd64 f amd64/130483 amd64 [mxge] MSI must be disabled when Myricom 10Gbps Card i o amd64/130368 amd64 [hang] Switching from xorg to console locks up compute o amd64/129889 amd64 [boot] [hang] The booting process stops at the line mo o amd64/129721 amd64 [hang] Motherboard K9N2G Neo-FD hangs on boot of 7.0-R o amd64/129667 amd64 [ata] Elitegroup A780GM-A IDE controller not recognize o amd64/129426 amd64 [panic] FreeBSD 7.0 crash after subdiskXX: detached o amd64/129315 amd64 [boot] [reboot] amd64 motherboard: Intel DG965WH mothe o amd64/128978 amd64 [install] FreeBSD 6.3 64-bit panics at boot time duri o amd64/128765 amd64 [install] Install CD loads to Install choices but stop o amd64/128263 amd64 [panic] 2 amd64 dl380 g5 with dual quadcore xeons, 8 a o amd64/128259 amd64 csh(1): "`" crashes csh o amd64/127640 amd64 gcc(1) will not build shared libraries with -fprofile- o amd64/127484 amd64 [timecounters] Drift problem with FreeBSD 7.0 and 7.1 o amd64/127451 amd64 [scheduler] incorrect load on quad core o amd64/127397 amd64 [amd64] 32bit application on FreeBSD-6.3 amd64 gets SI s amd64/127276 amd64 ldd(1) invokes linux yes o amd64/125873 amd64 [smbd] [panic] Repeated kernel panics, trap 12 page fa o amd64/125002 amd64 [install] amd64, SATA hard disks not detected o amd64/124432 amd64 [panic] 7.0-STABLE panic: invalbuf: dirty bufs o amd64/124134 amd64 [kernel] The kernel doesn't follow the calling convent o amd64/123562 amd64 [install] FreeBSD amd64 not installs o amd64/123520 amd64 [ahd] unable to boot from net while using ahd p amd64/123456 amd64 fstat(1): /usr/bin/fstat shows error messages and hang f amd64/123275 amd64 [cbb] [pcmcia] cbb/pcmcia drivers on amd64 failure [re o kern/122782 amd64 [modules] accf_http.ko kernel module is not loadable o amd64/122695 amd64 [cpufreq] Lack of cpufreq control using amd64 eith cor o amd64/122549 amd64 7.0-RELEASE-amd64-bootonly.iso doesn't work w/ serial o amd64/122468 amd64 Compile problems after upgrading to 7.0 o amd64/122174 amd64 [panic] 7.0 no longer includes "device atpic" so fails f amd64/121590 amd64 [est] [p4tcc] [acpi_perf] setting dev.cpu.0.freq somet o amd64/120202 amd64 [amd64] [patch] [panic] kernel panic at start_all_aps, o amd64/119591 amd64 [amd64] [patch] time_t on 64-bit architecture o amd64/117418 amd64 [hang] FreeBSD 6.2 crash on amd64 4400+ with ssh o amd64/117316 amd64 [acpi] ACPI lockups on SuperMicro motherboard o amd64/117296 amd64 [ata] I don`t see second SATA IDE on VIA VT8237A a amd64/117186 amd64 [modules] kldload Unsupported file type on STABLE amd6 s amd64/116689 amd64 [request] support for MSI K9MM-V o amd64/116620 amd64 [hang] ifconfig spins when creating carp(4) device on o amd64/116322 amd64 [panic] At start fsck on current, the system panics o amd64/116159 amd64 [panic] Panic while debugging on CURRENT s amd64/115815 amd64 [ata] [request] Gigabyte GA-M61P-S3 Motherboard unsupp o amd64/115581 amd64 [Makefile] [patch] -mfancy-math-387 has no effect o amd64/115194 amd64 LCD screen remains blank after Dell XPS M1210 lid is c o amd64/114270 amd64 [cpufreq] cpufreq doesnt work when compiled in to kern o amd64/110599 amd64 [geli] geli attach to gmirror device hangs and cannot s amd64/108861 amd64 [nve] nve(4) driver on FreeBSD 6.2 AMD64 does not work o amd64/106186 amd64 [panic] panic in swap_pager_swap_init (amd64/smp/6.2-p f amd64/105531 amd64 [ata] gigabyte GA-M51GM-S2G / nVidia nForce 430 - does f amd64/105514 amd64 [boot] FreeBSD/amd64 - Fails to boot on HP Pavilion dv f amd64/102716 amd64 ex with no argument in an xterm gets SIGSEGV o amd64/97337 amd64 [dri] xorg reboots system if dri module is enabled o amd64/95888 amd64 [ata] kernel: ad2: TIMEOUT - WRITE_DMA retrying on HP o amd64/94677 amd64 [panic] panic in amd64 install at non-root user creati o amd64/93961 amd64 [busdma] Problem in bounce buffer handling in sys/amd6 o amd64/92337 amd64 [em] FreeBSD 6.0 Release Intel Pro 1000 MT em1 no buff o amd64/91405 amd64 [asr] [panic] Kernel panic caused by asr on 6.0-amd64 o amd64/89501 amd64 [install] System crashes on install using ftp on local o amd64/88790 amd64 [panic] kernel panic on first boot (after the FreeBSD o amd64/88568 amd64 [panic] 6.0-RELEASE install cd does not boot with usb o amd64/87689 amd64 [powerd] [hang] powerd hangs SMP Opteron 244 5-STABLE o amd64/87305 amd64 [smp] Dual Opteron / FreeBSD 5 & 6 / powerd results in s amd64/85273 amd64 [install] FreeBSD (NetBSD or OpenBSD) not install on l o amd64/78406 amd64 [panic]AMD64 w/ SCSI: issue 'rm -r /usr/ports' and sys o amd64/76136 amd64 [hang] system halts before reboot o amd64/74747 amd64 [panic] System panic on shutdown when process will not 111 problems total. From owner-freebsd-amd64@FreeBSD.ORG Mon Jun 21 13:21:56 2010 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D8B2E1065676; Mon, 21 Jun 2010 13:21:56 +0000 (UTC) (envelope-from gavin@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id B0D958FC17; Mon, 21 Jun 2010 13:21:56 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o5LDLuR3023514; Mon, 21 Jun 2010 13:21:56 GMT (envelope-from gavin@freefall.freebsd.org) Received: (from gavin@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o5LDLubN023510; Mon, 21 Jun 2010 13:21:56 GMT (envelope-from gavin) Date: Mon, 21 Jun 2010 13:21:56 GMT Message-Id: <201006211321.o5LDLubN023510@freefall.freebsd.org> To: stageline@gmail.com, gavin@FreeBSD.org, freebsd-amd64@FreeBSD.org From: gavin@FreeBSD.org Cc: Subject: Re: amd64/147963: cpu l2 cache error X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Jun 2010 13:21:56 -0000 Synopsis: cpu l2 cache error State-Changed-From-To: open->feedback State-Changed-By: gavin State-Changed-When: Mon Jun 21 13:21:33 UTC 2010 State-Changed-Why: Mark as awaiting feedback. This looks like it may be a hardware issue http://www.freebsd.org/cgi/query-pr.cgi?pr=147963 From owner-freebsd-amd64@FreeBSD.ORG Mon Jun 21 15:43:41 2010 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 074D8106566B; Mon, 21 Jun 2010 15:43:41 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id CDE378FC19; Mon, 21 Jun 2010 15:43:40 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id 5988246B46; Mon, 21 Jun 2010 11:43:40 -0400 (EDT) Received: from jhbbsd.localnet (smtp.hudson-trading.com [209.249.190.9]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 675F88A03C; Mon, 21 Jun 2010 11:43:39 -0400 (EDT) From: John Baldwin To: freebsd-amd64@freebsd.org Date: Mon, 21 Jun 2010 08:05:09 -0400 User-Agent: KMail/1.12.1 (FreeBSD/7.3-CBSD-20100217; KDE/4.3.1; amd64; ; ) References: <201006181022.o5IAMWa0074956@www.freebsd.org> In-Reply-To: <201006181022.o5IAMWa0074956@www.freebsd.org> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201006210805.09991.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (bigwig.baldwin.cx); Mon, 21 Jun 2010 11:43:39 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.95.1 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.5 required=4.2 tests=AWL,BAYES_00, DATE_IN_PAST_03_06 autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on bigwig.baldwin.cx Cc: Gabor Illo , freebsd-gnats-submit@freebsd.org Subject: Re: amd64/147963: cpu l2 cache error X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Jun 2010 15:43:41 -0000 On Friday 18 June 2010 6:22:32 am Gabor Illo wrote: > > >Number: 147963 > >Category: amd64 > >Synopsis: cpu l2 cache error > >Confidential: no > >Severity: serious > >Priority: medium > >Responsible: freebsd-amd64 > >State: open > >Quarter: > >Keywords: > >Date-Required: > >Class: sw-bug > >Submitter-Id: current-users > >Arrival-Date: Fri Jun 18 10:30:02 UTC 2010 > >Closed-Date: > >Last-Modified: > >Originator: Gabor Illo > >Release: 8.1-PRERELEASE > >Organization: > - > >Environment: > FreeBSD ns1.stageline.hu 8.1-PRERELEASE FreeBSD 8.1-PRERELEASE #1: Fri Jun 4 11:47:01 CEST 2010 stageline@ns1.stageline.hu:/usr/obj/usr/src/sys/SAJAT > >Description: > cpu0 (BSP): APIC ID: 0 > cpu1 (AP): APIC ID: 1 > cpu2 (AP): APIC ID: 2 > cpu3 (AP): APIC ID: 3 > cpu0: on acpi0 > cpu1: on acpi0 > cpu2: on acpi0 > cpu3: on acpi0 > est0: on cpu0 > p4tcc0: on cpu0 > est1: on cpu1 > est: cpu_vendor GenuineIntel, msr 928092806000928 > p4tcc1: on cpu1 > est2: on cpu2 > est: cpu_vendor GenuineIntel, msr 928092806000928 > p4tcc2: on cpu2 > est3: on cpu3 > est: cpu_vendor GenuineIntel, msr 928092806000928 > p4tcc3: on cpu3 > cpu0 (BSP): APIC ID: 0 > cpu1 (AP): APIC ID: 1 > cpu2 (AP): APIC ID: 2 > cpu3 (AP): APIC ID: 3 > cpu0: on acpi0 > cpu1: on acpi0 > cpu2: on acpi0 > cpu3: on acpi0 > est0: on cpu0 > p4tcc0: on cpu0 > est1: on cpu1 > est: cpu_vendor GenuineIntel, msr 928092806000928 > p4tcc1: on cpu1 > est2: on cpu2 > est: cpu_vendor GenuineIntel, msr 928092806000928 > p4tcc2: on cpu2 > est3: on cpu3 > est: cpu_vendor GenuineIntel, msr 928092806000928 > p4tcc3: on cpu3 > cpu0 (BSP): APIC ID: 0 > cpu1 (AP/HT): APIC ID: 1 > cpu2 (AP/HT): APIC ID: 2 > cpu3 (AP/HT): APIC ID: 3 > cpu0: on acpi0 > cpu1: on acpi0 > cpu2: on acpi0 > cpu3: on acpi0 > est0: on cpu0 > p4tcc0: on cpu0 > est1: on cpu1 > est: cpu_vendor GenuineIntel, msr 928092806000928 > p4tcc1: on cpu1 > est2: on cpu2 > est: cpu_vendor GenuineIntel, msr 928092806000928 > p4tcc2: on cpu2 > est3: on cpu3 > est: cpu_vendor GenuineIntel, msr 928092806000928 > p4tcc3: on cpu3 > > > > MCA: Bank 3, Status 0x942000842801010a > MCA: Global Cap 0x0000000000000806, Status 0x0000000000000000 > MCA: Vendor "GenuineIntel", ID 0x6f7, APIC ID 0 > MCA: CPU 0 COR (2) GCACHE L2 ERR error > MCA: Address 0x42de00 > MCA: Bank 3, Status 0x902000442920100e > MCA: Global Cap 0x0000000000000806, Status 0x0000000000000000 > MCA: Vendor "GenuineIntel", ID 0x6f7, APIC ID 0 > MCA: CPU 0 COR (1) L2 memory error > MCA: Bank 3, Status 0x902000442a20100e > MCA: Global Cap 0x0000000000000806, Status 0x0000000000000000 > MCA: Vendor "GenuineIntel", ID 0x6f7, APIC ID 0 > MCA: CPU 0 COR (1) L2 memory error > MCA: Bank 3, Status 0x942000c42b01010a > MCA: Global Cap 0x0000000000000806, Status 0x0000000000000000 > MCA: Vendor "GenuineIntel", ID 0x6f7, APIC ID 0 > MCA: CPU 0 COR (3) GCACHE L2 ERR error > MCA: Address 0x22aad300 > MCA: Bank 3, Status 0x902000c42c20100e > MCA: Global Cap 0x0000000000000806, Status 0x0000000000000000 > MCA: Vendor "GenuineIntel", ID 0x6f7, APIC ID 0 > MCA: CPU 0 COR (3) L2 memory error > MCA: Bank 3, Status 0x902000842d20100e > MCA: Global Cap 0x0000000000000806, Status 0x0000000000000000 > MCA: Vendor "GenuineIntel", ID 0x6f7, APIC ID 0 > MCA: CPU 0 COR (2) L2 memory error You are probably getting correctable memory errors. You can get spurious single-bit errors in modern systems. If you get any uncorrectable errors or a high rate (10's of thousands per hour) of correctable errors, then your RAM may be failing. -- John Baldwin From owner-freebsd-amd64@FreeBSD.ORG Mon Jun 21 15:43:42 2010 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 31FE7106564A; Mon, 21 Jun 2010 15:43:42 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 03EF38FC1A; Mon, 21 Jun 2010 15:43:42 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id ABD0546B4C; Mon, 21 Jun 2010 11:43:41 -0400 (EDT) Received: from jhbbsd.localnet (smtp.hudson-trading.com [209.249.190.9]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 960A48A04E; Mon, 21 Jun 2010 11:43:40 -0400 (EDT) From: John Baldwin To: freebsd-amd64@freebsd.org Date: Mon, 21 Jun 2010 08:06:14 -0400 User-Agent: KMail/1.12.1 (FreeBSD/7.3-CBSD-20100217; KDE/4.3.1; amd64; ; ) References: <201006192345.o5JNjOpl023426@www.freebsd.org> In-Reply-To: <201006192345.o5JNjOpl023426@www.freebsd.org> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201006210806.14225.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (bigwig.baldwin.cx); Mon, 21 Jun 2010 11:43:40 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.95.1 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.5 required=4.2 tests=AWL,BAYES_00, DATE_IN_PAST_03_06 autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on bigwig.baldwin.cx Cc: freebsd-gnats-submit@freebsd.org, Mike Subject: Re: amd64/148002: panic / page fault while booting from install dvd on asrock 939-dual sata X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Jun 2010 15:43:42 -0000 On Saturday 19 June 2010 7:45:24 pm Mike wrote: > > >Number: 148002 > >Category: amd64 > >Synopsis: panic / page fault while booting from install dvd on asrock 939-dual sata > >Confidential: no > >Severity: serious > >Priority: medium > >Responsible: freebsd-amd64 > >State: open > >Quarter: > >Keywords: > >Date-Required: > >Class: sw-bug > >Submitter-Id: current-users > >Arrival-Date: Sat Jun 19 23:50:01 UTC 2010 > >Closed-Date: > >Last-Modified: > >Originator: Mike > >Release: 8.0-Release > >Organization: > >Environment: > unable to do, machine doesn't boot > >Description: > I downloaded the dvd from one of the ftp mirrors, burned it and tried to boot from it. Right after harddisk detection the kernel panics like this: > > fatal trap 12: page fault while in kernel mode > cpuid = 0; apic id = 00 > fault = virtual address = 0x0 > fault code = supervisor read, page not present > instruction pointer = 0x20:0x0 > stack pointer = 0x28:0xe5b64b68 > frame pointer = 0x28:0xe5b64b9c > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor iflags = interrupt enabled, resume, IOPL = 0 > current process = 4 (g_down) > trap number = 12 > panic: page fault > cpuid = 0 > Uptime: 2s > > Hardware: > Mainboard: ASRock 939Dual-SATA2 > CPU: AMD Athlon 64 (2GHz) > RAM: 2GBytes DDR400 > Video Card: nVida Gefroce 7300GS > HDD: 2 Sata150 Disks, connected to the SATA connectors on the board. SATA2 is disabled. > > Tried to deactivate ACPI, set kern.smp.disabled from loaderprompt, both didn't help. > Tried to boot i386 dvd instead of i386-64: didn't work either with the same panic. > Tried FreeBSD 7.2/i386: booted cleanly, was able to install. > > >How-To-Repeat: > Get this very hardware, try to boot with FreeBSD 8.0 => crash > >Fix: Can you install 7.2, then build an 8.0 kernel with DDB enabled and get a stack trace of the crash? -- John Baldwin From owner-freebsd-amd64@FreeBSD.ORG Mon Jun 21 15:43:52 2010 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 12B141065672; Mon, 21 Jun 2010 15:43:52 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id D9C8C8FC14; Mon, 21 Jun 2010 15:43:51 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id 8D2D846B5C; Mon, 21 Jun 2010 11:43:51 -0400 (EDT) Received: from jhbbsd.localnet (smtp.hudson-trading.com [209.249.190.9]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id A1DC68A04F; Mon, 21 Jun 2010 11:43:50 -0400 (EDT) From: John Baldwin To: Andriy Gapon Date: Mon, 21 Jun 2010 11:43:26 -0400 User-Agent: KMail/1.12.1 (FreeBSD/7.3-CBSD-20100217; KDE/4.3.1; amd64; ; ) References: <4C1F798C.7010204@freebsd.org> In-Reply-To: <4C1F798C.7010204@freebsd.org> MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: 7bit Message-Id: <201006211143.26459.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (bigwig.baldwin.cx); Mon, 21 Jun 2010 11:43:50 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.95.1 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.5 required=4.2 tests=AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on bigwig.baldwin.cx Cc: freebsd-hackers@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: amd64 kernel modules: mapping sections to addresses X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Jun 2010 15:43:52 -0000 On Monday 21 June 2010 10:39:08 am Andriy Gapon wrote: > > I've noticed that on amd64 addresses (sh_addr) of all sections in a kernel module > are zeros. > This is unlike kernel itself and i386 modules. > > Kernel linker maps SHT_PROGBITS and SHT_NOBITS sections sequentially starting at a > certain base address and taking into account their sizes and alignment requirements. > > On the other hand, kgdb calculates section address as module base address plus > sh_addr of the section. Which puts all sections, e.g. .text, .data, .bss, at the > same address. This is correct only for .text which is normally the first section > described in a header. > > DTrace situation is even worse, because don't even take into account module base > address, not speaking of section relative addresses. > > Perhaps we should put some sh_addr values into amd64 kernel modules that would > match calculations done in link_elf_load_file. > Or should we replicate logic from link_elf_load_file in all places that need to > map loaded module's sections to load addresses? > > What do you think? > Thanks! > > P.S. > As I understand CTF data includes a symbol table. > What kind of symbol addresses is used there? Are they relative within a > corresponding section? Or something else? np@ has a patch to gdb to fix this for kgdb. I haven't committed it as it patched gdb internals and wasn't in a kgdb-specific place, but I'm not sure of a better way to fix kgdb. -- John Baldwin From owner-freebsd-amd64@FreeBSD.ORG Mon Jun 21 15:50:04 2010 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 68FE8106566B for ; Mon, 21 Jun 2010 15:50:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 3F9D98FC29 for ; Mon, 21 Jun 2010 15:50:04 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o5LFo4VB043367 for ; Mon, 21 Jun 2010 15:50:04 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o5LFo40Q043366; Mon, 21 Jun 2010 15:50:04 GMT (envelope-from gnats) Date: Mon, 21 Jun 2010 15:50:04 GMT Message-Id: <201006211550.o5LFo40Q043366@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: John Baldwin Cc: Subject: Re: amd64/147963: cpu l2 cache error X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: John Baldwin List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Jun 2010 15:50:04 -0000 The following reply was made to PR amd64/147963; it has been noted by GNATS. From: John Baldwin To: freebsd-amd64@freebsd.org Cc: Gabor Illo , freebsd-gnats-submit@freebsd.org Subject: Re: amd64/147963: cpu l2 cache error Date: Mon, 21 Jun 2010 08:05:09 -0400 On Friday 18 June 2010 6:22:32 am Gabor Illo wrote: > > >Number: 147963 > >Category: amd64 > >Synopsis: cpu l2 cache error > >Confidential: no > >Severity: serious > >Priority: medium > >Responsible: freebsd-amd64 > >State: open > >Quarter: > >Keywords: > >Date-Required: > >Class: sw-bug > >Submitter-Id: current-users > >Arrival-Date: Fri Jun 18 10:30:02 UTC 2010 > >Closed-Date: > >Last-Modified: > >Originator: Gabor Illo > >Release: 8.1-PRERELEASE > >Organization: > - > >Environment: > FreeBSD ns1.stageline.hu 8.1-PRERELEASE FreeBSD 8.1-PRERELEASE #1: Fri Jun 4 11:47:01 CEST 2010 stageline@ns1.stageline.hu:/usr/obj/usr/src/sys/SAJAT > >Description: > cpu0 (BSP): APIC ID: 0 > cpu1 (AP): APIC ID: 1 > cpu2 (AP): APIC ID: 2 > cpu3 (AP): APIC ID: 3 > cpu0: on acpi0 > cpu1: on acpi0 > cpu2: on acpi0 > cpu3: on acpi0 > est0: on cpu0 > p4tcc0: on cpu0 > est1: on cpu1 > est: cpu_vendor GenuineIntel, msr 928092806000928 > p4tcc1: on cpu1 > est2: on cpu2 > est: cpu_vendor GenuineIntel, msr 928092806000928 > p4tcc2: on cpu2 > est3: on cpu3 > est: cpu_vendor GenuineIntel, msr 928092806000928 > p4tcc3: on cpu3 > cpu0 (BSP): APIC ID: 0 > cpu1 (AP): APIC ID: 1 > cpu2 (AP): APIC ID: 2 > cpu3 (AP): APIC ID: 3 > cpu0: on acpi0 > cpu1: on acpi0 > cpu2: on acpi0 > cpu3: on acpi0 > est0: on cpu0 > p4tcc0: on cpu0 > est1: on cpu1 > est: cpu_vendor GenuineIntel, msr 928092806000928 > p4tcc1: on cpu1 > est2: on cpu2 > est: cpu_vendor GenuineIntel, msr 928092806000928 > p4tcc2: on cpu2 > est3: on cpu3 > est: cpu_vendor GenuineIntel, msr 928092806000928 > p4tcc3: on cpu3 > cpu0 (BSP): APIC ID: 0 > cpu1 (AP/HT): APIC ID: 1 > cpu2 (AP/HT): APIC ID: 2 > cpu3 (AP/HT): APIC ID: 3 > cpu0: on acpi0 > cpu1: on acpi0 > cpu2: on acpi0 > cpu3: on acpi0 > est0: on cpu0 > p4tcc0: on cpu0 > est1: on cpu1 > est: cpu_vendor GenuineIntel, msr 928092806000928 > p4tcc1: on cpu1 > est2: on cpu2 > est: cpu_vendor GenuineIntel, msr 928092806000928 > p4tcc2: on cpu2 > est3: on cpu3 > est: cpu_vendor GenuineIntel, msr 928092806000928 > p4tcc3: on cpu3 > > > > MCA: Bank 3, Status 0x942000842801010a > MCA: Global Cap 0x0000000000000806, Status 0x0000000000000000 > MCA: Vendor "GenuineIntel", ID 0x6f7, APIC ID 0 > MCA: CPU 0 COR (2) GCACHE L2 ERR error > MCA: Address 0x42de00 > MCA: Bank 3, Status 0x902000442920100e > MCA: Global Cap 0x0000000000000806, Status 0x0000000000000000 > MCA: Vendor "GenuineIntel", ID 0x6f7, APIC ID 0 > MCA: CPU 0 COR (1) L2 memory error > MCA: Bank 3, Status 0x902000442a20100e > MCA: Global Cap 0x0000000000000806, Status 0x0000000000000000 > MCA: Vendor "GenuineIntel", ID 0x6f7, APIC ID 0 > MCA: CPU 0 COR (1) L2 memory error > MCA: Bank 3, Status 0x942000c42b01010a > MCA: Global Cap 0x0000000000000806, Status 0x0000000000000000 > MCA: Vendor "GenuineIntel", ID 0x6f7, APIC ID 0 > MCA: CPU 0 COR (3) GCACHE L2 ERR error > MCA: Address 0x22aad300 > MCA: Bank 3, Status 0x902000c42c20100e > MCA: Global Cap 0x0000000000000806, Status 0x0000000000000000 > MCA: Vendor "GenuineIntel", ID 0x6f7, APIC ID 0 > MCA: CPU 0 COR (3) L2 memory error > MCA: Bank 3, Status 0x902000842d20100e > MCA: Global Cap 0x0000000000000806, Status 0x0000000000000000 > MCA: Vendor "GenuineIntel", ID 0x6f7, APIC ID 0 > MCA: CPU 0 COR (2) L2 memory error You are probably getting correctable memory errors. You can get spurious single-bit errors in modern systems. If you get any uncorrectable errors or a high rate (10's of thousands per hour) of correctable errors, then your RAM may be failing. -- John Baldwin From owner-freebsd-amd64@FreeBSD.ORG Mon Jun 21 15:50:07 2010 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3B4AB106564A for ; Mon, 21 Jun 2010 15:50:07 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 10AB28FC1F for ; Mon, 21 Jun 2010 15:50:07 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o5LFo6bG043409 for ; Mon, 21 Jun 2010 15:50:06 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o5LFo6qJ043404; Mon, 21 Jun 2010 15:50:06 GMT (envelope-from gnats) Date: Mon, 21 Jun 2010 15:50:06 GMT Message-Id: <201006211550.o5LFo6qJ043404@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: John Baldwin Cc: Subject: Re: amd64/148002: panic / page fault while booting from install dvd on asrock 939-dual sata X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: John Baldwin List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Jun 2010 15:50:07 -0000 The following reply was made to PR amd64/148002; it has been noted by GNATS. From: John Baldwin To: freebsd-amd64@freebsd.org Cc: Mike , freebsd-gnats-submit@freebsd.org Subject: Re: amd64/148002: panic / page fault while booting from install dvd on asrock 939-dual sata Date: Mon, 21 Jun 2010 08:06:14 -0400 On Saturday 19 June 2010 7:45:24 pm Mike wrote: > > >Number: 148002 > >Category: amd64 > >Synopsis: panic / page fault while booting from install dvd on asrock 939-dual sata > >Confidential: no > >Severity: serious > >Priority: medium > >Responsible: freebsd-amd64 > >State: open > >Quarter: > >Keywords: > >Date-Required: > >Class: sw-bug > >Submitter-Id: current-users > >Arrival-Date: Sat Jun 19 23:50:01 UTC 2010 > >Closed-Date: > >Last-Modified: > >Originator: Mike > >Release: 8.0-Release > >Organization: > >Environment: > unable to do, machine doesn't boot > >Description: > I downloaded the dvd from one of the ftp mirrors, burned it and tried to boot from it. Right after harddisk detection the kernel panics like this: > > fatal trap 12: page fault while in kernel mode > cpuid = 0; apic id = 00 > fault = virtual address = 0x0 > fault code = supervisor read, page not present > instruction pointer = 0x20:0x0 > stack pointer = 0x28:0xe5b64b68 > frame pointer = 0x28:0xe5b64b9c > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor iflags = interrupt enabled, resume, IOPL = 0 > current process = 4 (g_down) > trap number = 12 > panic: page fault > cpuid = 0 > Uptime: 2s > > Hardware: > Mainboard: ASRock 939Dual-SATA2 > CPU: AMD Athlon 64 (2GHz) > RAM: 2GBytes DDR400 > Video Card: nVida Gefroce 7300GS > HDD: 2 Sata150 Disks, connected to the SATA connectors on the board. SATA2 is disabled. > > Tried to deactivate ACPI, set kern.smp.disabled from loaderprompt, both didn't help. > Tried to boot i386 dvd instead of i386-64: didn't work either with the same panic. > Tried FreeBSD 7.2/i386: booted cleanly, was able to install. > > >How-To-Repeat: > Get this very hardware, try to boot with FreeBSD 8.0 => crash > >Fix: Can you install 7.2, then build an 8.0 kernel with DDB enabled and get a stack trace of the crash? -- John Baldwin From owner-freebsd-amd64@FreeBSD.ORG Mon Jun 21 14:39:12 2010 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9AAFA106564A; Mon, 21 Jun 2010 14:39:12 +0000 (UTC) (envelope-from avg@freebsd.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 442D28FC0A; Mon, 21 Jun 2010 14:39:10 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id RAA23978; Mon, 21 Jun 2010 17:39:09 +0300 (EEST) (envelope-from avg@freebsd.org) Message-ID: <4C1F798C.7010204@freebsd.org> Date: Mon, 21 Jun 2010 17:39:08 +0300 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.24 (X11/20100517) MIME-Version: 1.0 To: freebsd-hackers@freebsd.org, freebsd-amd64@freebsd.org X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Mon, 21 Jun 2010 16:26:33 +0000 Cc: Subject: amd64 kernel modules: mapping sections to addresses X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Jun 2010 14:39:12 -0000 I've noticed that on amd64 addresses (sh_addr) of all sections in a kernel module are zeros. This is unlike kernel itself and i386 modules. Kernel linker maps SHT_PROGBITS and SHT_NOBITS sections sequentially starting at a certain base address and taking into account their sizes and alignment requirements. On the other hand, kgdb calculates section address as module base address plus sh_addr of the section. Which puts all sections, e.g. .text, .data, .bss, at the same address. This is correct only for .text which is normally the first section described in a header. DTrace situation is even worse, because don't even take into account module base address, not speaking of section relative addresses. Perhaps we should put some sh_addr values into amd64 kernel modules that would match calculations done in link_elf_load_file. Or should we replicate logic from link_elf_load_file in all places that need to map loaded module's sections to load addresses? What do you think? Thanks! P.S. As I understand CTF data includes a symbol table. What kind of symbol addresses is used there? Are they relative within a corresponding section? Or something else? -- Andriy Gapon From owner-freebsd-amd64@FreeBSD.ORG Mon Jun 21 15:57:20 2010 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9BB25106564A; Mon, 21 Jun 2010 15:57:20 +0000 (UTC) (envelope-from avg@freebsd.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 44D5E8FC0A; Mon, 21 Jun 2010 15:57:18 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id SAA25914; Mon, 21 Jun 2010 18:57:17 +0300 (EEST) (envelope-from avg@freebsd.org) Message-ID: <4C1F8BDD.9010408@freebsd.org> Date: Mon, 21 Jun 2010 18:57:17 +0300 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.24 (X11/20100517) MIME-Version: 1.0 To: John Baldwin , Navdeep Parhar References: <4C1F798C.7010204@freebsd.org> <201006211143.26459.jhb@freebsd.org> In-Reply-To: <201006211143.26459.jhb@freebsd.org> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Mon, 21 Jun 2010 16:38:41 +0000 Cc: freebsd-hackers@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: amd64 kernel modules: mapping sections to addresses X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Jun 2010 15:57:20 -0000 on 21/06/2010 18:43 John Baldwin said the following: > np@ has a patch to gdb to fix this for kgdb. I haven't committed it as it > patched gdb internals and wasn't in a kgdb-specific place, but I'm not sure of > a better way to fix kgdb. Oh, yes, section mapping is done in common gdb code. Perhaps kld.c shouldn't call build_section_table, but directly call bfd_map_over_sections with a custom variant of add_to_section_table? Can you please share the patch? Still, what about a small tool, elf(3)-base porgram or objdump+objcopy shell script, that would set section addresses in amd64 .ko (relocatable object file) similarly to how they are set in i386 .ko (full-blown DSO)? Or is this too much useless hassle? -- Andriy Gapon From owner-freebsd-amd64@FreeBSD.ORG Mon Jun 21 20:15:53 2010 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BBD30106564A; Mon, 21 Jun 2010 20:15:53 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 8B4C78FC12; Mon, 21 Jun 2010 20:15:53 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id 3FA7A46B5B; Mon, 21 Jun 2010 16:15:53 -0400 (EDT) Received: from jhbbsd.localnet (smtp.hudson-trading.com [209.249.190.9]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id A69AA8A03C; Mon, 21 Jun 2010 16:15:52 -0400 (EDT) From: John Baldwin To: Andriy Gapon Date: Mon, 21 Jun 2010 16:10:45 -0400 User-Agent: KMail/1.12.1 (FreeBSD/7.3-CBSD-20100217; KDE/4.3.1; amd64; ; ) References: <4C1F798C.7010204@freebsd.org> <201006211143.26459.jhb@freebsd.org> <4C1F8BDD.9010408@freebsd.org> In-Reply-To: <4C1F8BDD.9010408@freebsd.org> MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: 7bit Message-Id: <201006211610.45811.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (bigwig.baldwin.cx); Mon, 21 Jun 2010 16:15:52 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.95.1 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.5 required=4.2 tests=AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on bigwig.baldwin.cx Cc: freebsd-hackers@freebsd.org, Navdeep Parhar , freebsd-amd64@freebsd.org Subject: Re: amd64 kernel modules: mapping sections to addresses X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Jun 2010 20:15:53 -0000 On Monday 21 June 2010 11:57:17 am Andriy Gapon wrote: > on 21/06/2010 18:43 John Baldwin said the following: > > np@ has a patch to gdb to fix this for kgdb. I haven't committed it as it > > patched gdb internals and wasn't in a kgdb-specific place, but I'm not sure of > > a better way to fix kgdb. > > Oh, yes, section mapping is done in common gdb code. > Perhaps kld.c shouldn't call build_section_table, but directly call > bfd_map_over_sections with a custom variant of add_to_section_table? > Can you please share the patch? It was deeper level than that, I'd have to dig it up. > Still, what about a small tool, elf(3)-base porgram or objdump+objcopy shell > script, that would set section addresses in amd64 .ko (relocatable object file) > similarly to how they are set in i386 .ko (full-blown DSO)? > Or is this too much useless hassle? No idea. If this worked and just let gdb work automatically that would be a nice fix to just put into the build process. -- John Baldwin From owner-freebsd-amd64@FreeBSD.ORG Mon Jun 21 20:44:35 2010 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 1205) id 2620C106566C; Mon, 21 Jun 2010 20:44:35 +0000 (UTC) Date: Mon, 21 Jun 2010 20:44:35 +0000 From: Navdeep Parhar To: John Baldwin Message-ID: <20100621204435.GA98177@hub.freebsd.org> Mail-Followup-To: John Baldwin , Andriy Gapon , freebsd-hackers@freebsd.org, freebsd-amd64@freebsd.org References: <4C1F798C.7010204@freebsd.org> <201006211143.26459.jhb@freebsd.org> <4C1F8BDD.9010408@freebsd.org> <201006211610.45811.jhb@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201006211610.45811.jhb@freebsd.org> User-Agent: Mutt/1.4.2.1i X-Mailman-Approved-At: Mon, 21 Jun 2010 20:53:09 +0000 Cc: freebsd-hackers@freebsd.org, freebsd-amd64@freebsd.org, Andriy Gapon Subject: Re: amd64 kernel modules: mapping sections to addresses X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Jun 2010 20:44:35 -0000 On Mon, Jun 21, 2010 at 04:10:45PM -0400, John Baldwin wrote: > On Monday 21 June 2010 11:57:17 am Andriy Gapon wrote: > > on 21/06/2010 18:43 John Baldwin said the following: > > > np@ has a patch to gdb to fix this for kgdb. I haven't committed it as it > > > patched gdb internals and wasn't in a kgdb-specific place, but I'm not > sure of > > > a better way to fix kgdb. > > > > Oh, yes, section mapping is done in common gdb code. > > Perhaps kld.c shouldn't call build_section_table, but directly call > > bfd_map_over_sections with a custom variant of add_to_section_table? > > Can you please share the patch? > > It was deeper level than that, I'd have to dig it up. I'm using this patch these days: http://people.freebsd.org/~np/kgdb+kld+amd64.diff The changes to the kernel linker were not required originally. See this for why they had to be made: http://lists.freebsd.org/pipermail/freebsd-hackers/2009-November/030093.html The patch is quite crude and I have no idea how it behaves on other platforms. Regards, Navdeep > > > Still, what about a small tool, elf(3)-base porgram or objdump+objcopy shell > > script, that would set section addresses in amd64 .ko (relocatable object > file) > > similarly to how they are set in i386 .ko (full-blown DSO)? > > Or is this too much useless hassle? > > No idea. If this worked and just let gdb work automatically that would be a > nice fix to just put into the build process. > > -- > John Baldwin From owner-freebsd-amd64@FreeBSD.ORG Mon Jun 21 21:34:54 2010 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4AD9D106564A; Mon, 21 Jun 2010 21:34:54 +0000 (UTC) (envelope-from avg@freebsd.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id D314A8FC15; Mon, 21 Jun 2010 21:34:52 +0000 (UTC) Received: from porto.topspin.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id AAA02380; Tue, 22 Jun 2010 00:34:51 +0300 (EEST) (envelope-from avg@freebsd.org) Received: from localhost.topspin.kiev.ua ([127.0.0.1]) by porto.topspin.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1OQodn-000Mvh-3K; Tue, 22 Jun 2010 00:34:51 +0300 Message-ID: <4C1FDAF9.3080808@freebsd.org> Date: Tue, 22 Jun 2010 00:34:49 +0300 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.24 (X11/20100603) MIME-Version: 1.0 To: Navdeep Parhar , freebsd-hackers@freebsd.org, freebsd-amd64@freebsd.org References: <4C1F798C.7010204@freebsd.org> <201006211143.26459.jhb@freebsd.org> <4C1F8BDD.9010408@freebsd.org> <201006211610.45811.jhb@freebsd.org> <20100621204435.GA98177@hub.freebsd.org> In-Reply-To: <20100621204435.GA98177@hub.freebsd.org> X-Enigmail-Version: 0.96.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Mon, 21 Jun 2010 21:42:45 +0000 Cc: Subject: Re: amd64 kernel modules: mapping sections to addresses X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Jun 2010 21:34:54 -0000 on 21/06/2010 23:44 Navdeep Parhar said the following: > On Mon, Jun 21, 2010 at 04:10:45PM -0400, John Baldwin wrote: >> On Monday 21 June 2010 11:57:17 am Andriy Gapon wrote: >>> on 21/06/2010 18:43 John Baldwin said the following: >>>> np@ has a patch to gdb to fix this for kgdb. I haven't committed it as it >>>> patched gdb internals and wasn't in a kgdb-specific place, but I'm not >> sure of >>>> a better way to fix kgdb. >>> Oh, yes, section mapping is done in common gdb code. >>> Perhaps kld.c shouldn't call build_section_table, but directly call >>> bfd_map_over_sections with a custom variant of add_to_section_table? >>> Can you please share the patch? >> It was deeper level than that, I'd have to dig it up. > > I'm using this patch these days: > http://people.freebsd.org/~np/kgdb+kld+amd64.diff > > The changes to the kernel linker were not required originally. See this > for why they had to be made: > http://lists.freebsd.org/pipermail/freebsd-hackers/2009-November/030093.html > > The patch is quite crude and I have no idea how it behaves on other > platforms. Thanks a lot! These are exact issues that I hit and the patches are what I think they should be, take or give. I don't think they are really crude. I will try to get them committed. Kernel linker change is good as is, I'd just like to move the zero size check before the switch statement. gdb change - I'd rather do it via kld_current_sos, kld_relocate_section_addresses. I'd like to avoid changing common gdb code for a variety of reasons. -- Andriy Gapon From owner-freebsd-amd64@FreeBSD.ORG Mon Jun 21 22:20:24 2010 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7FC0F1065670; Mon, 21 Jun 2010 22:20:24 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 569B88FC12; Mon, 21 Jun 2010 22:20:24 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o5LMKOxY079584; Mon, 21 Jun 2010 22:20:24 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o5LMKNsw079508; Mon, 21 Jun 2010 22:20:23 GMT (envelope-from linimon) Date: Mon, 21 Jun 2010 22:20:23 GMT Message-Id: <201006212220.o5LMKNsw079508@freefall.freebsd.org> To: dura-zell@freenet.de, linimon@FreeBSD.org, freebsd-amd64@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: amd64/148002: [boot] panic / page fault while booting from install dvd on asrock 939-dual sata X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Jun 2010 22:20:24 -0000 Synopsis: [boot] panic / page fault while booting from install dvd on asrock 939-dual sata State-Changed-From-To: open->feedback State-Changed-By: linimon State-Changed-When: Mon Jun 21 22:20:11 UTC 2010 State-Changed-Why: Note that feedback was requested. http://www.freebsd.org/cgi/query-pr.cgi?pr=148002 From owner-freebsd-amd64@FreeBSD.ORG Mon Jun 21 22:00:35 2010 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 1205) id 859DD1065670; Mon, 21 Jun 2010 22:00:35 +0000 (UTC) Date: Mon, 21 Jun 2010 22:00:35 +0000 From: Navdeep Parhar To: Andriy Gapon Message-ID: <20100621220035.GA8746@hub.freebsd.org> Mail-Followup-To: Andriy Gapon , freebsd-hackers@freebsd.org, freebsd-amd64@freebsd.org, John Baldwin References: <4C1F798C.7010204@freebsd.org> <201006211143.26459.jhb@freebsd.org> <4C1F8BDD.9010408@freebsd.org> <201006211610.45811.jhb@freebsd.org> <20100621204435.GA98177@hub.freebsd.org> <4C1FDAF9.3080808@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4C1FDAF9.3080808@freebsd.org> User-Agent: Mutt/1.4.2.1i X-Mailman-Approved-At: Mon, 21 Jun 2010 22:50:36 +0000 Cc: freebsd-hackers@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: amd64 kernel modules: mapping sections to addresses X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Jun 2010 22:00:35 -0000 On Tue, Jun 22, 2010 at 12:34:49AM +0300, Andriy Gapon wrote: > on 21/06/2010 23:44 Navdeep Parhar said the following: > > On Mon, Jun 21, 2010 at 04:10:45PM -0400, John Baldwin wrote: > >> On Monday 21 June 2010 11:57:17 am Andriy Gapon wrote: > >>> on 21/06/2010 18:43 John Baldwin said the following: > >>>> np@ has a patch to gdb to fix this for kgdb. I haven't committed it as it > >>>> patched gdb internals and wasn't in a kgdb-specific place, but I'm not > >> sure of > >>>> a better way to fix kgdb. > >>> Oh, yes, section mapping is done in common gdb code. > >>> Perhaps kld.c shouldn't call build_section_table, but directly call > >>> bfd_map_over_sections with a custom variant of add_to_section_table? > >>> Can you please share the patch? > >> It was deeper level than that, I'd have to dig it up. > > > > I'm using this patch these days: > > http://people.freebsd.org/~np/kgdb+kld+amd64.diff > > > > The changes to the kernel linker were not required originally. See this > > for why they had to be made: > > http://lists.freebsd.org/pipermail/freebsd-hackers/2009-November/030093.html > > > > The patch is quite crude and I have no idea how it behaves on other > > platforms. > > Thanks a lot! These are exact issues that I hit and the patches are what I > think they should be, take or give. I don't think they are really crude. > I will try to get them committed. > > Kernel linker change is good as is, I'd just like to move the zero size check > before the switch statement. I'm not so sure about this. There is code inside the second switch that runs whether sh_size is 0 or not. Either all of it is pointless code (when sh_size is 0) or or you'll make sure that it still runs, right? Regards, Navdeep > > gdb change - I'd rather do it via kld_current_sos, > kld_relocate_section_addresses. I'd like to avoid changing common gdb code for > a variety of reasons. > > -- > Andriy Gapon From owner-freebsd-amd64@FreeBSD.ORG Mon Jun 21 22:17:18 2010 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 38E191065670; Mon, 21 Jun 2010 22:17:18 +0000 (UTC) (envelope-from avg@freebsd.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id D3F6D8FC15; Mon, 21 Jun 2010 22:17:16 +0000 (UTC) Received: from porto.topspin.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id BAA03191; Tue, 22 Jun 2010 01:17:15 +0300 (EEST) (envelope-from avg@freebsd.org) Received: from localhost.topspin.kiev.ua ([127.0.0.1]) by porto.topspin.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1OQpIp-000Mxu-0y; Tue, 22 Jun 2010 01:17:15 +0300 Message-ID: <4C1FE4E9.8080400@freebsd.org> Date: Tue, 22 Jun 2010 01:17:13 +0300 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.24 (X11/20100603) MIME-Version: 1.0 To: Navdeep Parhar , freebsd-hackers@freebsd.org, freebsd-amd64@freebsd.org References: <4C1F798C.7010204@freebsd.org> <201006211143.26459.jhb@freebsd.org> <4C1F8BDD.9010408@freebsd.org> <201006211610.45811.jhb@freebsd.org> <20100621204435.GA98177@hub.freebsd.org> <4C1FDAF9.3080808@freebsd.org> <20100621220035.GA8746@hub.freebsd.org> In-Reply-To: <20100621220035.GA8746@hub.freebsd.org> X-Enigmail-Version: 0.96.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Mon, 21 Jun 2010 23:06:58 +0000 Cc: Subject: Re: amd64 kernel modules: mapping sections to addresses X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Jun 2010 22:17:18 -0000 on 22/06/2010 01:00 Navdeep Parhar said the following: > > I'm not so sure about this. There is code inside the second switch that runs > whether sh_size is 0 or not. Either all of it is pointless code (when sh_size > is 0) or or you'll make sure that it still runs, right? It's definitely pointless. [IMHO :-)] -- Andriy Gapon From owner-freebsd-amd64@FreeBSD.ORG Tue Jun 22 09:21:32 2010 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4AE0E106566B; Tue, 22 Jun 2010 09:21:32 +0000 (UTC) (envelope-from avg@freebsd.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id C28E88FC16; Tue, 22 Jun 2010 09:21:29 +0000 (UTC) Received: from porto.topspin.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id MAA17232; Tue, 22 Jun 2010 12:21:28 +0300 (EEST) (envelope-from avg@freebsd.org) Received: from localhost.topspin.kiev.ua ([127.0.0.1]) by porto.topspin.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1OQzfc-000PcO-8F; Tue, 22 Jun 2010 12:21:28 +0300 Message-ID: <4C208096.3030602@freebsd.org> Date: Tue, 22 Jun 2010 12:21:26 +0300 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.24 (X11/20100603) MIME-Version: 1.0 To: Navdeep Parhar , John Baldwin References: <4C1F798C.7010204@freebsd.org> <201006211143.26459.jhb@freebsd.org> <4C1F8BDD.9010408@freebsd.org> <201006211610.45811.jhb@freebsd.org> <20100621204435.GA98177@hub.freebsd.org> <4C1FDAF9.3080808@freebsd.org> In-Reply-To: <4C1FDAF9.3080808@freebsd.org> X-Enigmail-Version: 0.96.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Tue, 22 Jun 2010 11:08:30 +0000 Cc: freebsd-hackers@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: amd64 kernel modules: mapping sections to addresses X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Jun 2010 09:21:32 -0000 on 22/06/2010 00:34 Andriy Gapon said the following: > gdb change - I'd rather do it via kld_current_sos, > kld_relocate_section_addresses. I'd like to avoid changing common gdb code for > a variety of reasons. I came up with the following patch. EXEC_P and DYNAMIC flags are bfd library equivalents of ET_EXEC and ET_DYN elf flags. Absence of both of these flags means ET_REL, which is a type of our amd64 kernel modules. The code all resides in kld.c and acts only kernel modules that are either auto-loaded via kld_current_sos or explicitly added with add-kld. I used a static variable in kld_relocate_section_addresses because that function is called on each section sequentially, so current offset can not be stored on stack. The offset is reset to module's load address when see that we are called with first section. Alternative is to glimpse at previous section's end address as you did. So the code depends on sections being passed in forward sequential order. How does this look? Could you please test it? diff --git a/gnu/usr.bin/gdb/kgdb/kld.c b/gnu/usr.bin/gdb/kgdb/kld.c index 716a67c..d5ba20a 100644 --- a/gnu/usr.bin/gdb/kgdb/kld.c +++ b/gnu/usr.bin/gdb/kgdb/kld.c @@ -198,12 +198,32 @@ find_kld_address (char *arg, CORE_ADDR *address) } static void +adjust_section_address (struct section_table *sec, CORE_ADDR *curr_base) +{ + struct bfd_section *asect = sec->the_bfd_section; + bfd *abfd = sec->bfd; + + if ((abfd->flags & (EXEC_P | DYNAMIC)) != 0) { + sec->addr += *curr_base; + sec->endaddr += *curr_base; + return; + } + + *curr_base = align_power(*curr_base, + bfd_get_section_alignment(abfd, asect)); + sec->addr = *curr_base; + sec->endaddr = sec->addr + bfd_section_size(abfd, asect); + *curr_base = sec->endaddr; +} + +static void load_kld (char *path, CORE_ADDR base_addr, int from_tty) { struct section_addr_info *sap; struct section_table *sections = NULL, *sections_end = NULL, *s; struct cleanup *cleanup; bfd *bfd; + CORE_ADDR curr_addr; int i; /* Open the kld. */ @@ -224,10 +244,9 @@ load_kld (char *path, CORE_ADDR base_addr, int from_tty) if (build_section_table (bfd, §ions, §ions_end)) error("\"%s\": can't find file sections", path); cleanup = make_cleanup(xfree, sections); - for (s = sections; s < sections_end; s++) { - s->addr += base_addr; - s->endaddr += base_addr; - } + curr_addr = base_addr; + for (s = sections; s < sections_end; s++) + adjust_section_address(s, &curr_addr); /* Build a section addr info to pass to symbol_file_add(). */ sap = build_section_addr_info_from_section_table (sections, @@ -284,9 +303,12 @@ kgdb_add_kld_cmd (char *arg, int from_tty) static void kld_relocate_section_addresses (struct so_list *so, struct section_table *sec) { + static CORE_ADDR curr_addr; + + if (sec == so->sections) + curr_addr = so->lm_info->base_address; - sec->addr += so->lm_info->base_address; - sec->endaddr += so->lm_info->base_address; + adjust_section_address(sec, &curr_addr); } static void -- Andriy Gapon From owner-freebsd-amd64@FreeBSD.ORG Tue Jun 22 16:12:15 2010 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 255A7106564A for ; Tue, 22 Jun 2010 16:12:15 +0000 (UTC) (envelope-from cfaber@gmail.com) Received: from mail-pv0-f182.google.com (mail-pv0-f182.google.com [74.125.83.182]) by mx1.freebsd.org (Postfix) with ESMTP id ED0C88FC0A for ; Tue, 22 Jun 2010 16:12:14 +0000 (UTC) Received: by pvg4 with SMTP id 4so507989pvg.13 for ; Tue, 22 Jun 2010 09:12:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:subject:content-type :content-transfer-encoding; bh=rESZhKK+evugJXhIy5g6gvbhqO32QT2nVxDCpaLVUjs=; b=rPjPbsAYs/gtUmecD/D7ZT41xFXygHUbVQ3e43aNQYlc5dwW5UYgFVmmprtj8Nhbxc O7TLKRjJWKmxh4mO+lNa4DFnWyTH7d3nQ8Y5Z3m3FNlqimTjXL4A1/xMlcrirVHlxtyk TQ/NJGpXvloePZpp9DoGOtIlSVjS3WzScSaj4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; b=s2MJY6SIzdmWflphcsz9bandmYhEDaWcqL0kuuFc3mCeXUE2ClDEDR+bmBmOy78g/y YUMRuFYMQvjHAUPZLOZqPTlp9Sf/IhZ+dZxQf53syxT3Rm7MlO2+wCuMRijQ4H04Ow9s da/dXPVZbTf+IDZg2d6vecd6qCb93BlUBGt4o= Received: by 10.142.10.27 with SMTP id 27mr5302434wfj.265.1277221255203; Tue, 22 Jun 2010 08:40:55 -0700 (PDT) Received: from [10.10.0.100] (c-71-229-204-48.hsd1.co.comcast.net [71.229.204.48]) by mx.google.com with ESMTPS id q10sm3447689rvp.20.2010.06.22.08.40.53 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 22 Jun 2010 08:40:54 -0700 (PDT) Message-ID: <4C20D984.70003@gmail.com> Date: Tue, 22 Jun 2010 09:40:52 -0600 From: Colin Faber User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.9) Gecko/20100423 Thunderbird/3.0.4 MIME-Version: 1.0 To: freebsd-amd64@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: strange network lockup with em0 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Jun 2010 16:12:15 -0000 Hi guys, I don't know if this message belongs here or elsewhere. So about every 15 to 18 days or so my em0 on amd64 7.3-STABLE machine just stops working. ifconfig indicates that em0 is still up, ip assigned, routing table good, just no traffic flows through that interface. Checking dmesg and system logs doesn't indicate anything wrong with the nic. I've experienced this issue with 7.2 forward. Does anyone happen to have any suggestions on what I should look at next? -cf From owner-freebsd-amd64@FreeBSD.ORG Tue Jun 22 20:09:44 2010 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 947021065670 for ; Tue, 22 Jun 2010 20:09:44 +0000 (UTC) (envelope-from cfaber@gmail.com) Received: from mail-gw0-f54.google.com (mail-gw0-f54.google.com [74.125.83.54]) by mx1.freebsd.org (Postfix) with ESMTP id 4E7C48FC1B for ; Tue, 22 Jun 2010 20:09:44 +0000 (UTC) Received: by gwb11 with SMTP id 11so245516gwb.13 for ; Tue, 22 Jun 2010 13:09:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:subject:content-type :content-transfer-encoding; bh=QXgQFTNZc27J1nE8CiWEL7YohwvxdvLIfw17j+//C7M=; b=fJPActG9QlIMWQVwC4lSCkIA/RTpgryu6slt6rFBPZRGt0Yu2iX/WIGFmMqclvUr1X NTE4lo46wMq7BtOUUT/jkfY6DaBYe7KnK73L4OPoc8MJViXehbyGfI58MAitUVGLZyis WjP+JomJDe6dys/Ynwl8FdKS8myPER/9evub0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; b=CYL0pz0G86YMb0v9d+ekZ2ulZ7GXzgSCPBfGTOTDaIZAUPze4JyIyJ88OaeK7V7Gqm uEtbZa4V2ggh3bnL3gYfF72utbXwWYYHrCMNTYCBqOsMe4YCBiYBoSeaHqTzYzcyYumE lNy/iq/x+wo4rOsbA9F8nU5i/RWzYqf6qATx4= Received: by 10.101.184.20 with SMTP id l20mr5547647anp.207.1277237383284; Tue, 22 Jun 2010 13:09:43 -0700 (PDT) Received: from [10.10.0.100] (c-71-229-204-48.hsd1.co.comcast.net [71.229.204.48]) by mx.google.com with ESMTPS id n18sm33632478anl.2.2010.06.22.13.09.41 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 22 Jun 2010 13:09:42 -0700 (PDT) Message-ID: <4C211884.8020007@gmail.com> Date: Tue, 22 Jun 2010 14:09:40 -0600 From: Colin Faber User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.9) Gecko/20100423 Thunderbird/3.0.4 MIME-Version: 1.0 To: freebsd-amd64@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: strange network lockup with em0 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Jun 2010 20:09:44 -0000 I should note that this does appear to be yet more strangeness with em0 as network works fine once em0 is disabled the onboard nic nfe0 works fine. From owner-freebsd-amd64@FreeBSD.ORG Wed Jun 23 03:10:06 2010 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6D03D1065677 for ; Wed, 23 Jun 2010 03:10:06 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 2B2D18FC0A for ; Wed, 23 Jun 2010 03:10:06 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o5N3A6xu095270 for ; Wed, 23 Jun 2010 03:10:06 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o5N3A60m095269; Wed, 23 Jun 2010 03:10:06 GMT (envelope-from gnats) Resent-Date: Wed, 23 Jun 2010 03:10:06 GMT Resent-Message-Id: <201006230310.o5N3A60m095269@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-amd64@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Paul Lambert Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D4FC5106564A for ; Wed, 23 Jun 2010 03:02:54 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (www.freebsd.org [IPv6:2001:4f8:fff6::21]) by mx1.freebsd.org (Postfix) with ESMTP id C3EE38FC15 for ; Wed, 23 Jun 2010 03:02:54 +0000 (UTC) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.14.3/8.14.3) with ESMTP id o5N32s3U076818 for ; Wed, 23 Jun 2010 03:02:54 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.14.3/8.14.3/Submit) id o5N32svK076817; Wed, 23 Jun 2010 03:02:54 GMT (envelope-from nobody) Message-Id: <201006230302.o5N32svK076817@www.freebsd.org> Date: Wed, 23 Jun 2010 03:02:54 GMT From: Paul Lambert To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.1 X-Mailman-Approved-At: Wed, 23 Jun 2010 04:38:27 +0000 Cc: Subject: amd64/148078: wireless networking stops functioning X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Jun 2010 03:10:06 -0000 >Number: 148078 >Category: amd64 >Synopsis: wireless networking stops functioning >Confidential: no >Severity: critical >Priority: high >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: update >Submitter-Id: current-users >Arrival-Date: Wed Jun 23 03:10:05 UTC 2010 >Closed-Date: >Last-Modified: >Originator: Paul Lambert >Release: 8.1 prerelease >Organization: BRSINC >Environment: FreeBSD BRSINC-VM02.local 8.0-RELEASE FreeBSD 8.0-RELEASE #0: Sat Nov 21 15:02:08 UTC 2009 root@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 >Description: I finally found time to work with Freebsd 8.0 release from last fall. After struggling to find the correct configuration I was able to get my wireless interface working just great. In an attempt to get Gnome 2.3 loaded I performed a freebsd-update to 8.1 prerelease. After running install and rebooting twice the system booted up with the wlan0 device stating "associated." However, no network response was forth coming. After researching this on the web I found a blog that stated to insert the line synchonous_dhclient="yes." I did and the network interface was able to perform pings and traceroutes. But when I went to download a new package the network froze. Again, I researched the web and found instructions to add if_vlan_load and vaps_ath0="wlan0". Adding these did not make matters any better. I then "rolled back" the Freebsd to 8.0 release and changed the conf files back and the network is up and running as expected. 8.0 release config files rc.conf wlans_ath0="wlan0" ifconfig_wlan0="WPA DHCP" loader.conf wlan_wep_load="YES" wlan_ccmp_load="YES" wlan_tkip_load="YES" wpa_supplicant.conf eapol_version=1 ap_scan=1 fast_reauth=1 # network={ ssid="my wireless AP" psk="my AP password" } >How-To-Repeat: upgrade to 8.1 prerelease >Fix: >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-amd64@FreeBSD.ORG Wed Jun 23 10:00:20 2010 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3C2801065670 for ; Wed, 23 Jun 2010 10:00:20 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 11ABC8FC14 for ; Wed, 23 Jun 2010 10:00:20 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o5NA0J3I081323 for ; Wed, 23 Jun 2010 10:00:19 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o5NA0Jxi081322; Wed, 23 Jun 2010 10:00:19 GMT (envelope-from gnats) Date: Wed, 23 Jun 2010 10:00:19 GMT Message-Id: <201006231000.o5NA0Jxi081322@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: Oliver Pinter Cc: Subject: Re: amd64/148078: wireless networking stops functioning X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Oliver Pinter List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Jun 2010 10:00:20 -0000 The following reply was made to PR amd64/148078; it has been noted by GNATS. From: Oliver Pinter To: Paul Lambert Cc: freebsd-gnats-submit@freebsd.org Subject: Re: amd64/148078: wireless networking stops functioning Date: Wed, 23 Jun 2010 11:52:47 +0200 hi! under 7.3-STABLE is the same problem, on boot +2-3 minutes the networking is ok, but after 2-3 minutes, it going down. The soultion is this: ifconfig_ath0="DHCP WPA protmode rtscts mode 11g -bgscan -burst channel 12 -powersave" It's an ar5212 tp-link wlan card. On 6/23/10, Paul Lambert wrote: > >>Number: 148078 >>Category: amd64 >>Synopsis: wireless networking stops functioning >>Confidential: no >>Severity: critical >>Priority: high >>Responsible: freebsd-amd64 >>State: open >>Quarter: >>Keywords: >>Date-Required: >>Class: update >>Submitter-Id: current-users >>Arrival-Date: Wed Jun 23 03:10:05 UTC 2010 >>Closed-Date: >>Last-Modified: >>Originator: Paul Lambert >>Release: 8.1 prerelease >>Organization: > BRSINC >>Environment: > FreeBSD BRSINC-VM02.local 8.0-RELEASE FreeBSD 8.0-RELEASE #0: Sat Nov 21 > 15:02:08 UTC 2009 > root@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 > >>Description: > I finally found time to work with Freebsd 8.0 release from last fall. After > struggling to find the correct configuration I was able to get my wireless > interface working just great. In an attempt to get Gnome 2.3 loaded I > performed a freebsd-update to 8.1 prerelease. After running install and > rebooting twice the system booted up with the wlan0 device stating > "associated." However, no network response was forth coming. After > researching this on the web I found a blog that stated to insert the line > synchonous_dhclient="yes." I did and the network interface was able to > perform pings and traceroutes. But when I went to download a new package > the network froze. Again, I researched the web and found instructions to > add if_vlan_load and vaps_ath0="wlan0". Adding these did not make matters > any better. I then "rolled back" the Freebsd to 8.0 release and changed the > conf files back and the network is up and running as expected. > > 8.0 release config files > > rc.conf > wlans_ath0="wlan0" > ifconfig_wlan0="WPA DHCP" > > loader.conf > wlan_wep_load="YES" > wlan_ccmp_load="YES" > wlan_tkip_load="YES" > > wpa_supplicant.conf > eapol_version=1 > ap_scan=1 > fast_reauth=1 > # > network={ > ssid="my wireless AP" > psk="my AP password" > } > > >>How-To-Repeat: > upgrade to 8.1 prerelease >>Fix: > > >>Release-Note: >>Audit-Trail: >>Unformatted: > _______________________________________________ > freebsd-amd64@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 > To unsubscribe, send any mail to "freebsd-amd64-unsubscribe@freebsd.org" > From owner-freebsd-amd64@FreeBSD.ORG Thu Jun 24 10:16:46 2010 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D27CC106567E for ; Thu, 24 Jun 2010 10:16:44 +0000 (UTC) (envelope-from ipluta@wp.pl) Received: from mx4.wp.pl (mx4.wp.pl [212.77.101.8]) by mx1.freebsd.org (Postfix) with ESMTP id 7471B8FC0C for ; Thu, 24 Jun 2010 10:16:44 +0000 (UTC) Received: (wp-smtpd smtp.wp.pl 7457 invoked from network); 24 Jun 2010 12:16:41 +0200 Received: from 82-210-167-137.home.aster.pl (HELO [127.0.0.1]) (ipluta@[82.210.167.137]) (envelope-sender ) by smtp.wp.pl (WP-SMTPD) with AES256-SHA encrypted SMTP for ; 24 Jun 2010 12:16:41 +0200 Message-ID: <4C233089.3020802@wp.pl> Date: Thu, 24 Jun 2010 12:16:41 +0200 From: Ireneusz Pluta User-Agent: Thunderbird 2.0.0.24 (Windows/20100228) MIME-Version: 1.0 To: freebsd-amd64@freebsd.org References: <4BD8849B.7060904@wp.pl> In-Reply-To: <4BD8849B.7060904@wp.pl> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-WP-AV: skaner antywirusowy poczty Wirtualnej Polski S. A. X-WP-SPAM: NO 0000000 [EZNE] Subject: Re: SMART data from behind SAS MegaRaid X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jun 2010 10:16:46 -0000 Ireneusz Pluta pisze: > Hello, > > does anyone know how to access SMART data from behind LSI SAS > MegaRAID? The smartctl utility does have -d megaraid option, however > supported only in Linux, not FreeBSD. Yes, this is wrong group to ask that. Anyway, to answer myself, and for the sake of completeness of this thread, mfip device is the way to go -> e.g. http://old.nabble.com/how-to-create-pass-devices-without-reboot--td27045949.html From owner-freebsd-amd64@FreeBSD.ORG Thu Jun 24 07:30:07 2010 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 66D671065678 for ; Thu, 24 Jun 2010 07:30:07 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 43B6F8FC12 for ; Thu, 24 Jun 2010 07:30:07 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o5O7U7p4019067 for ; Thu, 24 Jun 2010 07:30:07 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o5O7U7V9019062; Thu, 24 Jun 2010 07:30:07 GMT (envelope-from gnats) Resent-Date: Thu, 24 Jun 2010 07:30:07 GMT Resent-Message-Id: <201006240730.o5O7U7V9019062@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-amd64@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Alexey Samoylov Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C371F106564A for ; Thu, 24 Jun 2010 07:29:03 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (www.freebsd.org [IPv6:2001:4f8:fff6::21]) by mx1.freebsd.org (Postfix) with ESMTP id 98DE78FC16 for ; Thu, 24 Jun 2010 07:29:03 +0000 (UTC) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.14.3/8.14.3) with ESMTP id o5O7T2Vm071018 for ; Thu, 24 Jun 2010 07:29:02 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.14.3/8.14.3/Submit) id o5O7T2tT071017; Thu, 24 Jun 2010 07:29:02 GMT (envelope-from nobody) Message-Id: <201006240729.o5O7T2tT071017@www.freebsd.org> Date: Thu, 24 Jun 2010 07:29:02 GMT From: Alexey Samoylov To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.1 X-Mailman-Approved-At: Thu, 24 Jun 2010 11:05:41 +0000 Cc: Subject: amd64/148106: nginx udplog causes kernel panic on 8.0-RELEASE-p2 amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jun 2010 07:30:07 -0000 >Number: 148106 >Category: amd64 >Synopsis: nginx udplog causes kernel panic on 8.0-RELEASE-p2 amd64 >Confidential: no >Severity: critical >Priority: medium >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Jun 24 07:30:06 UTC 2010 >Closed-Date: >Last-Modified: >Originator: Alexey Samoylov >Release: 8.0-RELEASE-p2 >Organization: E-Commerce LLC >Environment: FreeBSD foo.bar 8.0-RELEASE-p2 FreeBSD 8.0-RELEASE-p2 #0: Tue Feb 9 08:30:33 CET 2010 root@neo.vx.sk:/usr/obj/usr/src/sys/GENERIC amd64 >Description: Hello! A few days ago I tried to use udplog module in nginx and was very upset of result: Jun 14 08:11:15 srv2 kernel: pid 22283 (nginx), uid 1001: exited on signal 11 Jun 14 08:11:15 srv2 kernel: pid 22284 (nginx), uid 1001: exited on signal 11 Jun 14 08:11:15 srv2 kernel: pid 22281 (nginx), uid 1001: exited on signal 11 Jun 14 08:11:15 srv2 kernel: pid 22288 (nginx), uid 1001: exited on signal 11 Jun 14 08:11:15 srv2 kernel: pid 22275 (nginx), uid 1001: exited on signal 11 Jun 14 08:11:15 srv2 kernel: Jun 14 08:11:15 srv2 kernel: Jun 14 08:11:15 srv2 kernel: Fatal trap 12: page fault while in kernel mode Jun 14 08:11:15 srv2 kernel: cpuid = 5; apic id = 05 Jun 14 08:11:15 srv2 kernel: fault virtual address = 0x20 Jun 14 08:11:15 srv2 kernel: fault code = supervisor read data, page not present Jun 14 08:11:15 srv2 kernel: instruction pointer = 0x20:0xffffffff805ba22e Jun 14 08:11:15 srv2 kernel: stack pointer = 0x28:0xffffff800012ba20 Jun 14 08:11:15 srv2 kernel: frame pointer = 0x28:0xffffff800012bb60 Jun 14 08:11:15 srv2 kernel: code segment = base 0x0, limit 0xfffff, type 0x1b Jun 14 08:11:15 srv2 kernel: = DPL 0, pres 1, long 1, def32 0, gran 1 Jun 14 08:11:15 srv2 kernel: processor eflags = interrupt enabled, resume, IOPL = 0 Jun 14 08:11:15 srv2 kernel: current process = 0 (thread taskq) Jun 14 08:11:15 srv2 kernel: trap number = 12 Jun 14 08:11:15 srv2 kernel: panic: page fault Jun 14 08:11:15 srv2 kernel: cpuid = 5 Jun 14 08:11:15 srv2 kernel: Uptime: 30d3h6m15s Jun 14 08:11:15 srv2 kernel: (ada0:ahcich0:0:0:0): Synchronize cache failed Jun 14 08:11:15 srv2 kernel: (ada1:ahcich1:0:0:0): Synchronize cache failed Jun 14 08:11:15 srv2 kernel: Cannot dump. Device not defined or unavailable. Jun 14 08:11:15 srv2 kernel: Automatic reboot in 15 seconds - press a key on the console to abort nginx is compiled with udplog module. Problem exists only if I use udplog directives in config file. Software versions: 8.0-RELEASE-p2 amd64, nginx/0.8.35 >How-To-Repeat: People in nginx mailing list say that this is a repeatable bug on 64bit FreeBSD. >Fix: >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-amd64@FreeBSD.ORG Thu Jun 24 20:30:32 2010 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F108A1065670; Thu, 24 Jun 2010 20:30:32 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id C89E18FC12; Thu, 24 Jun 2010 20:30:32 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o5OKUWmi012660; Thu, 24 Jun 2010 20:30:32 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o5OKUWjZ012562; Thu, 24 Jun 2010 20:30:32 GMT (envelope-from linimon) Date: Thu, 24 Jun 2010 20:30:32 GMT Message-Id: <201006242030.o5OKUWjZ012562@freefall.freebsd.org> To: sav@ecom24.ru, linimon@FreeBSD.org, freebsd-amd64@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: amd64/148106: [panic] nginx udplog causes kernel panic on 8.0-RELEASE-p2 amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jun 2010 20:30:33 -0000 Old Synopsis: nginx udplog causes kernel panic on 8.0-RELEASE-p2 amd64 New Synopsis: [panic] nginx udplog causes kernel panic on 8.0-RELEASE-p2 amd64 State-Changed-From-To: open->feedback State-Changed-By: linimon State-Changed-When: Thu Jun 24 20:29:33 UTC 2010 State-Changed-Why: Can you show us a stack trace of the panic? http://www.freebsd.org/cgi/query-pr.cgi?pr=148106 From owner-freebsd-amd64@FreeBSD.ORG Fri Jun 25 09:28:09 2010 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 565961065670; Fri, 25 Jun 2010 09:28:09 +0000 (UTC) (envelope-from avg@freebsd.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 9169B8FC13; Fri, 25 Jun 2010 09:28:07 +0000 (UTC) Received: from porto.topspin.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id MAA21258; Fri, 25 Jun 2010 12:28:04 +0300 (EEST) (envelope-from avg@freebsd.org) Received: from localhost.topspin.kiev.ua ([127.0.0.1]) by porto.topspin.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1OS5Cc-000C90-Ny; Fri, 25 Jun 2010 12:28:02 +0300 Message-ID: <4C2476A1.1080307@freebsd.org> Date: Fri, 25 Jun 2010 12:28:01 +0300 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.24 (X11/20100603) MIME-Version: 1.0 To: freebsd-hackers@freebsd.org, freebsd-amd64@freebsd.org References: <4C1F798C.7010204@freebsd.org> <201006211143.26459.jhb@freebsd.org> <4C1F8BDD.9010408@freebsd.org> <201006211610.45811.jhb@freebsd.org> <20100621204435.GA98177@hub.freebsd.org> <4C1FDAF9.3080808@freebsd.org> <4C208096.3030602@freebsd.org> In-Reply-To: <4C208096.3030602@freebsd.org> X-Enigmail-Version: 0.96.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Fri, 25 Jun 2010 10:56:57 +0000 Cc: Rui Paulo , Navdeep Parhar Subject: Re: amd64 kernel modules: mapping sections to addresses X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Jun 2010 09:28:09 -0000 Here's a patch that is supposed to do the right thing for dtrace. Perhaps I should have put the new code under __amd64__, but I decided to go more "generic" and check for module's ELF type (ET_REL). Reviews and testing are welcome! diff --git a/cddl/contrib/opensolaris/lib/libdtrace/common/dt_impl.h b/cddl/contrib/opensolaris/lib/libdtrace/common/dt_impl.h index 6bcc5bc..a712d24 100644 --- a/cddl/contrib/opensolaris/lib/libdtrace/common/dt_impl.h +++ b/cddl/contrib/opensolaris/lib/libdtrace/common/dt_impl.h @@ -137,6 +137,7 @@ typedef struct dt_module { dt_idhash_t *dm_extern; /* external symbol definitions */ #if !defined(sun) caddr_t dm_reloc_offset; /* Symbol relocation offset. */ + uintptr_t *dm_sec_offsets; #endif } dt_module_t; diff --git a/cddl/contrib/opensolaris/lib/libdtrace/common/dt_module.c b/cddl/contrib/opensolaris/lib/libdtrace/common/dt_module.c index af17501..d33fb95 100644 --- a/cddl/contrib/opensolaris/lib/libdtrace/common/dt_module.c +++ b/cddl/contrib/opensolaris/lib/libdtrace/common/dt_module.c @@ -83,6 +83,14 @@ dt_module_syminit32(dt_module_t *dmp) uint_t i, n = dmp->dm_nsymelems; uint_t asrsv = 0; +#if defined(__FreeBSD__) + GElf_Ehdr ehdr; + int is_elf_obj; + + gelf_getehdr(dmp->dm_elf, &ehdr); + is_elf_obj = (ehdr.e_type == ET_REL); +#endif + for (i = 0; i < n; i++, sym++) { const char *name = base + sym->st_name; uchar_t type = ELF32_ST_TYPE(sym->st_info); @@ -97,8 +105,12 @@ dt_module_syminit32(dt_module_t *dmp) (ELF32_ST_BIND(sym->st_info) != STB_LOCAL || sym->st_size)) { asrsv++; /* reserve space in the address map */ -#if !defined(sun) +#if defined(__FreeBSD__) sym->st_value += (Elf_Addr) dmp->dm_reloc_offset; + if (is_elf_obj && sym->st_shndx != SHN_UNDEF && + sym->st_shndx < ehdr.e_shnum) + sym->st_value += + dmp->dm_sec_offsets[sym->st_shndx]; #endif } @@ -117,6 +129,14 @@ dt_module_syminit64(dt_module_t *dmp) uint_t i, n = dmp->dm_nsymelems; uint_t asrsv = 0; +#if defined(__FreeBSD__) + GElf_Ehdr ehdr; + int is_elf_obj; + + gelf_getehdr(dmp->dm_elf, &ehdr); + is_elf_obj = (ehdr.e_type == ET_REL); +#endif + for (i = 0; i < n; i++, sym++) { const char *name = base + sym->st_name; uchar_t type = ELF64_ST_TYPE(sym->st_info); @@ -130,9 +150,12 @@ dt_module_syminit64(dt_module_t *dmp) if (sym->st_value != 0 && (ELF64_ST_BIND(sym->st_info) != STB_LOCAL || sym->st_size)) { asrsv++; /* reserve space in the address map */ - -#if !defined(sun) +#if defined(__FreeBSD__) sym->st_value += (Elf_Addr) dmp->dm_reloc_offset; + if (is_elf_obj && sym->st_shndx != SHN_UNDEF && + sym->st_shndx < ehdr.e_shnum) + sym->st_value += + dmp->dm_sec_offsets[sym->st_shndx]; #endif } @@ -722,7 +745,12 @@ dt_module_unload(dtrace_hdl_t *dtp, dt_module_t *dmp) free(dmp->dm_asmap); dmp->dm_asmap = NULL; } - +#if defined(__FreeBSD__) + if (dmp->dm_sec_offsets != NULL) { + free(dmp->dm_sec_offsets); + dmp->dm_sec_offsets = NULL; + } +#endif dmp->dm_symfree = 0; dmp->dm_nsymbuckets = 0; dmp->dm_nsymelems = 0; @@ -846,9 +874,12 @@ dt_module_update(dtrace_hdl_t *dtp, struct kld_file_stat *k_stat) (void) snprintf(fname, sizeof (fname), "%s/%s/object", OBJFS_ROOT, name); #else + GElf_Ehdr ehdr; GElf_Phdr ph; char name[MAXPATHLEN]; + uintptr_t mapbase, alignmask; int i = 0; + int is_elf_obj; (void) strlcpy(name, k_stat->name, sizeof(name)); (void) strlcpy(fname, k_stat->pathname, sizeof(fname)); @@ -893,7 +924,20 @@ dt_module_update(dtrace_hdl_t *dtp, struct kld_file_stat *k_stat) dt_module_destroy(dtp, dmp); return; } - +#if defined(__FreeBSD__) + mapbase = (uintptr_t)k_stat->address; + gelf_getehdr(dmp->dm_elf, &ehdr); + is_elf_obj = (ehdr.e_type == ET_REL); + if (is_elf_obj) { + dmp->dm_sec_offsets = + malloc(ehdr.e_shnum * sizeof(*dmp->dm_sec_offsets)); + if (dmp->dm_sec_offsets == NULL) { + dt_dprintf("failed to allocate memory\n"); + dt_module_destroy(dtp, dmp); + return; + } + } +#endif /* * Iterate over the section headers locating various sections of * interest and use their attributes to flesh out the dt_module_t. @@ -902,7 +946,19 @@ dt_module_update(dtrace_hdl_t *dtp, struct kld_file_stat *k_stat) if (gelf_getshdr(sp, &sh) == NULL || sh.sh_type == SHT_NULL || (s = elf_strptr(dmp->dm_elf, shstrs, sh.sh_name)) == NULL) continue; /* skip any malformed sections */ - +#if defined(__FreeBSD__) + if (sh.sh_size == 0) + continue; + if (is_elf_obj && (sh.sh_type == SHT_PROGBITS || + sh.sh_type == SHT_NOBITS)) { + alignmask = sh.sh_addralign - 1; + mapbase += alignmask; + mapbase &= ~alignmask; + sh.sh_addr = mapbase; + dmp->dm_sec_offsets[elf_ndxscn(sp)] = sh.sh_addr; + mapbase += sh.sh_size; + } +#endif if (strcmp(s, ".text") == 0) { dmp->dm_text_size = sh.sh_size; dmp->dm_text_va = sh.sh_addr; @@ -927,6 +983,13 @@ dt_module_update(dtrace_hdl_t *dtp, struct kld_file_stat *k_stat) #if defined(sun) dmp->dm_modid = (int)OBJFS_MODID(st.st_ino); #else + /* + * Include .rodata and special sections into .text. + * This depends on default section layout produced by GNU ld + * for ELF objects and libraries: + * [Text][R/O data][R/W data][Dynamic][BSS][Non loadable] + */ + dmp->dm_text_size = dmp->dm_data_va - dmp->dm_text_va; #if defined(__i386__) /* * Find the first load section and figure out the relocation -- Andriy Gapon From owner-freebsd-amd64@FreeBSD.ORG Fri Jun 25 12:40:01 2010 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 722621065670 for ; Fri, 25 Jun 2010 12:40:01 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 35F7A8FC15 for ; Fri, 25 Jun 2010 12:40:01 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o5PCe15C004612 for ; Fri, 25 Jun 2010 12:40:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o5PCe1V5004611; Fri, 25 Jun 2010 12:40:01 GMT (envelope-from gnats) Resent-Date: Fri, 25 Jun 2010 12:40:01 GMT Resent-Message-Id: <201006251240.o5PCe1V5004611@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-amd64@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Marcel Grandemange Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CF34D106566C for ; Fri, 25 Jun 2010 12:30:13 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (www.freebsd.org [IPv6:2001:4f8:fff6::21]) by mx1.freebsd.org (Postfix) with ESMTP id BDDA58FC0C for ; Fri, 25 Jun 2010 12:30:13 +0000 (UTC) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.14.3/8.14.3) with ESMTP id o5PCUDDb028198 for ; Fri, 25 Jun 2010 12:30:13 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.14.3/8.14.3/Submit) id o5PCUDqS028197; Fri, 25 Jun 2010 12:30:13 GMT (envelope-from nobody) Message-Id: <201006251230.o5PCUDqS028197@www.freebsd.org> Date: Fri, 25 Jun 2010 12:30:13 GMT From: Marcel Grandemange To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.1 X-Mailman-Approved-At: Fri, 25 Jun 2010 12:53:15 +0000 Cc: Subject: amd64/148138: zfs raidz pool commands freeze X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Jun 2010 12:40:01 -0000 >Number: 148138 >Category: amd64 >Synopsis: zfs raidz pool commands freeze >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Jun 25 12:40:00 UTC 2010 >Closed-Date: >Last-Modified: >Originator: Marcel Grandemange >Release: 8.0 Release >Organization: E-Soul Technologies >Environment: FreeBSD johan.thavinci.za.net 8.0-RELEASE-p3 FreeBSD 8.0-RELEASE-p3 #0: Tue May 25 20:54:11 UTC 2010 root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 >Description: Built a raidz in a vm, killed one drive booted up state was degraded. Replaced drive tried to rebuild no success with only some zfs related commands causing lock. After adding another drive and attemping to add it to current pool so i could try the zpool offline method, now all zpool related commands lock up and can't be ctrl-c or kill 9 or anything. Pool is uncontrollable now and i assume only way around is too recreate everything from scratch. [update] Even this isnt possible as zpool destroy tank also freezes some command results: [root@johan ~]# zpool status I do a CTRL-T load: 0.00 cmd: zpool 1061 [spa_namespace_lock] 4630.58r 0.00u 0.00s 0% 1756k load: 0.00 cmd: zpool 1061 [spa_namespace_lock] 5145.49r 0.00u 0.00s 0% 1756k and [root@johan ~]# zpool list load: 0.00 cmd: zpool 1257 [spa_namespace_lock] 2.03r 0.02u 0.00s 0% 1760k load: 0.00 cmd: zpool 1257 [spa_namespace_lock] 2.48r 0.02u 0.00s 0% 1760k and [root@johan ~]# zpool destroy tank load: 0.05 cmd: zpool 1262 [spa_namespace_lock] 46.71r 0.00u 0.00s 0% 1744k load: 0.05 cmd: zpool 1262 [spa_namespace_lock] 47.08r 0.00u 0.00s 0% 1744k >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-amd64@FreeBSD.ORG Fri Jun 25 23:40:04 2010 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BFB4A1065746 for ; Fri, 25 Jun 2010 23:40:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 3CFCA8FC1A for ; Fri, 25 Jun 2010 23:40:04 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o5PNe41R015314 for ; Fri, 25 Jun 2010 23:40:04 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o5PNe4KU015313; Fri, 25 Jun 2010 23:40:04 GMT (envelope-from gnats) Resent-Date: Fri, 25 Jun 2010 23:40:04 GMT Resent-Message-Id: <201006252340.o5PNe4KU015313@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-amd64@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Paul Lambert Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2D5E2106564A for ; Fri, 25 Jun 2010 23:31:04 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (www.freebsd.org [IPv6:2001:4f8:fff6::21]) by mx1.freebsd.org (Postfix) with ESMTP id 1C3D08FC08 for ; Fri, 25 Jun 2010 23:31:04 +0000 (UTC) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.14.3/8.14.3) with ESMTP id o5PNV34a076866 for ; Fri, 25 Jun 2010 23:31:03 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.14.3/8.14.3/Submit) id o5PNV3jL076865; Fri, 25 Jun 2010 23:31:03 GMT (envelope-from nobody) Message-Id: <201006252331.o5PNV3jL076865@www.freebsd.org> Date: Fri, 25 Jun 2010 23:31:03 GMT From: Paul Lambert To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.1 X-Mailman-Approved-At: Sat, 26 Jun 2010 04:11:16 +0000 Cc: Subject: amd64/148152: Run levels crash on boot up for dv7-1130US HP Laptop. X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Jun 2010 23:40:04 -0000 >Number: 148152 >Category: amd64 >Synopsis: Run levels crash on boot up for dv7-1130US HP Laptop. >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Jun 25 23:40:03 UTC 2010 >Closed-Date: >Last-Modified: >Originator: Paul Lambert >Release: 8.1-RC1 >Organization: BRSINC >Environment: 8.1-RC1 FreeBSD Jun 14 Buffalo.edu Generic amd64 >Description: The run levels 2 and 3 crash when I select them from the BSD boot selection screen. Run levels 1 and 4 work fine. The boot process stops at: Time counters tick every 1.000 sec. My hardware is an HP dv7-1130US laptop with an AMD Turion X2-70 cpu with ATI Radeon Graphics. >How-To-Repeat: Select run level 2 or 3 before count time on boot select screens reaches zero. >Fix: Unknown >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-amd64@FreeBSD.ORG Sat Jun 26 06:10:10 2010 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 150FD1065670 for ; Sat, 26 Jun 2010 06:10:10 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id CBD138FC24 for ; Sat, 26 Jun 2010 06:10:08 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o5Q6A80i064834 for ; Sat, 26 Jun 2010 06:10:08 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o5Q6A8jE064833; Sat, 26 Jun 2010 06:10:08 GMT (envelope-from gnats) Resent-Date: Sat, 26 Jun 2010 06:10:08 GMT Resent-Message-Id: <201006260610.o5Q6A8jE064833@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-amd64@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Shant Kassardjian Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4A8921065672 for ; Sat, 26 Jun 2010 06:00:31 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (www.freebsd.org [IPv6:2001:4f8:fff6::21]) by mx1.freebsd.org (Postfix) with ESMTP id 1FCA88FC1D for ; Sat, 26 Jun 2010 06:00:31 +0000 (UTC) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.14.3/8.14.3) with ESMTP id o5Q60UmH067838 for ; Sat, 26 Jun 2010 06:00:30 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.14.3/8.14.3/Submit) id o5Q60Unw067837; Sat, 26 Jun 2010 06:00:30 GMT (envelope-from nobody) Message-Id: <201006260600.o5Q60Unw067837@www.freebsd.org> Date: Sat, 26 Jun 2010 06:00:30 GMT From: Shant Kassardjian To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.1 X-Mailman-Approved-At: Sat, 26 Jun 2010 11:17:11 +0000 Cc: Subject: amd64/148157: IPFW in kernel nat BUG found in FreeBSD 8.1-PRERELEASE X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Jun 2010 06:10:10 -0000 >Number: 148157 >Category: amd64 >Synopsis: IPFW in kernel nat BUG found in FreeBSD 8.1-PRERELEASE >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sat Jun 26 06:10:08 UTC 2010 >Closed-Date: >Last-Modified: >Originator: Shant Kassardjian >Release: 8.1-PRERELEASE >Organization: >Environment: FreeBSD core.skylab.ca 8.1-PRERELEASE FreeBSD 8.1-PRERELEASE #0: Tue Jun 22 21:38:07 EDT 2010 >Description: Discovered a bug while running IPFW in kernel nat and TCP redirect_port. The system does a core dump and restarts immediately. Here is what I see: Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0xc fault code = supervisor write data, page not present instruction pointer = 0x20:0xffffffff801d5cd6 stack pointer = 0x28:0xffffff8074fdf370 frame pointer = 0x28:0xffffff8074fdf620 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 1804 (sshd) trap number = 12 panic: page fault cpuid = 0 Uptime: 3m9s Cannot dump. Device not defined or unavailable. Automatic reboot in 15 seconds - press a key on the console to abort >How-To-Repeat: Problem can be replicated by creating a test ipfw policy: ipfw add 001 nat 100 ip from any to any via em0 ipfw nat 100 config ip 192.168.1.104 redirect_port tcp 172.25.1.1:22 22 kernel options: options HZ=1000 options DUMMYNET options IPDIVERT options IPFIREWALL options LIBALIAS options IPFIREWALL_NAT options IPFIREWALL_FORWARD options IPFIREWALL_VERBOSE options IPFIREWALL_VERBOSE_LIMIT=5 options IPFIREWALL_DEFAULT_TO_ACCEPT sysctl settings: kern.ipc.maxsockbuf=16777216 kern.ipc.nmbclusters=32768 kern.ipc.somaxconn=32768 kern.maxfiles=65536 kern.maxfilesperproc=32768 kern.maxvnodes=800000 net.inet.tcp.delayed_ack=0 net.inet.tcp.inflight.enable=0 net.inet.tcp.path_mtu_discovery=0 net.inet.tcp.recvbuf_auto=1 net.inet.tcp.recvbuf_inc=524288 net.inet.tcp.recvbuf_max=16777216 net.inet.tcp.recvspace=65536 net.inet.tcp.rfc1323=1 net.inet.tcp.sendbuf_auto=1 net.inet.tcp.sendbuf_inc=524288 net.inet.tcp.sendspace=65536 net.inet.udp.maxdgram=57344 net.inet.udp.recvspace=65536 net.local.stream.recvspace=65536 net.inet.tcp.sendbuf_max=16777216 net.inet.tcp.mssdflt=1460 net.link.bridge.ipfw=1 net.inet.ip.fw.one_pass=0 net.inet.ip.dummynet.io_fast=1 net.inet.ip.dummynet.hash_size=64 >Fix: Using /etc/rc.d/natd with config /etc/natd.conf port 8668 interface em0 redirect_port tcp 172.25.1.1:22 22 redirect_port tcp 172.25.1.10:3389 3389 >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-amd64@FreeBSD.ORG Sat Jun 26 19:00:17 2010 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D4E2C1065670 for ; Sat, 26 Jun 2010 19:00:17 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id C3EB38FC16 for ; Sat, 26 Jun 2010 19:00:17 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o5QJ0Ht2065982 for ; Sat, 26 Jun 2010 19:00:17 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o5QJ0Hv2065981; Sat, 26 Jun 2010 19:00:17 GMT (envelope-from gnats) Date: Sat, 26 Jun 2010 19:00:17 GMT Message-Id: <201006261900.o5QJ0Hv2065981@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: Garrett Cooper Cc: Subject: Re: amd64/148157: IPFW in kernel nat BUG found in FreeBSD 8.1-PRERELEASE X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Garrett Cooper List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Jun 2010 19:00:17 -0000 The following reply was made to PR amd64/148157; it has been noted by GNATS. From: Garrett Cooper To: Shant Kassardjian Cc: freebsd-gnats-submit@freebsd.org Subject: Re: amd64/148157: IPFW in kernel nat BUG found in FreeBSD 8.1-PRERELEASE Date: Sat, 26 Jun 2010 11:52:01 -0700 Hi, Do you have a backtrace for the issue (bt from ddb, or the equivalent bt from kgdb)? I'm asking because I saw various issues running with in kernel nat as well in various bits of the kernel -- one was the ip routing code, one was the ipfw_nat code, and the other was the network driver that I was using, bce(4). All items suggested that there's a locking issue. The reference to the mail thread I started is here: http://lists.freebsd.org/pipermail/freebsd-net/2010-June/025594.html (note that it's an issue with 8.1-* and 9-CURRENT). Thanks, -Garrett From owner-freebsd-amd64@FreeBSD.ORG Sat Jun 26 20:53:25 2010 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A06371065670; Sat, 26 Jun 2010 20:53:25 +0000 (UTC) (envelope-from rpaulo@freebsd.org) Received: from karen.lavabit.com (karen.lavabit.com [72.249.41.33]) by mx1.freebsd.org (Postfix) with ESMTP id 400B98FC15; Sat, 26 Jun 2010 20:53:25 +0000 (UTC) Received: from e.earth.lavabit.com (e.earth.lavabit.com [192.168.111.14]) by karen.lavabit.com (Postfix) with ESMTP id 6D3A418F39B; Sat, 26 Jun 2010 15:32:00 -0500 (CDT) Received: from 10.0.10.3 (54.81.54.77.rev.vodafone.pt [77.54.81.54]) by lavabit.com with ESMTP id N0S35NBA68I9; Sat, 26 Jun 2010 15:31:58 -0500 Mime-Version: 1.0 (Apple Message framework v1081) Content-Type: text/plain; charset=us-ascii From: Rui Paulo In-Reply-To: <4C2476A1.1080307@freebsd.org> Date: Sat, 26 Jun 2010 21:31:54 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <99843999-233B-4E07-B815-9808B85B599A@freebsd.org> References: <4C1F798C.7010204@freebsd.org> <201006211143.26459.jhb@freebsd.org> <4C1F8BDD.9010408@freebsd.org> <201006211610.45811.jhb@freebsd.org> <20100621204435.GA98177@hub.freebsd.org> <4C1FDAF9.3080808@freebsd.org> <4C208096.3030602@freebsd.org> <4C2476A1.1080307@freebsd.org> To: Andriy Gapon X-Mailer: Apple Mail (2.1081) X-Mailman-Approved-At: Sat, 26 Jun 2010 22:48:43 +0000 Cc: freebsd-hackers@freebsd.org, Navdeep Parhar , freebsd-amd64@freebsd.org Subject: Re: amd64 kernel modules: mapping sections to addresses X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Jun 2010 20:53:25 -0000 On 25 Jun 2010, at 10:28, Andriy Gapon wrote: >=20 > Here's a patch that is supposed to do the right thing for dtrace. > Perhaps I should have put the new code under __amd64__, but I decided = to go more > "generic" and check for module's ELF type (ET_REL). >=20 > Reviews and testing are welcome! I believe this is good to go. Regards, -- Rui Paulo