Skip to contentSkip to conversation

logbuffer

U-Boot-Users Michael R. Hines 3 participants 6 messages Jun 30, 2006 – Jul 6, 2006

lore
Share & tools
lore
#0 lore raw

I'd like to use the logbuffer functionality in u-boot...

After #define'ing CONFIG_LOGBUFFER, I can successfully see our data getting printed to the reserved 16K region in dram. However, we want to grab that data back out after linux has booted.

During the various initializations that linux does on boot, (somewhere before init is actually run, I believe), the data in the 16K buffer at the end of dram gets over-written by somebody inside linux, and is lost.

I found a thread somewhere on the net where Wolfgang mentioned that linux needed a patch to be told not to intrude on those logbuffer pages, but nothing more than that.

Is there a proper way to handle this?

Thanks,
- Michael R. Hines

#1 lore raw
Quoted 18 lines · --- "Michael R. Hines

I'd like to use the logbuffer functionality in u-boot...

After #define'ing CONFIG_LOGBUFFER, I can successfully see our data getting printed to the reserved 16K region in dram. However, we want to grab that data back out after linux has booted.

During the various initializations that linux does on boot, (somewhere before init is actually run, I believe), the data in the 16K buffer at the end of dram gets over-written by somebody inside linux, and is lost.

I found a thread somewhere on the net where Wolfgang mentioned that linux needed a patch to be told not to intrude on those logbuffer pages, but nothing more than that.

Quoted 4 lines

Is there a proper way to handle this?

Thanks,
- Michael R. Hines

I've never used the log buffer before, but I would think you could just tell the kernel you have less memory then is physically there. That way the kernel wouldn't touch the area used by the log buffer...

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com

#2 lore raw

That's what my first attempt tried to do, but it didn't seem to work.

I reduced mem_size (I think) inside the bd_info struct by 16K.

Just curious if there was a more properly intended way of going about it...

- Michael

Quoted 36 lines · Frank
Quoted 17 lines · --- "Michael R. Hines

I'd like to use the logbuffer functionality in u-boot...

After #define'ing CONFIG_LOGBUFFER, I can successfully see our data getting printed to the reserved 16K region in dram. However, we want to grab that data back out after linux has booted.

During the various initializations that linux does on boot, (somewhere before init is actually run, I believe), the data in the 16K buffer at the end of dram gets over-written by somebody inside linux, and is lost.

I found a thread somewhere on the net where Wolfgang mentioned that linux needed a patch to be told not to intrude on those logbuffer pages, but nothing more than that.

Quoted 5 lines

Is there a proper way to handle this?

Thanks,
- Michael R. Hines

I've never used the log buffer before, but I would think you could just tell the kernel you have less memory then is physically there. That way the kernel wouldn't touch the area used by the log buffer...

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com

#3 lore raw
Quoted 35 lines · --- "Michael R. Hines

That's what my first attempt tried to do, but it didn't seem to work.

I reduced mem_size (I think) inside the bd_info struct by 16K.

Just curious if there was a more properly intended way of going about it...

- Michael

Quoted 5 lines · Frank
Quoted 2 lines · --- "Michael R. Hines

I'd like to use the logbuffer functionality in u-boot...

Quoted 7 lines
Quoted 7 lines

After #define'ing CONFIG_LOGBUFFER, I can successfully see our data getting printed to the reserved 16K region in dram. However, we want to grab that data back out after linux has booted.

During the various initializations that linux does on boot, (somewhere before init is actually run, I believe), the

data

Quoted 10 lines
Quoted 10 lines

in the 16K buffer at the end of dram gets over-written by somebody inside linux, and is lost.

I found a thread somewhere on the net where Wolfgang mentioned that linux needed a patch to be told not to intrude on those logbuffer pages, but nothing more than that.

Is there a proper way to handle this?

Quoted 9 lines
Quoted 7 lines
Quoted 3 lines

Thanks,
- Michael R. Hines

I've never used the log buffer before, but I would think you could just tell the kernel you have less memory then is physically there. That way the kernel wouldn't touch the

area

Quoted 1 line

used by the log buffer...

Try reducing it on the kernel cmdline (mem=xxM) by 1Meg increments.

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com

#4 lore raw

That's exactly what I needed. Thank. Instead, however I reduced it by exactly 16 KB, the size of the logbuffer.

Quoted 54 lines · Frank
Quoted 42 lines · --- "Michael R. Hines

That's what my first attempt tried to do, but it didn't seem to work.

I reduced mem_size (I think) inside the bd_info struct by 16K.

Just curious if there was a more properly intended way of going about it...

- Michael

Quoted 6 lines · Frank
Quoted 2 lines · --- "Michael R. Hines

I'd like to use the logbuffer functionality in u-boot...

Quoted 8 lines
Quoted 8 lines

After #define'ing CONFIG_LOGBUFFER, I can successfully see our data getting printed to the reserved 16K region in dram. However, we want to grab that data back out after linux has booted.

During the various initializations that linux does on boot, (somewhere before init is actually run, I believe), the

data

Quoted 14 lines
Quoted 14 lines

in the 16K buffer at the end of dram gets over-written by somebody inside linux, and is lost.

I found a thread somewhere on the net where Wolfgang mentioned that linux needed a patch to be told not to intrude on those logbuffer pages, but nothing more than that.

Is there a proper way to handle this?

Thanks,
- Michael R. Hines

Quoted 8 lines
Quoted 4 lines

I've never used the log buffer before, but I would think you could just tell the kernel you have less memory then is physically there. That way the kernel wouldn't touch the

area

Quoted 2 lines

used by the log buffer...

Quoted 7 lines

Try reducing it on the kernel cmdline (mem=xxM) by 1Meg increments.

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: OpenPGP digital signature
Url : http://lists.denx.de/pipermail/u-boot/attachments/20060706/b4d905cd/attachment.pgp

#5 lore raw
In reply to Michael R. Hines
Quoted 2 lines · In message <[email protected]> you wrote:

I'd like to use the logbuffer functionality in u-boot...

OK.

Quoted 4 lines

I found a thread somewhere on the net where Wolfgang mentioned that linux needed a patch to be told not to intrude on those logbuffer pages, but nothing more than that.

Corresponding code can be found in our linux-2.4 kernel tree.

Best regards,

Wolfgang Denk

Signature · 6 lines
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Boss, n.: According to the Oxford English Dictionary, in  the  Middle
Ages  the  words  "boss"  and "botch" were largely synonymous, except
that boss, in addition to meaning  "a  supervisor  of  workers"  also
meant "an ornamental stud."