mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Johannes Erdfelt <johannes@erdfelt.com>
To: Heitzso <xxh1@cdc.gov>
Cc: "'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: Re: usb broken in 2.4.0 test 12 versus 2.2.18
Date: Mon, 18 Dec 2000 16:41:03 -0500	[thread overview]
Message-ID: <20001218164101.D1627@sventech.com> (raw)
In-Reply-To: <B7F9A3E3FDDDD11185510000F8BDBBF2019C79D3@mcdc-atl-5.cdc.gov>
In-Reply-To: <B7F9A3E3FDDDD11185510000F8BDBBF2019C79D3@mcdc-atl-5.cdc.gov>; from Heitzso on Mon, Dec 18, 2000 at 04:33:26PM -0500

On Mon, Dec 18, 2000, Heitzso <xxh1@cdc.gov> wrote:
> I have a Canon usb camera that I access via a
> recent copy of the s10sh program (with -u option).
> 
> Getting to the camera via s10sh -u worked through 
> large sections of 2.4.0 test X but broke recently.  
> I cannot say for certain which test/patch the 
> break occurred in.
> 
> Running 2.4.0 test12 malloc errors appear.
> Everything is fine with 2.2.18.  I haven't tried
> the test13 series of patches.  
> 
> key .config options:
>  CONFIG_USB on
>  DEVICEFS on
>  HOTPLUG on
>  UHCI on
> everything else off (i.e. printers, keyboards,
> mice, etc.). 
> 
> Baseline system is RH6.2 with most patches applied
> (so avoiding RH7 compiler problems).  Basic dev
> environment is same (i.e. compiling the two kernels
> on the same box).
> 
> If someone wants to email me a debug sequence or
> ask more specific questions feel free.

Could you give us the exact error message you saw?

JE

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2000-12-18 22:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-18 21:33 Heitzso
2000-12-18 21:41 ` Johannes Erdfelt [this message]
2000-12-18 22:00 ` bert hubert

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=20001218164101.D1627@sventech.com \
    --to=johannes@erdfelt.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xxh1@cdc.gov \
    /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®