I am using 64 bit ARMV8, on Kernel 3.18 based android device.
I am trying to use kgdb using kgdboc on Serial port. When I try to enable the kgdboc, it gets failed (Error -19).
echo ttyS1 > /sys/module/kgdboc/parameters/kgdboc
Please help me to resolve this issue.
Related
I am following this webpage to install nvidia GPU drivers in my fedora 34 64 bit system but it prompts me with an error of unable to load nvidia-drm kernel module while installing. The nvidia driver I used is Quadro RTX 4000 version, 470.74
The log during installation is here.
https://pastebin.com/5GbYcMgp log for nvidia fedora installation
Help of any sort will be appreciated!
I'm using ubuntu 18.04 and trying to boot kernel 2.6.34.7 compiled from source. I tried to boot from ubuntu but it says "kernel too old", then I came up with the idea of using qemu, but I got the same problem... The version of my QEMU emulator is 2.11.1, the error code is:
...
FATAL: kernel too old
[ 5.299747] Kernel panic - not syncing: Attempted to kill init!
[ 5.300415] Pid: 1, comm: init Not tainted 2.6.34.7 #1
...
This is not a problem with QEMU. The "FATAL: kernel too old" message comes from your guest's userspace, specifically its glibc. Your guest's userspace binaries were built to require a newer kernel than the one you're trying to boot, so the two are not compatible. You need to either use a set of userspace binaries (ie a disk image) which was built to work with that old kernel, or you need to use a newer kernel that will work with the binaries you're using.
I created a setup of a guest virtual machine High Sierra which runs by VirtualBox.
I KDP on both guest and host.
I copied the development version of XNU from the KDP directory into the kernel directory on both guest and host.
I read that VirtualBox does not have the implementation for NVRAM so I had to use the following command to setup the kernel boot arguments for kernel debugging.
VBoxManage setextradata “your virtual machine name>" "VBoxInternal2/EfiBootArgs" [here go the kernel boot arguments]
However, I tried the combination of Command+Option+Control+Shift+Esc however it does not work.
As far as I'm aware, Command+Option+Control+Shift+Esc has a special meaning in hardware on Mac laptops. For a VM, you probably want to set the 0x8000 bit in the debug kernel argument and just send an ACPI power event to trigger the debugger instead.
I can't say if this will work in VirtualBox though as I haven't used that to do kernel debugging for a number of years.
My preferred method for attaching to a VM is using DTrace:
sudo dtrace -w -n "BEGIN { breakpoint(); }"
Then from the host you can:
kdp-remote <vm-ip>
I have built the linux kernel 3.14 with debug info. When I tried to boot it gives following error and after that booting freezes
Can somebody tell me how to fix this ?
Linux Version : Slitaz in Qemu
I am trying to connect openOCD to BeagleBone via onboard FTDI JTAG Emulator on Windows 7 x64. I have installed the ftdi driver 64bit that came with BeagleBone. when i connect the BBone to windows, USB Serial Converter A and B shows up along with COM port.
the hardware id of device-managers shows up as:
USB\VID_0403&PID_6010
I have downloaded openOCD 0.6.1 with both 32 & 64 bit binaries and ti_beaglebone.cfg script and the VID PID matches as above.
I have tried executing:
openocd-x64-0.6.1.exe -f board/ti_beaglebone.cfg
But it doesn't recognize the FTDI at all and shows up following lines:
Open On-Chip Debugger 0.6.1 (2012-10-07-10:39)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.sourceforge.net/doc/doxygen/bugs.html
Info : only one transport option; autoselect 'jtag'
adapter speed: 16000 kHz
trst_and_srst separate srst_gates_jtag trst_push_pull srst_open_drain
Warn : unable to open ftdi device (trying more): device not found
Error: unable to open ftdi device: device not found
in procedure 'init'
I have tried both 32 and 64-bit binaries of OpenOCD and no luck.
Any help would be appreciated
Thanks