Date   

Re: [ANNOUNCE] v4.19.50-cip3-rt2

Pavel Machek
 

Hi!

I finally was able to make the viable .config... For the previous
rt-kernel for BBB.

root@beaglebone:~# uname -a
Linux beaglebone 4.19.13-cip1-rt1 #1 PREEMPT RT Tue Jul 23 12:18:18
GMT 2019 armv7l GNU/Linux

It was very tough and rough... But I have it! Now I need to abandon
this effort, since I have another immediate things to do!
No problem. You should be able to use same .config with the new
kernel...

Best regards,
Pavel
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany


Re: [ANNOUNCE] v4.19.50-cip3-rt2

Zoran
 

I finally was able to make the viable .config... For the previous
rt-kernel for BBB.

root@beaglebone:~# uname -a
Linux beaglebone 4.19.13-cip1-rt1 #1 PREEMPT RT Tue Jul 23 12:18:18
GMT 2019 armv7l GNU/Linux

It was very tough and rough... But I have it! Now I need to abandon
this effort, since I have another immediate things to do!

Well...

Zoran
_______

On Tue, Jul 23, 2019 at 11:06 PM Pavel Machek <pavel@denx.de> wrote:

Hi!

Trees are available at

https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git/log/?h=linux-4.19.y-cip-rt-rebase

https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git/log/?h=linux-4.19.y-cip-rt

And their content should be identical. I attempted to tag it in a way
consistent with previous releases, and I attempted to sign a tag.
...but you didn't push the tag yet? Or is this WiP?
Sorry, I forgot I need to push the tag. It should be fixed now.

Best regards,
Pavel
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
_______________________________________________
cip-dev mailing list
cip-dev@lists.cip-project.org
https://lists.cip-project.org/mailman/listinfo/cip-dev


[ANNOUNCE] v4.4.185-cip35-rt24

Pavel Machek
 

Hi!

v4.4.185-cip35-rt24 should be available at kernel.org.

Daniel says:
# in the v4.4-rt is still a problem with f01f17d3705b ("mm,
# vmstat: make quiet_vmstat lighter"). It is needed to boot on x86_64
# but it breaks on NVIDIA's boards, e.g. Jetson. Unfortunately, I don't
# have a NVIDIA board in my lab to figure out what is missing. So I
# suspect there is a still a problem hidden in the current v4.4-rt tree.

I did nothing to solve that problem. If someone uses NVIDIA boards,
let me know.

Trees are available at

https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git/log/?h=linux-4.4.y-cip-rt-rebase

https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git/log/?h=linux-4.4.y-cip-rt

And their content should be identical. It should be tagged and tag
should be signed.

Best regards,
Pavel

--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany


Re: [ANNOUNCE] v4.19.50-cip3-rt2

Pavel Machek
 

Hi!

Trees are available at

https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git/log/?h=linux-4.19.y-cip-rt-rebase

https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git/log/?h=linux-4.19.y-cip-rt

And their content should be identical. I attempted to tag it in a way
consistent with previous releases, and I attempted to sign a tag.
...but you didn't push the tag yet? Or is this WiP?
Sorry, I forgot I need to push the tag. It should be fixed now.

Best regards,
Pavel
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany


Re: [PATCH 4.4.y-cip 03/10] rtc: pcf85363: set time accurately

Ben Hutchings <ben.hutchings@...>
 

On Wed, 2019-07-17 at 07:47 +0000, Biju Das wrote:
Hi Pavel,

Thanks for the feedback.

-----Original Message-----
From: Pavel Machek <pavel@denx.de>
Sent: Tuesday, July 16, 2019 10:04 PM
To: Biju Das <biju.das@bp.renesas.com>
Cc: cip-dev@lists.cip-project.org
Subject: Re: [cip-dev] [PATCH 4.4.y-cip 03/10] rtc: pcf85363: set time
accurately

On Tue 2019-07-16 09:15:14, Biju Das wrote:
commit 188306ac9536ec47674ffa9dd330f69927679aeb upstream.

As per 8.2.6 Setting and reading the time in RTC mode, first stop the
clok, then reset it before setting the date and time registers.
Finally, start the clock.

This uses register address wrap around from 0x2f to 0x00 for
efficiency.
How does wrap around work? AFAICT it is supposed to have ram at 0x40.
Please see the document [1] and [2] section 8, that have the details related to wrap around.
[1] https://www.nxp.com/docs/en/data-sheet/PCF85363A.pdf
[2] https://www.nxp.com/docs/en/data-sheet/PCF85263A.pdf
Regardless of what the hardware does...

