Re: Lenovo 110s Laptop - bug or unsupported hardware?
Hi, I have exactly the same behaviour in a Lenovo Ideapad IBR 110S here using i3 or Lumina using *any* browser after a couple of minutes, so it is not faulty hw of the poster. The behaviour was not present with 6.1. On 28 October 2017 at 04:33, J Vans <3...@startmail.com> wrote: > I decided to post this in misc because I am not sure if this a bug or > unsupported hardware. It is a Lenovo 110s laptop. > > Apm works on this machine. Suspend and resume work on this machine. > > When running X, and doing things that require a lot of memory (open > firefox and watch a youtube video + 3 or 4 more tabs + open evince and open > a sizeable PDF was my test) this machine freezes, and the screen goes > black. Sometimes this happens in 30 seconds, sometimes it takes 10 minutes > or more. I also tested with Chrome and Midori, and got the same behavior. I > also tested playing video locally and the results were the same. On a few > occasions it crashed while not doing much, but for the most part if I keep > memory usage low (i.e. use a text based browser, for example) it does not > crash. DDB is opening in the background after the crash, but I cannot see > it. I type ps, and trace, but they do not show up in the messages after > rebooting. I have however been able to get several core dumps. They look > identical to eachother, which leads me to believe it is the same problem > happening in each crash. > > The above behavior is consistant across i3, Fvwm, and Cwm, with apmd > enabled or no, across all flag settings of apm, and machdep.aperture=0, 1, > and 2. > > Serial console is not an option on this machine but I have quite a > collection of core dumps. Any advice on trouble shooting this further (or > if it's unsupported hardware) would be appreciated. > > The below info was generated using a kernel built from GENERIC's config + > makeoptions DEBUG="-g", built from the CURRENT tree on 10/26. > > GNU gdb 6.3 > Copyright 2004 Free Software Foundation, Inc. > GDB is free software, covered by the GNU General Public License, and you > are > welcome to change it and/or distribute copies of it under certain > conditions. > Type "show copying" to see the conditions. > There is absolutely no warranty for GDB. Type "show warranty" for details. > This GDB was configured as "amd64-unknown-openbsd6.2". > (gdb) file bsd.8 > Reading symbols from /home/utilis/CRASH/102717/607pm/bsd.8...done. > (gdb) target kvm bsd.8.core > #0 0x8167c544 in dumpsys () at /usr/src/sys/arch/amd64/amd64/ > machdep.c:949 > 949 error = (*dump)(dumpdev, blkno, va, n); > Current language: auto; currently minimal > (gdb) where > #0 0x8167c544 in dumpsys () at /usr/src/sys/arch/amd64/amd64/ > machdep.c:949 > #1 0x8167bfea in boot (howto=0) > at /usr/src/sys/arch/amd64/amd64/machdep.c:743 > #2 0x813cccf5 in reboot (howto=Variable "howto" is not available. > ) at /usr/src/sys/kern/kern_xxx.c:70 > #3 0x81009f7e in db_boot_crash_cmd (addr=Variable "addr" is not > available. > ) > at /usr/src/sys/ddb/db_command.c:790 > #4 0x8100986d in db_command (last_cmdp=0x0, cmd_table=Variable > "cmd_table" is not available. > ) > at /usr/src/sys/ddb/db_command.c:303 > #5 0x8100a331 in db_command_loop () at > /usr/src/sys/ddb/db_command.c:703 > #6 0x816694d4 in db_trap (type=Variable "type" is not available. > ) at /usr/src/sys/ddb/db_trap.c:93 > #7 0x812a75ca in db_ktrap (type=0, code=0, regs=0x0) > at /usr/src/sys/arch/amd64/amd64/db_interface.c:152 > #8 0x811c150c in trap (frame=0x0) > at /usr/src/sys/arch/amd64/amd64/trap.c:188 > #9 0x81618a25 in calltrap () > #10 0x81405af0 in pmap_flush_cache (addr=18446603336235712512, > len=Variable "len" is not available. > ) > at /usr/src/sys/arch/amd64/amd64/pmap.c:1288 > #11 0x815b1a2b in gen8_ppgtt_clear_pte_range > (vm=0x80994000, > pdp=0x809941a0, start=Variable "start" is not available. > ) > at /usr/src/sys/dev/pci/drm/i915/i915_gem_gtt.c:394 > #12 0x81068ae8 in __i915_vma_unbind (vma=0x156, wait=Variable > "wait" is not available. > ) > at /usr/src/sys/dev/pci/drm/i915/i915_gem.c:3784 > #13 0x8106aa3e in i915_gem_free_object (gem_obj=0x80dd16d0) > at /usr/src/sys/dev/pci/drm/i915/i915_gem.c:3817 > #14 0x81332741 in drm_gem_object_handle_unreference_unlocked > (obj=0x156) > at /usr/src/sys/dev/pci/drm/drm_gem.c:900 > #15 0x81332626 in drm_gem_handle_delete (filp=0x1a7ec083, handle=3) > at /usr/src/sys/dev/pci/drm/drm_gem.c:424 > #16 0x8169da2c in drm_do_ioctl (dev=0x3, minor=Variable "minor" is > not available. > ) > at /usr/src/sys/dev/pci/drm/drm_drv.c:859 > #17 0x8169db2f in drmioctl (kdev=Variable "kdev" is not available. > ) > at /usr/src/sys/dev/pci/drm/drm_drv.c:886 > #18 0x8172fc5e in VOP_IOCTL (vp=Variable "vp" is not available. > ) at /usr/s
Re: Lenovo 110s Laptop - bug or unsupported hardware?
On 10/27/17 23:33, J Vans wrote: > I decided to post this in misc because I am not sure if this a bug or > unsupported hardware. It is a Lenovo 110s laptop. > > Apm works on this machine. Suspend and resume work on this machine. > > When running X, and doing things that require a lot of memory (open > firefox and watch a youtube video + 3 or 4 more tabs + open evince > and open a sizeable PDF was my test) this machine freezes, and the > screen goes black. Sometimes this happens in 30 seconds, sometimes it > takes 10 minutes or more. I also tested with Chrome and Midori, and > got the same behavior. I also tested playing video locally and the > results were the same. On a few occasions it crashed while not doing > much, but for the most part if I keep memory usage low (i.e. use a > text based browser, for example) it does not crash. DDB is opening in > the background after the crash, but I cannot see it. I type ps, and > trace, but they do not show up in the messages after rebooting. I > have however been able to get several core dumps. They look identical > to eachother, which leads me to believe it is the same problem > happening in each crash. > > The above behavior is consistant across i3, Fvwm, and Cwm, with apmd > enabled or no, across all flag settings of apm, and > machdep.aperture=0, 1, and 2. > > Serial console is not an option on this machine but I have quite a > collection of core dumps. Any advice on trouble shooting this further > (or if it's unsupported hardware) would be appreciated. ... > $dmesg > OpenBSD 6.2-current (DEBUG) #2: Thu Oct 26 18:46:09 CDT 2017 > myu...@groo.my.domain:/usr/src/sys/arch/amd64/compile/DEBUG > real mem = 1970376704 (1879MB) > avail mem = 1900142592 (1812MB) chrome, firefox, and other bloatware on 2G RAM? In my experience with 4G RAM, it's just not enough. Are you sure you have entered the Swap Hell Zone? Nick.
Atmel and Elantech Touchpads
The hardware drivers for Atmel touchpads (iatp) and the older Elantech models (pms, for versions 1-3) have been updated in -current. If anybody is using a laptop with one of those models, tests with the next snapshots would be welcome, ideally with both synaptics(4) and the wsmouse-internal input driver, see https://marc.info/?l=openbsd-misc&m=150153498920367&w=2 Whatever you observe, please don't hesitate to inform me, be it on misc@, bugs@, or off-list.
typo in FAQ
I noticed that the example command for ‘ifconfig’ at https://www.openbsd.org/faq/faq6.html#Wireless contains a typo. $ ifconfig ath0 media should read $ ifconfig athn0 media
Re: typo in FAQ
Sorry, this is actually NOT a typo, I was misreading the section. As it tends to be, I realized my mistake immediately after sending the email. > On Oct 28, 2017, at 1:05 PM, Nathan Dietzenbach > wrote: > > I noticed that the example command for ‘ifconfig’ at > https://www.openbsd.org/faq/faq6.html#Wireless contains a typo. > > $ ifconfig ath0 media > > should read > > $ ifconfig athn0 media
MATE Desktop Environment 1.18.0
Hi, I'm currently using MATE Desktop with OpenBSD / amd64 6.2 -stable on a Lenovo ThinkPad T430. I want to report some errors encountered during its use. Have you ever encountered these errors and possibly found a solution? gnome-keyring-daemon[31733]: couldn't access control socket: /var/run/user/1000/keyring/control: No such file or directory gnome-keyring-daemon[31733]: The PKCS#11 component was already initialized gnome-keyring-daemon[31733]: The Secret Service was already initialized console-kit-daemon[49025]: WARNING: Error waiting for native console 1 activation: Permission denied console-kit-daemon[49025]: WARNING: Error waiting for native console 2 activation: Permission denied console-kit-daemon[49025]: WARNING: Error waiting for native console 3 activation: Permission denied console-kit-daemon[49025]: WARNING: Error waiting for native console 4 activation: Permission denied mate-session[53962]: WARNING: Unable to find provider '' of required component 'dock' ** (mate-settings-daemon:59867): WARNING **: Error opening directory /etc/xrdb: No such file or directory [system] Activating service name='org.mate.SettingsDaemon.DateTimeMechanism' (using servicehelper) [system] Activated service 'org.mate.SettingsDaemon.DateTimeMechanism' failed: Launch helper exited with unknown return code 1 pulseaudio[87536]: [(null)] authkey.c: Failed to open cookie file '/home/loginname/.config/pulse/cookie': No such file or directory pulseaudio[87536]: [(null)] authkey.c: Failed to load authentication key '/home/loginname/.config/pulse/cookie': No such file or directory pulseaudio[87536]: [(null)] authkey.c: Failed to open cookie file /home/loginname/.pulse-cookie': No such file or directory pulseaudio[87356]: [(null)] authkey.c: Failed to load authentication key '/home/loginname/.pulse-cookie': No such or directory pulseaudio[87536]: [(null)] core-util.c: Failed to create secure directory (/var/run/user/1000/pulse): No such file or directory DEBUG (42951): glibtop_open_p () LibGTop-Server(c=42951): [ERROR] kvm_open: Operation not permitted glibtop(c=57092/s=42951): [ERROR] read 8 bytes: Resource temporarily unavailable (marco:5367): Gdk-ERROR **: The program 'marco' received an X Window System error. This probably reflets a bug in the program. The error was 'BadRegion (invalid Region parameter)'. (Details: serial 116413 error_code 140 request_code 138 (XFIXES) minor_code 10) Thank you for your help. - Olivier Regnier
Re: MATE Desktop Environment 1.18.0
A little off topic.. but.. I haven't tried MATE, but I have the same laptop (T430) and can report that XFCE works very well without major issue ..although I did find that some problems with over-heating and constant fan use resulting in faster battery drain. Gnome3 didn't perform well on my T430 - had to remove it after just a couple of hours. The performance difference between Gnome3 on OpenBSD and Gnome3 on Debian is like night and day. Anyway, just thought I'd share some stuff I've noticed with having the same machine. > Original Message > Subject: MATE Desktop Environment 1.18.0 > Local Time: October 28, 2017 9:33 PM > UTC Time: October 28, 2017 8:33 PM > From: oregn...@riseup.net > To: misc@openbsd.org > > Hi, > > I'm currently using MATE Desktop with OpenBSD / amd64 6.2 -stable on a > Lenovo ThinkPad T430. > I want to report some errors encountered during its use. > Have you ever encountered these errors and possibly found a solution? > > gnome-keyring-daemon[31733]: couldn't access control socket: > /var/run/user/1000/keyring/control: No such file or directory > gnome-keyring-daemon[31733]: The PKCS#11 component was already initialized > gnome-keyring-daemon[31733]: The Secret Service was already initialized > > console-kit-daemon[49025]: WARNING: Error waiting for native console 1 > activation: Permission denied > console-kit-daemon[49025]: WARNING: Error waiting for native console 2 > activation: Permission denied > console-kit-daemon[49025]: WARNING: Error waiting for native console 3 > activation: Permission denied > console-kit-daemon[49025]: WARNING: Error waiting for native console 4 > activation: Permission denied > > mate-session[53962]: WARNING: Unable to find provider '' of required > component 'dock' > > ** (mate-settings-daemon:59867): WARNING **: Error opening directory > /etc/xrdb: No such file or directory > > [system] Activating service > name='org.mate.SettingsDaemon.DateTimeMechanism' (using servicehelper) > [system] Activated service 'org.mate.SettingsDaemon.DateTimeMechanism' > failed: Launch helper exited with unknown return code 1 > > pulseaudio[87536]: [(null)] authkey.c: Failed to open cookie file > '/home/loginname/.config/pulse/cookie': No such file or directory > pulseaudio[87536]: [(null)] authkey.c: Failed to load authentication key > '/home/loginname/.config/pulse/cookie': No such file or directory > pulseaudio[87536]: [(null)] authkey.c: Failed to open cookie file > /home/loginname/.pulse-cookie': No such file or directory > pulseaudio[87356]: [(null)] authkey.c: Failed to load authentication key > '/home/loginname/.pulse-cookie': No such or directory > > pulseaudio[87536]: [(null)] core-util.c: Failed to create secure directory > (/var/run/user/1000/pulse): No such file or directory > > DEBUG (42951): glibtop_open_p () > LibGTop-Server(c=42951): [ERROR] kvm_open: Operation not permitted > glibtop(c=57092/s=42951): [ERROR] read 8 bytes: Resource temporarily > unavailable > > (marco:5367): Gdk-ERROR **: The program 'marco' received an X Window > System error. > This probably reflets a bug in the program. > The error was 'BadRegion (invalid Region parameter)'. > (Details: serial 116413 error_code 140 request_code 138 (XFIXES) > minor_code 10) > > Thank you for your help. > > - Olivier Regnier
MATE Desktop without pulseaudio
Hi, Is it possible through the ports tree to install MATE without pulseaudio? - Olivier
Fail2ban alternative for OpenBSD
Hi, Coming from the Linux world, I wonder if there is a better alternative to fail2ban, already being used in OpenBSD servers by the majority. cheers. x9p
Re: Fail2ban alternative for OpenBSD
On 2017-10-28 21:20, x9p wrote: Hi, Coming from the Linux world, I wonder if there is a better alternative to fail2ban, already being used in OpenBSD servers by the majority. cheers. x9p The pf firewall provides the capability to block brute force attacks. See max-src-conn-rate. https://www.openbsd.org/faq/pf/filter.html#stateopts
Re: Fail2ban alternative for OpenBSD
Note that PF cannot discriminate between legitimate and abusive multiple connections from same cidr. If you whitelist the cidr of a mobile network, to avoid banning yourself on port 993, you also whitelist bruteforce attacks from the same cidr. Sent from ProtonMail Mobile On Sun, Oct 29, 2017 at 5:26 AM, Tom Rosso wrote: > On 2017-10-28 21:20, x9p wrote: > Hi, > > Coming from the Linux world, I > wonder if there is a better alternative > to fail2ban, already being used in > OpenBSD servers by the majority. > > cheers. > > x9p The pf firewall provides > the capability to block brute force attacks. See max-src-conn-rate. > https://www.openbsd.org/faq/pf/filter.html#stateopts
