2.6.36-rc6: udev settle timeouts during rcS (audio-related?)

2010-10-27 Thread martin f krafft
Hello,

I installed sid onto a new machine yesterday (Intel ICH chipset).
2.6.32-5-amd64 boots fine, but 2.6.36-rc6-amd64 makes udev settle
timeout when run from the rcS.d/udev script. As a consequence,
a random combination of PCI devices then won't be available: at some
point, the sound card will be missing, at others there won't be
a network card, sometimes the graphics cards go AWOL, etc.

A few seconds before rcS starts, I always get a BUG (see below) in
modprobe, which does not appear with 2.6.32. I suspect it's related,
but I don't know for sure. The referenced PCI device (last sysfs
file) always seems to be one on PCI bus ff:*.* (see below for
lspci). The device alternatives between those, but the rest of the
BUG and the trace always looks the same.

I am finding this hard to debug because I have not been able to
capture the messages sent to the console; syslog does not get them,
bootlog does not get them, dmesg does not see all of them (e.g. not
the timeout from udevadm settle).

During the settle timeout, if I press ctrl-c, I can get to a shell
and inspect the processes. There are a few modprobe processes, some
in D state, and looking at the PCI IDs embedded in the PCI alias
arguments to modprobe, they all seem to be related to PCI and USB
controllers (PCI bus 00:1*.* basically).

The first thing I did was reduce the timeout to facilitate
debugging, and I only needed to edit /etc/rcS.d/S02udev for that
(append --timeout=20 to udevadm settle). Now I didn't have to wait
180 seconds each time.

Then I tried to get netconsole to work to capture the console
messages, which I could not find in any log file post-boot. However,
even though I moved /etc/rcS.d/S09module-init-tools to
S00module-init-tools, and inserted a sleep 30 at the end of the
script, netconsole would only get loaded well after the timeout
passed.

Yet, the timeout length is controlled from /etc/rcS.d/S02udev,
which is supposed to start afterwards. Weird.

I added 'exec /lib/init/rw/udev.output' to the udev script and now
managed to capture the output:

  Waiting for /dev to be fully populated...
  udevadm settle - timeout of 20 seconds reached, the event queue contains:
/sys/devices/pci:00/:00:03.0/:02:00.0/:03:00.0/:04:00.1 
(1264)
/sys/devices/pci:00/:00:03.0/:02:00.0/:03:02.0/:05:00.1 
(1268)
/sys/devices/pci:00/:00:07.0/:06:00.1 (1274)
/sys/devices/pci:00/:00:1b.0 (1321)
  done (timeout).

All of those seem related to *audio* devices (the graphics cards
apparently have audio devices too nowadays), and most often they do,
but occasionally I see another device in there, e.g. just now the
SMBus controller.

I am keen on getting this resolved, so I'll gladly do whatever is
necessary to help this problem get resolved. I can even provide
access to the machine, if it would help.


lspci -k:
  00:00.0 Host bridge: Intel Corporation 5520/5500/X58 I/O Hub to ESI Port (rev 
13)
Subsystem: ASUSTeK Computer Inc. Device 836b
  00:01.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root 
Port 1 (rev 13)
  00:03.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root 
Port 3 (rev 13)
  00:07.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root 
Port 7 (rev 13)
  00:14.0 PIC: Intel Corporation 5520/5500/X58 I/O Hub System Management 
Registers (rev 13)
Kernel driver in use: i7core_edac
  00:14.1 PIC: Intel Corporation 5520/5500/X58 I/O Hub GPIO and Scratch Pad 
Registers (rev 13)
  00:14.2 PIC: Intel Corporation 5520/5500/X58 I/O Hub Control Status and RAS 
Registers (rev 13)
  00:14.3 PIC: Intel Corporation 5520/5500/X58 I/O Hub Throttle Registers (rev 
13)
  00:1a.0 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI 
Controller #4
Subsystem: ASUSTeK Computer Inc. Device 82d4
Kernel driver in use: uhci_hcd
  00:1a.1 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI 
Controller #5
Subsystem: ASUSTeK Computer Inc. Device 82d4
Kernel driver in use: uhci_hcd
  00:1a.2 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI 
Controller #6
Subsystem: ASUSTeK Computer Inc. Device 82d4
Kernel driver in use: uhci_hcd
  00:1a.7 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB2 EHCI 
Controller #2
Subsystem: ASUSTeK Computer Inc. Device 82d4
Kernel driver in use: ehci_hcd
  00:1b.0 Audio device: Intel Corporation 82801JI (ICH10 Family) HD Audio 
Controller
Subsystem: ASUSTeK Computer Inc. Device 82ea
  00:1c.0 PCI bridge: Intel Corporation 82801JI (ICH10 Family) PCI Express Root 
Port 1
  00:1c.1 PCI bridge: Intel Corporation 82801JI (ICH10 Family) PCI Express Port 
2
  00:1c.2 PCI bridge: Intel Corporation 82801JI (ICH10 Family) PCI Express Root 
Port 3
  00:1d.0 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI 
Controller #1
Subsystem: ASUSTeK Computer Inc. Device 82d4
Kernel driver in use: uhci_hcd
  00:1d.1 USB 

Bug#600992: further logs

2010-10-27 Thread Tecnici

Il 22/10/2010 16:02, Ian Campbell ha scritto:

On Fri, 2010-10-22 at 15:40 +0200, Tecnici wrote:

Thanks again Ian, should you need more logs and/or tests please let us
know

I understand that this problem may be related to the lost of
connectivity problems we had in bugs 597865, 596635, 598057.
As we escaped from *-23 kernel to solve these we met this other
problem also related to netfront smartpoll not being disabled

pretty much. the patch which added the option to disable smartpoll was
not complete and left some things uninitialised which were subsequently
relied on.


Ian how much do you think should we wait for a *-27 release? Please let 
us know if you need any testing on merging the additional patches to the 
kernel.


regards



--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4cc7d61d.5060...@advert.it



Bug#600992: further logs

2010-10-27 Thread Ian Campbell
On Wed, 2010-10-27 at 09:34 +0200, Tecnici wrote:
 Il 22/10/2010 16:02, Ian Campbell ha scritto:
  On Fri, 2010-10-22 at 15:40 +0200, Tecnici wrote:
  Thanks again Ian, should you need more logs and/or tests please let us
  know
 
  I understand that this problem may be related to the lost of
  connectivity problems we had in bugs 597865, 596635, 598057.
  As we escaped from *-23 kernel to solve these we met this other
  problem also related to netfront smartpoll not being disabled
  pretty much. the patch which added the option to disable smartpoll was
  not complete and left some things uninitialised which were subsequently
  relied on.
 
 Ian how much do you think should we wait for a *-27 release? Please let 
 us know if you need any testing on merging the additional patches to the 
 kernel.

I'm not involved in that aspect of debian-kernel procedure. It might be
a couple of weeks at the most.

Ian.

-- 
Ian Campbell

A bird in the hand is worth two in the bush.
-- Cervantes


signature.asc
Description: This is a digitally signed message part


Bug#601550: [nfs-kernel-server] Root is always squashed when using sec=gss/krb5

2010-10-27 Thread ares
Package: nfs-kernel-server
Version: 1:1.1.2-6lenny2
Severity: normal

--- Please enter the report below this line. ---
I have a NFSv4 server exports configured as follows:
/export   
gss/krb5(rw,fsid=0,insecure,no_root_squash,no_subtree_check,async)
/export/users 
gss/krb5(rw,nohide,insecure,no_root_squash,no_subtree_check,async)

On the other side I have clients with autofs configration like:
*   -fstype=nfs4,rw,soft,intr,bg,nosuid,nodev,sec=krb5,port=2049,proto=tcp  
nfs.mydomain.cz:/users/

Everythink works great for regular users but when root is always squashed even 
when I set no_root_squash. I tried a configuration without kerberos and it 
worked as expected (I just removed gss/krb5 and sec=krb5 from configurations). 
Using kerberos root is always mapped to nobody:nogroup. Output from idmapd:

r...@server# rpc.idmapd -c /etc/idmapd.conf -f -vvv
rpc.idmapd: libnfsidmap: using domain: localdomain

rpc.idmapd: libnfsidmap: using translation method: nsswitch

rpc.idmapd: Expiration time is 600 seconds.
rpc.idmapd: Opened /proc/net/rpc/nfs4.nametoid/channel
rpc.idmapd: Opened /proc/net/rpc/nfs4.idtoname/channel
rpc.idmapd: nfsdcb: authbuf=gss/krb5 authtype=user
rpc.idmapd:  Server: (user) id 0 - name r...@localdomain
rpc.idmapd: nfsdcb: authbuf=gss/krb5 authtype=group
rpc.idmapd:  Server: (group) id 0 - name r...@localdomain
rpc.idmapd: nfsdcb: authbuf=gss/krb5 authtype=user
rpc.idmapd:  Server: (user) id 2000 - name a...@localdomain
rpc.idmapd: nfsdcb: authbuf=gss/krb5 authtype=group
rpc.idmapd:  Server: (group) id 2000 - name a...@localdomain

