[Bug 240853] Any moderate I/O panics the kernel when MAC_BIBA + multilabel is enabled

2019-09-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240853

Kubilay Kocak  changed:

   What|Removed |Added

   See Also||https://bugs.freebsd.org/bu
   ||gzilla/show_bug.cgi?id=2309
   ||62
   Keywords||crash, needs-qa
   Assignee|b...@freebsd.org|f...@freebsd.org
 Status|New |Open
 CC||f...@freebsd.org,
   ||mckus...@freebsd.org

--- Comment #1 from Kubilay Kocak  ---
Thank you for your report

Could you please include more information, including:

- Exact FreeBSD version (uname -a)
- /var/run/dmesg.boot output (as an attachment)
- Check and confirm that the file system is clean (fsck -fy in single user), or
report back if it is not
- See if you can obtain a kernel panic backtrace [1], and in particular try to
catch the initial "panic message"
- Clarify whether or not the panic is reproducible *without* MAC_BIBA and/or
multilabel enabled (test each combination)

[1]
https://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug.html#kerneldebug-obtain

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 240856] sqrt problem

2019-09-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240856

Bug ID: 240856
   Summary: sqrt problem
   Product: Base System
   Version: 12.0-STABLE
  Hardware: amd64
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: misc
  Assignee: b...@freebsd.org
  Reporter: heinrich.a...@iml.unibe.ch

if I compile :

#include 

double Summx2 = 2.0;
double StandardDeviation;

int main (int argc, char **argv)
{
StandardDeviation = sqrt(Summx2);

return 0;
}

with :
gcc `pkg-config --cflags gtk+-3.0` -o "test" "test.c" `pkg-config --libs
gtk+-3.0`

I receive
/usr/local/bin/ld: /tmp//ccQtgX7c.o: undefined reference to symbol
'sqrt@@FBSD_1.0'
/usr/local/bin/ld: /lib/libm.so.5: error adding symbols: DSO missing from
command line
collect2: error: ld returned 1 exit status

Its only the problem part I need gtk for display the GUI, the full programm ist
to long.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 239961] 13.0-CURRENT freezes on Powermac G5 7,2

2019-09-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239961

Jost Menke  changed:

   What|Removed |Added

 Resolution|--- |Overcome By Events
 Status|New |Closed

--- Comment #2 from Jost Menke  ---
I found out that a quad port ethernet card which was built into the system
caused the problem. The card works fine under Debian though. Seems to be an old
problem somebody already posted a couple of years ago on the mailing list:
https://lists.freebsd.org/pipermail/freebsd-ppc/2012-August/005801.html

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 240856] sqrt problem

2019-09-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240856

--- Comment #1 from Andriy Gapon  ---
sqrt is provided by libm.
That's what the error message tells you.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 240871] snd_hda: Add Intel Comet Lake and Ice Lake support

2019-09-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240871

Bug ID: 240871
   Summary: snd_hda: Add Intel Comet Lake and Ice Lake support
   Product: Base System
   Version: CURRENT
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Many People
  Priority: ---
 Component: kern
  Assignee: b...@freebsd.org
  Reporter: n...@neelc.org

Created attachment 207888
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=207888&action=edit
Patch (Revision 1)

Add the PCI IDs for Intel Comet Lake and Ice Lake PCHs.

This patch was built using the same logic as my Cannon Lake patch, however this
patch is untested as I lack hardware with Comet Lake and Ice Lake, so other
people will need to test this patch.

Inspired by Linux commits d4c2ccdb5855ce8786ebc66f7405096065d0c198 (Comet Lake)
and 491f833134ac474434e1c950925c58b2ac13ca72 (Ice Lake).

Phabricator: https://reviews.freebsd.org/D21818

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 240875] usr.sbin/sysrc: If the file to be modified does not exist, an error message is displayed

2019-09-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240875

Bug ID: 240875
   Summary: usr.sbin/sysrc: If the file to be modified does not
exist, an error message is displayed
   Product: Base System
   Version: CURRENT
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: bin
  Assignee: b...@freebsd.org
  Reporter: jldu...@gmail.com

Created attachment 207890
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=207890&action=edit
sysrc.subr patch obtained from
https://github.com/freebsd/poudriere/pull/708#issuecomment-526753174

Currently, with sysrc, if the file to be modified does not exist, an error
message is displayed.

In this case, there is no /etc/rc.conf:

root@test:~ # sysrc hostname="test.example.com"
awk: can't open file /etc/rc.conf
 source line number 1
hostname:  -> test.example.com

The patch fixes this situation.

This patch was created by @dteske, obtained from
https://github.com/freebsd/poudriere/pull/708#issuecomment-526753174

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 240837] crash with 12.1-BETA1

