On Mon, Jan 15, 2007 at 05:13:04PM +0100, Fernando Apestegu?a wrote: > On 1/15/07, Erik Mouw <mouw@xxxxxxxxxxxx> wrote: > >On Mon, Jan 15, 2007 at 02:13:29PM +0100, Fernando Apestegu?a wrote: > >> Today, when I tried to switch down my computer I got this message: > >> (copied in the next boot from /var/log/messages, so I lost the > >> traceback, sorry) > >> > >> Jan 15 13:24:38 hammer kernel: DWARF2 unwinder stuck at > >> system_call+0x7e/0x83 > >> > >> The system finally went down shutting down services as usual. > >> > >> The point is that greping my messages file, I found more than 15 > >> occurrences of this. > >> > >> What does it mean? > > > >It means that the built-in dwarf unwinder couldn't do a full backtrace > >on Oops or lock validator trap. Shouldn't happen anymore with the > >latest kernel. If it does, contact lkml. > > OK, this is not the latest, but so recent: > > 2.6.18-1.2869.fc6 > > Should I report this? If Fedora has no newer kernel than 2.6.18, then yes. Otherwise try a later FC kernel. > BTW, can you point me to a site where I can see what is an "unwinder"? > (A kernel built-in feature to do backtraces??) Pff, dunno. It's one of those things that changed on the road to linux-2.6, I have no idea when it was. Erik -- They're all fools. Don't worry. Darwin may be slow, but he'll eventually get them. -- Matthew Lammers in alt.sysadmin.recovery
Attachment:
signature.asc
Description: Digital signature