--- System information. ---
Debian Release: 5.0.6
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.26-2-xen-amd64 (SMP w/1 CPU core)
Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8) (ignored: 
LC_ALL set to cs_CZ.UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages nfs-kernel-server depends on:
ii  libblkid1   1.41.3-1 block device id library
ii  libc6   2.7-18lenny6 GNU C Library: Shared libraries
ii  libcomerr2  1.41.3-1 common error description library
ii  libgssglue1 0.1-2mechanism-switch gssapi library
ii  libkrb531.6.dfsg.4~beta1-5lenny4 MIT Kerberos runtime libraries
ii  libnfsidmap20.20-1   An nfs idmapping library
ii  librpcsecgss3   0.18-1   allows secure rpc communication 
us
ii  libwrap07.6.q-16 Wietse Venema's TCP wrappers 
libra
ii  lsb-base3.2-20   Linux Standard Base 3.2 init 
scrip
ii  nfs-common  1:1.1.2-6lenny2  NFS support files common to client
ii  ucf 3.0016   Update Configuration File: preserv

nfs-kernel-server recommends no packages.

nfs-kernel-server suggests no packages.







-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201010271031.55609.a...@igloonet.cz



Bug#597904: phonet/chromium kernel oops still in 2.6.32-26

2010-10-27 Thread debbug597904 . 597904 . iridos


Hi,

I am still seeing kernel panics with the 2.6.32-26 version of the 
kernel currently in squeeze.
Indeed, I had also been running chromium on an up-to-date squeeze and 
phonet loaded. Crashes seem to happen within a couple of hours of 
loading phonet.


Oops messages below, let me know if I can supply additional information.

Cheers,
Karsten

2.3.32-5-686-bigmmem:

[35221.762853] usb 3-2: USB disconnect, address 13
[38994.824565] lo: Disabled Privacy Extensions
[38995.024896] BUG: unable to handle kernel NULL pointer dereference at 0008
[38995.024907] IP: [c127e9ad] _spin_lock_bh+0xd/0x1e
[38995.024917] *pdpt = 34c3d001 *pde =  
[38995.024923] Oops: 0002 [#1] SMP 
[38995.024928] last sysfs file: /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq

[38995.024932] Modules linked in: cdc_phonet cdc_ether usbnet phonet cdc_acm 
dvb_core v4l2_common ir_common i2c_algo_bit videobuf_dma_sg videobuf_core 
btcx_risc tveeprom netconsole configfs
 usblp nls_utf8 nls_cp437 vfat fat parport_pc ppdev lp parport sco bridge stp 
bnep powernow_k8 rfcomm l2cap crc16 cpufreq_userspace cpufreq_stats 
cpufreq_powersave bluetooth cpufreq_conserv
ative binfmt_misc kvm_amd kvm uinput fuse loop firewire_sbp2 arc4 ecb zd1211rw 
uvcvideo videodev v4l1_compat mac80211 snd_usb_audio snd_usb_lib cfg80211 
rfkill snd_hda_codec_atihdmi snd_hda
_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep snd_pcm_oss snd_mixer_oss 
snd_pcm snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq i2c_piix4 snd_timer 
snd_seq_device pcspkr i2c_core
 snd fglrx(P) button evdev processor soundcore snd_page_alloc xfs exportfs sg 
sr_mod sd_mod cdrom ata_generic crc_t10dif usbhid hid usb_storage firewire_ohci 
r8169 pata_atiixp ahci libata m
ii ohci_hcd ehci_hcd thermal thermal_sys usbcore firewire_core nls_base 
crc_itu_t scsi_mod [last unloaded: bttv]
[38995.025157] 
[38995.025161] Pid: 21, comm: netns Tainted: P   (2.6.32-5-686-bigmem #1) MS-7646

[38995.025165] EIP: 0060:[c127e9ad] EFLAGS: 00010206 CPU: 1
[38995.025169] EIP is at _spin_lock_bh+0xd/0x1e
[38995.025172] EAX: 0100 EBX: 0008 ECX: ef91e000 EDX: 0001
[38995.025175] ESI: 0008 EDI:  EBP: ef91e000 ESP: f70d9ef8
[38995.025179]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
[38995.025182] Process netns (pid: 21, ti=f70d8000 task=f7099980 
task.ti=f70d8000)
[38995.025184] Stack:
[38995.025186]   f83ea108 f83ec5f8 ef91e000   f83ea504 
fff2
[38995.025201] 0 0296 0006 f8dc50f0 f8dc59e8 adb46683 f83ec5f8 
ffee c1280638
[38995.025219] 0 ef91e000 0006 ef91e000 f4308940 f70d9fb0 f4308950 
c104d766 
[38995.025235] Call Trace:
[38995.025241]  [f83ea108] ? phonet_device_destroy+0x54/0xf8 [phonet]
[38995.025245]  [f83ea504] ? phonet_device_notify+0x94/0xae [phonet]
[38995.025251]  [f8dc50f0] ? netconsole_netdev_event+0xa4/0xab [netconsole]
[38995.025255]  [c1280638] ? notifier_call_chain+0x2a/0x47
[38995.025260]  [c104d766] ? raw_notifier_call_chain+0x9/0xc
[38995.025265]  [c11ea290] ? rollback_registered+0x9a/0xec
[38995.025269]  [c11ea311] ? unregister_netdevice+0x2f/0x54
[38995.025273]  [c11ea345] ? unregister_netdev+0xf/0x15
[38995.025277]  [c11e6093] ? cleanup_net+0x43/0x7d
[38995.025281]  [c10473c7] ? worker_thread+0x141/0x1bd
[38995.025284]  [c11e6050] ? cleanup_net+0x0/0x7d
[38995.025288]  [c104a0fe] ? autoremove_wake_function+0x0/0x2d
[38995.025292]  [c1047286] ? worker_thread+0x0/0x1bd
[38995.025295]  [c1049ecc] ? kthread+0x61/0x66
[38995.025299]  [c1049e6b] ? kthread+0x0/0x66
[38995.025304]  [c1008d27] ? kernel_thread_helper+0x7/0x10
[38995.025306] Code: e8 f1 fd ff ff 5b c3 53 89 c3 e8 42 ca db ff 89 d8 f0 83 28 01 
79 05 e8 f6 fd ff ff 5b c3 53 89 c3 e8 2b ca db ff b8 00 01 00 00 f0 66 0f c1 
03 38 e0 74 06 f3 90 8a 0
3 eb f6 5b c3 53 89 c3 e8 
[38995.025448] EIP: [c127e9ad] _spin_lock_bh+0xd/0x1e SS:ESP 0068:f70d9ef8

[38995.025456] CR2: 0008
[38995.025459] ---[ end trace e36124e232b8b66b ]---
[38995.025462] Kernel panic - not syncing: Fatal exception in interrupt
[38995.025466] Pid: 21, comm: netns Tainted: P  D2.6.32-5-686-bigmem #1
[38995.025469] Call Trace:
[38995.025473]  [c127ce3a] ? panic+0x38/0xe4
[38995.025476]  [c127f441] ? oops_end+0x91/0x9d
[38995.025481]  [c1020c66] ? no_context+0x134/0x13d
[38995.025485]  [c1020d84] ? __bad_area_nosemaphore+0x115/0x11d
[38995.025490]  [c122928c] ? snmp_mib_free+0x1a/0x29
[38995.025494]  [c1249511] ? addrconf_ifdown+0x23f/0x260
[38995.025498]  [c124ac14] ? addrconf_notify+0x6a4/0x776
[38995.025501]  [c1280307] ? do_page_fault+0x0/0x307
[38995.025505]  [c1020d96] ? bad_area_nosemaphore+0xa/0xc
[38995.025509]  [c127eb33] ? error_code+0x73/0x78
[38995.025513]  [c127e9ad] ? _spin_lock_bh+0xd/0x1e
[38995.025517]  [f83ea108] ? phonet_device_destroy+0x54/0xf8 [phonet]
[38995.025522]  [f83ea504] ? phonet_device_notify+0x94/0xae [phonet]
[38995.025527]  [f8dc50f0] ? netconsole_netdev_event+0xa4/0xab [netconsole]

Bug#594089: keyboard-configuration: caps lock keycode problem

2010-10-27 Thread Dmitry Torokhov
On Tue, Oct 26, 2010 at 05:04:44PM -0400, Tom Vier wrote:
 On 10/26/2010 12:18 PM, Dmitry Torokhov wrote:
 Hmm, it looks like it uses the same usages (MSC_SCAN) for
 CapsLock/Favorites and RightShift/Previous... What does lsusb say about
 the keyboard (VID/PID)?
 
 The scroll wheel on the keyboard is a separate device:
 
 Bus 005 Device 003: ID 046d:c30a Logitech, Inc. iTouch Composite
 Bus 005 Device 002: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse
 

Thanks Tom. This device is handled by drivers/hid/hid-lg.c sub-driver
and there seem to be a few issues there, still I do not see how they can
produce the results you are seeing.

First of all, the device appears to use duplicate usages for
CapsLock/Favorites and RightShift/Previous so we better set up the
duplicate usages quirk. I wonder how the other OS copes with diferent
keys using the same usages. Jiri, any ideas?

Also, based on evtest data I only see presses/releases for one key (Caps
Lock, Right Shift, etc.) I do not see the presses for the additional
keys in the evtest stream so I am baffled as to where the additional
scancode is coming from... Do you have some funky keymap loaded?
Anything interesting in dumpkeys?

-- 
Dmitry

Input: hid-lgff - mark Logitech Elite as having duplicate reports

From: Dmitry Torokhov dmitry.torok...@gmail.com

Also make sure we clear bits when mapping keys to ensure that
hid-input will not try to add more keycodes.

Signed-off-by: Dmitry Torokhov d...@mail.ru
---

 drivers/hid/hid-lg.c |   59 ++
 1 files changed, 40 insertions(+), 19 deletions(-)


diff --git a/drivers/hid/hid-lg.c b/drivers/hid/hid-lg.c
index b629fba..2979b68 100644
--- a/drivers/hid/hid-lg.c
+++ b/drivers/hid/hid-lg.c
@@ -78,8 +78,8 @@ static __u8 *lg_report_fixup(struct hid_device *hdev, __u8 
*rdesc,
return rdesc;
 }
 
-#define lg_map_key_clear(c)hid_map_usage_clear(hi, usage, bit, max, \
-   EV_KEY, (c))
+#define lg_map_key_clear(c) \
+   hid_map_usage_clear(hi, usage, bit, max, EV_KEY, (c))
 
 static int lg_ultrax_remote_mapping(struct hid_input *hi,
struct hid_usage *usage, unsigned long **bit, int *max)
@@ -88,6 +88,7 @@ static int lg_ultrax_remote_mapping(struct hid_input *hi,
return 0;
 
set_bit(EV_REP, hi-input-evbit);
+
switch (usage-hid  HID_USAGE) {
/* Reported on Logitech Ultra X Media Remote */
case 0x004: lg_map_key_clear(KEY_AGAIN);break;
@@ -168,8 +169,10 @@ static int lg_wireless_mapping(struct hid_input *hi, 
struct hid_usage *usage,
case 0x102a: lg_map_key_clear(KEY_BACK);break;
case 0x102b: lg_map_key_clear(KEY_CYCLEWINDOWS);break;
case 0x102d: lg_map_key_clear(KEY_WWW); break;
-   /* The following two are 'Start/answer call' and 'End/reject call'
-  on the MX3200 */
+   /*
+* The following two are 'Start/answer call' and 'End/reject call'
+* on the MX3200
+*/
case 0x1031: lg_map_key_clear(KEY_OK);  break;
case 0x1032: lg_map_key_clear(KEY_CANCEL);  break;
case 0x1041: lg_map_key_clear(KEY_BATTERY); break;
@@ -195,17 +198,35 @@ static int lg_input_mapping(struct hid_device *hdev, 
struct hid_input *hi,
struct hid_field *field, struct hid_usage *usage,
unsigned long **bit, int *max)
 {
-   /* extended mapping for certain Logitech hardware (Logitech cordless
-  desktop LX500) */
+   /*
+* Extended mapping for certain Logitech hardware (such as
+* Logitech cordless desktop LX500)
+*/
static const u8 e_keymap[] = {
- 0,216,  0,213,175,156,  0,  0,  0,  0,
-   144,  0,  0,  0,  0,  0,  0,  0,  0,212,
-   174,167,152,161,112,  0,  0,  0,154,  0,
- 0,  0,  0,  0,  0,  0,  0,  0,  0,  0,
- 0,  0,  0,  0,  0,  0,  0,  0,  0,  0,
- 0,  0,  0,  0,  0,  0,  0,  0,  0,  0,
- 0,  0,  0,  0,  0,183,184,185,186,187,
-   188,189,190,191,192,193,194,  0,  0,  0
+   [ 1] = KEY_CHAT,
+   [ 3] = KEY_SOUND,
+   [ 4] = KEY_MOVE,
+   [ 5] = KEY_BOOKMARKS,
+   [10] = KEY_FILE,
+   [19] = KEY_CAMERA,
+   [20] = KEY_EXIT,
+   [21] = KEY_RECORD,
+   [22] = KEY_SCREENLOCK,
+   [23] = KEY_EJECTCD,
+   [24] = KEY_MACRO,
+   [28] = KEY_CYCLEWINDOWS,
+   [65] = KEY_F13,
+   [66] = KEY_F14,
+   [67] = KEY_F15,
+   [68] = KEY_F16,
+   [69] = KEY_F17,
+   [70] = KEY_F18,
+   [71] = KEY_F19,
+   [72] = KEY_F20,
+   [73] = KEY_F21,
+   [74] = KEY_F22,
+   [75] = KEY_F23,
+   

Bug#601449: closed by Ben Hutchings b...@decadent.org.uk (Re: Bug#601449: linux-image-2.6-686: SCSI scanner not recognized at boot time - SCSI subsystem not active)

2010-10-27 Thread Ben Hutchings
On Tue, 2010-10-26 at 22:59 +0200, Sebastian Niehaus wrote:
  | rescan-scsi-bus.sh
  | Error: SCSI subsystem not active
  [...]
 
  This script is buggy; you need to remove the lines:
 
  if test ! -d /proc/scsi/; then
echo Error: SCSI subsystem not active
exit 1
  fi  
 
 Okay, the scanner was found now. 
 
 Thanks. 
 
 Will there be a fixed version of the script in the next update? 

I wasn't aware that this script was shipped in Debian.  But I see it's
part of the scsitools package, so I'll reassign the bug.

Ben.

-- 
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.


signature.asc
Description: This is a digitally signed message part


Bug#597904: phonet/chromium kernel oops still in 2.6.32-26

2010-10-27 Thread Ben Hutchings
On Wed, 2010-10-27 at 10:02 +0200, debbug597904.597904.iri...@xoxy.net
wrote:
 Hi,
 
 I am still seeing kernel panics with the 2.6.32-26 version of the 
 kernel currently in squeeze.
 Indeed, I had also been running chromium on an up-to-date squeeze and 
 phonet loaded. Crashes seem to happen within a couple of hours of 
 loading phonet.
 
 Oops messages below, let me know if I can supply additional information.
[...]

Sorry about this.  It's understood and will be fixed shortly.

Ben.

-- 
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.


signature.asc
Description: This is a digitally signed message part


Bug#594089: keyboard-configuration: caps lock keycode problem

2010-10-27 Thread Samuel Thibault
Dmitry Torokhov, le Wed 27 Oct 2010 02:10:29 -0700, a écrit :
 Also, based on evtest data I only see presses/releases for one key (Caps
 Lock, Right Shift, etc.) I do not see the presses for the additional
 keys in the evtest stream so I am baffled as to where the additional
 scancode is coming from... Do you have some funky keymap loaded?
 Anything interesting in dumpkeys?

Err, since the duplicates appear in scancodes already, is the content of
dumpkeys really involved?

Samuel



--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20101027120513.gt4...@const.famille.thibault.fr



Bug#594089: keyboard-configuration: caps lock keycode problem

2010-10-27 Thread Tom Vier

On 10/27/2010 12:08 PM, Dmitry Torokhov wrote:
 On Wed, Oct 27, 2010 at 05:22:42PM +0200, Samuel Thibault wrote:
 Dmitry Torokhov, le Wed 27 Oct 2010 08:06:26 -0700, a écrit :
 Sure, but dumpkeys shows the table from scancodes to keycodes, not from
 input events to scancodes.

 I am just wondering if some of the translation is leaking even though
 the keyboard is in raw mode...

 OK, scratch that... Are there any other input devices? Anything
 connected via uinput and listening? What does /proc/bus/input/devices
 show? Maybe if Tom could compile and load evbug module it would show us
 where the additional events are coming form, becaus ethey surely are not
 generated by the keyboard itself (otherwise we'd have seen them in
 evtest output for that device).

Minor correction to what I wrote earlier about the scroll wheel. That is 
actually my mouse. It says Dell but it's really made by Logitech.


I just tried the console and what's funny is Favorites actually works as 
Capslock and Previous works as right-shift. X has the opposite problem.


In case anyone missed it, Debian Stable works fine with this keyboard. 
The keyboard on the working Stable machine is exactly the same (same usb 
id's). I'm not familiar with the input stack, but in case it is a kernel 
problem, the difference is:


Stable dist, working:
Linux zero 2.6.26-2-amd64 #1 SMP Thu Sep 16 15:56:38 UTC 2010 x86_64 
GNU/Linux


Testing dist, not working:
Linux tom 2.6.32-5-amd64 #1 SMP Fri Sep 17 21:50:19 UTC 2010 x86_64 
GNU/Linux



/proc/bus/input/devices on the problem machine:

I: Bus=0017 Vendor=0001 Product=0001 Version=0100
N: Name=Macintosh mouse button emulation
P: Phys=
S: Sysfs=/devices/virtual/input/input0
U: Uniq=
H: Handlers=mouse0 event0
B: EV=7
B: KEY=7 0 0 0 0
B: REL=3

I: Bus=0003 Vendor=046d Product=c016 Version=0110
N: Name=Logitech Optical USB Mouse
P: Phys=usb-:00:13.0-1/input0
S: Sysfs=/devices/pci:00/:00:13.0/usb5/5-1/5-1:1.0/input/input1
U: Uniq=
H: Handlers=mouse1 event1
B: EV=17
B: KEY=7 0 0 0 0
B: REL=103
B: MSC=10

I: Bus=0019 Vendor= Product=0001 Version=
N: Name=Power Button
P: Phys=PNP0C0C/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input4
U: Uniq=
H: Handlers=kbd event4
B: EV=3
B: KEY=10 0

I: Bus=0019 Vendor= Product=0001 Version=
N: Name=Power Button
P: Phys=LNXPWRBN/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input5
U: Uniq=
H: Handlers=kbd event5
B: EV=3
B: KEY=10 0

I: Bus=0010 Vendor=001f Product=0001 Version=0100
N: Name=PC Speaker
P: Phys=isa0061/input0
S: Sysfs=/devices/platform/pcspkr/input/input6
U: Uniq=
H: Handlers=kbd event6
B: EV=40001
B: SND=6

I: Bus=0003 Vendor=046d Product=c30a Version=0110
N: Name=Logitech Logitech USB Keyboard
P: Phys=usb-:00:13.0-2/input0
S: Sysfs=/devices/pci:00/:00:13.0/usb5/5-2/5-2:1.0/input/input9
U: Uniq=
H: Handlers=kbd event2
B: EV=120013
B: KEY=10007 ff8007ff febeffdfffef fffe
B: MSC=10
B: LED=1f

I: Bus=0003 Vendor=046d Product=c30a Version=0110
N: Name=Logitech Logitech USB Keyboard
P: Phys=usb-:00:13.0-2/input1
S: Sysfs=/devices/pci:00/:00:13.0/usb5/5-2/5-2:1.1/input/input10
U: Uniq=
H: Handlers=kbd mouse2 event3
B: EV=17
B: KEY=f f840334 60d8fafd01d008 1f 0
B: REL=103
B: MSC=10


--
Tom Vier t...@triadsys.com
Senior Net/Sys Admin
Triad Systems Engineering, Inc.




--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4cc870bb.2050...@triadsys.com



Bug#594089: keyboard-configuration: caps lock keycode problem

2010-10-27 Thread Dmitry Torokhov
On Wed, Oct 27, 2010 at 02:34:35PM -0400, Tom Vier wrote:
 On 10/27/2010 12:08 PM, Dmitry Torokhov wrote:
  On Wed, Oct 27, 2010 at 05:22:42PM +0200, Samuel Thibault wrote:
  Dmitry Torokhov, le Wed 27 Oct 2010 08:06:26 -0700, a écrit :
  Sure, but dumpkeys shows the table from scancodes to keycodes, not from
  input events to scancodes.
 
  I am just wondering if some of the translation is leaking even though
  the keyboard is in raw mode...
 
  OK, scratch that... Are there any other input devices? Anything
  connected via uinput and listening? What does /proc/bus/input/devices
  show? Maybe if Tom could compile and load evbug module it would show us
  where the additional events are coming form, becaus ethey surely are not
  generated by the keyboard itself (otherwise we'd have seen them in
  evtest output for that device).
 
 Minor correction to what I wrote earlier about the scroll wheel.
 That is actually my mouse. It says Dell but it's really made by
 Logitech.
 
 I just tried the console and what's funny is Favorites actually
 works as Capslock and Previous works as right-shift. X has the
 opposite problem.
 
 In case anyone missed it, Debian Stable works fine with this
 keyboard. The keyboard on the working Stable machine is exactly the
 same (same usb id's). I'm not familiar with the input stack, but in
 case it is a kernel problem, the difference is:
 
 Stable dist, working:
 Linux zero 2.6.26-2-amd64 #1 SMP Thu Sep 16 15:56:38 UTC 2010 x86_64
 GNU/Linux
 
 Testing dist, not working:
 Linux tom 2.6.32-5-amd64 #1 SMP Fri Sep 17 21:50:19 UTC 2010 x86_64
 GNU/Linux
 
 
 /proc/bus/input/devices on the problem machine:
 

...

 
 I: Bus=0003 Vendor=046d Product=c30a Version=0110
 N: Name=Logitech Logitech USB Keyboard
 P: Phys=usb-:00:13.0-2/input0
 S: Sysfs=/devices/pci:00/:00:13.0/usb5/5-2/5-2:1.0/input/input9
 U: Uniq=
 H: Handlers=kbd event2
 B: EV=120013
 B: KEY=10007 ff8007ff febeffdfffef fffe
 B: MSC=10
 B: LED=1f
 
 I: Bus=0003 Vendor=046d Product=c30a Version=0110
 N: Name=Logitech Logitech USB Keyboard
 P: Phys=usb-:00:13.0-2/input1
 S: Sysfs=/devices/pci:00/:00:13.0/usb5/5-2/5-2:1.1/input/input10
 U: Uniq=
 H: Handlers=kbd mouse2 event3
 B: EV=17
 B: KEY=f f840334 60d8fafd01d008 1f 0
 B: REL=103
 B: MSC=10
 


Hmm, this keyboard registers 2 input devices... I wonder, if you press
CapsLock/Favories and RightShift/Previous and monitor both event devices
with evtest - will it report events on both devices at once?

-- 
Dmitry



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20101027192508.ga29...@core.coreip.homeip.net



Bug#594089: keyboard-configuration: caps lock keycode problem

2010-10-27 Thread Dmitry Torokhov
On Wednesday, October 27, 2010 01:20:09 pm H Hartley Sweeten wrote:
 Wednesday, October 27, 2010 12:25 PM, Dmitry Torokhov wrote:
  I: Bus=0003 Vendor=046d Product=c30a Version=0110
  N: Name=Logitech Logitech USB Keyboard
  P: Phys=usb-:00:13.0-2/input0
  S: Sysfs=/devices/pci:00/:00:13.0/usb5/5-2/5-2:1.0/input/input9
  U: Uniq=
  H: Handlers=kbd event2
  B: EV=120013
  B: KEY=10007 ff8007ff febeffdfffef fffe
  B: MSC=10
  B: LED=1f
  
  I: Bus=0003 Vendor=046d Product=c30a Version=0110
  N: Name=Logitech Logitech USB Keyboard
  P: Phys=usb-:00:13.0-2/input1
  S: Sysfs=/devices/pci:00/:00:13.0/usb5/5-2/5-2:1.1/input/input10
  U: Uniq=
  H: Handlers=kbd mouse2 event3
  B: EV=17
  B: KEY=f f840334 60d8fafd01d008 1f 0
  B: REL=103
  B: MSC=10
  
  Hmm, this keyboard registers 2 input devices... I wonder, if you press
  CapsLock/Favories and RightShift/Previous and monitor both event devices
  with evtest - will it report events on both devices at once?
 
 I haven't really been following this thread but I think the two input
 devices is normal if the keyboard has multi-media keys.  All the extra
 keys show up as a separate input device.
 
 You might get the CapsLock and RightShift events on one device and the
 Favorites and Previous events on the other.

It is normal on sane devices however in this case there are ghost
key presses coming from an unknown source.


-- 
Dmitry



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201010271325.37935.dmitry.torok...@gmail.com



Processed: tagging 601146

2010-10-27 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 # Automatically generated email from bts, devscripts version 2.10.35lenny7
 tags 601146 + pending
Bug #601146 [linux-2.6] linux-2.6: [l10n:ca] New Catalan translation of Debconf 
templates
Ignoring request to alter tags of bug #601146 to the same tags previously set

End of message, stopping processing here.

Please contact me if you need assistance.
-- 
601146: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=601146
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/handler.s.c.128821117615185.transcr...@bugs.debian.org



Processed: tagging 601534

2010-10-27 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 # Automatically generated email from bts, devscripts version 2.10.35lenny7
 tags 601534 + pending
Bug #601534 [linux-2.6] linux-2.6: [INTL:vi] Vietnamese debconf templates 
translation update
Added tag(s) pending.

End of message, stopping processing here.

Please contact me if you need assistance.
-- 
601534: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=601534
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/handler.s.c.128821118315232.transcr...@bugs.debian.org



Processed: tagging 601102

2010-10-27 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 # Automatically generated email from bts, devscripts version 2.10.35lenny7
 tags 601102 + pending
Bug #601102 [linux-2.6] linux-2.6: [INTL:pt_BR] Brazilian Portuguese debconf 
templates translation
Ignoring request to alter tags of bug #601102 to the same tags previously set

End of message, stopping processing here.

Please contact me if you need assistance.
-- 
601102: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=601102
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/handler.s.c.128821118015214.transcr...@bugs.debian.org



Bug#594089: keyboard-configuration: caps lock keycode problem

2010-10-27 Thread H Hartley Sweeten
Wednesday, October 27, 2010 12:25 PM, Dmitry Torokhov wrote:
 
 I: Bus=0003 Vendor=046d Product=c30a Version=0110
 N: Name=Logitech Logitech USB Keyboard
 P: Phys=usb-:00:13.0-2/input0
 S: Sysfs=/devices/pci:00/:00:13.0/usb5/5-2/5-2:1.0/input/input9
 U: Uniq=
 H: Handlers=kbd event2
 B: EV=120013
 B: KEY=10007 ff8007ff febeffdfffef fffe
 B: MSC=10
 B: LED=1f
 
 I: Bus=0003 Vendor=046d Product=c30a Version=0110
 N: Name=Logitech Logitech USB Keyboard
 P: Phys=usb-:00:13.0-2/input1
 S: Sysfs=/devices/pci:00/:00:13.0/usb5/5-2/5-2:1.1/input/input10
 U: Uniq=
 H: Handlers=kbd mouse2 event3
 B: EV=17
 B: KEY=f f840334 60d8fafd01d008 1f 0
 B: REL=103
 B: MSC=10
 


 Hmm, this keyboard registers 2 input devices... I wonder, if you press
 CapsLock/Favories and RightShift/Previous and monitor both event devices
 with evtest - will it report events on both devices at once?

I haven't really been following this thread but I think the two input devices
is normal if the keyboard has multi-media keys.  All the extra keys show up
as a separate input device.

You might get the CapsLock and RightShift events on one device and the Favorites
and Previous events on the other.

Hartley


--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/0d753d10438da54287a00b027084269764819c6...@ausp01vmbx24.collaborationhost.net



Bug#601625: linux-patch-debian-2.6.32: unapplying 18 fails

2010-10-27 Thread Micah Anderson
Package: linux-patch-debian-2.6.32
Version: 2.6.32-26
Severity: normal

r...@cassowary:/usr/src/linux-source-2.6.32# 
/usr/src/kernel-patches/all/2.6.32/unpatch/debian all





-- 19 fully unapplied.
-- Try to unapply 18.
  (+) OK   bugfix/all/3c59x-Fix-call-to-mdio_sync-with-the-wrong-argument.patch
  (+) OK   debian/revert-x86-paravirt-Add-a-global-synchronization-point.patch
  (+) OK   bugfix/all/sched-fix-over-scheduling-bug.patch
  (+) OK   bugfix/x86/drm-i915-add-reclaimable-to-i915-self-reclaimable-pa.patch
  (+) OK   
features/all/rt28x0/0042-Staging-rt2860-add-Belkin-F5D8055-Wireless-N-USB-Don.patch
  (+) OK   
features/all/rt28x0/0041-Staging-rt2860-correct-onstack-wait_queue_head-decla.patch
  (+) OK   
features/all/rt28x0/0040-Staging-rt-2860-2870-sta-Use-request_firmware-to-loa.patch
  (+) OK   
features/all/rt28x0/0039-Staging-rt2870sta-constify-RTUSBMultiWrite-RTUSBFirm.patch
  (+) OK   
features/all/rt28x0/0038-Staging-rt2860-sta_ioctl.c-Two-branches-the-same-in-.patch
  (+) OK   features/all/rt28x0/0037-Staging-rt2860-Use-skb_tail_pointer.patch
  (+) OK   
features/all/rt28x0/0036-Staging-rt2870-Remove-unnecessary-forward-declaratio.patch
  (+) OK   
features/all/rt28x0/0035-Staging-rt2870-rtusb_probe-should-be-in-section-__de.patch
  (+) OK   
features/all/rt28x0/0034-Staging-rt2860-test-off-by-one-in-RtmpAsicSendComman.patch
  (+) OK   
features/all/rt28x0/0033-Staging-rt28x0-remove-no-longer-needed-common-cmm_da.patch
  (+) OK   
features/all/rt28x0/0032-Staging-rt2860-reduce-superfluous-exclamation-marks.patch
  (+) OK   
features/all/rt28x0/0031-Staging-rt28x0-fix-comments-in-chip-mac_pci.h.patch
  (+) OK   
features/all/rt28x0/0030-Staging-rt2860-remove-superfluous-newlines.patch
  (+) OK   
features/all/rt28x0/0029-Staging-rt2860-remove-remainders-of-etc-reading-stuf.patch
  (+) OK   
features/all/rt28x0/0028-Staging-rt28x0-remove-typedefs-part-three.patch
  (+) OK   
features/all/rt28x0/0027-Staging-rt28x0-remove-typedefs-part-two.patch
  (+) OK   
features/all/rt28x0/0026-Staging-rt28x0-remove-typedefs-part-one.patch
  (+) OK   
features/all/rt28x0/0025-Staging-rt28x0-fix-comments-in-.h-files.patch
  (+) OK   
features/all/rt28x0/0024-Staging-rt28x0-fix-comments-in-sta-.c-files.patch
  (+) OK   
features/all/rt28x0/0023-Staging-rt28x0-fix-comments-in-common-.c-files.patch
  (+) OK   
features/all/rt28x0/0022-Staging-rt28x0-fix-comments-in-.c-files.patch
  (+) OK   
features/all/rt28x0/0021-Staging-rt28x0-run-.h-files-through-Lindent.patch
  (+) OK   
features/all/rt28x0/0020-Staging-rt28x0-run-sta-.c-files-through-Lindent.patch
  (+) OK   
features/all/rt28x0/0019-Staging-rt28x0-run-common-.c-files-through-Lindent.patch
  (+) OK   
features/all/rt28x0/0018-Staging-rt28x0-run-.c-files-through-Lindent.patch
  (+) OK   
features/all/rt28x0/0017-Staging-rt28x0-remove-__LINE__-instances.patch
  (+) OK   features/all/rt28x0/0016-Staging-rt28x0-remove-dead-code.patch
  (+) OK   
features/all/rt28x0/0015-Staging-rt28x0-remove-unused-SHA256-code.patch
  (+) OK   
features/all/rt28x0/0014-Staging-rt28x0-remove-dead-code-from-rtmp_phy.h.patch
  (+) OK   
features/all/rt28x0/0013-Staging-rt28x0-remove-optional-cmm-profile-parameter.patch
  (+) OK   features/all/rt28x0/0012-Staging-rt28x0-fix-some-build-warnings.patch
  (+) OK   
features/all/rt28x0/0011-Staging-rt28x0-remove-optional-loading-of-EEPROM-fro.patch
  (+) OK   
features/all/rt28x0/0010-Staging-rt28x0-remove-support-for-private-driver-par.patch
  (+) OK   
features/all/rt28x0/0009-Staging-rt28x0-remove-private-WEXT-handlers.patch
  (+) OK   
features/all/rt28x0/0008-Staging-rt28x0-remove-private-RTPRIV_IOCTL_GSITESURV.patch
  (+) OK   
features/all/rt28x0/0007-Staging-rt28x0-remove-private-RTPRIV_IOCTL_SET-ioctl.patch
  (+) OK   
features/all/rt28x0/0006-Staging-rt28x0-remove-unused-code-from-common-ee_efu.patch
  (+) OK   
features/all/rt28x0/0005-Staging-rt28x0-remove-unused-eewrite-methods.patch
  (X) FAIL features/all/rt28x0/remove-rt3090-driver.commands
Error: 


-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages linux-patch-debian-2.6.32 depends on:
ii  bzip2   1.0.5-6  high-quality block-sorting file co
ii  linux-support-2.6.32-5  2.6.32-26Support files for Linux 2.6.32
ii  python  2.6.6-3+squeeze1 interactive high-level object-orie

linux-patch-debian-2.6.32 recommends no packages.

Versions of packages linux-patch-debian-2.6.32 suggests:
ii  linux-source-2.6.32   2.6.32-26  Linux kernel source for version 2.

-- no debconf information



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 

Bug#601625: linux-patch-debian-2.6.32: unapplying 18 fails

2010-10-27 Thread Ben Hutchings
On Wed, 2010-10-27 at 17:15 -0400, Micah Anderson wrote:
 Package: linux-patch-debian-2.6.32
 Version: 2.6.32-26
 Severity: normal
 
 r...@cassowary:/usr/src/linux-source-2.6.32# 
 /usr/src/kernel-patches/all/2.6.32/unpatch/debian all
[...]

Right, you can't unapply removals.  I'm not sure whether it's important
for this to work.

Ben.

-- 
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.


signature.asc
Description: This is a digitally signed message part


Bug#601322: Acknowledgement (linux: USB drives not working anymore)

2010-10-27 Thread Ben Hutchings
On Tue, 2010-10-26 at 17:41 +0200, Benoît Dejean wrote:
 2010/10/25 Ben Hutchings b...@decadent.org.uk
 In experimental, yes.  But we will release Debian 6.0
 'squeeze' with a
 kernel based on 2.6.32.
 
 
 I'm running ii  linux-image-2.6.36-rc6-amd64
 2.6.36~rc6-1~experimental.1 and same problem. Could this be an issue
 with udev or some power saving configuration ?

Probably not.  I don't see any fixes to USB between 2.6.36-rc6 and the
stable 2.6.36, so please report this upstream at
https://bugzilla.kernel.org under product 'Drivers', component 'USB'.
Let us know the bug number or URL so we can track it.

Ben.

-- 
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.


signature.asc
Description: This is a digitally signed message part


Processed: tagging 601322

2010-10-27 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 tags 601322 + moreinfo upstream
Bug #601322 [linux-2.6] linux: USB drives not working anymore
Added tag(s) upstream and moreinfo.
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
601322: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=601322
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/handler.s.c.128821849817995.transcr...@bugs.debian.org



Processed: tagging 589403

2010-10-27 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 # Automatically generated email from bts, devscripts version 2.10.35lenny7
 tags 589403 + pending
Bug #589403 [linux-2.6] linux-image-2.6.32-5-amd64: rndis_host fails to create 
an interface for an HTC tatoo phone
Added tag(s) pending.

End of message, stopping processing here.

Please contact me if you need assistance.
-- 
589403: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=589403
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/handler.s.c.128822115130203.transcr...@bugs.debian.org



Processed: tagging 600660

2010-10-27 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 # Automatically generated email from bts, devscripts version 2.10.35lenny7
 tags 600660 + pending
Bug #600660 [linux-2.6] linux-2.6: Please revert patch for USB54Gs wireless 
device
Ignoring request to alter tags of bug #600660 to the same tags previously set

End of message, stopping processing here.

Please contact me if you need assistance.
-- 
600660: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=600660
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/handler.s.c.128822115330220.transcr...@bugs.debian.org