2019-09-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240837

Michael Tuexen  changed:

   What|Removed |Added

   Assignee|b...@freebsd.org|tue...@freebsd.org
 Status|New |In Progress

--- Comment #3 from Michael Tuexen  ---
The problem was fixed for head in
https://svnweb.freebsd.org/changeset/base/352386
, which was MFCed to stable/12 in
https://svnweb.freebsd.org/changeset/base/352508. I missed to MFS the fix to
releng.12.1, which was branched at r352480.

What happened is that overflowing the sackblks[] changed sackhint.nexthole to
an invalid value which was not NULL. From the core provided:

  sackblks = {{
  start = 0xc1f54a52, 
  end = 0xc1f54ffe
}, {
  start = 0xc1f5229e, 
  end = 0xc1f5284a
}, {
  start = 0xc1f5229e, 
  end = 0xc1f5284a
}, {
  start = 0xc1f5229e, 
  end = 0xc1f5284a
}, {
  start = 0xc1f5229e, 
  end = 0xc1f5284a
}, {
  start = 0xc1f51746, 
  end = 0xc1f51cf2
}}, 
  sackhint = {
nexthole = 0xc1f5119ac1f50bee, 
sack_bytes_rexmit = 0x0, 
last_sack_ack = 0x3fe9f863, 
ispare = 0x0, 
sacked_bytes = 0xb65, 
_pad1 = {0x0}, 
_pad = {0x0}
  },

Since I can't get any changes in BETA2 anymore, the fix will be in BETA3 or
RC1.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 240700] [META] FreeBSD 12.1-RELEASE blockers

2019-09-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240700

Glen Barber  changed:

   What|Removed |Added

Version|CURRENT |12.1-RELEASE

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 240881] acpi_lid: dev.acpi_lid.0.state: 0 after resume (lid opened)

2019-09-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240881

Bug ID: 240881
   Summary: acpi_lid: dev.acpi_lid.0.state: 0 after resume (lid
opened)
   Product: Base System
   Version: CURRENT
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: kern
  Assignee: b...@freebsd.org
  Reporter: joha...@freebsd.org

As the title says, state remains = 0 after resume by opening the lid.

This happens when I suspend with command 'acpiconf -s3' and the lid is already
closed (for example suspending while an external screen is connected)

Dell Latitude 2018 laptop
FreeBSD 13-CURRENT as of this date.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 240881] acpi_lid: dev.acpi_lid.0.state: 0 after resume (lid opened)

2019-09-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240881

--- Comment #1 from Johannes Lundberg  ---
Some more consistent test results.

If lid switch does nothing, dev.acpi_lid.0.state updates as it should on lid
open/close.

If lid switch suspends, or if I wake up from suspend by opening the lid, state
remains 0.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 240485] ig4: Add Cannon Lake LP and H I2C Controller IDs

2019-09-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240485

--- Comment #8 from Vladimir Kondratyev  ---
(In reply to Neel Chauhan from comment #7)
> The touchpad does not work with this patch.
That is strange. I see no attempts to read HID descriptor by your I2C device in
dmesg. Such attempts should look like:
iichid0: HID command I2C_HID_CMD_DESCR at 0xXX

Do you observe such a lines in dmesg? They precedes first communication with
HID device through I2C so they do not depend on state of the ig4 driver.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 240889] mount -t nozfs, noufs, nodevfs, notmpfs - does not work as advertised in man page

2019-09-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240889

Bug ID: 240889
   Summary: mount -t nozfs,noufs,nodevfs,notmpfs - does not work
as advertised in man page
   Product: Base System
   Version: 12.1-RELEASE
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Many People
  Priority: ---
 Component: bin
  Assignee: b...@freebsd.org
  Reporter: verma...@interia.pl

>From man 8 mount page:


  -t [no]type[,type ...]
  The argument following the -t is used to indicate the file system
  type.  The type ufs is the default.  The -t option can be used to
  indicate that the actions should only be taken on file systems of
  the specified type.  More than one type may be specified in a
  comma separated list.  The list of file system types can be
  prefixed with no to specify the file system types for which
  action should not be taken.  For example, the mount command:

mount -a -t nonfs,nullfs

  mounts all file systems except those of type NFS and NULLFS.

  The default behavior of mount is to pass the -t option directly
  to the nmount(2) system call in the fstype option.

  However, for the following file system types: cd9660, mfs,
  msdosfs, nfs, nullfs, smbfs, udf, and unionfs mount will not call
  nmount(2) directly and will instead attempt to execute a program
  in /sbin/mount_type where type is replaced by the file system
  type name.  For example, nfs file systems are mounted by the
  program /sbin/mount_nfs.

  Most file systems will be dynamically loaded by the kernel if not
  already present, and if the kernel module is available.


