public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Frank <mhf@linuxmail.org>
To: Keith Owens <kaos@sgi.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.22 hangs upon echo > /proc/acpi/alarm
Date: Fri, 14 Nov 2003 02:24:43 +0800	[thread overview]
Message-ID: <200311140224.43459.mhf@linuxmail.org> (raw)
In-Reply-To: <2758.1068686462@kao2.melbourne.sgi.com>

On Thursday 13 November 2003 09:21, Keith Owens wrote:
> On Wed, 12 Nov 2003 20:33:18 +0800, 
> Michael Frank <mhf@linuxmail.org> wrote:
> >ACPI version is 20031002
> >
> >Initial backtrace obtained with kdb:
> >
> >acpi_os_read_port+36
> >acpi_hw_lowlevel_read+7b
> >acpi_ev_gpe_detect+94
> >acpi_ev_sci_xrupt_handler+3c
> >acpi_irq+d
> >handle_IRQ_event+31
> >do_IRQ+72
> >call_do_IRQ+5
> >do_softirq+5a
> >do_IRQ+a1
> >proc_file_write+9b
> >sys_write+be
> >system_call+33
> >
> >Further stepping shows endless loop around:
> >
> >acpi_ev_gpe_detect+80
> >  acpi_hw_lowlevel_read
> >    acpi_os_read_port
> >    acpi_ut_get_region_name
> >    acpi_ut_debug_print 
> >  acpi_ut_debug_print
> >  jmp acpi_ev_gpe_detect+80
> >
> >Debugging is compiled in, but no meesages go to dmesg
> >
> >How to enable acpi_ut_debug_print output?
> 
> printk() can be called from anywhere but the text is only stored in the
> log buffer.  The text is written from the log buffer to the console or
> syslog when the kernel is not running in interrupt context.  This is a
> common problem with printk, you get no output when debugging interrupt
> problems.
> 
> Since you have already applied the kdb patch, change acpi to add
> #include <linux/kdb.h> and call kdb_printf() instead of printk for
> debugging messages.  kdb_printf uses polling mode I/O so you get the
> output immediately.
> 

Thank you for your reply. I'll make good use of kdb_printf in future.

In this case however the messages did not even go into the dmesg buffer
as the acpi debug output (via its own printf) must be enabled by debug 
section flags which were disabled. I'll file a bug report against acpi asap.

I have two questions about kdb 3.0, x86 hw on 2.4.22 kernel

 - is there any netpoll interface for kdb for legacy free hw wo serial port.
 - on another non-acpi machine kdb hangs permanently and blinking kbleds stop once 
    - any key is pressed on the at keyboard 
    - after about a minute inside kdb (operating via serial port)


Regards
Michael


  reply	other threads:[~2003-11-13 18:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-12 12:33 2.4.22 hangs upon echo > /proc/acpi/alarm Michael Frank
2003-11-13  1:21 ` Keith Owens
2003-11-13 18:24   ` Michael Frank [this message]
2003-11-14  1:20     ` Keith Owens
     [not found] <Retd.1TR.7@gated-at.bofh.it>
     [not found] ` <RuoB.4pK.25@gated-at.bofh.it>
2003-11-14  0:03   ` Karol Kozimor

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=200311140224.43459.mhf@linuxmail.org \
    --to=mhf@linuxmail.org \
    --cc=kaos@sgi.com \
    --cc=linux-kernel@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: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox