From: "Peter A. Goodall" <pete@ximian.com>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Seg fault when syncing Sony Clie 760 with USB cradle
Date: 02 Nov 2001 17:57:44 -0500 [thread overview]
Message-ID: <1004741864.7016.35.camel@colobus.ximian.com> (raw)
In-Reply-To: <20011025205538.A25032@kroah.com>
In-Reply-To: <1004062619.1406.29.camel@localhost.localdomain> <20011025205538.A25032@kroah.com>
On Thu, 2001-10-25 at 23:55, Greg KH wrote:
> On Thu, Oct 25, 2001 at 10:16:59PM -0400, Peter A. Goodall wrote:
> > I am running Redhat 7.1 with the 2.4.12 kernel and using xfs. I have
> > applied an SGI patch (linux-2.4.12-xfs-2001-10-11.patch.bz2) to run
> > xfs. I am using coldsync 2.2.0 to sync and everytime I try to sync it I
> > get a seg fault. This causes a kernel panic and I am no longer able to
> > use the USB port until I reboot. Below is the end of /var/log/messages:
>
> Does the oops happen at the end of the sync, or at the beginning?
>
> Can you run that oops through ksymoops for me?
>
> thanks,
>
> greg k-h
I noticed that my last kernel was not behaving correctly. Specifically
that nfs (unrelated) and devfs were not starting correctly. I upgraded
to the 2.4.13 kernel and paid special attention to those two items. Now
syncing with Coldsync no longer causes a kernel panic. It just doesn't
work. It can't communicate with the Clie to get the serial number and
other information. Since I'm using devfs I can't say it is the kernel.
I will have to test it further.
- PAG
--
Pete Goodall
Support Tech
Ximian, Inc.
pete@ximian.com
next prev parent reply other threads:[~2001-11-02 22:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-26 2:16 Seg fault when syncing Sony Clie 760 with USB cradle Peter A. Goodall
2001-10-26 3:55 ` Greg KH
2001-10-26 21:16 ` Peter A. Goodall
2001-11-02 22:57 ` Peter A. Goodall [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-11-07 0:34 James Funkhouser
2001-11-07 3:13 ` Greg KH
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=1004741864.7016.35.camel@colobus.ximian.com \
--to=pete@ximian.com \
--cc=greg@kroah.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox