Ms. Zou | 19 Jul 15:45 2014
Picon

Spam Good-day

Good-day

My name is Ms. Zou from Taiwan, i will like to make an inquiry on your product please inform me on (minimum and
maximum order quantity and latest product catalog) Send it asap so that we can place a trial order.

Regards.
Ms. Zou
Sales manager.

Heather Walker | 13 Jul 14:55 2014

Hello..

I am Heather Walker,This is my Third Email to you,I am at the end of the
road, and about to donate a huge amount through you. I promise that your
assistance would be rewarded. Please reply back to me for more
information. Remain Blessed

Ms. Zou | 9 Jul 23:24 2014
Picon

RE

Good-day

My name is Ms. Zou from Taiwan, i will like to make an inquiry on your product please inform me on (minimum and
maximum order quantity and latest product catalog) Send it asap so that we can place a trial order.

Regards.
Ms. Zou
Sales manager.

Ib-Michael Martinsen | 6 Jul 15:06 2014
Picon

Disk Problems

Dear Community.

For some weeks my disk setup has consisted of two 2TB disk fully
allocated to NetBSD. I have created several slices of which most
are used in RAID1 configurations.

The other day I experienced a problem on the first partition(s)
(wd0a/wd1a) which are allocated to a RAID1 volume. Somehow I
had been able to allocate the raid volume too close to the
beginning of the disks, so some part of one or both mirrors were
in a disk write-protected zone.

The misplacement of the raid volume led to filesystem and
mirroring errors. The odd thing was that in the first days (or
weeks?) I did not see any errors from the raid volume. Anyway,
I solved the problem by moving the raid volume further away 
from the start of the disks.

But then I discovered a new problem I have not been able to
solve. For some reason I am unable to update the fdisk settings
on disk wd1. I would like to change the settings, so they become
identical on the two disks.

The following example shows the problem:

List the settings of wd0
------------------------
root <at> asus:/root # fdisk /dev/rwd0d
Disk: /dev/rwd0d
NetBSD disklabel disk geometry:
(Continue reading)

Fredrik Pettai | 18 Jun 11:17 2014
Picon

Re: VMware VMXNET3 driver

On Jun 9, 2014, at 13:29 , Hikaru Abe <hikaru.abe <at> gmail.com> wrote:
> Hi
> 
> I'm porting the vmx(4) driver from OpenBSD.
> Is this ok to commit?
> 
> http://www.netbsd.org/~hikaru/vmxnet3.patch

It would be nice if this could be backported to netbsd-6 as well. 

Does sys/dev/pci/if_vmx.c & sys/dev/pci/if_vmxreg.h need any adjustments for netbsd-6 ?
If not, I'll make a pull-up request...

Re,
/P
Hikaru Abe | 9 Jun 16:35 2014
Picon

Re: VMware VMXNET3 driver

2014-06-09 23:16 GMT+09:00 Joerg Sonnenberger <joerg <at> britannica.bec.de>:
> On Mon, Jun 09, 2014 at 08:29:21PM +0900, Hikaru Abe wrote:
>> I'm porting the vmx(4) driver from OpenBSD.
>> Is this ok to commit?
>
> Any reason why it is not in arch/x86?

No reason. I will move it to under sys/arch/x86/pci.

John D. Baker | 4 Jun 23:38 2014

atppc (ppbus) patches for gcc48

For anyone wanting to mess with ppbus, the atppc driver requires the
following to make gcc48 happy (set but not used):

+Index: sys/dev/ic/atppc.c
+===================================================================
+RCS file: /cvsroot/src/sys/dev/ic/atppc.c,v
+retrieving revision 1.30
+diff -u -b -r1.30 atppc.c
+--- sys/dev/ic/atppc.c	26 May 2011 02:37:25 -0000	1.30
++++ sys/dev/ic/atppc.c	12 Mar 2014 18:28:41 -0000
+ <at>  <at>  -1962,7 +1962,6  <at>  <at> 
+ static void
+ atppc_std_write(struct atppc_softc * const atppc)
+ {
+-	unsigned int timecount;
+ 	unsigned char ctr;
+ 
+ 	ctr = atppc_r_ctr(atppc);
+ <at>  <at>  -1997,7 +1996,6  <at>  <at> 
+ 		atppc_barrier_w(atppc);
+ 
+ 		/* Wait for nACK for MAXBUSYWAIT */
+-		timecount = 0;
+ 		if (atppc->sc_use & ATPPC_USE_INTR) {
+ 			atppc->sc_outerr = atppc_wait_interrupt(atppc,
+ 				&atppc->sc_out_cv, ATPPC_IRQ_nACK);

--

-- 
|/"\ John D. Baker, KN5UKS               NetBSD     Darwin/MacOS X
|\ / jdbaker[snail]mylinuxisp[flyspeck]com    OpenBSD            FreeBSD
(Continue reading)

Darren Reed | 3 Jun 15:50 2014
Picon

Simple panic with 6.1.4?

I was extracting src.tgz in a VM and thinking that it was taking too
long, opened up another window and did "mount -o async -u /".

uvm_fault(0xc0c736c0, 0xfffff000, 1) -> 0xe
fatal page fault in supervisor mode
trap type 6 code 0 eip c053913f cs 8 eflags 10283 cr2 fffffffc ilevel 0
panic: trap
cpu0: Begin traceback...
printf_nolog(c0ba9593,c781bbac,c781bbac,c053913f,8,10283,fffffffc,0,c11d3aa0,c05
4cde4) at netbsd:printf_nolog
trap_tss() at netbsd:trap_tss
--- trap via task gate ---
c11d3aa0:
cpu0: End traceback...

(gdb) where
#0  0xc05a2208 in cpu_reboot ()
#1  0xc0790ada in vpanic ()
#2  0xc0790b7f in panic ()
#3  0xc07df31c in trap ()
#4  0xc010cf48 in calltrap ()
#5  0xc781bbac in end ()
#6  0x00000010 in _KERNEL_OPT_NVCODA ()
#7  0x00000030 in _KERNEL_OPT_RASOPS_DEFAULT_HEIGHT ()
#8  0xc0b70010 in ?? ()
#9  0xc0892bf4 in wapbl_begin ()
#10 0xc0814600 in ufs_reclaim ()
#11 0xc030d2d6 in ffs_reclaim ()
#12 0xc08ac57a in VOP_RECLAIM ()
#13 0xc088efa2 in vclean ()
(Continue reading)

'Mr.Stephen Gianino' | 29 May 01:25 2014
Picon

Info, View attached!!

gmane.os.netbsd.ports.i386
Attachment (Stephen Gianino.doc): application/msword, 36 KiB
Brian Buhrow | 19 May 21:14 2014

Unable to find netbsd-INSTALL.gz in the NetBSD-5.2 installation tree.

	Hello.  I'm writing to ask what I'm sure is a very simple question,
but I'm at a complete loss as to where to find the netbsd-INSTALL.gz file
in the NetBSD-5.2 distribution tree.  I've got an old copy of the file
which I'm using to pxeboot machines for installation, but it's from the
NetBSD-5.1 distribution tree and I'd like to update it.  Unfortunately, the
file I'm actually using has been renamed, so I don't remember the source
file name.  I find it hard to believe the NetBS-5.x installation files have
changed that significantly and, indeed, I find netbsd-INSTALL.gz in the
-current distribution tree.  What am I missing?
-thanks
-Brian

Ib-Michael Martinsen | 16 May 22:47 2014
Picon

LVM on NetBSD/i386 v6.1.4

Dear list-members.

I have been trying out LVM on a vanilla NetBSD v6.1.4 installation.
So far it is looking good although I have experienced a few
problems.

For now I am able to create and use physical volumes, volume groups
and simple linear logical volumes, but whenever I try to create a
mirror LV or a snapshot LV, I get the following errors:

root:/root # lvm lvcreate -L 2g -n lv00 vg00
  Logical volume "lv00" created

root:/root # lvm lvcreate -L 2g -n lv01 -m 1 --mirrorlog core vg00
  Can't expand LV lv01: mirror target support missing from kernel?
  Aborting. Failed to activate new LV to wipe the start of it.

root:/root # lvm lvcreate -v -L 2g -n lv01 -m 1 --mirrorlog core vg00
    Setting logging type to core
    Finding volume group "vg00"
    Archiving volume group "vg00" metadata (seqno 17).
    Creating logical volume lv01
    Creating logical volume lv01_mimage_0
    Creating logical volume lv01_mimage_1
    Creating volume group backup "/etc/lvm/backup/vg00" (seqno 18).
    Found volume group "vg00"
  Can't expand LV lv01: mirror target support missing from kernel?
  Aborting. Failed to activate new LV to wipe the start of it.
    Found volume group "vg00"
    Found volume group "vg00"
(Continue reading)


Gmane