I have dual COM port pci card:
none7@pci0:8:1:0: class=0x070002 card=0x32534348 chip=0x32534348
rev=0x10 hdr=0x00
class = simple comms
subclass = UART
bar [10] = type I/O Port, range 32, base 0xe880, size 8, enabled
bar [14] = type I/O Port, range 32, base 0xe80
2011/8/15 Andrey V. Elsukov :
> On 10.08.2011 07:12, Kevin Oberman wrote:
>> I have /boot/pmbr loaded into the PMBR and gptboot into the
>> freebsd-boot partition. I'll
>> admit that I did this by rote and don't understand how these two files
>> interact with the
>> UEFI BIOS to get the loader star
On Wednesday, August 10, 2011 7:55:18 pm Jan Mikkelsen wrote:
> Hi,
>
> I have added these device IDs to pucdata.c to support the Moxa CP-112UL board
> family.
>
> Should I submit a problem report, or is there an easier way to get the patch
> merged?
>
> (I care about 8-STABLE at the moment …)
- Original Message -
From: "Andriy Gapon"
To: "Steven Hartland"
Cc:
Sent: Monday, August 15, 2011 4:36 PM
Subject: Re: debugging frequent kernel panics on 8.2-RELEASE
on 15/08/2011 17:56 Steven Hartland said the following:
- Original Message - From: "Andriy Gapon"
To: "
On 10.08.2011 07:12, Kevin Oberman wrote:
> I have /boot/pmbr loaded into the PMBR and gptboot into the
> freebsd-boot partition. I'll
> admit that I did this by rote and don't understand how these two files
> interact with the
> UEFI BIOS to get the loader started. I'm not really certain that I
>
on 15/08/2011 17:56 Steven Hartland said the following:
>
> - Original Message - From: "Andriy Gapon"
> To: "Steven Hartland"
> Cc:
> Sent: Monday, August 15, 2011 2:20 PM
> Subject: Re: debugging frequent kernel panics on 8.2-RELEASE
>
>
>> on 15/08/2011 15:51 Steven Hartland said th
- Original Message -
From: "Andriy Gapon"
To: "Steven Hartland"
Cc:
Sent: Monday, August 15, 2011 2:20 PM
Subject: Re: debugging frequent kernel panics on 8.2-RELEASE
on 15/08/2011 15:51 Steven Hartland said the following:
- Original Message - From: "Andriy Gapon"
on
on 15/08/2011 15:51 Steven Hartland said the following:
> - Original Message - From: "Andriy Gapon"
>
>
>> on 15/08/2011 13:34 Steven Hartland said the following:
>>> (kgdb) list *0x8053b691
>>> 0x8053b691 is in vm_fault (/usr/src/sys/vm/vm_fault.c:239).
>>> 234
- Original Message -
From: "Andriy Gapon"
on 15/08/2011 13:34 Steven Hartland said the following:
(kgdb) list *0x8053b691
0x8053b691 is in vm_fault (/usr/src/sys/vm/vm_fault.c:239).
234 /*
235 * Find the backing store object and offset into it
on 15/08/2011 13:34 Steven Hartland said the following:
> (kgdb) list *0x8053b691
> 0x8053b691 is in vm_fault (/usr/src/sys/vm/vm_fault.c:239).
> 234 /*
> 235 * Find the backing store object and offset into it to begin
> the
> 236 * search.
> 2
on 15/08/2011 13:34 Steven Hartland said the following:
> - Original Message - From: "Andriy Gapon"
>> I think (not 100% sure) that with DDB in kernel we could get a better
>> backtrace
>> here, possibly with pre-dblfault stack frames, because DDB backend is a bit
>> more
>> smarter than
- Original Message -
From: "Andriy Gapon"
We have 352 thread entries starting with:-
#0 sched_switch (td=0x8083e4e0, newtd=0xff0012d838c0,
flags=Variable "flags" is not available.
23 with:-
cpustop_handler () at atomic.h:285
and 16 with:-
#0 fork_trampoline () at /usr/src/s
on 14/08/2011 17:43 Steven Hartland said the following:
> - Original Message - From: "Andriy Gapon"
>>
>> Maybe test it on couple of machines first just in case I overlooked something
>> essential, although I have a report from another use that the patch didn't
>> break
>> anything for hi
13 matches
Mail list logo
