linux-kernel - Re: how to get the kernel to be more "verbose"?

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <98975a8b0610060319u30b6862as886232e9bb5a3723@mail.gmail.com>
Date:	Fri, 6 Oct 2006 12:19:29 +0200
From:	"Witold Władysław Wojciech Wilk" 
	<witold.wilk@...il.com>
To:	"Uwe Zeisberger" <zeisberg@...ormatik.uni-freiburg.de>,
	"Witold W?adys?aw Wojciech Wilk" <witold.wilk@...il.com>,
	linux-kernel@...r.kernel.org
Subject: Re: how to get the kernel to be more "verbose"?

2006/10/6, Uwe Zeisberger <zeisberg@...ormatik.uni-freiburg.de>:
> > No, I've used the config I had in the 2.6.8 (in proc/config.gz), but
> > the SAME kernel 2.6.8 source compiled incorrectly. So I think this
> > might be some glitch on my machine... because it is im possible to
> > make a kernel that is always getting stuck in the same place.
> Did you notice that Debian kernels are not vanilla but patched?
> You can get the patches from http://packages.debian.org/

OK, I'll check them out. Maybe they did patch them somewhere... But if
such a patch exist I think it should be for quite some time in the
mainstream, because this is quite a critical kernel bug, that it
crashes down.

> > >You can try the "initcall_debug" kernel parameter to see which init
> > >functions are called.
> > I will use that then. I am quite new to debugging the kernel... My
> > programming knowledge is still quite low ;) But I will try that today
> > after work... I will write more. I need to get the Wi-Fi working ASAP.
> Another thing that could help you is SysRQ, there is a request that
> prints out a stack dump.

Unfortunately the SysRQ does not respond. I've tried that to reboot,
shutdown, etc the system after the crash. There is simply no response.
I've tried even compiling into the kernel some really abstract
drivers, just in case I forgot something. I've managed once even a
2.5MB kernel image ;) unfortunately it got stuck just like the rest.

Thanks again, I'll write something more through the weekend, maybe I
will solve this... at least I hope so.
-- 
Witold Wladyslaw Wojciech Wilk Et39m:+48605066384 gg3211630 (lepiej @)
prr: giant boulder'02 @13kkm - brak czasu :( / tychy-sosnowiec-gliwice
pms: vw golf 2 byl, juz sprzedany :) / pierwszeimie.nazwisko@...il.com
pms/kc: citroen xantia mkI 2.0 8v 1995 225kkm/17kkm hydrokomfortowa :)
-
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/