On Wed, Aug 1, 2018 at 10:55 PM, Guenter Roeck wrote:
> On Wed, Aug 01, 2018 at 10:46:06PM +0530, Ivid Suvarna wrote:
>> On Wed, Aug 1, 2018 at 6:49 PM, Guenter Roeck wrote:
>> > On 08/01/2018 05:35 AM, Ivid Suvarna wrote:
>> >>
>> >> Hi,
>> &g
On Wed, Aug 1, 2018 at 10:55 PM, Guenter Roeck wrote:
> On Wed, Aug 01, 2018 at 10:46:06PM +0530, Ivid Suvarna wrote:
>> On Wed, Aug 1, 2018 at 6:49 PM, Guenter Roeck wrote:
>> > On 08/01/2018 05:35 AM, Ivid Suvarna wrote:
>> >>
>> >> Hi,
>> &g
On Wed, Aug 1, 2018 at 6:49 PM, Guenter Roeck wrote:
> On 08/01/2018 05:35 AM, Ivid Suvarna wrote:
>>
>> Hi,
>>
>> When pstore is enabled and a *pr_info(any printk) in
>> __memcpy_toio(arch/arm64/kernel/io.c)* is added, kernel wont boot and
>> just ha
On Wed, Aug 1, 2018 at 6:49 PM, Guenter Roeck wrote:
> On 08/01/2018 05:35 AM, Ivid Suvarna wrote:
>>
>> Hi,
>>
>> When pstore is enabled and a *pr_info(any printk) in
>> __memcpy_toio(arch/arm64/kernel/io.c)* is added, kernel wont boot and
>> just ha
Hi,
When pstore is enabled and a *pr_info(any printk) in
__memcpy_toio(arch/arm64/kernel/io.c)* is added, kernel wont boot and
just hangs.
The path where __memcpy_toio is called is below:
->persistent_ram_update
-> memcpy_toio
-> __memcpy_toio
I tried with trace_printk and kernel boots
Hi,
When pstore is enabled and a *pr_info(any printk) in
__memcpy_toio(arch/arm64/kernel/io.c)* is added, kernel wont boot and
just hangs.
The path where __memcpy_toio is called is below:
->persistent_ram_update
-> memcpy_toio
-> __memcpy_toio
I tried with trace_printk and kernel boots
Hi All,
Could you please provide some sample test module for causing a
Softlockup and Hardlockup in latest kernel for SMP for testing
purposes. I assume there are some Kconfigs to be enabled as well for
this.
I had tried with the module where I put a busy loop inside spinlock
but was not able to
Hi All,
Could you please provide some sample test module for causing a
Softlockup and Hardlockup in latest kernel for SMP for testing
purposes. I assume there are some Kconfigs to be enabled as well for
this.
I had tried with the module where I put a busy loop inside spinlock
but was not able to
Hi Greg,
> 4.1.15 is a kernel that is very old and obsolete (released almost 3
> years ago, and tens of thousands of changes old.) Please try something
> newer and more modern like 4.15. If the issue is still there, the
> community will be glad to help you out.
>
> If you are stuck at that old
Hi Greg,
> 4.1.15 is a kernel that is very old and obsolete (released almost 3
> years ago, and tens of thousands of changes old.) Please try something
> newer and more modern like 4.15. If the issue is still there, the
> community will be glad to help you out.
>
> If you are stuck at that old
Hi All,
Facing below warning backtrace during resume from suspend to disk. I
am using 4.1.15 freescale kernel. After this warning there is a huge
time gap (nearly 10 sec) between Enabling non-boot cpus and CPU1 being
up. Any pointers on this would be helpful.
[ 545.227081] Hardware name:
Hi All,
Facing below warning backtrace during resume from suspend to disk. I
am using 4.1.15 freescale kernel. After this warning there is a huge
time gap (nearly 10 sec) between Enabling non-boot cpus and CPU1 being
up. Any pointers on this would be helpful.
[ 545.227081] Hardware name:
Hi All,
I was going through usb serial driver console related source code
(drivers/usb/serial/console.c) in linux kernel and came across
"usb_console_write" function and was wondering if any usb serial
convertor drivers were using this function? If so any pointers on how
it is being used?
Also
Hi All,
I was going through usb serial driver console related source code
(drivers/usb/serial/console.c) in linux kernel and came across
"usb_console_write" function and was wondering if any usb serial
convertor drivers were using this function? If so any pointers on how
it is being used?
Also
On Tue, Nov 7, 2017 at 9:19 PM, Alan Stern <st...@rowland.harvard.edu> wrote:
> On Tue, 7 Nov 2017, Ivid Suvarna wrote:
>
>> Hi,
>>
>> I am trying to support suspend to disk(hibernate) on Hikey with 4.4
>> kernel. During suspend, I could see the usb devices ge
On Tue, Nov 7, 2017 at 9:19 PM, Alan Stern wrote:
> On Tue, 7 Nov 2017, Ivid Suvarna wrote:
>
>> Hi,
>>
>> I am trying to support suspend to disk(hibernate) on Hikey with 4.4
>> kernel. During suspend, I could see the usb devices getting reset and I
>> c
Hi,
I am trying to support suspend to disk(hibernate) on Hikey with 4.4
kernel. During suspend, I could see the usb devices getting reset and I
can access them properly. Message can be seen as below:
usb 1-1: reset high-speed USB device number 2 using dwc2
usb 1-1.2: reset high-speed USB device
Hi,
I am trying to support suspend to disk(hibernate) on Hikey with 4.4
kernel. During suspend, I could see the usb devices getting reset and I
can access them properly. Message can be seen as below:
usb 1-1: reset high-speed USB device number 2 using dwc2
usb 1-1.2: reset high-speed USB device
Hi all,
I am trying to support suspend to disk(hibernate) on Hikey with 4.4
kernel. During suspend, I could see the usb devices getting reset and I
can access them properly. Message can be seen as below:
usb 1-1: reset high-speed USB device number 2 using dwc2
usb 1-1.2: reset high-speed USB
Hi all,
I am trying to support suspend to disk(hibernate) on Hikey with 4.4
kernel. During suspend, I could see the usb devices getting reset and I
can access them properly. Message can be seen as below:
usb 1-1: reset high-speed USB device number 2 using dwc2
usb 1-1.2: reset high-speed USB
20 matches
Mail list logo
