Re: [PATCH 5.10 00/40] 5.10.3-rc1 review

[Jeffrin Jose T]

On Wed, 2021-01-06 at 20:49 +0100, Greg Kroah-Hartman wrote:
> On Thu, Jan 07, 2021 at 01:08:01AM +0530, Jeffrin Jose T wrote:
> > On Mon, 2021-01-04 at 07:21 +0100, Greg Kroah-Hartman wrote:
> > > On Sun, Jan 03, 2021 at 06:37:51PM +0530, Jeffrin Jose T wrote:
> > > > On Mon, 2020-12-28 at 12:41 -0800, Guenter Roeck wrote:
> > > > > On 12/28/20 1:50 AM, Pavel Machek wrote:
> > > > > > Hi!
> > > > > > 
> > > > > > > > > > > > https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.10.3-rc1.gz
> > > > > > > > > > > > or in the git tree and branch at:
> > > > > > > > > > > > git://git.kernel.org/pub/scm/linux/kern
> > > > > > > > > > > > el/g
> > > > > > > > > > > > it/s
> > > > > > > > > > > > table/
> > > > > > > > > > > > linu
> > > > > > > > > > > > x-
> > > > > > > > > > > > stable-rc.git linux-5.10.y
> > > > > > > > > > > > and the diffstat can be found below.
> > > > > > > > > > > > 
> > > > > > > > > > > > thanks,
> > > > > > > > > > > > 
> > > > > > > > > > > > greg k-h
> > > > > > > > > > > 
> > > > > > > > > > > hello ,
> > > > > > > > > > > Compiled and booted 5.10.3-rc1+.
> > > > > > > > > > > 
> > > > > > > > > > > dmesg -l err gives...
> > > > > > > > > > > --x-x--->
> > > > > > > > > > >    43.190922] Bluetooth: hci0: don't support
> > > > > > > > > > > firmware
> > > > > > > > > > > rome
> > > > > > > > > > > 0x31010100
> > > > > > > > > > > --x---x->
> > > > > > > > > > > 
> > > > > > > > > > > My Bluetooth is Off.
> > > > > > > > > > 
> > > > > > > > > > Is this a new warning?  Does it show up on 5.10.2?
> > > > > > > > > > 
> > > > > > > > > > > Tested-by: Jeffrin Jose T <
> > > > > > > > > > > jeff...@rajagiritech.edu.in>
> > > > > > > > > > 
> > > > > > > > > > thanks for testing?
> > > > > > > > > > 
> > > > > > > > > > greg k-h
> > > > > > > > > 
> > > > > > > > > this does not show up in 5.10.2-rc1+
> > > > > > > > 
> > > > > > > > Odd.  Can you run 'git bisect' to find the offending
> > > > > > > > commit?
> > > > > > > > 
> > > > > > > > Does this same error message show up in Linus's git
> > > > > > > > tree?
> > > > > > 
> > > > > > > i will try to do "git bisect" .  i saw this error in
> > > > > > > linus's 
> > > > > > > tree.
> > > > > > 
> > > > > > The bug is in -stable, too, so it is probably easiest to do
> > > > > > bisect
> > > > > > on
> > > > > > -stable tree. IIRC there's less then few hundred commits,
> > > > > > so it
> > > > > > should
> > > > > > be feasible to do bisection by hand if you are not familiar
> > > > > > with
> > > > > > git
> > > > > > bisect.
> > > > > > 
> > > > > 
> > > > > My wild guess would be commit b260e4a68853 ("Bluetooth: Fix
> > > > > slab-
> > > > > out-
> > > > > of-bounds
> > > > > read in hci_le_direct_adv_report_evt()"), but I don't see
> > > > > what
> > > > > might
> > > > > be wrong
> > > > > with it unless some BT device sends a bad report which used
> > > > > to be
> > > > > accepted
> > > > > but is now silently ignored.
> > > > > 
> > > > > Guenter
> > > > > 
> > > > hello,
> > > > 
> > > > Did  "git bisect" in  a typically ok fashion and found that
> > > > 5.9.0
> > > > is
> > > > working for bluetooth related. But 5.10.0-rc1  related is not
> > > > working.
> > > > 
> > > > some related information in bisect.txt  attached.
> > > > 
> > > > -- 
> > > > software engineer
> > > > rajagiri school of engineering and technology - autonomous
> > > > 
> > > 
> > > > $sudo git bisect bad
> > > > Bisecting: 0 revisions left to test after this (roughly 1 step)
> > > > [194810f78402128fe07676646cf9027fd3ed431c] dt-bindings: leds:
> > > > Update devicetree documents for ID_RGB
> > > > 
> > > > $sudo git bisect bad
> > > > Bisecting: 0 revisions left to test after this (roughly 0
> > > > steps)
> > > > [3650b228f83adda7e5ee532e2b90429c03f7b9ec] Linux 5.10-rc1
> > > 
> > > That's really odd, as that commit only has a Makefile change.
> > 
> > i will try to work on it again
> > 
> > > Also, why run this as root?
> > > 
> > there may be some problem in my sudo configurtion or the way in run
> > sudo.\
> > when i run "make modules_install" and "make install" using sudo
> > typical
> > files 
> > ownership changes to root.
> 
> That's fine when installing the kernel, but not when building or
> running
> git, please don't do that.

ok related .

Re: [PATCH 5.10 00/40] 5.10.3-rc1 review

[Jeffrin Jose T]

On Mon, 2021-01-04 at 07:21 +0100, Greg Kroah-Hartman wrote:
> On Sun, Jan 03, 2021 at 06:37:51PM +0530, Jeffrin Jose T wrote:
> > On Mon, 2020-12-28 at 12:41 -0800, Guenter Roeck wrote:
> > > On 12/28/20 1:50 AM, Pavel Machek wrote:
> > > > Hi!
> > > > 
> > > > > > > > > > https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.10.3-rc1.gz
> > > > > > > > > > or in the git tree and branch at:
> > > > > > > > > > git://git.kernel.org/pub/scm/linux/kernel/g
> > > > > > > > > > it/s
> > > > > > > > > > table/
> > > > > > > > > > linu
> > > > > > > > > > x-
> > > > > > > > > > stable-rc.git linux-5.10.y
> > > > > > > > > > and the diffstat can be found below.
> > > > > > > > > > 
> > > > > > > > > > thanks,
> > > > > > > > > > 
> > > > > > > > > > greg k-h
> > > > > > > > > 
> > > > > > > > > hello ,
> > > > > > > > > Compiled and booted 5.10.3-rc1+.
> > > > > > > > > 
> > > > > > > > > dmesg -l err gives...
> > > > > > > > > --x-x--->
> > > > > > > > >    43.190922] Bluetooth: hci0: don't support firmware
> > > > > > > > > rome
> > > > > > > > > 0x31010100
> > > > > > > > > --x---x->
> > > > > > > > > 
> > > > > > > > > My Bluetooth is Off.
> > > > > > > > 
> > > > > > > > Is this a new warning?  Does it show up on 5.10.2?
> > > > > > > > 
> > > > > > > > > Tested-by: Jeffrin Jose T <
> > > > > > > > > jeff...@rajagiritech.edu.in>
> > > > > > > > 
> > > > > > > > thanks for testing?
> > > > > > > > 
> > > > > > > > greg k-h
> > > > > > > 
> > > > > > > this does not show up in 5.10.2-rc1+
> > > > > > 
> > > > > > Odd.  Can you run 'git bisect' to find the offending
> > > > > > commit?
> > > > > > 
> > > > > > Does this same error message show up in Linus's git tree?
> > > > 
> > > > > i will try to do "git bisect" .  i saw this error in linus's 
> > > > > tree.
> > > > 
> > > > The bug is in -stable, too, so it is probably easiest to do
> > > > bisect
> > > > on
> > > > -stable tree. IIRC there's less then few hundred commits, so it
> > > > should
> > > > be feasible to do bisection by hand if you are not familiar
> > > > with
> > > > git
> > > > bisect.
> > > > 
> > > 
> > > My wild guess would be commit b260e4a68853 ("Bluetooth: Fix slab-
> > > out-
> > > of-bounds
> > > read in hci_le_direct_adv_report_evt()"), but I don't see what
> > > might
> > > be wrong
> > > with it unless some BT device sends a bad report which used to be
> > > accepted
> > > but is now silently ignored.
> > > 
> > > Guenter
> > > 
> > hello,
> > 
> > Did  "git bisect" in  a typically ok fashion and found that 5.9.0
> > is
> > working for bluetooth related. But 5.10.0-rc1  related is not
> > working.
> > 
> > some related information in bisect.txt  attached.
> > 
> > -- 
> > software engineer
> > rajagiri school of engineering and technology - autonomous
> > 
> 
> > $sudo git bisect bad
> > Bisecting: 0 revisions left to test after this (roughly 1 step)
> > [194810f78402128fe07676646cf9027fd3ed431c] dt-bindings: leds:
> > Update devicetree documents for ID_RGB
> > 
> > $sudo git bisect bad
> > Bisecting: 0 revisions left to test after this (roughly 0 steps)
> > [3650b228f83adda7e5ee532e2b90429c03f7b9ec] Linux 5.10-rc1
> 
> That's really odd, as that commit only has a Makefile change.

i will try to work on it again

> Also, why run this as root?
> 
there may be some problem in my sudo configurtion or the way in run
sudo.\
when i run "make modules_install" and "make install" using sudo typical
files 
ownership changes to root.

-- 
software engineer
rajagiri school of engineering and technology - autonomous

Re: [PATCH 5.10 00/63] 5.10.5-rc1 review

[Jeffrin Jose T]

On Tue, 2021-01-05 at 14:05 +0100, Greg Kroah-Hartman wrote:
> On Tue, Jan 05, 2021 at 06:25:14PM +0530, Jeffrin Jose T wrote:
> > On Mon, 2021-01-04 at 16:56 +0100, Greg Kroah-Hartman wrote:
> > > This is the start of the stable review cycle for the 5.10.5
> > > release.
> > > There are 63 patches in this series, all will be posted as a
> > > response
> > > to this one.  If anyone has any issues with these being applied,
> > > please
> > > let me know.
> > > 
> > > Responses should be made by Wed, 06 Jan 2021 15:56:52 +.
> > > Anything received after that time might be too late.
> > > 
> > > The whole patch series can be found in one patch at:
> > > 
> > > https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.10.5-rc1.gz
> > > or in the git tree and branch at:
> > > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linu
> > > x-
> > > stable-rc.git linux-5.10.y
> > > and the diffstat can be found below.
> > > 
> > > thanks,
> > > 
> > > greg k-h
> > 
> > hello,
> > 
> > Compiled  and  booted  5.10.5-rc1+ . dmesg  related shows 
> > no new errors  and  may be no major warning. 
> > 
> > Having said that, "dmesg -l warn"  show  a BUG related stuff.
> > 
> > warning-5.10.5-rc1+.txt file is attached.
> 
> Is this new?  If so, can you bisect it?
> 
> thanks,
> 
> greg k-h

hello,
it seems to be new and i will  try to bisect it.

-- 
software engineer
rajagiri school of engineering and technology - autonomous

Re: [PATCH 5.10 00/63] 5.10.5-rc1 review

[Jeffrin Jose T]

On Mon, 2021-01-04 at 16:56 +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.10.5 release.
> There are 63 patches in this series, all will be posted as a response
> to this one.  If anyone has any issues with these being applied,
> please
> let me know.
> 
> Responses should be made by Wed, 06 Jan 2021 15:56:52 +.
> Anything received after that time might be too late.
> 
> The whole patch series can be found in one patch at:
> 
> https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.10.5-rc1.gz
> or in the git tree and branch at:
> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-
> stable-rc.git linux-5.10.y
> and the diffstat can be found below.
> 
> thanks,
> 
> greg k-h

hello,

Compiled  and  booted  5.10.5-rc1+ . dmesg  related shows 
no new errors  and  may be no major warning. 

Having said that, "dmesg -l warn"  show  a BUG related stuff.

warning-5.10.5-rc1+.txt file is attached.

Tested-by: Jeffrin Jose T 

-- 
software engineer
rajagiri school of engineering and technology - autonomous


[0.819083] Lock dependency validator: Copyright (c) 2006 Red Hat, Inc., 
Ingo Molnar
[0.819088] ... MAX_LOCKDEP_SUBCLASSES:  8
[0.819092] ... MAX_LOCK_DEPTH:  48
[0.819097] ... MAX_LOCKDEP_KEYS:8192
[0.819101] ... CLASSHASH_SIZE:  4096
[0.819105] ... MAX_LOCKDEP_ENTRIES: 32768
[0.819109] ... MAX_LOCKDEP_CHAINS:  65536
[0.819114] ... CHAINHASH_SIZE:  32768
[0.819118]  memory used by lock dependency info: 6365 kB
[0.819123]  memory used for stack traces: 4224 kB
[0.819127]  per task-struct memory footprint: 1920 bytes
[0.983486] MDS CPU bug present and SMT on, data leak possible. See 
https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html for more 
details.
[0.985392]  #3
[1.166946] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'

[4.367570] =
[4.367582] [ BUG: Invalid wait context ]
[4.367596] 5.10.5-rc1+ #12 Not tainted
[4.367608] -
[4.367621] ksoftirqd/3/26 is trying to lock:
[4.367635] 88810005c918 (>list_lock){-...}-{3:3}, at: 
unfreeze_partials+0x6d/0x1f0
[4.367671] other info that might help us debug this:
[4.367684] context-{2:2}
[4.367695] 1 lock held by ksoftirqd/3/26:
[4.367707]  #0: ab991160 (rcu_callback){}-{0:0}, at: 
rcu_core+0x340/0x8c0
[4.367742] stack backtrace:
[4.367755] CPU: 3 PID: 26 Comm: ksoftirqd/3 Not tainted 5.10.5-rc1+ #12
[4.367773] Hardware name: ASUSTeK COMPUTER INC. VivoBook 15_ASUS Laptop 
X507UAR/X507UAR, BIOS X507UAR.203 05/31/2018
[4.367794] Call Trace:
[4.367805]  
[4.367820]  dump_stack+0xae/0xe5
[4.367835]  __lock_acquire.cold+0x204/0x34c
[4.367856]  ? __lock_acquire+0x870/0x2d40
[4.367872]  ? lockdep_hardirqs_on_prepare+0x220/0x220
[4.367889]  ? lockdep_enabled+0x39/0x50
[4.367906]  lock_acquire+0x236/0x510
[4.367922]  ? unfreeze_partials+0x6d/0x1f0
[4.367938]  ? lock_release+0x410/0x410
[4.367954]  ? free_unref_page_commit+0x129/0x1b0
[4.367976]  _raw_spin_lock+0x2c/0x40
[4.367991]  ? unfreeze_partials+0x6d/0x1f0
[4.368006]  unfreeze_partials+0x6d/0x1f0
[4.368023]  ? nohz_balance_exit_idle+0x2c/0x250
[4.368043]  flush_smp_call_function_queue+0xf4/0x2c0
[4.368059]  ? slub_cpu_dead+0xf0/0xf0
[4.368076]  __sysvec_call_function+0x71/0x250
[4.368093]  asm_call_irq_on_stack+0x12/0x20
[4.368106]  
[4.368119]  sysvec_call_function+0x84/0xa0
[4.368135]  asm_sysvec_call_function+0x12/0x20
[4.368152] RIP: 0010:__orc_find+0x6e/0xc0
[4.368168] Code: 37 4c 89 e8 4c 29 f8 48 89 c1 48 c1 e8 3f 48 c1 f9 02 48 
01 c8 48 d1 f8 4d 8d 34 87 4c 89 f7 e8 28 ab 3b 00 49 63 06 4c 01 f0 <48> 39 c3 
73 c6 4d 8d 6e fc 4d 39 fd 73 c9 4c 29 e5 48 8b 34 24 48
[4.368204] RSP: :c923f808 EFLAGS: 0283
[4.368222] RAX: a9c0523d RBX: a9c05251 RCX: dc00
[4.368241] RDX: 0003 RSI: ac038784 RDI: abe63b98
[4.368259] RBP: abe63b90 R08: a9c9e4d8 R09: ac06fef1
[4.368277] R10: fbfff580dfde R11: 0001 R12: abe63b68
[4.368296] R13: abe63b9c R14: abe63b98 R15: abe63b94
[4.368333]  ? ret_from_fork+0x21/0x30
[4.368348]  ? __orc_find+0x68/0xc0
[4.368362]  ? ret_from_fork+0xd/0x30
[4.368380]  ? __orc_find+0x68/0xc0
[4.368396]  unwind_next_frame+0x11d/0xa60
[4.368412]  ? ret_from_fork+0x22/0x30
[4.368427]  ? ret_from_fork+0x22/0x30
[4.368441]  ? ret_from_fork+0x22/0x30
[4.368456]  ? deref_stack_reg+0xb0/0xb0
[4.368473]  ? __unwind_start+0x2ed/0x370
[4.368488]  ? create_prof_cpu_mask+0x20/0x20
[4.368505]  arch_stack_walk+0x88/0

Re: [PATCH 5.10 00/40] 5.10.3-rc1 review

[Jeffrin Jose T]

On Mon, 2020-12-28 at 12:41 -0800, Guenter Roeck wrote:
> On 12/28/20 1:50 AM, Pavel Machek wrote:
> > Hi!
> > 
> > > > > > > > https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.10.3-rc1.gz
> > > > > > > > or in the git tree and branch at:
> > > > > > > > git://git.kernel.org/pub/scm/linux/kernel/git/s
> > > > > > > > table/
> > > > > > > > linu
> > > > > > > > x-
> > > > > > > > stable-rc.git linux-5.10.y
> > > > > > > > and the diffstat can be found below.
> > > > > > > > 
> > > > > > > > thanks,
> > > > > > > > 
> > > > > > > > greg k-h
> > > > > > > 
> > > > > > > hello ,
> > > > > > > Compiled and booted 5.10.3-rc1+.
> > > > > > > 
> > > > > > > dmesg -l err gives...
> > > > > > > --x-x--->
> > > > > > >    43.190922] Bluetooth: hci0: don't support firmware
> > > > > > > rome
> > > > > > > 0x31010100
> > > > > > > --x---x->
> > > > > > > 
> > > > > > > My Bluetooth is Off.
> > > > > > 
> > > > > > Is this a new warning?  Does it show up on 5.10.2?
> > > > > > 
> > > > > > > Tested-by: Jeffrin Jose T 
> > > > > > 
> > > > > > thanks for testing?
> > > > > > 
> > > > > > greg k-h
> > > > > 
> > > > > this does not show up in 5.10.2-rc1+
> > > > 
> > > > Odd.  Can you run 'git bisect' to find the offending commit?
> > > > 
> > > > Does this same error message show up in Linus's git tree?
> > 
> > > i will try to do "git bisect" .  i saw this error in linus's 
> > > tree.
> > 
> > The bug is in -stable, too, so it is probably easiest to do bisect
> > on
> > -stable tree. IIRC there's less then few hundred commits, so it
> > should
> > be feasible to do bisection by hand if you are not familiar with
> > git
> > bisect.
> > 
> 
> My wild guess would be commit b260e4a68853 ("Bluetooth: Fix slab-out-
> of-bounds
> read in hci_le_direct_adv_report_evt()"), but I don't see what might
> be wrong
> with it unless some BT device sends a bad report which used to be
> accepted
> but is now silently ignored.
> 
> Guenter
> 
hello,

Did  "git bisect" in  a typically ok fashion and found that 5.9.0 is
working for bluetooth related. But 5.10.0-rc1  related is not working.

some related information in bisect.txt  attached.

-- 
software engineer
rajagiri school of engineering and technology - autonomous

$sudo git bisect bad
Bisecting: 0 revisions left to test after this (roughly 1 step)
[194810f78402128fe07676646cf9027fd3ed431c] dt-bindings: leds: Update devicetree 
documents for ID_RGB

$sudo git bisect bad
Bisecting: 0 revisions left to test after this (roughly 0 steps)
[3650b228f83adda7e5ee532e2b90429c03f7b9ec] Linux 5.10-rc1

Re: [PATCH 5.10 00/40] 5.10.3-rc1 review

[Jeffrin Jose T]

On Sun, 2020-12-27 at 17:05 +0100, Greg Kroah-Hartman wrote:
> On Sun, Dec 27, 2020 at 09:20:07PM +0530, Jeffrin Jose T wrote:
> > On Sat, 2020-12-26 at 16:06 +0100, Greg Kroah-Hartman wrote:
> > > On Thu, Dec 24, 2020 at 03:13:38PM +0530, Jeffrin Jose T wrote:
> > > > On Wed, 2020-12-23 at 16:33 +0100, Greg Kroah-Hartman wrote:
> > > > > This is the start of the stable review cycle for the 5.10.3
> > > > > release.
> > > > > There are 40 patches in this series, all will be posted as a
> > > > > response
> > > > > to this one.  If anyone has any issues with these being
> > > > > applied,
> > > > > please
> > > > > let me know.
> > > > > 
> > > > > Responses should be made by Fri, 25 Dec 2020 15:05:02 +.
> > > > > Anything received after that time might be too late.
> > > > > 
> > > > > The whole patch series can be found in one patch at:
> > > > > 
> > > > > https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.10.3-rc1.gz
> > > > > or in the git tree and branch at:
> > > > > git://git.kernel.org/pub/scm/linux/kernel/git/stable/
> > > > > linu
> > > > > x-
> > > > > stable-rc.git linux-5.10.y
> > > > > and the diffstat can be found below.
> > > > > 
> > > > > thanks,
> > > > > 
> > > > > greg k-h
> > > > 
> > > > hello ,
> > > > Compiled and booted 5.10.3-rc1+.
> > > > 
> > > > dmesg -l err gives...
> > > > --x-x--->
> > > >    43.190922] Bluetooth: hci0: don't support firmware rome
> > > > 0x31010100
> > > > --x---x->
> > > > 
> > > > My Bluetooth is Off.
> > > 
> > > Is this a new warning?  Does it show up on 5.10.2?
> > > 
> > > > Tested-by: Jeffrin Jose T 
> > > 
> > > thanks for testing?
> > > 
> > > greg k-h
> > 
> > this does not show up in 5.10.2-rc1+
> 
> Odd.  Can you run 'git bisect' to find the offending commit?
> 
> Does this same error message show up in Linus's git tree?
> 
> thanks,
> 
> greg k-h

