lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <F7C43F8B2814514CA05F3436BC68046EF2297D@039-SN2MPN1-013.039d.mgd.msft.net>
Date:	Fri, 28 Jun 2013 16:58:58 +0000
From:	Stehle Vincent-B46079 <B46079@...escale.com>
To:	Stephen Boyd <sboyd@...eaurora.org>
CC:	Thomas Gleixner <tglx@...utronix.de>,
	"linux-next@...r.kernel.org" <linux-next@...r.kernel.org>,
	John Stultz <john.stultz@...aro.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Mark Rutland <mark.rutland@....com>
Subject: RE: next-20130627 breaks i.MX6 sabre sd UART console

From: linux-next-owner@...r.kernel.org [mailto:linux-next-owner@...r.kernel.org] On Behalf Of Stephen Boyd
(..)
> Do you have debug_ll support to get some serial logs?

Hi,

Thanks for your concern on the matter. You are right, there is debug_ll support for i.MX6. If I activate it for next-20130628 imx_v6_v7_defconfig, that only "buys" me one additional line, though:

  Uncompressing Linux... done, booting the kernel.

> Also could you try booting with maxcpus=1 on the kernel commandline?

Good idea; it goes much further with this one (until it crashes in wm8962_probe(), which is as far as I go when I revert 064706514ec3fea740c2656e03c4f01f6a551ac4).

> And it would be useful to have the output of /proc/timer_list if you have it from a working device.

Sure; I pasted it below.

> I believe you have a per-cpu TWD timer and a global imx-gpt?

I think you are right from what I see in /proc/interrupts.

> Can you try this patch? (sorry about the whitespace damage)

Sorry, this patch had no visible effect.

Best regards,

V.

--- /proc/timer_list ---
Timer List Version: v0.7
HRTIMER_MAX_CLOCK_BASES: 4
now at 104544862569 nsecs

cpu: 0
 clock 0:
  .base:       80fcc5a0
  .index:      0
  .resolution: 1 nsecs
  .get_time:   ktime_get
  .offset:     0 nsecs
active timers:
 #0: <80fcc720>, tick_sched_timer, S:01
 # expires at 104550000000-104550000000 nsecs [in 5138067 to 5138067 nsecs]
 #1: <bf869a98>, hrtimer_wakeup, S:01
 # expires at 108088808660-108093808657 nsecs [in 3543946727 to 3548946724 nsecs]
 #2: <bf27df28>, hrtimer_wakeup, S:01
 # expires at 152209022299-152209072299 nsecs [in 47664160366 to 47664210366 nsecs]
 #3: <bfb91910>, it_real_fn, S:01
 # expires at 389697029617-389697029617 nsecs [in 285152167684 to 285152167684 nsecs]
 #4: <bf305a98>, hrtimer_wakeup, S:01
 # expires at 86489728463860-86489828463860 nsecs [in 86385183601927 to 86385283601927 nsecs]
 clock 1:
  .base:       80fcc5d8
  .index:      1
  .resolution: 1 nsecs
  .get_time:   ktime_get_real
  .offset:     31109466222080 nsecs
active timers:
 clock 2:
  .base:       80fcc610
  .index:      2
  .resolution: 1 nsecs
  .get_time:   ktime_get_boottime
  .offset:     0 nsecs
active timers:
 clock 3:
  .base:       80fcc648
  .index:      3
  .resolution: 1 nsecs
  .get_time:   ktime_get_clocktai
  .offset:     31109466222080 nsecs
active timers:
  .expires_next   : 104550000000 nsecs
  .hres_active    : 1
  .nr_events      : 4632
  .nr_retries     : 0
  .nr_hangs       : 0
  .max_hang_time  : 0 nsecs
  .nohz_mode      : 2
  .last_tick      : 104530000000 nsecs
  .tick_stopped   : 0
  .idle_jiffies   : 4294947748
  .idle_calls     : 12180
  .idle_sleeps    : 1193
  .idle_entrytime : 104542811418 nsecs
  .idle_waketime  : 104531758281 nsecs
  .idle_exittime  : 104531841675 nsecs
  .idle_sleeptime : 81643279539 nsecs
  .iowait_sleeptime: 5577955342 nsecs
  .last_jiffies   : 4294947750
  .next_jiffies   : 4294947751
  .idle_expires   : 104560000000 nsecs
jiffies: 4294947750

Tick Device: mode:     1
Broadcast device
Clock Event Device: <NULL>
tick_broadcast_mask: 00000000
tick_broadcast_oneshot_mask: 00000000

Tick Device: mode:     1
Per CPU device: 0
Clock Event Device: mxc_timer1
 max_delta_ns:   65075261923
 min_delta_ns:   3863
 mult:           141733921
 shift:          31
 mode:           3
 next_event:     104550000000 nsecs
 set_next_event: v2_set_next_event
 set_mode:       mxc_set_mode
 event_handler:  hrtimer_interrupt
 retries:        0


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