Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #61888 > unrolled thread

Regression in 4.17 Kernels (?)

Back to article view | Back to linux.debian.kernel

Contents

  Regression in 4.17 Kernels (?) Rainer Dorsch <ml@bokomoko.de> - 2018-08-22 19:00 +0200
    Re: Regression in 4.17 Kernels (?) Yves-Alexis Perez <corsac@debian.org> - 2018-08-23 12:00 +0200
      Re: Regression in 4.17 Kernels (?) Rainer Dorsch <ml@bokomoko.de> - 2018-08-23 13:20 +0200
        Re: Regression in 4.17 Kernels (?) Yves-Alexis Perez <corsac@debian.org> - 2018-08-23 14:00 +0200
          Re: Regression in 4.17 Kernels (?) Rainer Dorsch <ml@bokomoko.de> - 2018-08-23 14:30 +0200
            Re: Regression in 4.17 Kernels (?) Yves-Alexis Perez <corsac@debian.org> - 2018-08-24 11:20 +0200
              Re: Regression in 4.17 Kernels (?) Rainer Dorsch <ml@bokomoko.de> - 2018-08-25 12:20 +0200
      Re: Regression in 4.17 Kernels (?) jose R Rodriguez <jose.r.r@metztli.com> - 2018-08-24 09:10 +0200
        Re: Regression in 4.17 Kernels (?) Yves-Alexis Perez <corsac@debian.org> - 2018-08-24 09:20 +0200

#61888 — Regression in 4.17 Kernels (?)

[Multipart message — attachments visible in raw view] — view raw

Hi,

I have a strange issue with 4.17 kernels:

When I run my scanner (Fujitsu fi-4220C2) using gscan2pdf/sane, the system reboots 
spontaneously after the first page, there is no log entry, no Oops, nothing, here are lines 
from kern.log (timestamps are too far apart for a spontaneous reboot):

Aug 22 18:26:33 b370 kernel: [ 3118.972889] perf: interrupt took too long (3993 > 3976), 
lowering kernel.perf_event_max_sample_rate to 50000
Aug 22 18:42:27 b370 kernel: [    0.000000] Linux version 4.17.0-3-amd64 (debian-
kernel@lists.debian.org) (gcc version 7.3.0 (Debian 7.3.0-28)) #1 SMP Debian 4.17.17-1 
(2018-08-18)

The issue seems to be 100% reproducible with the 4.17 kernels I tried on my system:

root@b370:~# dpkg --get-selections |grep linux-image-4.17 

Any idea what happens here is welcome.

Should I open a bug report? If yes, which data should I include?

Thanks
Rainer

-- 
Rainer Dorsch
http://bokomoko.de/

[toc] | [next] | [standalone]

#61893

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On Wed, 2018-08-22 at 18:57 +0200, Rainer Dorsch wrote:
> The issue seems to be 100% reproducible with the 4.17 kernels I tried on my
> system:

Hi,

is it OK with other kernels?

Regards,
- -- 
Yves-Alexis
-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAlt+hP0ACgkQ3rYcyPpX
RFuFzggAy+U/KGJJf3Tv+aFcrYkYpq5UsEaI7hjHzsnpfgqwwpM51ErIqi8HeTO6
M652r0Ha9tsbvsyIq7Wa7Fu7Z9VjZ23mM+SKiLDve3jiM8nIYmjX9JFyjcFq0Smb
g8baM7qs3MmodFMH/RqlXFxp3HqPIKph4NnaYBFjbvKop3PfKzRItzpqFtGW3jJn
zXRJwbBEgNASwJhuwY78dsBsBx4/m+MFGRb6ME+8Ol+lKayAx7F7L24xmFm5vLg6
8f3oebZ+JHQhJvFn8MrBOfnBlxOCmM9O8dbu0g+TvRKc3B1rN5trKzzpY59pLkPA
LY3+YEll2W6BM4uZm+2Uo7NzVUwvTQ==
=YnA3
-----END PGP SIGNATURE-----

[toc] | [prev] | [next] | [standalone]

#61896

Am Donnerstag, 23. August 2018, 11:57:17 CEST schrieb Yves-Alexis Perez:
> On Wed, 2018-08-22 at 18:57 +0200, Rainer Dorsch wrote:
> > The issue seems to be 100% reproducible with the 4.17 kernels I tried on
> > my
> 
> > system:
> Hi,
> 
> is it OK with other kernels?

