Hi, I've forgotten about this question.
Recently I found that the reason printk in the next line seemed to have
started when the program is stuck during the first printk processing was
because there was an exception and the exception handler also calls printk.
I thought the printk was coming
On Thu, 3 Mar 2022, 02:05 FMDF, wrote:
> On Wed, 2 Mar 2022, 17:57 Guddla Rupesh, wrote:
>
>> I have seen the config from /proc/config.gz and found that processor
>> family as generic x86 64.
>>
>> Actually my system consists of i3 10th gen comet lake 10100 which has
>> integrated graphics and
On Wed, 2 Mar 2022, 17:57 Guddla Rupesh, wrote:
> I have seen the config from /proc/config.gz and found that processor
> family as generic x86 64.
>
> Actually my system consists of i3 10th gen comet lake 10100 which has
> integrated graphics and pci express 4.0 and also lots of new instructions
On Tue, Mar 01, 2022 at 04:42:53PM +0530, Guddla Rupesh wrote:
> Someone of you asked what is the need of compiling source code of kernel
> and I am doing so due to the following reasons.
>
> The main issues are when I click the shutdown button in desktop
> environments like gnome, mate the
Hi Guddla,
On Wed, Mar 02, 2022 at 10:27:15PM +0530, Guddla Rupesh wrote:
> I think that normal kernel shipped by the distro is generic and it
> doesn't have support for latest instructions like avx2, sse4 etc.,. To
> get support we must compile kernel with lots of tuning.
I believe most of
I have seen the config from /proc/config.gz and found that processor family
as generic x86 64.
Actually my system consists of i3 10th gen comet lake 10100 which has
integrated graphics and pci express 4.0 and also lots of new instructions
like avx2, sse4 etc.,.
The main reason of compiling
I have seen the config from /proc/config.gz and found that processor family
as generic x86 64.
Actually my system consists of i3 10th gen comet lake 10100 which has
integrated graphics and pci express 4.0 and also lots of new instructions
like avx2, sse4 etc.,.
The main reason of compiling
Alright, got it.
The trace is in the file
/sys/kernel/debug/tracing/trace
I was checking for the messages in dmesg instead. My issue. Also, enabling
all the events is probably not a good idea, on my system the file does not
open after enabling all the events, my guess is that there are way to
Yes, I am using that reference but since no tracepoints are being hit, it
leaves me confused.
On Wed, Mar 2, 2022 at 5:53 PM Constantine Shulyupin <
constantine.shulyu...@gmail.com> wrote:
> Please check
> https://www.kernel.org/doc/html/latest/trace/events.html
>
> On Wed, 2 Mar 2022 at 16:38,
Please check
https://www.kernel.org/doc/html/latest/trace/events.html
On Wed, 2 Mar 2022 at 16:38, David Kahurani wrote:
> Hello,
>
> I have compiled a pretty recent Linux kernel mostly basing the
> configuration on the older kernel.
>
> I am now testing out the event tracing system but seem to
Hello,
I have compiled a pretty recent Linux kernel mostly basing the
configuration on the older kernel.
I am now testing out the event tracing system but seem to be having a
problem.
Having enabled all events with
# echo *:* > /sys/kernel/debug/tracing/set_event
As described here [1], I
11 matches
Mail list logo
