From owner-freebsd-stable@FreeBSD.ORG Tue Oct 17 14:00:30 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4487E16A40F for ; Tue, 17 Oct 2006 14:00:30 +0000 (UTC) (envelope-from nvass@teledomenet.gr) Received: from arwen.teledomenet.gr (arwen.teledomenet.gr [213.142.128.58]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5B9A443D5F for ; Tue, 17 Oct 2006 14:00:28 +0000 (GMT) (envelope-from nvass@teledomenet.gr) Received: from iris ([192.168.1.71]) by arwen.teledomenet.gr (8.12.10/8.12.10) with ESMTP id k9HE0Qm1024153; Tue, 17 Oct 2006 17:00:26 +0300 From: Nikos Vassiliadis To: "[LoN]Kamikaze" Date: Tue, 17 Oct 2006 17:01:23 +0300 User-Agent: KMail/1.9.1 References: <45338F10.2030006@gmx.de> <200610171031.51350.nvass@teledomenet.gr> <4534E056.60608@gmx.de> In-Reply-To: <4534E056.60608@gmx.de> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200610171701.23904.nvass@teledomenet.gr> Cc: freebsd-stable@freebsd.org Subject: Re: kldunload -f has no effect X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Oct 2006 14:00:30 -0000 On Tuesday 17 October 2006 16:53, [LoN]Kamikaze wrote: > Nikos Vassiliadis wrote: > > On Monday 16 October 2006 16:54, [LoN]Kamikaze wrote: > >> I need to 'kldunload -f drm' in order to go into suspend to ram > >> with my thinkpad (suspend works fine with dri disabled). > >> Unfortunately, despite the claims of the manpage the '-f' flag > >> does not alter the behaviour of the kldunload tool. > > > > In my experience using -f will result in a kernel panic. And > > that's well documented in the manual page. I guess you are > > lucky it didn't work:) So, why don't you just reboot? and keep > > the module off your kernel(if that's an option). > > > >> How do I get drm unloaded? > > > > The easy way, just reboot. Or the hard way, fix the kernel module! > > What's the point of suspend if you have to reboot to resume? > > none as I did tell before "Or the hard way, fix the kernel module!" or send a PR HTH, Nikos