Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Randolph Chung <randolph@tausq.org>
To: jsoe0708@tiscali.be
Cc: Grant Grundler <grundler@dsl2.external.hp.com>,
	Joel Soete <joel.soete@freebel.net>,
	parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] jfs-1.0.23 as well xfs-cvs break fb console on k-2.4.19-pa22
Date: Mon, 21 Oct 2002 09:42:54 -0700	[thread overview]
Message-ID: <20021021164254.GW5602@tausq.org> (raw)
In-Reply-To: <3DA56CAE00003DB5@ocpmta8.be.tiscali.com>

> it sounds like a gcc bug:
> 
> simply adding "printk("VC: %s: %d\n", __FUNCTION__, __LINE__);" some where
> in the middle of take_over_console (to check the way) and the problem is
> solved???

unlikely a gcc bug, more likely is that the code has some timing
dependencies and adding printk changed the timing.

randolph
--  
Randolph Chung
Debian GNU/Linux Developer, hppa/ia64 ports
http://www.tausq.org/

  reply	other threads:[~2002-10-21 16:39 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-17 17:48 [parisc-linux] FW: [Bug #3332] jfs-1.0.22 and 1.0.23 break fb console on k-2.4.19-pa22 jsoe0708
2002-10-18 14:43 ` jsoe0708
2002-10-18 14:07   ` [parisc-linux] Linux version 2.4.19-pa22 uname -a fault phi
2002-10-18 15:41     ` Thibaut VARENE
2002-10-18 15:57       ` Randolph Chung
2002-10-18 17:02   ` [parisc-linux] jfs-1.0.22 and 1.0.23 break fb console on k-2.4.19-pa22 jsoe0708
2002-10-19 19:45     ` [parisc-linux] jfs-1.0.23 as well xfs-cvs " Joel Soete
2002-10-20  3:44       ` Grant Grundler
2002-10-21 14:43         ` jsoe0708
2002-10-21 16:42           ` Randolph Chung [this message]
2002-10-21 17:48             ` jsoe0708
2002-10-21 16:46           ` John David Anglin
2002-10-22 15:02             ` Michael S.Zick
2002-10-22 15:36               ` John David Anglin
2002-10-23  5:54                 ` jsoe0708
2002-10-23 15:01                   ` John David Anglin
2002-10-24  5:44                     ` jsoe0708
2002-10-24 16:23                       ` John David Anglin

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=20021021164254.GW5602@tausq.org \
    --to=randolph@tausq.org \
    --cc=grundler@dsl2.external.hp.com \
    --cc=joel.soete@freebel.net \
    --cc=jsoe0708@tiscali.be \
    --cc=parisc-linux@lists.parisc-linux.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