Re: PAE broken on -current, likely broken on stable/9
Hi, On Mon, Dec 5, 2011 at 11:12 PM, Arnaud Lacombe wrote: > On Mon, Dec 5, 2011 at 5:15 PM, Arnaud Lacombe wrote: >> Hi, >> >> The kernel tree is utterly broken when PAE is enabled, it chokes >> [non-exclusively] on the following: >> > After finally having been able to complete a build, the resulting > kernel miserably panics on: > > real memory: 25769803776 (24576 MB) > panic: kmem_suballoc: bad status return of 3 > Just for the fun, after having fought for 8h for nearly nothing with FreeBSD, I thought it would be fair to give it a try with Linux, say the latest -rc, that is 3.2-rc3, with a snapshot of the upcoming openwrt. The result: root@OpenWrt:/# free total used free sharedbuffers Mem: 16628216 14864 16613352 0236 -/+ buffers:14628 16613588 Swap:0 0 0 total time spent to get to userland: about 30 min. too easy... Let's give it a try with a system with 32GB of RAM: root@OpenWrt:/# free total used free sharedbuffers Mem: 33274356 17124 33257232 0252 -/+ buffers:16872 33257484 Swap:0 0 0 d'oh! ok, I'm not entirely honest, tmpfs chocked: tmpfs: Bad value '1.70365e+10' for mount option 'size'. Let's give it a try with 60GB now: root@OpenWrt:/# free total used free sharedbuffers Mem: 62405104 17116 62387988 0256 -/+ buffers:16860 62388244 Swap:0 0 0 damn... Linux' no fun... :-( - Arnaud ps: the kernel actually panic with the full 64GB of RAM, while mounting the filesystem. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: PAE broken on -current, likely broken on stable/9
Hi *, [I could have renamed the subject 1001 fancy ways to crash FreeBSD, but I'll avoid :)] On Mon, Dec 5, 2011 at 5:15 PM, Arnaud Lacombe wrote: > Hi, > > The kernel tree is utterly broken when PAE is enabled, it chokes > [non-exclusively] on the following: > After finally having been able to complete a build, the resulting kernel miserably panics on: real memory: 25769803776 (24576 MB) panic: kmem_suballoc: bad status return of 3 This was with the default value of `vm.kmem_size' and `vm.kmem_size_max'. I cannot find a good value for either of them. With 2GB of RAM and 9.0RC2 (the release kernel), 700MB of kmem boots fine. The same and 750MB of kmem chokes, when bringing up userland, on: Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0xbfc0 fault code = supervisor read, page not present instruction pointer = 0x20:0xc0d4baca stack pointer = 0x28:0xc520f9dc frame pointer = 0x28:0xc520fa14 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, IOPL = 0 current process = 1 (kernel) trap number = 12 panic: page fault cpuid = 0 KDB: stack backtrace: #0 0xc0a4b027 at kdb_backtrace+0x47 #1 0xc0a185f7 at panic+0x117 #2 0xc0d48a03 at trap_fatal+0x323 #3 0xc0d48abd at trap_pfault+0xad #4 0xc0d49845 at trap+0x465 #5 0xc0d3279c at calltrap+0x6 #6 0xc09e57a0 at exec_map_first_page+0x430 #7 0xc09e61fc at kern_execve+0x58c #8 0xc09e75bc at sys_execve+0x4c #9 0xc09cb372 at start_init+0x292 #10 0xc09ea8d7 at fork_exit+0x97 #11 0xc0d32814 at fork_trampoline+0x8 Uptime: 1s Automatic reboot in 15 seconds - press a key on the console to abort With 12GB of RAM and 700MB of kmem, chokes early on: CPU: QEMU Virtual CPU version 0.14.50 (2660.71-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x633 Family = 6 Model = 3 Stepping = 3 Features=0x781abf9 Features2=0x8081 real memory = 12884901888 (12288 MB) panic: kmem_suballoc: bad status return of 3 cpuid = 0 KDB: enter: panic [ thread pid 0 tid 0 ] Stopped at kdb_enter+0x3a: movl$0,kdb_why db> bt Tracing pid 0 tid 0 td 0xc068edb0 kdb_enter(c0603b0a,c0603b0a,c061fbb4,c08f6cbc,0,...) at kdb_enter+0x3a panic(c061fbb4,3,0,0,c06c3a54,...) at panic+0x134 kmem_suballoc(c0ba6000,c06c3a54,c06c3a58,90f8000,1,...) at kmem_suballoc+0x85 vm_ksubmap_init(c06c3a4c,0,3,3000,0,...) at vm_ksubmap_init+0xbc cpu_startup(0,8f0020,8f0020,8f,8fb000,...) at cpu_startup+0x27c mi_startup() at mi_startup+0xac begin() at begin+0x2c db> Reverting to the default value for `vm.kmem_size' and `vm.kmem_size_max', 4GB (and 6GB) of RAM, with a PAE-enabled -current kernel triggers an infinite loop of: CPU: QEMU Virtual CPU version 0.14.50 (2660.40-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x633 Family = 6 Model = 3 Stepping = 3 Features=0x781abf9 Features2=0x8081 real memory = 6442450944 (6144 MB) kernel trap 12 with interrupts disabled kernel trap 12 with interrupts disabled kernel trap 12 with interrupts disabled kernel trap 12 with interrupts disabled [...] kernel trap 12 with interrupts disabled At this point, even FreeBSD 7.1 is better, as it goes at least up until: Copyright (c) 1992-2009 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 7.1-RELEASE-p13 #0: Mon Nov 21 17:23:05 UTC 2011 root@build:/freebsd/conf/PAE Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: QEMU Virtual CPU version 0.14.50 (2660.26-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x633 Stepping = 3 Features=0x781abf9 Features2=0x8081> real memory = 16642998272 (15872 MB) avail memory = 15784312832 (15053 MB) It hanged there for a while, I'm not sure if it's because the system is running on a VM with a disk-backed memory or another issue. I killed qemu at this point. 6GB was "fine" too. Coming back to -current, but now with `vm.kmem_size' and `vm.kmem_size_max' set to 512M, a 12G system boots: CPU: QEMU Virtual CPU version 0.14.50 (2660.39-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x633 Family = 6 Model = 3 Stepping = 3 Features=0x781abf9 Features2=0x8081 real memory = 12884901888 (12288 MB) avail memory = 12621688832 (12036 MB) Event timer "LAPIC" quality 400 ACPI APIC Table: ioapic0: Changing APIC ID to 1 ioapic0 irqs 0-23 on motherboard [...] up until right before multi-user, where it just directly reboot, without triggering any message: ada0: Previously was known as ad0 pass1 at ata1 bus 0 scbus1 target 0 lun 0 pass1: Removable CD-ROM SCSI-0 device pass1: 16.700MB/s transfers (WDMA2, ATAPI 12bytes, PIO 65534bytes) Timecounter "TSC" frequency 2660388588 Hz quality 800 /boot/kernel/kernel data=0xc3e4ec+0xbda74 syms=[0x4+0xaff70+0
Re: PAE broken on -current, likely broken on stable/9
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12/05/11 14:15, Arnaud Lacombe wrote: > Hi, > > The kernel tree is utterly broken when PAE is enabled, it chokes > [non-exclusively] on the following: > > dev/dpt/dpt_scsi.c:279: warning: cast to pointer from integer of > different size [-Wint-to-pointer-cast] [snip] [delphij@build] /usr/src/sys/i386/conf> grep dpt PAE nodevicedpt It seems you have added 'option PAE' in your own custom kernel configuration? Not all drivers works with PAE so these has to be removed. If PAE is a requirement, consider using the stock 'PAE' kernel configuration if you don't want to configure it the hard way. > Could re@ please includes, proudly (or not), in its future > announces, that PAE is no longer supported ? > > Thanks, - Arnaud > > ps: this is just a report, I'm not really expecting anything, any > longer, from the FreebSD "community". > ___ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current To > unsubscribe, send any mail to > "freebsd-current-unsubscr...@freebsd.org" - -- Xin LI https://www.delphij.net/ FreeBSD - The Power to Serve! Live free or die -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.18 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk7dSdIACgkQOfuToMruuMAT/wCggYzwl1LSt8rYqaRaRjwAWXtO 8fsAn1d5rctjsdMSY15cVG/eAM3rdPnB =n6sn -END PGP SIGNATURE- ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
PAE broken on -current, likely broken on stable/9
Hi, The kernel tree is utterly broken when PAE is enabled, it chokes [non-exclusively] on the following: dev/dpt/dpt_scsi.c:279: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast] dev/dpt/dpt_scsi.c:279: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast] dev/dpt/dpt_scsi.c:964: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast] dev/ida/ida.c:145: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast] dev/ida/ida.c:145: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast] dev/ida/ida.c:154: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast] dev/ida/ida.c:154: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast] dev/ida/ida_eisa.c:105: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast] dev/ida/ida_eisa.c:106: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast] dev/malo/if_malo_pci.c:232: warning: large integer implicitly truncated to unsigned type [-Woverflow] dev/malo/if_malo_pci.c:232: warning: large integer implicitly truncated to unsigned type [-Woverflow] dev/mwl/if_mwl_pci.c:210: warning: large integer implicitly truncated to unsigned type [-Woverflow] dev/mwl/if_mwl_pci.c:210: warning: large integer implicitly truncated to unsigned type [-Woverflow] dev/sym/sym_hipd.c:7922: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast] dev/trm/trm.c:648: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast] dev/hptmv/entry.c:2635: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast] dev/hptmv/entry.c:2765: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast] dev/hptmv/entry.c:2970: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast] Could re@ please includes, proudly (or not), in its future announces, that PAE is no longer supported ? Thanks, - Arnaud ps: this is just a report, I'm not really expecting anything, any longer, from the FreebSD "community". ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