Does it really provide increased efficiency (given regmap layer in
between) and will such trick cause problems in future? If regmap is not
aware of register mirrors it might get confused and provide stale values, for
example...
...I think Pavel is right on this point. regmap doesn't seem to have
any provision for register addresses wrapping around, and it looks like
this causes a buffer overrun in the register cache.

Ben.

--
Ben Hutchings, Software Developer Codethink Ltd
https://www.codethink.co.uk/ Dale House, 35 Dale Street
Manchester, M1 2HF, United Kingdom


Re: [ANNOUNCE] v4.19.50-cip3-rt2

Jan Kiszka
 

On 23.07.19 14:40, Pavel Machek wrote:
Hi!

4.19.50-cip3-rt2 should be available at kernel.org. It performs well
on socfpga (Altera-Terasic-Deo-NanoAltera); but not so well on iwg20m
(r8a7743-iwg20d-q7) board.
Thanks!

Trees are available at

https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git/log/?h=linux-4.19.y-cip-rt-rebase

https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git/log/?h=linux-4.19.y-cip-rt

And their content should be identical. I attempted to tag it in a way
consistent with previous releases, and I attempted to sign a tag.
...but you didn't push the tag yet? Or is this WiP?

Jan

--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux


[ANNOUNCE] v4.19.50-cip3-rt2

Pavel Machek
 

Hi!

4.19.50-cip3-rt2 should be available at kernel.org. It performs well
on socfpga (Altera-Terasic-Deo-NanoAltera); but not so well on iwg20m
(r8a7743-iwg20d-q7) board.

Trees are available at

https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git/log/?h=linux-4.19.y-cip-rt-rebase

https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git/log/?h=linux-4.19.y-cip-rt

And their content should be identical. I attempted to tag it in a way
consistent with previous releases, and I attempted to sign a tag.

Best regards,
Pavel
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany


Re: [RFC/RFT] -cip-rt kernels for review/testing

Pavel Machek
 

Hi!

On 6/24/19 8:28 AM, Jan Kiszka wrote:
On 23.06.19 22:37, Pavel Machek wrote:
v4.19.50-rt22-cip3-rebase was reasonably easy to do, as -cip1 was
empty. v4.4.179-rt181-cip34-rebase was more interesting.
Yep, the v4.4.179 brought some conflicts. Have you compared with my merge
for v4.4-rt? Not sure if I understand your worklfow correctly. It looks like
you used for the rebase branches the upstream -rt patchset and merged the
cip branch. Is this correct?
It looks like I'll need to redo the rebase at least for 4.4. I plan to
rebase -cip specific patches on top of -rt.

What I did for the v4.4-cip-rt and v4.19-cip-rt is following

- initial setup (only once):

took the latest cip release and applied the current/matching -rt patcheset

- regulare update:

$ cd v4.4-rt
$ git tag -l 'v4\.4\.*' --sort=v:refname | tail
$ git merge v4.4.120 [fixup conflicts]

# do some testing (this is on Linutronix -rt test infrastrucure)
$ git push lxcvs -f --follow-tag HEAD:stable-maintenance-4.4.y-rt

$ srt commit
$ srt tag

$ cd v4.4-rt-rebase
$ git rebase -i v4.4.120 [fixup conflicts]
$ srt commit
$ srt tag

# check if the -rt-rebase branch is identical to v4.4-rt
$ git diff v4.4-rt

$ srt create v4.4.115-rt130 v4.4.120-rt135
$ srt sign v4.4.115-rt130 v4.4.120-rt135
$ srt upload v4.4.115-rt130 v4.4.120-rt135
$ srt push v4.4.115-rt130 v4.4.120-rt135

# XXX push missing tags
$ git push origin v4.4.115-rt131 v4.4.116-rt132 v4.4.118-rt133
v4.4.119-rt134

$ srt announce v4.4.115-rt130 v4.4.120-rt135 > ../announce-rt
$ cat ../announce-rt | msmtp -t --

The srt tool is available here: https://github.com/igaw/stable-rt-tools
It a few lines around git to make the steps consist. It is based on Steven
Rostedt workflow. Tom Zanussi (also -rt stable maintainer) and I am using
the tool to maintain the -rt trees.
Thanks for pointer. It does not want to run here (incompatible version
of python 3?), so let me try to do one more manual attempt, and if
that fails I'll try to fix/workaround python problems.

