From: Grant Grundler <grundler@dsl2.external.hp.com>
To: Joel Soete <joel.soete@freebel.net>
Cc: 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: Sat, 19 Oct 2002 21:44:03 -0600 [thread overview]
Message-ID: <20021020034403.AF4F14829@dsl2.external.hp.com> (raw)
In-Reply-To: Message from Joel Soete <joel.soete@freebel.net> of "Sat, 19 Oct 2002 19:45:35 -0000." <3DB1B65F.5020203@freebel.net>
Joel Soete wrote:
> The very first patch 2.4.19 I still have was pa5 and the same problem occur.
> It seems definitely that JFS and STI FB in 2.4.19 are incompatible.
> Where do I have to start my investigation?
...
> Really no idea?
Sorry. I don't. And until 2.4.19 boots on the A500-6X,
I'm not interested in chasing the JFS/STI issue.
My advice is to start adding printk's in the main vfs_ops entry
points to JFS until you can narrow down which entry point is
having problems. Then start looking STI to see if anything
in the JFS code uses the same services or something.
grant
next prev parent reply other threads:[~2002-10-20 3:44 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 [this message]
2002-10-21 14:43 ` jsoe0708
2002-10-21 16:42 ` Randolph Chung
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=20021020034403.AF4F14829@dsl2.external.hp.com \
--to=grundler@dsl2.external.hp.com \
--cc=joel.soete@freebel.net \
--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 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.