In message <[EMAIL PROTECTED]>, David Xu writes:
>On Thursday 19 September 2002 17:03, Poul-Henning Kamp wrote:
>> Can you try with rev. 1.101 of sys/kern/uipc_mbuf.c please ? The
>> 1.102... is wrong and could easily cause this.
>>
>> Poul-Henning
>>
>> In message <01be01c25fb1$8b92a990$ef01a8c0
On Thursday 19 September 2002 17:03, Poul-Henning Kamp wrote:
> Can you try with rev. 1.101 of sys/kern/uipc_mbuf.c please ? The
> 1.102... is wrong and could easily cause this.
>
> Poul-Henning
>
> In message <01be01c25fb1$8b92a990$ef01a8c0@davidwnt>, "David Xu" writes:
> >#11 0xc02fca38 in call
Can you try with rev. 1.101 of sys/kern/uipc_mbuf.c please ? The
1.102... is wrong and could easily cause this.
Poul-Henning
In message <01be01c25fb1$8b92a990$ef01a8c0@davidwnt>, "David Xu" writes:
>#11 0xc02fca38 in calltrap () at {standard input}:98
>#12 0xc022b699 in sbappendaddr (sb=0xc27
Thanks, it works again. :)
- Original Message -
From: "Julian Elischer" <[EMAIL PROTECTED]>
To: "David Xu" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Thursday, September 19, 2002 4:35 PM
Subject: Re: kernel crash at boot time
> try now
On Thu, 19 Sep 2002, Don Lewis wrote:
>
> - if ((m0->m_flags & M_PKTHDR) != 0)
> - return (m0->m_pkthdr.len);
> -
> len = 0;
> for (m = m0; m != NULL; m = m->m_next) {
> len += m->m_len;
>
already done
To Unsubscribe: send mail to [EMAIL PROTECTED
try now
On Thu, 19 Sep 2002, David Xu wrote:
> Fatal trap 12: page fault while in kernel mode
> fault virtual address = 0x10
> fault code = supervisor read, page not present
> instruction pointer = 0x8:0xc0227c89
> stack pointer = 0x10:0xcd3029c4
> frame pointer
On 19 Sep, David Xu wrote:
> Fatal trap 12: page fault while in kernel mode
> fault virtual address = 0x10
> fault code = supervisor read, page not present
> instruction pointer = 0x8:0xc0227c89
> stack pointer = 0x10:0xcd3029c4
> frame pointer = 0x10:0xcd302
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x10
fault code = supervisor read, page not present
instruction pointer = 0x8:0xc0227c89
stack pointer = 0x10:0xcd3029c4
frame pointer = 0x10:0xcd3029c4
code segment= base 0x0,
>Could someone with a recent (ie < 1 week) -CURRENT confirm whether they
>have problems booting their system when setting allscreens_flags to
>"VESA_800x600"? I have now verified the problem with two different
>systems -- Compaq Professional Workstation 5100 (UP, Matrox Millenium
>II) and Intel P
Could someone with a recent (ie < 1 week) -CURRENT confirm whether they
have problems booting their system when setting allscreens_flags to
"VESA_800x600"? I have now verified the problem with two different
systems -- Compaq Professional Workstation 5100 (UP, Matrox Millenium
II) and Intel Provi
10 matches
Mail list logo
