On Fri, 31 Mar 2017, Andrey Chernov wrote:
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
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
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
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
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
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
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
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
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:
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
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:
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
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
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
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
> 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
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
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
On 29.03.2017 6:29, Bruce Evans wrote:
> Using rc_debug=yes I see that it is the kernel problem, not rc
> problem.
> Sometimes rc backward sequence executed even fully, sometimes only
> partly, but in unpredictable moment inside rc sequence the kernel
> decide
> to reboot
On Tue, 28 Mar 2017, Ngie Cooper wrote:
On Mar 28, 2017, at 21:40, Bruce Evans wrote:
On Wed, 29 Mar 2017, Bruce Evans wrote:
On Wed, 29 Mar 2017, Andrey Chernov wrote:
...
Moreover, I can't enter KDB via Ctrl-Alt-ESC in the syscons only mode
anymore - nothing
On Wed, 29 Mar 2017, Bruce Evans wrote:
On Wed, 29 Mar 2017, Andrey Chernov wrote:
...
Moreover, I can't enter KDB via Ctrl-Alt-ESC in the syscons only mode
anymore - nothing happens. In the vt mode I can, but can't exit via "c"
properly, all chars typed after "c" produce beep unless I switch
On Wed, 29 Mar 2017, Andrey Chernov wrote:
On 29.03.2017 0:46, Ngie Cooper (yaneurabeya) wrote:
On Mar 28, 2017, at 14:27, Andrey Chernov wrote:
???
Using rc_debug=yes I see that it is the kernel problem, not rc problem.
Sometimes rc backward sequence executed even
> On Mar 29, 2017, at 01:26, Bruce Evans wrote:
>
> On Tue, 28 Mar 2017, Ngie Cooper wrote:
>
>>> On Mar 28, 2017, at 21:40, Bruce Evans wrote:
>>>
On Wed, 29 Mar 2017, Bruce Evans wrote:
> On Wed, 29 Mar 2017, Andrey Chernov wrote:
> On Mar 28, 2017, at 21:40, Bruce Evans wrote:
>
>> On Wed, 29 Mar 2017, Bruce Evans wrote:
>>
>>> On Wed, 29 Mar 2017, Andrey Chernov wrote:
>>> ...
>>> Moreover, I can't enter KDB via Ctrl-Alt-ESC in the syscons only mode
>>> anymore - nothing happens. In the vt mode I
On 29.03.2017 0:46, Ngie Cooper (yaneurabeya) wrote:
>
>> On Mar 28, 2017, at 14:27, Andrey Chernov wrote:
>
> …
>
>>> Using rc_debug=yes I see that it is the kernel problem, not rc problem.
>>> Sometimes rc backward sequence executed even fully, sometimes only
>>> partly,
25 matches
Mail list logo