From: Kalle Valo <kvalo@qca.qualcomm.com> To: <greearb@candelatech.com> Cc: <ath10k@lists.infradead.org>, <linux-wireless@vger.kernel.org> Subject: Re: [PATCH 1/4] ath10k: provide firmware crash info via debugfs. Date: Fri, 6 Jun 2014 09:55:37 +0300 [thread overview] Message-ID: <87bnu6msra.fsf@kamboji.qca.qualcomm.com> (raw) In-Reply-To: <1401904902-5842-1-git-send-email-greearb@candelatech.com> (greearb@candelatech.com's message of "Wed, 4 Jun 2014 11:01:39 -0700") greearb@candelatech.com writes: > From: Ben Greear <greearb@candelatech.com> > > Store the firmware crash registers and last 128 or so > firmware debug-log ids and present them to user-space > via debugfs. > > Should help with figuring out why the firmware crashed. > > Signed-off-by: Ben Greear <greearb@candelatech.com> [...] > + dump_data->kernel_ver_code = LINUX_VERSION_CODE; > + strncpy(dump_data->kernel_ver, VERMAGIC_STRING, > + sizeof(dump_data->kernel_ver) - 1); Other thing nice to have here is the kernel timestamp in the kernel log "[123456.4321]". How difficult would it be to add that to the dump? -- Kalle Valo
WARNING: multiple messages have this Message-ID (diff)
From: Kalle Valo <kvalo@qca.qualcomm.com> To: greearb@candelatech.com Cc: linux-wireless@vger.kernel.org, ath10k@lists.infradead.org Subject: Re: [PATCH 1/4] ath10k: provide firmware crash info via debugfs. Date: Fri, 6 Jun 2014 09:55:37 +0300 [thread overview] Message-ID: <87bnu6msra.fsf@kamboji.qca.qualcomm.com> (raw) In-Reply-To: <1401904902-5842-1-git-send-email-greearb@candelatech.com> (greearb@candelatech.com's message of "Wed, 4 Jun 2014 11:01:39 -0700") greearb@candelatech.com writes: > From: Ben Greear <greearb@candelatech.com> > > Store the firmware crash registers and last 128 or so > firmware debug-log ids and present them to user-space > via debugfs. > > Should help with figuring out why the firmware crashed. > > Signed-off-by: Ben Greear <greearb@candelatech.com> [...] > + dump_data->kernel_ver_code = LINUX_VERSION_CODE; > + strncpy(dump_data->kernel_ver, VERMAGIC_STRING, > + sizeof(dump_data->kernel_ver) - 1); Other thing nice to have here is the kernel timestamp in the kernel log "[123456.4321]". How difficult would it be to add that to the dump? -- Kalle Valo _______________________________________________ ath10k mailing list ath10k@lists.infradead.org http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2014-06-06 6:56 UTC|newest] Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-06-04 18:01 [PATCH 1/4] ath10k: provide firmware crash info via debugfs greearb 2014-06-04 18:01 ` greearb 2014-06-04 18:01 ` [PATCH 2/4] ath10k: save firmware debug log messages greearb 2014-06-04 18:01 ` greearb 2014-06-04 18:01 ` [PATCH 3/4] ath10k: save firmware stack upon firmware crash greearb 2014-06-04 18:01 ` greearb 2014-06-04 18:01 ` [PATCH 4/4] ath10k: Dump exception stack contents on " greearb 2014-06-04 18:01 ` greearb 2014-06-05 16:18 ` [PATCH 1/4] ath10k: provide firmware crash info via debugfs Kalle Valo 2014-06-05 16:18 ` Kalle Valo 2014-06-05 18:25 ` Ben Greear 2014-06-05 18:25 ` Ben Greear 2014-06-06 6:10 ` Kalle Valo 2014-06-06 6:10 ` Kalle Valo 2014-06-06 6:30 ` Michal Kazior 2014-06-06 6:30 ` Michal Kazior 2014-06-06 8:55 ` Kalle Valo 2014-06-06 8:55 ` Kalle Valo 2014-06-06 9:45 ` Michal Kazior 2014-06-06 9:45 ` Michal Kazior 2014-06-06 16:11 ` Ben Greear 2014-06-06 16:11 ` Ben Greear 2014-06-07 12:55 ` Kalle Valo 2014-06-07 12:55 ` Kalle Valo 2014-06-07 15:32 ` Ben Greear 2014-06-07 15:32 ` Ben Greear 2014-06-08 8:28 ` Kalle Valo 2014-06-08 8:28 ` Kalle Valo 2014-06-08 15:40 ` Ben Greear 2014-06-08 15:40 ` Ben Greear 2014-06-06 6:55 ` Kalle Valo [this message] 2014-06-06 6:55 ` Kalle Valo 2014-06-06 16:01 ` Ben Greear 2014-06-06 16:01 ` Ben Greear 2014-06-07 12:50 ` Kalle Valo 2014-06-07 12:50 ` Kalle Valo 2014-06-06 9:33 ` Kalle Valo 2014-06-06 9:33 ` Kalle Valo 2014-06-06 17:06 ` Ben Greear 2014-06-06 17:06 ` Ben Greear 2014-06-07 12:57 ` Kalle Valo 2014-06-07 12:57 ` Kalle Valo 2014-06-07 15:29 ` Ben Greear 2014-06-07 15:29 ` Ben Greear 2014-06-08 8:12 ` Kalle Valo 2014-06-08 8:12 ` Kalle Valo
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=87bnu6msra.fsf@kamboji.qca.qualcomm.com \ --to=kvalo@qca.qualcomm.com \ --cc=ath10k@lists.infradead.org \ --cc=greearb@candelatech.com \ --cc=linux-wireless@vger.kernel.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.