Re: Realtek Audio On Kabylake

On 03/30/2017 14:30, Pete Wright wrote: On 03/30/2017 14:26, Dimitry Andric wrote: On 30 Mar 2017, at 20:18, Pete Wright wrote: Hello, I have a new Kabylake based Intel laptop running CURRENT (well drm-next). Everything has "just worked" so far except audio. Here is

Re: New syscons bugs: shutdown -r doesn't execute rc.d sequence and others

On 30.03.2017 21:53, Bruce Evans wrote: > I think it was the sizing. The non-updated mode is 80x25, so the row > address can be out of bounds in the teken layer. I have text 80x30 mode set at rc stage, and _after_ that may have many kernel messages on console, all without causing reboot. How it

Re: FYI: what it takes for RAM+swap to build devel/llvm40 with 4 processors or cores and WITH__DEBUG= (powerpc64 example)

On 2017-Mar-30, at 1:22 PM, Mark Millard wrote: > On 2017-Mar-29, at 8:53 AM, Brooks Davis wrote: > >> On Mon, Mar 27, 2017 at 03:25:04AM -0700, Mark Millard wrote: >>> On 2017-Mar-27, at 2:41 AM, Dimitry Andric wrote: >>> On 26 Mar 2017, at 23:36, Mark Millard

Re: Realtek Audio On Kabylake

On 03/30/2017 14:26, Dimitry Andric wrote: On 30 Mar 2017, at 20:18, Pete Wright wrote: Hello, I have a new Kabylake based Intel laptop running CURRENT (well drm-next). Everything has "just worked" so far except audio. Here is the output of /dev/sndstat: $ cat

Re: Realtek Audio On Kabylake

On 30 Mar 2017, at 20:18, Pete Wright wrote: > > Hello, > I have a new Kabylake based Intel laptop running CURRENT (well > drm-next). Everything has "just worked" so far except audio. Here is > the output of /dev/sndstat: > > $ cat /dev/sndstat > Installed devices: > pcm0:

Re: FYI: what it takes for RAM+swap to build devel/llvm40 with 4 processors or cores and WITH__DEBUG= (powerpc64 example)

On 30 Mar 2017, at 19:55, Brooks Davis wrote: > > On Thu, Mar 30, 2017 at 07:26:19PM +0200, Dimitry Andric wrote: ... >> >> As said, this is because of WITH_DEBUG. Don't use that for the llvm >> ports, for now. It will also allow you to build them with much less RAM >> in

Re: FYI: what it takes for RAM+swap to build devel/llvm40 with 4 processors or cores and WITH__DEBUG= (powerpc64 example)

On 2017-Mar-30, at 10:55 AM, Brooks Davis wrote: > P.S. Somewhat off topice, but related. FAIR WARNING: the days of > self-hosted 32-bit systems are numbered. Switching to lld from our > ancient BFD linker will probably buy us some time, but I'd be surprised > if you will be able to build

Re: FYI: what it takes for RAM+swap to build devel/llvm40 with 4 processors or cores and WITH__DEBUG= (powerpc64 example)

On 2017-Mar-29, at 8:53 AM, Brooks Davis wrote: > On Mon, Mar 27, 2017 at 03:25:04AM -0700, Mark Millard wrote: >> On 2017-Mar-27, at 2:41 AM, Dimitry Andric wrote: >> >>> On 26 Mar 2017, at 23:36, Mark Millard wrote: I upgraded from llvm40 r4 to final. An

Re: increased power consumption lately?

I don't /think/ so - which thread is it on your end? Can you run pmcstat -S instructions -T to see what's taking your CPU? -adrian On 28 March 2017 at 13:36, Johannes Lundberg wrote: > Hi > > Personally I got some acpi-something kernel thread at 100% CPU constant > usage.

Re: New syscons bugs: shutdown -r doesn't execute rc.d sequence and others

On Thu, 30 Mar 2017, Andrey Chernov wrote: On 30.03.2017 18:13, Bruce Evans wrote: On Thu, 30 Mar 2017, Andrey Chernov wrote: ... Finally I have good news and bad news with today's -current: 1) It seems your latest commit r316136 fix premature reboot issue. Now I need to know how that

Realtek Audio On Kabylake

