I am analyzing the kdump in latest crash utility 8.0.4++.
I think I loaded the module symbols correctly :
crash> mod
MODULE NAME TEXT_BASE SIZE OBJECT FILE
80007a7e2040 npdereference 80007a7e 12288 (not loaded)
[CONFIG_KALLSYMS]
crash>
crash> mod
I am analyzing the kdump in latest crash utility 8.0.4++.
I think I loaded the module symbols correctly :
crash> mod
MODULE NAME TEXT_BASE SIZE OBJECT FILE
80007a7e2040 npdereference 80007a7e 12288 (not loaded)
[CONFIG_KALLSYMS]
crash>
crash> mod
From: Tao Liu
Sent: Tuesday, April 2, 2024 12:15 PM
To: devel@lists.crash-utility.osci.io
Cc: Tao Liu ; Naveen Chaudhary
Subject: [Crash-Utility][PATCH] symbols.c: skip non-exist module memory type
Not all mod_mem_type will be included for kernel modules. E.g. in the
following module
Hi,
I figured out that I should add "--disable-werror" to the configure.
After this I was able to build successfully.
Thanks,
Naveen
____
From: Naveen Chaudhary
Sent: Wednesday, August 19, 2020 3:54 PM
To: bug-g...@gnu.org ; grub-devel@gnu.org
Subject:
Hi,
I figured out that I should add "--disable-werror" to the configure.
After this I was able to build successfully.
Thanks,
Naveen
____
From: Naveen Chaudhary
Sent: Wednesday, August 19, 2020 3:54 PM
To: bug-grub@gnu.org ; grub-de...@gnu.org
Subject:
Hi,
Host : Ubuntu 18.04.3 LTS
GCC : gcc (Ubuntu 7.3.0-16ubuntu3) 7.3.0
uname : Linux vm 5.0.0-27-generic #28~18.04.1-Ubuntu SMP Thu Aug 22 03:00:32
UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
I have clone the GRUB2 from https://github.com/rhboot/grub2 today and the HEAD
points to
Hi,
Host : Ubuntu 18.04.3 LTS
GCC : gcc (Ubuntu 7.3.0-16ubuntu3) 7.3.0
uname : Linux vm 5.0.0-27-generic #28~18.04.1-Ubuntu SMP Thu Aug 22 03:00:32
UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
I have clone the GRUB2 from https://github.com/rhboot/grub2 today and the HEAD
points to
Hi,
I am trying to understand what is the activity corresponding to the fixes
suggested by Intel security advisories relating to the processor/controller
flaws. I took a glance at commit history and did grep "CVE" but there is
nothing there.
Once the advisories are released by Intel, on
PM
To: Naveen Chaudhary ; werner@siemens.com
Cc: coreboot@coreboot.org
Subject: RE: Call to FSP_FSP_INIT never returns back
Hello Naveen,
The longer time is expected on the first boot. After that this should not take
that long.
If every boot takes that long please check if the
Hi fellow engineers,
I got that RAM stick working when I changed the fourth byte of SPD from from
mini-UDIMM (0x06) to SO-DIMM (0x03) and its working fine... But still I am
curious why mini-UDIMM didn't work out. Perhaps this form factor was not
supported by FSP?
Another thing I observed that
Please ignore the addendum (that was my own repo messed up, found the
smi_handler at src/soc/intel/fsp_broadwell_de/smihandler.c).
Please consider the first message.
Regards,
Naveen
From: Naveen Chaudhary
Sent: Wednesday, November 6, 2019 2:06 PM
To: coreboot
,
Naveen
From: Naveen Chaudhary
Sent: Wednesday, November 6, 2019 1:03 PM
To: coreboot@coreboot.org
Subject: [coreboot] How does SMI handling designed in Coreboot and how does
payload behave?
Hi,
I am using Linux bzImage as the payload for coreboot with a minimal
Hi,
I am using Linux bzImage as the payload for coreboot with a minimal initrd that
gives me a shell to play with (or even kexec the bigger kernel on disk).
I could see that Coreboot has SMI handler at src/cpu/x86/smm/smihandler.c which
I am yet to explore more.
1. But by design, who is
You can go with MinnowMax which is based on Baytrail SoC and its compatible
with core boot. In fact, I tested that yesterday only and I am actively using
it with core boot from past few weeks. The latest version of the same board is
Minnow3 that is I believe based on ApolloLake, though I am not
he alternative way could be to
>>> create a UINT8 buff [512] and typecast to
>>> UpdData->MemDownCh0Dimm0SpdPtr = (UINT32) buff;
>>> directly.
>>>
>>> While I am testing all this, anyone please correct me on the .bin
>>> part, so that it helps future contributors as well, as its not
>>&
chip which was failing earlier.
I just put the same data in the initial attempt to see if the values are
getting read properly. But why I get all zeros, is this expected?
Regards,
Naveen
From: Naveen Chaudhary
Sent: Wednesday, October 30, 2019 1:01 PM
To: David Hendric
/smmstub.manual
src/arch/x86/Makefile.inc:246: recipe for target
'build/cbfs/fallback/romstage.debug' failed
Regards,
Naveen
From: Naveen Chaudhary
Sent: Thursday, October 31, 2019 9:46 AM
To: David Hendricks
Cc: Wim Vervoorn ; Nico Huber ;
coreboot@coreboot.org
ibutors as well, as its not documented anywhere in
coreboot.
Regards,
Naveen
From: David Hendricks
Sent: Wednesday, 30 October, 2019, 12:44 PM
To: Naveen Chaudhary
Cc: Wim Vervoorn; Nico Huber; coreboot@coreboot.org
Subject: Re: [coreboot] Re: Coreboot FSP fails to
sentence.
Please correct me.
Regards,
Naveen
Get Outlook for Android<https://aka.ms/ghei36>
From: Wim Vervoorn
Sent: Tuesday, October 29, 2019 3:47:34 PM
To: Naveen Chaudhary ; Nico Huber
; David Hendricks
Cc: coreboot@coreboot.org
Subject: RE: [corebo
Get Outlook for Android<https://aka.ms/ghei36>
From: Wim Vervoorn
Sent: Tuesday, October 29, 2019 3:07:44 PM
To: Nico Huber ; Naveen Chaudhary
; David Hendricks
Cc: coreboot@coreboot.org
Subject: RE: [coreboot] Re: Coreboot FSP fails to initiali
d experience working with custom DIMMs that
aren't POR for FSP? How did you come through this problem? Need your experience
here guys. Please help.
Regards,
Naveen
From: Nico Huber
Sent: Sunday, October 27, 2019 4:03 PM
To: Naveen Chaudhary ; David Hendricks
Cc: c
g an account on GitHub.
github.com
From: David Hendricks
Sent: Saturday, October 26, 2019 7:29 AM
To: Naveen Chaudhary
Cc: coreboot@coreboot.org
Subject: Re: [coreboot] Coreboot FSP fails to initialize RAM - "Configuration
not in POR table"
I am using Faceboot Watson image (with no code changes) on a custom BroadwellDE
based motherboard. Current the FSP_FSP_INIT api never returns back. I enabled
the FSP logs and got the following messages :
bootMode = NormalBoot
subBootMode = ColdBoot
Dispatch Slaves -- Started
Dispatch Slaves -
!
FatalError: SocketId = 0 registered Major Code = 0x 7, Minor Code = 0x 8
Regards,
Naveen
From: Naveen Chaudhary
Sent: Thursday, October 24, 2019 1:13 PM
To: werner@siemens.com
Cc: coreboot@coreboot.org
Subject: Re: Call to FSP_FSP_INIT never returns back
2019 11:16 AM
To: Naveen Chaudhary
Cc: coreboot@coreboot.org
Subject: AW: Call to FSP_FSP_INIT never returns back
Hi.
If you decide to use MemoryDown, you need to provide the SPD data to FSP in a
buffer.
If you use normal DIMM configuration, FSP is able to read SPD data form the SPD
EEPROM
? (MemDownCh*Dimm*SpdPtr is
related to soldered RAM and can't be used).
Can someone please confirm this last thing. Thanks.
Regards,
Naveen
From: Naveen Chaudhary
Sent: Wednesday, October 23, 2019 9:02 PM
To: werner@siemens.com ; coreboot@coreboot.org
Subject: Re
coreboot initializes DIMM
memory for BroadwellDE ? Is it unimplemented or am I missing something?
I request the community to please help and guide.
Regards,
Naveen
From: werner@siemens.com
Sent: Wednesday, October 23, 2019 10:49 AM
To: Naveen Chaudhary
Hi All,
Need some guidance. Please read.
I am porting coreboot for a "Broadwell D 1519" based motherboard which has both
Memory Down as well as 2 DIMM slots. Hence, I built an image for Facebook
Watson since its the closest mainboard with no code changes. The call from
FSP_FSP_INIT never
Hi,
The title seems pretty stupid but that's what I am observing on my MinnowMax.
When I have built coreboot and flashed and the moment I connect the power cable
back, I see the following logs (no romstage beginning logs, no console_init
logs):
romstage_main_continue status: 0 hob_list_ptr:
e logs. The romstage logs
come only when the SeaBIOS waits for 60 seconds and does a hard reboot.
Physically removing the power cable directly leads me to the ramstage.
Regards,
Naveen
From: Naveen Chaudhary
Sent: Sunday, October 20, 2019 4:48 PM
To: coreboot@corebo
S engineer
____
From: Naveen Chaudhary
Sent: Sunday, October 20, 2019 5:16 PM
To: coreboot@coreboot.org
Subject: Re: Bootblock and Romstage logs getting skipped on first boot and boot
continues from ramstage instead
From past 5 days, I have built and flashed coreboot a 100 times a
something similar to point to the coreboot's internal toolchain?
Regards,
Naveen
From: David Hendricks
Sent: Sunday, October 20, 2019 5:47 AM
To: Naveen Chaudhary
Cc: coreboot@coreboot.org
Subject: Re: [coreboot] How to use crossgcc-i386 during make?
Hi Naveen,
D
As per the Wiki : https://www.coreboot.org/Build_HOWTO I did "make
crossgcc-i386". Now when I do make, I get compilation errors because my host
gcc verion is 4.3. In case I update the host gcc version is updated to some
later version, says gcc-8 , the errors are gone.
Looks like coreboot build
Can someone please help here?
Regards,
Naveen
From: Naveen Chaudhary
Sent: Sunday, October 13, 2019 10:47 PM
To: coreboot@coreboot.org
Subject: GRUB2 payload build error
I am able to successfully build with SeaBIOS as payload and also able to boot
I am able to successfully build with SeaBIOS as payload and also able to boot
it on MinnowBoard Max. But when I change the payload to GRUB2, it fails with
the following build error :
Copying file m4/time_h.m4
Copying file m4/unistd-safer.m4
Copying file m4/unistd_h.m4
Copying file
to be the
connection and thus the curl replies with error code 7.
On Thursday, August 10, 2017 at 9:58:58 PM UTC+5:30, Naveen Chaudhary wrote:
>
> I am getting the following jack-server error :
>
> 15:46:17 [ 16% 8051/47793] Ensure Jack server is installed and started
> 15:46:
jack-admin code and I am getting curl code 7,
until the timeout.
On Thursday, August 10, 2017 at 9:58:58 PM UTC+5:30, Naveen Chaudhary wrote:
>
> I am getting the following jack-server error :
>
> 15:46:17 [ 16% 8051/47793] Ensure Jack server is installed and started
> 15
*** This bug is a duplicate of bug 1676881 ***
https://bugs.launchpad.net/bugs/1676881
Public bug reported:
whenever i boot up my laptop, after login, a window pops up saying
system failed : report it.Thats it
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: cups-daemon (not
*** This bug is a duplicate of bug 1676881 ***
https://bugs.launchpad.net/bugs/1676881
Public bug reported:
whenever i boot up my laptop, after login, a window pops up saying
system failed : report it.Thats it
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: cups-daemon (not
*** This bug is a duplicate of bug 1676881 ***
https://bugs.launchpad.net/bugs/1676881
Public bug reported:
whenever i boot up my laptop, after login, a window pops up saying
system failed : report it.Thats it
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: cups-daemon (not
40 matches
Mail list logo
