From: Marc Giger <gigerstyle@gmx.ch>
To: Marc Giger <gigerstyle@gmx.ch>
Cc: "Ivan Kokshaysky" <ink@jurassic.park.msu.ru>,
linux-xfs@oss.sgi.com, "Måns Rullgård" <mru@kth.se>,
linux-kernel@vger.kernel.org
Subject: Re: status of Linux on Alpha?
Date: Tue, 27 Apr 2004 18:51:24 +0200 [thread overview]
Message-ID: <20040427185124.134073cd@vaio.gigerstyle.ch> (raw)
In-Reply-To: <20040413194907.7ce8ceb7@vaio.gigerstyle.ch>
Hi,
What's the current status of the problem? Is nobody interested to fix
it, or am I just impatient? Did I provide not enough information?
I'm running 2.6.5 with the reverted patch for 2 weeks now without any
problems.
Regards
Marc
On Tue, 13 Apr 2004 19:49:07 +0200
Marc Giger <gigerstyle@gmx.ch> wrote:
> Hi Ivan, All
>
> First, sorry for the cross posting...
>
> After long sessions of patching, recompiling, and testing I finally
> found the cause of my problems. XFS people, please read:
> http://marc.theaimsgroup.com/?l=linux-kernel&m=108047692409817&w=2
> and
> http://marc.theaimsgroup.com/?l=linux-kernel&m=107910319729364&w=2
>
> After reverting 1.1608.29.12 all is fine again.
> Interestingly, this patch was listed on bkbits between 2.6.3
> and 2.6.4-rc1 but was added to the source tree between 2.6.4-rc1 and
> 2.6.4-rc2 :-( Again something learned for the future...
>
> Ivan, I think your new semaphore code is still ok because it doesn't
> matter if it is the new or old code. Both versions have a problem with
> the xfs-patch.
>
> For further questions you know how to reach me:-)
>
> greets
>
> Marc
>
>
> On Fri, 9 Apr 2004 23:06:51 +0400
> Ivan Kokshaysky <ink@jurassic.park.msu.ru> wrote:
>
> > On Fri, Apr 09, 2004 at 01:48:28PM +0200, Marc Giger wrote:
> > > > Presently, I reached a stage on which I don't know longer what
> > > > to do:-( I isolated the problem between 2.6.3-rc1 and 2.6.3-rc2.
> > > > I
> > > ^^^^^^^^^^^^^^^^^^^^^^^
> > > read as 2.6.4-rc1 and 2.6.4-rc2
> >
> > Thanks for your work.
> >
> > > > also reverted 1.1608.56.1 , 1.1608.51.36 and all xfs related
> > > > patches from rc2 with no luck.
> > > > All other changes seems unrelated to me.
> >
> > I'd also revert 1.1608.51.22 and all networking changes.
> >
> > Ivan.
> >
>
>
next prev parent reply other threads:[~2004-04-27 16:51 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-28 12:26 Måns Rullgård
2004-03-28 16:17 ` Ivan Kokshaysky
2004-03-28 16:19 ` Måns Rullgård
2004-03-28 16:43 ` Ivan Kokshaysky
2004-03-28 20:18 ` Marc Giger
2004-03-28 20:36 ` Måns Rullgård
2004-03-29 18:52 ` Marc Giger
2004-04-04 10:10 ` Marc Giger
2004-04-09 11:45 ` Marc Giger
2004-04-09 11:48 ` Marc Giger
2004-04-09 19:06 ` Ivan Kokshaysky
2004-04-13 17:49 ` Marc Giger
2004-04-27 16:51 ` Marc Giger [this message]
2004-04-27 17:23 ` Eric Sandeen
2004-04-27 17:57 ` Marc Giger
2004-04-27 17:55 ` Ivan Kokshaysky
2004-04-27 18:08 ` Marc Giger
2004-04-27 20:20 ` Ivan Kokshaysky
2004-04-27 20:42 ` Marc Giger
2004-04-27 21:27 ` Ivan Kokshaysky
2004-04-28 6:00 ` Nathan Scott
2004-04-28 13:13 ` Dru
2004-04-28 13:29 ` Måns Rullgård
2004-04-28 14:09 ` Ivan Kokshaysky
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=20040427185124.134073cd@vaio.gigerstyle.ch \
--to=gigerstyle@gmx.ch \
--cc=ink@jurassic.park.msu.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@oss.sgi.com \
--cc=mru@kth.se \
/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
all inboxes | Powered by JetHome®