All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joshua Kwan <joshk@ludicrus.ath.cx>
To: linux-kernel@vger.kernel.org
Cc: akpm@digeo.com, dilinger@voxel.net
Subject: Re: 2.5.59-mm6
Date: Mon, 27 Jan 2003 00:24:53 -0800	[thread overview]
Message-ID: <20030127082452.GA18747@ludicrus.ath.cx> (raw)
In-Reply-To: <pan.2003.01.27.08.17.50.697367@voxel.net>

[-- Attachment #1: Type: text/plain, Size: 1261 bytes --]

On Mon, Jan 27, 2003 at 03:17:54AM -0500, Andres Salomon wrote:
> This one boots for me (with devfs enabled).  I got some rather interesting
> stack dumps, however, during boot.

I'm experiencing similar problems without devfs...

> Warning! Detected 2173 micro-second gap between interrupts.
>   Compensating for 1 lost ticks.
> Call Trace:
>  [<c010b8a8>] handle_IRQ_event+0x38/0x60
>  [<c010bade>] do_IRQ+0xae/0x160
>  [<c0105000>] _stext+0x0/0x30
>  [<c010a150>] common_interrupt+0x18/0x20
>  [<c0105000>] _stext+0x0/0x30

Each of these warnings reproduces for each input device on my system 
(there are 3 now, so if i disconnect, say, my USB mouse, there will be 
only 2.)

In other news (this happened in -mm5, not sure if this happened to 
others or not:)

Hangcheck: starting hangcheck timer 0.5.0 (tick is 180 seconds, margin 
is 60 seconds).
Uninitialised timer!
This is just a warning.  Your computer is OK
function=0xc0216100, data=0x0
Call Trace:
 [<c0121ce1>] check_timer_failed+0x61/0x70
 [<c0216100>] hangcheck_fire+0x0/0xc0
 [<c0121e5f>] mod_timer+0x2f/0x180
 [<c0105075>] init+0x35/0x160
 [<c0105040>] init+0x0/0x160
 [<c010713d>] kernel_thread_helper+0x5/0x18

No visible problems though, at all.

-Josh

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2003-01-27  8:15 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-27  7:10 2.5.59-mm6 Andrew Morton
2003-01-27  7:10 ` 2.5.59-mm6 Andrew Morton
2003-01-27  8:17 ` 2.5.59-mm6 Andres Salomon
2003-01-27  8:24   ` Joshua Kwan [this message]
2003-01-27  8:40     ` 2.5.59-mm6 Andrew Morton
2003-01-27  8:46       ` 2.5.59-mm6 Joshua Kwan
2003-01-27  9:51 ` 2.5.59-mm6 Helge Hafting
2003-01-27  9:51   ` 2.5.59-mm6 Helge Hafting
  -- strict thread matches above, loose matches on Subject: below --
2003-01-27 12:27 2.5.59-mm6 Luuk van der Duim
2003-01-27 18:50 ` 2.5.59-mm6 Mike Galbraith
2003-01-27 19:17   ` 2.5.59-mm6 Zwane Mwaikambo
     [not found]   ` <Pine.LNX.4.44.0301271414230.28141-100000@montezuma.mastece nde.com>
2003-01-27 20:11     ` 2.5.59-mm6 Mike Galbraith
2003-01-27 21:13       ` 2.5.59-mm6 Zwane Mwaikambo

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=20030127082452.GA18747@ludicrus.ath.cx \
    --to=joshk@ludicrus.ath.cx \
    --cc=akpm@digeo.com \
    --cc=dilinger@voxel.net \
    --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 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.