Re: Address Collision using i386 4G/4G Memory Split
On Mon, Dec 17, 2018 at 02:51:48PM +0100, Alexander Lochmann wrote:
> Hi folks!
>
> According to git commit e3089a (https://reviews.freebsd.org/D1463)
> FreeBSD 12.0 i386 uses separate address spaces for kernel and user
> space. So basically two memory areas, one in each space, can have the
> same address.
> Is this possible with FreeBSD 12.0? Is this likely to happen?
The feature was added to HEAD during this summer, before stable/12 was
branched.
>
> On my opinion, this is also very expensive in terms of performance.
> Any copy{in,out} has to flush the TLB.
> (http://fxr.watson.org/fxr/source/i386/i386/copyout_fast.s#L91)
> Why are you still using this 4G/4G approach?
Because it is needed for i386 to self-host, in modern world 1G KVA
is too small, and because it provides Meltdown mitigation.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Address Collision using i386 4G/4G Memory Split
Alexander Lochmann writes:
According to git commit e3089a (https://reviews.freebsd.org/D1463)
FreeBSD 12.0 i386 uses separate address spaces for kernel and user
space. So basically two memory areas, one in each space, can have the
same address.
Is this possible with FreeBSD 12.0? Is this likely to happen?
If the userspace program and the kernel address happen to overlap, the
system will deal with it. There's not anything to worry about. As to
whether or not it's likely to happen -- I'm not sure about that. I
expect the default stack and heap space locations for a fresh process
have changed due to this change, but it should not matter.
On my opinion, this is also very expensive in terms of performance.
Any copy{in,out} has to flush the TLB.
(http://fxr.watson.org/fxr/source/i386/i386/copyout_fast.s#L91)
Why are you still using this 4G/4G approach?
The complete split between the user address space and kernel address
space mapping is largely due to the mitigation of the Spectre attacks,
as I understand things. To have both the kernel and userspace mapped
at the same time, can be used to extract information from the kernel
that should not be made available.
I think it falls into the "slower but safer" class of change.
Someone will, undoubtedly, correct me if I'm wrong.
-Kurt
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: mps and LSI SAS2308: controller resets on 12.0 - IOC Fault 0x40000d04, Resetting
On 12/17/2018 10:52 AM, Mark Martinec wrote: > Anyone else seen problems with mps driver and LSI SAS2308 controller? > > (btw, on another machine the mps driver with LSI SAS2004 is working > just fine under 12.0) Sort of ran into this as well, but with the mfi driver. The same card in *some* machines would boot just fine, but in others, it would hang at boot time. Not sure if its related or not https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231432 I was able to get a MegaRAID SAS-3 3108 [Invader] card working by forcing it to use the mrsas driver instead of the mfi. However, my 9240s fail with the mfi and they will not work with the mrsas ---Mike -- --- Mike Tancsa, tel +1 519 651 3400 x203 Sentex Communications, m...@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
mps and LSI SAS2308: controller resets on 12.0 - IOC Fault 0x40000d04, Resetting
One of our servers that was upgraded from 11.2 to 12.0 (to RC2 initially, then to RC3 and lastly to a 12.0-RELEASE) is suffering severe instability of a disk controller, resetting itself a couple of times a day, usually associated with high disk usage (like poudriere buils or zfs scrub or nightly file system scans). The same setup was rock-solid under 11.2 (and still/again is). The disk controller is LSI SAS2308. It has four disks attached as JBODs, one pair of SSDs and one pair of hard disks, each pair forming its own zpool. A controller reset can occur regardless of which pair is in heavy use. The following can be found in logs, just before machine becomes unusable (although not logged always, as disks may be dropped before syslog has a chance of writing anything): xxx kernel: [2382] mps0: IOC Fault 0x4d04, Resetting xxx kernel: [2382] mps0: Reinitializing controller xxx kernel: [2383] mps0: Firmware: 20.00.02.00, Driver: 21.02.00.00-fbsd xxx kernel: [2383] mps0: IOCCapabilities: 5a85c xxx kernel: [2383] (da0:mps0:0:0:0): Invalidating pack The IOC Fault location is always the same. Apparently the disk controller resets, all disk devices are dropped and ZFS finds itself with no disks. The machine still responds to ping, and if logged-in during the event and running zpool status -v 1, zfs reports loss of all devices for each pool: pool: data0 state: UNAVAIL status: One or more devices are faulted in response to IO failures. action: Make sure the affected devices are connected, then run 'zpool clear'. see: http://illumos.org/msg/ZFS-8000-HC scan: scrub repaired 0 in 0 days 03:53:41 with 0 errors on Sat Nov 17 00:22:38 2018 config: NAME STATE READ WRITE CKSUM data0 UNAVAIL 0 0 0 mirror-0UNAVAIL 024 0 2396428274137360341 REMOVED 0 0 0 was /dev/gpt/da2-PN1334PCKAKD4S 16738407333921736610 REMOVED 0 0 0 was /dev/gpt/da3-PN2338P4GJ1XYC (and similar for the other pool) At this point the machine is unusable and needs to be hard-reset. My guess is that after the controller resets, disk devices come up again (according to the report seen on the console, stating 'periph destroyed' first, then listing full info on each disk) - but zfs ignores them. I don't see any mention of changes of the mps driver in the 12.0 release notes, although diff-ing its sources between 11.2 and 12.0 shows plenty of nontrivial changes. After suffering this instability for some time, I finally downgraded the OS to 11.2, and things are back to normal again! This downgrade path was nontrivial, as I have foolishly upgraded pool features to what comes with 12.0, so downgrading involved hacking with dismantling both zfs mirror pools, recreating pools without the two new features, zfs send/receive copying, while having a machine hang during some of these operations. Not something for the faint at heart. I know, foolish of me to upgrade pools after just one day of uptime with 12.0. Some info on the controller: kernel: mps0: port 0xf000-0xf0ff mem 0xfbe4- 0xfbe4,0xfbe0-0xfbe3 irq 64 at device 0.0 numa-domain 1 on pci11 kernel: mps0: Firmware: 20.00.02.00, Driver: 21.02.00.00-fbsd mpsutil shows: mps0 Adapter: Board Name: LSI2308-IT Board Assembly: Chip Name: LSISAS2308 Chip Revision: ALL BIOS Revision: 7.39.00.00 Firmware Revision: 20.00.02.00 Integrated RAID: no So, what has changed in the mps driver for this to be happening? Would it be possible to take mps driver sources from 11.2, transplant them to 12.0, recompile, and use that? Could the new mps driver be using some new feature of the controller and hits a firmware bug? I have resisted upgrading SAS2308 firmware and its BIOS, as it is working very well under 11.2. Anyone else seen problems with mps driver and LSI SAS2308 controller? (btw, on another machine the mps driver with LSI SAS2004 is working just fine under 12.0) Mark ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Common Desktop Environment broken when compiling from ports tree on FreeBSD 12 RC3 (May also apply to the final build)
pon., 17 gru 2018 o 00:42 Alex McKeever napisał(a): > > I ran into problems compiling the CDE in FreeBSD 12.0 RC3 (PowerPC) on my > eMac. It says it is broken and cannot be compiled. Also, any ETA on when this > port of the OS will go into Tier 1? Compiling software, desktop environments, > X11, using 11.1 and the now unsupported 10.4 failed when I tried those a > while back (and personally I have been partial to Linux and how easily I can > just get software via APT or Zypper... I would be running Debian Sid if they > didn’t drop support for the eMac in terms of my internal display not working > after Jessie) FWIW, the x11/cde port is not just broken on MIPS and PowerPC; it's marked broken on FreeBSD 12 on all architectures. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Address Collision using i386 4G/4G Memory Split
Hi folks!
According to git commit e3089a (https://reviews.freebsd.org/D1463)
FreeBSD 12.0 i386 uses separate address spaces for kernel and user
space. So basically two memory areas, one in each space, can have the
same address.
Is this possible with FreeBSD 12.0? Is this likely to happen?
On my opinion, this is also very expensive in terms of performance.
Any copy{in,out} has to flush the TLB.
(http://fxr.watson.org/fxr/source/i386/i386/copyout_fast.s#L91)
Why are you still using this 4G/4G approach?
Regards,
Alex
--
Technische Universität Dortmund
Alexander LochmannPGP key: 0xBC3EF6FD
Otto-Hahn-Str. 16 phone: +49.231.7556141
D-44227 Dortmund fax:+49.231.7556116
http://ess.cs.tu-dortmund.de/Staff/al
signature.asc
Description: OpenPGP digital signature
Re: Common Desktop Environment broken when compiling from ports tree on FreeBSD 12 RC3 (May also apply to the final build)
Hi people, (and thanks Alan for copying me in) On 2018-12-17 01:42, Mark Linimon wrote: On Sun, Dec 16, 2018 at 04:35:32PM -0500, Alex McKeever wrote: I ran into problems compiling the CDE in FreeBSD 12.0 RC3 (PowerPC) on my eMac. I don't know of anyone else who has tried to run it. The server-class ports on powerpc64 have been in good shape for several years. However, the desktop ports are lagging way behind. For instance, we are still working to get gnome and kde working properly. Other desktop environments are going to require more people to take up working on them. I personally would like to see powerpc64 ports at (near-) parity with amd64, but we have a lot of work to go yet. I'm not sure if it's supported on PowerPC at all anyway by the developers (although obviously it used to work, perhaps not on FreeBSD though). Was it a straightforward error? Chris -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: APU2, legacy firmware 4.0.22, FreeBSD 12.0 hangs in boot
Hi! > Our developers ask for the full log you could provide. Below the boot1 with 4.0.22, that stalled. And the boot2, with 4.8.0.5, that worked. Serial Number: 1086158 -boot1--- PC Engines apu2 coreboot build 20180312 BIOS version v4.0.22 4080 MB ECC DRAM SeaBIOS (version rel-1.11.0.7-0-gdc51f90) Press F10 key now for boot menu Booting from Hard Disk... //bbtt//ccoonnffiigg:: --DDhh --SS5522000 0 CCoonnssoolleess:: iinntteerrnnaall vviiddeeoo//kkeeyybbooaarrdd sseerriiaall ppoorrtt BBIIOOSS ddrriivvee CC:: iiss ddiisskk00 ||// --\\||//-- \\||//--\\||//--\\||//--\\||//--\\||//--\\||//--\\ ||//--\\||//BBIIOOSS 663399kkBB//3388779922kkBB aavvaaiillaabbllee mmeemmoorryy FFrrBBSSDD//xx8866 bbttssttrraapp llooaaddeerr,, RReevviissiioonn 11..11 --\\||//-- \\||//--\\||//--\\||//--\\|| //--\\||//--\\||//--\\||//--\\||//--\\||//--\\||//--\\||//-- \\||//--\\||//--\\||//--\\||//--\\||//--\\||//--\\||//--\\||//--\\ ||//--\\||//--\\||//--\\||//--\\||//--\\||//--\\||//--\\||//--\\ ||//--\\||//--\\||//--\\||//--\\||//--\\||//--\\||//--\\||//--\\||// --\\||//--\\||//--\\||//--\\||//--\\||//--\\||//--\\||//--\\||//--\\||//--\\|| //--\\||//--\\||//--\\||//--\\||//--\\||//--\\||//--\\||//--\\||//--\\||//--\\||//--\\||// --\\||//--\\||//--\\||//--\\||//--\\||//--\\||//--\\||//--\\|| //--\\||//--\\||//--\\||//--\\||//--\\||//--\\||//--\\||//--\\||//--\\||//--\\||//--\\|| //--\\||//--\\||//--\\||//--\\||//--\\||//--\\||//--\\||//--\\||//--\\||//--\\||//--\\||//--\\|| //LLooaaddiinngg //bbtt//ddeeffaauullttss//llooaaddeerr..ccoonnff LLooaaddiinngg //bbtt//ddeevviiccee..hhiinnttss --\\||//--\\||//--\\ LLooaaddiinngg //bbtt//llooaaddeerr..ccoonnff ||//--\\||//--\\||//Loading /boot/loader.conf.local ```` s` `.---...--.``` -/ +o .--` /y:` +. yo`:.:o `+- y/ -/` -o/ .- ::/sy+:. / `-- / `: :` `: :` / / .- -. -- -.`:` `:` .-- `--. .---.. __ _ _ | | | _ \ / | __ \ | |___ _ __ ___ ___ | |_) | (___ | | | | | ___| '__/ _ \/ _ \| _ < \___ \| | | | | | | | | __/ __/| |_) |) | |__| | | | | | |||| | | | |_| |_| \___|\___||/|_/|_/ ??Welcome to FreeBSD1. Boot Multi user [Enter]2. Boot Single user3. Escape to loader prompt4. RebootOptions:5. Kernel: default/2kernel (1 of 1)6. Boot OptionsAutoboot in 10 seconds, hit [Enter] to boot or any other key to stop Autoboot in 9 seconds, hit [Enter] to boot or any other key to stop Autoboot in 8 seconds, hit [Enter] to boot or any other key to stop Autoboot in 7 seconds, hit [Enter] to boot or any other key to stop Autoboot in 6 seconds, hit [Enter] to boot or any other key to stop Autoboot in 5 seconds, hit [Enter] to boot or any other key to stop Autoboot in 4 seconds, hit [Enter] to boot or any other key to stop Autoboot in 3 seconds, hit [Enter] to boot or any other key to stop Autoboot in 2 seconds, hit [Enter] to boot or any other key to stop Autoboot in 1 seconds, hit [Enter] to boot or any other key to stop Autoboot in 0 seconds, hit [Enter] to boot or any other key to stop Loading kernel... /boot/kernel/kernel text=0x1678a68 data=0x1cd288+0x768b40 syms=[0x8+0x174cd8+0x8+0x19224a] Loading configured modules... /boot/entropy size=0x1000 /boot/kernel/zfs.ko size 0x3a9a10 at 0x263e000 loading required module 'opensolaris' /boot/kernel/opensolaris.ko size 0xa4f0 at 0x29e8000 ---<>--- Copyright (c) 1992-2018 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 12.0-RELEASE r341666 GENERIC amd64 FreeBSD clang version 6.0.1 (tags/RELEASE_601/final 335540) (based on LLVM 6.0.1) VT(vga): resolution 640x480 CPU: AMD GX-412TC SOC(998.15-MHz K8-class CPU) Origin="AuthenticAMD" Id=0x730f01 Family=0x16 Model=0x30 Stepping=1 Features=0x178bfbff Features2=0x3ed8220b AMD Features=0x2e500800 AMD Features2=0x1d4037ff Structured Extended Features=0x8 XSAVE Features=0x1 SVM: NP,NRIP,AFlush,DAssist,NAsids=8 TSC: P-state invariant, performance statistics real memory = 4815060992 (4592 MB) avail memory = 4092137472 (3902 MB) Event timer "LAPIC" quality 600 ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs FreeBSD/SMP: 1 package(s) x 4 core(s) random:
Re: APU2, legacy firmware 4.0.22, FreeBSD 12.0 hangs in boot
Hi, Our developers ask for the full log you could provide. Thanks. Best regards, Michael Steinmann Am Sa., 15. Dez. 2018 um 21:00 Uhr schrieb Kurt Jaeger : > Hi! > > Testing FreeBSD 12.0 on an apu2d4 with WLAN board, after upgrading to > > http://pcengines.ch/file/apu2_v4.0.22.rom.tar.gz > > the boot hangs after: > > [...] > Event timer "RTC" frequency 32768 Hz quality 0 > attimer0: port 0x40-0x43 irq 0 on acpi0 > Timecounter "i8254" frequency 1193182 Hz quality 0 > Event timer "i8254" frequency 1193182 Hz quality 100 > hpet0: iomem 0xfed0-0xfed003ff on acpi0 > Timecounter "HPET" frequency 14318180 Hz quality 950 > Timecounter "ACPI-safe" frequency 3579545 Hz quality 850 > acpi_timer0: <32-bit timer at 3.579545MHz> port 0x818-0x81b on acpi0 > acpi_button0: on acpi0 > pcib0: port 0xcf8-0xcff on acpi0 > pci0: on pcib0 > > It booted with the former version, but very slowly. > > I can provide a full boot log if required. Any ideas ? > > -- > p...@freebsd.org +49 171 3101372 2 years to go ! > ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: APU2, legacy firmware 4.0.22, FreeBSD 12.0 hangs in boot
Hi, Thanks, we'll look at it ... Best regards, Michael Steinmann Am Sa., 15. Dez. 2018 um 21:40 Uhr schrieb Kurt Jaeger : > Hi! > > > Testing FreeBSD 12.0 on an apu2d4 with WLAN board, after upgrading to > > > > http://pcengines.ch/file/apu2_v4.0.22.rom.tar.gz > > > > the boot hangs after: > > With apu2_v4.8.0.5.rom it boots. > > -- > p...@freebsd.org +49 171 3101372 2 years to go ! > ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