Yes, I have never seen that with 4.16 and any kernel I used before. I run not 
4.16.

Rainer
-- 
Rainer Dorsch
http://bokomoko.de/

[toc] | [prev] | [next] | [standalone]

#61897

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On Thu, 2018-08-23 at 13:17 +0200, Rainer Dorsch wrote:
> Yes, I have never seen that with 4.16 and any kernel I used before. I run not 
> 4.16.

Sorry I'm a bit unsure how to read the last sentence. Can you retry right now
with 4.16 kernel (and changing only that) and report back? It's possible that
there is a regression in the USB handling in the 4.17 kernel but we'd need a
bit more information to confirm that.

Regards,
- -- 
Yves-Alexis
-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAlt+oDwACgkQ3rYcyPpX
RFvuLAf/f8qVwnDNzB4z0B3/Q93Uc7JQlJsLqAcstdWLgxYgoiO0+m4LuwHscfde
bWLF+MxSfU3+LsgzbzfPPHohUfxdQ4VYa5bD0BUzgowBBuKy0IvFytIwN8b0lH4r
3FCRenR8MK9f+ic0UvPTIS/T9Rg24xrbL6A96RIYKfiByuicKzG0rPW5SbVTgXnL
QxzRcxNw3+uhus0S8SGtiT7G+rYi+27agCcrC0EYPyZP6HSrYV1YybPn7W5FmToB
OQJLEij3OmSO44Qraohga6P5IsOD6/I+bkmkmkT6sSv8qT+1t60unx281K5KA9d9
MIUIwl1i47gSvCBxdpgBIf3gO5Y/DA==
=I5LU
-----END PGP SIGNATURE-----

[toc] | [prev] | [next] | [standalone]

#61898

Hi Yves-Alexis,

Am Donnerstag, 23. August 2018, 13:53:32 CEST schrieb Yves-Alexis Perez:
> On Thu, 2018-08-23 at 13:17 +0200, Rainer Dorsch wrote:
> > Yes, I have never seen that with 4.16 and any kernel I used before. I run
> > not 4.16.
> 
> Sorry I'm a bit unsure how to read the last sentence. Can you retry right
> now with 4.16 kernel (and changing only that) and report back? It's
> possible that there is a regression in the USB handling in the 4.17 kernel
> but we'd need a bit more information to confirm that.

Sorry, this was a typo, I meant

I run *now* 4.16 [again].

...and I did not observe the issue.

Feel free to ask, I am sorry that I did not provide more information, but 
since there is nothing in the log files, nothing on the screen, it is hard for 
me to provide anything useful. I could switch to a VT which the scanner is 
running shortly before the crash, but not sure if that helps.

Rainer



-- 
Rainer Dorsch
http://bokomoko.de/

[toc] | [prev] | [next] | [standalone]

#61901

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On Thu, 2018-08-23 at 14:20 +0200, Rainer Dorsch wrote:
> Feel free to ask, I am sorry that I did not provide more information, but 
> since there is nothing in the log files, nothing on the screen, it is hard for 
> me to provide anything useful. I could switch to a VT which the scanner is 
> running shortly before the crash, but not sure if that helps.

If you manage to reproduce the crash that way, I guess it would help yes. It
might help to increase the dmesg log verbosity too.

If vt switch is not enough, you might want to try using ssh or netconsole.

Regards,
- -- 
Yves-Alexis
-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAlt/y/8ACgkQ3rYcyPpX
RFt0/wf/aDkcDb15t7iM/8KVAOBBFJl8slxxXX3CeJMM4jyb4rcicU5ovPzkI0le
uRidL+xJN4ovWlR+8Jm+dwvZ0s2c5lNwpTwpRnspn6GF4UEil1+TzLequDyVxgHc
jE1L7vXX0jyPcFSWLEs7lpmVbxrr/w2T2sxLBRJG9/C22qjqpdJccC/5EfHWHBPI
mc17Cin+7g2l+wsX+yzph+uxwS/s82glyDls872iMBnw0MtW5NieuhFOCP2LJBTD
5D62bC3qvP7k0Ma+APlcRutfC27tzVr79i3QnAkMoqHiFyUd3oz3c8HVlbOXIjn7
jehTB+x+flhEN0WKwAHuZtMrIYL3fw==
=CHjj
-----END PGP SIGNATURE-----

[toc] | [prev] | [next] | [standalone]

#61906

