In article <[EMAIL PROTECTED]> you write:
>On Fri, Jul 13, 2007 at 10:46:04PM +0200, Juergen Lock wrote:
>> Okay what do you guys think about the following patch for now:
>> (the SMP thing might actually be the cause for ports/113430, can
>> someone verify?)
>
>I wonder if perhaps the port should
On Fri, Jul 13, 2007 at 10:46:04PM +0200, Juergen Lock wrote:
> Okay what do you guys think about the following patch for now:
> (the SMP thing might actually be the cause for ports/113430, can
> someone verify?)
I wonder if perhaps the port should be marked NO_PACKAGE, since quite a
bit depends
On 07/13/07 15:46, Juergen Lock wrote:
On Thu, Jul 12, 2007 at 01:07:50PM -0500, Craig Boston wrote:
On Thu, Jul 12, 2007 at 12:52:52PM -0500, Craig Boston wrote:
For some reason when the ioctl is issued, curproc points to a totally
bogus proc structure. curthread seems to be sane as far as I
On Thu, Jul 12, 2007 at 01:07:50PM -0500, Craig Boston wrote:
> On Thu, Jul 12, 2007 at 12:52:52PM -0500, Craig Boston wrote:
> > For some reason when the ioctl is issued, curproc points to a totally
> > bogus proc structure. curthread seems to be sane as far as I can tell,
> > but the process it
2007/7/12, Craig Boston <[EMAIL PROTECTED]>:
On Thu, Jul 12, 2007 at 12:52:52PM -0500, Craig Boston wrote:
> For some reason when the ioctl is issued, curproc points to a totally
> bogus proc structure. curthread seems to be sane as far as I can tell,
> but the process it claims to belong to is
On 7/12/07, Craig Boston <[EMAIL PROTECTED]> wrote:
Aha! The problem isn't that curproc is garbage, but rather that it's
being interpreted wrong.
struct proc has some extra fields when KSE is #defined. KSE recently
became a kernel option and was put in the DEFAULTS file, so everyone's
kernel h
On Thursday 12 July 2007 02:30:51 pm Eric Anderson wrote:
> Craig Boston wrote:
> > On Thu, Jul 12, 2007 at 12:52:52PM -0500, Craig Boston wrote:
> >> For some reason when the ioctl is issued, curproc points to a totally
> >> bogus proc structure. curthread seems to be sane as far as I can tell,
>
Craig Boston wrote:
On Thu, Jul 12, 2007 at 12:52:52PM -0500, Craig Boston wrote:
For some reason when the ioctl is issued, curproc points to a totally
bogus proc structure. curthread seems to be sane as far as I can tell,
but the process it claims to belong to is full of junk.
Aha! The prob
On Mon, Jul 09, 2007 at 11:49:33PM +0200, Juergen Lock wrote:
> In article <[EMAIL PROTECTED]> you write:
> >2007/7/9, Doug Rabson <[EMAIL PROTECTED]>:
> >> On Monday 09 July 2007, Attilio Rao wrote:
> >> > Please also note that stack here seems highly corrupted since values
> >> > passed to _vm_ma
On Thu, Jul 12, 2007 at 12:52:52PM -0500, Craig Boston wrote:
> For some reason when the ioctl is issued, curproc points to a totally
> bogus proc structure. curthread seems to be sane as far as I can tell,
> but the process it claims to belong to is full of junk.
Aha! The problem isn't that cur
In article <[EMAIL PROTECTED]> you write:
>2007/7/9, Doug Rabson <[EMAIL PROTECTED]>:
>> On Monday 09 July 2007, Attilio Rao wrote:
>> > 2007/7/9, Eric Anderson <[EMAIL PROTECTED]>:
>> > > Fatal trap 12: page fault while in kernel mode
>> > > cpuid = 0; apic id = 00
>> > > fault virtual address =
In article <[EMAIL PROTECTED]> you write:
>Eric Anderson wrote:
>> On 07/09/07 09:28, Attilio Rao wrote:
>>> Eric Anderson wrote:
On 07/09/07 08:00, Eric Anderson wrote:
> Juergen Lock wrote:
>> On Sun, Jul 08, 2007 at 01:15:35PM -0500, Eric Anderson wrote:
>>> On 07/07/07 09:02, J
Eric Anderson wrote:
On 07/09/07 08:00, Eric Anderson wrote:
Juergen Lock wrote:
On Sun, Jul 08, 2007 at 01:15:35PM -0500, Eric Anderson wrote:
On 07/07/07 09:02, Juergen Lock wrote:
In article <[EMAIL PROTECTED]> you write:
On 07/05/07 22:31, Eric Anderson wrote:
[...]
Although now I have t
On 07/09/07 08:00, Eric Anderson wrote:
Juergen Lock wrote:
On Sun, Jul 08, 2007 at 01:15:35PM -0500, Eric Anderson wrote:
On 07/07/07 09:02, Juergen Lock wrote:
In article <[EMAIL PROTECTED]> you write:
On 07/05/07 22:31, Eric Anderson wrote:
[...]
Although now I have the issue where using k
Juergen Lock wrote:
On Sun, Jul 08, 2007 at 01:15:35PM -0500, Eric Anderson wrote:
On 07/07/07 09:02, Juergen Lock wrote:
In article <[EMAIL PROTECTED]> you write:
On 07/05/07 22:31, Eric Anderson wrote:
[...]
Although now I have the issue where using kqemu-kmod causes my system to
reboot
On Sun, Jul 08, 2007 at 01:15:35PM -0500, Eric Anderson wrote:
> On 07/07/07 09:02, Juergen Lock wrote:
>> In article <[EMAIL PROTECTED]> you write:
>>> On 07/05/07 22:31, Eric Anderson wrote:
>>>[...]
>>> Although now I have the issue where using kqemu-kmod causes my system to
>>> reboot or powe
On 07/07/07 09:02, Juergen Lock wrote:
In article <[EMAIL PROTECTED]> you write:
On 07/05/07 22:31, Eric Anderson wrote:
On 07/02/07 15:30, Juergen Lock wrote:
Looks like its time for this again... Many bugs have been fixed,
some features have been added, like, qemu-system-arm has grown
emula
In article <[EMAIL PROTECTED]> you write:
>On 07/05/07 22:31, Eric Anderson wrote:
>> On 07/02/07 15:30, Juergen Lock wrote:
>>> Looks like its time for this again... Many bugs have been fixed,
>>> some features have been added, like, qemu-system-arm has grown
>>> emulation of a few PDAs like some
In article <[EMAIL PROTECTED]> you write:
>0n Thu, Jul 05, 2007 at 10:31:29PM -0500, Eric Anderson wrote:
>
>>On 07/02/07 15:30, Juergen Lock wrote:
>>> Looks like its time for this again... Many bugs have been fixed,
>>> some features have been added, like, qemu-system-arm has grown
>>>
On 07/05/07 22:31, Eric Anderson wrote:
On 07/02/07 15:30, Juergen Lock wrote:
Looks like its time for this again... Many bugs have been fixed,
some features have been added, like, qemu-system-arm has grown
emulation of a few PDAs like some Zaurus models, etc. As always,
please test now, befor
0n Thu, Jul 05, 2007 at 10:31:29PM -0500, Eric Anderson wrote:
>On 07/02/07 15:30, Juergen Lock wrote:
>> Looks like its time for this again... Many bugs have been fixed,
>> some features have been added, like, qemu-system-arm has grown
>> emulation of a few PDAs like some Zaurus models,
On 07/02/07 15:30, Juergen Lock wrote:
Looks like its time for this again... Many bugs have been fixed,
some features have been added, like, qemu-system-arm has grown
emulation of a few PDAs like some Zaurus models, etc. As always,
please test now, before I commit this, so we won't be in for
na
Looks like its time for this again... Many bugs have been fixed,
some features have been added, like, qemu-system-arm has grown
emulation of a few PDAs like some Zaurus models, etc. As always,
please test now, before I commit this, so we won't be in for
nasty surprises afterwards...
Thanx & enj
On 04/05/07 16:03, Juergen Lock wrote:
Hi!
There have been a few interesting commits to qemu cvs, like,
a qcow2 corruption bugfix, vmware vga emulation (-vmwarevga), and
several emulated eepro100 (fxp) nic variants (-net nic,model=i82557b
-net user worked for me with FreeBSD and linux guests, a
On 04/05/07 16:03, Juergen Lock wrote:
Hi!
There have been a few interesting commits to qemu cvs, like,
a qcow2 corruption bugfix, vmware vga emulation (-vmwarevga), and
several emulated eepro100 (fxp) nic variants (-net nic,model=i82557b
-net user worked for me with FreeBSD and linux guests, a
Hi!
There have been a few interesting commits to qemu cvs, like,
a qcow2 corruption bugfix, vmware vga emulation (-vmwarevga), and
several emulated eepro100 (fxp) nic variants (-net nic,model=i82557b
-net user worked for me with FreeBSD and linux guests, and seemed even
slightly faster than the r
On 03/03/07 13:32, Juergen Lock wrote:
In article <[EMAIL PROTECTED]> [EMAIL PROTECTED] (Eric Anderson)writes:
On 02/24/07 13:27, Juergen Lock wrote:
On Sat, Feb 24, 2007 at 08:17:23PM +0100, Juergen Lock wrote:
In article <[EMAIL PROTECTED]> you write:
Is anyone else experiencing a nearly us
In article <[EMAIL PROTECTED]> [EMAIL PROTECTED] (Eric Anderson)writes:
>On 02/24/07 13:27, Juergen Lock wrote:
>> On Sat, Feb 24, 2007 at 08:17:23PM +0100, Juergen Lock wrote:
>>> In article <[EMAIL PROTECTED]> you write:
Is anyone else experiencing a nearly useless qemu experience with the
28 matches
Mail list logo