On Wed, 19 Feb 2020 06:19:10 +, "Pankaj Vinadrao Joshi" said:
> I am using linux 5.4.3 with our custom Yocto distro on RISC v machine i want
> to get kernel crash log(hard panic) since RISC v does mot have support for the
> kxec how i can collect the crash logs?
Is netconsole an option, if et
Hi,
I am using linux 5.4.3 with our custom Yocto distro on RISC v machine i want to
get kernel crash log(hard panic) since RISC v does mot have support for the
kxec how i can collect the crash logs?
___
Kernelnewbies mailing list
Kernelnewbies@kernel
Hi Saket,
Thank you so much for the clear instructions. I really wanted to get qemu
to work on my 64bit system so I kept trying and finally I got things to
work.
After following your instructions I could get further but gdb complained
about a "Remote 'g' packet reply is too long".Your way works f
Hi Aruna,
Please find the steps below -
The kernel needs to be compiled with debugging support, for the same
add -g option in KBUILD_CFLAGS and KBUILD_CXXFLAGS.
CONFIG_DEBUG_INFO=y
make ARCH=i386 menuconfig
make ARCH=i386 bzImage -j 5
Now we have compiled the 32 bit binaries
Starting the qemu
Hi,
If anyone uses Qemu can someone please show me how to get started ?
I tried :
sudo qemu-system-x86_64 -s -S -kernel arch/x86/boot/bzImage -initrd
/boot/initrd.img-4.1.2-vtaqemu+ /dev/zero
And it does allow me to access through gdb using target remote
localhost:1234 but when I set a breakpoi
Hi Saket,
You may configure kdump and use crash utility for debugging offline.
Here are some useful links.
https://sites.google.com/site/syscookbook/rhel/rhel-kdump-rhel6
http://www.novell.com/support/kb/doc.php?id=3374462
Otherwise systemtap is good option too.
http://www.linuxforu.com/2010/09/
I am facing an issue where I have been developing a filesystem driver(over
x86) which has become "unstable" by which I mean , at compile time it is
building but during runtime it fails when I call the corresponding APIs
from the user-space.
In order to find out exactly where it is failing, I n
That was quick Silesh. Thanks it worked.
On Mon, Jun 27, 2011 at 11:22 AM, Silesh C V wrote:
> Hi,
>
> On Mon, Jun 27, 2011 at 2:30 PM, amit mehta wrote:
>>
>> I've two 64 bit machines,both have Linux kernel running, but on one of
>> the machines
>> I'm not seeing any node under /sys/kernel/deb
Hi,
On Mon, Jun 27, 2011 at 2:30 PM, amit mehta wrote:
>
> I've two 64 bit machines,both have Linux kernel running, but on one of
> the machines
> I'm not seeing any node under /sys/kernel/debug.
Debugfs is not mounted maybe?
mount -t debugfs none /sys/kernel/debug
Regards,
Silesh
___
I've two 64 bit machines,both have Linux kernel running, but on one of
the machines
I'm not seeing any node under /sys/kernel/debug.
I checked some config(CONFIG_*) in the kernel configuration file on
both machines
but they seem to be the same. More information below:
1: SuseX86_64:~ # uname -a
Li
On Mon, 2 May 2011, Greg KH wrote:
> On Mon, May 02, 2011 at 10:31:54PM +0530, Vikram Narayanan wrote:
> > > i'm getting ready to teach a basic device drivers course in a couple
> > >weeks with someone else's courseware and i just wanted to bring some
> > >sections up to date. there's one sectio
On Mon, May 02, 2011 at 10:31:54PM +0530, Vikram Narayanan wrote:
> > i'm getting ready to teach a basic device drivers course in a couple
> >weeks with someone else's courseware and i just wanted to bring some
> >sections up to date. there's one section on basic debugging that
> >covers printk()
> i'm getting ready to teach a basic device drivers course in a couple
>weeks with someone else's courseware and i just wanted to bring some
>sections up to date. there's one section on basic debugging that
>covers printk() as well as other topics from LDD3 such as
>printk_ratelimit(), setting th
On Mon, 2 May 2011, Eduardo Silva wrote:
> for specific printk i would suggest to check the source header:
>
> include/linux/printk.h
yes, i'm already doing that. also the device-related debugging
primitives defined in include/linux/device.h as well.
rday
--
==
for specific printk i would suggest to check the source header:
include/linux/printk.h
On Mon, May 2, 2011 at 11:33 AM, Robert P. J. Day wrote:
>
> i'm getting ready to teach a basic device drivers course in a couple
> weeks with someone else's courseware and i just wanted to bring some
>
i'm getting ready to teach a basic device drivers course in a couple
weeks with someone else's courseware and i just wanted to bring some
sections up to date. there's one section on basic debugging that
covers printk() as well as other topics from LDD3 such as
printk_ratelimit(), setting the co
16 matches
Mail list logo
