RREGRESSION: gnome-pilot can't see my palm V (jpilot can)

[Matt Price <matt price utoronto ca>]

Hi Matt,

I think there's some problem with the hardware on my palm.  SUddenly I
can no longer connect with pilot-xfer OR jpilot, and removing the USB
cable from the computer generates a kernel OOPS:

[  882.757176] ----------- [cut here ] --------- [please bite here ]
---------
[  882.757180] Kernel BUG at kernel/workqueue.c:109
[  882.757183] invalid operand: 0000 [1] PREEMPT SMP
[  882.757186] CPU 0
[  882.757188] Modules linked in: rfcomm l2cap bluetooth ppdev radeon
drm cpufreq_userspace cpufreq_stats freq_table cpufreq_powersave
cpufreq_ondemand cpufreq_conservative video tc1100_wmi sony_acpi
pcc_acpi hotkey dev_acpi container button acpi_sbs battery i2c_acpi_ec
ac reiserfs ext3 jbd ipv6 sr_mod sbp2 lp tsdev analog usb_storage
parport_pc kl5kusb105 gameport snd_intel8x0 snd_ac97_codec
snd_ac97_bus visor parport snd_mpu401 snd_mpu401_uart snd_pcm_oss
usbserial snd_rawmidi snd_mixer_oss snd_pcm snd_seq_device snd_timer
pcspkr psmouse snd shpchp i2c_nforce2 pci_hotplug serio_raw sk98lin
i2c_core soundcore skge snd_page_alloc af_packet sg evdev xfs exportfs
dm_mod raid1 md_mod ide_generic ohci1394 ieee1394 forcedeth ehci_hcd
ohci_hcd usbcore ide_cd cdrom ide_disk generic sd_mod amd74xx sata_nv
libata scsi_mod thermal processor fan capability commoncap vga16fb
cfbcopyarea vgastate cfbimgblt cfbfillrect fbcon tileblit font bitblit
softcursor
[  882.757232] Pid: 2114, comm: khubd Not tainted 2.6.15-23-amd64-k8
#1
[  882.757235] RIP: 0010:[<ffffffff8015025e>]
<ffffffff8015025e>{queue_work+62}
[  882.757245] RSP: 0018:ffff81007dc2dce8  EFLAGS: 00010286
[  882.757248] RAX: ffff8100746b0a28 RBX: 0000000000000000 RCX:
0000000000000034
[  882.757252] RDX: 0000000000000000 RSI: ffff8100746b0a20 RDI:
ffff810037901860
[  882.757255] RBP: ffff810037df6cc8 R08: 0000000000000000 R09:
0000000000000000
[  882.757258] R10: 0000000000000000 R11: ffffffff80274720 R12:
ffff810037df6cc0
[  882.757262] R13: ffff81007ff87c20 R14: ffff81007e3c8448 R15:
ffff81007dc49c00
[  882.757266] FS:  00002aaaab7acce0(0000) GS:ffffffff80446800(0000)
knlGS:0000000000000000
[  882.757270] CS:  0010 DS: 0018 ES: 0018 CR0: 000000008005003b
[  882.757272] CR2: 0000000000d69010 CR3: 000000007d36d000 CR4:
00000000000006e0
[  882.757276] Process khubd (pid: 2114, threadinfo ffff81007dc2c000,
task ffff81007dc278e0)
[  882.757279] Stack: 0000000000000001 ffffffff882dfd69
ffffffff80311d20 ffffffff883132c0
[  882.757285]        ffff81007ff87c00 ffffffff88313300
ffff81007ff87c20 ffffffff880af113
[  882.757292]        ffff81007ff87d10 ffff81007ff87c20
[  882.757296] Call
Trace:<ffffffff882dfd69>{:usbserial:usb_serial_disconnect+105}
[  882.757313]        <ffffffff80311d20>{klist_release+0}
<ffffffff880af113>{:usbcore:usb_unbind_interface+83}
[  882.757341]        <ffffffff80274145>{__device_release_driver+133}
<ffffffff802744ae>{device_release_driver+46}
[  882.757352]        <ffffffff80273b62>{bus_remove_device+146}
<ffffffff80272aa6>{device_del+70}
[  882.757365]
<ffffffff880b5cbc>{:usbcore:usb_disable_device+140}
[  882.757381]        <ffffffff880af982>{:usbcore:usb_disconnect+194}
<ffffffff880b225b>{:usbcore:hub_thread+971}
[  882.757412]        <ffffffff80312dd0>{thread_return+0}
<ffffffff801550c0>{autoremove_wake_function+0}
[  882.757429]        <ffffffff880b1e90>{:usbcore:hub_thread+0}
<ffffffff80154b90>{keventd_create_kthread+0}
[  882.757451]        <ffffffff80154d59>{kthread+217}
<ffffffff80139430>{schedule_tail+64}
[  882.757459]        <ffffffff80110dfe>{child_rip+8}
<ffffffff80154b90>{keventd_create_kthread+0}
[  882.757469]        <ffffffff80154c80>{kthread+0}
<ffffffff80110df6>{child_rip+0}
[  882.757484]
[  882.757488]
[  882.757489] Code: 0f 0b 68 08 01 33 80 c2 6d 00 48 8b 07 48 63 d2
bb 01 00 00
[  882.757498] RIP <ffffffff8015025e>{queue_work+62} RSP
<ffff81007dc2dce8>
[  882.757504]  <6>note: khubd[2114] exited with preempt_count 1
------------------------------------
THis was happening for a while before but I'dthought it had to do with
suspend-to-RAM problems, which can't apply here as I've done several
fresh restarts.  I'm wondering whether there's a way to capture the
Palm's output directly -- cat /dev/ttyUSB0 > file.hex ,and then read
it somehow?  WOuld that help? Anyway it's very strange to me that
suddenly everything's not working.