Hello, I have a new Kabylake based Intel laptop running CURRENT (well drm-next). Everything has "just worked" so far except audio. Here is the output of /dev/sndstat: $ cat /dev/sndstat Installed devices: pcm0: (play/rec) default pcm1: (play) No devices installed from userspace. I am unable

Re: FYI: what it takes for RAM+swap to build devel/llvm40 with 4 processors or cores and WITH__DEBUG= (powerpc64 example)

On Thu, Mar 30, 2017 at 07:26:19PM +0200, Dimitry Andric wrote: > On 30 Mar 2017, at 19:06, Alexey Dokuchaev wrote: > > > > On Mon, Mar 27, 2017 at 11:41:40AM +0200, Dimitry Andric wrote: > >> On 26 Mar 2017, at 23:36, Mark Millard wrote: > >>> ... > >>>

Re: FYI: what it takes for RAM+swap to build devel/llvm40 with 4 processors or cores and WITH__DEBUG= (powerpc64 example)

On Thursday 30 March 2017 17:06:48 Alexey Dokuchaev wrote: > On Mon, Mar 27, 2017 at 11:41:40AM +0200, Dimitry Andric wrote: > > On 26 Mar 2017, at 23:36, Mark Millard wrote: > > > ... > > > Also interesting was: > > > > > > Installed packages to be REMOVED: > > >

Re: FYI: what it takes for RAM+swap to build devel/llvm40 with 4 processors or cores and WITH__DEBUG= (powerpc64 example)

On 30 Mar 2017, at 19:06, Alexey Dokuchaev wrote: > > On Mon, Mar 27, 2017 at 11:41:40AM +0200, Dimitry Andric wrote: >> On 26 Mar 2017, at 23:36, Mark Millard wrote: >>> ... >>> Also interesting was: >>> >>> Installed packages to be REMOVED: >>>

Re: New syscons bugs: shutdown -r doesn't execute rc.d sequence and others

On 30.03.2017 18:13, Bruce Evans wrote: > On Thu, 30 Mar 2017, Andrey Chernov wrote: > >> On 30.03.2017 12:34, Andrey Chernov wrote: >>> On 30.03.2017 12:23, Andrey Chernov wrote: Yes, only for reboot/shutdown. The system does not do anythings wrong even under high load. On reboot or

Re: FYI: what it takes for RAM+swap to build devel/llvm40 with 4 processors or cores and WITH__DEBUG= (powerpc64 example)

On Mon, Mar 27, 2017 at 11:41:40AM +0200, Dimitry Andric wrote: > On 26 Mar 2017, at 23:36, Mark Millard wrote: > > ... > > Also interesting was: > > > > Installed packages to be REMOVED: > > llvm40-4.0.0.r4 > > > > Number of packages to be removed: 1 > > > > The

D10203: loader: zfs reader should check all labels

Hi! Sorry about forward, but this patch is something a bit more complicated and if we have some people willing to test, it would be really nice:) I have had it around for my illumos port for some time now, but those small details about the zfsboot/gptzfsboot etc sometimes do count a lot…

Re: New syscons bugs: shutdown -r doesn't execute rc.d sequence and others