Am Freitag, 24. August 2018, 11:12:31 schrieb Yves-Alexis Perez:
> On Thu, 2018-08-23 at 14:20 +0200, Rainer Dorsch wrote:
> > Feel free to ask, I am sorry that I did not provide more information, but
> > since there is nothing in the log files, nothing on the screen, it is hard
> > for me to provide anything useful. I could switch to a VT which the
> > scanner is running shortly before the crash, but not sure if that helps.
> 
> If you manage to reproduce the crash that way, I guess it would help yes. It
> might help to increase the dmesg log verbosity too.
> 
> If vt switch is not enough, you might want to try using ssh or netconsole.
> 

Thanks for the pointer to netconsole and ssh....I will give it a try, as soon 
as I have physical access to the system again. Will take a few days...

Rainer

[toc] | [prev] | [next] | [standalone]

#61899

On Thu, 2018-08-23 at 11:57 +0200, Yves-Alexis Perez wrote:
> On Wed, 2018-08-22 at 18:57 +0200, Rainer Dorsch wrote:
> > The issue seems to be 100% reproducible with the 4.17 kernels I
> > tried on my
> > system:
> 
> Hi,
> 
> is it OK with other kernels?
> 
FYI I also experienced one sudden reboot yesterday with Linux kernel
built 'the Debian way' from debian source 4.17.17-1. Only difference is
my kernels are reiser4 -patched and modified to be built with GCC6 for
stretch-backports.

Notwithstanding, I was not using USB scanner, but my development
machine was under increased CPU/fan load due to evolution email client
running -- downloading thousands of messages. Weird but this
application causes *that*.

However, after the machine rebooted, I built the kernel again but this
time I applied the upstream kernel.org delta patch-4.17.17-18 and
everything seems to fine today. Yes, still experienced an initial
increased CPU/fan use early during evolution mail fetching fewer
messages but no hangs, reboots, etc. As a matter of fact, my fan is now
quiet, i.e., not agitated.

dpkg --get-selections |grep linux-image-4.17
linux-image-4.17.0-1+reiser4.0.2-amd64          install
linux-image-4.17.0-3+reiser4.0.2-amd64          install

uname -a
Linux huitzilopochtli 4.17.0-3+reiser4.0.2-amd64 #1 SMP Debian 4.17.18-
1+reiser4.0.2 (2018-08-23) x86_64 GNU/Linux
> Regards,

Best Professional Regards.



-- 
Jose R R
http://metztli.it
---------------------------------------------------------------------
------------------------
Download Metztli Reiser4: Debian Stretch w/ Linux 4.17 AMD64
---------------------------------------------------------------------
------------------------
feats ZSTD compression https://sf.net/projects/metztli-reiser4/
---------------------------------------------------------------------
----------------------
Official current Reiser4 resources: https://reiser4.wiki.kernel.org/

[toc] | [prev] | [next] | [standalone]

#61900

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On Thu, 2018-08-23 at 23:46 -0700, jose R Rodriguez wrote:
> FYI I also experienced one sudden reboot yesterday with Linux kernel
> built 'the Debian way' from debian source 4.17.17-1. Only difference is
> my kernels are reiser4 -patched and modified to be built with GCC6 for
> stretch-backports.

Hi Jose,

I'm sorry but I don't think we can do anything with that, especially without
any log from the reboot. It's different enough from our kernels that it's
basically unsupported.

Regards,
- -- 
Yves-Alexis
-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAlt/r8MACgkQ3rYcyPpX
RFsYnwgAu4qtjiDjZNqPmd5WGi7wuDQX86OeqVtWEK8jSq2CLfqHkc8/PErlj68b
N6WAarVgs7Xrow9nIKGWqoSSwp3pbuRaKeOIEDZ6reVru+NyfQnI57BbXozeNkeH
nojxlcRWP0MGgU0dHJ4/FkXkdVE4FObPCexlxPTn8t2Bn9XSfW/4XsliOoG0peTD
is3GYpJsIDWxrlp0SrNtgJIg7aXi6rPnWKs6KMqZnM9dgwYBgkeG/tRk9GM4xRGJ
POMC2eAORGrht0c4xB33fB/RkC2aVebwsjIFd7gqO4jMPjv+nB4IqKpeOmz+SHYY
lB33+RlmcfQHkxYBqFM5WUrUOHOcrw==
=tWh7
-----END PGP SIGNATURE-----

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web