[Bug 195914] freebsd-update loop on /usr/share/zoneinfo

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195914

Andrew Daugherity  changed:

   What|Removed |Added

 CC||andrew.daugher...@gmail.com

--- Comment #3 from Andrew Daugherity  ---
I believe this is the same underlying issue as #189249.

Sadly it was never fixed for 8.4, but as 8.4 is now EOL and this bug is fixed
in all supported releases (9.3, 10.1, 10.2) there's no more need to keep this
one open.

-- 
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 205932] [panic] Kernel panic when copying from ext2fs partition to UFS partition

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205932

--- Comment #7 from Will B  ---
(In reply to Damjan Jovanovic from comment #6)
Thank you for that explanation, Damjan.  

Fortunately Midnight Commander copies the files just fine, so I used it instead
of cp to bring over my 160 GB of data from the ext4 partition.

Thanks for the patches.  I don't think I'll be able to apply them right away,
but maybe I'll get FreeBSD running in a VM and do it that way as my real metal
is used for my busy day-to-day business.

Thanks again! :-)

-- 
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 198062] FreeBSD 10.1-RELEASE kernel freezes on 'pci0: on pcib0'

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198062

--- Comment #27 from John Baldwin  ---
Ok, I've added some more tracing.  Please do a 'git pull' and rebuild the
kernel and test again.  This is still narrowing down where it is hanging and
doesn't have a fix yet.

-- 
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 195914] freebsd-update loop on /usr/share/zoneinfo

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195914

NGie Cooper  changed:

   What|Removed |Added

 Status|New |Closed
 Resolution|--- |DUPLICATE
 CC||n...@freebsd.org

--- Comment #4 from NGie Cooper  ---
(In reply to Andrew Daugherity from comment #3)

Agreed based on later comments. I'll mark this bug as a dupe of bug 189249.

*** This bug has been marked as a duplicate of bug 189249 ***

-- 
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 205932] [panic] Kernel panic when copying from ext2fs partition to UFS partition

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205932

--- Comment #8 from Pedro F. Giffuni  ---
(In reply to Will B from comment #7)

Hello;

Unfortunately, testing the ext4 support is difficult because most testsuites
out there want to be able to write to the filesystem, so the ext4 support has
received a lot less testing than ext 2/3.

I think the sysutils/fusefs-lkl may be in a better position functionally among
the alternatives.

Damjan's patches look good and may have some effect here but if we can't
reproduce this particular bug we will have to close the issue.

-- 
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 206047] TCP Stack: Challenge ACKs and Timestamps

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206047

Jonathan T. Looney  changed:

   What|Removed |Added

   Assignee|freebsd-bugs@FreeBSD.org|j...@freebsd.org
 CC||j...@freebsd.org
 Status|New |In Progress

--- Comment #1 from Jonathan T. Looney  ---
See https://reviews.freebsd.org/D4808 for proposed change.

-- 
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 205787] Can't compile freebsd srcs (/usr/src) with clang/llvm 3.8 and option -march=haswell

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205787

--- Comment #2 from Leo  ---
(In reply to Ed Maste from comment #1)

Hello, adding -DNO_WERROR option to make is ok, but then it stops at
/usr/src/sys/boot/i386/boot2

The error is:

===> sys/boot/i386/boot2 (all)
--- boot2 ---
-265 bytes available
*** [boot2] Error code 1

If I compile with the default clang version that comes with Freebsd 10 (3.4.1),
even  if I modify the CFLAGS/CXXFLAGS (-O3 -march=corei7 -fomit-frame-pointer),
all goes well, but if I try to compile with clang 3.6
(/usr/ports/lang/clang36), clang 3.7 and clang 3.8 (clang-devel), then this
error appears, with variable "-[X] bytes available" error message.

-- 
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 206016] Changing MTU on the interface Infiniband network card (Mellanox MHQH29B-XTR) causes panic

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206016

Mark Linimon  changed:

   What|Removed |Added

   Assignee|freebsd-bugs@FreeBSD.org|freebsd-...@freebsd.org

-- 
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 206012] jail(8): Cannot assign link-local IPv6 address to a jail

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206012

Mark Linimon  changed:

   What|Removed |Added

   Assignee|freebsd-bugs@FreeBSD.org|freebsd-j...@freebsd.org

-- 
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 205998] release/release.sh fails if packages are already installed in chroot

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205998

Mark Linimon  changed:

   What|Removed |Added

   Keywords||patch

-- 
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 205998] release/release.sh fails if packages are already installed in chroot

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205998

Glen Barber  changed:

   What|Removed |Added

   Assignee|freebsd-bugs@FreeBSD.org|g...@freebsd.org

-- 
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 206003] ports-mgmt/pkg crash if env variable HTTP_USER_AGENT is empty

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206003

Mark Linimon  changed:

   What|Removed |Added

Summary|pkg crash   |ports-mgmt/pkg crash if env
   ||variable HTTP_USER_AGENT is
   ||empty
   Assignee|freebsd-bugs@FreeBSD.org|p...@freebsd.org
Version|10.2-STABLE |Latest
Product|Base System |Ports & Packages
  Component|bin |Individual Port(s)

-- 
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 206031] [EFI] boot/loader.efi doesn't export smbios serial numbers (esp. system.uuid)

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206031

