On 09/23/18 17:19, Thomas Gleixner wrote:
Other than RTFM, or please build a bunch of kernels from source on your slow
machine, using differing config options to help track down the cause of
this...any thoughts about a solution?
Yes. This was decoded recently as an issue on 32bit due to a c
On 09/24/18 02:23, Thomas Gleixner wrote:
No that thing does not affect 64bit for sure. Can you please provide me a
full dmesg from that machine?
Will do. See attached dmesg.txt file
[0.00] Linux version 4.18.7-100.fc27.x86_64
(mockbu...@bkernel04.phx2.fedoraproject.org) (gcc
On 09/23/18 17:19, Thomas Gleixner wrote:
What is that value for the second Athlon core (seems extremely bogus), and
would/could that be the reason for the schedule_timeouts? This bogus value
also shows up in the bootup log when the second core is activated. Seems to
be AMD specific, as t
Please CC me on comments.
I'm seeing a lot of these errors on my dual core fileserver:
---
Sep 23 01:51:28 files kernel: INFO: rcu_sched detected stalls on CPUs/tasks:
Sep 23 01:51:28 files kernel: 1-...!: (0 ticks thi
y the base baud rate in setserial from a
startup script. Having the additional ports at BAUD 0 (unusable) until
some explicit action is taken strikes me as a safer option, provided
this gets properly documented in the kernel Documentation directory and
in Linux HOWTO docs.
-Rob Prowel
Russell King wrote:
On Mon, Feb 26, 2007 at 12:02:57PM -0500, Rob Prowel wrote:
See below for a (script) dump of that demonstrates the behavior I
describe. Additional ports are not configurable until a driver such as
fourport is loaded. This is in 2.6.20.1 and 2.6.17 (those versions I
Stuart MacDonald wrote:
I use the options below:
CONFIG_SERIAL_8250=y
CONFIG_SERIAL_8250_CONSOLE=y
CONFIG_SERIAL_8250_PCI=y
CONFIG_SERIAL_8250_NR_UARTS=32
This makes the internal table be 32 ports big. The first four ports
end up configured for legacy/standard com ports, the rest are
unco
Thanks so much for your followup.
Russell King wrote:
On Fri, Feb 23, 2007 at 12:05:48PM -0500, Rob Prowel wrote:
At least now, with fourport compiled into the kernel,
You don't even need to do that. Just configure SERIAL_8250_NR_UARTS
and SERIAL_8250_RUNTIME_UARTS appropri
6 7 8 9 a b c d e f
00: ff ff ff ff 00 ff ff ff ff ff ff ff ff ff ff ff
-bash-3.1#
I would so much appreciate if someone intimately familiar with the
serial drivers could enlighten me as to what is going on here.
I'm not registered on the kernel list so CC to my email address wou
le not an error, per se, it is kind of sloppy and
it is amazing that it hasn't shown up before now.
using the identifier "new" in kernel headers that are
visible to applications programs is a bad idea.
Thanks,
Rob Prowel
___
10 matches
Mail list logo