If it helps, I am going to give a talk at Plubmers on how to maintain the
-rt trees:
Thanks for pointer. I'm not sure I'll be at Plumbers.

Best regards,
Pavel
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany


[Git][cip-project/cip-kernel/cip-kernel-sec][master] Import more data

Agustin Benito Bethencourt
 

Ben Hutchings pushed to branch master at cip-project / cip-kernel / cip-kernel-sec

Commits:

  • 87656eff
    by Ben Hutchings at 2019-07-22T20:09:29Z
    Import more data
    

5 changed files:

Changes:

  • issues/CVE-2019-10126.yml
    ... ... @@ -5,6 +5,9 @@ references:
    5 5
     - https://marc.info/?l=oss-security&m=155965912410053&w=2
    
    6 6
     fixed-by:
    
    7 7
       linux-3.16.y: [a62393d7eb63bd075c51154002825cc7ab4dd3eb]
    
    8
    +  linux-4.14.y: [b1459fb34061337efbf0d47a3ba6208f2f59829d]
    
    8 9
       linux-4.19.y: [c7e427e28a3a2d1b89b8f9fa7c3f559774d91a7b]
    
    10
    +  linux-4.4.y: [3a611df229a90247c9a5159d136c60f4008c29a2]
    
    11
    +  linux-4.9.y: [f70d411e2ecd1f8297e1fd7e91108ca220986784]
    
    9 12
       linux-5.1.y: [e9111176d9c195ba709245f1bf1d3d1dae5cd22a]
    
    10 13
       mainline: [69ae4f6aac1578575126319d3f55550e7e440449]

  • issues/CVE-2019-13272.yml
    1
    +description: 'ptrace: Fix ->ptracer_cred handling for PTRACE_TRACEME'
    
    2
    +references:
    
    3
    +- https://bugzilla.suse.com/show_bug.cgi?id=1140671
    
    4
    +- https://bugs.chromium.org/p/project-zero/issues/detail?id=1903
    
    5
    +- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-13272
    
    6
    +- http://packetstormsecurity.com/files/153663/Linux-PTRACE_TRACEME-Broken-Permission-Object-Lifetime-Handling.html
    
    7
    +- https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=6994eefb0053799d2e07cd140df6c2ea106c41ee
    
    8
    +- https://bugzilla.redhat.com/show_bug.cgi?id=1730895
    
    9
    +comments:
    
    10
    +  Debian-carnil: |-
    
    11
    +    64b875f7ac8a ("ptrace: Capture the ptracer's creds not
    
    12
    +    PT_PTRACE_CAP") which is in 4.10 was backported to older stable
    
    13
    +    series as well, got included in v4.9.32
    
    14
    +reporters:
    
    15
    +- Jann Horn
    
    16
    +introduced-by:
    
    17
    +  linux-3.16.y: [d55a94ed03a24794d47f80d5300825f6c095a0a7]
    
    18
    +  linux-4.4.y: [1c1f15f8ebfbd5042883a1c9ae4b18a6299c9c5f]
    
    19
    +  linux-4.4.y-cip: [1c1f15f8ebfbd5042883a1c9ae4b18a6299c9c5f]
    
    20
    +  linux-4.4.y-cip-rt: [1c1f15f8ebfbd5042883a1c9ae4b18a6299c9c5f]
    
    21
    +  linux-4.9.y: [e747b4ae3b6bca205d82e86366e140cdcbfb7731]
    
    22
    +  mainline: [64b875f7ac8a5d60a4e191479299e931ee949b67]
    
    23
    +fixed-by:
    
    24
    +  linux-4.14.y: [bf71ef9655d25e8b275ec6ed649b6bd719231ddc]
    
    25
    +  linux-4.19.y: [54435b7fff7bfb9515cc457b71c3734c1c3fff76]
    
    26
    +  linux-4.19.y-cip: [54435b7fff7bfb9515cc457b71c3734c1c3fff76]
    
    27
    +  linux-4.4.y: [54562d2b0be5c120b01c8bb94baef1aca37fd329]
    
    28
    +  linux-4.4.y-cip: [54562d2b0be5c120b01c8bb94baef1aca37fd329]
    
    29
    +  linux-4.4.y-cip-rt: [54562d2b0be5c120b01c8bb94baef1aca37fd329]
    
    30
    +  linux-4.9.y: [d8b99303da935228a33fa7656a964adfb33e271b]
    
    31
    +  linux-5.1.y: [49887fc3f2a7e6185777af3a9c96095aeb2bce1b]
    
    32
    +  mainline: [6994eefb0053799d2e07cd140df6c2ea106c41ee]

  • issues/CVE-2019-13631.yml
    1
    +description: 'Input: gtco - bounds check collection indent level'
    
    2
    +references:
    
    3
    +- https://patchwork.kernel.org/patch/11040813/
    
    4
    +- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-13631
    
    5
    +introduced-by:
    
    6
    +  mainline: [a19ceb56cbd1e1beff3e9cf6042e1f31f6487aa6]
    
    7
    +fixed-by:
    
    8
    +  mainline: [2a017fd82c5402b3c8df5e3d6e5165d9e6147dc1]

  • issues/CVE-2019-13648.yml
    1
    +description: 'powerpc/tm: Fix oops on sigreturn on systems without TM'
    
    2
    +references:
    
    3
    +- https://patchwork.ozlabs.org/patch/1133904/
    
    4
    +- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-13648

  • issues/CVE-2019-3846.yml
    ... ... @@ -9,6 +9,9 @@ introduced-by:
    9 9
       mainline: [5e6e3a92b9a4c9416b17f468fa5c7fa2233b8b4e]
    
    10 10
     fixed-by:
    
    11 11
       linux-3.16.y: [a24ac7326f38ffab2b63141496d075da144cec7d]
    
    12
    +  linux-4.14.y: [d50f6b58d7ad30ad8e96c0bbc3e5ecfe9b91ba77]
    
    12 13
       linux-4.19.y: [d4c0f752c1d2c6383cc7582c19b2ed7159d45937]
    
    14
    +  linux-4.4.y: [5d43b417e60ab25984fc7c41175f3ce8cee992bd]
    
    15
    +  linux-4.9.y: [58ec3690a908494f7a7c3e8a302eb491bef9d979]
    
    13 16
       linux-5.1.y: [cb48f5e50582bf44f63599b78941b325a17fa1ec]
    
    14 17
       mainline: [13ec7f10b87f5fc04c4ccbd491c94c7980236a74]


  • Re: Request for guidance: removal of old config files [was: Kernel configurations for 4.19?]

    Pavel Machek
     

    On Sun 2019-07-21 19:58:40, Zoran S wrote:
    Good point. I have not yet tried running 4.19 on the BBB, but I can
    look at adding one - or perhaps Nobuhiro or Pavel already has a
    suitable config?
    Excellent point, which spares me time to begin the new email thread
    about 4.19 BBB rt-config file.

    Actually, I have one 4.19 BBB rt-config file, which at the end of trimming
    goes to cycles (not able to set three parameters).

    git clone git://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git
    cd linux-cip
    *git checkout -b cip_v4.19.13-cip1-rt1-rebase v4.19.13-cip1-rt1-rebase*
    export TREE_NAME=cip-example
    export ARCH=arm
    export CROSS_COMPILE=arm-linux-gnueabihf-
    make -j4 -k -s ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- O=build-arm
    omap2plus_defconfig

    I did adjust all the RT parameters, and at the end of three cycles of
    compiling, I've got the following CONFIG file (attached to this email).

    My problem is, that I ended with cyclic loop, since every time I start
    compiling with:
    make -j4 -k -s ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- O=build-arm

    I end up with changed .config, with always three parameters changed:
    I'm not sure I completely understand your problem. But "/" in
    menuconfig is helpful:

    *** 585,591 ****
    #
    # CONFIG_SUSPEND is not set
    # CONFIG_HIBERNATION is not set
    *! CONFIG_PM=y <<== (should be # CONFIG_PM is not set)*
    CONFIG_PM_DEBUG=y
    # CONFIG_PM_ADVANCED_DEBUG is not set
    # CONFIG_APM_EMULATION is not set
    │ Symbol: PM [=y]
    │ Type : bool
    │ Prompt: Device power management core functionality
    │ Location:
    │ (1) -> Power management options
    │ Defined at kernel/power/Kconfig:144
    │ Selected by [y]:
    │ - ARCH_OMAP2PLUS_TYPICAL [=y] && (ARCH_MULTI_V6 [=y] ||
    ARCH_MULTI_V7 │

    -> you need to disable OMAP2PLUS_TYPICAL.

    --- 2320,2325 ----
    ***************
    *** 5469,5476 ****
    CONFIG_DEBUG_SPINLOCK=y
    CONFIG_DEBUG_MUTEXES=y
    CONFIG_DEBUG_WW_MUTEX_SLOWPATH=y

    *! CONFIG_DEBUG_LOCK_ALLOC=y <<== (should be #
    CONFIG_DEBUG_LOCK_ALLOC is
    │ Symbol: DEBUG_LOCK_ALLOC [=y]
    │ Type : bool
    │ Prompt: Lock debugging: detect incorrect freeing of live locks
    │ Location:
    │ -> Kernel hacking
    │ (1) -> Lock Debugging (spinlocks, mutexes, etc...)
    │ Defined at lib/Kconfig.debug:1163
    │ Depends on: DEBUG_KERNEL [=y] && LOCK_DEBUGGING_SUPPORT [=y]
    │ Selects: DEBUG_SPINLOCK [=y] && DEBUG_MUTEXES [=y] &&
    DEBUG_RT_MUTEXE │
    │ Selected by [y]:
    │ - DEBUG_WW_MUTEX_SLOWPATH [=y] && DEBUG_KERNEL [=y] &&
    LOCK_DEBUGGING │

    You need to disable DEBUG_WW_MUTEX_SLOWPATH AFAICT.


    Pavel
    --
    DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
    HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany


    Re: Explanation for cip-kernel-config

    Pavel Machek
     

    On Sun 2019-07-21 19:56:02, Zoran S wrote:
    I've commited suitable config for socfpga board. (And added it to the
    README).
    For the starters, could you, please, forward to me the public (I
    assume so, somewhere on CIP pages) web pointer of the README file you
    are talking about?
    Here you go. README.md.

    https://gitlab.com/cip-project/cip-kernel/cip-kernel-config

    Best regards,
    Pavel
    --
    DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
    HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany


    Re: Request for guidance: removal of old config files [was: Kernel configurations for 4.19?]

    Zoran
     

    >> Good point.  I have not yet tried running 4.19 on the BBB, but I can
    >> look at adding one - or perhaps Nobuhiro or Pavel already has a
    >> suitable config?

    Excellent point, which spares me time to begin the new email thread
    about 4.19 BBB rt-config file.

    Actually, I have one 4.19 BBB rt-config file, which at the end of trimming
    goes to cycles (not able to set three parameters).

    git clone git://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git
    cd linux-cip
    git checkout -b cip_v4.19.13-cip1-rt1-rebase v4.19.13-cip1-rt1-rebase
    export TREE_NAME=cip-example
    export ARCH=arm
    export CROSS_COMPILE=arm-linux-gnueabihf-
    make -j4 -k -s ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- O=build-arm omap2plus_defconfig

    I did adjust all the RT parameters, and at the end of three cycles of
    compiling, I've got the following CONFIG file (attached to this email).

    My problem is, that I ended with cyclic loop, since every time I start
    compiling with:
    make -j4 -k -s ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- O=build-arm

    I end up with changed .config, with always three parameters changed:

    vagrant@stretch:~/git-repos/linux-cip/build-arm$ diff -c .config CONFIG
    *** .config 2019-07-21 17:31:28.524419156 +0000
    --- CONFIG 2019-07-20 18:29:58.349570260 +0000
    ***************
    *** 73,78 ****
    --- 73,79 ----
      # Timers subsystem
      #
      CONFIG_TICK_ONESHOT=y
    + CONFIG_NO_HZ_COMMON=y
      CONFIG_HZ_PERIODIC=y
      # CONFIG_NO_HZ_IDLE is not set
      # CONFIG_NO_HZ is not set
    ***************
    *** 585,591 ****
      #
      # CONFIG_SUSPEND is not set
      # CONFIG_HIBERNATION is not set
    ! CONFIG_PM=y <<== (should be # CONFIG_PM is not set)
      CONFIG_PM_DEBUG=y
      # CONFIG_PM_ADVANCED_DEBUG is not set
      # CONFIG_APM_EMULATION is not set
    --- 586,592 ----
      #
      # CONFIG_SUSPEND is not set
      # CONFIG_HIBERNATION is not set
    ! # CONFIG_PM is not set
      CONFIG_PM_DEBUG=y
      # CONFIG_PM_ADVANCED_DEBUG is not set
      # CONFIG_APM_EMULATION is not set
    ***************
    *** 2319,2325 ****
      # CONFIG_HSI_CHAR is not set
      CONFIG_PPS=y
      # CONFIG_PPS_DEBUG is not set
    - CONFIG_NTP_PPS=y
     
      #
      # PPS clients support
    --- 2320,2325 ----
    ***************
    *** 5469,5476 ****
      CONFIG_DEBUG_SPINLOCK=y
      CONFIG_DEBUG_MUTEXES=y
      CONFIG_DEBUG_WW_MUTEX_SLOWPATH=y
    ! CONFIG_DEBUG_LOCK_ALLOC=y <<== (should be # CONFIG_DEBUG_LOCK_ALLOC is not set)
    ! CONFIG_LOCKDEP=y<<== (should be # CONFIG_LOCKDEP is not set)

      # CONFIG_DEBUG_LOCKDEP is not set
      CONFIG_DEBUG_ATOMIC_SLEEP=y
      # CONFIG_LOCK_TORTURE_TEST is not set
    --- 5469,5476 ----
      CONFIG_DEBUG_SPINLOCK=y
      CONFIG_DEBUG_MUTEXES=y
      CONFIG_DEBUG_WW_MUTEX_SLOWPATH=y
    ! # CONFIG_DEBUG_LOCK_ALLOC is not set
    ! # CONFIG_LOCKDEP is not set
      # CONFIG_DEBUG_LOCKDEP is not set
      CONFIG_DEBUG_ATOMIC_SLEEP=y
      # CONFIG_LOCK_TORTURE_TEST is not set

    What I am doing/setting wrong here???

    Thank you,
    Zoran
    _______

    On Sun, Jul 21, 2019 at 6:26 PM Pavel Machek <pavel@...> wrote:
    On Fri 2019-07-12 17:34:47, Ben Hutchings wrote:
    > On Thu, 2019-07-11 at 18:51 +0200, Jan Kiszka wrote:
    > [...]
    > > > 4.19/arm/hitachi_omap_defconfig
    > > > 4.19/arm/moxa_mxc_defconfig
    > > > 4.19/arm/siemens_am335x-axm2_defconfig
    > > > 4.19/arm/siemens_am335x-draco_defconfig
    > > > 4.19/arm/siemens_am335x-dxr2_defconfig
    > > > 4.19/arm/siemens_am335x-etamin_defconfig
    > > > 4.19/arm/siemens_am57xx-pxm3_defconfig
    > >
    > > Those can go, I'm not aware of their usage on 4.19. But do we have one for the
    > > am335-x-based BBB, our reference board?
    >
    > Good point.  I have not yet tried running 4.19 on the BBB, but I can
    > look at adding one - or perhaps Nobuhiro or Pavel already has a
    > suitable config?

    No easy access to BBB here, sorry.

    I have added directory 4.19-rt and added config for socfpga I'd like
    to be used for testing in Lava lab. It is not configuration that needs
    to be officially supported with CIP project.

    I hope that is okay.

    If someone uses rt on some other hardware, I'd like to know.

    Best regards,
                                                                    Pavel
    --
    DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
    HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
    _______________________________________________
    cip-dev mailing list
    cip-dev@...
    https://lists.cip-project.org/mailman/listinfo/cip-dev


    Re: Explanation for cip-kernel-config

    Zoran
     

    I've commited suitable config for socfpga board. (And added it to the
    README).
    For the starters, could you, please, forward to me the public (I
    assume so, somewhere on CIP pages) web pointer of the README file you
    are talking about?

    I know that I fell on this list out of nowhere... So I did not follow
    the recent conversations for months. ;-)

    If you need some kind of help with kernel configuration (etc), just
    let me know.
    The email about BBB 4.19-rt .config file woes will come right after
    this one... Indeed! :-)

    Thank you,
    Zoran
    _______


    On Sat, Jul 20, 2019 at 10:24 PM Pavel Machek <pavel@denx.de> wrote:

    Hi!

    Yup... I am very interested in this one, I should say. ;-)

    Let us see what will come out of this effort. :-)
    I've commited suitable config for socfpga board. (And added it to the
    README).

    If you need some kind of help with kernel configuration (etc), just
    let me know.

    Best regards,
    Pavel
    --
    DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
    HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany


    Re: Request for guidance: removal of old config files [was: Kernel configurations for 4.19?]

    Pavel Machek
     

    On Fri 2019-07-12 17:34:47, Ben Hutchings wrote:
    On Thu, 2019-07-11 at 18:51 +0200, Jan Kiszka wrote:
    [...]
    4.19/arm/hitachi_omap_defconfig
    4.19/arm/moxa_mxc_defconfig
    4.19/arm/siemens_am335x-axm2_defconfig
    4.19/arm/siemens_am335x-draco_defconfig
    4.19/arm/siemens_am335x-dxr2_defconfig
    4.19/arm/siemens_am335x-etamin_defconfig
    4.19/arm/siemens_am57xx-pxm3_defconfig
    Those can go, I'm not aware of their usage on 4.19. But do we have one for the
    am335-x-based BBB, our reference board?
    Good point. I have not yet tried running 4.19 on the BBB, but I can
    look at adding one - or perhaps Nobuhiro or Pavel already has a
    suitable config?
    No easy access to BBB here, sorry.

    I have added directory 4.19-rt and added config for socfpga I'd like
    to be used for testing in Lava lab. It is not configuration that needs
    to be officially supported with CIP project.

    I hope that is okay.

    If someone uses rt on some other hardware, I'd like to know.

    Best regards,
    Pavel
    --
    DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
    HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany


    Re: Explanation for cip-kernel-config

    Pavel Machek
     

    Hi!

    Yup... I am very interested in this one, I should say. ;-)

    Let us see what will come out of this effort. :-)
    I've commited suitable config for socfpga board. (And added it to the
    README).

    If you need some kind of help with kernel configuration (etc), just
    let me know.

    Best regards,
    Pavel
    --
    DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
    HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany


    FW: [Linaro/test-definitions] Preempt rt v1 review (#85)

    Chris Paterson
     

    Hello Pavel,

     

    This PR from Daniel is probably of interest to you.

     

    Kind regards, Chris

     

    From: Daniel Wagner <notifications@...>
    Sent: 19 July 2019 23:51
    To: Linaro/test-definitions <test-definitions@...>
    Cc: Subscribed <subscribed@...>
    Subject: [Linaro/test-definitions] Preempt rt v1 review (#85)

     

    I am maintaining the v4.4-rt stable tree and using LAVA with the test-definition to verify my work.

    With a Python script I create several tests jobs. All started very small but nowadays I a pretty happy with what I got. Still a lot to do but it's a good starting point

    Anyway, I improved (obviously it's a point of view thing) the current test scripts in test-definition slightly:

    ·        introduce MAX_LATENCY: fail if the max latency is reached

    ·        added a bunch of command options (e,g. duration)

    ·        extended the error parsing for the test tools

    The first point is important to my work. I really need the test to fail if on a given board the values go above MAX_LATENCY.

    Hope this makes any sense.


    You can view, comment on, or merge this pull request online at:

      https://github.com/Linaro/test-definitions/pull/85

    Commit Summary

    ·        cyclictest: Update parameters

    ·        signaltest: Update parameters

    ·        rt-migrate-test: Parse pass/fail result

    ·        cyclictest: Add MAX_LATENCY argument

    ·        signaltest: Add MAX_LATENCY argument

    ·        pi-stress: Check for errors in the log file

    ·        pmqtest: Add MAX_LATENCY argument

    ·        sh-test-lib: Add convert_to_sec helper

    ·        cyclictest: Introduce duration option

    ·        pi-stress: Introduce duration option

    ·        pmqtest: Introduce duration option

    ·        rt-migrate-test: Introduce duration option

    ·        signaltest: Introduce duration option

    File Changes

    ·        M automated/lib/sh-test-lib (23)

    ·        M automated/linux/cyclictest/cyclictest.sh (26)

    ·        M automated/linux/cyclictest/cyclictest.yaml (15)

    ·        A automated/linux/cyclictest/parse_results.py (54)

    ·        M automated/linux/pi-stress/pi-stress.sh (22)

    ·        M automated/linux/pi-stress/pi-stress.yaml (6)

    ·        A automated/linux/pmqtest/parse_results.py (60)

    ·        M automated/linux/pmqtest/pmqtest.sh (16)

    ·        M automated/linux/pmqtest/pmqtest.yaml (7)

    ·        M automated/linux/rt-migrate-test/rt-migrate-test.sh (9)

    ·        M automated/linux/rt-migrate-test/rt-migrate-test.yaml (3)

    ·        A automated/linux/signaltest/parse_results.py (54)

    ·        M automated/linux/signaltest/signaltest.sh (20)

    ·        M automated/linux/signaltest/signaltest.yaml (10)

    Patch Links:

    ·        https://github.com/Linaro/test-definitions/pull/85.patch

    ·        https://github.com/Linaro/test-definitions/pull/85.diff


    You are receiving this because you are subscribed to this thread.
    Reply to this email directly, view it on GitHub, or mute the thread.


    Re: [OBSOLETE?] CONFIG_PREEMPT_RT_FULL config parameter in 4.19?!

    Daniel Wagner <wagi@...>
     

    On 7/19/19 9:03 PM, Zoran S wrote:
    v4.19.58-cip6
    v4.19.58-cip6-rebase
    There is also a corresponding branch for those tags.

    - linux-4.4.y-cip-rt:
    contains the -rt patchses. no rebases, just merges.
    - linux-4.4.y-cip-rt-rebase:
    has the -rt patches on top of the last cip release.


    Re: [OBSOLETE?] CONFIG_PREEMPT_RT_FULL config parameter in 4.19?!

    Zoran
     

    OK, I see. Wrong check-out!

    git checkout -b cip_v4.19.58-cip6 v4.19.58-cip6

    Yup... This is the root cause of the problem!

    v4.19.13-cip1
    v4.19.13-cip1-rt1
    v4.19.13-cip1-rt1-rebase

    v4.19.13-cip2
    v4.19.13-cip2-rebase
    v4.19.50-cip3
    v4.19.50-cip3-rebase
    v4.19.52-cip4
    v4.19.52-cip4-rebase
    v4.19.56-cip5
    v4.19.56-cip5-rebase
    v4.19.58-cip6
    v4.19.58-cip6-rebase

    Psychological mislead! Well... Blind trust in what I see (and I do see NOT reality, just what I did expect! ;-)

    Well, I need to fix this psychosocial problems with my brain! :-)

    Case Closed!

    Thank you,
    Zoran
    _______


    On Fri, Jul 19, 2019 at 8:11 PM Ben Hutchings <ben.hutchings@...> wrote:
    On Fri, 2019-07-19 at 19:58 +0200, Zoran S wrote:
    > > This never existed in the upstream kernel, only in -rt branches.
    > > It still exists in 4.19-rt.
    >
    > Sure. The following is done by me:
    >
    > git clone git://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git
    >
    > Isn't this CIP RT-kernel real-time tree?
    [...]

    It's the CIP kernel repository.  Only the branches with "-rt" in the
    name include the real-time patch set.

    Ben.

    --
    Ben Hutchings, Software Developer                         Codethink Ltd
    https://www.codethink.co.uk/                 Dale House, 35 Dale Street
                                         Manchester, M1 2HF, United Kingdom


    Re: [OBSOLETE?] CONFIG_PREEMPT_RT_FULL config parameter in 4.19?!

    Ben Hutchings <ben.hutchings@...>
     

    On Fri, 2019-07-19 at 19:58 +0200, Zoran S wrote:
    This never existed in the upstream kernel, only in -rt branches.
    It still exists in 4.19-rt.
    Sure. The following is done by me:

    git clone git://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git

    Isn't this CIP RT-kernel real-time tree?
    [...]

    It's the CIP kernel repository. Only the branches with "-rt" in the
    name include the real-time patch set.

    Ben.

    --
    Ben Hutchings, Software Developer Codethink Ltd
    https://www.codethink.co.uk/ Dale House, 35 Dale Street
    Manchester, M1 2HF, United Kingdom


    Re: Explanation for cip-kernel-config

    Zoran
     

    Yup... I am very interested in this one, I should say. ;-)

    Let us see what will come out of this effort. :-)

    Thank you,
    Zoran Stojsavljevic
    _______

    On Fri, Jul 19, 2019 at 4:05 PM Pavel Machek <pavel@denx.de> wrote:

    Hi!

    I started README.md file in cip-kernel-config. It should provide some
    explanation and I believe we should also provide table with mapping of
    boards (their names and their codes in Lava) and config files.

    Best regards,
    Pavel
    --
    (english) http://www.livejournal.com/~pavelmachek
    (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
    _______________________________________________
    cip-dev mailing list
    cip-dev@lists.cip-project.org
    https://lists.cip-project.org/mailman/listinfo/cip-dev

    5621 - 5640 of 8382