From mboxrd@z Thu Jan 1 00:00:00 1970 From: Clemens Koller Date: Tue, 13 Nov 2007 21:08:27 +0100 Subject: [U-Boot-Users] LinuxPostMortemAnalysis only smells like DEADBEEF In-Reply-To: References: <4739F659.6000907@anagramm.de> Message-ID: <473A043B.9060204@anagramm.de> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de robert lazarski schrieb: > Hi Clemens, maybe I can help you this time ;-) . I just so happen to > be running 85xx / 2.6.23 / latest u-boot also have serial port > problems - though in my case its intermittent. I've been able to get > output once every 20 times or so. However, I can always get the > messages from "__log_buf" . In my case, my log buf is 2a0f24 . So I > execute: > > => md 2a0f24 700 > deadbeef is the magic value from u-boot that is used to init memory, > and 003b2ea8 doesn't seem right considering I'm using the same kernel. I'm using 2.6.23.1 and would expect the __log_buf address to change with varying kernel configuration. Can you please send me your kernel .config to verify some stuff. (off-list, I think) I am currently building the latest paulus.git to check my mileage with that tree... The next step is to kick u-boot's memory wipe out of the way. (AFAIK it sets up a DMA channel to wipe the available RAM...) ...and to setup the PRAM command (Protect RAM) which might be useful here. > As for my problems, I'm waiting for my hardware guys to give me a > second serial port to try out kgdb. I've been using just printk's for > now, but I just got my bdi back so I might know more soon. Maybe we > could help each other. I would be interested in the kgdb stuff as well... once it's working 8-) Well, talk to you tomorrow. Regards, Clemens Koller __________________________________ R&D Imaging Devices Anagramm GmbH Rupert-Mayer-Stra?e 45/1 Linhof Werksgel?nde D-81379 M?nchen Tel.089-741518-50 Fax 089-741518-19 http://www.anagramm-technology.com