i will try to do "git bisect" .  i saw this error in linus's  tree.

-- 
software engineer
rajagiri school of engineering and technology - autonomous

Re: [PATCH 5.10 00/40] 5.10.3-rc1 review

[Jeffrin Jose T]

On Sat, 2020-12-26 at 16:06 +0100, Greg Kroah-Hartman wrote:
> On Thu, Dec 24, 2020 at 03:13:38PM +0530, Jeffrin Jose T wrote:
> > On Wed, 2020-12-23 at 16:33 +0100, Greg Kroah-Hartman wrote:
> > > This is the start of the stable review cycle for the 5.10.3
> > > release.
> > > There are 40 patches in this series, all will be posted as a
> > > response
> > > to this one.  If anyone has any issues with these being applied,
> > > please
> > > let me know.
> > > 
> > > Responses should be made by Fri, 25 Dec 2020 15:05:02 +.
> > > Anything received after that time might be too late.
> > > 
> > > The whole patch series can be found in one patch at:
> > > 
> > > https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.10.3-rc1.gz
> > > or in the git tree and branch at:
> > > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linu
> > > x-
> > > stable-rc.git linux-5.10.y
> > > and the diffstat can be found below.
> > > 
> > > thanks,
> > > 
> > > greg k-h
> > 
> > hello ,
> > Compiled and booted 5.10.3-rc1+.
> > 
> > dmesg -l err gives...
> > --x-x------->
> >    43.190922] Bluetooth: hci0: don't support firmware rome
> > 0x31010100
> > --x---x->
> > 
> > My Bluetooth is Off.
> 
> Is this a new warning?  Does it show up on 5.10.2?
> 
> > Tested-by: Jeffrin Jose T 
> 
> thanks for testing?
> 
> greg k-h

this does not show up in 5.10.2-rc1+

-- 
software engineer
rajagiri school of engineering and technology - autonomous

Re: [PATCH 5.10 00/40] 5.10.3-rc1 review

[Jeffrin Jose T]

On Wed, 2020-12-23 at 16:33 +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.10.3 release.
> There are 40 patches in this series, all will be posted as a response
> to this one.  If anyone has any issues with these being applied,
> please
> let me know.
> 
> Responses should be made by Fri, 25 Dec 2020 15:05:02 +.
> Anything received after that time might be too late.
> 
> The whole patch series can be found in one patch at:
> 
> https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.10.3-rc1.gz
> or in the git tree and branch at:
> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-
> stable-rc.git linux-5.10.y
> and the diffstat can be found below.
> 
> thanks,
> 
> greg k-h

hello ,
Compiled and booted 5.10.3-rc1+.

dmesg -l err gives...
--x-x--->
   43.190922] Bluetooth: hci0: don't support firmware rome 0x31010100
--x-------x----->

My Bluetooth is Off.


Tested-by: Jeffrin Jose T 
-- 
software engineer
rajagiri school of engineering and technology - autonomous

Re: [PATCH 5.10 00/16] 5.10.2-rc1 review

[Jeffrin Jose T]

On Sat, 2020-12-19 at 13:57 +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.10.2 release.
> There are 16 patches in this series, all will be posted as a response
> to this one.  If anyone has any issues with these being applied,
> please
> let me know.
> 
> Responses should be made by Mon, 21 Dec 2020 12:53:29 +.
> Anything received after that time might be too late.
> 
> The whole patch series can be found in one patch at:
> 
> https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.10.2-rc1.gz
> or in the git tree and branch at:
> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-
> stable-rc.git linux-5.10.y
> and the diffstat can be found below.
> 
> thanks,
> 
> greg k-h
> 
hello,

Compiled and booted  5.10.2-rc1+. No typical dmesg regression or
regressions

Tested-by: Jeffrin Jose T 


-- 
software engineer
rajagiri school of engineering and technology - autonomous

Re: related to fixing depreciated api

[Jeffrin Jose T]

