From devnull at illumos.org  Sun Sep  4 07:10:01 2011
From: devnull at illumos.org (illumos project)
Date: Sun, 4 Sep 2011 07:10:01 +0000
Subject: [Illumos-team] [OpenIndiana Distribution - Bug #1329] cant run /
	boot - openindiana from flash usb stick
References: <redmine.issue-1329.20110802200201@illumos.org>
Message-ID: <redmine.journal-3598.20110904071001@illumos.org>


Issue #1329 has been updated by Ryo Murakawa.

Assignee changed from Ryo Murakawa to OI illumos

Sorry for lately processing.
I think this is same of #1148. So I move this to OI illumos.
----------------------------------------
Bug #1329: cant run / boot - openindiana from flash usb stick
https://www.illumos.org/issues/1329

Author: Sam Gridley
Status: New
Priority: Normal
Assignee: OI illumos
Category: 
Target version: 
Difficulty: Medium
Tags: compactflush


I initially tried to install the desktop version of OI on a 16G usb flash device which did not go well... the entire (default) install of the OI desktop 148 took more than 12 hours to get it on the stick.  I was able to boot freeNAS off of the same stick yesterday as well as a few other OS's. Also when OI was finally installed - i waited some 30 minutes for it to boot up - all the time it appeared to be doing something (with the OI logo and the red 'progress'(?) bar, going back and forth). And again after say 30 min i cycled the power to track down a sata controller and extra disk. Has anyone tried running OpenIndiana off of flash. I am now using a SATA disk. but how and who do i notify to have them look into this problem / possible bug? 

if you need more info feel free to contact me..


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://www.illumos.org/my/account


From devnull at illumos.org  Tue Sep  6 02:59:42 2011
From: devnull at illumos.org (illumos project)
Date: Tue, 6 Sep 2011 02:59:42 +0000
Subject: [Illumos-team] [OpenIndiana Distribution - Bug #736] root crontab
	does not survive reboot
References: <redmine.issue-736.20110217011342@illumos.org>
Message-ID: <redmine.journal-3644.20110906025942@illumos.org>


Issue #736 has been updated by Ken Mays.

Due date set to 2011-09-14
Category set to OS/Net (Kernel and Userland)
Assignee set to OI illumos
Target version set to oi_151_stable
Estimated time set to 8.00


----------------------------------------
Bug #736: root crontab does not survive reboot
https://www.illumos.org/issues/736

Author: N2Deep N2Deep
Status: Feedback
Priority: High
Assignee: OI illumos
Category: OS/Net (Kernel and Userland)
Target version: oi_151_stable
Difficulty: Medium
Tags: SMF


Making changes to a B148 root crontab is pointless if you reboot the machine. Your changes will be overwritten at the next reboot. After every reboot, the root crontab will look like it did after the initial B148 installation. I have confirmed this on two separate B148 desktop installs.

User crontabs seem to survive reboots.


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://www.illumos.org/my/account


From devnull at illumos.org  Tue Sep  6 03:11:48 2011
From: devnull at illumos.org (illumos project)
Date: Tue, 6 Sep 2011 03:11:48 +0000
Subject: [Illumos-team] [OpenIndiana Distribution - Bug #1404] Can't boot
	Openindiana b151 paravirtual guest on xen/xvm when using
	boot_archive from fresh install
References: <redmine.issue-1404.20110823105831@illumos.org>
Message-ID: <redmine.journal-3646.20110906031148@illumos.org>


Issue #1404 has been updated by Ken Mays.

Due date set to 2011-09-14
Category set to OS/Net (Kernel and Userland)
Assignee set to OI illumos
Estimated time set to 40.00


----------------------------------------
Bug #1404: Can't boot Openindiana b151 paravirtual guest on xen/xvm when using boot_archive from fresh install
https://www.illumos.org/issues/1404

Author: Florian Manschwetus
Status: In Progress
Priority: Normal
Assignee: OI illumos
Category: OS/Net (Kernel and Userland)
Target version: oi_151_stable
Difficulty: Medium
Tags: needs-triage


When using boot_archive from livecd (text here, as a pv guest needs not really a gui), it works so far (some trouble with secondary zfs-pool as system id changes), with any kernel (installed as well the one from install-media).
When using the installed boot_archive, the following error occurs on booting the guest:

<pre>
xl create -c openindiana
Parsing config file openindiana
Daemon running with PID 2634
                            v4.1.1 chgset 'unavailable'
OpenIndiana Build oi_151 64-bit (illumos a4e1558c0599)
SunOS Release 5.11 - Copyright 1983-2010 Oracle and/or its affiliates.
All rights reserved. Use is subject to license terms.

panic[cpu0]/thread=fffffffffbc609e0: BAD TRAP: type=e (#pf Page fault) rp=fffffffffbcb42d0 addr=fffffe00041ed840

#pf Page fault
Bad kernel fault at addr=0xfffffe00041ed840
pid=0, pc=0xfffffffffb8c03f3, sp=0xfffffffffbcb43c8, eflags=0x10246
cr0: 8005003b<pg,wp,ne,et,ts,mp,pe> cr4: 2660<vmxe,xmme,fxsr,mce,pae>
cr2: fffffe00041ed840
        rdi: fffffe00041ed840 rsi:                0 rdx:        10a559273
        rcx:                3  r8:                0  r9: ffffff00c6708000
        rax:                0 rbx:        10a559273 rbp: fffffffffbcb4460
        r10: ffffff00c554b000 r11: ffffff0000000000 r12:                0
        r13:                1 r14: fffffe00041ed840 r15:        10a559273
        fsb:        200000000 gsb: fffffffffbc61c20  ds:                0
         es:                0  fs:                0  gs:                0
        trp:                e err:                3 rip: fffffffffb8c03f3
         cs:             e030 rfl:            10246 rsp: fffffffffbcb43c8
         ss:             e02b

Warning - stack not written to the dump buffer
fffffffffbcb41b0 unix:die+10f ()
fffffffffbcb42c0 unix:trap+17af ()
fffffffffbcb42d0 unix:cmntrap+12b ()
fffffffffbcb4460 unix:atomic_cas_64+3 ()
fffffffffbcb4500 unix:hati_pte_map+18c ()
fffffffffbcb4580 unix:hati_load_common+15d ()
fffffffffbcb4640 unix:hat_devload+198 ()
fffffffffbcb46a0 unix:kmem_override_cache_attrs+be ()
fffffffffbcb4720 unix:i_ddi_mem_alloc+1a4 ()
fffffffffbcb47e0 genunix:ddi_dma_mem_alloc+1a3 ()
fffffffffbcb48a0 unix:xvdi_alloc_ring+d4 ()
fffffffffbcb48f0 xdf:xdf_setstate_init+f5 ()
fffffffffbcb4980 xdf:xdf_attach+387 ()
fffffffffbcb49e0 genunix:devi_attach+80 ()
fffffffffbcb4a10 genunix:attach_node+95 ()
fffffffffbcb4a50 genunix:i_ndi_config_node+c4 ()
fffffffffbcb4a70 genunix:i_ddi_attachchild+40 ()
fffffffffbcb4ab0 genunix:devi_attach_node+ac ()
fffffffffbcb4b10 genunix:ndi_devi_online+c7 ()
fffffffffbcb4bd0 unix:xvdi_create_dev+258 ()
fffffffffbcb4c40 xpvd:xpvd_bus_config+91 ()
fffffffffbcb4cc0 genunix:ndi_devi_config_one+bd ()
fffffffffbcb4d70 genunix:resolve_pathname+19c ()
fffffffffbcb4dd0 genunix:ldi_vp_from_name+ef ()
fffffffffbcb4e40 genunix:ldi_open_by_name+57 ()
fffffffffbcb4ed0 zfs:vdev_disk_read_rootlabel+a0 ()
fffffffffbcb4f20 zfs:spa_generate_rootconf+26 ()
fffffffffbcb4f90 zfs:spa_import_rootpool+31 ()
fffffffffbcb4ff0 zfs:zfs_mountroot+eb ()
fffffffffbcb5010 genunix:fsop_mountroot+1a ()
fffffffffbcb5040 genunix:rootconf+133 ()
fffffffffbcb5080 genunix:vfs_mountroot+63 ()
fffffffffbcb50b0 genunix:main+136 ()
fffffffffbcb50c0 unix:_locore_start+7e ()

skipping system dump - no dump device configured
rebooting...
</pre>


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://www.illumos.org/my/account


From devnull at illumos.org  Tue Sep  6 03:20:28 2011
From: devnull at illumos.org (illumos project)
Date: Tue, 6 Sep 2011 03:20:28 +0000
Subject: [Illumos-team] [OpenIndiana Distribution - Bug #1025] (Closed) GRUB
	loading failure
References: <redmine.issue-1025.20110512130748@illumos.org>
Message-ID: <redmine.journal-3648.20110906032028@illumos.org>


Issue #1025 has been updated by Ken Mays.

Due date set to 2011-09-14
Category set to OS/Net (Kernel and Userland)
Status changed from Feedback to Closed
Assignee set to OI illumos
Target version set to oi_151_stable
Estimated time set to 40.00

Please refile this bug in the Illumos_gate bug tracker. This issue not handled by the OI-dev team.
----------------------------------------
Bug #1025: GRUB loading failure
https://www.illumos.org/issues/1025

Author: Artem  D
Status: Closed
Priority: Normal
Assignee: OI illumos
Category: OS/Net (Kernel and Userland)
Target version: oi_151_stable
Difficulty: Medium
Tags: grub


System Configuration: Gigabyte Technology Co., Ltd. GA-790XT-USB3
BIOS Configuration: Award Software International, Inc. F5a 09/23/2010

==== Processor Sockets ====================================

Version                          Location Tag
-------------------------------- --------------------------
AMD Athlon(tm) II X4 615e Processor Socket M2

==== Memory Device Sockets ================================

Type        Status Set Device Locator      Bank Locator
----------- ------ --- ------------------- ----------------
unknown     in use 0   A0                  Bank0/1
unknown     in use 0   A1                  Bank2/3
unknown     in use 0   A2                  Bank4/5
unknown     in use 0   A3                  Bank6/7

==== On-Board Devices =====================================

==== Upgradeable Slots ====================================

ID  Status    Type             Description
--- --------- ---------------- ----------------------------
7   available PCI              PCI
6   available PCI              PCI
8   available PCI              PCI
0   unknown   PCI Express      PCI Express x16
0   unknown   PCI Express      PCI Express x16
0   unknown   PCI Express      PCI Express x1
0   unknown   PCI Express      PCI Express x1

prtconf: see file attached


cfgadm -al
Ap_Id                          Type         Receptacle   Occupant     Condition
sata0/0                        sata-port    empty        unconfigured ok
sata0/1                        sata-port    empty        unconfigured ok
sata0/2                        sata-port    empty        unconfigured ok
sata0/3                        sata-port    empty        unconfigured ok
sata0/4::dsk/c1t4d0            disk         connected    configured   ok
sata0/5                        sata-port    empty        unconfigured ok
sata1/0::dsk/c3t0d0            disk         connected    configured   ok
sata1/1::dsk/c3t1d0            disk         connected    configured   ok
sata2/0::dsk/c4t0d0            disk         connected    configured   ok
sata2/1::dsk/c4t1d0            disk         connected    configured   ok

Boot disk:
sata0/4::dsk/c1t4d0

RAIDZ disks:
sata1/0::dsk/c3t0d0            disk         connected    configured   ok
sata1/1::dsk/c3t1d0            disk         connected    configured   ok
sata2/0::dsk/c4t0d0            disk         connected    configured   ok
sata2/1::dsk/c4t1d0            disk         connected    configured   ok

Boot disk is connected to the motherboard.
4 Raid-z disks are connected to 2 SATA cards (si3124) in pci-e slots:
PCIEX1_1 (channel 0 and channel 1) and PCIEX1_2 (channel 0 and channel 1)

BIOS initializes PCIEX1_1 then PCIEX1_2 first, and on-board SATA last.
There is no way to change the order.

In BIOS disks are recognized as:
boot disk - SCSI-4

raidz disks - SCSI-0, SCSI-1, SCSI-2, SCSI-3

When raidz disks are inserted, GRUB stage2 load fails.

Loading operating system...
GRUB Loading stage2...

and that's all.

All possible combinations:
1. PCIEX1_1 ch 0 & ch 1 occupied
    PCIEX1_2 ch 0 & ch 1 empty
    Result: Boot succeed.

2. PCIEX1_1 ch 0 & ch 1 empty
    PCIEX1_2 ch 0 & ch 1 occupied
    Result: Boot succeed.

3. PCIEX1_1 ch 0 occupied, ch 1 empty
    PCIEX1_2 ch 0 occupied, ch 1 empty
    Result: GRUB stage2 load failure

4. PCIEX1_1 ch 0 empty, ch 1 occupied
    PCIEX1_1 ch 0 empty, ch 1 occupied
    Result: GRUB stage2 load failure

5. PCIEX1_1 ch 0 empty, ch 1 occupied
    PCIEX1_1 ch 0 occupied, ch 1 empty
    Result: GRUB load failure
    Console output: Loading Operating System...
                            GRUB Loading stage2...
                            GRUB GRUB
6. PCIEX1_1 ch 0 occupied, ch 1 empty
    PCIEX1_1 ch 0 empty, ch 1 occupied
    Result: GRUB load failure
    Console output: Loading Operating System...
                            GRUB Loading stage2...
                            GRUB
     
Boot order is set properly in BIOS


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://www.illumos.org/my/account


From devnull at illumos.org  Tue Sep  6 03:28:39 2011
From: devnull at illumos.org (illumos project)
Date: Tue, 6 Sep 2011 03:28:39 +0000
Subject: [Illumos-team] [OpenIndiana Distribution - Feature #286] Default
	ulmits should be upped
References: <redmine.issue-286.20100930101339@illumos.org>
Message-ID: <redmine.journal-3652.20110906032838@illumos.org>


Issue #286 has been updated by Ken Mays.

Due date set to 2011-09-14
Assignee set to OI illumos
Estimated time set to 8.00


----------------------------------------
Feature #286: Default ulmits should be upped
https://www.illumos.org/issues/286

Author: Alasdair Lumsden
Status: Feedback
Priority: Low
Assignee: OI illumos
Category: OS/Net (Kernel and Userland)
Target version: oi_151_stable
Difficulty: Medium
Tags: needs-triage


<pre>
root ~ (pkgdev.openindiana): ulimit -a
core file size          (blocks, -c) unlimited
data seg size           (kbytes, -d) unlimited
file size               (blocks, -f) unlimited
open files                      (-n) 256
pipe size            (512 bytes, -p) 10
stack size              (kbytes, -s) 10240
cpu time               (seconds, -t) unlimited
max user processes              (-u) 29995
virtual memory          (kbytes, -v) unlimited
</pre>

Thankfully it is no longer 1988. So I'd propose the conservative open files limit be upped to something more sane, such as 32768 (or 1024 at an absolute minimum).

256 is very low and encountered quickly.


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://www.illumos.org/my/account


From devnull at illumos.org  Tue Sep  6 03:42:43 2011
From: devnull at illumos.org (illumos project)
Date: Tue, 6 Sep 2011 03:42:43 +0000
Subject: [Illumos-team] [OpenIndiana Distribution - Bug #661] (Closed) IBM
	Model M Keyboard Support
References: <redmine.issue-661.20110124145537@illumos.org>
Message-ID: <redmine.journal-3653.20110906034243@illumos.org>


Issue #661 has been updated by Ken Mays.

Due date set to 2011-09-14
Category set to OS/Net (Kernel and Userland)
Status changed from New to Closed
Assignee set to OI illumos
Target version set to oi_151_stable
Estimated time set to 1.00
Difficulty set to Medium
Tags set to needs-triage

+1 per Guido's statement (I have these keyboards as well). Closing ticket.
----------------------------------------
Bug #661: IBM Model M Keyboard Support
https://www.illumos.org/issues/661

Author: Justin Hannah
Status: Closed
Priority: Low
Assignee: OI illumos
Category: OS/Net (Kernel and Userland)
Target version: oi_151_stable
Difficulty: Medium
Tags: needs-triage


http://www.wotwefink.net/forums/showthread.php?t=8059

I have a lot of these Model M PS/2 keyboards and they actually are still manufactured by Unicomp at www.pckeyboard.com

Unfortunately they quit working with OpenSolaris and Solaris 10 several years ago.  The num lock light comes on but even when plugged into a USB-PS/2 adapter they do not work in a text console even.  Can anybody give me pointers on commands to run to dump information you need to fix this bug.   It would be great if they worked in OpenIndiana.  Thanks.



-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://www.illumos.org/my/account


From devnull at illumos.org  Tue Sep  6 03:51:17 2011
From: devnull at illumos.org (illumos project)
Date: Tue, 6 Sep 2011 03:51:17 +0000
Subject: [Illumos-team] [OpenIndiana Distribution - Bug #304] Networking
	problems with oi_147 under VMware Workstation
References: <redmine.issue-304.20101006011017@illumos.org>
Message-ID: <redmine.journal-3657.20110906035117@illumos.org>


Issue #304 has been updated by Ken Mays.

Category set to OS/Net (Kernel and Userland)
Assignee set to OI illumos
Estimated time changed from 8.00 to 40.00


----------------------------------------
Bug #304: Networking problems with oi_147 under VMware Workstation
https://www.illumos.org/issues/304

Author: Brian Bienvenu
Status: Feedback
Priority: Low
Assignee: OI illumos
Category: OS/Net (Kernel and Userland)
Target version: oi_151_stable
Difficulty: Medium
Tags: dhcp


Doing a live-boot with oi_147 under VMware Workstation (I've tried 7.0.1 and 7.1.1) causes NWAM to get exceptionally confused, as per http://img842.imageshack.us/img842/5489/badoi.png

The system gets a DHCP lease, then decides the network device has been unplugged, then repeats this every 10 seconds or so.

OpenSolaris 134 works fine, doing the same thing. (ie it gets and keeps a DHCP lease).

I was running VMware with most everything on default, except the networking set to "bridged", from the default of "NAT".


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://www.illumos.org/my/account


From devnull at illumos.org  Tue Sep  6 03:53:35 2011
From: devnull at illumos.org (illumos project)
Date: Tue, 6 Sep 2011 03:53:35 +0000
Subject: [Illumos-team] [OpenIndiana Distribution - Bug #560] (Resolved)
	nwamd - unable to assign static IPv6 address as stated in manual
References: <redmine.issue-560.20101219040432@illumos.org>
Message-ID: <redmine.journal-3658.20110906035335@illumos.org>


Issue #560 has been updated by Ken Mays.

Due date set to 2011-09-14
Category set to Documentation
Status changed from New to Resolved
Assignee set to OI illumos
Target version set to oi_151_stable
% Done changed from 0 to 100
Estimated time set to 8.00
Difficulty set to Medium
Tags set to needs-triage

Manual updates done by Illumos_gate team.
----------------------------------------
Bug #560: nwamd - unable to assign static IPv6 address as stated in manual
https://www.illumos.org/issues/560

Author: N2Deep N2Deep
Status: Resolved
Priority: Low
Assignee: OI illumos
Category: Documentation
Target version: oi_151_stable
Difficulty: Medium
Tags: needs-triage


After installing b148-text the nwamd manual states:

"A static IP address can be configured by changing the line in /etc/nwam/llp file that contains an interface name and the name of the method for obtaining an IP address...
...An optional static IPv6 address can be provided on the same line, immediately after the ipv6 token. Whether you provide a static address or not, IPv6 will use DHCPv6 or stateless address configuration, as directed by the local network configuration."

My local network runs stateless. Note that nwamd configures a stateless address just fine on this machine and I can ping/traceroute public addresses, etc, but the static address stated in /etc/nwam/llp is not listed by ipadm or ifconfig in addition to the stateless address.  Also this machine has another unconfigured wired network adapter, if it matters.

/etc/nwam/llp:
e1000g1 ipv6 <static-ipv6-address>


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://www.illumos.org/my/account


From devnull at illumos.org  Tue Sep  6 06:28:30 2011
From: devnull at illumos.org (illumos project)
Date: Tue, 6 Sep 2011 06:28:30 +0000
Subject: [Illumos-team] [OpenIndiana Distribution - Bug #993] (Closed)
	Marvell SATA controller 88SE9128 - driver issue?
References: <redmine.issue-993.20110505194142@illumos.org>
Message-ID: <redmine.journal-3681.20110906062830@illumos.org>


Issue #993 has been updated by Ken Mays.

Due date set to 2011-09-14
Category set to Drivers
Status changed from New to Closed
Assignee changed from OI Caiman to OI illumos
Target version set to oi_151_stable
Estimated time set to 40.00

Ticket closed. The Marvell 88SE9128 is not being supported at this time by oi-dev.
----------------------------------------
Bug #993: Marvell SATA controller 88SE9128 - driver issue?
https://www.illumos.org/issues/993

Author: Lou Picciano
Status: Closed
Priority: Normal
Assignee: OI illumos
Category: Drivers
Target version: oi_151_stable
Difficulty: Medium
Tags: SATA Controller


h2. We are unable to configure any drive connected to the Marvell 88SE9128 controller. (controller is apparently implemented as a PCI device)
mobo: GigaByte GA-P67A-UD7-B3
Note: all drives controlled directly by the P67A work fine.

Specifically:
Drive does appear in cfgadm connected/unconfigured

# cfgadm -c configure sata1/0  
---  Failed to config device at ap_id: /devices/pci at 0,0/pci8086,1c1c at 1c,6/pci1458,b000 at 0:0

After making these changes to /etc/system:
> set ahci:ahci_msi_enabled = 0
> set sata:sata_max_queue_depth = 0x1

# cfgadm -a (does not even see the 'type' as sata-port): 
sata1/0  unknown      connected    unconfigured unknown


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://www.illumos.org/my/account


From devnull at illumos.org  Tue Sep  6 14:36:44 2011
From: devnull at illumos.org (illumos project)
Date: Tue, 6 Sep 2011 14:36:44 +0000
Subject: [Illumos-team] [illumos gate - Feature #993] (New) Marvell SATA
	controller 88SE9128 - driver issue?
References: <redmine.issue-993.20110505194142@illumos.org>
Message-ID: <redmine.journal-3713.20110906143644@illumos.org>


Issue #993 has been updated by Albert Lee.

Tracker changed from Bug to Feature
Project changed from OpenIndiana Distribution to illumos gate
Category deleted (Drivers)
Status changed from Closed to New
Priority changed from Normal to Low
Target version deleted (oi_151_stable)


----------------------------------------
Feature #993: Marvell SATA controller 88SE9128 - driver issue?
https://www.illumos.org/issues/993

Author: Lou Picciano
Status: New
Priority: Low
Assignee: OI illumos
Category: 
Target version: 
Difficulty: Medium
Tags: SATA Controller


h2. We are unable to configure any drive connected to the Marvell 88SE9128 controller. (controller is apparently implemented as a PCI device)
mobo: GigaByte GA-P67A-UD7-B3
Note: all drives controlled directly by the P67A work fine.

Specifically:
Drive does appear in cfgadm connected/unconfigured

# cfgadm -c configure sata1/0  
---  Failed to config device at ap_id: /devices/pci at 0,0/pci8086,1c1c at 1c,6/pci1458,b000 at 0:0

After making these changes to /etc/system:
> set ahci:ahci_msi_enabled = 0
> set sata:sata_max_queue_depth = 0x1

# cfgadm -a (does not even see the 'type' as sata-port): 
sata1/0  unknown      connected    unconfigured unknown


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://www.illumos.org/my/account


From devnull at illumos.org  Tue Sep  6 14:37:57 2011
From: devnull at illumos.org (illumos project)
Date: Tue, 6 Sep 2011 14:37:57 +0000
Subject: [Illumos-team] [OpenIndiana Distribution - Bug #560] (New) nwamd -
	unable to assign static IPv6 address as stated in manual
References: <redmine.issue-560.20101219040432@illumos.org>
Message-ID: <redmine.journal-3714.20110906143757@illumos.org>


Issue #560 has been updated by Ken Mays.

Status changed from Resolved to New
% Done changed from 100 to 0


----------------------------------------
Bug #560: nwamd - unable to assign static IPv6 address as stated in manual
https://www.illumos.org/issues/560

Author: N2Deep N2Deep
Status: New
Priority: Low
Assignee: OI illumos
Category: Documentation
Target version: oi_151_stable
Difficulty: Medium
Tags: needs-triage


After installing b148-text the nwamd manual states:

"A static IP address can be configured by changing the line in /etc/nwam/llp file that contains an interface name and the name of the method for obtaining an IP address...
...An optional static IPv6 address can be provided on the same line, immediately after the ipv6 token. Whether you provide a static address or not, IPv6 will use DHCPv6 or stateless address configuration, as directed by the local network configuration."

My local network runs stateless. Note that nwamd configures a stateless address just fine on this machine and I can ping/traceroute public addresses, etc, but the static address stated in /etc/nwam/llp is not listed by ipadm or ifconfig in addition to the stateless address.  Also this machine has another unconfigured wired network adapter, if it matters.

/etc/nwam/llp:
e1000g1 ipv6 <static-ipv6-address>


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://www.illumos.org/my/account


From devnull at illumos.org  Sat Sep 10 19:18:35 2011
From: devnull at illumos.org (illumos project)
Date: Sat, 10 Sep 2011 19:18:35 +0000
Subject: [Illumos-team] [OpenIndiana Distribution - Bug #841] (Feedback)
	OI_148a locks up on any problems with ZFS pools
References: <redmine.issue-841.20110320023149@illumos.org>
Message-ID: <redmine.journal-3788.20110910191835@illumos.org>


Issue #841 has been updated by Ken Mays.

Due date set to 2011-09-14
Category set to OS/Net (Kernel and Userland)
Status changed from New to Feedback
Target version set to oi_151_stable
Estimated time set to 8.00

Have user image-update usinglatest dev-il repo and reverify issue.
----------------------------------------
Bug #841: OI_148a locks up on any problems with ZFS pools
https://www.illumos.org/issues/841

Author: Jim Klimov
Status: Feedback
Priority: Normal
Assignee: OI illumos
Category: OS/Net (Kernel and Userland)
Target version: oi_151_stable
Difficulty: Medium
Tags: needs-triage


I have a 6-spindle raidz2 pool named "pool" on commodity hardware. Over that pool I've made a zvol which is exported and re-imported as an iSCSI device, and over that iSCSI device the same system creates another ZFS pool "dcpool".

Occasionally the system times out on some accesses to either pool (at least once due to a flaky SATA connector) and locks up completely - the X11 session is unresponsive, I can't SSH into the machine, it does not respond to power-button so I have to reset it.

I expected the ZFS pool to continue working properly (albeit slowly) in such case and perhaps trigger a resilver - even if one SATA connection is lost, the raidz2 pool without one disk still has an extra disk worth of parity data.

Also on some timeouts (i.e. the system is too busy processing data) the "dcpool"'s iSCSI localhost connection gets dropped, so the underlying device becomes UNAVAIL. This also causes system-wide lockup. I kinda hoped that the system would just fail the outstanding IOs (like on USB flash being yanked out) or wait for the device (iSCSI connection) to come back (like on NFS server reboot).

Instead, this system can hang for hours until it is reset. Which makes me nervous, at least. And it's not reliable as I'd hoped.

Some details regarding the "dcpool":

To be precise, the zvol is compressed in "pool" and for all datasets in "dcpool" I have enabled deduplication, so the system goes through write cycles faster. Instead of 'compress+dedup+dispose of common blocks' it can go like 'dedup+dispose of common blocks+compress unique blocks'.

The iSCSI loopback instead of making "dcpool" directly in the zvol was suggested by Darren Moffat:
http://blogs.sun.com/darren/entry/compress_encrypt_checksum_deduplicate_with

When the system boots up, the "dcpool" is deemed "UNAVAIL" (it was imported and remains cached via zpool.cache). However, after the startup of "iscsi/target" and "iscsi/initiator" it is automatically found, imported and mounted by the time X11 session logs in.

I had to tweak the SMF service properties - initiator now depends on target, so that they start in proper order for this setup.



-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://www.illumos.org/my/account


From devnull at illumos.org  Sat Sep 10 21:16:48 2011
From: devnull at illumos.org (illumos project)
Date: Sat, 10 Sep 2011 21:16:48 +0000
Subject: [Illumos-team] [OpenIndiana Distribution - Bug #276] (Resolved)
	error when attempting to eject DVD from drive
References: <redmine.issue-276.20100928084105@illumos.org>
Message-ID: <redmine.journal-3794.20110910211648@illumos.org>


Issue #276 has been updated by Ken Mays.

Due date set to 2011-09-14
Status changed from New to Resolved
Target version set to oi_151_stable
% Done changed from 0 to 100
Estimated time set to 1.00

This was resolved. I verified it on oi_151a using:
--> pfexec eject cdrom
cdrom /dev/dsk/... ejected (cdrom drive ejects CD/DVD)

if you are not root or have root privs:
---> eject cdrom
eject of cdrom * failed (mounted by another user process))

Then, reinserted CD/DVD... no warning messages and proper mounting and display of CD/DvD contents.

This is on oi_151a. Please reopen if you update and still have further issues. 

----------------------------------------
Bug #276: error when attempting to eject DVD from drive
https://www.illumos.org/issues/276

Author: r a
Status: Resolved
Priority: Low
Assignee: OI illumos
Category: OS/Net (Kernel and Userland)
Target version: oi_151_stable
Difficulty: Medium
Tags: needs-triage


After inserting a DVD into a drive, a warning message "cannot mount volume" is display; however the DVD is mounted and can be accessed. When attempting to unmount the same drive as a normal user via the command line the folllowing error is displayed (GUI only reports "Cannot umount volume").

bash-4.0$ eject cdrom
eject of cdrom /dev/dsk/c4t0d0s2 failed: Rejected send message, 2 matched rules; type="method_call", sender=":1.113" (uid=101 pid=4664 comm="") interface="org.freedesktop.Hal.Device.Storage" member="Eject" error name="(unset)" requested_reply=0 destination="org.freedesktop.Hal" (uid=0 pid=458 comm=""))
bash-4.0$ pfexec eject cdrom
eject of cdrom /dev/dsk/c4t0d0s2 failed: Rejected send message, 2 matched rules; type="method_call", sender=":1.114" (uid=101 pid=4666 comm="") interface="org.freedesktop.Hal.Device.Storage" member="Eject" error name="(unset)" requested_reply=0 destination="org.freedesktop.Hal" (uid=0 pid=458 comm=""))
bash-4.0$ 

The DVD can only be ejected by becoming root

root at fred:~#  eject cdrom






-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://www.illumos.org/my/account


From devnull at illumos.org  Sun Sep 11 19:51:10 2011
From: devnull at illumos.org (illumos project)
Date: Sun, 11 Sep 2011 19:51:10 +0000
Subject: [Illumos-team] [OpenIndiana Distribution - Bug #1495] OpenIndiana
	svn_151 support on Adaptec 6xxx
References: <redmine.issue-1495.20110911144059@illumos.org>
Message-ID: <redmine.journal-3804.20110911195110@illumos.org>


Issue #1495 has been updated by Ken Mays.

Due date set to 2011-12-11
Assignee set to OI illumos
Estimated time set to 40.00
Difficulty changed from Medium to Expert
Tags changed from needs-triage to aac

The Illumos project handles storage driver research to support the Illumos kernel. See them for further support.
----------------------------------------
Bug #1495: OpenIndiana svn_151 support on Adaptec 6xxx
https://www.illumos.org/issues/1495

Author: Kevin Herald
Status: New
Priority: Normal
Assignee: OI illumos
Category: Drivers
Target version: oi_151_stable
Difficulty: Expert
Tags: aac


I have Adaptec 6805 installed on OpenIndiana and am trying to get it being detected. Although according to this page http://wiki.openindiana.org/oi/Storage+Controllers+(HBA,+Raid+etc), it mentioned that the Adaptec 6xxx is supported but it just could not detect it on default installation. Trying to load the default aac module and devfsadm it would failed in attaching the driver to the controller.

I have tried to install the driver from vendor website, it does install correctly but would hang the system when manually devfsadm or add_drv. Have verify that driver works well on Solaris 10 update 8 without issue. I have submitted a report to the vendor and at the same time would like to seek help here.

Thank you. 


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://www.illumos.org/my/account


From devnull at illumos.org  Mon Sep 12 06:00:40 2011
From: devnull at illumos.org (illumos project)
Date: Mon, 12 Sep 2011 06:00:40 +0000
Subject: [Illumos-team] [OpenIndiana Distribution - Bug #1399] (Feedback)
	oi_151, wireless signals not detected on laptop
References: <redmine.issue-1399.20110822135914@illumos.org>
Message-ID: <redmine.journal-3822.20110912060040@illumos.org>


Issue #1399 has been updated by Ken Mays.

Due date set to 2011-09-14
Status changed from New to Feedback
Target version set to oi_151_stable
% Done changed from 0 to 100
Estimated time set to 1.00
Tags changed from wifi to ath

Use ath at 0.5.11,5.11-0.151.1:20110910T085136Z on oi-151a.
----------------------------------------
Bug #1399: oi_151, wireless signals not detected on laptop
https://www.illumos.org/issues/1399

Author: Fred Kimball
Status: Feedback
Priority: Normal
Assignee: OI illumos
Category: Drivers
Target version: oi_151_stable
Difficulty: Medium
Tags: ath


Wireless signals are not detected on a Sony Vaio laptop equipped with an Atheros (AR5001) wireless network adapter when booted in oi_151. oi_148 was initially installed in this computer and wireless signals are detected and obtains an IP address from the router when booted into oi_148.


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://www.illumos.org/my/account


From devnull at illumos.org  Mon Sep 12 06:13:26 2011
From: devnull at illumos.org (illumos project)
Date: Mon, 12 Sep 2011 06:13:26 +0000
Subject: [Illumos-team] [OpenIndiana Distribution - Bug #1399] oi_151,
	wireless signals not detected on laptop
References: <redmine.issue-1399.20110822135914@illumos.org>
Message-ID: <redmine.journal-3825.20110912061326@illumos.org>


Issue #1399 has been updated by Garrett D'Amore.


I wonder if this is another item of fall out caused by 534, such 1402.

Would be interesting to know if the latest kernel with the cache tweaks backed out works properly.

I don't recall seeing anything specific to wifi changing in the interim, at any rate.
----------------------------------------
Bug #1399: oi_151, wireless signals not detected on laptop
https://www.illumos.org/issues/1399

Author: Fred Kimball
Status: Feedback
Priority: Normal
Assignee: OI illumos
Category: Drivers
Target version: oi_151_stable
Difficulty: Medium
Tags: ath


Wireless signals are not detected on a Sony Vaio laptop equipped with an Atheros (AR5001) wireless network adapter when booted in oi_151. oi_148 was initially installed in this computer and wireless signals are detected and obtains an IP address from the router when booted into oi_148.


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://www.illumos.org/my/account


From devnull at illumos.org  Mon Sep 12 12:42:28 2011
From: devnull at illumos.org (illumos project)
Date: Mon, 12 Sep 2011 12:42:28 +0000
Subject: [Illumos-team] [OpenIndiana Distribution - Bug #1441] cpqary3
	driver is old and causes panic in oi_151
References: <redmine.issue-1441.20110901184406@illumos.org>
Message-ID: <redmine.journal-3833.20110912124228@illumos.org>


Issue #1441 has been updated by Ken Mays.

Category changed from oi-build to Drivers
Assignee changed from OI Userland to OI illumos
Difficulty changed from Medium to Expert
Tags changed from needs-triage to cpqary3

Moved this to Illumos team for licensing and testing review.
----------------------------------------
Bug #1441: cpqary3 driver is old and causes panic in oi_151
https://www.illumos.org/issues/1441

Author: Bryan Leaman
Status: Feedback
Priority: High
Assignee: OI illumos
Category: Drivers
Target version: oi_151_stable
Difficulty: Expert
Tags: cpqary3


oi_151 (and probably anything beyond snv_139) cannot be installed or used on some HP Proliant hardware that uses the cpqary3 driver.  An attempt to boot the oi_151 install CD results in a kernel panic in cpqary3_retrieve().

This was initially reported as an illumos issue:

http://www.illumos.org/issues/348

however using a newer HP driver seems to fix the problem.  

On a Proliant DL360 G4p with a SmartArray 6i controller, I installed snv_134 and then upgraded to oi_151a in a new BE.  Booting into that BE failed with a kernel panic with the 2.2.0a driver from dev-il.  Upgrading the driver to the latest version 2.4.6 available from HP allows the BE to boot successfully, and 24 hours of filebench load testing was successful without any problems.

It may be a good idea to update this driver for the 151 release.


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://www.illumos.org/my/account


From devnull at illumos.org  Tue Sep 13 12:29:03 2011
From: devnull at illumos.org (illumos project)
Date: Tue, 13 Sep 2011 12:29:03 +0000
Subject: [Illumos-team] [OpenIndiana Distribution - Bug #1399] oi_151,
	wireless signals not detected on laptop
References: <redmine.issue-1399.20110822135914@illumos.org>
Message-ID: <redmine.journal-3863.20110913122903@illumos.org>


Issue #1399 has been updated by Fred Kimball.


Hello Ken and Garrett.

The pkg you mention has a later time stamp that what is currently installed, so hopefully the issue is fixed in oi_151_stable. No update is showing in the oi_151a repo. Here is my output of pkg info:
~$ pkg info ath
          Name: driver/network/ath
       Summary: Atheros 802.11b/g Wireless NIC Driver
   Description: Atheros AR52xx 802.11b/g Wireless NIC Driver
      Category: Drivers/Networking
         State: Installed
     Publisher: openindiana.org
       Version: 0.5.11
 Build Release: 5.11
        Branch: 0.151.1
Packaging Date: August 18, 2011 08:52:32 PM 
          Size: 765.83 kB
          FMRI: pkg://openindiana.org/driver/network/ath at 0.5.11,5.11-0.151.1:20110818T205232Z
----------------------------------------
Bug #1399: oi_151, wireless signals not detected on laptop
https://www.illumos.org/issues/1399

Author: Fred Kimball
Status: Feedback
Priority: Normal
Assignee: OI illumos
Category: Drivers
Target version: oi_151_stable
Difficulty: Medium
Tags: ath


Wireless signals are not detected on a Sony Vaio laptop equipped with an Atheros (AR5001) wireless network adapter when booted in oi_151. oi_148 was initially installed in this computer and wireless signals are detected and obtains an IP address from the router when booted into oi_148.


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://www.illumos.org/my/account


From devnull at illumos.org  Tue Sep 13 18:09:34 2011
From: devnull at illumos.org (illumos project)
Date: Tue, 13 Sep 2011 18:09:34 +0000
Subject: [Illumos-team] [OpenIndiana Distribution - Feature #1509] (New)
	Provide ixgbe driver support update
Message-ID: <redmine.issue-1509.20110913180934@illumos.org>


Issue #1509 has been reported by Ken Mays.

----------------------------------------
Feature #1509: Provide ixgbe driver support update 
https://www.illumos.org/issues/1509

Author: Ken Mays
Status: New
Priority: Immediate
Assignee: Alasdair Lumsden
Category: OS/Net (Kernel and Userland)
Target version: oi_151_stable
Difficulty: Bite-size
Tags: needs-triage


Ref: https://bitbucket.org/illumos/illumos-gate/changeset/f03238cace0b

Please provide thee latest ixgbe driver update to maintain high-end server support, usage, and testing of the Intel 82598/82599-based 10Gb Ethernet Controllers. 



-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://www.illumos.org/my/account


From devnull at illumos.org  Tue Sep 13 18:57:42 2011
From: devnull at illumos.org (illumos project)
Date: Tue, 13 Sep 2011 18:57:42 +0000
Subject: [Illumos-team] [OpenIndiana Distribution - Bug #1495] (Resolved)
	OpenIndiana svn_151 support on Adaptec 6xxx
References: <redmine.issue-1495.20110911144059@illumos.org>
Message-ID: <redmine.journal-3874.20110913185742@illumos.org>


Issue #1495 has been updated by Ken Mays.

Status changed from New to Resolved

Ticket duplicate of Illumos ticket #1497. Closing this one.
----------------------------------------
Bug #1495: OpenIndiana svn_151 support on Adaptec 6xxx
https://www.illumos.org/issues/1495

Author: Kevin Herald
Status: Resolved
Priority: Normal
Assignee: OI illumos
Category: Drivers
Target version: oi_151_stable
Difficulty: Expert
Tags: aac


I have Adaptec 6805 installed on OpenIndiana and am trying to get it being detected. Although according to this page http://wiki.openindiana.org/oi/Storage+Controllers+(HBA,+Raid+etc), it mentioned that the Adaptec 6xxx is supported but it just could not detect it on default installation. Trying to load the default aac module and devfsadm it would failed in attaching the driver to the controller.

I have tried to install the driver from vendor website, it does install correctly but would hang the system when manually devfsadm or add_drv. Have verify that driver works well on Solaris 10 update 8 without issue. I have submitted a report to the vendor and at the same time would like to seek help here.

Thank you. 


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://www.illumos.org/my/account


From devnull at illumos.org  Wed Sep 14 03:29:00 2011
From: devnull at illumos.org (illumos project)
Date: Wed, 14 Sep 2011 03:29:00 +0000
Subject: [Illumos-team] [OpenIndiana Distribution - Bug #1399] oi_151,
	wireless signals not detected on laptop
References: <redmine.issue-1399.20110822135914@illumos.org>
Message-ID: <redmine.journal-3884.20110914032900@illumos.org>


Issue #1399 has been updated by Ken Mays.


Fred - can you do this:
1. pfexec pkg refresh --full
2. pfexec pkg image-update
3. pkg info ath
----------------------------------------
Bug #1399: oi_151, wireless signals not detected on laptop
https://www.illumos.org/issues/1399

Author: Fred Kimball
Status: Feedback
Priority: Normal
Assignee: OI illumos
Category: Drivers
Target version: oi_151_stable
Difficulty: Medium
Tags: ath


Wireless signals are not detected on a Sony Vaio laptop equipped with an Atheros (AR5001) wireless network adapter when booted in oi_151. oi_148 was initially installed in this computer and wireless signals are detected and obtains an IP address from the router when booted into oi_148.


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://www.illumos.org/my/account


From devnull at illumos.org  Wed Sep 14 16:07:46 2011
From: devnull at illumos.org (illumos project)
Date: Wed, 14 Sep 2011 16:07:46 +0000
Subject: [Illumos-team] [OpenIndiana Distribution - Bug #1441] (Resolved)
	cpqary3 driver is old and causes panic in oi_151
References: <redmine.issue-1441.20110901184406@illumos.org>
Message-ID: <redmine.journal-3890.20110914160746@illumos.org>


Issue #1441 has been updated by Ken Mays.

Status changed from Feedback to Resolved

Per Albert Lee's notes in #348:
"cpqary3 is actually part of ON's closed bits. Even if the root cause of the panic is fixed, it may make sense to drop it entirely since it's outdated and there is an alternative source (unless someone can convince HP to provide a new driver under a licence that allows unlimited redistribution)."

Resolution: We don't need to add it to IPS and deal with OI distribution licensing issues. Removing cpqary3 from OI-IPS makes sense (since it is proven defective) and HP server admins can add, maintain, and receive HP technical support for the CPQary3 driver themselves during installations.
----------------------------------------
Bug #1441: cpqary3 driver is old and causes panic in oi_151
https://www.illumos.org/issues/1441

Author: Bryan Leaman
Status: Resolved
Priority: High
Assignee: OI illumos
Category: Drivers
Target version: oi_151_stable
Difficulty: Expert
Tags: cpqary3


oi_151 (and probably anything beyond snv_139) cannot be installed or used on some HP Proliant hardware that uses the cpqary3 driver.  An attempt to boot the oi_151 install CD results in a kernel panic in cpqary3_retrieve().

This was initially reported as an illumos issue:

http://www.illumos.org/issues/348

however using a newer HP driver seems to fix the problem.  

On a Proliant DL360 G4p with a SmartArray 6i controller, I installed snv_134 and then upgraded to oi_151a in a new BE.  Booting into that BE failed with a kernel panic with the 2.2.0a driver from dev-il.  Upgrading the driver to the latest version 2.4.6 available from HP allows the BE to boot successfully, and 24 hours of filebench load testing was successful without any problems.

It may be a good idea to update this driver for the 151 release.


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://www.illumos.org/my/account


From devnull at illumos.org  Thu Sep 15 13:04:58 2011
From: devnull at illumos.org (illumos project)
Date: Thu, 15 Sep 2011 13:04:58 +0000
Subject: [Illumos-team] [OpenIndiana Distribution - Bug #1399] oi_151,
	wireless signals not detected on laptop
References: <redmine.issue-1399.20110822135914@illumos.org>
Message-ID: <redmine.journal-3918.20110915130458@illumos.org>


Issue #1399 has been updated by Fred Kimball.


Ken, good news, I'm now connected through the wireless connection. So you can mark this bug closed. I had pkgs from sfebuild which did not refresh, so had to unset and check the wiki for it's replacement. image-update required package/pkg to be updated first.

Thank you for your help and everyone else on the illumos and oi team!
----------------------------------------
Bug #1399: oi_151, wireless signals not detected on laptop
https://www.illumos.org/issues/1399

Author: Fred Kimball
Status: Feedback
Priority: Normal
Assignee: OI illumos
Category: Drivers
Target version: oi_151_stable
Difficulty: Medium
Tags: ath


Wireless signals are not detected on a Sony Vaio laptop equipped with an Atheros (AR5001) wireless network adapter when booted in oi_151. oi_148 was initially installed in this computer and wireless signals are detected and obtains an IP address from the router when booted into oi_148.


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://www.illumos.org/my/account


From devnull at illumos.org  Thu Sep 15 16:14:28 2011
From: devnull at illumos.org (illumos project)
Date: Thu, 15 Sep 2011 16:14:28 +0000
Subject: [Illumos-team] [OpenIndiana Distribution - Bug #1399] (Resolved)
	oi_151, wireless signals not detected on laptop
References: <redmine.issue-1399.20110822135914@illumos.org>
Message-ID: <redmine.journal-3925.20110915161419@illumos.org>


Issue #1399 has been updated by Ken Mays.

Status changed from Feedback to Resolved

Resolved, per user's request.
----------------------------------------
Bug #1399: oi_151, wireless signals not detected on laptop
https://www.illumos.org/issues/1399

Author: Fred Kimball
Status: Resolved
Priority: Normal
Assignee: OI illumos
Category: Drivers
Target version: oi_151_stable
Difficulty: Medium
Tags: ath


Wireless signals are not detected on a Sony Vaio laptop equipped with an Atheros (AR5001) wireless network adapter when booted in oi_151. oi_148 was initially installed in this computer and wireless signals are detected and obtains an IP address from the router when booted into oi_148.


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://www.illumos.org/my/account


From devnull at illumos.org  Thu Sep 15 22:39:01 2011
From: devnull at illumos.org (illumos project)
Date: Thu, 15 Sep 2011 22:39:01 +0000
Subject: [Illumos-team] [OpenIndiana Distribution - Bug #1523] (Feedback)
	OI151a can't access Symbios 53c875
References: <redmine.issue-1523.20110915204836@illumos.org>
Message-ID: <redmine.journal-3931.20110915223901@illumos.org>


Issue #1523 has been updated by Ken Mays.

Due date set to 2011-09-30
Category set to Drivers
Status changed from New to Feedback
Assignee set to OI illumos
Priority changed from Normal to Low
Target version set to oi_151_stable
Estimated time set to 1.00
Difficulty changed from Medium to Bite-size
Tags changed from needs-triage to glm

Peter - Yes, the glm driver is provided:
driver/storage/glm at 0.5.11,5.11-0.151.1:20110912T031049Z
Please test and review for functionality with your system.
----------------------------------------
Bug #1523: OI151a can't access Symbios 53c875
https://www.illumos.org/issues/1523

Author: Peter Tribble
Status: Feedback
Priority: Low
Assignee: OI illumos
Category: Drivers
Target version: oi_151_stable
Difficulty: Bite-size
Tags: glm


I have a system with several Symbios 53c875 SCSI cards. These aren't picked up by OI151a.

At least, the device driver utility says it doesn't have a driver for them.

They work fine with 2009.06, using the ncrs driver. From path_to_inst there, I see:

"/pci at 0,0/pci8086,244e at 1e/pci1000,1000 at 0" 0 "ncrs"
"/pci at 0,0/pci8086,244e at 1e/pci1000,1000 at 1" 1 "ncrs"
"/pci at 0,0/pci8086,244e at 1e/pci1000,1000 at 1,1" 2 "ncrs"

Now, ncrs has gone. Should glm be a viable replacement?



-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://www.illumos.org/my/account


From devnull at illumos.org  Thu Sep 15 22:46:12 2011
From: devnull at illumos.org (illumos project)
Date: Thu, 15 Sep 2011 22:46:12 +0000
Subject: [Illumos-team] [OpenIndiana Distribution - Bug #1522] eject fails
	for normal user
References: <redmine.issue-1522.20110915203820@illumos.org>
Message-ID: <redmine.journal-3932.20110915224612@illumos.org>


Issue #1522 has been updated by Ken Mays.

Due date set to 2011-09-30
Category set to OS/Net (Kernel and Userland)
Assignee set to OI illumos
Priority changed from Normal to Low
Target version set to oi_151_stable
Estimated time set to 1.00
Difficulty changed from Medium to Bite-size
Tags changed from needs-triage to SUNWcs


----------------------------------------
Bug #1522: eject fails for normal user
https://www.illumos.org/issues/1522

Author: Peter Tribble
Status: New
Priority: Low
Assignee: OI illumos
Category: OS/Net (Kernel and Userland)
Target version: oi_151_stable
Difficulty: Bite-size
Tags: SUNWcs


Running OI151a, I attempt to eject the cd/dvd. It fails:

~$ eject cdrom
eject of cdrom /dev/dsk/c2t1d0s2 failed: hal-storage-can-unmount-volumes-mounted-by-others refused uid 101

I'm forced to eject the cd as root, which is definitely undesirable.


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://www.illumos.org/my/account


From devnull at illumos.org  Thu Sep 15 22:48:55 2011
From: devnull at illumos.org (illumos project)
Date: Thu, 15 Sep 2011 22:48:55 +0000
Subject: [Illumos-team] [OpenIndiana Distribution - Bug #1522] (Feedback)
	eject fails for normal user
References: <redmine.issue-1522.20110915203820@illumos.org>
Message-ID: <redmine.journal-3933.20110915224855@illumos.org>


Issue #1522 has been updated by Ken Mays.

Status changed from New to Feedback

Verified bug. As default user 'jack':
1. eject cdrom
->should work, but doesn't (permissions)
2. pfexec eject cdrom
-> works

----------------------------------------
Bug #1522: eject fails for normal user
https://www.illumos.org/issues/1522

Author: Peter Tribble
Status: Feedback
Priority: Low
Assignee: OI illumos
Category: OS/Net (Kernel and Userland)
Target version: oi_151_stable
Difficulty: Bite-size
Tags: SUNWcs


Running OI151a, I attempt to eject the cd/dvd. It fails:

~$ eject cdrom
eject of cdrom /dev/dsk/c2t1d0s2 failed: hal-storage-can-unmount-volumes-mounted-by-others refused uid 101

I'm forced to eject the cd as root, which is definitely undesirable.


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://www.illumos.org/my/account


From devnull at illumos.org  Fri Sep 16 15:32:51 2011
From: devnull at illumos.org (illumos project)
Date: Fri, 16 Sep 2011 15:32:51 +0000
Subject: [Illumos-team] [OpenIndiana Distribution - Bug #1523] OI151a can't
	access Symbios 53c875
References: <redmine.issue-1523.20110915204836@illumos.org>
Message-ID: <redmine.journal-3952.20110916153250@illumos.org>


Issue #1523 has been updated by Ken Mays.

Assignee changed from Ken Mays to OI illumos

Peter - Thanks for your verification of this as I did note the missing pci-ids, but didn't know if it was intentional for a reason or just an oversight of the driver packaging. 

I'll push this to illumos-gate to add the pci-ids to the glm driver for:
pci1000,1
pci1000,2 
pci1000,3 
pci1000,4 
pci1000,6 
pci1000,c 
pci1000,f
----------------------------------------
Bug #1523: OI151a can't access Symbios 53c875
https://www.illumos.org/issues/1523

Author: Peter Tribble
Status: Feedback
Priority: Low
Assignee: OI illumos
Category: Drivers
Target version: oi_151_stable
Difficulty: Bite-size
Tags: glm


I have a system with several Symbios 53c875 SCSI cards. These aren't picked up by OI151a.

At least, the device driver utility says it doesn't have a driver for them.

They work fine with 2009.06, using the ncrs driver. From path_to_inst there, I see:

"/pci at 0,0/pci8086,244e at 1e/pci1000,1000 at 0" 0 "ncrs"
"/pci at 0,0/pci8086,244e at 1e/pci1000,1000 at 1" 1 "ncrs"
"/pci at 0,0/pci8086,244e at 1e/pci1000,1000 at 1,1" 2 "ncrs"

Now, ncrs has gone. Should glm be a viable replacement?



-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://www.illumos.org/my/account


From devnull at illumos.org  Fri Sep 16 18:24:14 2011
From: devnull at illumos.org (illumos project)
Date: Fri, 16 Sep 2011 18:24:14 +0000
Subject: [Illumos-team] [OpenIndiana Distribution - Bug #618] i/o hang with
	mega_sas driver
References: <redmine.issue-618.20110110121051@illumos.org>
Message-ID: <redmine.journal-3965.20110916182414@illumos.org>


Issue #618 has been updated by Ken Mays.

Assignee set to OI illumos


----------------------------------------
Bug #618: i/o hang with mega_sas driver
https://www.illumos.org/issues/618

Author: Steve Jacobson
Status: New
Priority: High
Assignee: OI illumos
Category: Drivers
Target version: oi_151_stable
Difficulty: Expert
Tags: megaraid


We have a system that has five (5) MegaRAID 8888ELP cards.  of the 10 channels on these cards, 9 of them are connected to 4 SATA drives each, for a total of 36 drives.   Whenever there is significant i/o, the i/o will hang on the system with the following symptoms:

* iostat -x shows that some of the drives are 100% blocked.  When this happens, the number of drives varies.  This most recent hang, there were six drives in this state.  They are always connected to a single controller, although which controller varies.
* ZFS commands all hang
* The command that was running (in this case a 'cp' commaand) also hangs.
* The box cannot be rebooted using either shutdown or reboot.  A power cycle is required
* There is nothing in /var/adm/messages related to disk i/o at the time of the hang, or since the last boot.

I'm attaching the output of "echo '::threadlist -v' | mdb -k" to this bug.  Please let me know what other information I can provide.

Thanks!

-Steve J



-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://www.illumos.org/my/account


From devnull at illumos.org  Fri Sep 16 22:27:28 2011
From: devnull at illumos.org (illumos project)
Date: Fri, 16 Sep 2011 22:27:28 +0000
Subject: [Illumos-team] [OpenIndiana Distribution - Bug #1071] kdestroy
	generates console errors for GSSAPI-related kernel modules
References: <redmine.issue-1071.20110528135726@illumos.org>
Message-ID: <redmine.journal-3967.20110916222728@illumos.org>


Issue #1071 has been updated by Bayard Bell.

Target version set to oi_151_stable
% Done changed from 0 to 50

Upstream change 1073 has now been integrated and needs to be pulled into OI's illumos-gate.
----------------------------------------
Bug #1071: kdestroy generates console errors for GSSAPI-related kernel modules
https://www.illumos.org/issues/1071

Author: Bayard Bell
Status: New
Priority: Normal
Assignee: OI illumos
Category: OS/Net (Kernel and Userland)
Target version: oi_151_stable
Difficulty: Medium
Tags: needs-triage


Need to dig in to see what's happening here and what these are about:

May 28 14:44:52 bloomington genunix: /kernel/misc/amd64/rpcsec_gss: undefined symbol
May 28 14:44:52 bloomington genunix:  'gss_import_name'
May 28 14:44:52 bloomington genunix: /kernel/misc/amd64/rpcsec_gss: undefined symbol
May 28 14:44:52 bloomington genunix:  'kgss_get_group_info'
May 28 14:44:52 bloomington genunix: /kernel/misc/amd64/rpcsec_gss: undefined symbol
May 28 14:44:52 bloomington genunix:  'GSS_C_NT_HOSTBASED_SERVICE'
May 28 14:44:52 bloomington genunix: /kernel/misc/amd64/rpcsec_gss: undefined symbol
May 28 14:44:52 bloomington genunix:  'kgsscred_expname_to_unix_cred'
May 28 14:44:52 bloomington genunix: /kernel/misc/amd64/rpcsec_gss: undefined symbol
May 28 14:44:52 bloomington genunix:  'kgss_accept_sec_context'
May 28 14:44:52 bloomington genunix: /kernel/misc/amd64/rpcsec_gss: undefined symbol
May 28 14:44:52 bloomington genunix:  'kgss_export_sec_context'
May 28 14:44:52 bloomington genunix: /kernel/misc/amd64/rpcsec_gss: undefined symbol
May 28 14:44:52 bloomington genunix:  'kgss_import_sec_context'
May 28 14:44:52 bloomington genunix: /kernel/misc/amd64/rpcsec_gss: undefined symbol
May 28 14:44:52 bloomington genunix:  'kgss_verify'
May 28 14:44:52 bloomington genunix: /kernel/misc/amd64/rpcsec_gss: undefined symbol
May 28 14:44:52 bloomington genunix:  'kgss_unseal'
May 28 14:44:52 bloomington genunix: /kernel/misc/amd64/rpcsec_gss: undefined symbol
May 28 14:44:52 bloomington genunix:  'kgss_display_status'
May 28 14:44:52 bloomington genunix: /kernel/misc/amd64/rpcsec_gss: undefined symbol
May 28 14:44:52 bloomington genunix:  'kgss_free_oid'
May 28 14:44:52 bloomington genunix: /kernel/misc/amd64/rpcsec_gss: undefined symbol
May 28 14:44:52 bloomington genunix:  'kgss_seal'
May 28 14:44:52 bloomington genunix: /kernel/misc/amd64/rpcsec_gss: undefined symbol
May 28 14:44:52 bloomington genunix:  'kgss_sign'
May 28 14:44:52 bloomington genunix: /kernel/misc/amd64/rpcsec_gss: undefined symbol
May 28 14:44:52 bloomington genunix:  'kgss_delete_sec_context'
May 28 14:44:52 bloomington genunix: /kernel/misc/amd64/rpcsec_gss: undefined symbol
May 28 14:44:52 bloomington genunix:  'gss_release_buffer'
May 28 14:44:52 bloomington genunix: /kernel/misc/amd64/rpcsec_gss: undefined symbol
May 28 14:44:52 bloomington genunix:  'kgss_init_sec_context'
May 28 14:44:52 bloomington genunix: /kernel/misc/amd64/rpcsec_gss: undefined symbol
May 28 14:44:52 bloomington genunix:  'gss_release_name'
May 28 14:44:52 bloomington genunix: /kernel/misc/amd64/rpcsec_gss: undefined symbol
May 28 14:44:52 bloomington genunix:  'kgss_release_cred'
May 28 14:44:52 bloomington genunix: WARNING: mod_load: cannot load module 'rpcsec_gss'
May 28 14:44:52 bloomington genunix: WARNING: rpcsec_gss: 
May 28 14:44:52 bloomington genunix: unable to resolve dependency, module 'misc/kgssapi' not found



-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://www.illumos.org/my/account


From devnull at illumos.org  Sat Sep 17 06:30:06 2011
From: devnull at illumos.org (illumos project)
Date: Sat, 17 Sep 2011 06:30:06 +0000
Subject: [Illumos-team] [OpenIndiana Distribution - Bug #1523] OI151a can't
	access Symbios 53c875
References: <redmine.issue-1523.20110915204836@illumos.org>
Message-ID: <redmine.journal-3969.20110917063006@illumos.org>


Issue #1523 has been updated by Garrett D'Amore.


The missing device ids are more complex than you might realize, because it turns out that under a given device id, there are different chip versions, and glm can support some, but not all of those versions.

Sadly, this just isn't as cut and dried as it should be.

Short of modifying glm to support all the legacy parts, I'm not sure what the right answer here is.  I'm inclined to just leave those parts out .. there aren't that many of these legacy controllers still out there in the field.
----------------------------------------
Bug #1523: OI151a can't access Symbios 53c875
https://www.illumos.org/issues/1523

Author: Peter Tribble
Status: Feedback
Priority: Low
Assignee: OI illumos
Category: Drivers
Target version: oi_151_stable
Difficulty: Bite-size
Tags: glm


I have a system with several Symbios 53c875 SCSI cards. These aren't picked up by OI151a.

At least, the device driver utility says it doesn't have a driver for them.

They work fine with 2009.06, using the ncrs driver. From path_to_inst there, I see:

"/pci at 0,0/pci8086,244e at 1e/pci1000,1000 at 0" 0 "ncrs"
"/pci at 0,0/pci8086,244e at 1e/pci1000,1000 at 1" 1 "ncrs"
"/pci at 0,0/pci8086,244e at 1e/pci1000,1000 at 1,1" 2 "ncrs"

Now, ncrs has gone. Should glm be a viable replacement?



-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://www.illumos.org/my/account


From devnull at illumos.org  Mon Sep 19 19:15:37 2011
From: devnull at illumos.org (illumos project)
Date: Mon, 19 Sep 2011 19:15:37 +0000
Subject: [Illumos-team] [OpenIndiana Distribution - Bug #1523] OI151a can't
	access Symbios 53c875
References: <redmine.issue-1523.20110915204836@illumos.org>
Message-ID: <redmine.journal-4008.20110919191537@illumos.org>


Issue #1523 has been updated by Peter Tribble.


I see two choices. We could simply have glm on x86 have the same list of device ids as on sparc. There's a certain level of consistency there. Or we get it to acquire everything from ncrs. I think I would much rather offer to support as many ids as possible, rather than desupport a load of hardware that actually will work.
----------------------------------------
Bug #1523: OI151a can't access Symbios 53c875
https://www.illumos.org/issues/1523

Author: Peter Tribble
Status: Feedback
Priority: Low
Assignee: OI illumos
Category: Drivers
Target version: oi_151_stable
Difficulty: Bite-size
Tags: glm


I have a system with several Symbios 53c875 SCSI cards. These aren't picked up by OI151a.

At least, the device driver utility says it doesn't have a driver for them.

They work fine with 2009.06, using the ncrs driver. From path_to_inst there, I see:

"/pci at 0,0/pci8086,244e at 1e/pci1000,1000 at 0" 0 "ncrs"
"/pci at 0,0/pci8086,244e at 1e/pci1000,1000 at 1" 1 "ncrs"
"/pci at 0,0/pci8086,244e at 1e/pci1000,1000 at 1,1" 2 "ncrs"

Now, ncrs has gone. Should glm be a viable replacement?



-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://www.illumos.org/my/account


From devnull at illumos.org  Tue Sep 20 11:46:33 2011
From: devnull at illumos.org (illumos project)
Date: Tue, 20 Sep 2011 11:46:33 +0000
Subject: [Illumos-team] [OpenIndiana Distribution - Bug #1500] KVM: System
	freezes after loading module
References: <redmine.issue-1500.20110913011303@illumos.org>
Message-ID: <redmine.journal-4025.20110920114633@illumos.org>


Issue #1500 has been updated by Ryo Murakawa.

Assignee changed from Ryo Murakawa to OI illumos


----------------------------------------
Bug #1500: KVM: System freezes after loading module
https://www.illumos.org/issues/1500

Author: Patrick Sodre
Status: New
Priority: Normal
Assignee: OI illumos
Category: 
Target version: oi_151_stable
Difficulty: Medium
Tags: kvm


Hi Guys,
   I am experiencing the same issue reported at 
https://github.com/joyent/illumos-kvm/issues/1.

It seems that richlowe(bottom of page) has posted a solution to that problem. 
 
I was going to try and compile KVM/OI by myself but quickly found I lacked the right tools/experience to do so.






-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://www.illumos.org/my/account


From devnull at illumos.org  Wed Sep 21 01:41:15 2011
From: devnull at illumos.org (illumos project)
Date: Wed, 21 Sep 2011 01:41:15 +0000
Subject: [Illumos-team] [OpenIndiana Distribution - Bug #1441] (Feedback)
	cpqary3 driver is old and causes panic in oi_151
References: <redmine.issue-1441.20110901184406@illumos.org>
Message-ID: <redmine.journal-4033.20110921014115@illumos.org>


Issue #1441 has been updated by Rich Lowe.

Status changed from Resolved to Feedback

Bugs that aren't resolved should not be Resolved.
----------------------------------------
Bug #1441: cpqary3 driver is old and causes panic in oi_151
https://www.illumos.org/issues/1441

Author: Bryan Leaman
Status: Feedback
Priority: High
Assignee: OI illumos
Category: Drivers
Target version: oi_151_stable
Difficulty: Expert
Tags: cpqary3


oi_151 (and probably anything beyond snv_139) cannot be installed or used on some HP Proliant hardware that uses the cpqary3 driver.  An attempt to boot the oi_151 install CD results in a kernel panic in cpqary3_retrieve().

This was initially reported as an illumos issue:

http://www.illumos.org/issues/348

however using a newer HP driver seems to fix the problem.  

On a Proliant DL360 G4p with a SmartArray 6i controller, I installed snv_134 and then upgraded to oi_151a in a new BE.  Booting into that BE failed with a kernel panic with the 2.2.0a driver from dev-il.  Upgrading the driver to the latest version 2.4.6 available from HP allows the BE to boot successfully, and 24 hours of filebench load testing was successful without any problems.

It may be a good idea to update this driver for the 151 release.


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://www.illumos.org/my/account


