From: Joel Soete <joel.soete@freebel.net>
To: parisc-linux@lists.parisc-linux.org
Subject: [parisc-linux] jfs-1.0.23 as well xfs-cvs break fb console on k-2.4.19-pa22
Date: Sat, 19 Oct 2002 19:45:35 +0000 [thread overview]
Message-ID: <3DB1B65F.5020203@freebel.net> (raw)
In-Reply-To: 3DA56CAE00003256@ocpmta8.be.tiscali.com
Funny isn't it?
Excepted those anoying problem all seems to work fine (I already
sucessfully tested a jfs fs (over a evms lvm) and still have to test a xfs).
Really no idea?
Joel
jsoe0708@tiscali.be wrote:
>>-- Original Message --
>>From: jsoe0708@tiscali.be
>>Subject: RE: [parisc-linux] FW: [Bug #3332] jfs-1.0.22 and 1.0.23 break
>
> fb
>
>>console on k-2.4.19-pa22
>>To: parisc-linux@lists.parisc-linux.org
>>Date: Fri, 18 Oct 2002 16:43:08 +0200
>>
>>
>>
>>>Hi all,
>>>
>>>May be much hppa specific problem.
>>>
>>>All advise is well come.
>>>
>>>Thanks in advance,
>>> Joel
>>>
>>>--- Start of the Attached Message ---
>>>
>>>Date: Thu, 17 Oct 2002 12:47:30 -0400
>>>To: joel.soete@tiscali.be
>>>Subject: [Bug #3332] jfs-1.0.22 and 1.0.23 break fb console on k-2.4.19-pa22
>>>From: admin@www-124.southbury.usf.ibm.com
>>>
>>>
>>>Bug #3332 has been submitted pending email address confirmation.
>>>Here is a current snapshot of the bug.
>>>
>>>Project:
>>>Category: kernel
>>>Status: Open
>>>Bug Group: bug
>>>Priority: 5
>>>Summary: jfs-1.0.22 and 1.0.23 break fb console on k-2.4.19-pa22
>>>
>>>Details: Hi all,
>>>
>>>Test your tools, I test early with success 1.0.17 (against k-2.4.18-pa54
>>>and latter).
>>
>>
>>Hmm I was wrong: I come back to jfs-2.4-1.0.17 against k-2.4.19-pa22 and
>>the problem is the same. So the actual problem is a change between 2.4.18(pa54)
>>and 2.4.19(pa22).
>>
>>Any idea?
>
>
> 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?
>
>
>>>Just an anoying problem the fb console is broken:
>>>just when kernel launches to detect the first scsi device the screen scroll
>>>stop and the rest of messages are all display over others on the very
>>
> top
>
>>>line of the screen.
>>>
>>
> Thanks in advance for help,
> Joel
>
> _______________________________________________
> parisc-linux mailing list
> parisc-linux@lists.parisc-linux.org
> http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
>
next prev parent reply other threads:[~2002-10-19 18: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 ` Joel Soete [this message]
2002-10-20 3:44 ` [parisc-linux] jfs-1.0.23 as well xfs-cvs " Grant Grundler
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=3DB1B65F.5020203@freebel.net \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox