From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S964791AbWGSK00 (ORCPT ); Wed, 19 Jul 2006 06:26:26 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S964792AbWGSK00 (ORCPT ); Wed, 19 Jul 2006 06:26:26 -0400 Received: from ug-out-1314.google.com ([66.249.92.172]:63454 "EHLO ug-out-1314.google.com") by vger.kernel.org with ESMTP id S964791AbWGSK0Z (ORCPT ); Wed, 19 Jul 2006 06:26:25 -0400 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=mSLj2Z4kQBR9v1/9Kq+oabgUO3BSfAA3yufi4QkptKRGD2wLnWs+yaBZSlg1Eni3faKjhPvpMhAtHaKzcy05jm1s1AFGPvUv7F6zt32Ud+tvtI3rJ8STbGBIxyWdBb+t6hdKIeT3y/dV6bjQLVxkCxVMih2BBG5/1tAdUB3s/9w= Message-ID: Date: Wed, 19 Jul 2006 10:26:24 +0000 From: "gmu 2k6" To: "Roman Zippel" , linux-kernel@vger.kernel.org Subject: Re: Re: i686 hang on boot in userspace In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20060714150418.120680@gmx.net> <20060717133809.150390@gmx.net> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On 7/18/06, gmu 2k6 wrote: > On 7/17/06, gmu 2k6 wrote: > > On 7/17/06, Roman Zippel wrote: > > > Hi, > > > > > > On Mon, 17 Jul 2006, gmu 2k6 wrote: > > > > > > > either I'm too dumb or there is an undocumented way to enable SysRq on > > > > bootup or the machine is really hanging hard. I'm not able use > > > > Alt+Print as nothing happens besides console showing the typed in > > > > characters ^[t. > > > > > > It might be a keyboard problem, try releasing Print, but keeping Alt > > > pressed and then try another key. > > > > maybe the problem is HP's Integrated Lights Out Java Applet. I will > > try tomorrow morning in the server room. > > yep that Java Applet was the problem. it worked when I was physically > connected by keyboard. I got the following by pressing Alt+SysRq+p but > I'm not sure it helps as being in cpu_idle looks normal to me: > Pid: 0, comm: swapper > EIP: 0060 [] CPU: 0 > EIP: isat mwait_idle+0x2a/0x34 > EAX: 00000000 EBX: c0414008 ECX: 00000000 EDX: 00000000 > ESI: c0414000 EDI: c33984e4 EPP: 00004864 DS: 007b ES: 007b > CR0: 8005003b CR2: b7f818cc CR3: 375e73c0 CR4: 000006f0 > [] cpu_idle+0x63/0x79 > [] start_kernel+0x262/0x393 > [] unknown_bootoption+0x0/0x25a > > Alt+SysRq+s seems to sync and write the logs to kern.log/messages but > the logs vanish after reboot. Therefore for the time being I had to > write it down by hand but I'm sure there's an elegant way like saving > the logfiles before booting up again via a second system or livecd. > Maybe there's a better way than that? same boot problem with 2.6.18-rc1-mm2 btw, did not SysRq for that though.