Mark Linimon  changed:

   What|Removed |Added

   Keywords||patch

-- 
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 206035] gpiobus causes panic when attached to gpio with a single pin

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206035

Mark Linimon  changed:

   What|Removed |Added

   Keywords||patch

-- 
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 206017] mips binary has segments with different permissions in same page

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206017

Mark Linimon  changed:

   What|Removed |Added

   Assignee|freebsd-bugs@FreeBSD.org|ema...@freebsd.org

-- 
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 206034] Dump Card State Ends

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206034

Mark Linimon  changed:

   What|Removed |Added

   Keywords||regression

-- 
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 206005] KDB should give a more helpful error message for encrypted swap

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206005

Mark Linimon  changed:

   What|Removed |Added

  Component|kern|bin

-- 
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 206007] Clean ZFS on root in stripe configuration in MBR format does not boot after install

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206007

Mark Linimon  changed:

   What|Removed |Added

   Assignee|freebsd-bugs@FreeBSD.org|freebsd-sysinstall@FreeBSD.
   ||org

-- 
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 198062] FreeBSD 10.1-RELEASE kernel freezes on 'pci0: on pcib0'

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198062

--- Comment #28 from Joseph King  ---
OK
OK boot -v
/boot/test/kernel text=0xfd2528 data=0x128030+0x207c00
syms=[0x8+0x145f20+0x8+0x160160]
Booting...
Table 'FACP' at 0xbfff0290
Table 'APIC' at 0xbfff0390
APIC: Found table at 0xbfff0390
APIC: Using the MADT enumerator.
MADT: Found CPU APIC ID 0 ACPI ID 1: enabled
SMP: Added CPU 0 (AP)
MADT: Found CPU APIC ID 1 ACPI ID 2: enabled
SMP: Added CPU 1 (AP)
MADT: Found CPU APIC ID 2 ACPI ID 3: enabled
SMP: Added CPU 2 (AP)
MADT: Found CPU APIC ID 3 ACPI ID 4: enabled
SMP: Added CPU 3 (AP)
MADT: Found CPU APIC ID 132 ACPI ID 5: disabled
MADT: Found CPU APIC ID 133 ACPI ID 6: disabled
MADT: Found CPU APIC ID 134 ACPI ID 7: disabled
MADT: Found CPU APIC ID 135 ACPI ID 8: disabled
MADT: Found CPU APIC ID 136 ACPI ID 9: disabled
MADT: Found CPU APIC ID 137 ACPI ID 10: disabled
MADT: Found CPU APIC ID 138 ACPI ID 11: disabled
MADT: Found CPU APIC ID 139 ACPI ID 12: disabled
Copyright (c) 1992-2016 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 10.2-STABLE #1 64e0804(pr_198062): Fri Jan  8 19:09:56 EST 2016
   
j...@netsys9.isolan.itsmine.com:/usr/obj/ufs/pr_198062-git/freebsd/sys/GENERIC
amd64
FreeBSD clang version 3.4.1 (tags/RELEASE_34/dot1-final 208032) 20140512
Preloaded elf kernel "/boot/test/kernel" at 0x819aa000.
Calibrating TSC clock ... TSC clock: 2793067889 Hz
CPU: Dual-Core AMD Opteron(tm) Processor 2220 (2793.07-MHz K8-class CPU)
  Origin="AuthenticAMD"  Id=0x40f13  Family=0xf  Model=0x41  Stepping=3
 
Features=0x178bfbff
  Features2=0x2001
  AMD Features=0xea500800
  AMD Features2=0x1f
  SVM: Features=0x0
Revision=1, ASIDs=64
L1 2MB data TLB: 8 entries, fully associative
L1 2MB instruction TLB: 8 entries, fully associative
L1 4KB data TLB: 32 entries, fully associative
L1 4KB instruction TLB: 32 entries, fully associative
L1 data cache: 64 kbytes, 64 bytes/line, 1 lines/tag, 2-way associative
L1 instruction cache: 64 kbytes, 64 bytes/line, 1 lines/tag, 2-way associative
L2 2MB unified TLB: 0 entries, disabled/not present
L2 4KB data TLB: 512 entries, 4-way associative
L2 4KB instruction TLB: 512 entries, 4-way associative
L2 unified cache: 1024 kbytes, 64 bytes/line, 1 lines/tag, 16-way associative
real memory  = 4294967296 (4096 MB)
Physical memory chunk(s):
0x0001 - 0x0009bfff, 573440 bytes (140 pages)
0x0010 - 0x001f, 1048576 bytes (256 pages)
0x019eb000 - 0xb7d60fff, 3057082368 bytes (746358 pages)
0x0001 - 0x00013ffe7fff, 1073643520 bytes (262120 pages)
avail memory = 4103352320 (3913 MB)
Event timer "LAPIC" quality 400
ACPI APIC Table: <062309 APIC1333>
INTR: Adding local APIC 1 as a target
INTR: Adding local APIC 2 as a target
INTR: Adding local APIC 3 as a target
FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
FreeBSD/SMP: 2 package(s) x 2 core(s)
 cpu0 (BSP): APIC ID:  0
 cpu1 (AP): APIC ID:  1
 cpu2 (AP): APIC ID:  2
 cpu3 (AP): APIC ID:  3
