Hi there, Revisiting this one, again. Firstly, since we've had no other people reporting having hit this issue, I plan to downgrade this from a "critical" bug... I assume if it was happening to everyone the arm port would be unusable, certainly that would be critical; and we'd probably have made a bit of progress figuring it out by now. :(
On Fri, Jun 10, 2005 at 11:36:18PM +0100, Jonathan David Amery wrote: > ... > I've just upgraded my system from woody to sarge. Among other upgrade > problems I noticed that programmes like cp, mv and install were occasionally > segfaulting (and the packages that were invoking them failing to get > installed), leaving register dumps like this in my logs: > > pc : [<400278ac>] lr : [<4002a348>] Not tainted > sp : bffff4f4 ip : 40049cf8 fp : bffff780 > r10: 400333bc r9 : bffffa38 r8 : bffff548 > r7 : bffff561 r6 : 00000000 r5 : 0001c324 r4 : bffff50c > r3 : 00000004 r2 : 00000000 r1 : 00009d6b r0 : bffff508 > Flags: nzCv IRQs on FIQs on Mode USER_32 Segment user > Control: 1C14917D Table: 1C14917D DAC: 00000015 So, its just dawned on me - you're saying these dumps are in your system log? That would suggest this is a kernel panic, or am I misunderstanding you there? The above trace does look like it may be the start of a kernel panic trace - was there anything else in the log? (eg. just prior, or a stack trace following the above?). I'm not at all familiar with how a kernel panic is reported on arm though. On i386, however, a kernel panic will result in something like the above being dumped (cpu register contents), followed by a stack trace, and the userspace program will typically get a SEGV (similar to what you described)... & the kernel struggles on (basically, sounds exactly likely what you described). cheers. -- Nathan
