Bug#700739: Kernel panic - not syncing: Fatal exception in interrupt

To: ben@decadent.org.uk
Cc: 700739@bugs.debian.org
Subject: Bug#700739: Kernel panic - not syncing: Fatal exception in interrupt
From: Kubo Hiroshi <h-kubo@geisya.or.jp>
Date: Tue, 26 Feb 2013 01:42:17 +0900 (JST)
Message-id: <[🔎] 20130226.014217.274437003.h-kubo@geisya.or.jp>
Reply-to: Kubo Hiroshi <h-kubo@geisya.or.jp>, 700739@bugs.debian.org
In-reply-to: <[🔎] 20130223.224441.191210039.h-kubo@geisya.or.jp>
References: <[🔎] 20130222.233714.492728149.h-kubo@geisya.or.jp> <[🔎] 1361571569.29126.100.camel@deadeye.wl.decadent.org.uk> <[🔎] 20130223.224441.191210039.h-kubo@geisya.or.jp>

Hi.

>> Do the functions 'i8xx_irq_handler' and 'queue_work_on' always appear in
>> the call trace?
> 
> I can't remember. If I encounter the problem again, 
> I will check it.

After the last reply, I encountered the same problems twice.
In the both problems, the functions 'i8xx_irq_handler' and
 'queue_work_on' appeared in the call trace.

---
Kubo Hiroshi <h-kubo@geisya.or.jp>

Reply to:

References:
- Bug#700739: Kernel panic - not syncing: Fatal exception in interrupt
  - From: Kubo Hiroshi <h-kubo@geisya.or.jp>
- Bug#700739: Kernel panic - not syncing: Fatal exception in interrupt
  - From: Ben Hutchings <ben@decadent.org.uk>
- Bug#700739: Kernel panic - not syncing: Fatal exception in interrupt
  - From: Kubo Hiroshi <h-kubo@geisya.or.jp>

Prev by Date: Bug#701643: linux-image-2.6.32-5-amd64: échec en écriture lors d'une copie de buffer pour backend dpkg-deb
Next by Date: Bug#701643: marked as done (linux-image-2.6.32-5-amd64: échec en écriture lors d'une copie de buffer pour backend dpkg-deb)
Previous by thread: Bug#700739: Kernel panic - not syncing: Fatal exception in interrupt
Next by thread: Bug#700739: Kernel panic - not syncing: Fatal exception in interrupt
Index(es):
- Date
- Thread