Re: kern/168520: [ng_ubt] [patch] "option VIMAGE" kernel with ng_ubt.ko cause kernel panic
Synopsis: [ng_ubt] [patch] "option VIMAGE" kernel with ng_ubt.ko cause kernel panic Responsible-Changed-From-To: freebsd-bugs->rodrigc Responsible-Changed-By: rodrigc Responsible-Changed-When: Fri Jul 12 00:56:25 PDT 2013 Responsible-Changed-Why: . http://www.freebsd.org/cgi/query-pr.cgi?pr=168520 ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
misc/180497: kbdcontrol cannot override function keys < 65
>Number: 180497 >Category: misc >Synopsis: kbdcontrol cannot override function keys < 65 >Confidential: no >Severity: non-critical >Priority: low >Responsible:freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Jul 12 15:30:00 UTC 2013 >Closed-Date: >Last-Modified: >Originator: Kip Coul >Release:FreeBSD 9.1 amd64 >Organization: Medlo >Environment: FreeBSD freebsd 9.1-RELEASE FreeBSD 9.1-RELEASE #0 r243825: Tue Dec 4 09:23:10 UTC 2012 r...@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 >Description: The kbdcontrol utility can be used to define specific values for the function keys. See here: http://www.freebsd.org/cgi/man.cgi?query=atkbd&apropos=0&sektion=0&manpath=FreeBSD+9.1-RELEASE&arch=default&format=html It is stated that the function keys can be overridden using kbdcontrol -f # s where '#' is a number from 1 to 96 and 's' is a string that will be outputted. When '#' is between 65 and 96 (unassigned functions), this works. However, this does not work for functions keys between 1 and 64! >How-To-Repeat: Type kbdcontrol -f 1 "string" then click F1 on your keyboard and see that "string" is not displayed. >Fix: >Release-Note: >Audit-Trail: >Unformatted: ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
Re: kern/139271: commit references a PR
The following reply was made to PR kern/139271; it has been noted by GNATS.
From: dfil...@freebsd.org (dfilter service)
To: bug-follo...@freebsd.org
Cc:
Subject: Re: kern/139271: commit references a PR
Date: Fri, 12 Jul 2013 18:02:24 + (UTC)
Author: marius
Date: Fri Jul 12 18:02:10 2013
New Revision: 253278
URL: http://svnweb.freebsd.org/changeset/base/253278
Log:
MFC: r240981, r240990, r240992, r244695
Add 32-bit ABI compat shims. Those are necessary for i386 binary-only
tools like sysutils/hpacucli (HP P4xx RAID controller management
suite) working on amd64 systems.
PR: 139271
Submitted by:Kazumi MORINAGA, Eugene Grosbein
Approved by: re (kib)
Modified:
stable/9/sys/dev/pci/pci_user.c
Directory Properties:
stable/9/sys/ (props changed)
stable/9/sys/dev/ (props changed)
Modified: stable/9/sys/dev/pci/pci_user.c
==
--- stable/9/sys/dev/pci/pci_user.cFri Jul 12 17:37:05 2013
(r253277)
+++ stable/9/sys/dev/pci/pci_user.cFri Jul 12 18:02:10 2013
(r253278)
@@ -225,6 +225,51 @@ struct pci_io_old {
u_int32_t pi_data;/* data to write or result of read */
};
+#ifdef COMPAT_FREEBSD32
+struct pci_conf_old32 {
+ struct pcisel_old pc_sel; /* bus+slot+function */
+ uint8_t pc_hdr; /* PCI header type */
+ uint16_tpc_subvendor; /* card vendor ID */
+ uint16_tpc_subdevice; /* card device ID, assigned by
+ card vendor */
+ uint16_tpc_vendor; /* chip vendor ID */
+ uint16_tpc_device; /* chip device ID, assigned by
+ chip vendor */
+ uint8_t pc_class; /* chip PCI class */
+ uint8_t pc_subclass;/* chip PCI subclass */
+ uint8_t pc_progif; /* chip PCI programming interface */
+ uint8_t pc_revid; /* chip revision ID */
+ charpd_name[PCI_MAXNAMELEN + 1]; /* device name */
+ uint32_tpd_unit;/* device unit number (u_long) */
+};
+
+struct pci_match_conf_old32 {
+ struct pcisel_old pc_sel; /* bus+slot+function */
+ charpd_name[PCI_MAXNAMELEN + 1]; /* device name */
+ uint32_tpd_unit;/* Unit number (u_long) */
+ uint16_tpc_vendor; /* PCI Vendor ID */
+ uint16_tpc_device; /* PCI Device ID */
+ uint8_t pc_class; /* PCI class */
+ pci_getconf_flags_old flags;/* Matching expression */
+};
+
+struct pci_conf_io32 {
+ uint32_tpat_buf_len;/* pattern buffer length */
+ uint32_tnum_patterns; /* number of patterns */
+ uint32_tpatterns; /* pattern buffer
+ (struct pci_match_conf_old32 *) */
+ uint32_tmatch_buf_len; /* match buffer length */
+ uint32_tnum_matches;/* number of matches returned */
+ uint32_tmatches;/* match buffer
+ (struct pci_conf_old32 *) */
+ uint32_toffset; /* offset into device list */
+ uint32_tgeneration; /* device list generation */
+ pci_getconf_status status; /* request status */
+};
+
+#define PCIOCGETCONF_OLD32 _IOWR('p', 1, struct pci_conf_io32)
+#endif/* COMPAT_FREEBSD32 */
+
#define PCIOCGETCONF_OLD_IOWR('p', 1, struct pci_conf_io)
#define PCIOCREAD_OLD _IOWR('p', 2, struct pci_io_old)
#define PCIOCWRITE_OLD _IOWR('p', 3, struct pci_io_old)
@@ -295,7 +340,71 @@ pci_conf_match_old(struct pci_match_conf
return(1);
}
-#endif
+#ifdef COMPAT_FREEBSD32
+static int
+pci_conf_match_old32(struct pci_match_conf_old32 *matches, int num_matches,
+struct pci_conf *match_buf)
+{
+ int i;
+
+ if ((matches == NULL) || (match_buf == NULL) || (num_matches <= 0))
+ return(1);
+
+ for (i = 0; i < num_matches; i++) {
+ if (match_buf->pc_sel.pc_domain != 0)
+ continue;
+
+ /*
+ * I'm not sure why someone would do this...but...
+ */
+ if (matches[i].flags == PCI_GETCONF_NO_MATCH_OLD)
+ continue;
+
+ /*
+ * Look at each of the match flags. If it's set, do the
+ * comparison. If the comparison fails, we don't have a
+ * match, go on to the next item if there is one.
+ */
+ if (((matches[i].flags & PCI_GETCONF_MATCH_BUS_OLD) != 0) &&
+ (match_buf->pc_sel.pc_bus != matches[i].pc_sel.pc_bus))
+ cont
misc/180521: Configuring jail in rc.conf fails to set the jail name correctly
>Number: 180521
>Category: misc
>Synopsis: Configuring jail in rc.conf fails to set the jail name
>correctly
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible:freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Fri Jul 12 19:20:01 UTC 2013
>Closed-Date:
>Last-Modified:
>Originator: Frank Leonhardt
>Release:9.0 (and others)
>Organization:
>Environment:
n/a
>Description:
When you configure a jail in rc.conf you give the jail a name and refer to this
when using the "service" command to turn it on and off subsequently. However,
the jail name is not set as far as the jail system is concerned - if you use
jls -v, for example, it will be seen that the name is the same as the jail-ID.
This is the default for the "jail" command when no name is specified, but it's
not helpful when you've named a jail and might reasonably want to go on
referring to it by that name.
>How-To-Repeat:
Create a jailed environments in /usr/jail1, jail2, jail3 &c
Add the following to rc.conf:
jail_enable="YES"
jail_list="jail1 jail2 jail3"
jail_jail1_rootdir="/usr/jail1"
jail_jail1_hostname="jail1.yourdomain"
jail_jail1_ip="192.168.1.211"
And so on...
Boot the machine or start a jail with:
service jail start jail1
or
/etc/rc.d/jail start jail1
Check to see if it's actually called jail1:
jls -v
Output will be:
bsd9-1# jls -v
JID Hostname Path
Name State
CPUSetID
IP Address(es)
5 jail1.yourdomain /usr/jail1
4 ACTIVE
5
192.168.1.215
It should say "jail1" in the position where it says "4" This fails every time!
>Fix:
Easy...
On line 647 of /etc/rc.d/jail add the -n option.
Current:
eval ${_setfib} jail ${_flags} -i ${_rootdir} ${_hostname} \
\"${_addrl}\" ${_exec_start} > ${_tmp_jail} 2>&1 \
${_tmp_jail} 2>&1 \
Release-Note:
>Audit-Trail:
>Unformatted:
___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
Re: misc/180521: Configuring jail in rc.conf fails to set the jail name correctly
The following reply was made to PR misc/180521; it has been noted by GNATS. From: Frank Leonhardt To: bug-follo...@freebsd.org, freebsd-...@fjl.co.uk Cc: Subject: Re: misc/180521: Configuring jail in rc.conf fails to set the jail name correctly Date: Sat, 13 Jul 2013 01:56:55 +0100 This is a multi-part message in MIME format. --050600060506040809070807 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit I see this has now been fixed in 9.1 and have tracked the change to revision 238102 - the wording meant I didn't find it when I searched earlier. Please ignore! --050600060506040809070807 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit I see this has now been fixed in 9.1 and have tracked the change to revision 238102 - the wording meant I didn't find it when I searched earlier. Please ignore! --050600060506040809070807-- ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