On Thu, 30 Mar 2017, Andrey Chernov wrote: On 30.03.2017 12:34, Andrey Chernov wrote: On 30.03.2017 12:23, Andrey Chernov wrote: Yes, only for reboot/shutdown. The system does not do anythings wrong even under high load. On reboot or hang those lines are never printed: kernel: Waiting (max

Re: New syscons bugs: shutdown -r doesn't execute rc.d sequence and others

On Thu, 30 Mar 2017, Andrey Chernov wrote: On 30.03.2017 14:23, Andriy Gapon wrote: On 30/03/2017 12:34, Andrey Chernov wrote: On 30.03.2017 12:23, Andrey Chernov wrote: Yes, only for reboot/shutdown. The system does not do anythings wrong even under high load. On reboot or hang those lines

Re: New syscons bugs: shutdown -r doesn't execute rc.d sequence and others

On Thu, 30 Mar 2017, Andrey Chernov wrote: We don't understand the bug yet. It might not even be in sc. Do you only see problems for shutdown? The shutdown environment is special for locking. Yes, only for reboot/shutdown. The system does not do anythings wrong even under high load. On

Re: New syscons bugs: shutdown -r doesn't execute rc.d sequence and others

On 30.03.2017 12:34, Andrey Chernov wrote: > On 30.03.2017 12:23, Andrey Chernov wrote: >> Yes, only for reboot/shutdown. The system does not do anythings wrong >> even under high load. On reboot or hang those lines are never printed: >> >> kernel: Waiting (max 60 seconds) for system process

Re: New syscons bugs: shutdown -r doesn't execute rc.d sequence and others

On 30.03.2017 14:23, Andriy Gapon wrote: > On 30/03/2017 12:34, Andrey Chernov wrote: >> On 30.03.2017 12:23, Andrey Chernov wrote: >>> Yes, only for reboot/shutdown. The system does not do anythings wrong >>> even under high load. On reboot or hang those lines are never printed: >>> >>> kernel:

Re: New syscons bugs: shutdown -r doesn't execute rc.d sequence and others

On Thu, 30 Mar 2017, Andrey Chernov wrote: On 30.03.2017 9:51, Andrey Chernov wrote: On 30.03.2017 8:53, Bruce Evans wrote: The escape sequences in dmesg are very interesting. You should debug those. I'll send you them a bit later. Since I don't want vt at all, I don't want to debug or

Re: New syscons bugs: shutdown -r doesn't execute rc.d sequence and others

On 30/03/2017 14:23, Andriy Gapon wrote: > On 30/03/2017 12:34, Andrey Chernov wrote: >> On 30.03.2017 12:23, Andrey Chernov wrote: >>> Yes, only for reboot/shutdown. The system does not do anythings wrong >>> even under high load. On reboot or hang those lines are never printed: >>> >>> kernel:

Re: New syscons bugs: shutdown -r doesn't execute rc.d sequence and others

On 30/03/2017 12:34, Andrey Chernov wrote: > On 30.03.2017 12:23, Andrey Chernov wrote: >> Yes, only for reboot/shutdown. The system does not do anythings wrong >> even under high load. On reboot or hang those lines are never printed: >> >> kernel: Waiting (max 60 seconds) for system process

Re: New syscons bugs: shutdown -r doesn't execute rc.d sequence and others

On Thu, 30 Mar 2017, Andrey Chernov wrote: On 29.03.2017 6:29, Bruce Evans wrote: ... I just found the cause, it is new syscons bug (bde@ cc'ed). I never compile vt driver into kernel, i.e. I don't have this lines in the kernel config: devicevt devicevt_vga devicevt_efifb When I

Re: New syscons bugs: shutdown -r doesn't execute rc.d sequence and others

On Thu, 30 Mar 2017, Andrey Chernov wrote: On 30.03.2017 8:53, Bruce Evans wrote: Maybe two will be enough too, I don't check. I just don't need _any_ of vt lines. What is matter it is that syscons only mode (without any vt) was recently broken, causing shutdown problems and file system damage

Re: New syscons bugs: shutdown -r doesn't execute rc.d sequence and others

On 30.03.2017 12:23, Andrey Chernov wrote: > Yes, only for reboot/shutdown. The system does not do anythings wrong > even under high load. On reboot or hang those lines are never printed: > > kernel: Waiting (max 60 seconds) for system process `vnlru' to stop...done > kernel: Waiting (max 60

Re: New syscons bugs: shutdown -r doesn't execute rc.d sequence and others

> We don't understand the bug yet. It might not even be in sc. Do you only > see problems for shutdown? The shutdown environment is special for > locking. Yes, only for reboot/shutdown. The system does not do anythings wrong even under high load. On reboot or hang those lines are never

Re: New syscons bugs: shutdown -r doesn't execute rc.d sequence and others

On 30.03.2017 9:51, Andrey Chernov wrote: > On 30.03.2017 8:53, Bruce Evans wrote: >>> Maybe two will be enough too, I don't check. I just don't need _any_ of >>> vt lines. What is matter it is that syscons only mode (without any vt) >>> was recently broken, causing shutdown problems and file

Re: New syscons bugs: shutdown -r doesn't execute rc.d sequence and others

On 30.03.2017 8:53, Bruce Evans wrote: >> Maybe two will be enough too, I don't check. I just don't need _any_ of >> vt lines. What is matter it is that syscons only mode (without any vt) >> was recently broken, causing shutdown problems and file system damage >> each time. Syscons only mode works