[request-sponsor] 6936304: vr causes a panic when a stopped device is interrupted.
On 03/18/10 02:59 PM, Joost Mulders wrote: I would like to work on this bug. Proposed fix is at http://cr.opensolaris.org/~joostm/onnv-vr/ SCA number is OSO458. Thanks much! Joost ___ request-sponsor mailing list request-sponsor at opensolaris.org I'll sponsor you. -- Garrett
[request-sponsor] sponsor request for 6913754, 6913756, 6913814 and 6913911
If nobody else wants it, I can sponsor you. However, I don't necessarily have access to these particular models of 8169. - Garrett Masa Murayama wrote: Hello, This is a request for sponsors for fixes on CRs below. 6913754 rge with rtl8169sc caused tx errors repeatedly on plumb 6913756 rge tx performance is very slow for rtl8169sc 6913814 tx performance of rge is very slow with RTL8169S 6913911 rge with rtl8169sc hanged in test05 of nicdrv They are problems on realtek gigabit ethernet nic chipset. I'm the submitter of them, and described required changes on the source codes in the bug reports. As I have the nic hardware, I can test the fixes by nicdrv. My SCA# is OS0107 thanks in advance Masayuki Murayama ___ request-sponsor mailing list request-sponsor at opensolaris.org
[request-sponsor] sponsorship update
This is to record that Steve Stallion (OS0383) has contributed a fix for CR 6898794 (dnet interface lost RUNNING flag after unplumb/plumb cycle). I'm sponsoring his integration, and I have already filed the RTI. For those keeping track of sponsored integrations, this is one more. - Garrett
[request-sponsor] Sponsor request for BUG ID: 6881910
James Purdy wrote: Hello, James Purdy (Contributor #OS0423) Requesting a sponsor for: BUG ID: 6881910 BUG SYNOPSIS: Adaptec 1220SA Controller on my workstation. It is using SIL3132. Username: evljames I have put the webrev at http://cr.opensolaris.org/~evljames/onnv-gate/ http://cr.opensolaris.org/%7Eevljames/onnv-gate/ This change looks like it is missing a change to the packaging to update driver_aliases. I'm thinking you need to update SUNWsi3124/ postinstall and preremove. (And when this is done, you should change the driver to use the new proc_drvutils so we can eliminate another instance of check_add_drv from the packaging scripts. :-) - Garrett Thanks! ___ request-sponsor mailing list request-sponsor at opensolaris.org
[request-sponsor] CR 6892693 rge with RTL8111C missing multicast packets
I'll sponsor this one. - Garrett Masa Murayama wrote: I'd like to request for sponsor on CR 6892693. This issue is that rge driver with RTL8111C chipset doesn't receive multicast packets. The root cause is that rge doesn't recognize the verison of the chipset correctly. It also included another bug that rge does't receive all multicast packets in promiscuous mode. I have made a modified version of rge, and the original bug reporter Jorgen Lundman, not me, has confirmed that all problems was gone with it. I have prepared webrev. http://cr.opensolaris.org/~mrym/rge.mcast/ Regards, Masayuki Murayama OS0107 ___ request-sponsor mailing list request-sponsor at opensolaris.org
[request-sponsor] CR 6890550
Ok. If you want me to do the push for you, I can be the responsible engineer. I'm sure Saurabh can do it for you as well. Either way, you should get credit for the effort in the hg comments, since obviously the major part of this effort is just testing the change. - Garrett Masa Murayama wrote: - Original Message - Date: Tue, 13 Oct 2009 07:35:39 -0700 From: Garrett D'Amore garrett at damore.org To: Masayuki Murayama khf04453 at nifty.ne.jp CC: request-sponsor at opensolaris.org Subject: Re: [request-sponsor] CR 6890550 Masayuki Murayama wrote: I'm sorry if it is not a right mailing list for the issue. I'm the submitter of CR6890550 below. The responsible engineer of the cr commented that further tests would be required to add the new PCI device id to bfe driver. I'd like to do what are required, and to send the result, but there is no mail address to contact the engineer. Should I request for sponsor here, or is there another way? My SCA is OS0107 If you run the tests (specifically we need a good NICDRV run), then I'll be happy to sponsor your changes. - Garrett Garrett, Thank you very much. The CR will be resolved by adding an entry into /etc/driver_aliases. So, I don't feel I need a sponsor to change the source code. My job will be just to send the test result to the responsible engineer. If it will be more difficult than I expect, I'd like to ask your help. Now I'll get started contacting the responsible engineer. thanks, again. -masa regards, Masayuki Murayama - Original Message - Date: Mon, 12 Oct 2009 11:02:58 -0600 (MDT) From: bugmail-sender at Sun.COM Subject: CR 6890550 Updated, User 1-5Q-6307 now responsible engineer, P3 driver/bfe bfe should support pci14e4,4401 device To: undisclosed-recipients:; *Synopsis*: bfe should support pci14e4,4401 device Due to a change requested by User 1-5Q-6307, User 1-5Q-6307 is now the responsible engineer for: CR 6890550 changed on Oct 12 2009 by User 1-5Q-6307 === Field === New Value = === Old Value = === = DescriptionNew Note Responsible Engineer User 1-5Q-6307 Status 3-Accepted 1-Dispatched == === === === = *Change Request ID*: 6890550 *Synopsis*: bfe should support pci14e4,4401 device Product: solaris Category: driver Subcategory: bfe Type: Defect Subtype: Status: 3-Accepted Substatus: Priority: 3-Medium Introduced In Release: Introduced In Build: Responsible Engineer: User 1-5Q-6307 Keywords: opensolaris === *Description* === = Category solaris/driver (Hardware Support - Devices/Drivers) Sub-Category bfe Description As bfe driver for broadcom bcm4401 fast ethernet nic in snv124 supports only pci14e4,970c device, my bcm4401 based pci add-on card, which pc i vendor/device id is pci14e4,4401, is not detected right after snv124 installation. pci14e4,4402 and pci14e4,170c are also known as ids for the bcm4401 nic. So bfe should support these three devices too, I think Frequency Always Regression No Steps to Reproduce Just install snv124, then see /etc/driver_aliases. So, following command failed. ifconfig bfe0 plumb Expected Result The lines below should be also included in /etc/driver_aliases right aft er opensolaris installation. bfe pci14e4,4401 bfe pci14e4,4402 bfe pci14e4,170c Actual Result installing snv124, there is an entry for bfe below in /etc/driver_aliase s bfe pci14e4,970c Error Message(s) N/A Test Case N/A Workaround do following for my nic card update_drv -a -i pci14e4,4401 bfe Additional configuration information the node information in the output of prtconf -v for my bcm4401 based pc i add-on card: Node 0x1d assigned-addresses: 82040810..febfc000..00 00 2000 reg: 00040800.....02040810 .0 000...2000 compatible: 'pci14e4,4401.14e4.8401.1' + 'pci14e4,4401.14e4 .8 401' + 'pci14e4,8401' + 'pci14e4,4401.1' + 'pci14e4,4401' + 'pciclass,02000 0' + 'pciclass,0200
[request-sponsor] CR 6890550
Masayuki Murayama wrote: I'm sorry if it is not a right mailing list for the issue. I'm the submitter of CR6890550 below. The responsible engineer of the cr commented that further tests would be required to add the new PCI device id to bfe driver. I'd like to do what are required, and to send the result, but there is no mail address to contact the engineer. Should I request for sponsor here, or is there another way? My SCA is OS0107 If you run the tests (specifically we need a good NICDRV run), then I'll be happy to sponsor your changes. - Garrett regards, Masayuki Murayama - Original Message - Date: Mon, 12 Oct 2009 11:02:58 -0600 (MDT) From: bugmail-sender at Sun.COM Subject: CR 6890550 Updated, User 1-5Q-6307 now responsible engineer, P3 driver/bfe bfe should support pci14e4,4401 device To: undisclosed-recipients:; *Synopsis*: bfe should support pci14e4,4401 device Due to a change requested by User 1-5Q-6307, User 1-5Q-6307 is now the responsible engineer for: CR 6890550 changed on Oct 12 2009 by User 1-5Q-6307 === Field === New Value = === Old Value = DescriptionNew Note Responsible Engineer User 1-5Q-6307 Status 3-Accepted 1-Dispatched == === == = *Change Request ID*: 6890550 *Synopsis*: bfe should support pci14e4,4401 device Product: solaris Category: driver Subcategory: bfe Type: Defect Subtype: Status: 3-Accepted Substatus: Priority: 3-Medium Introduced In Release: Introduced In Build: Responsible Engineer: User 1-5Q-6307 Keywords: opensolaris === *Description* === = Category solaris/driver (Hardware Support - Devices/Drivers) Sub-Category bfe Description As bfe driver for broadcom bcm4401 fast ethernet nic in snv124 supports only pci14e4,970c device, my bcm4401 based pci add-on card, which pc i vendor/device id is pci14e4,4401, is not detected right after snv124 installation. pci14e4,4402 and pci14e4,170c are also known as ids for the bcm4401 nic. So bfe should support these three devices too, I think Frequency Always Regression No Steps to Reproduce Just install snv124, then see /etc/driver_aliases. So, following command failed. ifconfig bfe0 plumb Expected Result The lines below should be also included in /etc/driver_aliases right after opensolaris installation. bfe pci14e4,4401 bfe pci14e4,4402 bfe pci14e4,170c Actual Result installing snv124, there is an entry for bfe below in /etc/driver_aliases bfe pci14e4,970c Error Message(s) N/A Test Case N/A Workaround do following for my nic card update_drv -a -i pci14e4,4401 bfe Additional configuration information the node information in the output of prtconf -v for my bcm4401 based pci add-on card: Node 0x1d assigned-addresses: 82040810..febfc000.. 2000 reg: 00040800.....02040810.0 000...2000 compatible: 'pci14e4,4401.14e4.8401.1' + 'pci14e4,4401.14e4.8 401' + 'pci14e4,8401' + 'pci14e4,4401.1' + 'pci14e4,4401' + 'pciclass,02' + 'pciclass,0200' model: 'Ethernet controller' power-consumption: 0001.0001 devsel-speed: interrupts: 0001 max-latency: min-grant: subsystem-vendor-id: 14e4 subsystem-id: 8401 unit-address: '1' class-code: 0002 revision-id: 0001 vendor-id: 14e4 device-id: 4401 name: 'pci14e4,8401' *** (#1 of 2): 2009-10-12 13:58:28 GMT+00:00 User 1-F4SZV I didn't have access to the hardware and that's the reason I didn't add those PCI-ID. If you access to the hardware, can you do basic testing and let me kn ow the result? *** (#2 of 2): 2009-10-12 16:54:05 GMT+00:00 User 1-5Q-6307 === *Public Comments* === = === *Workaround* = === *Additional Details* = Targeted Release: Commit To Fix In Build: Fixed In Build: Integrated In Build: Verified In Build: See Also: 6882713, 6890551 Duplicate of: Hooks: Hook1: Hook2: Hook3: Hook4:
[request-sponsor] Sponsor sought for CR6625801 (*mv* mv.c macros could be cleaned up)
danny webster wrote: Hi, I'd like to request sponsorship for Bug ID 6625801 Synopsis *mv* mv.c macros could be cleaned up State 4-Defer:No Resource Available SCA: OS0243 User: dsw Cheers dan. ___ request-sponsor mailing list request-sponsor at opensolaris.org I'll sponsor it. Send me diffs, or a URL to a mercurial workspace with your changes. This should be trivial to fix, since the changes should not affect the binary. (So we can use elfcmp to verify that the binary has not changed as a result of your changes. :-) - Garrett
[request-sponsor] please remove 6730277 from request sponsor table
I've picked this one up, and am doing it myself without code from the original requester. (The original requester has been involved with code review and such, but the code is coming from Sun.) -- Garrett
[request-sponsor] please change ownership of 6650184
Lucy Wang (Xiuyan.Wang at Sun.COM) has been working with the requester/submitter, and should be noted as the sponsor rather than me. - Garrett
[request-sponsor] Requesting sponsor for CR #6799167 (real gcc build fails in libshell) ...
John Sonnenschein wrote: Sorry to butt in here, but I was under the impression that code should never make reference to the bug it fixes. Am I mistaken here? Normally yes. However in this case, I think since the workaround may need some explanation, its not a bad idea to reference it. - Garrett -JohnS On 2-Mar-09, at 10:05 AM, Roger A. Faulkner wrote: Date: Mon, 02 Mar 2009 16:20:44 +0100 From: Roland Mainz roland.mainz at nrubsig.org Subject: Re: [request-sponsor] Requesting sponsor for CR #6799167 (real gcc build fails in libshell) ... To: request-sponsor at opensolaris.org request-sponsor at opensolaris.org, Milan Jurik Milan.Jurik at sun.com, ksh93-integration-discuss ksh93-integration-discuss at opensolaris.org Roland Mainz wrote: This is a sponsor request to fix ([1]) CR #6799167 (http://bugs.opensolaris.org/view_bug.do?bug_id=6799167 - real gcc build fails in libshell). [1]=The fix is more a workaround since I don't know exactly how the ctf*-tools can be fixed. My contributor ID is OS0025. Webrev follows later when my hg clone is complete... Webrev is now available at http://cr.opensolaris.org/~gisburn/ksh93_integration_cr_6799167_001/ - can anyone give me a short code review for the change, please (we'll file a new bug in bugster to make sure the original issues doesn't get forgotten) ? The code change looks good to me (and compiles for me). (I've been concerned about the not-buildable-with-gcc issue for some time now. I thought I was the only one.) Nit: Could you break the comment into more than one line, to make it fit in 80-columns, something like: /* * Allocate one extra array entry as workaround for: * CR 6799167 real gcc build fails in libshell */ Thanks, Roger ___ request-sponsor mailing list request-sponsor at opensolaris.org ___ request-sponsor mailing list request-sponsor at opensolaris.org
[request-sponsor] Requesting sponsor for CR #6807179 (ksh93 does unneccesary |libc::getpwnam()| lookups for ~(modifer)pattern patterns)
Casper.Dik at Sun.COM wrote: Casper.Dik at Sun.COM wrote: This is a sponsor request to fix CR #6807179 (ksh93 does unneccesary |libc::getpwnam()| lookups for ~(modifer)pattern patterns) My contributor ID is OS0025. Webrev can be found at http://cr.opensolaris.org/~gisburn/ksh93_integration_cr_6807179_001/ (matching ksh93 test suite module comes later) I'll take this. I hope to get this in this build (110). Thanks! :-) So, if I can have some codereviewers then I can putback this change to build 110. LGTM. Ship it. -- Garrett Casper ___ request-sponsor mailing list request-sponsor at opensolaris.org
[request-sponsor] OpenSolaris enhancement: add support for the Broadcom 5780 chipset to the bge kernel driver
Bart Van Assche wrote: Hello Garrett, I understand the importance of the NICDRV test, and I really would like to run that test, but unfortunately I do not have sufficient time to do this (my contract with Q-layer finishes on Friday June 20, 2008). I can run the tests, if I can get access to hardware. The problem is, I haven't got any such hardware immediately at hand. If anyone has either a system they can ship me, or alternatively, I could accept remote access (via SSH) to a pair of systems -- one with this hardware, and one with some other GbE port, both running Solaris 10 or OpenSolaris, then I can run the tests remotely. The configuration for such remote access would need to be: Machine A: * ideally a dual core system, but a 2.0GHz or better CPU single core at minimum * one regular, non bcm5780 connection to the internet * a bcm5780 with a back-to-back ethernet cable to Machine B Machine B: * ideally a similar CPU configuration as machine A, at least 2.0GHz please * one regular connection to the internet * one non-bcm5780 (e.g. other bge or e1000g or rge) GbE connected to bcm5780 of machine A I'd need access to such a configuration for probably about 3-4 days to get the tests, assuming no issues are found during test. -- Garrett Bart. - Garrett D'Amore gdamore at sun.com wrote: Bart, The CRT advocate wants a more formal NICDRV test. I'm going to try to convince him that one is not needed, but if you're game, we'd really like to have a complete run done. The URL for NICDRV is here: http://opensolaris.org/os/community/device_drivers/projects/nicdrvtest/ It will take a while to run. Meanwhile I'll try again to convince the RTI advocate to let me putback your changes with the level of testing that you have already performed. If you have any questions about NICDRV, please let me know. I'd like to know in any case whether you're going to run the tests or not. ___ request-sponsor mailing list request-sponsor at opensolaris.org
[request-sponsor] OpenSolaris enhancement: add support for the Broadcom 5780 chipset to the bge kernel driver
Bart, The CRT advocate wants a more formal NICDRV test. I'm going to try to convince him that one is not needed, but if you're game, we'd really like to have a complete run done. The URL for NICDRV is here: http://opensolaris.org/os/community/device_drivers/projects/nicdrvtest/ It will take a while to run. Meanwhile I'll try again to convince the RTI advocate to let me putback your changes with the level of testing that you have already performed. If you have any questions about NICDRV, please let me know. I'd like to know in any case whether you're going to run the tests or not. -- Garrett Bart Van Assche wrote: Hello Garrett, We ran the following tests on a Tyan S3992-E motherboard (http://www.tyan.com/product_board_detail.aspx?pid=517): - Installed OpenSolaris build 89. - Activated the bge driver. - Verified whether ICMP ping, ftp, HTTP and NFS work fine over the bge interface. - Verified whether VLAN works fine on the bge interface. - Verified whether no more packets were lost than for other interfaces on the same network for 300 MB/s ICMP traffic between the interface and a Linux system (ran the following command on the Linux system: for ((i=0;i5;i++)); do ping -s 3 -f 10.100.92.1 -c 1 -q done). Bart. - Garrett D'Amore gdamore at opensolaris.org wrote: OK, thanks. Bart, I presume you've run some tests, can you tell me what the tests that you have run are, and on what particular hardware? -- Garrett Bonnie Corwin wrote: RE is Crisson Hou. Seems to know all about this and says you should sponsor. So I put this on the table. Thanks. Bonnie Garrett D'Amore wrote: I don't know, I've not investigated. Check with the RE, and if he can't sponsor, or is already doing the work and doesn't need/want this contribution, then I'll defer. Otherwise, I can step up and help out if needed. The changes look pretty obvious to me, actually. Its mostly just a matter of testing. -- Garrett Bonnie Corwin wrote: Hi Garrett, There is an RE on this bug already. Do you know if work is already happening inside Sun? If not, I'll put this on the table with you as sponsor. Thanks a lot. Bonnie Garrett D'Amore wrote: Bart Van Assche wrote: Hello, Can you please review the following enhancement: RFE ID: 6560313 (http://bugs.opensolaris.org/view_bug.do?bug_id=6560313). Synopsis: add support for the Broadcom 5780 chipset to the bge kernel driver. My full name: Bart Van Assche. Number assigned to my Sun Contributor Agreement: OS0226. Webrev: http://cr.opensolaris.org/~bvassche/broadcom-bcm5780-support-b90/ Thanks, Bart Van Assche Q-layer N.V. http://www.qlayer.com/ ___ request-sponsor mailing list request-sponsor at opensolaris.org This looks pretty good to me. I'd sponsor it, except I don't have access to the hardware to verify the change. If nobody else here does either, then I'll sponsor it anyway. (Anyone else with such hardware want to sponsor Bart?) -- Garrett ___ request-sponsor mailing list request-sponsor at opensolaris.org
[request-sponsor] Sponsor needed for CR 6710047
I'll take it. The change is pretty obvious. I presume you've run a system with this change and verified it still works. (I can't see any reason it wouldn't.) -- Garrett Cyril Plisko wrote: Anyone ? On Thu, Jun 5, 2008 at 3:54 PM, Cyril Plisko cyril.plisko at mountall.com wrote: Hi ! I am looking for sponsor for integrating fix for CR6710047 - lofi driver ignores the return value from ddi_create_minor_node() call [1] The webrev can be found at http://cr.opensolaris.org/~imp/6710047 [1] http://bugs.opensolaris.org/view_bug.do?bug_id=6710047 -- Regards, Cyril
[request-sponsor] CR #6668828 (Quagga SMF script may return random return code) ...
I'll pick this one up as well. -- Garrett Roland Mainz wrote: Hi! This is a sponsor request to fix CR #6668828 (Quagga SMF script may return random return code). My contributor ID is OS0025. Bye, Roland
[request-sponsor] CR #6667990 (quagga svc method script breaks with ksh93) ...
I'll sponsor this request. -- Garrett Roland Mainz wrote: Hi! This is a sponsor request to fix CR #6667990 (quagga svc method script breaks with ksh93). My contributor ID is OS0025. Bye, Roland
[request-sponsor] Bug ID - 4149430
I don't think ddi.h should bring in systm.h. Instead it should be the other way around, or possibly, systm.h should just have its macros removed. systm.h brings in other non-public definitions that have no business in the namespace when ddi.h is #included. -- Garrett Sanjay Nambiar wrote: Hi. I am Sanjay M Nambiar from Amrita Vishwa Vidyapeetham. me (Sanjay) (sanjaymn OS0150 ) and Chitra B(OS0233 chitraos) are interested in working on Bug ID: 4149430 Synopsis - include conflict between ddi.h and systm.h on min() and max() Category:Subcategory -kernel:header please see the file attached -- --- Thanks Regards Sanjay Chitra ___ request-sponsor mailing list request-sponsor at opensolaris.org
[request-sponsor] 6482159 kernel hangs in pcic_attach at boot time on FujitsuFMV6800MG laptop
No worries Masa-san. Just let me know when you want to move forward with it. :-) -- Garrett Masa Murayama wrote: - Original Message - Date: Wed, 16 Jan 2008 02:36:40 +0900 (JST) From: Masa Murayama khf04453 at nifty.ne.jp To: Garrett D'Amore garrett at damore.org Subject: Re: 6482159 kernel hangs in pcic_attach at boot time on FujitsuFMV68 00MG laptop Cc: Masa Murayama khf04453 at nifty.ne.jp, request-sponsor at opensolaris.org - Original Message - Date: Tue, 15 Jan 2008 09:14:14 -0800 From: Garrett D'Amore garrett at damore.org To: Masa Murayama khf04453 at nifty.ne.jp, request-sponsor at opensolaris.org Subject: 6482159 kernel hangs in pcic_attach at boot time on FujitsuFMV6800M G laptop I'm willing to sponsor this request, if you still have the diffs handy, and a machine capable of reproducing the problem. -- Garrett Thank you very much. Let me check that the latest solaris can boot on the laptop, because I'm using only windows2000 for long time, instead of solaris, and it have only 256M byte memory and addtional usb keyboard instead of broken built-in keyboard. I'll try that on this weekend. I'm sorry that I could not setup my laptop for installing the latest open solaris on the weekend. I think I'll need netboot environment to test the new kernel. I spent my time for other problems, including vfe and bfe issue. I'll try it again on the next weekend or later. I would like to notify you when I'll have been ready. best regards, -masa ___ request-sponsor mailing list request-sponsor at opensolaris.org
[request-sponsor] Request to work on a bug.
Bonnie Corwin wrote:
Hi,
Varrun Ramani offered a contribution for this bug on 12/18/07. It is
#40 under Awaiting Sponsor on the request-sponsor table.
Garrett, I assume you will sponsor Varrun for this bug. Let me know
if that's not correct.
It is correct, I offered to sponsor it.
-- Garrett
Thanks.
Bonnie
Garrett D'Amore wrote:
I'll sponsor you for this one.
-- Garrett
Neena A S wrote:
I would like to work on the bug having id- 6614275.
The following are the bug description :
In /usr/include/getopt.h, struct option is declared as:
struct option {
char *name; /* name of long option */
int has_arg;/* whether option takes an argument */
int *flag; /* if not NULL, set *flag to val when option
found */
int val;/* if flag is not NULL, value to set *flag
to. */
/* if flag is NULL, return value */
};
According to the Solaris man page and the GNU documentation for
getopt_long(), the name member should be of type const char*.
category:-library
subcategory:-libc
Thanking you.
Neena A S
SCA no - OS0161
Amrita vishwa vidyapeetham.
___
request-sponsor mailing list
request-sponsor at opensolaris.org
___
request-sponsor mailing list
request-sponsor at opensolaris.org
[request-sponsor] 6482159 kernel hangs in pcic_attach at boot time on FujitsuFMV6800MG laptop
I'm willing to sponsor this request, if you still have the diffs handy, and a machine capable of reproducing the problem. -- Garrett
[request-sponsor] Bug 6555164 : remove pointless bmac.h header file
I will sponsor Rishi Nair to work on this bug. -- Garrett
[request-sponsor] Request sponsor for a new Project (Observability)
I think you're asking the wrong list. request-sponsor is for external contributions who need a putback/rti sponsor. I think you're looking for an ARC or C team sponsor? You might want to check sac.eng if you're looking for an ARC sponsor. -- Garrett Amir Javanshir wrote: Hi all I would like to submit a new project request and hopefully get a sponsor. Project Name: HAR (Hardware Activity Reporter) Project Description The goal of this project is to develop a performance monitoring tool that samples hardware counters in the system (primarily cpu counters, but could extend to bus counters) to produce higher-level metrics (eg, mips, flops, cache miss, stall rate, bus utilization) which can guide a bottleneck analysis and performance tuning process. There exists a first release of HAR, developed internally at Sun, that only looks at cpu counters and supports currently only UltraSPARC1-4 (not 4+) Pentium3 systems. The open-sourcing of the existing HAR code has been approved by Sun. There are a few users of HAR out there that keep asking for newer releases (eg eBay) and support for recent hardware. The purpose of open-sourcing HAR is to provide a proper place for the continued development dissemination of HAR. The primary task will be to port HAR to Solaris 10 and libcpc2 so Niagara, AMD and modern Intel processors can be supported. Related Projects There are no known related projects or dependencies. HAR will build directly on top of libcpc2 for accessing cpu counters. Access to bus counters has not been researched yet. Current Team We are already 3 engineers working on this subject Cheers, Amir Javanshir This message posted from opensolaris.org ___ request-sponsor mailing list request-sponsor at opensolaris.org
[request-sponsor] Tehuti OpenSolaris drivers
Once I know the CR number (which has yet to be assigned, due to the way the triage system works, which mere mortals like myself don't fully understand...) I'll be happy to act as your sponsor for this case. You should get an e-mail message in the next day or two with the CR number. Please respond with the CR number, and then we'll have to get you added to the list of outstanding CRs. Also, you'll need to know your Sun Contributor Agreement number. As I understand that you have faxed it in, you need to get back the number. Once you have got a response from that, please let us know your SCA# as well as the CR #. Thanks. -- Garrett Alexander Indenbaum wrote: Hello, I've submitted a bug/RFE with Synopsis Tehuti 10GbE support in OpenSolaris. We have a year old ALPHA quality GLDv3 based driver, which was tested on SunOS 5.10 Generic_Patch_118844-30 powered by amd64. We produced the driver based on Nevada b40 GLDv3 header file using Sun C 5.7 Patch 117837-04 compiler. The driver provides fully functional full duplex TCP/IP network interface. The release is stable enough to support iperf stress tool. Solaris Driver Known Issues List: None what so ever? :) ? VLAN hardware offload interface not implemented ? Big Endian CPU architecture is not supported ? Multicast filtering hardware offload interface not implemented ? Only one port is supported ? NDD Solaris management interface not implemented ? RX performance is far from optimal Our main development platform is Linux and its driver provides all the mentioned missing features and good performance. The Linux driver is open source and could be used as reference implementation: http://git.kernel.org/?p=linux/kernel/git/davem/net-2.6.24.git;a=commitdiff;h=54406a1c0281af619e4d90bd7e719562be90216e We ready to release driver sources under CDDL license and it could be cool if Tehuti driver could be a part of OpenSolaris base distribution. Thank you, Alexander Indenbaum
[request-sponsor] Tehuti OpenSolaris drivers
Alexander Indenbaum wrote: Garrett, I'll get back to you with the tracking numbers as soon as I get those. I'm pretty clear with Sun Contributor Agreement number since I faxed it and expect human intervention to finish the process. Is there any way to track the progress? Not that I know of. You could try e-mailing Bonnie Corwin. But at this point, I'd just sit tight for a day or two. If you've not heard back by Friday, then we'll escalate. I'm a little bit confused about CR# though. I expected to get id upon bug submission, but I got success message from web GUI without any id. Is it normal? Should I resubmit the bug once I have Sun Contributor Agreement number? No. Its normal and a result of the fact that there is an intermediate human step. Your initial submission goes into a triage queue, and a human checks it before filing a real bug on your behalf. Its an annoying artifact of the fact that bug tracking database is not public, and that we don't have a way to automatically vet CR submissions. You should get an e-mail response in a day or two. - Garrett Alexander Indenbaum -Original Message- From: Garrett D'Amore [mailto:garrett at damore.org] Sent: Tuesday, September 25, 2007 5:36 PM To: Alexander Indenbaum Cc: request-sponsor at opensolaris.org; 'Nick Bhavsar' Subject: Re: Tehuti OpenSolaris drivers Once I know the CR number (which has yet to be assigned, due to the way the triage system works, which mere mortals like myself don't fully understand...) I'll be happy to act as your sponsor for this case. You should get an e-mail message in the next day or two with the CR number. Please respond with the CR number, and then we'll have to get you added to the list of outstanding CRs. Also, you'll need to know your Sun Contributor Agreement number. As I understand that you have faxed it in, you need to get back the number. Once you have got a response from that, please let us know your SCA# as well as the CR #. Thanks. -- Garrett Alexander Indenbaum wrote: Hello, I've submitted a bug/RFE with Synopsis Tehuti 10GbE support in OpenSolaris. We have a year old ALPHA quality GLDv3 based driver, which was tested on SunOS 5.10 Generic_Patch_118844-30 powered by amd64. We produced the driver based on Nevada b40 GLDv3 header file using Sun C 5.7 Patch 117837-04 compiler. The driver provides fully functional full duplex TCP/IP network interface. The release is stable enough to support iperf stress tool. Solaris Driver Known Issues List: None what so ever? :) . VLAN hardware offload interface not implemented . Big Endian CPU architecture is not supported . Multicast filtering hardware offload interface not implemented . Only one port is supported . NDD Solaris management interface not implemented . RX performance is far from optimal Our main development platform is Linux and its driver provides all the mentioned missing features and good performance. The Linux driver is open source and could be used as reference implementation: http://git.kernel.org/?p=linux/kernel/git/davem/net- 2.6.24.git;a=commitdiff;h=54406a1c0281af619e4d90bd7e719562be90216e We ready to release driver sources under CDDL license and it could be cool if Tehuti driver could be a part of OpenSolaris base distribution. Thank you, Alexander Indenbaum
[request-sponsor] close 6487387
Please update the sponors web page for 6487387... I putback the change myself. :-) I am now part of Sun. :-) -- Garrett
[request-sponsor] close 6487387
Bonnie Corwin wrote: Hi Garrett, Thanks for letting me know. I'll put this one in the 'accounted for by other means' section. Well, the code was submitted while I was not a Sun employee... so I think you should mark it closed per the normal process... its just instead of my sponsor doing the putback I did it. Question - what about 6484159 and 6497366? Do you want me to just leave those alone for the moment? Yes, please. Note that some of this work is done on my own time, so it is reasonable for it to get counted as community work. Also, some of the work includes code that was contributed by Tadpole, so it definitely counts. -- Garrett Thanks. Bonnie Garrett D'Amore wrote: Please update the sponors web page for 6487387... I putback the change myself. :-) I am now part of Sun. :-) -- Garrett ___ request-sponsor mailing list request-sponsor at opensolaris.org
[request-sponsor] adjustments
I have two contributor ids now (one for work I submit personally, and one for work submitted as an employee of Tadpole/General Dynamics). I would like to update some cases so that instead of OS0034, my alternate work SCA of OS0057 is used. Specifically these two cases should be changed to using OS0057: 6487387 pcic driver contains obsolete private Tadpole code that should be removed 6484159 kb8042 should provide mappings for common keys on Tadpole hardware Thanks. -- Garrett D'Amore, Principal Software Engineer Tadpole Computer / Computing Technologies Division, General Dynamics C4 Systems http://www.tadpolecomputer.com/ Phone: 951 325-2134 Fax: 951 325-2191
[request-sponsor] administrivia: 4514779 is closed
I notice on http://www.opensolaris.org/os/bug_reports/request_sponsor/ that bug 4514779 is marked as still in progress. In fact, this bug was fixed with the putback of 4521640. (4514779 was marked a duplicate, as 4521640 was a superset.) Can someone update the web page accordingly (probably accounting by means other than putback? Although the red state on that page makes one believe that there was some problem with the bug, which is just not the case here.) Also, note that 6487582 has been putback as well, so probably that needs to be updated. I don't know how all this page gets updated, but I wanted to point it out. Thanks! -- Garrett D'Amore, Principal Software Engineer Tadpole Computer / Computing Technologies Division, General Dynamics C4 Systems http://www.tadpolecomputer.com/ Phone: 951 325-2134 Fax: 951 325-2191
[request-sponsor] looking for cardbus sponsor
I need someone who can sponsor me for CR 6487387, which basically entails cleaning some obsolete Tadpole-specific code from the Solaris pcic driver. Anyone willing to help out? -- Garrett D'Amore, Principal Software Engineer Tadpole Computer / Computing Technologies Division, General Dynamics C4 Systems http://www.tadpolecomputer.com/ Phone: 951 325-2134 Fax: 951 325-2191
[request-sponsor] request sponsor to unify xargs/xpg6/xargs
The CR for this is 6487582. Basically, there is some trivial POSIX behavior (-E is permitted and interpreted to mean no eofstr, read the man page for xargs(1) for more info) that can (and should) be applied to the /usr/bin/xargs version. Then /usr/xpg6/bin/xargs can just be a link to /usr/bin/xargs I suspect this will require a trivial fasttrack (primarily because of the man page change), and I have drafted a simple fasttrack already. The code and manual page changes are trivial. -- Garrett D'Amore, Principal Software Engineer Tadpole Computer / Computing Technologies Division, General Dynamics C4 Systems http://www.tadpolecomputer.com/ Phone: 951 325-2134 Fax: 951 325-2191
[request-sponsor] request for sponsor to add synaptics support
Casper.Dik at Sun.COM wrote: Well, I've never _seen_ a Ferrari laptop. But our systems have a 4 scroll buttons, plus the normal 3 buttons, giving a total of 7 buttons. They all work. Pretty much like the Ferrari. The reason why I originally id my driver was the ability to use the buttons then the next feature was scrolling (which is the thing I miss and which I can't even get to work on Windows anymore) Well, I'm not sure what exactly you mean here. The Windows drivers allows you to scroll by moving your finger around (a selected) edge. Both horizontal and vertical, if you wish. Yes, our driver supports that. I very much like that feature and implemented it in my driver. Also, do your scroll buttons auto-repeat? (I know that the touchpad does not so you have to fake it) I have to check into that, because I'm not sure. -- Garrett Casper -- Garrett D'Amore, Principal Software Engineer Tadpole Computer / Computing Technologies Division, General Dynamics C4 Systems http://www.tadpolecomputer.com/ Phone: 951 325-2134 Fax: 951 325-2191
[request-sponsor] request for sponsor to add synaptics support
Casper.Dik at Sun.COM wrote: I am told that there may be a synaptics driver in casper's frkit. If so, I've not checked it out yet. Our driver just behaves as a vuid module. (Casper, can you comment on this?) That driver replaced the Xorg mouse_drv.so module. We also have a very nice Tcl/Tk configuration and test UI, that could be integrated along with this. That's cewl. Does it support all the extended buttons like we have on our ferrari's? Well, I've never _seen_ a Ferrari laptop. But our systems have a 4 scroll buttons, plus the normal 3 buttons, giving a total of 7 buttons. They all work. The reason why I originally id my driver was the ability to use the buttons then the next feature was scrolling (which is the thing I miss and which I can't even get to work on Windows anymore) Well, I'm not sure what exactly you mean here. -- Garrett Casper -- Garrett D'Amore, Principal Software Engineer Tadpole Computer / Computing Technologies Division, General Dynamics C4 Systems http://www.tadpolecomputer.com/ Phone: 951 325-2134 Fax: 951 325-2191
[request-sponsor] looking for a sponsor to help with getting some ps2 key maps to improve support for Tadpole/Ultra3 systems
Many Tadpole hardware platforms (including the Ultra 3 systems that were being sold until recently) have internal keyboards. These keyboards have Sun keys for things like Stop, Again, Props, etc. They also have a Compose key instead of a Windows Menu key. I would like to add the mappings required to allow Ultra 3 and Tadpole to be able to access the full range of keys. Its a pretty small set of changes, actually. I've filed a bug requesting the change (don't know the number yet), and I'd like to work on it myself. I do need a sponsor though. Can anyone help me out? Thanks! -- Garrett D'Amore, Principal Software Engineer Tadpole Computer / Computing Technologies Division, General Dynamics C4 Systems http://www.tadpolecomputer.com/ Phone: 951 325-2134 Fax: 951 325-2191
[request-sponsor] kstat const changes
I'm requesting a sponsor to handle the kstat changes to make kstat_create, etc. take const char * instead of char *. I sent mail about this to osol-code recently. The CR# I got after filing the bug report is CR 6461778 Created P4 opensolaris/triage-queue kstat_create, named_init, etc. should use constified char * Peter Memishian had volunteered to take this on, but I want to make sure all my ducks are in a row, so I'm formally requesting a sponsor for this. Note that this probably needs a PSARC fast-track because it means a compatible API change to make the char * arguments to kstat_create, kstat_named_init, etc. use const char * instead of char *. It probably also needs a man page change. The diffs themselves are super trivial, and I can pass them on if anyone wants to see them first. Thanks! -- Garrett D'Amore, Principal Software Engineer Tadpole Computer / Computing Technologies Division, General Dynamics C4 Systems http://www.tadpolecomputer.com/ Phone: 951 325-2134 Fax: 951 325-2191
[request-sponsor] platform support for TAD,Viper (CR 6458566)
Darren J Moffat wrote: Garrett D'Amore wrote: I would like to work on getting the core platform support (namely /platform links and the custom platmod support) for TAD,Viper into OpenSolaris. The bug came in with CR 6458566, and it is not in b.o.o yet. I'll take this one, if or no other reason than Garrett and I have worked together before. Note that this will need a quick simple ARC case to reserve the name into $PLATFORM namespace, I'll sponsor that part as well. Great. Okay, so I've got a platmod that seems to work, and I've got stuff to add to the following packages: SUNWcakr.u SUNWcar.u SUNWkvm.u SUNWhea Essentially all this does is set up the /platform and /usr/platform links, and populate an initial platmod and ppm.conf file. (From uts/sun4u/viper.) Here's the system info for this system: # uname -a SunOS bullfrog 5.11 snv_44 sun4u sparc TAD,Viper There will be future stuff we want to add (primarily for power management), but we can do that as a separate case. For now I think my code is pretty much ready to go. I'm in the process of trying to make sure our company has an SCA in place. What else do I need to do to make this happen? (I.e. what is the next step?) -- Garrett D'Amore, Principal Software Engineer Tadpole Computer / Computing Technologies Division, General Dynamics C4 Systems http://www.tadpolecomputer.com/ Phone: 951 325-2134 Fax: 951 325-2191
[request-sponsor] platform support for TAD,Viper (CR 6458566)
I would like to work on getting the core platform support (namely /platform links and the custom platmod support) for TAD,Viper into OpenSolaris. The bug came in with CR 6458566, and it is not in b.o.o yet. -- Garrett D'Amore, Principal Software Engineer Tadpole Computer / Computing Technologies Division, General Dynamics C4 Systems http://www.tadpolecomputer.com/ Phone: 951 325-2134 Fax: 951 325-2191
