problem with USB cdc-acm
Wim de Vries
I am trying to connect a (serial) USB device to my asus eee pc 900 with
Dedian.
The device connects OK on my HP compaq 6910p with Suse 10.3:
dmesg:
usb 7-1: new full speed USB device using uhci_hcd and address 4
usb 7-1: new device found, idVendor=04d8, idProduct=000a
usb 7-1: new device strings: Mfr=1, Product=2, SerialNumber=3
usb 7-1: Product: PIC18 USB CDC
usb 7-1: Manufacturer: Microchip
usb 7-1: SerialNumber: V1.1FS
usb 7-1: configuration #1 chosen from 1 choice
drivers/usb/class/cdc-acm.c: This device cannot do calls on its own. It
is no modem.
cdc_acm 7-1:1.0: ttyACM0: USB ACM device
so it should ánd can use cdc-acm
on the eee pc (the cdc-acm module is installed):
[ 216.648044] usb 2-1: new full speed USB device using uhci_hcd and address 4
[ 216.704127] hub 2-0:1.0: unable to enumerate USB device on port 1
[ 217.888078] usb 2-1: new full speed USB device using uhci_hcd and address 5
[ 218.031991] usb 2-1: device descriptor read/all, error -71
[ 218.088093] hub 2-0:1.0: unable to enumerate USB device on port 1
[ 219.128078] usb 2-1: new full speed USB device using uhci_hcd and address 7
[ 219.277888] usb 2-1: unable to read config index 0 descriptor/all
[ 219.277888] usb 2-1: can't read configurations, error -71
[ 219.336093] hub 2-0:1.0: unable to enumerate USB device on port 1
[ 220.368043] usb 2-1: new full speed USB device using uhci_hcd and address 9
[ 220.424086] hub 2-0:1.0: unable to enumerate USB device on port 1
[ 221.608071] usb 2-1: new full speed USB device using uhci_hcd and address 10
[ 221.750199] usb 2-1: device descriptor read/all, error -71
[ 221.808058] hub 2-0:1.0: unable to enumerate USB device on port 1
[ 222.848077] usb 2-1: new full speed USB device using uhci_hcd and address 12
[ 222.990081] usb 2-1: device descriptor read/all, error -71
[ 223.048063] hub 2-0:1.0: unable to enumerate USB device on port 1
[ 224.088066] usb 2-1: new full speed USB device using uhci_hcd and address 14
[ 224.144103] hub 2-0:1.0: unable to enumerate USB device on port 1
[ 225.328076] usb 2-1: new full speed USB device using uhci_hcd and address 15
[ 225.476010] usb 2-1: unable to read config index 0 descriptor/start: -71
[ 225.476010] usb 2-1: chopping to 0 config(s)
[ 225.483627] usb 2-1: string descriptor 0 read error: -71
[ 225.491359] usb 2-1: string descriptor 0 read error: -71
[ 225.499051] usb 2-1: string descriptor 0 read error: -71
[ 225.499051] usb 2-1: no configuration chosen from 0 choices
[ 225.499051] usb 2-1: New USB device found, idVendor=04d8, idProduct=000a
[ 225.499051] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 225.499051] usb 2-1: USB disconnect, address 15
[ 226.568073] usb 2-1: new full speed USB device using uhci_hcd and address 16
[ 226.710080] usb 2-1: device descriptor read/all, error -71
[ 226.768103] hub 2-0:1.0: unable to enumerate USB device on port 1
[ 227.808075] usb 2-1: new full speed USB device using uhci_hcd and address 18
[ 227.950081] usb 2-1: device descriptor read/all, error -71
[ 228.008095] hub 2-0:1.0: unable to enumerate USB device on port 1
[ 229.068076] usb 2-1: new full speed USB device using uhci_hcd and address 20
[ 229.125840] hub 2-0:1.0: unable to enumerate USB device on port 1
[ 230.288075] usb 2-1: new full speed USB device using uhci_hcd and address 21
[ 230.430184] usb 2-1: device descriptor read/all, error -71
[ 230.488094] hub 2-0:1.0: unable to enumerate USB device on port 1
[ 231.528176] usb 2-1: new full speed USB device using uhci_hcd and address 23
[ 231.670199] usb 2-1: device descriptor read/all, error -71
[ 231.728102] hub 2-0:1.0: unable to enumerate USB device on port 1
[ 232.768075] usb 2-1: new full speed USB device using uhci_hcd and address 25
[ 232.824102] hub 2-0:1.0: unable to enumerate USB device on port 1
[ 234.008069] usb 2-1: new full speed USB device using uhci_hcd and address 26
[ 234.150081] usb 2-1: device descriptor read/all, error -71
[ 234.208090] hub 2-0:1.0: unable to enumerate USB device on port 1
[ 235.248078] usb 2-1: new full speed USB device using uhci_hcd and address 28
[ 235.304101] hub 2-0:1.0: unable to enumerate USB device on port 1
[ 236.488081] usb 2-1: new full speed USB device using uhci_hcd and address 29
[ 236.638138] usb 2-1: unable to read config index 0 descriptor/all
[ 236.638138] usb 2-1: can't read configurations, error -71
[ 236.696109] hub 2-0:1.0: unable to enumerate USB device on port 1
[ 237.728077] usb 2-1: new full speed USB device using uhci_hcd and address 31
[ 237.877946] usb 2-1: unable to read config index 0 descriptor/all
[ 237.877946] usb 2-1: can't read configurations, error -71
[ 237.936107] hub 2-0:1.0: unable to enumerate USB device on port 1
[ 238.968077] usb 2-1: new full speed USB device using uhci_hcd and address 33
[ 239.024075] hub 2-0:1.0: unable to enumerate USB device on port 1
[ 240.208067] usb 2-1: new full speed USB device using uhci_hcd and address 34
[ 240.350082] usb 2-1: device descriptor read/all, error -71
[ 240.408093] hub 2-0:1.0: unable to enumerate USB device on port 1
[ 241.448075] usb 2-1: new full speed USB device using uhci_hcd and address 36
[ 241.504095] hub 2-0:1.0: unable to enumerate USB device on port 1
[ 242.688047] usb 2-1: new full speed USB device using uhci_hcd and address 37
[ 242.830269] usb 2-1: device descriptor read/all, error -71
[ 242.888077] hub 2-0:1.0: unable to enumerate USB device on port 1
[ 243.928077] usb 2-1: new full speed USB device using uhci_hcd and address 39
[ 244.078015] usb 2-1: unable to read config index 0 descriptor/all
[ 244.078015] usb 2-1: can't read configurations, error -71
[ 244.136101] hub 2-0:1.0: unable to enumerate USB device on port 1
[ 245.168039] usb 2-1: new full speed USB device using uhci_hcd and address 41
[ 245.310084] usb 2-1: device descriptor read/all, error -71
[ 245.368063] hub 2-0:1.0: unable to enumerate USB device on port 1
[ 246.408036] usb 2-1: new full speed USB device using uhci_hcd and address 43
[ 246.464069] hub 2-0:1.0: unable to enumerate USB device on port 1
... etc.
I have googled and tried the whole day but cannot get it working.
Is there a way to force the use of the cdc-acm module for this device?
thanks.
Wim
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
microwaverich
properly.
When I enter a single command at the command line, like:
aptitude install xawtv
it works fine.
If I just enter 'aptitude' to start the full-screen (ncurses?) version,
when it completes an install it stops responding to the keyboard. I can
abort using CTRL-C, but nothing else seems to work.
Advice?
....Rich
Daniel Burrows
> I upgraded from Etch to Lenny yesterday. Now aptitude isn't behaving
> properly.
>
>
> When I enter a single command at the command line, like:
>
> aptitude install xawtv
>
> it works fine.
>
> If I just enter 'aptitude' to start the full-screen (ncurses?) version,
> when it completes an install it stops responding to the keyboard. I can
> abort using CTRL-C, but nothing else seems to work.
>
> Advice?
No, but I'm curious what your hardware / software configuration is.
I've been trying to figure out this bug for over a year now, and I
can't figure out why just a few systems show it.
If you're up to running some historical versions to see where the
bug was introduced, we could try pulling old packages from
snapshot.debian.net. For starters, maybe these:
Version 0.4.5.3-1:
http://snapshot.debian.net/archive/2007/06/18/debian/pool/main/a/aptitude/
Version 0.4.7-1:
http://snapshot.debian.net/archive/2007/10/31/debian/pool/main/a/aptitude/
Version 0.4.10-1:
http://snapshot.debian.net/archive/2007/12/17/debian/pool/main/a/aptitude/
Version 0.4.11-2:
http://snapshot.debian.net/archive/2008/03/17/debian/pool/main/a/aptitude/
Some of these will also need libcwidget1, which you can find here:
libcwidget1:
http://snapshot.debian.net/archive/2008/04/13/debian/pool/main/c/cwidget/
Thanks,
Daniel
microwaverich
I don't know if I'm "up to" it, but I'd love to give it a go.
Here's some possibly relevant info about my system. Let me know if you
need more.
Processor: 1.8 GHz AMD Athlon XP 2200+
Total Memory: 1 GB
The problem occurs with both kernels 2.6.18-6-K7 and 2.6..26-1-686.
As I stated originally, it did not happen with Etch (using 2.6.18.6-K7),
but it does happen with Lenny using that same kernel.
I had done the upgrade by:
1. following the recommended "Preparing for the next release" steps
(remove obsolete packages, get rid of /etc/network/options, etc.)
2. changed /etc/apt/sources.list settings from 'etch' to 'lenny' (I use
ftp.us.debian.org)
3. run:
aptitude update
aptitude install apt
aptitude install dpkg
aptitude install aptitude
aptitude dist-upgrade
They all seemed to work fine except:
X didn't work, and I found I had to run:
aptitude install xserver-xorg-video-nv
When I found that aptitude froze after an install in ncurses mode, I ran:
aptitude autoclean
aptitude reinstall apt
aptitude reinstall dpkg
aptitude reinstall aptitude
but that didn't help.
If I understand you correctly, I should try installing the above
aptitudes (in reverse order?) and then installing some other package
(any package?).
.... Rich
Daniel Burrows
> I don't know if I'm "up to" it, but I'd love to give it a go.
Cool. Thanks! Part of the problem is, it doesn't happen on my
computer. :-(
> If I understand you correctly, I should try installing the above
> aptitudes (in reverse order?) and then installing some other package
> (any package?).
Yes -- starting with the most recent ones, install each aptitude
version (just the ones I listed would be fine for now), then try
installing or removing some small package. I use xsoldier for this
sort of test, but you can pick a different victim if you like. The
goal is to find the most recent broken version (i.e., the one where
the breaking change was introduced).
Thanks,
Daniel
Boyd Stephen Smith Jr.
about 'Re: aptitude freezes after install':
>> aptitudes (in reverse order?) and then installing some other package
>> (any package?).
>
> Yes -- starting with the most recent ones, install each aptitude
>version (just the ones I listed would be fine for now), then try
>installing or removing some small package. I use xsoldier for this
>sort of test, but you can pick a different victim if you like. The
>goal is to find the most recent broken version (i.e., the one where
>the breaking change was introduced).
Wow, this sounds like a job for "git bisect". Unfortuntely, I can't use
that method as the issue doesn't manifest itself on any of my systems.
--
Boyd Stephen Smith Jr. ,= ,-_-. =.
b...@iguanasuicide.net ((_/)o o(\_))
ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-'
http://iguanasuicide.net/ \_/
Boyd Stephen Smith Jr.
>aptitude update
>aptitude install apt
>aptitude install dpkg
>aptitude install aptitude
>aptitude dist-upgrade
I could be completely wrong here (and I would love a correction) but I
thought the preferred order was:
aptitude update
aptitude install dpkg # Core package handling
aptitude install apt # Core repository management
aptitude install aptitude # State-of-the-art dependency handling
aptitude full-upgrade # See below
Aptitude for Lenny and above like "safe-upgrade" instead of "upgrade"
and "full-upgrade" instead of "dist-upgrade".
Daniel Burrows
> On Saturday 17 January 2009, Daniel Burrows <dbur...@debian.org> wrote
> about 'Re: aptitude freezes after install':
> >On Sat, Jan 17, 2009 at 08:55:10PM -0500, microwaverich <rich...@one.net>
> was heard to say:
> >> If I understand you correctly, I should try installing the above
> >> aptitudes (in reverse order?) and then installing some other package
> >> (any package?).
> >
> > Yes -- starting with the most recent ones, install each aptitude
> >version (just the ones I listed would be fine for now), then try
> >installing or removing some small package. I use xsoldier for this
> >sort of test, but you can pick a different victim if you like. The
> >goal is to find the most recent broken version (i.e., the one where
> >the breaking change was introduced).
>
> Wow, this sounds like a job for "git bisect". Unfortuntely, I can't use
> that method as the issue doesn't manifest itself on any of my systems.
The problem is, the earliest version of aptitude which is known to be
free of the bug is so old that it no longer builds with the current
toolchain in Debian. And if you run "hg bisect", giving that version as
the starting point, "bisect" picks a version that requires a version of
libcwidget-dev that is no longer in the archive.
I'm trying to find a way of doing this without posting the horribly
convoluted instructions that would be necessary to deal with that
situation.
Boyd Stephen Smith Jr.
>free of the bug is so old that it no longer builds with the current
>toolchain in Debian. And if you run "hg bisect", giving that version as
>the starting point, "bisect" picks a version that requires a version of
>libcwidget-dev that is no longer in the archive.
>
> I'm trying to find a way of doing this without posting the horribly
>convoluted instructions that would be necessary to deal with that
>situation.
At this moment, I am particularly glad IANADD. ;)
microwaverich
> On Sat, Jan 17, 2009 at 08:55:10PM -0500, microwaverich <rich...@one.net> was heard to say:
>> I don't know if I'm "up to" it, but I'd love to give it a go.
>
> Cool. Thanks! Part of the problem is, it doesn't happen on my
> computer. :-(
>
>> If I understand you correctly, I should try installing the above
>> aptitudes (in reverse order?) and then installing some other package
>> (any package?).
>
> Yes -- starting with the most recent ones, install each aptitude
> version (just the ones I listed would be fine for now), then try
> installing or removing some small package. I use xsoldier for this
> sort of test, but you can pick a different victim if you like. The
> goal is to find the most recent broken version (i.e., the one where
> the breaking change was introduced).
>
> Thanks,
> Daniel
>
>
middle and work outward.
I went to
http://snapshot.debian.net/archive/2007/12/17/debian/pool/main/a/aptitude/
and downloaded aptitude_0.4.10-1_i386.deb and tried installing that. I
didn't see a k7 version, if that matters.
It told me I needed libcwidget1, as you said it might, so I went back
and got that, and it seemed to install just fine.
Then I repeated the install of aptitude, and here's what it told me:
dpkg -i '///home/rich/downloads/aptitude_0.4.10-1_i386.deb' ;echo RESULT=$?
(Reading database ... 112547 files and directories currently installed.)
Preparing to replace aptitude 0.4.10-1 (using
..../aptitude_0.4.10-1_i386.deb) ...
Unpacking replacement aptitude ...
dpkg: dependency problems prevent configuration of aptitude:
aptitude depends on libapt-pkg-libc6.6-6-4.6; however:
Package libapt-pkg-libc6.6-6-4.6 is not installed.
dpkg: error processing aptitude (--install):
dependency problems - leaving unconfigured
Processing triggers for man-db ...
Processing triggers for menu ...
Errors were encountered while processing:
aptitude
RESULT=1
I don't see such a libapt-pkg ... in the Lenny repository.
I next tried installing the older version 0.4.5.3-1, but the installer
refused to replace the 0.4.10-1 version due to dependencies with tasksel.
So I tried the newest one in your list: 0.4.11-2
It installed with no errors.
I invoked aptitude in a console and checked Help->About to verify that I
had the 0.4.11-2 version.
Then I searched for kstars, selected it (+), and hit 'g'. aptitude
advised of three dependencies it would load (e.g., kstars data) and that
libcwidget3 would be removed. I hit 'g' and off it went. When it
returned, it responded to commands and exited properly when I selected 'q'.
:-) :-) :-)
What next, Doc?
Wim de Vries
Some additional information:
when unplug the power supply, I can get it working for a few minutes
(ttyACM0). Then the same errors appears.
Unplugging and plugging it in again results in a change to ttyACM1.
regards, wim.
Daniel Burrows
> Then I repeated the install of aptitude, and here's what it told me:
>
> dpkg -i '///home/rich/downloads/aptitude_0.4.10-1_i386.deb' ;echo RESULT=$?
> (Reading database ... 112547 files and directories currently installed.)
> Preparing to replace aptitude 0.4.10-1 (using
> ..../aptitude_0.4.10-1_i386.deb) ...
> Unpacking replacement aptitude ...
> dpkg: dependency problems prevent configuration of aptitude:
> aptitude depends on libapt-pkg-libc6.6-6-4.6; however:
> Package libapt-pkg-libc6.6-6-4.6 is not installed.
Ouch. I forgot that the apt ABI had changed. So much for that clever
idea. I don't think we want to get into downgrading your apt.
But the one thing you did confirm is that apparently 0.4.11-2 doesn't
exhibit this bug. That gives us a starting point (and also limits how
far back we need to go, which will be a help). I think the version
range is narrow enough for "hg bisect" to be useful.
First, install the build dependencies of aptitude. You'll also want
mercurial.
# aptitude build-depends aptitude build-essential+ mercurial+
Now, get a copy of the aptitude source in the current directory:
$ hg clone http://hg.debian.org/hg/aptitude/head aptitude
$ cd aptitude
Tell "hg bisect" that the last known-good revision is 0.4.11:
$ hg bisect --good 0.4.11
$ hg bisect --bad tip
Mercurial will tell you that it's checked out a changeset for you to
test:
> Testing changeset 1499:79935933f5ba (305 changesets remaining, ~8 tests)
> 136 files updated, 0 files merged, 8 files removed, 0 files unresolved
Now, compile aptitude by running
$ sh ./autogen.sh
$ ./configure --disable-werror
$ make -C src
When you're done, run ./src/aptitude as root:
# ./src/aptitude
If you can reproduce the bug, mark the current revision as bad:
$ hg bisect --bad
If not, mark it as good:
$ hg bisect --good
Then in theory you can just continue compiling aptitude (using the
steps above) and running it, telling "hg" at each step whether the
revision is good or bad. If you hit a revision that you can't compile,
you can try this:
$ hg bisect --skip
If that doesn't work, post the output of "hg identify" and the
compile error, and I'll see if I can figure out a workaround for you.
Otherwise, keep going (should take about 8 tries) until mercurial says
what it thinks the first bad revision is, then post the output here.
Thanks,
Daniel
microwaverich
Wow! You've got more confidence in me than I do, Daniel!
Anyway, I plunged into the above steps. Everything went ok until I
tried compiling aptitude. Here's that part of the script file:
rich@peninsula:~/aptitudetests/aptitude$ hg bisect --good 0.4.11
rich@peninsula:~/aptitudetests/aptitude$ hg bisect --bad tip
Testing changeset 1499:79935933f5ba (305 changesets remaining, ~8 tests)
136 files updated, 0 files merged, 8 files removed, 0 files unresolved
rich@peninsula:~/aptitudetests/aptitude$ sh ./autogen.sh
../autogen.sh: line 5: aclocal-1.9: command not found
$ find / -name aclocal* turned up a four items named aclocal, but no
aclocal-1.9.
Maybe I should have just plowed ahead with the configure command, but I
decided to ask first.
.... Rich
Sven Joachim
> Anyway, I plunged into the above steps. Everything went ok until I
> tried compiling aptitude. Here's that part of the script file:
>
> rich@peninsula:~/aptitudetests/aptitude$ hg bisect --good 0.4.11
> rich@peninsula:~/aptitudetests/aptitude$ hg bisect --bad tip
> Testing changeset 1499:79935933f5ba (305 changesets remaining, ~8 tests)
> 136 files updated, 0 files merged, 8 files removed, 0 files unresolved
> rich@peninsula:~/aptitudetests/aptitude$ sh ./autogen.sh
> ../autogen.sh: line 5: aclocal-1.9: command not found
>
> $ find / -name aclocal* turned up a four items named aclocal, but no
> aclocal-1.9.
>
> Maybe I should have just plowed ahead with the configure command, but
> I decided to ask first.
You need to install automake1.9 and autoconf to make autogen.sh work.
Sven
Daniel Burrows
> Anyway, I plunged into the above steps. Everything went ok until I
> tried compiling aptitude. Here's that part of the script file:
>
> rich@peninsula:~/aptitudetests/aptitude$ hg bisect --good 0.4.11
> rich@peninsula:~/aptitudetests/aptitude$ hg bisect --bad tip
> Testing changeset 1499:79935933f5ba (305 changesets remaining, ~8 tests)
> 136 files updated, 0 files merged, 8 files removed, 0 files unresolved
> rich@peninsula:~/aptitudetests/aptitude$ sh ./autogen.sh
> ../autogen.sh: line 5: aclocal-1.9: command not found
>
> $ find / -name aclocal* turned up a four items named aclocal, but no
> aclocal-1.9.
Ah, my mistake. I forgot you need some extra tools to build from the
repository. Install the packages "automake" and "autoconf" and you
should be set.
Thanks for your help,
Daniel
Daniel Burrows
0.4.11-2. So we may just be tracking down the trigger for the bug on
*your* computer. I hope that this information is useful anyway, but it
might end up not helping after all. :( I'm still curious what your
search turns up, but I'd understand if you wanted to spend your time
doing something else.
Daniel
microwaverich
> BTW, I have another report that this does happen to someone else on
> 0.4.11-2. So we may just be tracking down the trigger for the bug on
> *your* computer. I hope that this information is useful anyway, but it
> might end up not helping after all. :( I'm still curious what your
> search turns up, but I'd understand if you wanted to spend your time
> doing something else.
>
> Daniel
>
>
have to the project.
If I can contribute, I'm delighted.
Now, on to your next message ....
microwaverich
> On Mon, Jan 19, 2009 at 11:23:22AM -0500, microwaverich <rich...@one.net> was heard to say:
>> Anyway, I plunged into the above steps. Everything went ok until I
>> tried compiling aptitude. Here's that part of the script file:
>>
>> rich@peninsula:~/aptitudetests/aptitude$ hg bisect --good 0.4.11
>> rich@peninsula:~/aptitudetests/aptitude$ hg bisect --bad tip
>> Testing changeset 1499:79935933f5ba (305 changesets remaining, ~8 tests)
>> 136 files updated, 0 files merged, 8 files removed, 0 files unresolved
>> rich@peninsula:~/aptitudetests/aptitude$ sh ./autogen.sh
>> ../autogen.sh: line 5: aclocal-1.9: command not found
>>
>> $ find / -name aclocal* turned up a four items named aclocal, but no
>> aclocal-1.9.
>
> Ah, my mistake. I forgot you need some extra tools to build from the
> repository. Install the packages "automake" and "autoconf" and you
> should be set.
>
> Thanks for your help,
> Daniel
>
>
Yes, the same advice as from Sven Joachim. Thanks to you both. I'll
proceed.
.... Rich
microwaverich
>
<snip>
Install the packages "automake" and "autoconf" and you
> should be set.
>
> Thanks for your help,
> Daniel
>
>
Daniel:
I did the above and began running the tests with mercurial. I made 5
passes without a bug until I ran into the following in the compile:
rich@peninsula:~/aptitudetests/aptitude$ make -C src
make: Entering directory `/home/rich/aptitudetests/aptitude/src'
Making all in generic
make[1]: Entering directory `/home/rich/aptitudetests/aptitude/src/generic'
Making all in util
make[2]: Entering directory
`/home/rich/aptitudetests/aptitude/src/generic/util'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory
`/home/rich/aptitudetests/aptitude/src/generic/util'
Making all in problemresolver
make[2]: Entering directory
`/home/rich/aptitudetests/aptitude/src/generic/problemresolver'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory
`/home/rich/aptitudetests/aptitude/src/generic/problemresolver'
Making all in apt
make[2]: Entering directory
`/home/rich/aptitudetests/aptitude/src/generic/apt'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory
`/home/rich/aptitudetests/aptitude/src/generic/apt'
make[2]: Entering directory `/home/rich/aptitudetests/aptitude/src/generic'
make[2]: Nothing to be done for `all-am'.
make[2]: Leaving directory `/home/rich/aptitudetests/aptitude/src/generic'
make[1]: Leaving directory `/home/rich/aptitudetests/aptitude/src/generic'
Making all in cmdline
make[1]: Entering directory `/home/rich/aptitudetests/aptitude/src/cmdline'
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory `/home/rich/aptitudetests/aptitude/src/cmdline'
Making all in mine
make[1]: Entering directory `/home/rich/aptitudetests/aptitude/src/mine'
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory `/home/rich/aptitudetests/aptitude/src/mine'
make[1]: Entering directory `/home/rich/aptitudetests/aptitude/src'
make[1]: Nothing to be done for `all-am'.
make[1]: Leaving directory `/home/rich/aptitudetests/aptitude/src'
make: Leaving directory `/home/rich/aptitudetests/aptitude/src'
So I tried this next:
rich@peninsula:~/aptitudetests/aptitude$ hg bisect --skip
Testing changeset 1650:f3c69fd9fb66 (5 changesets remaining, ~2 tests)
2 files updated, 0 files merged, 0 files removed, 0 files unresolved
but got the same result when I repeated the compile steps. Finally, you
asked for this:
rich@peninsula:~/aptitudetests/aptitude$ hg identify
f3c69fd9fb66
So ... What's up, doc?
.... Rich
Daniel Burrows
> I did the above and began running the tests with mercurial. I made 5
> passes without a bug until I ran into the following in the compile:
>
(more of that)
Hm, it looks like aptitude isn't finding anything to recompile. It
didn't print any "*** (error)" lines that I saw, anyway. Maybe you
hit a revision or two with only test / documentation changes. I would
just try re-running your test and running "hg bisect --good" or
"hg bisect --bad" depending on the outcome.
> rich@peninsula:~/aptitudetests/aptitude$ hg identify
> f3c69fd9fb66
Hm, I don't see that revision in my tree. What do you get from this?
$ hg log -r f3c69fd9fb66
Thanks,
Daniel
Daniel Burrows
> On Mon, Jan 19, 2009 at 03:36:19PM -0500, microwaverich <rich...@one.net> was heard to say:
> > I did the above and began running the tests with mercurial. I made 5
> > passes without a bug until I ran into the following in the compile:
> >
> > make[2]: Nothing to be done for `all'.
>
> (more of that)
>
> Hm, it looks like aptitude isn't finding anything to recompile. It
s/aptitude/make/
microwaverich
> On Mon, Jan 19, 2009 at 03:36:19PM -0500, microwaverich <rich...@one.net> was heard to say:
>> I did the above and began running the tests with mercurial. I made 5
>> passes without a bug until I ran into the following in the compile:
>>
>> make[2]: Nothing to be done for `all'.
>
> (more of that)
>
> Hm, it looks like aptitude isn't finding anything to recompile. It
> didn't print any "*** (error)" lines that I saw, anyway. Maybe you
> hit a revision or two with only test / documentation changes. I would
> just try re-running your test and running "hg bisect --good" or
> "hg bisect --bad" depending on the outcome.
>
>> rich@peninsula:~/aptitudetests/aptitude$ hg identify
>> f3c69fd9fb66
>
> Hm, I don't see that revision in my tree. What do you get from this?
>
> $ hg log -r f3c69fd9fb66
>
> Thanks,
> Daniel
>
>
rich@peninsula:~/aptitudetests/aptitude$ hg log -r f3c69fd9fb66
changeset: 1650:f3c69fd9fb66
user: Jens Seidel <jenss...@users.sf.net>
date: Tue Nov 11 21:50:28 2008 +0100
summary: Further minor Italian translation update
I'll get back to the test after I see your next message.
.... Rich
microwaverich
> On Mon, Jan 19, 2009 at 07:14:24PM -0800, Daniel Burrows <dbur...@debian.org> was heard to say:
>> On Mon, Jan 19, 2009 at 03:36:19PM -0500, microwaverich <rich...@one.net> was heard to say:
>>> I did the above and began running the tests with mercurial. I made 5
>>> passes without a bug until I ran into the following in the compile:
>>>
>>> make[2]: Nothing to be done for `all'.
>> (more of that)
>>
>> Hm, it looks like aptitude isn't finding anything to recompile. It
>
> s/aptitude/make/
>
> Daniel
>
>
Apparently something got chopped out of this post(?) I don't understand.
.... Rich
Daniel Burrows
> Daniel Burrows wrote:
>> On Mon, Jan 19, 2009 at 07:14:24PM -0800, Daniel Burrows <dbur...@debian.org> was heard to say:
>>> On Mon, Jan 19, 2009 at 03:36:19PM -0500, microwaverich <rich...@one.net> was heard to say:
>>>> I did the above and began running the tests with mercurial. I made
>>>> 5 passes without a bug until I ran into the following in the
>>>> compile:
>>>>
>>>> make[2]: Nothing to be done for `all'.
>>> (more of that)
>>>
>>> Hm, it looks like aptitude isn't finding anything to recompile. It
>>
>> s/aptitude/make/
>>
>> Daniel
>>
>>
>
>
> Apparently something got chopped out of this post(?) I don't understand.
It's not aptitude that isn't finding anything to recompile, it's make.
Daniel
microwaverich
I ran the autogen/configure/make sequence two more times (I didn't
restart from the beginning, just continued where I had left off) and
then got this:
rich@peninsula:~/aptitudetests/aptitude$ hg bisect --good
The first bad revision is:
changeset: 1652:c6e9af2ee01d
tag: tip
user: Jens Seidel <jenss...@users.sf.net>
date: Mon Jan 12 14:10:55 2009 +0100
summary: Minor Swedish translation improvement. Closes: #511238
The aptitude I ran just before this didn't freeze up, but ... well, you
see what happened. Does this make sense?
.... Rich
Daniel Burrows
> Daniel:
>
> I ran the autogen/configure/make sequence two more times (I didn't
> restart from the beginning, just continued where I had left off) and
> then got this:
>
>
> rich@peninsula:~/aptitudetests/aptitude$ hg bisect --good
> The first bad revision is:
> changeset: 1652:c6e9af2ee01d
> tag: tip
> user: Jens Seidel <jenss...@users.sf.net>
> date: Mon Jan 12 14:10:55 2009 +0100
> summary: Minor Swedish translation improvement. Closes: #511238
>
>
> The aptitude I ran just before this didn't freeze up, but ... well, you
> see what happened. Does this make sense?
Hmmm. That's the most recent update to the source tree. Which would
mean aptitude doesn't freeze for you. Yay! We solved your problem and
we didn't even change any code! :-D
....
Did you get any freezes during your test, or did everything work for
you? Also, just to check: /usr/bin/aptitude still exhibits the bug,
right?
Daniel
microwaverich
>
<snip>
>
>
> Hmmm. That's the most recent update to the source tree. Which would
> mean aptitude doesn't freeze for you. Yay! We solved your problem and
> we didn't even change any code! :-D
>
> ....
>
> Did you get any freezes during your test, or did everything work for
> you? Also, just to check: /usr/bin/aptitude still exhibits the bug,
> right?
>
> Daniel
>
>
I got no freezes during the test. Everything worked Ok.
/usr/bin/aptitude DOES NOT still exhibit the bug! It works Ok!
Some potentially non-trivial differences in the versions:
rich@peninsula:~/aptitudetests/aptitude$ ./src/aptitude --version
aptitude 0.4.11.10 compiled at Jan 19 2009 14:37:47
Compiler: g++ 4.3.2
Compiled against:
apt version 4.6.0
NCurses version 5.7
libsigc++ version: 2.0.18
Ept support disabled.
Current library versions:
NCurses version: ncurses 5.7.20081213
cwidget version: 0.5.12
Apt version: 4.6.0
rich@peninsula:~/aptitudetests/aptitude$ /usr/bin/aptitude --version
aptitude 0.4.11 compiled at Mar 16 2008 17:32:32
Compiler: g++ 4.2.3 (Debian 4.2.3-2)
NCurses version: 5.6
libsigc++ version: 2.0.18
Ept support enabled.
Do we declare victory, or does this lead somewhere else?
.... Rich
Daniel Burrows
> rich@peninsula:~/aptitudetests/aptitude$ /usr/bin/aptitude --version
> aptitude 0.4.11 compiled at Mar 16 2008 17:32:32
> Compiler: g++ 4.2.3 (Debian 4.2.3-2)
>
> NCurses version: 5.6
> libsigc++ version: 2.0.18
> Ept support enabled.
Ah, I forgot that I told you to downgrade to a working version. What
if you upgrade it by running "aptitude install aptitude" first?
Daniel
microwaverich
> On Wed, Jan 21, 2009 at 07:16:06AM -0500, microwaverich <rich...@one.net> was heard to say:
>> rich@peninsula:~/aptitudetests/aptitude$ /usr/bin/aptitude --version
>> aptitude 0.4.11 compiled at Mar 16 2008 17:32:32
>> Compiler: g++ 4.2.3 (Debian 4.2.3-2)
>>
>> NCurses version: 5.6
>> libsigc++ version: 2.0.18
>> Ept support enabled.
>
> Ah, I forgot that I told you to downgrade to a working version. What
> if you upgrade it by running "aptitude install aptitude" first?
>
> Daniel
>
>
Ok, did that. The new aptitude did not freeze. Tried it twice. Here's
what I've got now:
rich@peninsula:~/aptitudetests/aptitude$ aptitude --version
aptitude 0.4.11.11 compiled at Dec 5 2008 02:43:34
Compiler: g++ 4.3.2
Compiled against:
apt version 4.6.0
NCurses version 5.6
libsigc++ version: 2.0.18
Ept support enabled.
Current library versions:
NCurses version: ncurses 5.7.20081213
cwidget version: 0.5.12
Apt version: 4.6.0
.... Rich
microwaverich
anymore, so we can't fix it :-)
I'll try something else if you want. I've learned quite a bit during
this exercise and enjoyed it all.
Thanks.
.... Rich