APIC: CPU 0 has ACPI ID 1
APIC: CPU 1 has ACPI ID 2
APIC: CPU 2 has ACPI ID 3
APIC: CPU 3 has ACPI ID 4
x86bios:  IVT 0x00-0x0004ff at 0xf800
x86bios: SSEG 0x098000-0x098fff at 0xfe011bbc
x86bios: EBDA 0x09f000-0x09 at 0xf809f000
x86bios:  ROM 0x0a-0x0fefff at 0xf80a
XEN: CPU 0 has VCPU ID 1
XEN: CPU 1 has VCPU ID 2
XEN: CPU 2 has VCPU ID 3
XEN: CPU 3 has VCPU ID 4
random device not loaded; using insecure entropy
ULE: setup cpu 0
ULE: setup cpu 1
ULE: setup cpu 2
ULE: setup cpu 3
ACPI: RSDP 0x000F8F90 24 (v02 ACPIAM)
ACPI: XSDT 0xBFFF0100 4C (v01 062309 XSDT1333 20090623 MSFT
0097)
ACPI: FACP 0xBFFF0290 F4 (v03 062309 FACP1333 20090623 MSFT
0097)
ACPI BIOS Warning (bug): 32/64X length mismatch in FADT/Gpe1Block: 96/64
(20150515/tbfadt-644)
ACPI: DSDT 0xBFFF04E0 00370B (v01 0AAAB  0AAAB001 0001 INTL
02002026)
ACPI: FACS 0xBFFFE000 40
ACPI: APIC 0xBFFF0390 000102 (v01 062309 APIC1333 20090623 MSFT
0097)
ACPI: OEMB 0xBFFFE040 56 (v01 062309 OEMB1333 20090623 MSFT
0097)
ACPI: SRAT 0xBFFF3BF0 E8 (v01 AMDFAM_F_10 0002 AMD 
0001)
ACPI: SSDT 0xBFFF3CE0 000574 (v01 A M I  POWERNOW 0001 AMD 
0001)
MADT: Found IO APIC ID 4, Interrupt 0 at 0xfec0
ioapic0: Routing external 8259A's -> intpin 0
MADT: Found IO APIC ID 5, Interrupt 16 at 0xfec01000
MADT: Found IO APIC ID 6, Interrupt 32 at 0xfec02000
lapic0: Routing NMI -> LINT1
lapic0: LINT1 trigger: edge
lapic0: LINT1 polarity: high
lapic1: Routing NMI 

[Bug 205787] Can't compile freebsd srcs (/usr/src) with clang/llvm 3.8 and option -march=haswell

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205787

NGie Cooper  changed:

   What|Removed |Added

 CC||d...@freebsd.org,
   ||n...@freebsd.org

--- Comment #3 from NGie Cooper  ---
CCing dim@

-- 
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 205787] Can't compile freebsd srcs (/usr/src) with clang/llvm 3.8 and option -march=haswell

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205787

--- Comment #4 from Dimitry Andric  ---
Without any further information, I'm guessing that your bsd.compiler.mk does
not detect the compiler version properly, and that incorrect flags are being
used to compile boot2.  (The whole sys/boot area is very sensitive to the exact
optimization flags, it will almost always grow too large if they aren't
correct.)

Can you provide a log of the commands being used to compile everything under
/usr/src/sys/boot?  For example, by running "make clean" in there, and then
running make as usual, but redirected to a log file.

I'm also interested in the COMPILER_TYPE and COMPILER_VERSION detected by your
version of the build system.  E.g. in /usr/src, run:

make -V COMPILER_TYPE -V COMPILER_VERSION

and paste the output here.

Having said all that, I think you will run into multiple problems that will be
pretty tricky to solve, if you continue this way.  10.2-RELEASE is completely
frozen, and misses a lot of important fixes and updates which are in 10-STABLE,
making the task even more difficult.

Therefore, I think it is wisest to abandon this attempt.  You will most likely
not gain any significant performance advantage by compiling with
-march=haswell, as opposed to e.g. -march=corei7.

-- 
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 206059] [ext2fs][patch] EXT4: cannot mount filesystems < 512 MiB in size: "ext2fs: no space for extra inode timestamps"

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206059

Bug ID: 206059
   Summary: [ext2fs][patch] EXT4: cannot mount filesystems < 512
MiB in size: "ext2fs: no space for extra inode
timestamps"
   Product: Base System
   Version: 11.0-CURRENT
  Hardware: Any
OS: Any
Status: New
  Keywords: patch
  Severity: Affects Some People
  Priority: ---
 Component: kern
  Assignee: freebsd-bugs@FreeBSD.org
  Reporter: damjan@gmail.com
CC: freebsd...@freebsd.org

Created attachment 165293
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=165293=edit
Allow inode size < sizeof(struct ext2fs_dinode) when EXT2F_ROCOMPAT_EXTRA_ISIZE
is set

When making the EXT4 filesystem, mkfs.ext4 uses different inode sizes depending
on the filesystem file.

For a large filesystem, "dumpe2fs" returns these relevant fields:

Filesystem features:  has_journal ext_attr resize_inode dir_index filetype
extent flex_bg sparse_super large_file huge_file uninit_bg dir_nlink
extra_isize
Inode size:   256
Required extra isize: 28
Desired extra isize:  28

