mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Witold Władysław Wojciech Wilk" <witold.wilk@gmail.com>
To: "Uwe Zeisberger" <zeisberg@informatik.uni-freiburg.de>,
	"Witold W?adys?aw Wojciech Wilk" <witold.wilk@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: how to get the kernel to be more "verbose"?
Date: Fri, 6 Oct 2006 12:19:29 +0200	[thread overview]
Message-ID: <98975a8b0610060319u30b6862as886232e9bb5a3723@mail.gmail.com> (raw)
In-Reply-To: <20061006094348.GB11065@informatik.uni-freiburg.de>

2006/10/6, Uwe Zeisberger <zeisberg@informatik.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@gmail.com
pms/kc: citroen xantia mkI 2.0 8v 1995 225kkm/17kkm hydrokomfortowa :)

  reply	other threads:[~2006-10-06 10:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-06  5:34 Witold Władysław Wojciech Wilk
2006-10-06  7:33 ` Uwe Zeisberger
     [not found]   ` <98975a8b0610060038t4d5dbd14ja348ce78351a93e3@mail.gmail.com>
2006-10-06  9:43     ` Uwe Zeisberger
2006-10-06 10:19       ` Witold Władysław Wojciech Wilk [this message]
2006-10-06 16:22   ` Randy Dunlap

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=98975a8b0610060319u30b6862as886232e9bb5a3723@mail.gmail.com \
    --to=witold.wilk@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zeisberg@informatik.uni-freiburg.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®