[Bug 202764] GPART corruption on Seagate ST9640423AS
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202764 Bug ID: 202764 Summary: GPART corruption on Seagate ST9640423AS Product: Base System Version: 10.2-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: ph...@rotfl.com.au Every reboot causes the secondary GPT header to become corrupt. dmesg snip... Copyright (c) 1992-2015 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-RELEASE #0 r28: Wed Aug 12 15:26:37 UTC 2015 r...@releng1.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 FreeBSD clang version 3.4.1 (tags/RELEASE_34/dot1-final 208032) 20140512 CPU: Intel(R) Core(TM) i7 CPU M 620 @ 2.67GHz (2660.06-MHz K8-class CPU) Origin="GenuineIntel" Id=0x20652 Family=0x6 Model=0x25 Stepping=2 Features=0xbfebfbff Features2=0x298e3ff AMD Features=0x28100800 AMD Features2=0x1 VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID TSC: P-state invariant, performance statistics real memory = 8589934592 (8192 MB) avail memory = 8256385024 (7873 MB) Event timer "LAPIC" quality 600 ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs FreeBSD/SMP: 1 package(s) x 2 core(s) x 2 SMT threads cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 4 cpu3 (AP): APIC ID: 5 ACPI BIOS Warning (bug): 32/64X FACS address mismatch in FADT: 0xCF36BF40/0xCF36ED40, using 64-bit address (20150515/tbfadt- 305) ada0 at ahcich0 bus 0 scbus0 target 0 lun 0 ada0: ATA8-ACS SATA 2.x device ada0: Serial Number 5WS0JWSP ada0: 300.000MB/s transfers (SATA 2.x, cd0 at ahcich1 bus 0 scbus1 target 0 lun 0 ada0: Command Queueing enabled ada0: 610480MB (1250263728 512 byte sectors: 16H 63S/T 16383C) ada0: quirks=0x1<4K> ada0: Previously was known as ad4 GEOM: ada0: the secondary GPT table is corrupt or invalid. GEOM: ada0: using the primary only -- recovery suggested. GEOM: diskid/DISK-5WS0JWSP: the secondary GPT table is corrupt or invalid. GEOM: diskid/DISK-5WS0JWSP: using the primary only -- recovery suggested. # uname -a FreeBSD catbert.rotfl.com.au 10.2-RELEASE FreeBSD 10.2-RELEASE #0 r28: Wed Aug 12 15:26:37 UTC 2015 r...@releng1.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 # gpart show =>34 1250263661 ada0 GPT (596G) [CORRUPT] 34 6- free - (3.0K) 401024 1 freebsd-boot (512K) 1064 1241512952 2 freebsd-ufs (592G) 1241514016 4194304 3 freebsd-swap (2.0G) 1245708320 4555375- free - (2.2G) # gpart status Name Status Components ada0p1 CORRUPT ada0 ada0p2 CORRUPT ada0 ada0p3 CORRUPT ada0 # gpart recover ada0 ada0 recovered # gpart status Name Status Components ada0p1 OK ada0 ada0p2 OK ada0 ada0p3 OK ada0 But after a reboot, it will be corrupt again. Either the gpart recover command isn't actually rewriting the secondary GPT header, or something in the shutdown process is corrupting 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 193672] FreeBSD UEFI boot panics with VirtualBox UEFI loader
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193672 Marcel Moolenaar changed: What|Removed |Added Status|New |Open --- Comment #9 from Marcel Moolenaar --- Is this bug still relevant? Can someone (Ed?) test again to see if the problem still exists? I for one can boot FreeBSD just fine in VirtualBox 5 with EFI and with just 1GB of memory. So maybe the problem got resolved and this bug can be closed? -- 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 202309] [uefi] smashed screen on HP Probook 430 G1 with UEFI
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202309 Oliver Pinter changed: What|Removed |Added CC||Ray"@FreeBSD.org, ||dumbb...@freebsd.org, ||mar...@freebsd.org See Also||https://bugs.freebsd.org/bu ||gzilla/show_bug.cgi?id=1940 ||63 CC|Ray"@FreeBSD.org|r...@freebsd.org Marcel Moolenaar changed: What|Removed |Added Status|New |Open CC|r...@freebsd.org | Assignee|freebsd-bugs@FreeBSD.org|mar...@freebsd.org Status|Open|In Progress --- Comment #1 from Marcel Moolenaar --- If I can read the screen correctly, it looks like the resolution is 1366x768, with a stride of 1366 and a color depth of 32 bits per pixel (or 4 bytes per pixel). The console output seems to be using a stride that's just wrong. Since the stride is coming from UEFI, it's hard to think of a reason why the kernel would do this. Have you tried updating the firmware? --- Comment #2 from Oliver Pinter --- Yes, today I updated to latest bios from HP, but the issue still exists. How could I extract these information without serial port or change the settings in loader or kernel? --- Comment #3 from Marcel Moolenaar --- Created attachment 160509 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=160509&action=edit loader with 'gop' command --- Comment #4 from Marcel Moolenaar --- (In reply to Oliver Pinter from comment #2) I committed revision 287299 (-current), that adds a 'gop' command to the loader. I attached a pre-compiled EFI loader with this command to this PR. Can you run 'gop get' and 'gop list' and add the output to this PR? Also: can you try different modes (if possible) and see if that makes a difference? -- 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 202309] [uefi] smashed screen on HP Probook 430 G1 with UEFI
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202309 Oliver Pinter changed: What|Removed |Added CC||Ray"@FreeBSD.org, ||dumbb...@freebsd.org, ||mar...@freebsd.org See Also||https://bugs.freebsd.org/bu ||gzilla/show_bug.cgi?id=1940 ||63 CC|Ray"@FreeBSD.org|r...@freebsd.org Marcel Moolenaar changed: What|Removed |Added Status|New |Open CC|r...@freebsd.org | --- Comment #1 from Marcel Moolenaar --- If I can read the screen correctly, it looks like the resolution is 1366x768, with a stride of 1366 and a color depth of 32 bits per pixel (or 4 bytes per pixel). The console output seems to be using a stride that's just wrong. Since the stride is coming from UEFI, it's hard to think of a reason why the kernel would do this. Have you tried updating the firmware? --- Comment #2 from Oliver Pinter --- Yes, today I updated to latest bios from HP, but the issue still exists. How could I extract these information without serial port or change the settings in loader or kernel? --- Comment #3 from Marcel Moolenaar --- Created attachment 160509 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=160509&action=edit loader with 'gop' command -- 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 202309] [uefi] smashed screen on HP Probook 430 G1 with UEFI
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202309 Oliver Pinter changed: What|Removed |Added CC||Ray"@FreeBSD.org, ||dumbb...@freebsd.org, ||mar...@freebsd.org See Also||https://bugs.freebsd.org/bu ||gzilla/show_bug.cgi?id=1940 ||63 CC|Ray"@FreeBSD.org|r...@freebsd.org Marcel Moolenaar changed: What|Removed |Added Status|New |Open CC|r...@freebsd.org | Assignee|freebsd-bugs@FreeBSD.org|mar...@freebsd.org --- Comment #1 from Marcel Moolenaar --- If I can read the screen correctly, it looks like the resolution is 1366x768, with a stride of 1366 and a color depth of 32 bits per pixel (or 4 bytes per pixel). The console output seems to be using a stride that's just wrong. Since the stride is coming from UEFI, it's hard to think of a reason why the kernel would do this. Have you tried updating the firmware? --- Comment #2 from Oliver Pinter --- Yes, today I updated to latest bios from HP, but the issue still exists. How could I extract these information without serial port or change the settings in loader or kernel? --- Comment #3 from Marcel Moolenaar --- Created attachment 160509 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=160509&action=edit loader with 'gop' command -- 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 194792] [amdtemp] [patch] all cpu support
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194792 Dan Langille changed: What|Removed |Added CC||d...@freebsd.org --- Comment #3 from Dan Langille --- CPU temps is very good to have. -- 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 202730] UEFI boot and console problems on 2008 Mac Pro w/ 10.2-STABLE
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202730 Marcel Moolenaar changed: What|Removed |Added Assignee|freebsd-bugs@FreeBSD.org|mar...@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 202730] UEFI boot and console problems on 2008 Mac Pro w/ 10.2-STABLE
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202730 Marcel Moolenaar changed: What|Removed |Added CC||mar...@freebsd.org --- Comment #2 from Marcel Moolenaar --- Just a thought: Macs have firewire. It may be possible to enable dcons in the kernel and connect another FreeBSD machine to the Mac Pro using firewire and run dconschat on that other FreeBSD machine. Also: if you suspect that the Mac is running FreeBSD fine, you may be able to ssh into the machine and get the dmesg output. If you use DHCP, then it probably has the same IP address as before. I think the only tweak you may need to make is to configure SSHD on the memstick to allow root login (or alternatively, mount the memstick, chroot into it and add a user). I guess what I would want to know at this time is whether VT uses the efifb driver or not. If not, then a solution pivots around finding the answer to the question: why isn't VT not using efifb. If it is already using efifb, then a solution pivots around: why aren't we seeing anything on the monitor? Both questions probably need information about the graphics protocol and graphics mode, which we should be able to get by tweaking the loader. -- 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 202730] UEFI boot and console problems on 2008 Mac Pro w/ 10.2-STABLE
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202730 --- Comment #1 from Marcel Moolenaar --- *** Bug 202731 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 202731] UEFI boot and console problems on 2008 Mac Pro w/ 10.2-STABLE
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202731 Marcel Moolenaar changed: What|Removed |Added Resolution|--- |DUPLICATE Status|New |Closed CC||mar...@freebsd.org --- Comment #1 from Marcel Moolenaar --- *** This bug has been marked as a duplicate of bug 202730 *** -- 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 202741] [regression][patch] ranlib's deterministic mode broken since r286024
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202741 Ed Maste changed: What|Removed |Added CC||ema...@freebsd.org 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 200628] Wired memory not released after deletion from ZFS, kernel kills processes
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200628 Vladimir Laskov changed: What|Removed |Added CC||samflan...@gmail.com --- Comment #1 from Vladimir Laskov --- my test case on 10.2-RELEASE amd64 1. create 1G file # dd if=/dev/urandom bs=1024 count=1024 of=blockout.bin 2. while : ; do cat blockout.bin ; done | pv -brt | dd bs=1024k count=16000 of=blockout2.bin 3. see Wired and ARC counts on 'top' output 4. remove blockout2.bin 5. see Wired and ARC counts on 'top' output my solution: disable UMA for ZFS vfs.zfs.zio.use_uma="0" vfs.zfs.arc_max="16G" try 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 202741] [regression][patch] ranlib's deterministic mode broken since r286024
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202741 --- Comment #1 from f...@fabiankeil.de --- Created attachment 160479 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=160479&action=edit usr.bin/ar: Fix deterministic mode when running as ranlib -- 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 202741] [regression][patch] ranlib's deterministic mode broken since r286024
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202741 Bug ID: 202741 Summary: [regression][patch] ranlib's deterministic mode broken since r286024 Product: Base System Version: 11.0-CURRENT Hardware: Any OS: Any Status: New Keywords: patch, regression Severity: Affects Some People Priority: --- Component: bin Assignee: freebsd-bugs@FreeBSD.org Reporter: f...@fabiankeil.de Keywords: patch, regression r286024 lets ranlib ignore the -D flag and default to non-deterministic mode as the chunk that sets AR_D is only reached when running as ar. The attached patch is one way to fix this. Obtained from ElectroBSD. -- 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 202740] vi/ex string substitution problem when there is multiple occurrences in a line
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202740 Bug ID: 202740 Summary: vi/ex string substitution problem when there is multiple occurrences in a line Product: Base System Version: 10.2-STABLE Hardware: Any OS: Any Status: New Severity: Affects Many People Priority: --- Component: bin Assignee: freebsd-bugs@FreeBSD.org Reporter: fnoyan...@yahoo.com Created attachment 160478 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=160478&action=edit ex string substutition bug demonstration ex/vi implementations in 10.2-RELEASE, and 11.0-CURRENT have issues with string substitution when the phrase that would be replaced with a new one appears in a single line more than once. This phenomena is visible when ex(1) is invoked with -s and -c options. Attached text file includes step by step demonstration of the problem. The last command in the attached file always fails. Problem is most probably visible in older versions of FreeBSD as well, I have only tested on these two systems. -- 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 202708] netstat(1) output depends on options order
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202708 --- Comment #2 from Dmitry Sivachenko --- Yes, I understands that, the point was that when options are mutually exclusive, an error should be produces instead, and not silently change behaviour. -- 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"