For a small filesystem, "dumpe2fs" returns this instead, and "Required extra
isize" and "Desired extra isize" are missing:

Filesystem features:  has_journal ext_attr resize_inode dir_index filetype
extent flex_bg sparse_super huge_file uninit_bg dir_nlink extra_isize
Inode size:   128

Bisection searching with different filesystem sizes ("dd if=/dev/zero
of=/tmp/filesystem bs=1M count=..." + "mkfs.ext4 /tmp/filesystem" + "dumpe2fs
-h /tmp/filesystem") shows inode size 256 is used for filesystems >= 512 MiB,
and smaller filesystems use inode size 128.

Attemping to mount the small filesystems fails with this error (and unless
you've patched ext2fs with the patch from bug 206056, also panics the
kernel!!):

ext2fs: no space for extra inode timestamps

That message comes from compute_sb_data() in ext2_vfsops.c, which does

   /* Check for extra isize in big inodes. */
   if (EXT2_HAS_RO_COMPAT_FEATURE(fs, EXT2F_ROCOMPAT_EXTRA_ISIZE) &&
   EXT2_INODE_SIZE(fs) < sizeof(struct ext2fs_dinode)) {
   printf("ext2fs: no space for extra inode timestamps\n");
   return (EINVAL);
   }

which must be wrong, because even small filesystems have the extra_isize
feature set, yet the inode size is 128 which is smaller than sizeof(struct
ext2fs_dinode).

Since EXT2F_ROCOMPAT_EXTRA_ISIZE isn't used anywhere else in the ext2fs module,
I've made a patch that deletes that entire section, and it gets the small
filesystems to mount and work.

-- 
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 206001] tcp fastpath, using ancient struct tcpcb field

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206001

Jonathan T. Looney  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 CC||j...@freebsd.org
   Assignee|freebsd-bugs@FreeBSD.org|j...@freebsd.org
 Status|New |Closed

--- Comment #3 from Jonathan T. Looney  ---
Fixed by r293313.

-- 
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 206053] There is a bug in kqueue support code of netmap

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206053

Bug ID: 206053
   Summary: There is a bug in kqueue support code of netmap
   Product: Base System
   Version: 11.0-CURRENT
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: kern
  Assignee: freebsd-bugs@FreeBSD.org
  Reporter: b...@mail.ustc.edu.cn

It seems that there is a bug in kqueue support code of netmap which can cause
kernel panic. And I can reproduce the kernel panic with this simple program on
-HEAD:

#include 
#include 

#include 
#include 
#include 

#ifndef NETMAP_WITH_LIBS
#define NETMAP_WITH_LIBS
#endif
#include 

static int
kq_add(int kq, int fd)
{
struct kevent changes[1];
int ret;

EV_SET([0], fd, EVFILT_READ, EV_ADD, 0, 0, NULL);
ret = kevent(kq, changes, 1, NULL, 0, NULL);
assert(ret != -1);

printf("[%s] success\n", __func__);

return (ret);
}

static void
kq_wait(int kq)
{
struct kevent events[1];
int ret;

ret = kevent(kq, NULL, 0, events, 1, NULL);
assert(ret != -1);

printf("[%s] success\n", __func__);
}

int main(void)
{
const char *ifname = "vale0:vm1";
struct nm_desc *d;
int kq;

d = nm_open(ifname, NULL, 0, 0);
assert(d != NULL);

kq = kqueue();
assert(kq != -1);

kq_add(kq, d->fd);
kq_wait(kq);

return (0);
}

And below is part of the crash summary:

freebsd dumped core - see /var/crash/vmcore.0

Fri Jan  8 22:19:39 CST 2016

FreeBSD freebsd 11.0-CURRENT FreeBSD 11.0-CURRENT #2 d1f6105(master)-dirty: Fri
Jan  8 21:55:33 CST 2016 btw@freebsd:/usr/obj/root/freebsd/sys/GENERIC 
amd64

..

panic: mutex nm_kn_lock not owned at /root/freebsd/sys/kern/kern_event.c:2073
cpuid = 1
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfe011744c420
vpanic() at vpanic+0x182/frame 0xfe011744c4a0
panic() at panic+0x43/frame 0xfe011744c500
__mtx_assert() at __mtx_assert+0xbf/frame 0xfe011744c510
knlist_add() at knlist_add+0x20/frame 0xfe011744c540
netmap_kqfilter() at netmap_kqfilter+0x101/frame 0xfe011744c580
devfs_kqfilter_f() at devfs_kqfilter_f+0x81/frame 0xfe011744c5d0
kqueue_register() at kqueue_register+0x5bf/frame 0xfe011744c670
kqueue_kevent() at kqueue_kevent+0xc8/frame 0xfe011744c840
kern_kevent_fp() at kern_kevent_fp+0x99/frame 0xfe011744c890
kern_kevent() at kern_kevent+0x9f/frame 0xfe011744c8f0
sys_kevent() at sys_kevent+0x11c/frame 0xfe011744c9a0
amd64_syscall() at amd64_syscall+0x2db/frame 0xfe011744cab0
Xfast_syscall() at Xfast_syscall+0xfb/frame 0xfe011744cab0
--- syscall (363, FreeBSD ELF64, sys_kevent), rip = 0x80095bc7a, rsp =
0x7fffe988, rbp = 0x7fffe9e0 ---
KDB: enter: panic

..

-- 
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 206055] share/zoneinfo "beforeinstall" fails to create needed directories in DESTDIR

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206055

Bug ID: 206055
   Summary: share/zoneinfo "beforeinstall" fails to create needed
directories in DESTDIR
   Product: Base System
   Version: 11.0-CURRENT
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: misc
  Assignee: freebsd-bugs@FreeBSD.org
  Reporter: rpok...@panasas.com
CC: d...@panasas.com

Timezone files used to be installed with `zic', but they have been switched to
using `install' as of r245265. However, that does not create the required
subdirectories leading to the final destination.

-- 
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 206056] [ext2fs][patch][panic] EXT4: mount panic from freeing invalid pointers

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206056

Bug ID: 206056
   Summary: [ext2fs][patch][panic] EXT4: mount panic from freeing
invalid pointers
   Product: Base System
   Version: 11.0-CURRENT
  Hardware: Any
OS: Any
Status: New
  Keywords: patch
  Severity: Affects Some People
  Priority: ---
 Component: kern
  Assignee: freebsd-bugs@FreeBSD.org
  Reporter: damjan@gmail.com
CC: freebsd...@freebsd.org
  Keywords: patch

Created attachment 165290
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=165290=edit
Preventing a panic when pointers from struct ext2mount's um_e2fs are freed

On Linux I made a 500MB EXT4 filesystem for testing, and when I tried to mount
it in FreeBSD with:

mdconfig -a /path/to/filesystem
mount -t ext2fs -o ro /dev/md0 /path/to/mountpoint

the following error got printed out, followed immediately by a panic:

ext2fs: no space for extra inode timestamps

Fatal trap 12: page fault while in kernel mode
cpuid = 0; apicid = 00
fault_virtual_address = 0x4
fault code= supervisor read, page not present
instruction pointer   = 0x20:0xc0b1f1cc
stack pointer = 0x28:0xcebee898
frame pointer = 0x28:0xcebee8c0
code segment  = base 0x0, limit 0xf, type 0x1b
  = DPL 0, pres 1, def32 1, gran 1
processor eflags  = interrupt enabled, resume, IOPL = 0
current process   = 777 (mount)
[ thread pid 777 tid 100065 ]
Stopped at  free+0x5c:movl0x4(%eax),%eax

db> bt
Tracing pid 777 tid 100065 td 0xc4e0c620
free(aa,c54ab298,2a3,2a1,0,...) at free+0x5c/frame 0xcebee8c0
ext2_mount(c4e16a80,c54ab208,c5374380,c4e10800,c4c40a70,...) at
ext2_mount+0x1604/frame 0xceebe9e8
vfs_donmount(c4e4c620,1,0,c4c11b00,c4c11b00,...) at vfs_donmount+0xdc6/frame
0xceebebf0
sys_nmount(c4e0c620,ceebeca8,c506890c,c4e0c620,c506890c,...) at
sys_nmount+0x78/frame 0xceebec18
syscall(ceebece8) at syscall+0x4a6/frame 0xceebecdc
Xint0x80_syscall() at Xint0x80_syscall+0x21/frame 0xceebecdc
--- syscall (378, FreeBSD ELF32, sys_nmount), eip = 0x280e013b, esp =
0xbfbfdd20, ebp = 0xbfbfe278


The "ext2fs: no space for extra inode timestamps" message comes from
compute_sb_data() in ext2_vfsops.c, which returns EINVAL after printing it,
never reaching the subsequent lines that initialize fs->e2fs_gd and
fs->e2fs_contigdirs. When ext2_mountfs() calls compute_sb_data(), it does a
"goto out" on error, and in "out" it attempts to free() those 2 fields. Since
the memory for the struct those fields are in wasn't initialized when it was
allocated, free() is being passed invalid pointers, resulting in a panic.

The attached patch initializes the struct with those fields to zeroes on
allocation, preventing the panic.

I'll investigate the original error that caused this buggy error path to be
taken in a separate issue.

-- 
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 206055] share/zoneinfo "beforeinstall" fails to create needed directories in DESTDIR

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206055

--- Comment #1 from Ravi Pokala  ---
Phabricator: https://reviews.freebsd.org/D4840

-- 
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 160392] [panic] double fault on configuring for php5-filter-5.3.8

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=160392

Jason Unovitch  changed:

   What|Removed |Added

   Assignee|freebsd-bugs@FreeBSD.org|junovi...@freebsd.org
 Status|In Progress |Closed
 Resolution|--- |Not Enough Information

-- 
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 205855] ICH7R identified as ICH9R, doesn't work in RAID mode

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205855

Alexander Motin  changed:

   What|Removed |Added

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

-- 
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 142198] SSLv3 failure with irc/xchat on FreeBSD 8.0

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=142198

Bernard Spil  changed:

   What|Removed |Added

 CC||cpbsdm...@gmail.com

--- Comment #10 from Bernard Spil  ---
*** Bug 203699 has been marked as a duplicate of this bug. ***

-- 
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 205855] ICH7R identified as ICH9R, doesn't work in RAID mode

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205855

--- Comment #8 from arca...@ivanovy.net ---
Alexander nailed it on the head. Between 10.1 and 10.2 the AHCI has been
removed from ada driver. It worked in 10.1 because it was actually there.
Adding "device ahci" solved my problem.(In reply to Alexander Motin from
comment #7)

-- 
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 205855] ICH7R identified as ICH9R, doesn't work in RAID mode

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205855

--- Comment #9 from arca...@ivanovy.net ---
10.2 dmesg.boot

Copyright (c) 1992-2016 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 10.2-STABLE #0 r293336: Thu Jan  7 12:45:10 EST 2016
ad...@fw1.home.ivanovy.net:/usr/obj/usr/src/sys/FIREWALL amd64
FreeBSD clang version 3.4.1 (tags/RELEASE_34/dot1-final 208032) 20140512
CPU: Intel(R) Core(TM)2 Duo CPU E7200  @ 2.53GHz (2527.05-MHz K8-class CPU)
  Origin="GenuineIntel"  Id=0x10676  Family=0x6  Model=0x17  Stepping=6
 
Features=0xbfebfbff
  Features2=0x8e39d
  AMD Features=0x20100800
  AMD Features2=0x1
  TSC: P-state invariant, performance statistics
real memory  = 1073741824 (1024 MB)
avail memory = 1020993536 (973 MB)
Event timer "LAPIC" quality 400
ACPI APIC Table: 
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
FreeBSD/SMP: 1 package(s) x 2 core(s)
 cpu0 (BSP): APIC ID:  0
 cpu1 (AP): APIC ID:  1
random device not loaded; using insecure entropy
ACPI BIOS Warning (bug): 32/64X length mismatch in FADT/Pm1aEventBlock: 32/8
(20150515/tbfadt-644)
ACPI BIOS Warning (bug): 32/64X length mismatch in FADT/Pm1aControlBlock: 16/8
(20150515/tbfadt-644)
ACPI BIOS Warning (bug): 32/64X length mismatch in FADT/PmTimerBlock: 32/8
(20150515/tbfadt-644)
ACPI BIOS Warning (bug): 32/64X length mismatch in FADT/Gpe0Block: 128/8
(20150515/tbfadt-644)
ACPI BIOS Warning (bug): Invalid length for FADT/Pm1aEventBlock: 8, using
default 32 (20150515/tbfadt-725)
ACPI BIOS Warning (bug): Invalid length for FADT/Pm1aControlBlock: 8, using
default 16 (20150515/tbfadt-725)
ACPI BIOS Warning (bug): Invalid length for FADT/PmTimerBlock: 8, using default
32 (20150515/tbfadt-725)
ioapic0: Changing APIC ID to 4
ioapic0  irqs 0-23 on motherboard
kbd0 at kbdmux0
random:  initialized
smbios0:  at iomem 0xf0be0-0xf0bfe on motherboard
smbios0: Version: 2.5, BCD Revision: 2.5
cryptosoft0:  on motherboard
acpi0:  on motherboard
acpi0: Power Button (fixed)
cpu0:  on acpi0
cpu1:  on acpi0
attimer0:  port 0x40-0x43 on acpi0
Timecounter "i8254" frequency 1193182 Hz quality 0
Event timer "i8254" frequency 1193182 Hz quality 100
hpet0:  iomem 0xfed0-0xfed003ff irq 0,8 on
acpi0
device_attach: hpet0 attach returned 12
atrtc0:  port 0x70-0x73 on acpi0
Event timer "RTC" frequency 32768 Hz quality 0
Timecounter "ACPI-fast" frequency 3579545 Hz quality 900
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0
acpi_button0:  on acpi0
pcib0:  port 0xcf8-0xcff on acpi0
pci0:  on pcib0
pcib1:  irq 16 at device 1.0 on pci0
pci1:  on pcib1
em0:  port 0xdf00-0xdf1f mem
0xfdae-0xfdaf,0xfdac-0xfdad irq 16 at device 0.0 on pci1
em0: Using an MSI interrupt
em0: Ethernet address: 00:15:17:85:7b:a2
em1:  port 0xde00-0xde1f mem
0xfdaa-0xfdab,0xfda8-0xfda9 irq 17 at device 0.1 on pci1
em1: Using an MSI interrupt
em1: Ethernet address: 00:15:17:85:7b:a3
vgapci0:  port 0xff00-0xff07 mem
0xfdf0-0xfdf7,0xd000-0xdfff,0xfdc0-0xfdcf irq 16 at
device 2.0 on pci0
agp0:  on vgapci0
agp0: aperture size is 256M, detected 4194300k stolen memory
vgapci0: Boot video device
em2:  port 0xfe00-0xfe1f mem
0xfdfc-0xfdfd,0xfdfff000-0xfdff irq 20 at device 25.0 on pci0
em2: Using an MSI interrupt
em2: Ethernet address: 00:21:9b:0b:a0:8c
uhci0:  port 0xfd00-0xfd1f irq 16 at device
26.0 on pci0
usbus0 on uhci0
uhci1:  port 0xfc00-0xfc1f irq 21 at device
26.1 on pci0
usbus1 on uhci1
uhci2:  port 0xfb00-0xfb1f irq 19 at device
26.2 on pci0
usbus2 on uhci2
ehci0:  mem 0xfdffe000-0xfdffe3ff irq
18 at device 26.7 on pci0
usbus3: EHCI version 1.0
usbus3 on ehci0
uhci3:  port 0xfa00-0xfa1f irq 23 at device
29.0 on pci0
usbus4 on uhci3
uhci4:  port 0xf900-0xf91f irq 19 at device
29.1 on pci0
usbus5 on uhci4
uhci5:  port 0xf800-0xf81f irq 18 at device
29.2 on pci0
usbus6 on uhci5
ehci1:  mem 0xfdffd000-0xfdffd3ff irq
23 at device 29.7 on pci0
usbus7: EHCI version 1.0
usbus7 on ehci1
pcib2:  at device 30.0 on pci0
pci2:  on pcib2
isab0:  at device 31.0 on pci0
isa0:  on isab0
ahci0:  port
0xf700-0xf707,0xf600-0xf603,0xf500-0xf507,0xf400-0xf403,0xf300-0xf31f mem
0xfdffc000-0xfdffc7ff irq 19 at device 31.2 on pci0
ahci0: AHCI v1.20 with 6 3Gbps ports, Port Multiplier supported
ahcich0:  at channel 0 on ahci0
ahcich1:  at channel 1 on ahci0
ahcich2:  at channel 2 on ahci0
ahcich3:  at channel 3 on ahci0
ahcich4:  at channel 4 on ahci0
ahcich5:  at channel 5 on ahci0
ahciem0:  on 

