lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Wed, 19 Jul 2006 10:26:24 +0000 From: "gmu 2k6" <gmu2006@...il.com> To: "Roman Zippel" <zippel@...ux-m68k.org>, linux-kernel@...r.kernel.org Subject: Re: Re: i686 hang on boot in userspace On 7/18/06, gmu 2k6 <gmu2006@...il.com> wrote: > On 7/17/06, gmu 2k6 <gmu2006@...il.com> wrote: > > On 7/17/06, Roman Zippel <zippel@...ux-m68k.org> 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 [<c0101a57>] 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 > [<c0101a175>] cpu_idle+0x63/0x79 > [<c041a6cf>] start_kernel+0x262/0x393 > [<c041a1c3>] 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. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists