Hello
I am tracking a rare bug with perfused, where an existing file is
reported as unexistent. It happens after a few hours of usage, and it
happens only once: if I retry accessing the file, I am successful.
Adding traces in perfused while performing ktrace on the calling
process, I am now confi
Hi
I just discovered the oddity below, on a netbsd-5 domU. Is there a
reason for not calling that a bug? Does it happens only at mine?
# strings /dev/mem > /dev/null
xpq_flush_queue: 1 entries
0xa8b5e948: 0x0221
panic: HYPERVISOR_mmu_update failed
fatal breakpoint trap in su
On Thu, Jan 12, 2012 at 09:25:04PM +0400, Evgeniy Ivanov wrote:
>
> Magic too :-) I fall into trouble with it. In generated listing (mbr.S):
>
> 518 00f1 E9FE7Bjmp BOOTADDR
>
> In obj file:
> f1: e9 fe 7b 5a 8a jmp8a5a7cf4
>
> In mbr (i.e. after linking):
>
Hi,
On Thu, Dec 29, 2011 at 11:20 PM, David Laight wrote:
> On Thu, Dec 29, 2011 at 07:55:18PM +0100, Antoine LECA wrote:
>>
>> David Laight wrote:
>> > The actual 'pc' boot sequence is:
>> > Stages 1-3 (and maybe 4) are common to all OS.
>> <...>
>> > 3) The pbr code has to determine where it wa
