From owner-freebsd-stable@FreeBSD.ORG Wed Feb 26 00:12:41 2014 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 38E01D29; Wed, 26 Feb 2014 00:12:41 +0000 (UTC) Received: from h2.funkthat.com (gate2.funkthat.com [208.87.223.18]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id EF10A1B81; Wed, 26 Feb 2014 00:12:40 +0000 (UTC) Received: from h2.funkthat.com (localhost [127.0.0.1]) by h2.funkthat.com (8.14.3/8.14.3) with ESMTP id s1Q0CcVk025024 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 25 Feb 2014 16:12:39 -0800 (PST) (envelope-from jmg@h2.funkthat.com) Received: (from jmg@localhost) by h2.funkthat.com (8.14.3/8.14.3/Submit) id s1Q0CcOZ025023; Tue, 25 Feb 2014 16:12:38 -0800 (PST) (envelope-from jmg) Date: Tue, 25 Feb 2014 16:12:38 -0800 From: John-Mark Gurney To: Lev Serebryakov Subject: Re: What is difference between loading module with loader and loading module wtih kldload? Message-ID: <20140226001238.GS92037@funkthat.com> Mail-Followup-To: Lev Serebryakov , hackers@freebsd.org, stable@freebsd.org References: <9890815.20140226013107@serebryakov.spb.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <9890815.20140226013107@serebryakov.spb.ru> User-Agent: Mutt/1.4.2.3i X-Operating-System: FreeBSD 7.2-RELEASE i386 X-PGP-Fingerprint: 54BA 873B 6515 3F10 9E88 9322 9CB1 8F74 6D3F A396 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html X-TipJar: bitcoin:13Qmb6AeTgQecazTWph4XasEsP7nGRbAPE X-to-the-FBI-CIA-and-NSA: HI! HOW YA DOIN? can i haz chizburger? X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.2 (h2.funkthat.com [127.0.0.1]); Tue, 25 Feb 2014 16:12:39 -0800 (PST) Cc: stable@freebsd.org, hackers@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Feb 2014 00:12:41 -0000 Lev Serebryakov wrote this message on Wed, Feb 26, 2014 at 01:31 +0400: > I've upgraded my fileserver to 10-STABLE and got very strange (but > very-very painful) problem, which I could not reproduce on virtual machine > (VirtualBox). > > I'm using geom_raid5 module (and I'm its maintainer, yes) and module, built > for 10-STABLE (after world & kernel build & install & reboot), and loaded > via /boot/loader.conf is reason to almost instant crash after boot. > Sometimes system mounts filesystems before crash and sometimes not. Most of > time it is "page write: page not present", in different places. PS/2 > keyboard is always blocked after that, I could not drop to debugger. No > memory dump performed. Several times it turend off video output (!) right > after crash. Can you give us an exact error message? I am not finding the string: "page write: page not present" anywhere in the tree, on close thing is in trap, where it could be user/supervisor write/read instruction/data page not present, where words seperated by slashes could be one or the other... This sounds like it could be a buffer overflow... Could you try turning on INVARIANTS and other related debugging on 10-STABLE since these were turned off for the RELEASE? Also uname -a would be helpful to know which arch you are on... > But if I boot without this module, drop to single-user mode, load module > with kldload and continue booting with "exit" everything work smoothly for > hours! > > I understand, that it it some incompatibility between module new kernel, > but I could not reproduce it on VirtualBox instance, and I'm puzzled, that > this crash does not occur if module loaded by kldload! Maybe, here is some > hint in this? There are a few differences between a boot time loaded module and a runtime loaded module... The linker runs earlier at boot time to link up the module before things start, the module may be partly run w/ cold set (which informs us the interrupts and other things may not be fully working).. Sysinits are run in a slightly different order (i.e. kernel SYSINITs that appear after your modules will be run first)... -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not."