On 03/23/12 04:46, Thomas Schmitt wrote:
Hi,
The trick is called "isohybrid".
Luigi Rizzo wrote:
interesting. It does work for me indeed.
So why not for Da Rock ?
Starting to feel left out here :)
I tried with your flags to dd (as opposed to those on Ubuntu - bs=1m -
not that I thought i
On Thu, Mar 22, 2012 at 16:24:16 +0100, Jake Smith wrote:
> Hello,
>
> I am trying to get the latest mps(4) driver in FreeBSD 9-STABLE working
> with am LSI SAS2008 variant from ASUS, they call it PIKE 2008/IMR. Link
> http://www.asus.com/Server_Workstation/Accessories/PIKE_2008IMR/
>
> From wh
On Thu, 22 Mar 2012 22:38:15 +0200 Mikolaj Golub wrote:
MG> Actually I don't see reasons why this may not be p_cansee, so I
MG> updated the patch and going to commit it if there is no objections.
The updated patch:
http://people.freebsd.org/~trociny/kern_proc_osrel.2.patch
--
Mikolaj Golub
On Sat, Mar 17, 2012 at 9:30 PM, Mikolaj Golub wrote:
> Hi,
>
> Currently we can check and change binary osreldate of another process via
> procfs(5).
>
> Kostik suggested to add a new sysctl for the same purpose and also extend
> procstat to show osrel.
>
> Here are patches I am going to commit i
Here is some code which fails with malloc < 1 page
and sometimes succeeds with large mallocs (> 16 pages)
What's wrong?
#include
#include
#include
#include
#include
#include
#include
#include
#include
// Copyright: skeleton took from an older post on the freebsd list
#include
#include
> If your kernel module creates a device in /dev that implements the
> mmap method, then you don't need to worry about mucking around with
> vm_maps and objects and whatnot. Your mmap method just needs to be
> able to convert offsets into the device into physical memory
> addresses,
Yes I'm aware
On Thu, Mar 22, 2012 at 10:42 AM, Eric Saint-Etienne
wrote:
> Actually when using kernel_map, the object returned is NULL! However the
> the vm_entry_t it returns seems a valid address, its 'object' field is NULL
> too (that's consistent)
> That's the reason why I didn't find it in any existing 'p
Hi,
> > The trick is called "isohybrid".
Luigi Rizzo wrote:
> interesting. It does work for me indeed.
So why not for Da Rock ?
> And it might be a nice trick for our images too, so we don't
> have to build a memstick and an ISO image...
I would be happy to help with that.
I am the developer
On Thu, Mar 22, 2012 at 8:03 AM, John Baldwin wrote:
> On Wednesday, March 21, 2012 4:20:17 pm Mark Saad wrote:
>> On Wed, Mar 21, 2012 at 12:39 PM, Sergey Kandaurov wrote:
>> > On 21 March 2012 19:19, John Baldwin wrote:
>> >> On Tuesday, March 20, 2012 11:37:57 am Sergey Kandaurov wrote:
>> >>
On Thu, Mar 22, 2012 at 05:42:27PM +0100, Thomas Schmitt wrote:
> Hi,
>
> Vitaly Magerya :
> > > you might want to try to dd the iso image directly onto USB instead; there
> > > where talks that Ubuntu would support this starting at 11.10.
>
> Da Rock :
> > Nada. Tried that and it didn't work. I'
Hello,
I am trying to get the latest mps(4) driver in FreeBSD 9-STABLE working
with am LSI SAS2008 variant from ASUS, they call it PIKE 2008/IMR. Link
http://www.asus.com/Server_Workstation/Accessories/PIKE_2008IMR/
From what I can see this card should be compatible with the mps(4)
driver MF
Hi,
Vitaly Magerya :
> > you might want to try to dd the iso image directly onto USB instead; there
> > where talks that Ubuntu would support this starting at 11.10.
Da Rock :
> Nada. Tried that and it didn't work. I'm not sure how that would work given
> that it uses isolinux to boot- ergo needs
On Thu, Mar 22, 2012 at 3:15 AM, Luigi Rizzo wrote:
> On Wed, Mar 21, 2012 at 10:52:53AM -0500, Mark Felder wrote:
>> As an alternative I recently purchased a Zalman ZM-VE200 device (there's
>> also a USB3.0 flavor) that lets you copy ISOs to it and it will emulate a
>> CDROM/DVDROM/BDROM for you
> By using kernel_map instead of kmem_map, vm_map_lookup() now always
> return a vm_object. That's a big progress.
> As expected, when this object is kmem_object, the user mapping works
> fine (for smaller or larger mallocs.)
>
> Otherwise that object doesn't match kernel_object. It's an anonymous
Hi,
On 22 March 2012 05:13, John Baldwin wrote:
> s/fixed/mostly worked around/
>
> The problem is that the work around isn't perfect. The root cause is still
> not fixed. avg@ has some ideas on better ways to handle this, but it is a bit
> tricky to get this right since we also dont' want pri
On 03/21/12 23:34, Andrzej Tobola wrote:
On Wed, Mar 21, 2012 at 11:16:59PM +1000, Da Rock wrote:
On 03/21/12 23:06, Matthias Apitz wrote:
Hello,
I've forwarded your question to a colleague who is an Ubuntu fan and he
replied, that the creation of a booting Ubuntu USB key is possile with
Ubunt
On Thursday, March 22, 2012 6:10:41 am Alexander Best wrote:
> hi there,
>
> a few years ago there were huge issues with SMP and dmesg output, where
> messages from various drivers were output to /dev/ttyv0 without any timing,
> which caused a lot of unreadable lines.
>
> this was fixed and almos
On Wednesday, March 21, 2012 7:27:58 pm Eric Saint-Etienne wrote:
> Hi,
>
> >From within the freeBSD kernel, not all malloc are made equal:
> * malloc() smaller than KMEM_ZMAX (set to one page size) end up in
> UMA SLABs, themselves laid out in powers of 2 (from 16 bytes, 32... to
> 4096 byt
On Wednesday, March 21, 2012 4:20:17 pm Mark Saad wrote:
> On Wed, Mar 21, 2012 at 12:39 PM, Sergey Kandaurov wrote:
> > On 21 March 2012 19:19, John Baldwin wrote:
> >> On Tuesday, March 20, 2012 11:37:57 am Sergey Kandaurov wrote:
> >>> On 22 November 2011 19:29, Mark Saad wrote:
> >>> > Hello
On Wed, Mar 21, 2012 at 04:35:13PM -0700, Sushanth Rai wrote:
> Sometimes I have trouble capturing the "correct" state of a
> multithreaded process using gcore. That is, it looks like target
> process might have done some work since the time command was issued
> and the core file was generated.
>
>
I've refined the behaviour I observe, which isn't consistent depending
on the size one mallocates.
(see interleaved comments)
> In my driver, I need to map some malloc-ed memory, obtained from
> another module, into userspace.
>
> The problem: on the smaller mallocs, as well as on some bigeer ones
On 22/03/12 12:15 +0100, Luigi Rizzo wrote:
> On Wed, Mar 21, 2012 at 10:52:53AM -0500, Mark Felder wrote:
> > As an alternative I recently purchased a Zalman ZM-VE200 device (there's
> > also a USB3.0 flavor) that lets you copy ISOs to it and it will emulate a
> > CDROM/DVDROM/BDROM for you so
On Wed, Mar 21, 2012 at 10:52:53AM -0500, Mark Felder wrote:
> As an alternative I recently purchased a Zalman ZM-VE200 device (there's
> also a USB3.0 flavor) that lets you copy ISOs to it and it will emulate a
> CDROM/DVDROM/BDROM for you so you never have to deal with this mess again.
> It
hi there,
a few years ago there were huge issues with SMP and dmesg output, where
messages from various drivers were output to /dev/ttyv0 without any timing,
which caused a lot of unreadable lines.
this was fixed and almost all of the dmesg lines i see now look similar to
dmesg on a non-SMP aware
On Wed, Mar 21, 2012 at 11:11:42PM +1000, Da Rock wrote:
...
> In the meantime I think I may have stumbled on the solution to the
> script: In the midst of all the output it mentions "usage realpath [-q]
> path". I wasn't 100% sure exactly what that meant, but I put the full
> path to the iso an
25 matches
Mail list logo