[Bug 142198] SSLv3 failure with irc/xchat on FreeBSD 8.0

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=142198

Bernard Spil  changed:

   What|Removed |Added

 CC||br...@freebsd.org,
   ||gn...@freebsd.org
 Attachment #165250||maintainer-approval?(gnome@
  Flags||FreeBSD.org)

--- Comment #11 from Bernard Spil  ---
Created attachment 165250
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=165250=edit
Patch for inclusion in files

Patch taken from 203699 by cpbsdm...@gmail.com

-- 
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 142198] SSLv3 failure with irc/xchat on FreeBSD 8.0

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=142198

Bernard Spil  changed:

   What|Removed |Added

Product|Base System |Ports & Packages
  Component|kern|Individual Port(s)
Version|8.0-RELEASE |Latest
   Severity|Affects Only Me |Affects Some People
   Assignee|freebsd-bugs@FreeBSD.org|freebsd-ports-bugs@FreeBSD.
   ||org

-- 
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 160392] [panic] double fault on configuring for php5-filter-5.3.8

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=160392

--- Comment #3 from Torsten Zühlsdorff  ---
How to handle this PR? PHP 5.3 is no longer in the Portstree, there is no
feedback from the submitter for about 2 months and there are no similar issues
in the tracker or watchers of this PR. Also the initial report is more than 4
years ago.
Can we close it?

-- 
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 206035] gpiobus causes panic when attached to gpio with a single pin

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206035

Bug ID: 206035
   Summary: gpiobus causes panic when attached to gpio with a
single pin
   Product: Base System
   Version: 11.0-CURRENT
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: kern
  Assignee: freebsd-bugs@FreeBSD.org
  Reporter: sgala...@gmail.com

Created attachment 165265
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=165265=edit
Suggested fix for the problem (please see comments for details)

While attaching a gpiobus to a GPIO controller with a single pin, the system
panics due to a failed KASSERT in gpiobus_init_softc().

This is due to the fact that gpiobus obtains the maximum pin number from the
GPIO controller (via GPIO_PIN_MAX) and immediately does a KASSERT, expecting
that the obtained value is != 0.

In the case of a GPIO controller which controls a single pin, the returned
value will be 0 (0 is the maximum pin number), which is absolutely valid.

Moreover, right after the KASSERT the code in gpiobus_init_softc() actually
adjusts the number of pins to the right value.

The suggestion is to change the KASSERT like so:
-   KASSERT(sc->sc_npins != 0, ("GPIO device with no pins"));
+   KASSERT(sc->sc_npins >= 0, ("GPIO device with no pins"));

This, I believe, is a better approach than, say, simply postponing the KASSERT
until after gpiobus has adjusted the number of pins, since if a broken GPIO
controller driver returns a < 0 value we'll be in even more trouble.

I've attached a patch with the suggested fix.

-- 
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 194766] [drm:pid12:i915_hangcheck_elapsed] [drm:pid12:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194766

--- Comment #39 from Kenneth Salerno  ---
First of all, this bug has been open 14 months. I would like to believe there
are fbsd developers left out there that care about laptop/desktop issues, and
so I wait. I upgraded to 10.2-RELEASE multiple times to try each "fix" and then
downgraded back to 10.1-RELEASE to have a working Xv acceleration again, but at
this point I will wait until I see a code fix enter the 10.2-RELEASE branch
rather than try any more "workarounds" (and a clue for other users, it is in
the drm2 driver not drm), or wait and see if 10.3-RELEASE incorporates changes
from 11-CURRENT that fix the i915kms/drm2 code.

This bug is the result of the import of Linux kernel modeset driver code that
brought the bug along with the version that was copied. If you search through
Linux kernel bug reports you'll see they had the same issue, and freebsd svn
logs confirm the wholesale import. Looking through the latest 11-CURRENT
branch, I see some attempts in the code to stop the GPU hung messages from
appearing but personally have not tested if that is a cosmetic bandaid or not.

-- 
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 206031] [EFI] boot/loader.efi doesn't export smbios serial numbers (esp. system.uuid)

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206031

