Re: Cannot understand iked
On 05/03/2016 10:23 PM, kasak wrote: Hello everybody. I hope somebody can help me with iked. I have 2 gates, both can ping each other. One has this iked.conf: ikev2 from 212.233.112.10 to 192.168.1.0/24 \ from 192.168.2.0/23 to 192.168.1.0/24 \ local 212.233.112.10 srcid 212.233.112.10 Another has: ikev2 active \ from 77.220.137.168 to 192.168.2.0/23 \ from 192.168.1.0/24 to 192.168.2.0/23 \ peer 212.233.112.10 srcid 77.220.137.168 And the problem is: local lan clients can reach remote lan, but local gate itself cannot reach. Look: $ ping -c 2 -I 192.168.2.10 192.168.1.240 PING 192.168.1.240 (192.168.1.240): 56 data bytes 64 bytes from 192.168.1.240: icmp_seq=0 ttl=63 time=2.987 ms 64 bytes from 192.168.1.240: icmp_seq=1 ttl=63 time=2.243 ms --- 192.168.1.240 ping statistics --- 2 packets transmitted, 2 packets received, 0.0% packet loss but $ ping -c 2 192.168.1.240 PING 192.168.1.240 (192.168.1.240): 56 data bytes --- 192.168.1.240 ping statistics --- 2 packets transmitted, 0 packets received, 100.0% packet loss Please check with tcpdump on the enc0 interface what kind of traffic is sent when doing the ping. # tcpdump -nvi enc0 icmp Both ping commands sent from same gate. Here is ipsecctl -sa from one of gates: FLOWS: flow esp in from 192.168.1.0/24 to 212.233.112.10 peer 77.220.137.168 srcid IPV4/212.233.112.10 dstid IPV4/77.220.137.168 type use flow esp out from 212.233.112.10 to 192.168.1.0/24 peer 77.220.137.168 srcid IPV4/212.233.112.10 dstid IPV4/77.220.137.168 type require flow esp in from 192.168.1.0/24 to 192.168.2.0/23 peer 77.220.137.168 srcid IPV4/212.233.112.10 dstid IPV4/77.220.137.168 type use flow esp out from 192.168.2.0/23 to 192.168.1.0/24 peer 77.220.137.168 srcid IPV4/212.233.112.10 dstid IPV4/77.220.137.168 type require flow esp out from ::/0 to ::/0 type deny SAD: esp tunnel from 212.233.112.10 to 77.220.137.168 spi 0x22dd1b34 auth hmac-sha2-256 enc aes-256 esp tunnel from 77.220.137.168 to 212.233.112.10 spi 0xd1abf711 auth hmac-sha2-256 enc aes-256 I have the same issue on my boxes that has to contact remote networks. I've solved this by translating my outgoing traffic from my gateway over ipsec to the remote network to a internal interface. See example below. /etc/pf.conf: ... match out log on enc0 from (egress) to 10.10.0.0/24 nat-to (em2) # where em2 is my LAN interface ...
Re: Will mmap and the read buffer cache be unified, anyone working with it?
On 2016/05/04 01:20, Tinker wrote: > A separate question about combining mmap access and file > IO in the current absence of a unified buffer cache: > > If I have a readonly mmap and do fwrite to it, could I use > fsync (or msync or any other call) right after the fwrite, as a tool to > guarantee that the memory mapping interface is up to date? It needs more than fsync. Playing around with the simple test program from https://lists.samba.org/archive/samba-technical/2001-May/013552.html (at least on amd64) it appears that msync (with either MS_SYNC, MS_ASYNC or MS_INVALIDATE) is needed after changes are made on the mmap side of things, and msync with MS_INVALIDATE is needed after changes done on the file io side of things. > Also between the fwrite and that call, the possible data inconsistency would > be limited to the particular bytes written right? I don't know.
Re: Openbsd broke my hard drive twice! Getting frustrated
Hi Gabe, I found it possible to boot and install 5.9 on an XPS 13" (9333)[0], but had problems getting the all important suspend to RAM (or anything which allowed me to close the lid and reopen to resume work) to work. Were you successful in getting this necessary laptop functionality working correctly? If so, would you mind sharing your configs? I'd love to reinstall OpenBSD on this machine, but can't sacrifice that. Cheers, Andrew [0]: To be fair, I suffered the same problems you did, where I thought the drive was dead. But, in reality, I just had to repartition it with EFI in mind from a thumb drive booted Linux installer, and try again. On Tue, May 3, 2016 at 8:30 PM, Gabriel Guzman wrote: > On 12/29, Gabriel Guzman wrote: > > I've been seeing a similar issue on a DELL XPS 13" Developer edition I > got > > back in June -- ran fine with ubuntu as shipped with Dell, and then I > > wiped and installed OpenBSD and now can't even access the BIOS. > > I figured out the issue. On my machine (DEL XPS 13) it was the "Intel > Rapid Boot" option in BIOS. Disabling that resolved all my boot issues. > I can now boot with MBR or GPT off the internal SSD. And, I can also > access the BIOS with the internal SSD installed in the system (this was > not possible before) > > gabe. > > -- http://apgwoz.com
Can't change rtadvd route preference for the default route
Hi, I want to change route preference for the default route in RA messages which are sent to clients. On 5.9 GENERIC.MP#1888 amd64 I do have rtadvd and changing rtflags in rtadvd.conf doesn't changes Default router Preference (it sends default value, where I define "l" = Low). In config I have just two items set: vlan6:\ :raflags#64:\ :rtflags="l": raflags#64 (Other stateful configuration flag bit) rtflags="l" (Low route preference for the route) I'm always getting pref=medium for default router preference. $ ndp -rn fe80:::::5e0c%vlan0 if=vlan0, flags=O, pref=medium, expire=29m52s However It works perfect for non-default route preference for the route, but not default e.g.: vlan6:\ :raflags#64:rtflags="l":rtprefix="2001:1:1:1::":rtplen#64: It will be great if someone can share working config options which allows to change DRFAULT router preference RA message value. -- With regards, Eugene Sudyr
Re: Xeon-D 10GE nics
On 12.4.2016. 15:15, Stuart Henderson wrote: > Does anyone know if the 10GE NICs on Xeon-D SoCs work on OpenBSD yet? > e.g. "Dual 10G SFP+ from D-1500 SoC" on Supermicro SYS-5018D-FN8T. > Hi, dmesg for https://www.supermicro.nl/products/motherboard/Xeon/D/X10SDV-TP8F.cfm OpenBSD 5.9-current (GENERIC.MP) #2003: Tue May 3 13:58:33 MDT 2016 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 17054797824 (16264MB) avail mem = 16533319680 (15767MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xed9b0 (54 entries) bios0: vendor American Megatrends Inc. version "T20160314212014" date 03/14/2016 bios0: Supermicro Super Server acpi0 at bios0: rev 2 acpi0: sleep states S0 S4 S5 acpi0: tables DSDT FACP APIC FPDT FIDT SPMI MCFG UEFI DBG2 HPET WDDT SSDT SSDT SSDT PRAD DMAR HEST BERT ERST EINJ acpi0: wakeup devices IP2P(S4) XHCI(S4) EHC1(S4) EHC2(S4) RP07(S4) RP08(S4) BR1A(S4) BR1B(S4) BR2A(S4) BR2B(S4) BR2C(S4) BR2D(S4) BR3A(S4) BR3B(S4) BR3C(S4) BR3D(S4) [...] acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Xeon(R) CPU D-1518 @ 2.20GHz, 2200.28 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,PQM,RDSEED,ADX,SMAP,PT,SENSOR,ARAT cpu0: 256KB 64b/line 8-way L2 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges cpu0: apic clock running at 99MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.2, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Xeon(R) CPU D-1518 @ 2.20GHz, 2200.00 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,PQM,RDSEED,ADX,SMAP,PT,SENSOR,ARAT cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 4 (application processor) cpu2: Intel(R) Xeon(R) CPU D-1518 @ 2.20GHz, 2200.00 MHz cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,PQM,RDSEED,ADX,SMAP,PT,SENSOR,ARAT cpu2: 256KB 64b/line 8-way L2 cache cpu2: smt 0, core 2, package 0 cpu3 at mainbus0: apid 6 (application processor) cpu3: Intel(R) Xeon(R) CPU D-1518 @ 2.20GHz, 2200.00 MHz cpu3: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,PQM,RDSEED,ADX,SMAP,PT,SENSOR,ARAT cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 0, core 3, package 0 cpu4 at mainbus0: apid 1 (application processor) cpu4: Intel(R) Xeon(R) CPU D-1518 @ 2.20GHz, 2200.00 MHz cpu4: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,PQM,RDSEED,ADX,SMAP,PT,SENSOR,ARAT cpu4: 256KB 64b/line 8-way L2 cache cpu4: smt 1, core 0, package 0 cpu5 at mainbus0: apid 3 (application processor) cpu5: Intel(R) Xeon(R) CPU D-1518 @ 2.20GHz, 2200.00 MHz cpu5: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,PQM,RDSEED,ADX,SMAP,PT,SENSOR,ARAT cpu5: 256KB 64b/line 8-way L2 cache cpu5: smt 1, core 1, package 0 cpu6 at mainbus0: apid 5 (application processor) cpu6: Intel(R) Xeon(R) CPU D-1518 @ 2.20GHz, 2200.00 MHz cpu6: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLM
Re: Short maximum interpreter length
On May 4, 2016 03:56, "Donald Allen" > So we can run /usr/bin/5CBC4234CA9D027019381215FAFB31E6482D4B252A36E1EBD5FCFAD12F9E10B85C4C2C917E3DBE6C765CED9719F4F449C47AC9263513458BBEA76B617339B75A > scripts. > This /has/ something to do with docker, right?
Re: FW: Re: watchdog suport for new hardware
This was added to GENERIC:
sel* at acpi?
and these four lines were added to files.acpi:
# SEL embedded controller
device sel
attach sel at acpi with sel_acpi
file dev/acpi/sel_acpi.c sel_acpi
With SEL0002 being the first item in the array, shouldn't it at least
match it if it exists? We will add NULL to the HID array and see what
happens.
On Tue, May 3, 2016 at 5:29 PM, Mike Larkin wrote:
> On Tue, May 03, 2016 at 03:32:34PM -0500, Chase Davis wrote:
>> Mike,
>>
>> We took your suggestion and re-wrote the driver to model sdhc_acpi. I
>> have attached the new code. However, the match function never returns
>> a 1. We put temporary print statements in the match routine. It is
>> being called several times during the kernel boot process, but it
>> never finds a device with HID SEL0002. Do you have any suggestions for
>> why it would show up in the DSDT tables when we do an acpidump, but
>> that the match routine never finds it?
>>
>> This is a snippet from the dmesg boot log
>>
>> Attempting to match SEL: result (0)
>> acpitimer0 at acpi0: 3579545 Hz, 24 bits
>> Attempting to match SEL: result (0)
>> Attempting to match SEL: result (0)
>> Attempting to match SEL: result (0)
>> Attempting to match SEL: result (0)
>> acpihpet0 at acpi0: 14318179 Hz
>> Attempting to match SEL: result (0)
>> acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
>>
>> int
>> sel_acpi_match(struct device *parent, void *match, void *aux)
>> {
>> struct acpi_attach_args *aaa = aux;
>> struct cfdata *cf = match;
>> printf("Attempting to match SEL: ");
>> int res = acpi_matchhids(aaa, sel_hids, cf->cf_driver->cd_name);
>> printf("result (%d)\n", res);
>> return res;
>> }
>>
>> Thanks,
>> Chase
>
> I think this diff is missing some parts. Like GENERIC?
>
> Also, you need a NULL after your last HID or matchhids will walk all
> through memory until it hits a NULL.
>
> -ml
>
>> /*$OpenBSD: sel.c,v 1.0 2016/04/01 05:00:00 jsg Exp $ */
>> /*
>> * Copyright (c) 2016 PREMIER System Integrators
>> *
>> * Permission to use, copy, modify, and distribute this software for any
>> * purpose with or without fee is hereby granted, provided that the above
>> * copyright notice and this permission notice appear in all copies.
>> *
>> * THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES
>> * WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
>> * MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR
>> * ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
>> * WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
>> * ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
>> * OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
>> *
>> * Schweitzer Engineering Laboratories: SEL-3355 Embedded controller
>> */
>>
>> #include
>> #include
>> #include
>> #include
>> #include
>> #include
>>
>> #include
>>
>> #include
>> #include
>> #include
>> #include
>> #include
>>
>> #include
>>
>> struct sel_host;
>>
>> struct sel_softc {
>> /* sc_dev must be the first item in the struct */
>> struct device sc_dev;
>> struct sel_host **sc_host;
>> };
>>
>> struct sel_acpi_softc {
>> struct sel_softcsc;
>> struct acpi_softc *sc_acpi;
>> struct aml_node *sc_node;
>>
>> /* device access through bus space */
>> bus_space_tag_t sc_iot;
>> bus_space_handle_t sc_ioh;
>> bus_addr_t sc_addr;
>> bus_size_t sc_size;
>>
>> struct sel_host *sc_host;
>> };
>>
>> int sel_wait(bus_space_tag_t, bus_space_handle_t, bool);
>>
>> /* Autoconfiguration glue */
>> int sel_acpi_match(struct device *, void *, void *);
>> void sel_acpi_attach(struct device *, struct device *, void *);
>> int sel_print(void *, const char *);
>> int sel_wd_cb(void *, int);
>>
>> /* functions to interact with the controller */
>> void sel_write_wdog(bus_space_tag_t, bus_space_handle_t, int);
>> u_int8_t sel_read_wdog(bus_space_tag_t, bus_space_handle_t);
>> u_int8_t sel_read_status(bus_space_tag_t, bus_space_handle_t);
>> void sel_abort(bus_space_tag_t, bus_space_handle_t);
>> u_int32_t sel_read_boardid(bus_space_tag_t, bus_space_handle_t);
>> u_int32_t sel_read_mcversion(bus_space_tag_t, bus_space_handle_t);
>> u_int16_t sel_read_pciboardid(bus_space_tag_t, bus_space_handle_t);
>> u_int8_t sel_read_ledctl0(bus_space_tag_t, bus_space_handle_t);
>> void sel_write_ledctl0(bus_space_tag_t, bus_space_handle_t, u_int8_t);
>> u_int8_t sel_read_ledctl1(bus_space_tag_t, bus_space_handle_t);
>> void sel_write_ledctl1(bus_space_tag_t, bus_space_handle_t, u_int8_t);
>> u_int8_t sel_read_miscctl0(bus_space_tag_t, bus_space_handle_t);
>> u_int8_t sel_read_miscctl1(bus_space_tag_t, bus_space_handle_t);
>> void sel_read_modelno(bus_space_tag_t, bus_space_handle_t, char*);
>> void sel_read_serialno(bus_space_tag_t, bus_space_ha
Re: owncloudclient GUI issues - core dumps when non-root
Thanks for responding to me, appreciate your tips/advice.. I checked the details though and my login class is 'staff', and as far as I can see the limits are plenty (I've been changing them) Here is the output of those commands/files: (Can you see an issue I am maybe blind too, thanks) I checked my login class: login nick passwd * uid 1000 groups nick wheel operator staff change NEVER class staff gecos nick dir /home/nick shell /bin/ksh expire NEVER And my ulimit -a: time(cpu-seconds) unlimited file(blocks) unlimited coredump(blocks) unlimited data(kbytes) 1572864 stack(kbytes) 4096 lockedmem(kbytes) 2675596 memory(kbytes) 8006984 nofiles(descriptors) 2048 processes 1310 And my login.conf: staff:\ :datasize-cur=1536M:\ :datasize-max=infinity:\ :maxproc-max=4096:\ :maxproc-cur=2048:\ :ignorenologin:\ :requirehome@:\ :openfiles-cur=2048:\ :openfiles-max=infinity:\ :tc=default: Original Message Subject: Re: owncloudclient GUI issues - core dumps when non-root Local Time: May 4, 2016 5:58 AM UTC Time: May 4, 2016 4:58 AM From: o...@drijf.net To: s...@protonmail.com CC: misc@openbsd.org On Tue, May 03, 2016 at 09:05:36PM -0400, Nick wrote: > Thanks for your advice, however it makes no difference changing login.conf in > the way you mentioned.. Still errors out and core dumps. > Root can't get access to it now either. Here's my login.conf, I changed the: > > :openfiles-cur=2048:\ > :openfiles-max=4096:\ > > on my staff group as well, for which I'm a member of. login class != group The question is, which login group are you in. Also, the synatx of login.conf is a bit tricky. Check which login class you are in with useinfo and check you actual limits with ulimit -a, -Otto > > *-*-*-*-*-*-*-*-*-*-*-*-*-* MY LOGIN.CONF: -*-*-*-*-*-*-*-*-*-*-*-*- > # /etc/login.conf > > default:\ > :path=/usr/bin /bin /usr/sbin /sbin /usr/X11R6/bin /usr/local/bin /usr/$ > :umask=022:\ > :datasize-max=2048M:\ > :datasize-cur=2048M:\ > :maxproc-max=1024:\ > :maxproc-cur=512:\ > :openfiles-cur=2048:\ > :openfiles-max=4096:\ > :stacksize-cur=4M:\ > :localcipher=blowfish,8:\ > :tc=auth-defaults:\ > :tc=auth-ftp-defaults: > > *-*-*-*-*-*-*-*-*-*-*-*-*-* AS REGULAR USER: -*-*-*-*-*-*-*-*-*-*-*-*- > $ owncloud > > (owncloud:29572): GLib-ERROR **: Creating pipes for GWakeup: Too many open > files > > Trace/BPT trap (core dumped) > > *-*-*-*-*-*-*-*-*-*-*-*-*-* AND AS ROOT: -*-*-*-*-*-*-*-*-*-*-*-*-*-*-*- > $ su > $ owncloud > > (process:3224): GConf-WARNING **: Client failed to connect to the D-BUS > daemon: > Did not receive a reply. Possible causes include: the remote application did > not send a reply, the message bus security policy blocked the reply, the > reply timeout expired, or the network connection was broken. > > (owncloud:3224): GConf-WARNING **: Client failed to connect to the D-BUS > daemon: > Did not receive a reply. Possible causes include: the remote application did > not send a reply, the message bus security policy blocked the reply, the > reply timeout expired, or the network connection was broken. > > (owncloud:3224): GConf-WARNING **: Client failed to connect to the D-BUS > daemon: > Did not receive a reply. Possible causes include: the remote application did > not send a reply, the message bus security policy blocked the reply, the > reply timeout expired, or the network connection was broken. > > (owncloud:3224): GLib-ERROR **: Creating pipes for GWakeup: Too many open > files > > Trace/BPT trap > > *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*- > > I can't think what could be causing this issue, not entirely sure how to > debug this.
Re: Openbsd broke my hard drive twice! Getting frustrated
Hello, on 04.05.2016 05:30, Gabriel Guzman wrote: I figured out the issue. On my machine (DEL XPS 13) it was the "Intel Rapid Boot" option in BIOS. Disabling that resolved all my boot issues. I can now boot with MBR or GPT off the internal SSD. And, I can also access the BIOS with the internal SSD installed in the system (this was not possible before) Ooouuhh ... Intel Rapid Start still messing up machines? There was a well-publicised series of problems with a number of ThinkPad models (T440p and many relatives) around the end of 2013 / early 2014. If I recall correctly, one needed to turn off some sort of UEFI mode (which disabled Intel Rapid Start at the same time) to prevent bricking the mainboard when installing OSs which were not sufficiently micro and soft. Seemed that the "feature" would read some data from a particular area of the harddisk, expecting that "the right data"(tm) would be there (why verify input, right?), and then just flash it to NVRAM. I'm aware your problem may be related to a different phenomenon. Just meaning to say: Lenovo (and probably other large vendors as well) released BIOS updates during 2014 to fix some rather nasty Intel Rapid Start issues, so in case your machine is of sufficient age, you might like to look into this. Hope it helps ... Christoph -- open...@aixplosive.net
Re: owncloudclient GUI issues - core dumps when non-root
On Wed, May 04, 2016 at 08:24:09AM -0400, Nick wrote: > Thanks for responding to me, appreciate your tips/advice.. I checked > the details though and my login class is 'staff', and as far as I can > see the limits are plenty (I've been changing them) > Here is the output of those commands/files: (Can you see an issue I am > maybe blind too, thanks) > > I checked my login class: > > login nick > passwd * > uid 1000 > groups nick wheel operator staff > change NEVER > class staff > gecos nick > dir /home/nick > shell /bin/ksh > expire NEVER > > And my ulimit -a: > > time(cpu-seconds) unlimited > file(blocks) unlimited > coredump(blocks) unlimited > data(kbytes) 1572864 > stack(kbytes) 4096 > lockedmem(kbytes) 2675596 > memory(kbytes) 8006984 > nofiles(descriptors) 2048 > processes 1310 > > And my login.conf: > > staff:\ > :datasize-cur=1536M:\ > :datasize-max=infinity:\ > :maxproc-max=4096:\ > :maxproc-cur=2048:\ > :ignorenologin:\ > :requirehome@:\ > :openfiles-cur=2048:\ > :openfiles-max=infinity:\ > :tc=default: Check how many files you have on your shared folder and set your limits accordingly. In my case I have $ find ~/ownCloud | wc -l 2744 My soft limit is 2048, and the hard limit is 4096: $ ulimit -n 2048 $ ulimit -Hn 4096 so I bump the soft limit when starting ownCloud: $ ulimit -n 3072 && owncloud How many file descriptors does is actually open? $ fstat -fp `pgrep owncloud` | wc -l 2853 --
Re: Openbsd broke my hard drive twice! Getting frustrated
On 05/04, Christoph Viethen wrote: > Hello, > > on 04.05.2016 05:30, Gabriel Guzman wrote: > > > I figured out the issue. On my machine (DEL XPS 13) it was the "Intel > > Rapid Boot" option in BIOS. Disabling that resolved all my boot issues. > > I can now boot with MBR or GPT off the internal SSD. And, I can also > > access the BIOS with the internal SSD installed in the system (this was > > not possible before) > > Ooouuhh ... Intel Rapid Start still messing up machines? > > I'm aware your problem may be related to a different phenomenon. Just > meaning to say: Lenovo (and probably other large vendors as well) released > BIOS updates during 2014 to fix some rather nasty Intel Rapid Start issues, > so in case your machine is of sufficient age, you might like to look into > this. Thanks for the info! Yeah, my machine is from right around then. My BIOS version is from 2014, so it's possible this was fixed with a BIOS update. Thanks, gabe.
Re: ftp.openbsd.org was down
it was disabled. just use http instead. http://ftp.openbsd.org On Wed, May 4, 2016 at 12:03 PM, freeunix freeunix wrote: > I tried connect to ftp.openbsd.org > > ftp -V ftp://ftp.openbsd.org/ > ftp: connect: Connection refused > ftp: Can't connect or login to host `ftp.openbsd.org'
Re: owncloud forgetting stored user and admin passwords. 5.9-Stable
On Tue, May 3, 2016 21:32, Nick wrote: > I have been having these issues with owncloud on 5.9 Stable where I will go to > log in and says password is wrong, I have two set ups - one in the cloud and > one at home, both are randomly doing this. My partner had to change password 8 > times last night before it would actually work on next log back in login. > > Anyone else been having similar issues? > > I suppose you're mixing up qtkeychain password and owncloud password. Take a closer look on the window you're entering password in.
ftp.openbsd.org was down
I tried connect to ftp.openbsd.org ftp -V ftp://ftp.openbsd.org/ ftp: connect: Connection refused ftp: Can't connect or login to host `ftp.openbsd.org'
Re: Cannot understand iked
04.05.2016 10:25, Andreas Karlsson пишет: On 05/03/2016 10:23 PM, kasak wrote: Hello everybody. I hope somebody can help me with iked. I have 2 gates, both can ping each other. One has this iked.conf: ikev2 from 212.233.112.10 to 192.168.1.0/24 \ from 192.168.2.0/23 to 192.168.1.0/24 \ local 212.233.112.10 srcid 212.233.112.10 Another has: ikev2 active \ from 77.220.137.168 to 192.168.2.0/23 \ from 192.168.1.0/24 to 192.168.2.0/23 \ peer 212.233.112.10 srcid 77.220.137.168 And the problem is: local lan clients can reach remote lan, but local gate itself cannot reach. Look: $ ping -c 2 -I 192.168.2.10 192.168.1.240 PING 192.168.1.240 (192.168.1.240): 56 data bytes 64 bytes from 192.168.1.240: icmp_seq=0 ttl=63 time=2.987 ms 64 bytes from 192.168.1.240: icmp_seq=1 ttl=63 time=2.243 ms --- 192.168.1.240 ping statistics --- 2 packets transmitted, 2 packets received, 0.0% packet loss but $ ping -c 2 192.168.1.240 PING 192.168.1.240 (192.168.1.240): 56 data bytes --- 192.168.1.240 ping statistics --- 2 packets transmitted, 0 packets received, 100.0% packet loss Please check with tcpdump on the enc0 interface what kind of traffic is sent when doing the ping. # tcpdump -nvi enc0 icmp (authentic,confidential): SPI 0xcc1509c7: 212.233.112.10 > 77.220.137.168: 212.233.112.10 > 192.168.1.240: icmp: echo request (id:7a30 seq:5) [icmp cksum ok] (ttl 255, id 62517, len 84) (ttl 64, id 21070, len 104, bad ip cksum 0! -> bcc) Both ping commands sent from same gate. Here is ipsecctl -sa from one of gates: FLOWS: flow esp in from 192.168.1.0/24 to 212.233.112.10 peer 77.220.137.168 srcid IPV4/212.233.112.10 dstid IPV4/77.220.137.168 type use flow esp out from 212.233.112.10 to 192.168.1.0/24 peer 77.220.137.168 srcid IPV4/212.233.112.10 dstid IPV4/77.220.137.168 type require flow esp in from 192.168.1.0/24 to 192.168.2.0/23 peer 77.220.137.168 srcid IPV4/212.233.112.10 dstid IPV4/77.220.137.168 type use flow esp out from 192.168.2.0/23 to 192.168.1.0/24 peer 77.220.137.168 srcid IPV4/212.233.112.10 dstid IPV4/77.220.137.168 type require flow esp out from ::/0 to ::/0 type deny SAD: esp tunnel from 212.233.112.10 to 77.220.137.168 spi 0x22dd1b34 auth hmac-sha2-256 enc aes-256 esp tunnel from 77.220.137.168 to 212.233.112.10 spi 0xd1abf711 auth hmac-sha2-256 enc aes-256 I have the same issue on my boxes that has to contact remote networks. I've solved this by translating my outgoing traffic from my gateway over ipsec to the remote network to a internal interface. See example below. /etc/pf.conf: ... match out log on enc0 from (egress) to 10.10.0.0/24 nat-to (em2) # where em2 is my LAN interface ... I have discovered with tcpdump that on remote gateway the echo request is still on enc0 interface, but echo reply is on em0 (egress) here is cut from tcpdump of em0 on remote gateway: 21:11:28.593541 192.168.1.240 > 212.233.112.10: icmp: echo reply But I can't catch any icmp reply on my pinging gate, nothing on enc0 and em0. So I think that packet going to 212.233.112.10 must go to the enc0 but it comes to em0 from em1. Here is the cut from tcpdump em1 on remote gate: 21:12:08.293106 212.233.112.10 > 192.168.1.240: icmp: echo request 21:12:08.293453 192.168.1.240 > 212.233.112.10: icmp: echo reply Packet that must go to enc0 but goes to em0. Maybe this is some routing issue? Both enc0 and em0 have ability to reach 212.233.112.10 and gate choose em0 instead of enc0 ?
pulseaudio RTP Streaming problem on X11 Desktop
hi, I use the OpenBSD 5.9 amd64 snapshots. and XDM Remote Deskop using is marvelous for OpenBSD. Now I have any problem.(I want use audio streaming for firefox.) I tried to use pulseaudio. but couldn't work it. #/etc/ttys(accept ttyC0 only) ttyC0 "/usr/libexec/getty std.9600" vt220 on secure #/etc/X11/xdm/Xservers :0 foregin :0 #~/.pulse/default.pa load-module module-native-protocol-tcp auth-anonymous=1 load-module module-native-protocol-unix load-module module-suspend-on-idle timeout=1 #~/.pulse/daemon.conf exit-idle-time = -1 1.run pulseaudio [ttyp0]#pulseaudio - W: [(null)] main.c: This program is not intended to be run as root (unless --system is specified). D: [(null)] core-util.c: setpriority() worked. I: [(null)] core-util.c: Successfully gained nice level -11. I: [(null)] main.c: This is PulseAudio 8.0 D: [(null)] main.c: Compilation host: x86_64-unknown-openbsd5.9 D: [(null)] main.c: Compilation CFLAGS: -O2 -pipe -Wall -W -Wextra -Wno-long-long -Wno-overlength-strings -Wunsafe-loop-optimizations -Wundef -Wformat=2 -Wsign-compare -Wformat-security -Wmissing-include-dirs -Wformat-nonliteral -Wpointer-arith -Winit-self -Wdeclaration-after-statement -Wfloat-equal -Wmissing-prototypes -Wredundant-decls -Wmissing-declarations -Wmissing-noreturn -Wshadow -Wendif-labels -Wcast-align -Wstrict-aliasing -Wwrite-strings -Wno-unused-parameter -ffast-math -fno-common -fdiagnostics-show-option D: [(null)] main.c: Running on host: OpenBSD amd64 5.9 GENERIC.MP#1983 D: [(null)] main.c: Found 4 CPUs. I: [(null)] main.c: Page size is 4096 bytes D: [(null)] main.c: Compiled with Valgrind support: no D: [(null)] main.c: Running in valgrind mode: no D: [(null)] main.c: Running in VM: no D: [(null)] main.c: Optimized build: yes D: [(null)] main.c: FASTPATH defined, only fast path asserts disabled. I: [(null)] main.c: Machine ID is b06e5d02cf33f06492d9b3a154934270. I: [(null)] main.c: Using runtime directory /root/.pulse/b06e5d02cf33f06492d9b3a154934270-runtime. I: [(null)] main.c: Using state directory /root/.pulse. I: [(null)] main.c: Using modules directory /usr/local/lib/pulse-8.0/modules. I: [(null)] main.c: Running in system mode: no I: [(null)] main.c: System appears to not support high resolution timers D: [(null)] memblock.c: Using shared memory pool with 1024 slots of size 64.0 KiB each, total size is 64.0 MiB, maximum usable slot size is 65472 D: [(null)] memblock.c: Using shared memory pool with 1024 slots of size 64.0 KiB each, total size is 64.0 MiB, maximum usable slot size is 65472 I: [(null)] cpu-x86.c: CPU flags: SSE3 SSSE3 SSE4_1 SSE4_2 MMXEXT 3DNOWEXT W: [(null)] socket-util.c: IP_TOS failed: Invalid argument I: [(null)] module.c: Loaded "module-native-protocol-tcp" (index: #0; argument: "auth-anonymous=1"). I: [(null)] module.c: Loaded "module-native-protocol-unix" (index: #1; argument: ""). I: [(null)] module.c: Loaded "module-suspend-on-idle" (index: #2; argument: "timeout=1"). D: [(null)] dbus-util.c: Successfully connected to D-Bus session bus 680246337c1b89695cadb60257291201 as :1.14 D: [(null)] main.c: Got org.PulseAudio1! D: [(null)] main.c: Got org.pulseaudio.Server! I: [(null)] main.c: Daemon startup complete. 2.run pactl [ttyp1]#pactl load-module module-null-sink sink_name=rtp 3 [ttyp0] I: [(null)] client.c: Created 0 "Native client (UNIX socket client)" D: [(null)] protocol-native.c: Protocol version: remote 30, local 30 D: [(null)] protocol-native.c: SHM possible: yes D: [(null)] protocol-native.c: Negotiated SHM: yes D: [(null)] srbchannel.c: SHM block is 65472 bytes, ringbuffer capacity is 2 * 32712 bytes D: [(null)] protocol-native.c: Failed to create srbchannel I: [(null)] sink.c: Created sink 0 "rtp" with sample spec s16le 2ch 44100Hz and channel map front-left,front-right I: [(null)] sink.c: device.description = "Null Output" I: [(null)] sink.c: device.class = "abstract" I: [(null)] sink.c: device.icon_name = "audio-card" I: [(null)] source.c: Created source 0 "rtp.monitor" with sample spec s16le 2ch 44100Hz and channel map front-left,front-right I: [(null)] source.c: device.description = "Monitor of Null Output" I: [(null)] source.c: device.class = "monitor" I: [(null)] source.c: device.icon_name = "audio-input-microphone" D: [null-sink] module-null-sink.c: Thread starting up D: [(null)] module-suspend-on-idle.c: Sink rtp becomes idle, timeout in 1 seconds. I: [(null)] module.c: Loaded "module-null-sink" (index: #3; argument: "sink_name=rtp"). I: [(null)] client.c: Freed 0 "pactl" I: [(null)] protocol-native.c: Connection died. I: [(null)] module-suspend-on-idle.c: Sink rtp idle for too long, suspending ... D: [(null)] sink.c: Suspend cause of sink rtp is 0x0004, suspending D: [(null)] core.c: Hmm, no streams around, trying to vacuum. 3.run pactl [ttyp1]#pactl load-module module-rtp-send source=rtp.monitor Failure: Module initialization failed [ttyp0] I: [(null)] client.c: Created 1 "Native client (UNIX socket client)" D
Re: Can't change rtadvd route preference for the default route
Evgeniy Sudyr writes: > Hi, > > I want to change route preference for the default route in RA messages > which are sent to clients. > > On 5.9 GENERIC.MP#1888 amd64 I do have rtadvd and changing rtflags in > rtadvd.conf doesn't changes > > Default router Preference (it sends default value, where I define "l" = Low). > > In config I have just two items set: > > vlan6:\ >:raflags#64:\ >:rtflags="l": > > raflags#64 (Other stateful configuration flag bit) > rtflags="l" (Low route preference for the route) I don't understand what "l" means here, rtadvd.conf(5) doesn't seem to mention this as a valid setting. > I'm always getting pref=medium for default router preference. > > $ ndp -rn > fe80:::::5e0c%vlan0 if=vlan0, flags=O, pref=medium, expire=29m52s > > However It works perfect for non-default route preference for the > route, but not default e.g.: > > vlan6:\ >:raflags#64:rtflags="l":rtprefix="2001:1:1:1::":rtplen#64: > > It will be great if someone can share working config options which > allows to change DRFAULT router preference RA message value. As the rtflags description says, bits 4 and 3 are used to encode the preference. "low" is 0x18 / 24. :raflags#24: seems to do the trick here. Your mail points out three problems imo: - tcpdump doesn't show the preference - the documentation of raflags is lacking - it's a shame that raflags was used instead of a nicer config abstraction. I think :pref="low":managed#1: would be a bit easier than playing with... bits. -- jca | PGP : 0x1524E7EE / 5135 92C1 AD36 5293 2BDF DDCC 0DFA 74AE 1524 E7EE
Re: Laptop not waking from suspend on opening lid
I just checked it and I can reproduce it on my T400 (dmesg below). On Tue May 3 2016 08:28, Anthony Campbell wrote: > On 03 May 2016, Anthony Campbell wrote: > > On 02 May 2016, Mike Larkin wrote: > > > On Sun, May 01, 2016 at 04:08:28PM +0100, Anthony Campbell wrote: > > > > This is on a Thinkpad Z61m running amd64. Suspend on lid closure has > > > > worked without problems for many months with numerous snapshots. After > > > > upgrading on 30 April the machine no longer wakes on lid opening. The > > > > sleep symbol below the screen blinks repeatedly but nothing else > > > > happens. > > > > > > > > If I suspend it with Fn+F4 the same thing happens; it is impossible to > > > > wake the machine. > > > > > > > > Another Thinkpad running i386 is not affected. > > > > > > > > > > When did it last work? Eg, when before "30 April"? Unfortunately, I didn't upgrade frequently - I made a jump from Apr 7. to Apr 29., but the kernel from Apr 7. works. I'll try to bisect. OpenBSD 5.9-current (GENERIC.MP) #2000: Fri Apr 29 17:01:24 MDT 2016 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 4166717440 (3973MB) avail mem = 4035842048 (3848MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xe0010 (80 entries) bios0: vendor LENOVO version "7UET94WW (3.24 )" date 10/17/2012 bios0: LENOVO 6475BE3 acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP SSDT ECDT APIC MCFG HPET SLIC BOOT ASF! SSDT TCPA DMAR SSDT SSDT SSDT acpi0: wakeup devices LID_(S3) SLPB(S3) UART(S3) IGBE(S4) EXP0(S4) EXP1(S4) EXP2(S4) EXP3(S4) EXP4(S4) PCI1(S4) USB0(S3) USB3(S3) USB5(S3) EHC0(S3) EHC1(S3) HDEF(S4) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpiec0 at acpi0 acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM)2 Duo CPU P8400 @ 2.26GHz, 2261.36 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,NXE,LONG,LAHF,PERF,SENSOR cpu0: 3MB 64b/line 8-way L2 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 7 var ranges, 88 fixed ranges cpu0: apic clock running at 265MHz cpu0: mwait min=64, max=64, C-substates=0.2.2.2.2.1.3, IBE cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Core(TM)2 Duo CPU P8400 @ 2.26GHz, 2261.00 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,NXE,LONG,LAHF,PERF,SENSOR cpu1: 3MB 64b/line 8-way L2 cache cpu1: smt 0, core 1, package 0 ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 24 pins ioapic0: misconfigured as apic 2, remapped to apid 1 acpimcfg0 at acpi0 addr 0xe000, bus 0-63 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (AGP_) acpiprt2 at acpi0: bus 2 (EXP0) acpiprt3 at acpi0: bus 3 (EXP1) acpiprt4 at acpi0: bus -1 (EXP2) acpiprt5 at acpi0: bus 5 (EXP3) acpiprt6 at acpi0: bus 13 (EXP4) acpiprt7 at acpi0: bus 21 (PCI1) acpicpu0 at acpi0: !C3(100@57 mwait.3@0x30), !C2(500@1 mwait.1@0x10), C1(1000@1 mwait.1), PSS acpicpu1 at acpi0: !C3(100@57 mwait.3@0x30), !C2(500@1 mwait.1@0x10), C1(1000@1 mwait.1), PSS acpipwrres0 at acpi0: PUBS, resource for USB0, USB3, USB5, EHC0, EHC1 acpitz0 at acpi0: critical temperature is 127 degC acpitz1 at acpi0: critical temperature is 100 degC acpibtn0 at acpi0: LID_ acpibtn1 at acpi0: SLPB "PNP0303" at acpi0 not configured "IBM0057" at acpi0 not configured "PNP0501" at acpi0 not configured "PNP0400" at acpi0 not configured acpibat0 at acpi0: BAT0 model "42T5264" serial 3499 type LION oem "Panasonic" acpiac0 at acpi0: AC unit online acpithinkpad0 at acpi0 "IBM0079" at acpi0 not configured "PNP0C14" at acpi0 not configured acpidock0 at acpi0: GDCK docked (15) acpivideo0 at acpi0: VID_ acpivout0 at acpivideo0: LCD0 acpivideo1 at acpi0: VID_ cpu0: Enhanced SpeedStep 2261 MHz: speeds: 2267, 2266, 1600, 800 MHz pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 "Intel GM45 Host" rev 0x07 inteldrm0 at pci0 dev 2 function 0 "Intel GM45 Video" rev 0x07 drm0 at inteldrm0 intagp0 at inteldrm0 agp0 at intagp0: aperture at 0xd000, size 0x1000 inteldrm0: msi inteldrm0: 1440x900 wsdisplay0 at inteldrm0 mux 1: console (std, vt100 emulation) wsdisplay0: screen 1-5 added (std, vt100 emulation) "Intel GM45 Video" rev 0x07 at pci0 dev 2 function 1 not configured "Intel GM45 HECI" rev 0x07 at pci0 dev 3 function 0 not configured em0 at pci0 dev 25 function 0 "Intel ICH9 IGP M AMT" rev 0x03: msi, address 00:1c:25:95:39:e7 uhci0 at pci0 dev 26 function 0 "Intel 82801I USB" rev 0x03: apic 1 int 20 uhci1 at pci0 dev 26 function 1 "Intel 82801I USB" rev 0x03: apic 1 int 21 uhci2 at pci0 dev 26 function 2 "Intel 82801I USB" rev 0x03: apic 1 int 22
Re: Laptop not waking from suspend on opening lid
On Wed, May 04, 2016 at 11:06:37PM +0200, Norman Golisz wrote: > I just checked it and I can reproduce it on my T400 (dmesg below). > > On Tue May 3 2016 08:28, Anthony Campbell wrote: > > On 03 May 2016, Anthony Campbell wrote: > > > On 02 May 2016, Mike Larkin wrote: > > > > On Sun, May 01, 2016 at 04:08:28PM +0100, Anthony Campbell wrote: > > > > > This is on a Thinkpad Z61m running amd64. Suspend on lid closure has > > > > > worked without problems for many months with numerous snapshots. After > > > > > upgrading on 30 April the machine no longer wakes on lid opening. The > > > > > sleep symbol below the screen blinks repeatedly but nothing else > > > > > happens. > > > > > > > > > > If I suspend it with Fn+F4 the same thing happens; it is impossible to > > > > > wake the machine. > > > > > > > > > > Another Thinkpad running i386 is not affected. > > > > > > > > > > > > > When did it last work? Eg, when before "30 April"? > > Unfortunately, I didn't upgrade frequently - I made a jump from Apr 7. > to Apr 29., but the kernel from Apr 7. works. > > I'll try to bisect. > This is probably the same problem that kettenis fixed in a recent post. I'd try applying that diff first. -ml
