From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1N1S8f-0003hq-I0 for garchives@archives.gentoo.org; Fri, 23 Oct 2009 21:57:37 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id D4A5EE08D5; Fri, 23 Oct 2009 21:57:11 +0000 (UTC) Received: from mail-pz0-f174.google.com (mail-pz0-f174.google.com [209.85.222.174]) by pigeon.gentoo.org (Postfix) with ESMTP id 74F06E08D5 for ; Fri, 23 Oct 2009 21:57:11 +0000 (UTC) Received: by pzk4 with SMTP id 4so11120826pzk.32 for ; Fri, 23 Oct 2009 14:57:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=uRdHDDUn2OB1LW1jLtE+DVR7gtCCHtXwfEpZXd/e6Ho=; b=lYzWVJ+wCBNxqz3sNt9NkZLw9fZXX2CPu11J+1C5yLgCA8hCqSn0ayTL143BAoqgcu ufCkv0xbuyIRPeeVO4z9RidsAsqkhT0v9hJ7nY9vJQ0jwNz5Ce65wUle4ICoPPHLrBQv th1em5B8am/UGbJ579RsySWmf9I0/sqXn2eqM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=ZJHNY2eTvdGbkiAR8FwarHMwfSf30OT0sZzyeOhEpGikHtLcIoLRI3LMeFMAZp8XTU wE8zx4dMFqv3dJMa5Z8617P6138z97zT1verCzaiyhDF2f7UOvVnfC5mJGwq1W6I9IIU 9JPJhmvRoOq7WDTpInbwFBlRqcPU4SEy4qiHI= Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Received: by 10.142.209.12 with SMTP id h12mr875645wfg.53.1256335031001; Fri, 23 Oct 2009 14:57:11 -0700 (PDT) In-Reply-To: References: Date: Fri, 23 Oct 2009 15:57:10 -0600 Message-ID: Subject: Re: [gentoo-user] Re: kernel panic -- finding proper config diff From: Maxim Wexler To: gentoo-user@lists.gentoo.org Content-Type: text/plain; charset=ISO-8859-1 X-Archives-Salt: a409e30f-1382-4ee6-b7e3-255bac03649b X-Archives-Hash: a447fb427cc03875e71bfa779094993b not an idea really but further experience Since LiveDvD-10.1 boots, albeit buggily, on the netbook. I tried to use the kernel config provided with it. I ran make oldconfig then opened up the menu and whittled away the extraneous modules, built the new kernel, installed it and rebooted. This time, after a flurry of red exclamation points, it reached the login and crashed there. Is it feasible that I should go back in and compile in that kernel log option, what's it called? Then after it crashes, reboot into the working kernel, and see if that log has been created? Hey, I guess that counts as an idea :) BTW, the major problem with the LiveDvD is the tendency for the syslog(?) console to bleed into all the other consoles -- messages just popped onto the screen. mw On 10/23/09, walt wrote: > On 10/22/2009 04:31 PM, walt wrote: >> On 10/21/2009 11:25 AM, Maxim Wexler wrote: > >>> The kernel panicked. The relevant messages are: >>> >>> <...> >>> VFS: Mounted root (ext2 filesystem) readonly on device 8:1, >>> Freeing unused kernel memory: 276k freed >>> Warning: unable to open an initial console > >> ...I don't know if that warning is important. > > Apparently it is important. I just discovered /var/log/kern.log, > which logs things that happen even before / is mounted. > > Here is the relevant part: > > Oct 23 08:18:39 k2 kernel: EXT3-fs: mounted filesystem with writeback data > mode. > Oct 23 08:18:39 k2 kernel: VFS: Mounted root (ext3 filesystem) readonly on > device 8:7. > Oct 23 08:18:39 k2 kernel: Freeing unused kernel memory: 256k freed > Oct 23 08:18:39 k2 kernel: kjournald starting. Commit interval 5 seconds > Oct 23 08:18:39 k2 kernel: udev: starting version 141 > > No such warning for me. The question is why not? Any ideas? > > >