Bug ID: 206031
   Summary: [EFI] boot/loader.efi doesn't export smbios serial
numbers (esp. system.uuid)
   Product: Base System
   Version: 11.0-CURRENT
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Some People
  Priority: ---
 Component: kern
  Assignee: freebsd-bugs@FreeBSD.org
  Reporter: sneakywum...@gmail.com

Created attachment 165258
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=165258=edit
Add defines needed to export smbios serial numbers

Some defines needed for exporting serial numbers from the SMBIOS seem to have
been missed during integration of SMBIOS support in the EFI boot loader
(r281138).

Attached patch adds these defines from sys/boot/i386/libi386/Makefile to
sys/boot/efi/loader/Makefile

This is needed for getting the hostid set from the system hardware UUID.

-- 
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 206034] Dump Card State Ends

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206034

Bug ID: 206034
   Summary: Dump Card State Ends
   Product: Base System
   Version: 10.2-RELEASE
  Hardware: i386
OS: Any
Status: New
  Severity: Affects Many People
  Priority: ---
 Component: kern
  Assignee: freebsd-bugs@FreeBSD.org
  Reporter: ups_20...@yahoo.co.uk
CC: freebsd-i...@freebsd.org
CC: freebsd-i...@freebsd.org

Created attachment 165263
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=165263=edit
kernel: Dump Card State Ends

After 9.3 ..-> 10.0, 10.1, 10.2, 11.0 ( i am test all) is problem with scsi
driver
I have Supremicro X5DA8 with SCSI = AIC 7902:
procesor = 2 x XEON
SCSI driver AIC 7902
HDD SCSI SEAGATE ST3146855LW 320Mb/s
video ATI 3650
DVD BLUERAY LG HL-DT-ST BD-RE  GGW-H20L YL07 - > NOT WORKING !!! ( in FreeBSD
9.3 wit recompiling kernel is working ! in 10, 10.1, 10.2 not working)
4,5G SDRAM

but the BIG PROBLEM IS : crash kernel
I have ( me and another person) this problem: in time instaler no problem but
after install : after 10 - 15 min start the kernel/hdd is crash
I tray to re-compiling kernel but in 10 min :((( 


kernel: < Dump Card State Ends >>
kernel: (da0:ahd0:0:0:0): SCB 500 - timed out
kernel: (da0:ahd0:0:0:0): Other SCB Timeout
kernel: (da0:ahd0:0:0:0): No other SCB worth waiting for...
kernel: ahd0: Issued Channel A Bus Reset. 55 SCBs aborted
kernel: (da0:ahd0:0:0:0): WRITE(10). CDB: 2a 00 0d c4 cf 28 00 00 08 00 
kernel: (da0:ahd0:0:0:0): CAM status: SCSI Status Error
kernel: (da0:ahd0:0:0:0): SCSI status: Check Condition
kernel: (da0:ahd0:0:0:0): SCSI sense: UNIT ATTENTION asc:29,2 (SCSI bus reset
occurred)
kernel: (da0:ahd0:0:0:0): Retrying command (per sense data)

Complet error -> in attachment  file "error.txt"

Thx

-- 
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 205932] [panic] Kernel panic when copying from ext2fs partition to UFS partition

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205932

--- Comment #6 from Damjan Jovanovic  ---
(In reply to Will B from comment #5)

In the "cp" tool, function copy_file() in file /usr/src/bin/cp/utils.c has 2
ways of copying a file: mmap + write, and read + write.

mmap + write is used only when all of the following are true:
* VM_AND_BUFFER_CACHE_SYNCHRONIZED is defined (it is, in Makefile)
* It's a regular file (according to S_ISREG())
* The file's size is > 0
* The file's size is <= 8 MiB
* Calling mmap() succeeds

You say it happens on different files each time. My guess is all of the files
that it happens on, are regular non-empty files <= 8 MiB in size.

There's 2 known bugs where mmap() succeeds but reading the mapped contents can
cause problems:

1. The serious bug 205938 where struct buf leaks from ext4_bmapext(), causing a
panic on every attempt to read even 1 byte of the mapped data. Because your
trace shows the panic happens with lbn=0 (the very first block of the file)
this is probably the problem here. This bug was fixed in CURRENT yesterday,
which is newer than your 10.2-RELEASE. You could try the patch from that bug,
it does apply and work for me (for a different mmap problem) on 10.2-RELEASE.

2. Even with that bug fixed, sparse blocks will at best contain garbage data
read from the wrong disk blocks instead of zeroes, corrupting the copied file
you create (maybe a panic is also possible?). This is bug 205816 which I
previously mentioned. This isn't even fixed in CURRENT, but there is a patch on
that bug you can try.

(BTW you could also use ext4fuse from ports instead of the in-kernel ext2fs
driver since it doesn't suffer from problem 1, but it does suffer from problem
2, and I don't know/have a patch for it)

With both those patches, copying files from EXT4 should be reliable and
correct, but very slow in the mmap + write case (about 250 kB/second with 100%
CPU usage) which is unbearably slow if you have lots of files <= 8 MiB. I have
a 1 line patch to speed it up about 100-fold, but it only works on CURRENT -
10.2 panics with it. Will keep trying.

This is the sad state of current EXT4 support outside Linux...

-- 
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"