On Tue, 2020-12-15 at 12:52 -0700, Shuah Khan wrote:
> On 12/15/20 9:12 AM, Shuah Khan wrote:
> > On 12/14/20 9:42 AM, Jeffrin Jose T wrote:
> > > hello,
> > > 
> > > i have worked on to  fix  depreciated api issue from
> > > tools/testing/selftests/intel_pstate/aerf.c
> > > 
> > > i met with the following error related...
> > > 
> > > --x--x->
> > > $pwd
> > > /home/jeffrin/UP/linux-
> > > kselftest/tools/testing/selftests/intel_pstate
> > > $make
> > > gcc  -Wall -D_GNU_SOURCE    aperf.c /home/jeffrin/UP/linux-
> > > kselftest/tools/testing/selftests/kselftest_harness.h
> > > /home/jeffrin/UP/linux-
> > > kselftest/tools/testing/selftests/kselftest.h -
> > > lm -o /home/jeffrin/UP/linux-
> > > kselftest/tools/testing/selftests/intel_pstate/aperf
> > > aperf.c: In function ‘main’:
> > > aperf.c:58:2: warning: ‘ftime’ is deprecated [-Wdeprecated-
> > > declarations]
> > >     58 |  ftime();
> > >    |  ^
> > > In file included from aperf.c:9:
> > > /usr/include/x86_64-linux-gnu/sys/timeb.h:39:12: note: declared
> > > here
> > >     39 | extern int ftime (struct timeb *__timebuf)
> > >    |    ^
> > > aperf.c:67:2: warning: ‘ftime’ is deprecated [-Wdeprecated-
> > > declarations]
> > >     67 |  ftime();
> > >    |  ^
> > > In file included from aperf.c:9:
> > > /usr/include/x86_64-linux-gnu/sys/timeb.h:39:12: note: declared
> > > here
> > >     39 | extern int ftime (struct timeb *__timebuf)
> > >    |    ^
> > > $
> > > x---x-->
> > > 
> > > 
> > > from ftime manual  i found that it is depreciated...
> > > 
> > > This  function is deprecated, and will be removed in a future
> > > version
> > > of the GNU C library.  Use clock_gettime(2) instead.
> > > 
> > > 
> > > now clock_gettime  gives  new data structure.
> > > 
> > >   struct timespec {
> > >     time_t   tv_sec;    /* seconds */
> > >     long tv_nsec;   /* nanoseconds */
> > >     };
> > > 
> > > 
> > > i worked on with the new data structure and some errors that came
> > > along.
> > > typical final output looks good but  values of runtime and
> > > typical
> > > frequency
> > > does not look normal during "sudo bash run.sh".
> > > 
> > > output of "git diff" and  a  portion of output of   "sudo bash
> > > run.sh".
> > > is attached.
> > > 
> > 
> > Please send a proper patch to fix intel_pstate to use
> > clock_gettime.
> > 
> 
> The fix for this is already in next - no need to send patch.
> 
> thanks,
> -- Shuah
> 
anyway thanks .


-- 
software engineer
rajagiri school of engineering and technology - autonomous

Re: [PATCH 5.9 000/105] 5.9.15-rc1 review

[Jeffrin Jose T]

On Mon, 2020-12-14 at 18:27 +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.9.15 release.
> There are 105 patches in this series, all will be posted as a
> response
> to this one.  If anyone has any issues with these being applied,
> please
> let me know.
> 
> Responses should be made by Wed, 16 Dec 2020 17:25:32 +.
> Anything received after that time might be too late.
> 
> The whole patch series can be found in one patch at:
> 
> https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.9.15-rc1.gz
> or in the git tree and branch at:
> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-
> stable-rc.git linux-5.9.y
> and the diffstat can be found below.
> 
> thanks,
> 
> greg k-h
hello,
 
Compiled and booted  5.9.15-rc1+ . No typical dmesg regression or
regressions

Tested-by: Jeffrin Jose T 

-- 
software engineer
rajagiri school of engineering and technology - autonomous

related to fixing depreciated api

[Jeffrin Jose T]

hello,

i have worked on to  fix  depreciated api issue from
tools/testing/selftests/intel_pstate/aerf.c

i met with the following error related...

--x--x->
$pwd
/home/jeffrin/UP/linux-kselftest/tools/testing/selftests/intel_pstate
$make
gcc  -Wall -D_GNU_SOURCEaperf.c /home/jeffrin/UP/linux-
kselftest/tools/testing/selftests/kselftest_harness.h
/home/jeffrin/UP/linux-kselftest/tools/testing/selftests/kselftest.h -
lm -o /home/jeffrin/UP/linux-
kselftest/tools/testing/selftests/intel_pstate/aperf
aperf.c: In function ‘main’:
aperf.c:58:2: warning: ‘ftime’ is deprecated [-Wdeprecated-
declarations]
   58 |  ftime();
  |  ^
In file included from aperf.c:9:
/usr/include/x86_64-linux-gnu/sys/timeb.h:39:12: note: declared here
   39 | extern int ftime (struct timeb *__timebuf)
  |^
aperf.c:67:2: warning: ‘ftime’ is deprecated [-Wdeprecated-
declarations]
   67 |  ftime();
  |  ^
In file included from aperf.c:9:
/usr/include/x86_64-linux-gnu/sys/timeb.h:39:12: note: declared here
   39 | extern int ftime (struct timeb *__timebuf)
  |^
$
x---x-->


from ftime manual  i found that it is depreciated...

This  function is deprecated, and will be removed in a future version
of the GNU C library.  Use clock_gettime(2) instead.


now clock_gettime  gives  new data structure.

 struct timespec {
   time_t   tv_sec;/* seconds */
   long tv_nsec;   /* nanoseconds */
   };


i worked on with the new data structure and some errors that came
along.
typical final output looks good but  values of runtime and typical
frequency
does not look normal during "sudo bash run.sh".

output of "git diff" and  a  portion of output of   "sudo bash run.sh".
is attached.



-- 
software engineer
rajagiri school of engineering and technology - autonomous


diff --git a/tools/testing/selftests/intel_pstate/aperf.c 
b/tools/testing/selftests/intel_pstate/aperf.c
index f6cd03a87493..7e35e7872f16 100644
--- a/tools/testing/selftests/intel_pstate/aperf.c
+++ b/tools/testing/selftests/intel_pstate/aperf.c
@@ -6,7 +6,7 @@
 #include 
 #include 
 #include 
-#include 
+#include 
 #include 
 #include 
 #include 