> The important thing is that "len=0xed030302" is nonsense - claiming that
> the data coming from the palm is about 3.8GB.  pilot-link is expecting
> about 50 bytes, and due to a bug starts trying to copy 3.8Gb of memory
> into a 50 byte buffer, and unsurprisingly crashes.  What I don't know is
> how we're getting to this state, and what's going wrong.
> 
> Has your kernel or udev package changed since the initial dapper
> release?  Is it possible for you to downgrade your kernel and/or udev?
> That's the sort of stuff I'd be looking at.  I'm tempted to try
> installing dapper myself to dig into these problems, as they're not
> showing up on other distributions (as far as I know). 

there've been several updates to the kernel since the first "Flight" I
tried a week ago -- but I've done nothing unconventional.  I think it
would bepretty hard to downgrade as I'm running 2.6.15, and I guess
the udev before that is quite different.  Isn'tthat right?

> 
> > > Another way of accomplishing the same thing is to suspect the gpilotd
> > > process by ctrl-Z at the command line, start the hotsync, and then
> > > resume gpilotd with 'fg'.
> > > 
> > no go -- I get the same behaviour as before, 
> 
> Bummer.  I had my hopes...  One other thing to try is killing gpilotd
> and perhaps 'bonobo-activation-server' too, then starting a hotsync and
> then starting gpilotd.
> 
> > (gnome_segv2:17370): Gtk-WARNING **: cannot open display:
> > 
> > that looks like a strange warning to me -- is gpilotd trying to open a
> > window to talk to me?  
> 
> It is probably trying to open the bug reporting window.  Not sure why
> it's not able to.  Are you starting gpilotd from a terminal with a valid
> DISPLAY environment variable (do "echo $DISPLAY"; if it's not set, do
> "export DISPLAY=127.0.0.1:0.0" or "setenv DISPLAY 127.0.0.1:0.0"
> depending on whether you use bash or tcsh.  That may or may not help.
> Either way, no biggie.
> 
> > I can't find the "LANSync" pref panel on my palm, will continue
> > looking for it/try to figure whether it is available on the V.
> 
> On my palmV (OS 3.3), it's available as follows:
> 1. go to hotsync application,
> 2. select 'local, direct serial' hotsync (as you already do, I'm sure)
> 3. go to 'menu->LANsync Prefs' and select 'LANSync' instead of 'Local
> HotSync'. OK.
> 4. go to 'menu->Primary PC Setup' and set 'Primary PC Name' to "!!", and
> then set the 'Primary PC Address' to the IP address of your gpilotd
> process - try '127.0.0.1' if you're running pi-nredir and gpilotd on the
> same machine.  And set the subnet mask to '255.255.255.0'.
> 
ok, thanks, found it -- but unfortunately this new probme (see above)
interferes with my ability to test this.

Matt


> M
> 
> Matt Davey	I like to browse in occult bookshops if for no other reason than
> mcdavey mrao cam ac uk   to refresh my commitment to science. -- Heinz Pagels
> _______________________________________________
> gnome-pilot-list mailing list
> gnome-pilot-list gnome org
> http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
> 

-------------------------------------------
Matt Price	    matt price utoronto ca
History Department, University of Toronto
(416) 978-2094
--------------------------------------------