linux-kernel - Re: How to get backtrace? modprobe -r iwlagn; modprobe iwlagn kills kernel

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: <201105181829.34827.stevie.trujillo@gmail.com>
Date:	Wed, 18 May 2011 18:29:34 +0200
From:	Stevie Trujillo <stevie.trujillo@...il.com>
To:	Milton Miller <miltonm@....com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: How to get backtrace? modprobe -r iwlagn; modprobe iwlagn kills kernel

On Wednesday 18 May 2011 17:55:01 Milton Miller wrote:
> On Wed May 18 2011 about 10:37:54 EST, Stevie Trujillo wrote:
> > I then tried kexec+crashkernel, but I only managed to get a backtrace
> > for the last panic (which I think is just a result of memory corruption
> > or something).  Finally I tried compiling ramoops into my kernel,
> > but it didn't want to load because of "No such device".
> 
> For the kexec+crashkernel, try to retrieve the kernel log buffer:
> 
> There are some macros available, but basically log_buf is a pointer
> to a buffer of length log_buf_len initialized to __log_buf (but can
> be expanded via the command line or sysctl, in). log_end is the
> end of the buffer.  If you haven't wrapped then just print log_end
> characters.

Thank you! This worked perfectly. I sent it to linux-wireless now.
--
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/