Reputation
Top tag
Next privilege 1,000 Rep.
See votes, expandable usercard
Badges
2 12 21
Impact
~81k people reached

  • 0 posts edited
  • 1 helpful flag
  • 36 votes cast
1d
awarded  Citizen Patrol
1d
revised Where in GRUB2 source code is the handover/jump to kernel code?
added 5 characters in body
1d
revised Where in GRUB2 source code is the handover/jump to kernel code?
deleted 24 characters in body
1d
asked Where in GRUB2 source code is the handover/jump to kernel code?
Aug
24
comment Why is debug_putstr() not being printed during boot?
It turns out when set debug=all in /boot/grub/grub.cfg is enabled, debug_putstr() is beeing printed.
Aug
24
revised Why is debug_putstr() not being printed during boot?
added 95 characters in body
Aug
24
asked Why is debug_putstr() not being printed during boot?
Aug
4
revised Where do these boot log entries come from and who creates them?
edited title
Aug
4
comment Where do these boot log entries come from and who creates them?
You are right, indeed. Now I wonder why there is a kernel: in front and thus where the kernel calls this function. Or does grub call it? Don't really get the flow there but it has to be grub I guess because the kernel has probably not been initialized at that moment.
Aug
4
comment Where do these boot log entries come from and who creates them?
But there's no such code, I greped the sources.
Aug
4
asked Where do these boot log entries come from and who creates them?
Jul
4
accepted Where in the kernel /dev/kmsg gets initialized?
Jul
4
comment Where in the kernel /dev/kmsg gets initialized?
Okay now I understand why I didn't find it. Thanks a lot!
Jul
4
comment Where in the kernel /dev/kmsg gets initialized?
But where is it called during boot process? Can't find it anywhere in /arch/x86 or init?
Jul
4
asked Where in the kernel /dev/kmsg gets initialized?
Jun
15
awarded  Notable Question
Jun
8
awarded  Yearling
Jun
7
awarded  Popular Question
May
27
comment Triggering hardware interrupts by connecting parallel port pins 9 and 10 does not work
Yeah, I could do that but dump_stack() eventually just calls printk() too, right. But isn't e1000 already available in initrd? As I said it does not seem to be called after /dev/kmsg is created since otherwise I'd see it. I'll give dump_stack() a try.
May
27
comment Triggering hardware interrupts by connecting parallel port pins 9 and 10 does not work
Hmm, at least e1000_open() and thus e1000_irq_enable() gets called before /dev/kmsg is created, since the printk() I put into e1000_open() is not available in dmesg.