Re: i915kms.ko regression?
On 22 May 2015 at 00:00, Stefan Parvu spa...@kronometrix.org wrote: Does -HEAD do the same thing still? I tried that couple of days back. Yes, same problem: blank screen, no luck with any settings like backlight. I can easily ssh and reboot or CTRL-ALT-F1 and CTRL-C and reboot (you see nothing on the screen) :) ok. i really do bet it's a backlight config problem, and unfortunately I don't have the laptop to be able to debug it. Sorry :( -a ___ 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: i915kms.ko regression?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 So, here's what I know. My UX32VD works okay if you back out https://svnweb.freebsd.org/changeset/base/277959 The problem with it is, once you do back that out, you won't be able to set the brightness anymore (via acpi_asus_wmi). Adrian- do you remember where you found the backlight tunable and which it was? I could back out those changes, install stock lemul (instead of backed-out 277959 + lemul), and see what happens. - -Johannes On 05/22/2015 10:10, Adrian Chadd wrote: On 22 May 2015 at 00:00, Stefan Parvu spa...@kronometrix.org wrote: Does -HEAD do the same thing still? I tried that couple of days back. Yes, same problem: blank screen, no luck with any settings like backlight. I can easily ssh and reboot or CTRL-ALT-F1 and CTRL-C and reboot (you see nothing on the screen) :) ok. i really do bet it's a backlight config problem, and unfortunately I don't have the laptop to be able to debug it. Sorry :( -a - -- Johannes Meixner| FreeBSD Committer x...@freebsd.org | http://people.freebsd.org/~xmj -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQEcBAEBCAAGBQJVXuswAAoJEPyeKTcbGw0LSbQIAJjRMmtKTn1SAYfsHhsp7N5x twizIEZpgttmjaMJr6FuOWt3ItmfXWhxuQaqRZrb0xazzt9Pg1d1DHmmDOXihuXc JaEM603/J/SrsvYz7lJgy9MXC4ErN453aRYupNkEQGtSqk2pQt/l+JvoVdQi+dLp pffmGD4mJFw4B9B0eGrAINrWzNi3so7P3CqRgrIf1B14WBGX2Nreq60MFdS5CrjV A0UONsJrMKPB9oyskfA9RHmtNI4UYUbDeyLl+X9LOz8zYlNI4l6/CfMZcKdUzmzh gQ3NqPERsdFw7s0DLZmx0jv42lYg6f2jEti7JRzgHVD900PGz49vk5XbqcwY2JM= =l5uv -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
Re: i915kms.ko regression?
ok. i really do bet it's a backlight config problem, and unfortunately I don't have the laptop to be able to debug it. Sorry :( no worries. But what does this mean in practice for future: do we need to wait for a new drm2 update or this problem will stay this way until somebody really does fix it ? -- Stefan Parvu spa...@kronometrix.org ___ 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: i915kms.ko regression?
Does -HEAD do the same thing still? I tried that couple of days back. Yes, same problem: blank screen, no luck with any settings like backlight. I can easily ssh and reboot or CTRL-ALT-F1 and CTRL-C and reboot (you see nothing on the screen) :) -- Stefan Parvu spa...@kronometrix.org ___ 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
FreeBSD_HEAD-tests - Build #1048 - Fixed
FreeBSD_HEAD-tests - Build #1048 - Fixed: Check console output at https://jenkins.freebsd.org/job/FreeBSD_HEAD-tests/1048/ to view the results. ___ 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: i915kms.ko regression?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 05/22/2015 11:55, Lutz Bichler wrote: - after some more syncing with Linux 3.5.7, brightness control using hw.acpi.video.lcd0.brightness works again How did you make that happen? Do you have a diff you could share? - brightness control using the function keys (acpi_asus_wmi?) never really worked, neither before nor after the changes to drm2/i915. Indeed. Do we actually have a tool with which I could ... keylog, for lack of a better word, all ACPI events, send them (the event name, debug info etc) to syslog, and so on? If there was, I could take a crack at making those buttons work. - -- Johannes Meixner| FreeBSD Committer x...@freebsd.org | http://people.freebsd.org/~xmj -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQEcBAEBCAAGBQJVXxPbAAoJEPyeKTcbGw0LxMcH/1vgxmS54QYOSABovDpEryEs A7hPRbXpM6sO0pvSEOYqCQKI8SyQlQh7061L3NxXM2ynjqLDwhJmZJwRA8uVbDqy U8bcWDmp3WdJ6vNymB/Ooat+1HtKKpi48LW+hdhDefBbUJP8WXd/pv+8v7iS9xHb +WcnAP/VDhoydzLgh7fK7wJFmOlYGfAFr7k7d2Huamo6kam96Z6Dktlh4E8ZTAYi ex36QBOYmaMZ2iKJLJb5Z2DYFpe7BiKNbzANGF3FOJN510iiJrhy5h8rF00KTEzH mTQXlQ1keH3broYA42r8jiLaNhGOtufCfEQH8pZucSgdSc9Hc8zkcHlNUx3eCdM= =i4es -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
Re: i915kms.ko regression?
Hi, on my UX31A it is/was like this: - after 277959 the display was dark - backing out 277959 gave full brightness, but no brightness control using hw.acpi.video.lcd0.brightness anymore - after some more syncing with Linux 3.5.7, brightness control using hw.acpi.video.lcd0.brightness works again - brightness control using the function keys (acpi_asus_wmi?) never really worked, neither before nor after the changes to drm2/i915. Regards, Lutz 2015-05-22 10:39 GMT+02:00 Johannes Jost Meixner x...@freebsd.org: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 So, here's what I know. My UX32VD works okay if you back out https://svnweb.freebsd.org/changeset/base/277959 The problem with it is, once you do back that out, you won't be able to set the brightness anymore (via acpi_asus_wmi). Adrian- do you remember where you found the backlight tunable and which it was? I could back out those changes, install stock lemul (instead of backed-out 277959 + lemul), and see what happens. - -Johannes On 05/22/2015 10:10, Adrian Chadd wrote: On 22 May 2015 at 00:00, Stefan Parvu spa...@kronometrix.org wrote: Does -HEAD do the same thing still? I tried that couple of days back. Yes, same problem: blank screen, no luck with any settings like backlight. I can easily ssh and reboot or CTRL-ALT-F1 and CTRL-C and reboot (you see nothing on the screen) :) ok. i really do bet it's a backlight config problem, and unfortunately I don't have the laptop to be able to debug it. Sorry :( -a - -- Johannes Meixner| FreeBSD Committer x...@freebsd.org | http://people.freebsd.org/~xmj -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQEcBAEBCAAGBQJVXuswAAoJEPyeKTcbGw0LSbQIAJjRMmtKTn1SAYfsHhsp7N5x twizIEZpgttmjaMJr6FuOWt3ItmfXWhxuQaqRZrb0xazzt9Pg1d1DHmmDOXihuXc JaEM603/J/SrsvYz7lJgy9MXC4ErN453aRYupNkEQGtSqk2pQt/l+JvoVdQi+dLp pffmGD4mJFw4B9B0eGrAINrWzNi3so7P3CqRgrIf1B14WBGX2Nreq60MFdS5CrjV A0UONsJrMKPB9oyskfA9RHmtNI4UYUbDeyLl+X9LOz8zYlNI4l6/CfMZcKdUzmzh gQ3NqPERsdFw7s0DLZmx0jv42lYg6f2jEti7JRzgHVD900PGz49vk5XbqcwY2JM= =l5uv -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
Re: xargs -P0 suport
On 05/21/15 23:25, Allan Jude wrote: On 2015-05-21 21:55, Nikolai Lifanov wrote: Hi current@! Can someone take a look at Bugzilla #199976 please? It's a pretty trivial patch that adds -P0 support to xargs. If there is any feedback or the patch is wrong, I can rework it. I've been running CURRENT with it for a bit now with no problems. I would like very much for it to make it to 10.2-RELEASE. It would make it much easier for me to convert some systems to FreeBSD as many custom scripts that use it will be able to port as-is. Thank you! - Nikolai Lifanov ___ 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 This has been submitted for code review https://reviews.freebsd.org/D2616 Thanks! - Nikolai Lifanov ___ 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: xargs -P0 suport
On 2015-05-22 11:31, Nikolai Lifanov wrote: On 05/21/15 23:25, Allan Jude wrote: On 2015-05-21 21:55, Nikolai Lifanov wrote: Hi current@! Can someone take a look at Bugzilla #199976 please? It's a pretty trivial patch that adds -P0 support to xargs. If there is any feedback or the patch is wrong, I can rework it. I've been running CURRENT with it for a bit now with no problems. I would like very much for it to make it to 10.2-RELEASE. It would make it much easier for me to convert some systems to FreeBSD as many custom scripts that use it will be able to port as-is. Thank you! - Nikolai Lifanov ___ 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 This has been submitted for code review https://reviews.freebsd.org/D2616 Thanks! - Nikolai Lifanov ___ 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 There is some question about if nargs is a sane value for maxprocs in the negative case. 5000 does seem a bit high, and the behaviour can get wonky depending on the order you specify -P and -n together on the command line. Any suggestions? -- Allan Jude signature.asc Description: OpenPGP digital signature
Re: Fwd: UMA initialization failure with 48 core ARM64
2015-05-22 16:36 GMT+02:00 Konstantin Belousov kostik...@gmail.com: On Fri, May 22, 2015 at 04:14:13PM +0200, Micha?? Stanek wrote: Success! I am finally able to boot 48 cores. I have been trying out different values given to uma_prealloc() and uma_zone_reserve(). It started working when I increased the parameter in uma_prealloc() 32 times and left uma_zone_reserve() as it was originally. UMA_BOOT_PAGES also needs to be set to 512. Thank you very much for your help. Do you know how the value to uma_prealloc() should scale with the number of CPUs? If it is not obvious, then maybe for now we should make a #define with a value to multiply BT_MAXALLOC by, with a comment that a higher number is required on platforms with many CPUs. What do you think the final fix should look like? I suspect it is not only the number of CPUs which makes the play. Note that the number of tags is already scaled with the number of CPUs. It is also the question of how much the given architecture needs to allocate before the normal uma/vmem mechanisms start working. My quess is that arm64 performes more kva_alloc()s on early stages than other architectures. I am forwarding the result of my conversation with Konstantin Belousov. With his help I was able to boot 48 cores on an arm64 platform. I needed to set UMA_BOOT_PAGES=512 and increase the parameter given to uma_prealloc() in vmem_startup() 32 times (giving 32 * BT_MAXALLOC). It looks like this should be made configurable to avoid running out of space for initial allocations on some platforms. In our case, the panic happened still in SI_SUB_VM sysinit. Best regards, Michal Stanek ___ 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: i915kms.ko regression?
Hi, That fix came from the linux commit hash i mentioned in the commit. I found the backlight tunable in the i915 source. :) (My asus zenbook works with that in -head, btw. But I dn't have acpi_asus_wmi loaded.) -adrian On 22 May 2015 at 01:39, Johannes Jost Meixner x...@freebsd.org wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 So, here's what I know. My UX32VD works okay if you back out https://svnweb.freebsd.org/changeset/base/277959 The problem with it is, once you do back that out, you won't be able to set the brightness anymore (via acpi_asus_wmi). Adrian- do you remember where you found the backlight tunable and which it was? I could back out those changes, install stock lemul (instead of backed-out 277959 + lemul), and see what happens. - -Johannes On 05/22/2015 10:10, Adrian Chadd wrote: On 22 May 2015 at 00:00, Stefan Parvu spa...@kronometrix.org wrote: Does -HEAD do the same thing still? I tried that couple of days back. Yes, same problem: blank screen, no luck with any settings like backlight. I can easily ssh and reboot or CTRL-ALT-F1 and CTRL-C and reboot (you see nothing on the screen) :) ok. i really do bet it's a backlight config problem, and unfortunately I don't have the laptop to be able to debug it. Sorry :( -a - -- Johannes Meixner| FreeBSD Committer x...@freebsd.org | http://people.freebsd.org/~xmj -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQEcBAEBCAAGBQJVXuswAAoJEPyeKTcbGw0LSbQIAJjRMmtKTn1SAYfsHhsp7N5x twizIEZpgttmjaMJr6FuOWt3ItmfXWhxuQaqRZrb0xazzt9Pg1d1DHmmDOXihuXc JaEM603/J/SrsvYz7lJgy9MXC4ErN453aRYupNkEQGtSqk2pQt/l+JvoVdQi+dLp pffmGD4mJFw4B9B0eGrAINrWzNi3so7P3CqRgrIf1B14WBGX2Nreq60MFdS5CrjV A0UONsJrMKPB9oyskfA9RHmtNI4UYUbDeyLl+X9LOz8zYlNI4l6/CfMZcKdUzmzh gQ3NqPERsdFw7s0DLZmx0jv42lYg6f2jEti7JRzgHVD900PGz49vk5XbqcwY2JM= =l5uv -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
Re: xargs -P0 suport
On 05/22/15 13:27, Mateusz Guzik wrote: On Fri, May 22, 2015 at 12:32:52PM -0400, Allan Jude wrote: There is some question about if nargs is a sane value for maxprocs in the negative case. 5000 does seem a bit high, and the behaviour can get wonky depending on the order you specify -P and -n together on the command line. Any suggestions? GNU xargs imposes no limit whatsoever, but it also supports reallocating its process table, while our xargs allocates one upfront and does not change it. I would say reading hard proc resource limit and using that as the limit would do the job just fine. GNU xargs uses MAX_INT for this limit. Our xargs performs much worse with it for a reason I haven't investigated. The 5000 number doesn't seem high and I have workflows that do ' | xargs -n1 -P0 ...' spawning about this many jobs. - Nikolai Lifanov ___ 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: xargs -P0 suport
On Fri, May 22, 2015 at 01:43:21PM -0400, Nikolai Lifanov wrote: On 05/22/15 13:27, Mateusz Guzik wrote: On Fri, May 22, 2015 at 12:32:52PM -0400, Allan Jude wrote: There is some question about if nargs is a sane value for maxprocs in the negative case. 5000 does seem a bit high, and the behaviour can get wonky depending on the order you specify -P and -n together on the command line. Any suggestions? GNU xargs imposes no limit whatsoever, but it also supports reallocating its process table, while our xargs allocates one upfront and does not change it. I would say reading hard proc resource limit and using that as the limit would do the job just fine. GNU xargs uses MAX_INT for this limit. Our xargs performs much worse with it for a reason I haven't investigated. The 5000 number doesn't seem high and I have workflows that do ' | xargs -n1 -P0 ...' spawning about this many jobs. Strictly speaking MAX_INT is indeed the upper limit, but the number is so big it's not a limit in practice and it's not going to be in foreseeable future. As noted earlier our xargs allocates the table upfront, which with MAX_INT limit means several MBs allocated for no good reason. For all practical purposes grabbing hard limit for processes and capping it with pid_max will have the end result of xargs not limiting the amount of processes. -- Mateusz Guzik mjguzik gmail.com ___ 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: xargs -P0 suport
On Fri, May 22, 2015 at 12:32:52PM -0400, Allan Jude wrote: There is some question about if nargs is a sane value for maxprocs in the negative case. 5000 does seem a bit high, and the behaviour can get wonky depending on the order you specify -P and -n together on the command line. Any suggestions? GNU xargs imposes no limit whatsoever, but it also supports reallocating its process table, while our xargs allocates one upfront and does not change it. I would say reading hard proc resource limit and using that as the limit would do the job just fine. -- Mateusz Guzik mjguzik gmail.com ___ 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