Default mount with all mounts:

% mount 
zroot/ROOT/12.1 on / (zfs, local, noatime, nfsv4acls)
devfs on /dev (devfs, local, multilabel)
linprocfs on /compat/linux/proc (linprocfs, local)
tmpfs on /compat/linux/dev/shm (tmpfs, local)
zroot/tmp on /tmp (zfs, local, noatime, nosuid, nfsv4acls)
zroot/home on /home (zfs, local, noatime, nfsv4acls)
zroot/var/log on /var/log (zfs, local, noatime, noexec, nosuid, nfsv4acls)
zroot/var/crash on /var/crash (zfs, local, noatime, noexec, nosuid, nfsv4acls)
zroot/jail on /jail (zfs, local, noatime, nfsv4acls)
zroot/var/mail on /var/mail (zfs, local, nfsv4acls)
zroot/usr/src on /usr/src (zfs, local, noatime, nfsv4acls)
zroot/usr/ports on /usr/ports (zfs, local, noatime, nosuid, nfsv4acls)
zroot/var/audit on /var/audit (zfs, local, noatime, noexec, nosuid, nfsv4acls)
zroot/var/tmp on /var/tmp (zfs, local, noatime, nosuid, nfsv4acls)
/dev/label/ASD on /mnt/tmp (msdosfs, local)
/dev/md0s1a on /mnt/ufs (ufs, local)
/dev/fuse on /mnt/ntfs (fusefs)
/dev/md0s1f on /mnt/ufs.other (ufs, local)
/dev/gpt/OTHER on /mnt/fat.other (msdosfs, local)

Excluding single filesystem works:

% mount -t nozfs
devfs on /dev (devfs, local, multilabel)
linprocfs on /compat/linux/proc (linprocfs, local)
tmpfs on /compat/linux/dev/shm (tmpfs, local)
/dev/label/ASD on /mnt/tmp (msdosfs, local)
/dev/md0s1a on /mnt/ufs (ufs, local)
/dev/fuse on /mnt/ntfs (fusefs)
/dev/md0s1f on /mnt/ufs.other (ufs, local)
/dev/gpt/OTHER on /mnt/fat.other (msdosfs, local)

Excluding multiple filesystem does not work (but should according to man page):

% mount -t nozfs,noufs,nodevfs,notmpfs
devfs on /dev (devfs, local, multilabel)
linprocfs on /compat/linux/proc (linprocfs, local)
tmpfs on /compat/linux/dev/shm (tmpfs, local)
/dev/label/ASD on /mnt/tmp (msdosfs, local)
/dev/md0s1a on /mnt/ufs (ufs, local)
/dev/fuse on /mnt/ntfs (fusefs)
/dev/md0s1f on /mnt/ufs.other (ufs, local)
/dev/gpt/OTHER on /mnt/fat.other (msdosfs, local)


Regards,
vermaden

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 240889] mount -t nozfs, noufs, nodevfs, notmpfs - does not work as advertised in man page

2019-09-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240889

--- Comment #1 from verma...@interia.pl ---
This is on 12.1-BETA1 system.

% uname -v
FreeBSD 12.1-BETA1 r352546 GENERIC

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 240700] [META] FreeBSD 12.1-RELEASE blockers

2019-09-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240700

--- Comment #3 from verma...@interia.pl ---
Another 'blocker' for 12.1-RELEASE:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240889

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 240760] Caps lock key became a character in GELI passphrase entry after upgrading to 12.0 w/root-on-ZFS

2019-09-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240760

--- Comment #3 from Ariel Millennium Thornton  ---
New information: The caps lock key can be used, but backspace must be pressed
once right after pressing caps lock.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 240889] mount -t nozfs, noufs, nodevfs, notmpfs - does not work as advertised in man page

2019-09-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240889

Yuri Pankov  changed:

   What|Removed |Added

 CC||yur...@freebsd.org

--- Comment #2 from Yuri Pankov  ---
I think you are reading it wrong, you should specify "no" just one time as
shown in the man page example you pasted:

mount -a -t nonfs,nullfs

...so it should be:

mount -t nozfs,ufs,devfs,tmpfs

...if you want exclude all of these FS types.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 240889] mount -t nozfs, noufs, nodevfs, notmpfs - does not work as advertised in man page

2019-09-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240889

verma...@interia.pl changed:

   What|Removed |Added

 Resolution|--- |Not A Bug
 Status|New |Closed

--- Comment #3 from verma...@interia.pl ---
(In reply to Yuri Pankov from comment #2)

...so it works that way, ok, now its obvious.

I will close the bug as 'not bug'.

Thank You for explanation.

Regards,
vermaden

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"