Removal of acorn26 port
Unless someone can give a good reason to keep it, the acorn26 port will be removed in a week or two or three. Along with the removal will be the cleanup of the common arm to remove the arm26 bits associated with it.
netbsd-7 panic
hello, I just got this: panic: kernel diagnostic assertion (m)-m_type != MT_FREE failed: file /dsk/l1/misc/bouyer/netbsd-7/src/sys/kern/uipc_mbuf.c, line 652 cpu0: Begin traceback... vpanic() at netbsd:vpanic+0x13c kern_assert() at netbsd:kern_assert+0x4f m_freem() at netbsd:m_freem+0xa7 ipf_fastroute() at netbsd:ipf_fastroute+0x397 ipf_send_ip() at netbsd:ipf_send_ip+0x13c ipf_send_icmp_err() at netbsd:ipf_send_icmp_err+0x1fa ipf_check() at netbsd:ipf_check+0x88c pfil_run_hooks() at netbsd:pfil_run_hooks+0xc4 ip6_input() at netbsd:ip6_input+0x1bb ip6intr() at netbsd:ip6intr+0x45 softint_dispatch() at netbsd:softint_dispatch+0xd3 This is netbsd-7/amd64 as of early february. Does it ring a bell to someone ? -- Manuel Bouyer bou...@antioche.eu.org NetBSD: 26 ans d'experience feront toujours la difference --
Re: Removal of acorn26 port
On 15 April 2015 at 14:36, Matt Thomas m...@3am-software.com wrote: Unless someone can give a good reason to keep it, the acorn26 port will be removed in a week or two or three. Along with the removal will be the cleanup of the common arm to remove the arm26 bits associated with it. I guess someone might say it is not in line with the process outlined on https://www.netbsd.org/ports/ Justin
Re: Removal of acorn26 port
Unless someone can give a good reason to keep it, the acorn26 port will be removed in a week or two or three. Along with the removal will be the cleanup of the common arm to remove the arm26 bits associated with it. Does the port currently work? If so, maybe it'd be nice to have a 7.0 release before it's removed so it's clear what the last known working release, tag and date are. John
Re: Removal of acorn26 port
On Wed, Apr 15, 2015 at 01:20:33PM -0700, Matt Thomas wrote: On Apr 15, 2015, at 10:28 AM, Justin Cormack jus...@specialbusservice.com wrote: On 15 April 2015 at 14:36, Matt Thomas m...@3am-software.com wrote: Unless someone can give a good reason to keep it, the acorn26 port will be removed in a week or two or three. Along with the removal will be the cleanup of the common arm to remove the arm26 bits associated with it. I guess someone might say it is not in line with the process outlined on https://www.netbsd.org/ports/ acorn26 build but has been suspected of being broken for years. The last post to port-acorn26 was in 2011. It should also be said that noone really cares about pre-ARMv4 in toolchain-land. We are already the odd kid for caring about ARMv4. Joerg
Re: Removal of acorn26 port
On Apr 15, 2015, at 10:28 AM, Justin Cormack jus...@specialbusservice.com wrote: On 15 April 2015 at 14:36, Matt Thomas m...@3am-software.com wrote: Unless someone can give a good reason to keep it, the acorn26 port will be removed in a week or two or three. Along with the removal will be the cleanup of the common arm to remove the arm26 bits associated with it. I guess someone might say it is not in line with the process outlined on https://www.netbsd.org/ports/ acorn26 build but has been suspected of being broken for years. The last post to port-acorn26 was in 2011.
Re: Removal of acorn26 port
In article trinity-40fe500f-df8d-4b60-a4b4-3b73f95b9bfe-1429133530648@3capp-mailcom-bs10, Kamil Rytarowski n...@gmx.com wrote: I strongly agree, please follow the rules and move it to Tier III even now. There are more broken or incomplete ports than acorn26. acorn26 should run on emulators/arcem, it's worth to give it a try. I a proponent of following the rules, but I feel we've been dragging dead bodies and it's having an impact in our available resources. People who use the port should shout if they want the port kept around. christos
Re: Removal of acorn26 port
Justin Cormack jus...@specialbusservice.com wrote: acorn26 build but has been suspected of being broken for years. The last post to port-acorn26 was in 2011. Yes, I am sure it qualifies to move to tier III, and has done for some years. Procedurally, moving it officially to tier III and then removing all support for it from the common code to make it even more broken (it would then be removed from the build matrix), and then deleting it in 6 months might be better than just deleting it now. Back in 2009 when I removed uarea swap-out [1], I managed to find only *one* user of acorn26 - its former maintainer (bjh21). He managed to boot to single-user mode but run out of time trying multi-user. Since then nobody managed to show acorn26 being usable without uarea swapout. There is really no point to keep it dusting. [1] https://mail-index.netbsd.org/source-changes/2009/10/21/msg002198.html -- Mindaugas
Re: Removal of acorn26 port
Sent: Wednesday, April 15, 2015 at 9:25 PM From: Justin Cormack jus...@specialbusservice.com To: Matt Thomas m...@3am-software.com Cc: port-arm port-...@netbsd.org, current-users current-users@netbsd.org, port-acor...@netbsd.org Subject: Re: Removal of acorn26 port On 15 April 2015 at 21:20, Matt Thomas m...@3am-software.com wrote: On Apr 15, 2015, at 10:28 AM, Justin Cormack jus...@specialbusservice.com wrote: On 15 April 2015 at 14:36, Matt Thomas m...@3am-software.com wrote: Unless someone can give a good reason to keep it, the acorn26 port will be removed in a week or two or three. Along with the removal will be the cleanup of the common arm to remove the arm26 bits associated with it. I guess someone might say it is not in line with the process outlined on https://www.netbsd.org/ports/ acorn26 build but has been suspected of being broken for years. The last post to port-acorn26 was in 2011. Yes, I am sure it qualifies to move to tier III, and has done for some years. Procedurally, moving it officially to tier III and then removing all support for it from the common code to make it even more broken (it would then be removed from the build matrix), and then deleting it in 6 months might be better than just deleting it now. I strongly agree, please follow the rules and move it to Tier III even now. There are more broken or incomplete ports than acorn26. acorn26 should run on emulators/arcem, it's worth to give it a try. Justin
Kernel panic when entering ACPI sleep state S3
Hi all, I'm running the latest snapshot from nyftp.netbsd.org (201504151050Z) on a Thinkpad X120e. I seem to be encountering some issues when attempting to enter ACPI sleep state S3, using: sysctl -w hw.acpi.sleep.state=3 Upon invoking the above command, my system seems to attempt to sleep (blanks the screen, the speakers click) but then halts and reboots. Figured I'd report this, and would appreciate any input. Please see the relevant output from /var/log/messages, and a dmesg following this. /var/log/messages: -- Apr 15 19:47:40 bmo /netbsd: acpi0: entering state S3 Apr 15 19:48:29 bmo syslogd[684]: restart Apr 15 19:48:29 bmo /netbsd: panic: kernel diagnostic assertion (bo-mem.bus.base (PAGE_SIZE - 1)) == 0 failed: file /home/source/ab/HEAD/src/sys/external/bsd/drm2/dist/drm/ttm/ttm_bo.c, line 1618 bo bus base addr not page-aligned: fe82125c69b0 Apr 15 19:48:29 bmo /netbsd: cpu0: Begin traceback... Apr 15 19:48:29 bmo /netbsd: vpanic() at netbsd:vpanic+0x13c Apr 15 19:48:29 bmo /netbsd: kern_assert() at netbsd:kern_assert+0x4f Apr 15 19:48:29 bmo /netbsd: ttm_bo_unmap_virtual_locked() at netbsd:ttm_bo_unmap_virtual_locked+0x17b Apr 15 19:48:29 bmo /netbsd: ttm_bo_handle_move_mem() at netbsd:ttm_bo_handle_move_mem+0x22f Apr 15 19:48:29 bmo /netbsd: ttm_mem_evict_first() at netbsd:ttm_mem_evict_first+0x4e0 Apr 15 19:48:29 bmo /netbsd: ttm_bo_force_list_clean() at netbsd:ttm_bo_force_list_clean+0x5a Apr 15 19:48:29 bmo /netbsd: radeon_suspend_kms() at netbsd:radeon_suspend_kms+0x13f Apr 15 19:48:29 bmo /netbsd: radeon_do_suspend() at netbsd:radeon_do_suspend+0x21 Apr 15 19:48:29 bmo /netbsd: device_pmf_driver_suspend() at netbsd:device_pmf_driver_suspend+0x35 Apr 15 19:48:29 bmo /netbsd: pmf_device_suspend_locked() at netbsd:pmf_device_suspend_locked+0xe3 Apr 15 19:48:29 bmo /netbsd: pmf_device_suspend() at netbsd:pmf_device_suspend+0x41 Apr 15 19:48:29 bmo /netbsd: pmf_system_suspend() at netbsd:pmf_system_suspend+0xc1 Apr 15 19:48:29 bmo /netbsd: acpi_enter_sleep_state() at netbsd:acpi_enter_sleep_state+0x115 Apr 15 19:48:29 bmo /netbsd: sysctl_hw_acpi_sleepstate() at netbsd:sysctl_hw_acpi_sleepstate+0xfe Apr 15 19:48:29 bmo /netbsd: sysctl_dispatch() at netbsd:sysctl_dispatch+0xc4 Apr 15 19:48:29 bmo /netbsd: sys___sysctl() at netbsd:sys___sysctl+0xd0 Apr 15 19:48:29 bmo /netbsd: syscall() at netbsd:syscall+0x9c Apr 15 19:48:29 bmo /netbsd: --- syscall (number 202) --- Apr 15 19:48:29 bmo /netbsd: 7f7ff7501d3a: Apr 15 19:48:29 bmo /netbsd: cpu0: End traceback... Apr 15 19:48:29 bmo /netbsd: Apr 15 19:48:29 bmo /netbsd: dumping to dev 0,1 (offset=3496, size=1992749): Apr 15 19:48:29 bmo /netbsd: dump Skipping crash dump on recursive panic Apr 15 19:48:29 bmo /netbsd: panic: wddump: polled command has been queued Apr 15 19:48:29 bmo /netbsd: cpu0: Begin traceback... Apr 15 19:48:29 bmo /netbsd: vpanic() at netbsd:vpanic+0x13c Apr 15 19:48:29 bmo /netbsd: snprintf() at netbsd:snprintf Apr 15 19:48:29 bmo /netbsd: wddump() at netbsd:wddump+0x282 Apr 15 19:48:29 bmo /netbsd: dump_header_flush() at netbsd:dump_header_flush+0x4f Apr 15 19:48:29 bmo /netbsd: dump_header_addbytes() at netbsd:dump_header_addbytes+0x46 Apr 15 19:48:29 bmo /netbsd: dump_header_addseg() at netbsd:dump_header_addseg+0x1e Apr 15 19:48:29 bmo /netbsd: dump_seg_iter() at netbsd:dump_seg_iter+0xce Apr 15 19:48:29 bmo /netbsd: cpu_dump() at netbsd:cpu_dump+0x6a Apr 15 19:48:29 bmo /netbsd: dodumpsys() at netbsd:dodumpsys+0xfb Apr 15 19:48:29 bmo /netbsd: dumpsys() at netbsd:dumpsys+0x1d Apr 15 19:48:29 bmo /netbsd: vpanic() at netbsd:vpanic+0x145 Apr 15 19:48:29 bmo /netbsd: kern_assert() at netbsd:kern_assert+0x4f Apr 15 19:48:29 bmo /netbsd: ttm_bo_unmap_virtual_locked() at netbsd:ttm_bo_unmap_virtual_locked+0x17b Apr 15 19:48:29 bmo /netbsd: ttm_bo_handle_move_mem() at netbsd:ttm_bo_handle_move_mem+0x22f Apr 15 19:48:29 bmo /netbsd: ttm_mem_evict_first() at netbsd:ttm_mem_evict_first+0x4e0 Apr 15 19:48:29 bmo /netbsd: ttm_bo_force_list_clean() at netbsd:ttm_bo_force_list_clean+0x5a Apr 15 19:48:29 bmo /netbsd: radeon_suspend_kms() at netbsd:radeon_suspend_kms+0x13f Apr 15 19:48:29 bmo /netbsd: radeon_do_suspend() at netbsd:radeon_do_suspend+0x21 Apr 15 19:48:29 bmo /netbsd: device_pmf_driver_suspend() at netbsd:device_pmf_driver_suspend+0x35 Apr 15 19:48:29 bmo /netbsd: pmf_device_suspend_locked() at netbsd:pmf_device_suspend_locked+0xe3 Apr 15 19:48:29 bmo /netbsd: pmf_device_suspend() at netbsd:pmf_device_suspend+0x41 Apr 15 19:48:29 bmo /netbsd: pmf_system_suspend() at netbsd:pmf_system_suspend+0xc1 Apr 15 19:48:29 bmo /netbsd: acpi_enter_sleep_state() at netbsd:acpi_enter_sleep_state+0x115 Apr 15 19:48:29 bmo /netbsd: sysctl_hw_acpi_sleepstate() at netbsd:sysctl_hw_acpi_sleepstate+0xfe Apr 15 19:48:29 bmo /netbsd: sysctl_dispatch() at netbsd:sysctl_dispatch+0xc4 Apr 15 19:48:29 bmo /netbsd: sys___sysctl() at netbsd:sys___sysctl+0xd0 Apr 15 19:48:29 bmo /netbsd: syscall() at
urtwn hostap
According to the man page, the urtwn driver is supposed to support the hostap option. Although perhaps I am not sure how to configure it with ifconfig, I cannot get it to work. Has anyone had success with this? Is it known not to work? Does anyone have a configuration, e.g., ifconfg.urtwnX, that is known to work? Thanks for your help. Cheers, Brook
Re: Removal of acorn26 port
On 15 April 2015 at 21:20, Matt Thomas m...@3am-software.com wrote: On Apr 15, 2015, at 10:28 AM, Justin Cormack jus...@specialbusservice.com wrote: On 15 April 2015 at 14:36, Matt Thomas m...@3am-software.com wrote: Unless someone can give a good reason to keep it, the acorn26 port will be removed in a week or two or three. Along with the removal will be the cleanup of the common arm to remove the arm26 bits associated with it. I guess someone might say it is not in line with the process outlined on https://www.netbsd.org/ports/ acorn26 build but has been suspected of being broken for years. The last post to port-acorn26 was in 2011. Yes, I am sure it qualifies to move to tier III, and has done for some years. Procedurally, moving it officially to tier III and then removing all support for it from the common code to make it even more broken (it would then be removed from the build matrix), and then deleting it in 6 months might be better than just deleting it now. Justin
Updating SQLite to 3.8.9
Hi there, a new version of SQLite is now available, 3.8.9: http://sqlite.org/releaselog/3_8_9.html Upgrading is recommended (http://sqlite.org/). Reading this blog post from lcamtuf, it does seems quite important to update indeed: http://lcamtuf.blogspot.de/2015/04/finding-bugs-in-sqlite-easy-way.html He found a number of crashes, some potentially security-critical (depending on the way the software is used). Even though there was no security advisory published to date, the new release fixes every issue found. HTH, -- khorben