@@ -22,10 +22,12 @@ int main(int argc, char **argv) {
long long tsc, old_tsc, new_tsc;
long long aperf, old_aperf, new_aperf;
long long mperf, old_mperf, new_mperf;
-   struct timeb before, after;
+   struct timespec before, after;
+clockid_t clkid;
long long int start, finish, total;
cpu_set_t cpuset;
 
+
if (argc != 2) {
usage(argv[0]);
return 1;
@@ -41,6 +43,10 @@ int main(int argc, char **argv) {
 
sprintf(msr_file_name, "/dev/cpu/%d/msr", cpu);
fd = open(msr_file_name, O_RDONLY);
+#define CLOCKFD 3
+#define FD_TO_CLOCKID(fd)   ((~(clockid_t) (fd) << 3) | CLOCKFD)
+clkid = FD_TO_CLOCKID(fd);
+
 
if (fd == -1) {
printf("/dev/cpu/%d/msr: %s\n", cpu, strerror(errno));
@@ -55,7 +61,7 @@ int main(int argc, char **argv) {
return 1;
}
 
-   ftime();
+   clock_gettime(clkid,);
pread(fd, _tsc,  sizeof(old_tsc), 0x10);
pread(fd, _aperf,  sizeof(old_mperf), 0xe7);
pread(fd, _mperf,  sizeof(old_aperf), 0xe8);
@@ -64,7 +70,7 @@ int main(int argc, char **argv) {
sqrt(i);
}
 
-   ftime();
+   clock_gettime(clkid,);
pread(fd, _tsc,  sizeof(new_tsc), 0x10);
pread(fd, _aperf,  sizeof(new_mperf), 0xe7);
pread(fd, _mperf,  sizeof(new_aperf), 0xe8);
@@ -73,11 +79,10 @@ int main(int argc, char **argv) {
aperf = new_aperf-old_aperf;
mperf = new_mperf-old_mperf;
 
-   start = before.time*1000 + before.millitm;
-   finish = after.time*1000 + after.millitm;
-   total = finish - start;
-
-   printf("runTime: %4.2f\n", 1.0*total/1000);
-   printf("freq: %7.0f\n", tsc / (1.0*aperf / (1.0 * mperf)) / total);
+   start = before.tv_sec*100 + before.tv_nsec;
+   finish = after.tv_sec*100 + after.tv_nsec;
+   total = finish - start; 
+   printf("runTime: %4.2f\n", 1.0*total/100); 
+   printf("freq: %7.0f\n", tsc / (1.0 * aperf /1.0 * (mperf)) / total);
return 0;
 }
Setting maximum frequency to 500
launching aperf load on 0
launching aperf load on 1
launching aperf load on 2
launching aperf load on 3
sleeping for 5 seconds
waiting for job id 7521
runTime: 0.00
freq: inf
runTime: 0.00
freq: inf
runTime: 0.00
freq: inf
runTime: 0.00
freq: inf
waiting for job id 7522
waiting for job id 7523
waiting for job id 7524
Setting maximum frequency to 400
launching aperf load on 0
launching aperf load on 1
launching aperf load on 2
launching aperf load on 3
sleeping for 5 seconds
waiting for job id 7540
runTime: 0.00
freq: inf

Re: [PATCH 5.9 00/75] 5.9.14-rc1 review

[Jeffrin Jose T]

On Thu, 2020-12-10 at 15:26 +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.9.14 release.
> There are 75 patches in this series, all will be posted as a response
> to this one.  If anyone has any issues with these being applied,
> please
> let me know.
> 
> Responses should be made by Sat, 12 Dec 2020 14:25:47 +.
> Anything received after that time might be too late.
> 
> The whole patch series can be found in one patch at:
> 
> https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.9.14-rc1.gz
> or in the git tree and branch at:
> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-
> stable-rc.git linux-5.9.y
> and the diffstat can be found below.
> 
> thanks,
> 
> greg k-h
> 
hello,

Compiled and  booted 5.9.14-rc1+. No typical dmesg regression or
regressions.

Tested-by: Jeffrin Jose T 


-- 
software engineer
rajagiri school of engineering and technology - autonomous

Fwd: [PROBLEM] kmemleak: 2 new suspected memory leaks

[Jeffrin Jose T]

--- Begin Message ---
hello,


kmemleaks  found. see related information below...

x--x>
cat /sys/kernel/debug/kmemleak 
unreferenced object 0x8881105d2348 (size 8):
  comm "kunit_try_catch", pid 139, jiffies 4294898877 (age 6055.628s)
  hex dump (first 8 bytes):
74 65 73 74 69 6e 67 00  testing.
  backtrace:
[<1d6f9546>] kmemdup+0x23/0x50
[<7157804e>] unpack_strdup+0xc7/0x140
[<0fcb0a94>]
policy_unpack_test_unpack_strdup_with_null_name+0xd0/0x350
[<43df290a>] kunit_try_run_case+0xa6/0x150
[<c069ee6a>] kunit_generic_run_threadfn_adapter+0x2e/0x50
[<929a25ad>] kthread+0x232/0x260
[<e5de2862>] ret_from_fork+0x22/0x30
unreferenced object 0x8881105d2bb8 (size 8):
  comm "kunit_try_catch", pid 140, jiffies 4294898878 (age 6055.624s)
  hex dump (first 8 bytes):
74 65 73 74 69 6e 67 00  testing.
  backtrace:
[<1d6f9546>] kmemdup+0x23/0x50
[<7157804e>] unpack_strdup+0xc7/0x140
[<ba70df5f>]
policy_unpack_test_unpack_strdup_with_name+0xc3/0x340
[<43df290a>] kunit_try_run_case+0xa6/0x150
[<c069ee6a>] kunit_generic_run_threadfn_adapter+0x2e/0x50
[<929a25ad>] kthread+0x232/0x260
[<e5de2862>] ret_from_fork+0x22/0x30
x--x--->

Reported-by: Jeffrin Jose T 

-- 
software engineer
rajagiri school of engineering and technology - autonomous

--- End Message ---

[PROBLEM] kmemleak: 2 new suspected memory leaks

[Jeffrin Jose T]

hello,


kmemleaks  found. see related information below...

x--x>
cat /sys/kernel/debug/kmemleak 
unreferenced object 0x8881105d2348 (size 8):
  comm "kunit_try_catch", pid 139, jiffies 4294898877 (age 6055.628s)
  hex dump (first 8 bytes):
74 65 73 74 69 6e 67 00  testing.
  backtrace:
[<1d6f9546>] kmemdup+0x23/0x50
[<7157804e>] unpack_strdup+0xc7/0x140
[<0fcb0a94>]
policy_unpack_test_unpack_strdup_with_null_name+0xd0/0x350
[<43df290a>] kunit_try_run_case+0xa6/0x150
[<c069ee6a>] kunit_generic_run_threadfn_adapter+0x2e/0x50
[<929a25ad>] kthread+0x232/0x260
[<e5de2862>] ret_from_fork+0x22/0x30
unreferenced object 0x8881105d2bb8 (size 8):
  comm "kunit_try_catch", pid 140, jiffies 4294898878 (age 6055.624s)
  hex dump (first 8 bytes):
74 65 73 74 69 6e 67 00  testing.
  backtrace:
[<1d6f9546>] kmemdup+0x23/0x50
[<7157804e>] unpack_strdup+0xc7/0x140
[<ba70df5f>]
policy_unpack_test_unpack_strdup_with_name+0xc3/0x340
[<43df290a>] kunit_try_run_case+0xa6/0x150
[<c069ee6a>] kunit_generic_run_threadfn_adapter+0x2e/0x50
[<929a25ad>] kthread+0x232/0x260
[<e5de2862>] ret_from_fork+0x22/0x30
x--x--->

Reported-by: Jeffrin Jose T 

-- 
software engineer
rajagiri school of engineering and technology - autonomous

Re: [PATCH 5.9 00/46] 5.9.13-rc1 review

[Jeffrin Jose T]

On Sun, 2020-12-06 at 12:17 +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.9.13 release.
> There are 46 patches in this series, all will be posted as a response
> to this one.  If anyone has any issues with these being applied,
> please
> let me know.
> 
> Responses should be made by Tue, 08 Dec 2020 11:15:42 +.
> Anything received after that time might be too late.
> 
> The whole patch series can be found in one patch at:
> 
> https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.9.13-rc1.gz
> or in the git tree and branch at:
> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-
> stable-rc.git linux-5.9.yo
> and the diffstat can be found below.
> 
> thanks,
> 5.9.13
> greg k-h
hello,

Compiled and booted 5.9.13-rc1+. No typical regression or regressions.

Tested-by: Jeffrin Jose T 

-- 
software engineer
rajagiri school of engineering and technology - autonomous

Re: BUG: KASAN lib/test_kasan.c

[Jeffrin Jose T]

On Fri, 2020-12-04 at 21:29 +0100, Marco Elver wrote:
> On Fri, 4 Dec 2020 at 19:56, Jeffrin Jose T
>  wrote:
> > hello,
> > 
> >  detected   KASAN   BUG
> > 
> > [ related information ]
> > 
> > ---x---x>
> > [   43.616259] BUG: KASAN: vmalloc-out-of-bounds in
> > vmalloc_oob+0x146/0x2c0
> > 
> > (gdb) l *vmalloc_oob+0x146/0x2c0
> > 0x81b8b0b0 is in vmalloc_oob (lib/test_kasan.c:764).
> 
> This is the KASAN test. It's a feature, not a bug. ;-)
> 
> > 759 kfree_sensitive(ptr);
> > 760 KUNIT_EXPECT_KASAN_FAIL(test,
> > kfree_sensitive(ptr));
> > 761 }
> > 762
> > 763 static void vmalloc_oob(struct kunit *test)
> > 764 {
> > 765 void *area;
> > 766
> > 767 if (!IS_ENABLED(CONFIG_KASAN_VMALLOC)) {
> > 768 kunit_info(test, "CONFIG_KASAN_VMALLOC is
> > not
> > enabled.");
> > (gdb) l *vmalloc_oob+0x146
> > 0x81b8b1f6 is in vmalloc_oob (lib/test_kasan.c:779).
> > 774  * The MMU will catch that and crash us.
> > 775  */
> > 776 area = vmalloc(3000);
> > 777 KUNIT_ASSERT_NOT_ERR_OR_NULL(test, area);
> > 778
> > 779 KUNIT_EXPECT_KASAN_FAIL(test, ((volatile char
> > *)area)[3100]);
> > 780 vfree(area);
> > 781 }
> > 782
> > 783 static struct kunit_case kasan_kunit_test_cases[] = {
> > x-x
> > >
> > 
> > Reported by: Jeffrin Jose T 
> 
> Which CI system is reporting these?
> 
> If you look, this is the KASAN test, and the report is very much
> intended since it's testing KASAN. Please blacklist the KASAN test
> (and any other tests testing debugging tools).
> 
> Thanks,
> -- Marco

gdb session was started by me.  (gdb ./vmlinux)

portion from dmesg output is as follows
xx-
-->
[   43.616259] BUG: KASAN: vmalloc-out-of-bounds in
vmalloc_oob+0x146/0x2c0
[   43.630470] Read of size 1 at addr c906ec1c by task
kunit_try_catch/193

[   43.659055] CPU: 2 PID: 193 Comm: kunit_try_catch Tainted: GB  
5.10.0-rc6+ #10
[   43.659070] Hardware name: ASUSTeK COMPUTER INC. VivoBook 15_ASUS
Laptop X507UAR/X507UAR, BIOS X507UAR.203 05/31/2018
[   43.659080] Call Trace:
[   43.659105]  dump_stack+0x119/0x179
[   43.659131]  print_address_description.constprop.0+0x1c/0x210
[   43.659163]  ? vmalloc_oob+0x146/0x2c0
[   43.659185]  kasan_report.cold+0x1f/0x37
[   43.659210]  ? vmalloc_oob+0x146/0x2c0
[   43.659234]  vmalloc_oob+0x146/0x2c0
[   43.659259]  ? kasan_global_oob+0x280/0x280
[   43.659287]  ? kunit_fail_assert_format+0xa0/0xa0
[   43.659313]  ? lock_release+0xb2/0x730
[   43.659334]  ? __kthread_parkme+0xa1/0x120
[   43.659356]  ? lock_acquired+0xb4/0x5b0
[   43.659379]  ? lock_downgrade+0x3d0/0x3d0
[   43.659403]  ? lock_contended+0x6e0/0x6e0
[   43.659423]  ? do_raw_spin_lock+0x1b0/0x1b0
[   43.659447]  ? io_schedule_timeout+0xb0/0xb0
[   43.659467]  ? static_obj+0x31/0x80
[   43.659492]  ? lockdep_hardirqs_on_prepare+0xe/0x240
[   43.659517]  ? memcg_accounted_kmem_cache+0x1b0/0x1b0
[   43.659542]  kunit_try_run_case+0xa6/0x150
[   43.659567]  ? kunit_catch_run_case+0x170/0x170
[   43.659591]  ? kunit_try_catch_throw+0x40/0x40
[   43.659617]  kunit_generic_run_threadfn_adapter+0x2e/0x50
[   43.659637]  kthread+0x232/0x260
[   43.659659]  ? __kthread_bind_mask+0x90/0x90
[   43.659684]  ret_from_fork+0x22/0x30


[   43.686511] Memory state around the buggy address:
[   43.700445]  c906eb00: 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00
[   43.714559]  c906eb80: 00 00 00 00 00 00 00 f8 f8 f8 f8 f8
f8 f8 f8 f8
[   43.728725] >c906ec00: f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8
f8 f8 f8 f8
[   43.742808] ^
[   43.757156]  c906ec80: f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8
f8 f8 f8 f8
[   43.771845]  c906ed00: f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8
f8 f8 f8 f8
[   43.785957]
==

---x-x-
-->


-- 
software engineer
rajagiri school of engineering and technology - autonomous

BUG: KASAN lib/test_kasan.c

[Jeffrin Jose T]

hello,

 detected   KASAN   BUG

[ related information ]

---x---x>
[   43.616259] BUG: KASAN: vmalloc-out-of-bounds in
vmalloc_oob+0x146/0x2c0

(gdb) l *vmalloc_oob+0x146/0x2c0
0x81b8b0b0 is in vmalloc_oob (lib/test_kasan.c:764).
759 kfree_sensitive(ptr);
760 KUNIT_EXPECT_KASAN_FAIL(test, kfree_sensitive(ptr));
761 }
762 
763 static void vmalloc_oob(struct kunit *test)
764 {
765 void *area;
766 
767 if (!IS_ENABLED(CONFIG_KASAN_VMALLOC)) {
768 kunit_info(test, "CONFIG_KASAN_VMALLOC is not
enabled.");
(gdb) l *vmalloc_oob+0x146
0x81b8b1f6 is in vmalloc_oob (lib/test_kasan.c:779).
774  * The MMU will catch that and crash us.
775  */
776 area = vmalloc(3000);
777 KUNIT_ASSERT_NOT_ERR_OR_NULL(test, area);
778 
779 KUNIT_EXPECT_KASAN_FAIL(test, ((volatile char
*)area)[3100]);
780 vfree(area);
781 }
782 
783 static struct kunit_case kasan_kunit_test_cases[] = {
x-x>

Reported by: Jeffrin Jose T 

-- 
software engineer
rajagiri school of engineering and technology - autonomous

[PROBLEM] drivers:hid 2 memory leaks suspected

[Jeffrin Jose T]

hello,

2 new suspected  memory leaks. 


$sudo cat /sys/kernel/debug/kmemleak
[sudo] password for jeffrin:
unreferenced object 0x88813128bee0 (size 16):
comm "irq/109-ELAN130", pid 152, jiffies 4294931163 (age 9576.624s)
hex dump (first 16 bytes):
04 03 08 0a eb 03 24 e7 01 80 13 44 00 00 00 00 ..$D
backtrace:
[<eff80361>] kmemdup+0x1a/0x40
[<552197bd>] hidraw_report_event+0xbc/0x190 [hid]
[<a102ccd5>] hid_report_raw_event+0x70a/0x790 [hid]
[<b1b8f73f>] hid_input_report+0x1b4/0x210 [hid]
[<e0f74a09>] i2c_hid_irq+0x164/0x1e0 [i2c_hid]
[<a79c6ce4>] irq_thread_fn+0x40/0xb0
[<37a84810>] irq_thread+0x23d/0x330
[<09e057aa>] kthread+0x1cd/0x1f0
[<5e7b7b46>] ret_from_fork+0x22/0x30
unreferenced object 0x88813128b640 (size 16):
comm "irq/109-ELAN130", pid 152, jiffies 4294931165 (age 9576.616s)
hex dump (first 16 bytes):
04 03 02 0a ee 03 74 e7 01 80 13 44 00 00 00 00 ..tD
backtrace:
[<eff80361>] kmemdup+0x1a/0x40
[<552197bd>] hidraw_report_event+0xbc/0x190 [hid]
[<a102ccd5>] hid_report_raw_event+0x70a/0x790 [hid]
[<b1b8f73f>] hid_input_report+0x1b4/0x210 [hid]
[<e0f74a09>] i2c_hid_irq+0x164/0x1e0 [i2c_hid]
[<a79c6ce4>] irq_thread_fn+0x40/0xb0
[<37a84810>] irq_thread+0x23d/0x330
[<09e057aa>] kthread+0x1cd/0x1f0
[<5e7b7b46>] ret_from_fork+0x22/0x30
$


[ Details about System ].

Linux debian 5.10.0-rc6 #4 SMP Wed Dec 2 02:49:21 IST 2020 x86_64
GNU/Linux

GNU C 10
GNU Make 4.3
Binutils 2.35.1
Util-linux 2.36.1
Mount 2.36.1
Bison 3.7.3
Flex 2.6.4
Dynamic linker (ldd) 2.31
Procps 3.3.16
Kbd 2.3.0
Console-tools 2.3.0
Sh-utils 8.32
Udev 246

Reported-by: Jeffrin Jose T 

-- 
software engineer
rajagiri school of engineering and technology - autonomous

Re: [PATCH 5.9 000/152] 5.9.12-rc1 review

[Jeffrin Jose T]

On Tue, 2020-12-01 at 09:51 +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.9.12 release.
> There are 152 patches in this series, all will be posted as a
> response
> to this one.  If anyone has any issues with these being applied,
> please
> let me know.
> 
> Responses should be made by Thu, 03 Dec 2020 08:46:29 +.
> Anything received after that time might be too late.
> 
> The whole patch series can be found in one patch at:
> 
> https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.9.12-rc1.gz
> or in the git tree and branch at:
> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-
> stable-rc.git linux-5.9.y
> and the diffstat can be found below.
> 
> thanks,
> 
> greg k-h

hello,

Compiled and booted  5.9.12-rc1+. No typical dmesg regression 
or regressions.

Tested-by: Jeffrin Jose T 

-- 
software engineer
rajagiri school of engineering and technology - autonomous

Re: [PATCH 5.9 00/14] 5.9.10-rc1 review

[Jeffrin Jose T]

On Fri, 2020-11-20 at 12:03 +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.9.10 release.
> There are 14 patches in this series, all will be posted as a response
> to this one.  If anyone has any issues with these being applied,
> please
> let me know.
> 
> Responses should be made by Sun, 22 Nov 2020 10:45:32 +.
> Anything received after that time might be too late.
> 
> The whole patch series can be found in one patch at:
>   
> https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.9.10-rc1.gz
> or in the git tree and branch at:
>   git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-
> stable-rc.git linux-5.9.y
> and the diffstat can be found below.
> 
hello,

Compiled and booted 5.9.10-rc1+. No issues with "dmesg -l err"
But "dmesg -l warn" shows something.

file dmesg-warn-nov-20-2020-portion.txt  is attached

Tested-by: Jeffrin Jose T 

--
software engineer
rajagiri school of engineering and technology - autonomous


[ 1135.758165] pcieport :00:1c.5: PCIe Bus Error: severity=Corrected, 
type=Data Link Layer, (Transmitter ID)
[ 1135.758174] pcieport :00:1c.5:   device [8086:9d15] error 
status/mask=1000/2000
[ 1135.758183] pcieport :00:1c.5:[12] Timeout   

Re: [PATCH 5.9 000/255] 5.9.9-rc1 review

[Jeffrin Jose T]

On Tue, 2020-11-17 at 14:02 +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.9.9 release.
> There are 255 patches in this series, all will be posted as a
> response
> to this one.  If anyone has any issues with these being applied,
> please
> let me know.
> 
> Responses should be made by Thu, 19 Nov 2020 12:20:51 +.
> Anything received after that time might be too late.
> 
> The whole patch series can be found in one patch at:
>   
> https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.9.9-rc1.gz
> or in the git tree and branch at:
>   git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-
> stable-rc.git linux-5.9.y
> and the diffstat can be found below.
> 
> thanks,
> 
> greg k-h
> 
> 
Compiled and booted 5.9.9-rc1+. No typical dmesg regression or
regressions.

Tested-by: Jeffrin Jose T 
-- 
software engineer
rajagiri school of engineering and technology - autonomous

Re: checking for "config" file existence.

[Jeffrin Jose T]

On Mon, 2020-11-16 at 11:32 -0700, Shuah Khan wrote:
> On 11/12/20 10:40 AM, Jeffrin Jose T wrote:
> > hello,
> > 
> > i wrote a  small program to check for the existence of "config"
> > files
> > for testing projects under kselftest framework.
> > 
> > chmod 755 test_config.py
> > This file should be located in "tools/testing/selftests"
> > This can be run as "./test_config.py"
> > 
> Why do we need a dedicated script when you can do it with:
> 
> cd tools/testing/selftests; find . -name config
> 
> I see that your script also prints if config doesn't exist.
> It is not a failure not have config as config is necessary
> only when a test has config option dependencies.
> 
> What does this script attempting to solve?

according to what  you said  this script may not be necessary
thanks for the explanation :)


-- 
software engineer
rajagiri school of engineering and technology - autonomous

[ERROR] Bluetooth: hci0: don't support firmware

[Jeffrin Jose T]

hello,

i got this stuff from "sudo dmesg -l err"
x--x
[   40.919919] Bluetooth: hci0: don't support firmware rome 0x31010100
-x-x

$uname -a
Linux debian 5.10.0-rc3+ #1 SMP Thu Nov 12 23:37:27 IST 2020 x86_64
GNU/Linux
$

$sudo hcitool dev
Devices:
$

GNU C   10
GNU Make4.3
Binutils2.35.1
Util-linux  2.36
Mount   2.36
Bison   3.7.3
Flex2.6.4
Dynamic linker (ldd)2.31
Procps  3.3.16
Kbd 2.3.0
Console-tools   2.3.0
Sh-utils8.32
Udev246

file bstatus.txt attached.


Reported-by: Jeffrin Jose T 

-- 
software engineer
rajagiri school of engineering and technology -  autonomous


● bluetooth.service - Bluetooth service
 Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset: enabled)
 Active: active (running) since Fri 2020-11-13 16:08:58 IST; 54min ago
   Docs: man:bluetoothd(8)
   Main PID: 582 (bluetoothd)
 Status: "Running"
  Tasks: 1 (limit: 4015)
 Memory: 2.9M
 CGroup: /system.slice/bluetooth.service
 └─582 /usr/libexec/bluetooth/bluetoothd

Nov 13 16:08:54 debian bluetoothd[582]: src/main.c:parse_controller_config() 
Key file does not have key “LEScanIntervalConnect” in group “Controller”
Nov 13 16:08:54 debian bluetoothd[582]: src/main.c:parse_controller_config() 
Key file does not have key “LEScanWindowConnect” in group “Controller”
Nov 13 16:08:54 debian bluetoothd[582]: src/main.c:parse_controller_config() 
Key file does not have key “LEMinConnectionInterval” in group “Controller”
Nov 13 16:08:54 debian bluetoothd[582]: src/main.c:parse_controller_config() 
Key file does not have key “LEMaxConnectionInterval” in group “Controller”
Nov 13 16:08:54 debian bluetoothd[582]: src/main.c:parse_controller_config() 
Key file does not have key “LEConnectionLatency” in group “Controller”
Nov 13 16:08:54 debian bluetoothd[582]: src/main.c:parse_controller_config() 
Key file does not have key “LEConnectionSupervisionTimeout” in group 
“Controller”
Nov 13 16:08:54 debian bluetoothd[582]: src/main.c:parse_controller_config() 
Key file does not have key “LEAutoconnecttimeout” in group “Controller”
Nov 13 16:08:58 debian systemd[1]: Started Bluetooth service.
Nov 13 16:08:58 debian bluetoothd[582]: Starting SDP server
Nov 13 16:09:00 debian bluetoothd[582]: Bluetooth management interface 1.18 
initialized

checking for "config" file existence.

[Jeffrin Jose T]

hello,

i wrote a  small program to check for the existence of "config" files
for testing projects under kselftest framework.

chmod 755 test_config.py
This file should be located in "tools/testing/selftests"
This can be run as "./test_config.py"



-- 
software engineer
rajagiri school of engineering and technology - autonomous



#!/usr/bin/python3
# SPDX-License-Identifier: GPL-2.0
# Copyright (C) 2020  RSET

import os
from pathlib import Path

ok = 0
notok = 0
for filename in os.listdir():
fileall = Path("./"+filename)
filecheck = Path("./"+filename+"/"+"config")
if (fileall.is_dir()) and (filename != "kselftest"):
if filecheck.exists():
print(filename," [PASS]\n")
ok = ok + 1 
else:
print(filename," [FAIL]\n")
notok = notok + 1

print(ok+notok,"TESTED") 
print(ok, "PASSED")
print(notok,"FAILED")

Re: [PATCH 5.9 000/133] 5.9.7-rc1 review

[Jeffrin Jose T]

On Mon, 2020-11-09 at 13:54 +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.9.7 release.
> There are 133 patches in this series, all will be posted as a
> response
> to this one.  If anyone has any issues with these being applied,
> please
> let me know.
> 
> Responses should be made by Wed, 11 Nov 2020 12:50:04 +.
> Anything received after that time might be too late.
> 
> The whole patch series can be found in one patch at:
>   
> https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.9.7-rc1.gz
> or in the git tree and branch at:
>   git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-
> stable-rc.git linux-5.9.y
> and the diffstat can be found below.
> 
> thanks,
> 
> greg k-h

Compiled and  booted  5.9.7-rc1+. No typical dmesg regressions.

Tested-by: Jeffrin Jose T 

-- 
software engineer
rajagiri school of engineering and technology  - autonomous

Re: [PATCH 5.9 000/133] 5.9.7-rc1 review

[Jeffrin Jose T]

On Mon, 2020-11-09 at 13:54 +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.9.7 release.
> There are 133 patches in this series, all will be posted as a
> response
> to this one.  If anyone has any issues with these being applied,
> please
> let me know.
> 
> Responses should be made by Wed, 11 Nov 2020 12:50:04 +.
> Anything received after that time might be too late.
> 
> The whole patch series can be found in one patch at:
>   
> https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.9.7-rc1.gz
> or in the git tree and branch at:
>   git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-
> stable-rc.git linux-5.9.y
> and the diffstat can be found below.
> 
> thanks,
> 
> greg k-h

Compiled and  booted  5.9.7-rc1+. No typical dmesg regressions.

Tested-by: Jeffrin Jose T 

-- 
software engineer
rajagiri school of engineering and technology  - autonomous

Re: [PATCH 5.9 000/391] 5.9.4-rc1 review

[Jeffrin Jose T]

On Tue, 2020-11-03 at 21:30 +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.9.4 release.
> There are 391 patches in this series, all will be posted as a
> response
> to this one.  If anyone has any issues with these being applied,
> please
> let me know.
> 
> Responses should be made by Thu, 05 Nov 2020 20:29:58 +.
> Anything received after that time might be too late.
> 
> The whole patch series can be found in one patch at:
>   
> https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.9.4-rc1.gz
> or in the git tree and branch at:
>   git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-
> stable-rc.git linux-5.9.y
> and the diffstat can be found below.
> 
> thanks,
> 
> greg k-h

Compiled and booted 5.9.4-rc1+ . No typical dmesg regressions.


Tested-by: Jeffrin Jose T 

-- 
software engineer
rajagiri school of engineering and technology  - autonomous

Re: [PATCH 5.9 00/74] 5.9.3-rc1 review

[Jeffrin Jose T]

On Sun, 2020-11-01 at 11:41 +0100, Greg Kroah-Hartman wrote:
> On Sat, Oct 31, 2020 at 10:41:38PM +0530, Jeffrin Jose T wrote:
> > On Sat, 2020-10-31 at 12:35 +0100, Greg Kroah-Hartman wrote:
> > > This is the start of the stable review cycle for the 5.9.3
> > > release.
> > > There are 74 patches in this series, all will be posted as a
> > > response
> > > to this one.  If anyone has any issues with these being applied,
> > > please
> > > let me know.
> > > 
> > > Responses should be made by Mon, 02 Nov 2020 11:34:42 +.
> > > Anything received after that time might be too late.
> > > 
> > > The whole patch series can be found in one patch at:
> > >   
> > > https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.9.3-rc1.gz
> > > or in the git tree and branch at:
> > >   git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-
> > > stable-rc.git linux-5.9.y
> > > and the diffstat can be found below.
> > > 
> > > thanks,
> > > 
> > > greg k-h
> > 
> > hello,
> > i have build using ktest. but then i did the normal compile.
> > compiled and booted 5.9.3-rc1+ . dmesg -l err is clear.
> > 
> > some lines from dmesg output related  
> > --x--x---x---
> > video: module verification failed: signature and/or required key
> > missing - tainting kernel
> > sdhci-pci :00:1e.6: failed to setup card detect gpio
> > x---x-x---
> > 
> > 
> > Now something related to kernel build and install..
> > --x-x--x---
> > WARNING: modpost: EXPORT symbol "copy_mc_fragile" [vmlinux] version
> > generation failed, symbol will not be versioned.
> > W: Possible missing firmware /lib/firmware/i915/rkl_dmc_ver2_01.bin
> > for
> > module i915
> > -x---x-x---
> > --
> > 
> > Now one thing during boot..
> > ---xx 
> > unable to start nftables
> > -x---x---
> > 
> > iam attaching a fileplease see...
> 
> Is this any different from 5.9.2?
according to dmesg,things are to  an extent ok.

the other stuff may be because of my system upgradation
and may be there is a change in kernel configuration

Overall i think there may be nothing serious in kernel space.

.

-- 
software engineer
rajagiri school of engineering and technology - autonomous

Re: [PATCH 5.9 00/74] 5.9.3-rc1 review

[Jeffrin Jose T]

On Sat, 2020-10-31 at 12:35 +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.9.3 release.
> There are 74 patches in this series, all will be posted as a response
> to this one.  If anyone has any issues with these being applied,
> please
> let me know.
> 
> Responses should be made by Mon, 02 Nov 2020 11:34:42 +.
> Anything received after that time might be too late.
> 
> The whole patch series can be found in one patch at:
>   
> https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.9.3-rc1.gz
> or in the git tree and branch at:
>   git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-
> stable-rc.git linux-5.9.y
> and the diffstat can be found below.
> 
> thanks,
> 
> greg k-h

hello,
i have build using ktest. but then i did the normal compile.
compiled and booted 5.9.3-rc1+ . dmesg -l err is clear.

some lines from dmesg output related  
--x--x---x---
video: module verification failed: signature and/or required key
missing - tainting kernel
sdhci-pci :00:1e.6: failed to setup card detect gpio
x---x-x---


Now something related to kernel build and install..
--x-x--x---
WARNING: modpost: EXPORT symbol "copy_mc_fragile" [vmlinux] version
generation failed, symbol will not be versioned.
W: Possible missing firmware /lib/firmware/i915/rkl_dmc_ver2_01.bin for
module i915
-x---x-x-

Now one thing during boot..
---xx 
unable to start nftables
-x-------x---

iam attaching a fileplease see...

Tested-by: Jeffrin Jose T 


-- 
software engineer
rajagiri school of engineering and technology  - autonomous



ld: arch/x86/boot/compressed/head_64.o: warning: relocation in read-only 
section `.head.text'
  LD [M]  drivers/net/wireless/ath/ath9k/ath9k_hw.ko
ld: warning: creating DT_TEXTREL in a PIE

Re: [PATCH 5.9 000/757] 5.9.2-rc1 review

[Jeffrin Jose T]

On Tue, 2020-10-27 at 14:44 +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.9.2 release.
> There are 757 patches in this series, all will be posted as a
> response
> to this one.  If anyone has any issues with these being applied,
> please
> let me know.
> 
> Responses should be made by Thu, 29 Oct 2020 13:52:54 +.
> Anything received after that time might be too late.
> 
> The whole patch series can be found in one patch at:
>   
> https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.9.2-rc1.gz
> or in the git tree and branch at:
>   git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-
> stable-rc.git linux-5.9.y
> and the diffstat can be found below.
> 
> thanks,
> 
> 

hello,

Compiled and booted  5.9.2-rc1+.
Looks like no typical regression or regressions.

Tested-by: Jeffrin Jose T 

-- 
software engineer
rajagiri school of engineering and technology  -  autonomous

Re: Fwd: [WARNING AND ERROR] may be system slow and audio and video breaking

[Jeffrin Jose T]

On Sun, 2020-10-18 at 23:03 +0200, Borislav Petkov wrote:
> On Mon, Oct 19, 2020 at 01:51:34AM +0530, Jeffrin Jose T wrote:
> > On Sun, 2020-10-18 at 19:49 +0200, Borislav Petkov wrote:
> > > On Sun, Oct 18, 2020 at 10:42:39PM +0530, Jeffrin Jose T wrote:
> > > > smpboot: Scheduler frequency invariance went wobbly, disabling!
> > > > [ 1112.592866] unchecked MSR access error: RDMSR from 0x123 at
> > > > rIP:
> > > > 0xb5c9a184 (native_read_msr+0x4/0x30)
> 
> Ok, you forgot to say in your initial mail that this happens when you
> suspend your laptop.
> 
> Now, this unchecked MSR error thing happens only once because that
> early
> during resume the microcode on CPU1 is not updated yet - and that
> needs
> to be debugged separately and I'll try to reproduce that on my
> machine -
> so the microcode is not updated yet and therefore the 0x123 MSR is
> not
> "emulated" by the microcode, so to speak, thus the warning.
> 
> That warning doesn't happen anymore, though, once the microcode is
> updated.
> 
> But what happens after that is you get a flood of correctable PCIe
> errors about a transaction to a device timeoutting:
> 
> pcieport :00:1c.5: AER: Corrected error received: :00:1c.5
> pcieport :00:1c.5: PCIe Bus Error: severity=Corrected, type=Data
> Link Layer, (Transmitter ID)
> pcieport :00:1c.5:   device [8086:9d15] error
> status/mask=1000/2000
> pcieport :00:1c.5:[12] Timeout 
> 
> and it looks like that flood is slowing down the machine because it
> is
> busy logging them.
> 
> Do
> 
> # lspci -nn -xxx
> 
> as root. It'll show us which device that 8086:9d15 is.
> 
> Thx.
> 

$sudo lspci -nn -xxx | grep 9d15
00:1c.5 PCI bridge [0604]: Intel Corporation Sunrise Point-LP PCI
Express Root Port #6 [8086:9d15] (rev f1)
$


file lspci.txt is attached
-- 
software engineer
rajagiri school of engineering and technology
00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core 
Processor Host Bridge/DRAM Registers [8086:5904] (rev 03)
00: 86 80 04 59 06 00 90 20 03 00 00 06 00 00 00 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 43 10 11 13
30: 00 00 00 00 e0 00 00 00 00 00 00 00 00 00 00 00
40: 01 90 d1 fe 00 00 00 00 01 00 d1 fe 00 00 00 00
50: c1 02 00 00 b1 00 00 00 47 00 f0 9f 01 00 00 9b
60: 03 00 00 f0 00 00 00 00 01 80 d1 fe 00 00 00 00
70: 00 00 00 ff 01 00 00 00 00 0c 00 ff 7f 00 00 00
80: 01 00 00 00 00 00 00 00 1a 00 00 00 00 00 00 00
90: 01 00 00 ff 01 00 00 00 01 00 f0 5e 02 00 00 00
a0: 01 00 00 00 02 00 00 00 01 00 00 5f 02 00 00 00
b0: 01 00 00 9c 01 00 80 9b 01 00 00 9b 01 00 00 a0
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 09 00 10 01 31 60 61 7a dc 80 15 94 00 c0 06 00
f0: 00 00 00 00 c8 0f 09 00 00 00 00 00 00 00 00 00

00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:5921] 
(rev 06)
00: 86 80 21 59 07 04 10 00 06 00 00 03 10 00 00 00
10: 04 00 00 ee 00 00 00 00 0c 00 00 d0 00 00 00 00
20: 01 f0 00 00 00 00 00 00 00 00 00 00 43 10 11 13
30: 00 00 00 00 40 00 00 00 00 00 00 00 ff 01 00 00
40: 09 70 0c 01 31 60 61 7a dc 80 15 94 00 00 00 00
50: c1 02 00 00 b1 00 00 00 00 00 00 00 01 00 00 9c
60: 00 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 10 ac 92 00 00 80 00 10 00 00 00 00 00 00 00 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 05 d0 01 00
b0: 18 00 e0 fe 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 01 00 22 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 80 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 18 50 90 9a

00:04.0 Signal processing controller [1180]: Intel Corporation Xeon E3-1200 
v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [8086:1903] (rev 03)
00: 86 80 03 19 02 00 90 00 03 00 80 11 00 00 00 00
10: 04 80 1a ef 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 43 10 11 13
30: 00 00 00 00 90 00 00 00 00 00 00 00 ff 01 00 00
40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
50: 00 00 00 00 b1 00 00 00 00 00 00 00 00 00 00 00
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 05 d0 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 01 e0 03 00 08 00 00 00 00 00 00 00 00 00 00 00
e0: 09 00 0c 01 31 60 61 7a dc 80 15 94 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00:14.0 USB controller [0c03]: Intel Corpora

Fwd: [WARNING AND ERROR] may be system slow and audio and video breaking

[Jeffrin Jose T]

--- Begin Message ---
hello,
System was slow and  audio and video
was breaking. I was compiling a kernel and also
played a youtube video in firefox and  maybe evolution.

meminfo.txt  and lscpu.txt files are attached.

The following is a part from "dmesg -l warn"

---x--x-x
smpboot: Scheduler frequency invariance went wobbly, disabling!
[ 1112.592866] unchecked MSR access error: RDMSR from 0x123 at rIP:
0xb5c9a184 (native_read_msr+0x4/0x30)
[ 1112.592869] Call Trace:
[ 1112.592876]  update_srbds_msr+0x6f/0xb0
[ 1112.592880]  smp_store_cpu_info+0x8e/0xb0
[ 1112.592883]  start_secondary+0x93/0x200
[ 1112.592887]  ? set_cpu_sibling_map+0xcb0/0xcb0
[ 1112.592891]  secondary_startup_64+0xa4/0xb0
[ 1112.592898] unchecked MSR access error: WRMSR to 0x123 (tried to
write 0x) at rIP: 0xb5c9a264
(native_write_msr+0x4/0x20)
[ 1112.592899] Call Trace:
[ 1112.592902]  update_srbds_msr+0x98/0xb0
[ 1112.592904]  smp_store_cpu_info+0x8e/0xb0
[ 1112.592907]  start_secondary+0x93/0x200
[ 1112.592911]  ? set_cpu_sibling_map+0xcb0/0xcb0
[ 1112.592914]  secondary_startup_64+0xa4/0xb0
[ 2915.106879] show_signal: 6 callbacks suppressed
[ 6089.209343] WARNING: stack going in the wrong direction? at
i915_gem_close_object+0x2fb/0x560 [i915]
$
-x---xx
Linux debian 5.9.1-rc1+ #4 SMP Fri Oct 16 16:48:04 IST 2020 x86_64
GNU/Linux

GNU Make4.3
Binutils2.35.1
Util-linux  2.36
Mount   2.36
Bison   3.7.2
Flex2.6.4
Dynamic linker (ldd)2.30
Procps  3.3.16
Kbd 2.3.0
Console-tools   2.3.0
Sh-utils8.32
Udev246


Reported-by: Jeffrin Jose T MemTotal:6952576 kB
MemFree:  299000 kB
MemAvailable:2964748 kB
Buffers:  169024 kB
Cached:  3447336 kB
SwapCached:  108 kB
Active:  1996356 kB
Inactive:3315820 kB
Active(anon): 643748 kB
Inactive(anon):  1950892 kB
Active(file):1352608 kB
Inactive(file):  1364928 kB
Unevictable:   57668 kB
Mlocked: 160 kB
SwapTotal:   8263676 kB
SwapFree:8261092 kB
Dirty: 16632 kB
Writeback: 0 kB
AnonPages:   1736772 kB
Mapped:   520572 kB
Shmem:898760 kB
KReclaimable: 264048 kB
Slab:1045968 kB
SReclaimable: 264048 kB
SUnreclaim:   781920 kB
KernelStack:   28320 kB
PageTables:27856 kB
NFS_Unstable:  0 kB
Bounce:0 kB
WritebackTmp:  0 kB
CommitLimit:11739964 kB
Committed_AS:7741848 kB
VmallocTotal:   34359738367 kB
VmallocUsed:   60544 kB
VmallocChunk:  0 kB
Percpu: 2672 kB
HardwareCorrupted: 0 kB
AnonHugePages:763904 kB
ShmemHugePages:0 kB
ShmemPmdMapped:0 kB
FileHugePages: 0 kB
FilePmdMapped: 0 kB
HugePages_Total:   0
HugePages_Free:0
HugePages_Rsvd:0
HugePages_Surp:0
Hugepagesize:   2048 kB
Hugetlb:   0 kB
DirectMap4k:  891756 kB
DirectMap2M: 7372800 kB
DirectMap1G: 1048576 kB
Architecture:x86_64
CPU op-mode(s):  32-bit, 64-bit
Byte Order:  Little Endian
Address sizes:   39 bits physical, 48 bits virtual
CPU(s):  4
On-line CPU(s) list: 0-3
Thread(s) per core:  2
Core(s) per socket:  2
Socket(s):   1
NUMA node(s):1
Vendor ID:   GenuineIntel
CPU family:  6
Model:   142
Model name:  Intel(R) Core(TM) i3-7020U CPU @ 2.30GHz
Stepping:9
CPU MHz: 2299.999
CPU max MHz: 2300.
CPU min MHz: 400.
BogoMIPS:4599.93
Virtualization:  VT-x
L1d cache:   64 KiB
L1i cache:   64 KiB
L2 cache:512 KiB
L3 cache:3 MiB
NUMA node0 CPU(s):   0-3
Vulnerability Itlb multihit: KVM: Mitigation: VMX disabled
Vulnerability L1tf:  Mitigation; PTE Inversion; VMX conditional 
cache flushes, SMT vulnerable
Vulnerability Mds:   Mitigation; Clear CPU buffers; SMT vulnerable
Vulnerability Meltdown:  Mitigation; PTI
Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass disabled 
via prctl and seccomp
Vulnerability Spectre v1:Mitigation; usercopy/swapgs barriers and 
__user pointer sanitization
Vulnerability Spectre v2:Mitigation; Full generic retpoline, IBPB 
conditional, IBRS_FW, STIBP conditional, RSB filling
Vulnerability Srbds: Mitigation;

[WARNING AND ERROR] may be system slow and audio and video breaking

[Jeffrin Jose T]

hello,
System was slow and  audio and video
was breaking. I was compiling a kernel and also
played a youtube video in firefox and  maybe evolution.

meminfo.txt  and lscpu.txt files are attached.

The following is a part from "dmesg -l warn"

---x--x-x
smpboot: Scheduler frequency invariance went wobbly, disabling!
[ 1112.592866] unchecked MSR access error: RDMSR from 0x123 at rIP:
0xb5c9a184 (native_read_msr+0x4/0x30)
[ 1112.592869] Call Trace:
[ 1112.592876]  update_srbds_msr+0x6f/0xb0
[ 1112.592880]  smp_store_cpu_info+0x8e/0xb0
[ 1112.592883]  start_secondary+0x93/0x200
[ 1112.592887]  ? set_cpu_sibling_map+0xcb0/0xcb0
[ 1112.592891]  secondary_startup_64+0xa4/0xb0
[ 1112.592898] unchecked MSR access error: WRMSR to 0x123 (tried to
write 0x) at rIP: 0xb5c9a264
(native_write_msr+0x4/0x20)
[ 1112.592899] Call Trace:
[ 1112.592902]  update_srbds_msr+0x98/0xb0
[ 1112.592904]  smp_store_cpu_info+0x8e/0xb0
[ 1112.592907]  start_secondary+0x93/0x200
[ 1112.592911]  ? set_cpu_sibling_map+0xcb0/0xcb0
[ 1112.592914]  secondary_startup_64+0xa4/0xb0
[ 2915.106879] show_signal: 6 callbacks suppressed
[ 6089.209343] WARNING: stack going in the wrong direction? at
i915_gem_close_object+0x2fb/0x560 [i915]
$
-x---xx
Linux debian 5.9.1-rc1+ #4 SMP Fri Oct 16 16:48:04 IST 2020 x86_64
GNU/Linux

GNU Make4.3
Binutils2.35.1
Util-linux  2.36
Mount   2.36
Bison   3.7.2
Flex2.6.4
Dynamic linker (ldd)2.30
Procps  3.3.16
Kbd 2.3.0
Console-tools   2.3.0
Sh-utils8.32
Udev246


Reported-by: Jeffrin Jose T MemTotal:6952576 kB
MemFree:  299000 kB
MemAvailable:2964748 kB
Buffers:  169024 kB
Cached:  3447336 kB
SwapCached:  108 kB
Active:  1996356 kB
Inactive:3315820 kB
Active(anon): 643748 kB
Inactive(anon):  1950892 kB
Active(file):1352608 kB
Inactive(file):  1364928 kB
Unevictable:   57668 kB
Mlocked: 160 kB
SwapTotal:   8263676 kB
SwapFree:8261092 kB
Dirty: 16632 kB
Writeback: 0 kB
AnonPages:   1736772 kB
Mapped:   520572 kB
Shmem:898760 kB
KReclaimable: 264048 kB
Slab:1045968 kB
SReclaimable: 264048 kB
SUnreclaim:   781920 kB
KernelStack:   28320 kB
PageTables:27856 kB
NFS_Unstable:  0 kB
Bounce:0 kB
WritebackTmp:  0 kB
CommitLimit:11739964 kB
Committed_AS:7741848 kB
VmallocTotal:   34359738367 kB
VmallocUsed:   60544 kB
VmallocChunk:  0 kB
Percpu: 2672 kB
HardwareCorrupted: 0 kB
AnonHugePages:763904 kB
ShmemHugePages:0 kB
ShmemPmdMapped:0 kB
FileHugePages: 0 kB
FilePmdMapped: 0 kB
HugePages_Total:   0
HugePages_Free:0
HugePages_Rsvd:0
HugePages_Surp:0
Hugepagesize:   2048 kB
Hugetlb:   0 kB
DirectMap4k:  891756 kB
DirectMap2M: 7372800 kB
DirectMap1G: 1048576 kB
Architecture:x86_64
CPU op-mode(s):  32-bit, 64-bit
Byte Order:  Little Endian
Address sizes:   39 bits physical, 48 bits virtual
CPU(s):  4
On-line CPU(s) list: 0-3
Thread(s) per core:  2
Core(s) per socket:  2
Socket(s):   1
NUMA node(s):1
Vendor ID:   GenuineIntel
CPU family:  6
Model:   142
Model name:  Intel(R) Core(TM) i3-7020U CPU @ 2.30GHz
Stepping:9
CPU MHz: 2299.999
CPU max MHz: 2300.
CPU min MHz: 400.
BogoMIPS:4599.93
Virtualization:  VT-x
L1d cache:   64 KiB
L1i cache:   64 KiB
L2 cache:512 KiB
L3 cache:3 MiB
NUMA node0 CPU(s):   0-3
Vulnerability Itlb multihit: KVM: Mitigation: VMX disabled
Vulnerability L1tf:  Mitigation; PTE Inversion; VMX conditional 
cache flushes, SMT vulnerable
Vulnerability Mds:   Mitigation; Clear CPU buffers; SMT vulnerable
Vulnerability Meltdown:  Mitigation; PTI
Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass disabled 
via prctl and seccomp
Vulnerability Spectre v1:Mitigation; usercopy/swapgs barriers and 
__user pointer sanitization
Vulnerability Spectre v2:Mitigation; Full generic retpoline, IBPB 
conditional, IBRS_FW, STIBP conditional, RSB filling
Vulnerability Srbds: Mitigation; Microcode
Vulnerability

Re: [PATCH 5.8 00/14] 5.8.16-rc1 review

[Jeffrin Jose T]

On Fri, 2020-10-16 at 17:00 +0200, Greg Kroah-Hartman wrote:
> On Fri, Oct 16, 2020 at 07:41:05PM +0530, Jeffrin Jose T wrote:
> > On Fri, 2020-10-16 at 11:07 +0200, Greg Kroah-Hartman wrote:
> > > This is the start of the stable review cycle for the 5.8.16
> > > release.
> > > There are 14 patches in this series, all will be posted as a
> > > response
> > > to this one.  If anyone has any issues with these being applied,
> > > please
> > > let me know.
> > > 
> > > Responses should be made by Sun, 18 Oct 2020 09:04:25 +.
> > > Anything received after that time might be too late.
> > > 
> > > The whole patch series can be found in one patch at:
> > >   
> > > https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.8.16-rc1.gz
> > > or in the git tree and branch at:
> > >   git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-
> > > stable-rc.git linux-5.8.y
> > > and the diffstat can be found below.
> > > 
> > > thanks,
> 
> > [   10.718252] i8042: PNP: PS/2 appears to have AUX port disabled,
> > if
> > this is incorrect please boot with i8042.nopnp
> 
> Is this incorrect?
it seems to be incorrect for me, because the warning
disappeared when i passed i8042.nopnp to kernel.
-- 
software engineer
rajagiri school of engineering and technology

Re: [PATCH 5.8 00/14] 5.8.16-rc1 review

[Jeffrin Jose T]

On Fri, 2020-10-16 at 11:07 +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.8.16 release.
> There are 14 patches in this series, all will be posted as a response
> to this one.  If anyone has any issues with these being applied,
> please
> let me know.
> 
> Responses should be made by Sun, 18 Oct 2020 09:04:25 +.
> Anything received after that time might be too late.
> 
> The whole patch series can be found in one patch at:
>   
> https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.8.16-rc1.gz
> or in the git tree and branch at:
>   git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-
> stable-rc.git linux-5.8.y
> and the diffstat can be found below.
> 
> thanks,
> 
> greg k-h

hello,

Compiled and booted  5.8.16-rc1+ .Every thing looks clean except "dmesg
-l warn"

--x--x-x---

$dmesg -l warn
[0.601699] MDS CPU bug present and SMT on, data leak possible. See 
https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html for
more details.
[0.603104]  #3
[0.749457] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
[   10.718252] i8042: PNP: PS/2 appears to have AUX port disabled, if
this is incorrect please boot with i8042.nopnp
[   12.651483] sdhci-pci :00:1e.6: failed to setup card detect gpio
[   14.398378] i2c_hid i2c-ELAN1300:00: supply vdd not found, using
dummy regulator
[   14.399033] i2c_hid i2c-ELAN1300:00: supply vddl not found, using
dummy regulator
[   23.866580] systemd[1]: /lib/systemd/system/plymouth-
start.service:16: Unit configured to use KillMode=none. This is unsafe,
as it disables systemd's process lifecycle management for the service.
Please update your service to use a safer KillMode=, such as 'mixed' or
'control-group'. Support for KillMode=none is deprecated and will
eventually be removed.
[   37.208082] uvcvideo 1-6:1.0: Entity type for entity Extension 4 was
not initialized!
[   37.208092] uvcvideo 1-6:1.0: Entity type for entity Processing 2
was not initialized!
[   37.208098] uvcvideo 1-6:1.0: Entity type for entity Camera 1 was
not initialized!
[   40.088516] FAT-fs (sda1): Volume was not properly unmounted. Some
data may be corrupt. Please run fsck.
---x---x-x-

Tested-by: Jeffrin Jose T 
-- 
software engineer
rajagiri school of engineering and technology

Re: [PATCH 5.9 00/15] 5.9.1-rc1 review

[Jeffrin Jose T]

On Fri, 2020-10-16 at 11:08 +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.9.1 release.
> There are 15 patches in this series, all will be posted as a response
> to this one.  If anyone has any issues with these being applied,
> please
> let me know.
> 
> Responses should be made by Sun, 18 Oct 2020 09:04:25 +.
> Anything received after that time might be too late.
> 
> The whole patch series can be found in one patch at:
>   
> https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.9.1-rc1.gz
> or in the git tree and branch at:
>   git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-
> stable-rc.git linux-5.9.y
> and the diffstat can be found below.
> 
> thanks,
> 
> greg k-h

hello,

Compiled and booted 5.9.1-rc1+. Everything looks clean except "dmesg -l
warn"
This kernel like 5.8.13-rc1+  shows issue related in warning.
Please see this...

x-x-x-

$dmesg -l warn 
[0.589254] MDS CPU bug present and SMT on, data leak possible. See 
https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html for
more details.
[0.592523]  #3
[0.735219] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
[   11.454156] i8042: PNP: PS/2 appears to have AUX port disabled, if
this is incorrect please boot with i8042.nopnp
[   13.519401] sdhci-pci :00:1e.6: failed to setup card detect gpio
[   15.518853] i2c_hid i2c-ELAN1300:00: supply vdd not found, using
dummy regulator
[   15.520777] i2c_hid i2c-ELAN1300:00: supply vddl not found, using
dummy regulator
[   24.934891] systemd[1]: /lib/systemd/system/plymouth-
start.service:16: Unit configured to use KillMode=none. This is unsafe,
as it disables systemd's process lifecycle management for the service.
Please update your service to use a safer KillMode=, such as 'mixed' or
'control-group'. Support for KillMode=none is deprecated and will
eventually be removed.
[   38.110160] uvcvideo 1-6:1.0: Entity type for entity Extension 4 was
not initialized!
[   38.110166] uvcvideo 1-6:1.0: Entity type for entity Processing 2
was not initialized!
[   38.110170] uvcvideo 1-6:1.0: Entity type for entity Camera 1 was
not initialized!
[   41.031588] FAT-fs (sda1): Volume was not properly unmounted. Some
data may be corrupt. Please run fsck.

-x--------xx---

Tested-by: Jeffrin Jose T 

-- 
software engineer
rajagiri school of engineering and technology

Re: [PATCH 5.8 000/124] 5.8.15-rc1 review

[Jeffrin Jose T]

On Wed, 2020-10-14 at 11:56 +0200, Greg Kroah-Hartman wrote:
> On Mon, Oct 12, 2020 at 11:00:07PM +0530, Jeffrin Jose T wrote:
> >  * On Mon, 2020-10-12 at 15:30 +0200, Greg Kroah-Hartman wrote:
> > > This is the start of the stable review cycle for the 5.8.15
> > > release.
> > > There are 124 patches in this series, all will be posted as a
> > > response
> > > to this one.  If anyone has any issues with these being applied,
> > > please
> > > let me know.
> > > 
> > > Responses should be made by Wed, 14 Oct 2020 13:31:22 +.
> > > Anything received after that time might be too late.
> > > 
> > > The whole patch series can be found in one patch at:
> > >   
> > > https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.8.15-rc1.gz
> > > or in the git tree and branch at:
> > >   git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-
> > > stable-rc.git linux-5.8.y
> > > and the diffstat can be found below.
> > > 
> > > thanks,
> > > 
> > > greg k-h
> > 
> > hello,
> > 
> > Compiled and booted 5.8.15-rc1+ .  No typical dmesg regression.
> > I also  have something to mention here. I saw  a warning related in
> > several  kernels which looks like the following...
> > 
> > "MDS CPU bug present and SMT on, data leak possible"
> > 
> > But now in 5.8.15-rc1+ , that warning disappeared.
> 
> Odds are your microcode/bios finally got updated on that machine,
> right?
> 
i do not think thot the bios got updoted, becouse the bug is still
shown 
to be present in 5.8.13-rc1+  . so moy be the updoted kernel is fixing
the 
bug or gives  o workround.

-- 
software engineer
rajagiri school of engineering and technology

Re: [PATCH 5.8 000/124] 5.8.15-rc1 review

[Jeffrin Jose T]

 * On Mon, 2020-10-12 at 15:30 +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.8.15 release.
> There are 124 patches in this series, all will be posted as a
> response
> to this one.  If anyone has any issues with these being applied,
> please
> let me know.
> 
> Responses should be made by Wed, 14 Oct 2020 13:31:22 +.
> Anything received after that time might be too late.
> 
> The whole patch series can be found in one patch at:
>   
> https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.8.15-rc1.gz
> or in the git tree and branch at:
>   git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-
> stable-rc.git linux-5.8.y
> and the diffstat can be found below.
> 
> thanks,
> 
> greg k-h

hello,

Compiled and booted 5.8.15-rc1+ .  No typical dmesg regression.
I also  have something to mention here. I saw  a warning related in
several  kernels which looks like the following...

"MDS CPU bug present and SMT on, data leak possible"

But now in 5.8.15-rc1+ , that warning disappeared.

Tested-by: Jeffrin Jose T 

-- 
software engineer
rajagiri school of engineering and technology

Re: [PATCH 5.8 00/85] 5.8.14-rc1 review

[Jeffrin Jose T]

On Mon, 2020-10-05 at 17:25 +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.8.14 release.
> There are 85 patches in this series, all will be posted as a response
> to this one.  If anyone has any issues with these being applied,
> please
> let me know.
> 
> Responses should be made by Wed, 07 Oct 2020 14:20:55 +.
> Anything received after that time might be too late.
> 
> The whole patch series can be found in one patch at:
>   
> https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.8.14-rc1.gz
> or in the git tree and branch at:
>   git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-
> stable-rc.git linux-5.8.y
> and the diffstat can be found below.
> 
> thanks,
> 
> greg k-h

forgot to add...

Tested-by: Jeffrin Jose T 



-- 
software engineer
rajagiri school of engineering and technology

Re: [PATCH 5.8 00/85] 5.8.14-rc1 review

[Jeffrin Jose T]

On Mon, 2020-10-05 at 17:25 +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.8.14 release.
> There are 85 patches in this series, all will be posted as a response
> to this one.  If anyone has any issues with these being applied,
> please
> let me know.
> 
> Responses should be made by Wed, 07 Oct 2020 14:20:55 +.
> Anything received after that time might be too late.
> 
> The whole patch series can be found in one patch at:
>   
> https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.8.14-rc1.gz
> or in the git tree and branch at:
>   git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-
> stable-rc.git linux-5.8.y
> and the diffstat can be found below.
> 
> thanks,
> 
> greg k-h

hello,

compiled and booted 5.8.14-rc1+.
No dmesg regression compared to 5.8.13.

networking (wifi): functional (ok)
ssh : works (ok)
rsync of a large directory over ssh : works (ok)
git clone : functional (ok)
web browser: works (ok)
email: works (ok)
wget: functional (ok).
play audio/video files : functional (ok)

Base Board Information:
Manufacturer: ASUSTeK COMPUTER INC.
Product Name: X507UAR
Version: 1.0   
Serial Number: N0CV1847MB0006040
Asset Tag: ATN12345678901234567
Board is a hosting board
Board is replaceable
Location In Chassis: MIDDLE  
Chassis Handle: 0x0003
Type: Motherboard
Contained Object Handles: 0


-- 
software engineer
rajagiri school of engineering and technology

Re: [PATCH 5.8 00/99] 5.8.13-rc1 review

[Jeffrin Jose T]

On Tue, 2020-09-29 at 13:00 +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.8.13 release.
> There are 99 patches in this series, all will be posted as a response
> to this one.  If anyone has any issues with these being applied,
> please
> let me know.


Compiled and booted 5.8.13-rc1+ .
"dmesg -l err" did not report any error or errors.

Tested-by: Jeffrin Jose T  


-- 
software engineer
rajagiri school of engineering and technology

Re: [PATCH 5.8 00/56] 5.8.12-rc1 review

[Jeffrin Jose T]

On Fri, 2020-09-25 at 14:47 +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.8.12 release.
> There are 56 patches in this series, all will be posted as a response
> to this one.  If anyone has any issues with these being applied,
> please
> let me know.
> 
> Responses should be made by Sun, 27 Sep 2020 12:47:02 +.
> Anything received after that time might be too late.
> 
> The whole patch series can be found in on
> greg k-

Compiled and booted 5.8.12-rc1+ . "dmesg -l err" did not report any
error or errors.

Tested-by:  Jeffrin Jose T 


-- 
software engineer
rajagiri school of engineering and technology

TEST

[Jeffrin Jose T]

This is  test mail

[PATCH v2] selftests: netfilter: missing error check when setting up veth interface

[Jeffrin Jose T]

A test for  the basic NAT functionality uses ip command which
needs veth device.There is a condition where the kernel support
for veth is not compiled into the kernel and the test script
breaks.This patch contains code for reasonable error display
and correct code exit.

Signed-off-by: Jeffrin Jose T 
---
 tools/testing/selftests/netfilter/nft_nat.sh | 6 +-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/tools/testing/selftests/netfilter/nft_nat.sh 
b/tools/testing/selftests/netfilter/nft_nat.sh
index 8ec76681605c..f25f72a75cf3 100755
--- a/tools/testing/selftests/netfilter/nft_nat.sh
+++ b/tools/testing/selftests/netfilter/nft_nat.sh
@@ -23,7 +23,11 @@ ip netns add ns0
 ip netns add ns1
 ip netns add ns2
 
-ip link add veth0 netns ns0 type veth peer name eth0 netns ns1
+ip link add veth0 netns ns0 type veth peer name eth0 netns ns1 > /dev/null 2>&1
+if [ $? -ne 0 ];then
+echo "SKIP: No virtual ethernet pair device support in kernel"
+exit $ksft_skip
+fi
 ip link add veth1 netns ns0 type veth peer name eth0 netns ns2
 
 ip -net ns0 link set lo up
-- 
2.20.1

[PATCH] selftests : netfilter: Wrote a error and exit code for a command which needed veth kernel module.

[Jeffrin Jose T]

A test for  the basic NAT functionality uses ip command which
needs veth device.There is a condition where the kernel support
for veth is not compiled into the kernel and the test script
breaks.This patch contains code for reasonable error display
and correct code exit.

Signed-off-by: Jeffrin Jose T 
---
 tools/testing/selftests/netfilter/nft_nat.sh | 6 +-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/tools/testing/selftests/netfilter/nft_nat.sh 
b/tools/testing/selftests/netfilter/nft_nat.sh
index 8ec76681605c..f25f72a75cf3 100755
--- a/tools/testing/selftests/netfilter/nft_nat.sh
+++ b/tools/testing/selftests/netfilter/nft_nat.sh
@@ -23,7 +23,11 @@ ip netns add ns0
 ip netns add ns1
 ip netns add ns2
 
-ip link add veth0 netns ns0 type veth peer name eth0 netns ns1
+ip link add veth0 netns ns0 type veth peer name eth0 netns ns1 > /dev/null 2>&1
+if [ $? -ne 0 ];then
+echo "SKIP: No virtual ethernet pair device support in kernel"
+exit $ksft_skip
+fi
 ip link add veth1 netns ns0 type veth peer name eth0 netns ns2
 
 ip -net ns0 link set lo up
-- 
2.20.1

[PATCH v2] selftests: kmod: worked on errors which breaks the overall execution of the test script. i have manually edited for v2 of the patch by changing the date and also commit log.

[Jeffrin Jose T]

The kmod.sh script breaks because an array is passed as input
instead of a single element input.This patch takes elements
one at a time and passed as input to the condition statement
which in turn fixes the error.There was an issue which had
the need for passing a single digit to the condition statement
which is fixed using regular expression.
Distribution: Debian GNU/Linux buster/sid
Bash Version: 5.0.0(1)-release

Signed-off-by: Jeffrin Jose T 
---
 tools/testing/selftests/kmod/kmod.sh | 9 ++---
 1 file changed, 6 insertions(+), 3 deletions(-)

diff --git a/tools/testing/selftests/kmod/kmod.sh 
b/tools/testing/selftests/kmod/kmod.sh
index 0a76314b4414..49b273c3646e 100755
--- a/tools/testing/selftests/kmod/kmod.sh
+++ b/tools/testing/selftests/kmod/kmod.sh
@@ -526,9 +526,12 @@ function run_all_tests()
TEST_ID=${i%:*:*}
ENABLED=$(get_test_enabled $TEST_ID)
TEST_COUNT=$(get_test_count $TEST_ID)
-   if [[ $ENABLED -eq "1" ]]; then
-   test_case $TEST_ID $TEST_COUNT
-   fi
+   for j in $ENABLED ; do
+CHECK=${j#*:*:}
+if [[ $CHECK -eq "1" ]]; then
+test_case $TEST_ID $TEST_COUNT
+fi
+   done
done
 }
 
-- 
2.20.1

[PATCH] selftests: kmod: worked on errors which breaks the overall execution of the test script

[Jeffrin Jose T]

The kmod.sh script breaks because an array is passed as input
instead of a single element input.This patch takes elements
one at a time and passed as input to the condition statement
which in turn fixes the error.There was an issue which had
the need for passing a single digit to the condition statement
which is fixed using regular expression.

Signed-off-by: Jeffrin Jose T 
---
 tools/testing/selftests/kmod/kmod.sh | 9 ++---
 1 file changed, 6 insertions(+), 3 deletions(-)

diff --git a/tools/testing/selftests/kmod/kmod.sh 
b/tools/testing/selftests/kmod/kmod.sh
index 0a76314b4414..49b273c3646e 100755
--- a/tools/testing/selftests/kmod/kmod.sh
+++ b/tools/testing/selftests/kmod/kmod.sh
@@ -526,9 +526,12 @@ function run_all_tests()
TEST_ID=${i%:*:*}
ENABLED=$(get_test_enabled $TEST_ID)
TEST_COUNT=$(get_test_count $TEST_ID)
-   if [[ $ENABLED -eq "1" ]]; then
-   test_case $TEST_ID $TEST_COUNT
-   fi
+   for j in $ENABLED ; do
+CHECK=${j#*:*:}
+if [[ $CHECK -eq "1" ]]; then
+test_case $TEST_ID $TEST_COUNT
+fi
+   done
done
 }
 
-- 
2.20.1

[RESEND PATCH] selftests: intel_pstate: notification about privilege required to run intel_pstate testing script

[Jeffrin Jose T]

The intel_pstate related testing script need root level privileges
when trying to access certain file for the successful execution of
the script.But this is not the case always like when using evaluation
only mode, which only require user level privilege.

This patch is to notify the user about the privilege the script
demands for the successful execution of the test.

Signed-off-by: Jeffrin Jose T (Rajagiri SET) 
---
 tools/testing/selftests/intel_pstate/run.sh | 6 ++
 1 file changed, 6 insertions(+)

diff --git a/tools/testing/selftests/intel_pstate/run.sh 
b/tools/testing/selftests/intel_pstate/run.sh
index 8576f6564307..e7008f614ad7 100755
--- a/tools/testing/selftests/intel_pstate/run.sh
+++ b/tools/testing/selftests/intel_pstate/run.sh
@@ -38,6 +38,12 @@ if ! uname -m | sed -e s/i.86/x86/ -e s/x86_64/x86/ | grep 
-q x86; then
exit $ksft_skip
 fi
 
+msg="skip all tests:"
+if [ $UID != 0 ] && [ $EVALUATE_ONLY == 0 ]; then
+echo $msg please run this as root >&2
+exit $ksft_skip
+fi
+
 max_cpus=$(($(nproc)-1))
 
 function run_test () {
-- 
2.17.0

[RESEND PATCH] selftests: intel_pstate: notification about privilege required to run intel_pstate testing script

[Jeffrin Jose T]

The intel_pstate related testing script need root level privileges
when trying to access certain file for the successful execution of
the script.But this is not the case always like when using evaluation
only mode, which only require user level privilege.

This patch is to notify the user about the privilege the script
demands for the successful execution of the test.

Signed-off-by: Jeffrin Jose T (Rajagiri SET) 
---
 tools/testing/selftests/intel_pstate/run.sh | 6 ++
 1 file changed, 6 insertions(+)

diff --git a/tools/testing/selftests/intel_pstate/run.sh 
b/tools/testing/selftests/intel_pstate/run.sh
index 8576f6564307..e7008f614ad7 100755
--- a/tools/testing/selftests/intel_pstate/run.sh
+++ b/tools/testing/selftests/intel_pstate/run.sh
@@ -38,6 +38,12 @@ if ! uname -m | sed -e s/i.86/x86/ -e s/x86_64/x86/ | grep 
-q x86; then
exit $ksft_skip
 fi
 
+msg="skip all tests:"
+if [ $UID != 0 ] && [ $EVALUATE_ONLY == 0 ]; then
+echo $msg please run this as root >&2
+exit $ksft_skip
+fi
+
 max_cpus=$(($(nproc)-1))
 
 function run_test () {
-- 
2.17.0

[PATCH] [RESEND] selftest: intel_pstate: debug support message from aperf.c and return value fix.

[Jeffrin Jose T]

Additional message along with an error message which is more
verbose for debug support from aperf.c and updated with the
new return value "KSFT_SKIP".

Signed-off-by: Jeffrin Jose T [Rajagiri SET] 
---
 tools/testing/selftests/intel_pstate/aperf.c | 6 --
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/tools/testing/selftests/intel_pstate/aperf.c 
b/tools/testing/selftests/intel_pstate/aperf.c
index d21edea9c560..f6cd03a87493 100644
--- a/tools/testing/selftests/intel_pstate/aperf.c
+++ b/tools/testing/selftests/intel_pstate/aperf.c
@@ -9,6 +9,8 @@
 #include 
 #include 
 #include 
+#include 
+#include "../kselftest.h"
 
 void usage(char *name) {
printf ("Usage: %s cpunum\n", name);
@@ -41,8 +43,8 @@ int main(int argc, char **argv) {
fd = open(msr_file_name, O_RDONLY);
 
if (fd == -1) {
-   perror("Failed to open");
-   return 1;
+   printf("/dev/cpu/%d/msr: %s\n", cpu, strerror(errno));
+   return KSFT_SKIP;
}
 
CPU_ZERO();
-- 
2.17.0

[PATCH] [RESEND] selftest: intel_pstate: debug support message from aperf.c and return value fix.

[Jeffrin Jose T]

Additional message along with an error message which is more
verbose for debug support from aperf.c and updated with the
new return value "KSFT_SKIP".

Signed-off-by: Jeffrin Jose T [Rajagiri SET] 
---
 tools/testing/selftests/intel_pstate/aperf.c | 6 --
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/tools/testing/selftests/intel_pstate/aperf.c 
b/tools/testing/selftests/intel_pstate/aperf.c
index d21edea9c560..f6cd03a87493 100644
--- a/tools/testing/selftests/intel_pstate/aperf.c
+++ b/tools/testing/selftests/intel_pstate/aperf.c
@@ -9,6 +9,8 @@
 #include 
 #include 
 #include 
+#include 
+#include "../kselftest.h"
 
 void usage(char *name) {
printf ("Usage: %s cpunum\n", name);
@@ -41,8 +43,8 @@ int main(int argc, char **argv) {
fd = open(msr_file_name, O_RDONLY);
 
if (fd == -1) {
-   perror("Failed to open");
-   return 1;
+   printf("/dev/cpu/%d/msr: %s\n", cpu, strerror(errno));
+   return KSFT_SKIP;
}
 
CPU_ZERO();
-- 
2.17.0

[PATCH] selftests: intel_pstate: notification about privilege required to run intel_pstate testing script

[Jeffrin Jose T]

The intel_pstate related testing script need root level privileges
when trying to access certain file for the successful execution of
the script.But this is not the case always like when using evaluation
only mode, which only require user level privilege.

This patch is to notify the user about the privilege the script
demands for the successful execution of the test.

Signed-off-by: Jeffrin Jose T (Rajagiri SET) <ahiliat...@gmail.com>
---
 tools/testing/selftests/intel_pstate/run.sh | 6 ++
 1 file changed, 6 insertions(+)

diff --git a/tools/testing/selftests/intel_pstate/run.sh 
b/tools/testing/selftests/intel_pstate/run.sh
index 6ded61670f6d..4ddd389c2cb9 100755
--- a/tools/testing/selftests/intel_pstate/run.sh
+++ b/tools/testing/selftests/intel_pstate/run.sh
@@ -33,6 +33,12 @@ EVALUATE_ONLY=0
 # Kselftest framework requirement - SKIP code is 4.
 ksft_skip=4
 
+msg="skip all tests:"
+if [ $UID != 0 ] && [ $EVALUATE_ONLY == 0 ]; then
+echo $msg please run this as root >&2
+exit $ksft_skip
+fi
+
 if ! uname -m | sed -e s/i.86/x86/ -e s/x86_64/x86/ | grep -q x86; then
echo "$0 # Skipped: Test can only run on x86 architectures."
exit $ksft_skip
-- 
2.17.0

[PATCH] selftests: intel_pstate: notification about privilege required to run intel_pstate testing script

[Jeffrin Jose T]

The intel_pstate related testing script need root level privileges
when trying to access certain file for the successful execution of
the script.But this is not the case always like when using evaluation
only mode, which only require user level privilege.

This patch is to notify the user about the privilege the script
demands for the successful execution of the test.

Signed-off-by: Jeffrin Jose T (Rajagiri SET) 
---
 tools/testing/selftests/intel_pstate/run.sh | 6 ++
 1 file changed, 6 insertions(+)

diff --git a/tools/testing/selftests/intel_pstate/run.sh 
b/tools/testing/selftests/intel_pstate/run.sh
index 6ded61670f6d..4ddd389c2cb9 100755
--- a/tools/testing/selftests/intel_pstate/run.sh
+++ b/tools/testing/selftests/intel_pstate/run.sh
@@ -33,6 +33,12 @@ EVALUATE_ONLY=0
 # Kselftest framework requirement - SKIP code is 4.
 ksft_skip=4
 
+msg="skip all tests:"
+if [ $UID != 0 ] && [ $EVALUATE_ONLY == 0 ]; then
+echo $msg please run this as root >&2
+exit $ksft_skip
+fi
+
 if ! uname -m | sed -e s/i.86/x86/ -e s/x86_64/x86/ | grep -q x86; then
echo "$0 # Skipped: Test can only run on x86 architectures."
exit $ksft_skip
-- 
2.17.0

TEST mail

[Jeffrin Jose T]

TEST MAIL

Signed-off-by: Jeffrin Jose T  <ahiliat...@gmail.com>
---
 tools/testing/selftests/intel_pstate/run.sh | 6 ++
 1 file changed, 6 insertions(+)

diff --git a/tools/testing/selftests/intel_pstate/run.sh 
b/tools/testing/selftests/intel_pstate/run.sh
index 6ded61670f6d..4ddd389c2cb9 100755
--- a/tools/testing/selftests/intel_pstate/run.sh
+++ b/tools/testing/selftests/intel_pstate/run.sh
@@ -33,6 +33,12 @@ EVALUATE_ONLY=0
 # Kselftest framework requirement - SKIP code is 4.
 ksft_skip=4
 
+msg="skip all tests:"
+if [ $UID != 0 ] && [ $EVALUATE_ONLY == 0 ]; then
+echo $msg please run this as root >&2
+exit $ksft_skip
+fi
+
 if ! uname -m | sed -e s/i.86/x86/ -e s/x86_64/x86/ | grep -q x86; then
echo "$0 # Skipped: Test can only run on x86 architectures."
exit $ksft_skip
-- 
2.17.0

TEST mail

[Jeffrin Jose T]

TEST MAIL

Signed-off-by: Jeffrin Jose T  
---
 tools/testing/selftests/intel_pstate/run.sh | 6 ++
 1 file changed, 6 insertions(+)

diff --git a/tools/testing/selftests/intel_pstate/run.sh 
b/tools/testing/selftests/intel_pstate/run.sh
index 6ded61670f6d..4ddd389c2cb9 100755
--- a/tools/testing/selftests/intel_pstate/run.sh
+++ b/tools/testing/selftests/intel_pstate/run.sh
@@ -33,6 +33,12 @@ EVALUATE_ONLY=0
 # Kselftest framework requirement - SKIP code is 4.
 ksft_skip=4
 
+msg="skip all tests:"
+if [ $UID != 0 ] && [ $EVALUATE_ONLY == 0 ]; then
+echo $msg please run this as root >&2
+exit $ksft_skip
+fi
+
 if ! uname -m | sed -e s/i.86/x86/ -e s/x86_64/x86/ | grep -q x86; then
echo "$0 # Skipped: Test can only run on x86 architectures."
exit $ksft_skip
-- 
2.17.0