Bug#648939: USB mouse stops work on battery power
Package: linux-2.6 Version: 3.1.1-1 Severity: normal Mouse works when the laptop is connected to power but stops about 20 seconds after power is disconnected. Re=connecting power and the mouse starts working again. This problem did not exist in 2.6.32 but did in 3.0. -- Package-specific info: ** Version: Linux version 3.1.0-1-amd64 (Debian 3.1.1-1) (b...@decadent.org.uk) (gcc version 4.6.2 (Debian 4.6.2-4) ) #1 SMP Mon Nov 14 08:02:25 UTC 2011 ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.1.0-1-amd64 root=UUID=b9dc7b52-178d-41d2-90dc-5ffb7af06598 ro quiet ** Not tainted ** Kernel log: [ 10.921574] loop: module loaded [ 11.780675] EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: (null) [ 12.551950] input: PS/2 Generic Mouse as /devices/platform/i8042/serio4/serio5/input/input12 [ 14.147453] fuse init (API version 7.17) [ 16.623745] input: ACPI Virtual Keyboard Device as /devices/virtual/input/input13 [ 19.936221] e1000e :00:19.0: irq 44 for MSI/MSI-X [ 19.992087] e1000e :00:19.0: irq 44 for MSI/MSI-X [ 19.992532] ADDRCONF(NETDEV_UP): eth0: link is not ready [ 22.502904] Bluetooth: Core ver 2.16 [ 22.502924] NET: Registered protocol family 31 [ 22.502925] Bluetooth: HCI device and connection manager initialized [ 22.502928] Bluetooth: HCI socket layer initialized [ 22.502929] Bluetooth: L2CAP socket layer initialized [ 22.502936] Bluetooth: SCO socket layer initialized [ 22.612317] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 22.612319] Bluetooth: BNEP filters: protocol multicast [ 22.672165] Bluetooth: RFCOMM TTY layer initialized [ 22.672169] Bluetooth: RFCOMM socket layer initialized [ 22.672170] Bluetooth: RFCOMM ver 1.11 [ 23.894729] lp0: using parport0 (interrupt-driven). [ 24.118226] ppdev: user-space parallel port driver [ 26.105566] Bridge firewalling registered [ 26.391395] ip_tables: (C) 2000-2006 Netfilter Core Team [ 26.935906] nf_conntrack version 0.5.0 (16384 buckets, 65536 max) [ 27.038157] ADDRCONF(NETDEV_UP): virbr0: link is not ready [ 27.448317] e1000e :00:19.0: irq 44 for MSI/MSI-X [ 27.504127] e1000e :00:19.0: irq 44 for MSI/MSI-X [ 27.504677] ADDRCONF(NETDEV_UP): eth0: link is not ready [ 28.499398] Ebtables v2.0 registered [ 28.619794] ip6_tables: (C) 2000-2006 Netfilter Core Team [ 33.731596] uhci_hcd :00:1a.0: PCI INT A disabled [ 33.731884] ehci_hcd :00:1a.7: PCI INT D disabled [ 33.731920] ehci_hcd :00:1a.7: PME# enabled [ 33.744547] uhci_hcd :00:1d.1: PCI INT B disabled [ 33.744751] uhci_hcd :00:1d.2: PCI INT C disabled [ 33.744950] ehci_hcd :00:1d.7: PCI INT D disabled [ 33.744990] ehci_hcd :00:1d.7: PME# enabled [ 33.828123] ehci_hcd :00:1a.7: BAR 0: set to [mem 0xd8826c00-0xd8826fff] (PCI address [0xd8826c00-0xd8826fff]) [ 33.828144] ehci_hcd :00:1a.7: restoring config space at offset 0xf (was 0x400, writing 0x40a) [ 33.828167] ehci_hcd :00:1a.7: restoring config space at offset 0x1 (was 0x290, writing 0x292) [ 33.828198] ehci_hcd :00:1a.7: PME# disabled [ 33.828209] ehci_hcd :00:1a.7: PCI INT D - GSI 19 (level, low) - IRQ 19 [ 33.828216] ehci_hcd :00:1a.7: setting latency timer to 64 [ 33.972086] ehci_hcd :00:1d.7: BAR 0: set to [mem 0xd8826800-0xd8826bff] (PCI address [0xd8826800-0xd8826bff]) [ 33.972107] ehci_hcd :00:1d.7: restoring config space at offset 0xf (was 0x400, writing 0x40a) [ 33.972130] ehci_hcd :00:1d.7: restoring config space at offset 0x1 (was 0x290, writing 0x292) [ 33.972171] ehci_hcd :00:1d.7: PME# disabled [ 33.972182] ehci_hcd :00:1d.7: PCI INT D - GSI 20 (level, low) - IRQ 20 [ 33.972189] ehci_hcd :00:1d.7: setting latency timer to 64 [ 34.025193] uhci_hcd :00:1a.0: PCI INT A - GSI 16 (level, low) - IRQ 16 [ 34.025200] uhci_hcd :00:1a.0: setting latency timer to 64 [ 34.073919] uhci_hcd :00:1d.1: PCI INT B - GSI 22 (level, low) - IRQ 22 [ 34.073935] uhci_hcd :00:1d.1: setting latency timer to 64 [ 34.115264] uhci_hcd :00:1d.2: PCI INT C - GSI 18 (level, low) - IRQ 18 [ 34.115281] uhci_hcd :00:1d.2: setting latency timer to 64 [ 34.818238] e1000e :00:19.0: PCI INT A disabled [ 34.818246] e1000e :00:19.0: PME# enabled [ 40.602886] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro,commit=0 [ 40.693995] EXT4-fs (sda3): re-mounted. Opts: commit=0 [ 96.304601] iwlagn :02:00.0: RF_KILL bit toggled to enable radio. [ 96.388960] iwlagn :02:00.0: L1 Disabled; Enabling L0S [ 96.389338] iwlagn :02:00.0: Radio type=0x0-0x2-0x0 [ 96.544411] iwlagn :02:00.0: L1 Disabled; Enabling L0S [ 96.544795] iwlagn :02:00.0: Radio type=0x0-0x2-0x0 [ 96.591349] ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 97.004069] usb 3-1: new full speed USB device number 2 using uhci_hcd [ 97.176393] usb 3-1: New USB device found, idVendor=03f0, idProduct=171d [
Bug#648754: [regression] suspend is flakey, shutdown -h now does not power off
Hello Jonathan Thanks a lot for your advices. Before I report upstream, here are some answers to your questions. Hmm. Someone else reported trouble on a Compal laptop a short while ago upstream[1]. [1] http://thread.gmane.org/gmane.linux.acpi.devel/50155 I had not found this one. Thanks. I will also contact this guy directly. I don't suspect it will change anything, but could you test with pci=nocrs on the kernel command line? No change, except from the comment in the log. I'll leave interpreting ACPI tables to the experts. Next time, please use attachments instead of copy+paste. I'm sorry for that. Hm, interesting. Does pcie_aspm=off on the newer kernels make a difference? (I don't think it will, but seems worth a try.) No. Because I'm incredibly lazy: can you check if this is the same as the acpidump from the system that doesn't work (3.x)? I did some diffs. Interesting summary: All acpidump obtained from non-working kernels are identical. There is a difference between the acpidump when the power off is working and when it does not work: $ diff acpidump-not-working acpidump-working 2805a2806,2813 RSDT @ 0xaf7fe0ac : 52 53 44 54 58 00 00 00 01 8a 49 4e 53 59 44 45 RSDTX.INSYDE 0010: 48 52 20 43 52 42 20 20 01 00 00 00 20 20 20 20 HR CRB 0020: 13 00 00 01 00 c0 7f af 00 d0 7f af 00 b0 7f af 0030: 00 a0 7f af 00 90 7f af 00 f0 7e af 00 e0 7e af ..~...~. 0040: 00 d0 7e af 00 b0 7e af 00 80 7e af 00 70 7e af ..~...~...~..p~. 0050: 00 60 7e af 00 50 7e af .`~..P~. Next step: upstream report Thanks again for your time. Matt -- 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/4ec38919.1070...@gmail.com
Bug#648944: (no subject)
Subject: linux-image-3.0.0-1-amd64: Each time I boot I see message: Error inserting padlock_sha and etc Package: linux-2.6 Version: 3.0.0-3 Severity: minor Dear Maintainer, I do not know how it results in total system working. But just for Your information. -- Package-specific info: ** Version: Linux version 3.0.0-1-amd64 (Debian 3.0.0-3) (b...@decadent.org.uk) (gcc version 4.5.3 (Debian 4.5.3-8) ) #1 SMP Sat Aug 27 16:21:11 UTC 2011 ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.0.0-1-amd64 root=UUID=993c69c1-2673-43a7-8cff-c38a3246fd68 ro quiet pci=use_crs ** Not tainted ** Kernel log: [ 1920.680233] [a013ffdc] ? ext4_da_write_begin+0xa6/0x221 [ext4] [ 1920.680239] [810ed34e] ? kmem_cache_free+0x2d/0x69 [ 1920.680251] [a00a6c6d] ? jbd2_journal_stop+0x205/0x217 [jbd2] [ 1920.680257] [810b5627] ? generic_file_buffered_write+0xf6/0x219 [ 1920.680276] [a015305c] ? __ext4_journal_stop+0x72/0x78 [ext4] [ 1920.680284] [810b6d51] ? __generic_file_aio_write+0x248/0x278 [ 1920.680290] [8103840a] ? should_resched+0x5/0x24 [ 1920.680294] [810b6ddb] ? generic_file_aio_write+0x5a/0xb2 [ 1920.680307] [a01388a9] ? ext4_file_write+0x1ee/0x245 [ext4] [ 1920.680313] [8106e09f] ? get_futex_key+0x8d/0x27a [ 1920.680325] [a01386bb] ? ext4_llseek+0xd0/0xd0 [ext4] [ 1920.680330] [810fc193] ? do_sync_readv_writev+0x9a/0xd5 [ 1920.680336] [810383fc] ? need_resched+0x1a/0x23 [ 1920.680340] [813358d7] ? _cond_resched+0x9/0x20 [ 1920.680347] [810fb603] ? copy_from_user+0x18/0x30 [ 1920.680353] [811653e9] ? security_file_permission+0x18/0x33 [ 1920.680358] [810fc3e1] ? do_readv_writev+0xa4/0x11a [ 1920.680363] [810fcb94] ? fput+0x1a/0x1a2 [ 1920.680367] [810383fc] ? need_resched+0x1a/0x23 [ 1920.680372] [8103840a] ? should_resched+0x5/0x24 [ 1920.680377] [813358d7] ? _cond_resched+0x9/0x20 [ 1920.680382] [81335f5c] ? mutex_lock+0xd/0x2d [ 1920.680386] [810fcb94] ? fput+0x1a/0x1a2 [ 1920.680398] [a01386a9] ? ext4_llseek+0xbe/0xd0 [ext4] [ 1920.680402] [810fc5c5] ? sys_writev+0x45/0x90 [ 1920.680408] [8133bd12] ? system_call_fastpath+0x16/0x1b [ 2040.680171] INFO: task qbittorrent:3335 blocked for more than 120 seconds. [ 2040.680185] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. [ 2040.680193] qbittorrent D 88004873ce60 0 3335 3322 0x [ 2040.680210] 88004873ce60 0086 880036815fd8 [ 2040.680224] 8160b020 00012800 880036815fd8 880036815fd8 [ 2040.680235] 00012800 88004873ce60 00012800 00012800 [ 2040.680247] Call Trace: [ 2040.680270] [81335bb1] ? schedule_timeout+0x2d/0xd7 [ 2040.680281] [810bef0e] ? put_page+0x18/0x27 [ 2040.680295] [8100e28d] ? paravirt_read_tsc+0x5/0x8 [ 2040.680306] [8100e74a] ? native_sched_clock+0x28/0x30 [ 2040.680316] [8100e757] ? sched_clock+0x5/0x8 [ 2040.680326] [81064b37] ? sched_clock_local+0x10/0x75 [ 2040.680336] [81023145] ? _flat_send_IPI_mask+0x6a/0x7c [ 2040.680348] [8133598b] ? wait_for_common+0x9d/0x116 [ 2040.680359] [8103f0a4] ? try_to_wake_up+0x199/0x199 [ 2040.680370] [811186db] ? bdi_queue_work+0xb8/0xca [ 2040.680379] [8111875f] ? writeback_inodes_sb_nr+0x72/0x78 [ 2040.680390] [811187b3] ? writeback_inodes_sb_if_idle+0x2f/0x43 [ 2040.680454] [a013ffdc] ? ext4_da_write_begin+0xa6/0x221 [ext4] [ 2040.680466] [810ed34e] ? kmem_cache_free+0x2d/0x69 [ 2040.680489] [a00a6c6d] ? jbd2_journal_stop+0x205/0x217 [jbd2] [ 2040.680504] [810b5627] ? generic_file_buffered_write+0xf6/0x219 [ 2040.680542] [a015305c] ? __ext4_journal_stop+0x72/0x78 [ext4] [ 2040.680557] [810b6d51] ? __generic_file_aio_write+0x248/0x278 [ 2040.680570] [8103840a] ? should_resched+0x5/0x24 [ 2040.680579] [810b6ddb] ? generic_file_aio_write+0x5a/0xb2 [ 2040.680605] [a01388a9] ? ext4_file_write+0x1ee/0x245 [ext4] [ 2040.680617] [8106e09f] ? get_futex_key+0x8d/0x27a [ 2040.680641] [a01386bb] ? ext4_llseek+0xd0/0xd0 [ext4] [ 2040.680652] [810fc193] ? do_sync_readv_writev+0x9a/0xd5 [ 2040.680663] [810383fc] ? need_resched+0x1a/0x23 [ 2040.680673] [813358d7] ? _cond_resched+0x9/0x20 [ 2040.680685] [810fb603] ? copy_from_user+0x18/0x30 [ 2040.680698] [811653e9] ? security_file_permission+0x18/0x33 [ 2040.680707] [810fc3e1] ? do_readv_writev+0xa4/0x11a [ 2040.680716] [810fcb94] ? fput+0x1a/0x1a2 [ 2040.680725] [810383fc] ? need_resched+0x1a/0x23 [ 2040.680734] [8103840a] ? should_resched+0x5/0x24 [ 2040.680744] [813358d7] ? _cond_resched+0x9/0x20 [ 2040.680754]
Bug#648155: Patch to make nfs4 return EKEYEXPIRED to user code
This patch (for 3.1-rc10, probably works for all versions that have this problem) makes nfs4 return the EKEYEXPIRED to user level, which works well with nfs4 mounted home directories on user systems. The normal case will be that the workstation screen will be locked when the ticket expires, the user will enter her password and a new ticket will be granted. Any processes that try to access the home directory while the ticket is expired will get EKEYEXPIRED and probably give up. diff --git a/fs/nfs/nfs4proc.c b/fs/nfs/nfs4proc.c index 4700fae..dc28a78 100644 --- a/fs/nfs/nfs4proc.c +++ b/fs/nfs/nfs4proc.c @@ -302,7 +302,6 @@ static int nfs4_handle_exception(struct nfs_server *server, int errorcode, struc } case -NFS4ERR_GRACE: case -NFS4ERR_DELAY: - case -EKEYEXPIRED: ret = nfs4_delay(server-client, exception-timeout); if (ret != 0) break; @@ -3732,7 +3731,6 @@ nfs4_async_handle_error(struct rpc_task *task, const struct nfs_server *server, case -NFS4ERR_DELAY: nfs_inc_server_stats(server, NFSIOS_DELAY); case -NFS4ERR_GRACE: - case -EKEYEXPIRED: rpc_delay(task, NFS4_POLL_RETRY_MAX); task-tk_status = 0; return -EAGAIN; diff --git a/fs/nfs/nfs4state.c b/fs/nfs/nfs4state.c index 39914be..2bee41e 100644 --- a/fs/nfs/nfs4state.c +++ b/fs/nfs/nfs4state.c @@ -1377,8 +1377,9 @@ static int nfs4_recovery_handle_error(struct nfs_client *clp, int error) /* Zero session reset errors */ return 0; case -EKEYEXPIRED: - /* Nothing we can do */ - nfs4_warn_keyexpired(clp-cl_hostname); + /* Nothing we can do, so do nothing. Don't even + print a warning message, this is not a kernel + problem */ return 0; } return error;
Bug#648811: Another stack trace.
Using the same process (kill the peer and mount the filesystem on spare node) gave us another stack trace today: Nov 16 11:46:03 wab2 kernel: [ 376.733674] ocfs2_dlm: Nodes in domain (57A2D6D463094E759EBEAB9D0775A4BB): 6 Nov 16 11:46:03 wab2 kernel: [ 376.779332] ocfs2: Mounting device (147,1) on (node 6, slot 1) with ordered data mode. Nov 16 11:46:03 wab2 kernel: [ 376.779795] [ cut here ] Nov 16 11:46:03 wab2 kernel: [ 376.781394] kernel BUG at /build/buildd-linux-2.6_2.6.32-38-i386-G9QRBd/linux-2.6-2.6.32/debian/build/source_i386_none/fs/ocfs2/journal.c:1702! Nov 16 11:46:03 wab2 kernel: [ 376.783299] invalid opcode: [#1] SMP Nov 16 11:46:03 wab2 kernel: [ 376.783299] last sysfs file: /sys/module/drbd/parameters/cn_idx Nov 16 11:46:03 wab2 kernel: [ 376.783299] Modules linked in: ocfs2 jbd2 quota_tree sha1_generic drbd lru_cache cn fuse ocfs2_dlmfs ocfs2_stack_o2cb ocfs2_dlm ocfs2_nodemanager ocfs2_stackglue configfs nfs lockd fscache nfs_acl auth_rpcgss sunrpc ext2 loop snd_pcm snd_timer snd i2c_piix4 parport_pc soundcore snd_page_alloc parport psmouse button processor pcspkr evdev i2c_core serio_raw ext3 jbd mbcache dm_mod sg sr_mod cdrom sd_mod crc_t10dif ata_generic ata_piix thermal libata floppy thermal_sys 8139too 8139cp mii scsi_mod [last unloaded: scsi_wait_scan] Nov 16 11:46:03 wab2 kernel: [ 376.783299] Nov 16 11:46:03 wab2 kernel: [ 376.783299] Pid: 2186, comm: ocfs2rec Not tainted (2.6.32-5-686 #1) Bochs Nov 16 11:46:03 wab2 kernel: [ 376.783299] EIP: 0060:[e15cc47a] EFLAGS: 00010246 CPU: 0 Nov 16 11:46:03 wab2 kernel: [ 376.783299] EIP is at __ocfs2_recovery_thread+0x3af/0x146d [ocfs2] Nov 16 11:46:03 wab2 kernel: [ 376.783299] EAX: 0006 EBX: ddca0800 ECX: 0001 EDX: 0001 Nov 16 11:46:03 wab2 kernel: [ 376.783299] ESI: 0001 EDI: df9ca408 EBP: ESP: de6cded4 Nov 16 11:46:03 wab2 kernel: [ 376.783299] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 Nov 16 11:46:03 wab2 kernel: [ 376.783299] Process ocfs2rec (pid: 2186, ti=de6cc000 task=ddfdc880 task.ti=de6cc000) Nov 16 11:46:03 wab2 kernel: [ 376.783299] Stack: Nov 16 11:46:03 wab2 kernel: [ 376.783299] ddfdc880 ddfdc880 ddca089c 0006 0001 ddca0800 df9ca408 df9ca400 Nov 16 11:46:03 wab2 kernel: [ 376.783299] 0 0002 c1c08138 c1025617 ddfdc880 df88fb80 c1001f10 c1c05e20 Nov 16 11:46:03 wab2 kernel: [ 376.783299] 0 df88fbb4 df88fbac c1c08138 c1c08100 df88fb80 df88fbac df88fbac 007eb000 Nov 16 11:46:03 wab2 kernel: [ 376.783299] Call Trace: Nov 16 11:46:03 wab2 kernel: [ 376.783299] [c1025617] ? dequeue_entity+0x15/0x14c Nov 16 11:46:03 wab2 WAB(root)[1184]: OK Nov 16 11:46:03 wab2 kernel: [ 376.783299] [c1001f10] ? __switch_to+0xcf/0x141 Nov 16 11:46:03 wab2 kernel: [ 376.783299] [c102b636] ? finish_task_switch+0x34/0x95 Nov 16 11:46:03 wab2 kernel: [ 376.783299] [c126d68e] ? schedule+0x78f/0x7dc Nov 16 11:46:03 wab2 kernel: [ 376.783299] [c102d4f4] ? try_to_wake_up+0x2a7/0x2b3 Nov 16 11:46:03 wab2 kernel: [ 376.783299] [c10207c5] ? __wake_up_common+0x34/0x59 Nov 16 11:46:03 wab2 kernel: [ 376.783299] [e15cc0cb] ? __ocfs2_recovery_thread+0x0/0x146d [ocfs2] Nov 16 11:46:03 wab2 kernel: [ 376.783299] [c1043dfc] ? kthread+0x61/0x66 Nov 16 11:46:03 wab2 kernel: [ 376.783299] [c1043d9b] ? kthread+0x0/0x66 Nov 16 11:46:03 wab2 kernel: [ 376.783299] [c1003d47] ? kernel_thread_helper+0x7/0x10 Nov 16 11:46:03 wab2 kernel: [ 376.783299] Code: 00 00 68 24 a7 60 e1 50 ff b2 2c 01 00 00 68 49 37 61 e1 e8 22 09 ca df 83 c4 20 8b 5c 24 14 8b 44 24 0c 39 83 bc 00 00 00 75 04 0f 0b eb fe 8d 84 24 d0 00 00 00 c7 84 24 d0 00 00 00 00 00 00 Nov 16 11:46:03 wab2 kernel: [ 376.783299] EIP: [e15cc47a] __ocfs2_recovery_thread+0x3af/0x146d [ocfs2] SS:ESP 0068:de6cded4 Nov 16 11:46:03 wab2 kernel: [ 376.828911] ---[ end trace 06d533c2f6318b49 ]---
Bug#648766: [sparc-unstable] kernel crash
I found this very similar BUG report: http://old.nabble.com/Ext4-stable-yet--td31660435.html Kind Regards, Tibor -- 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/4ec396db.1060...@gmail.com
Re: [PATCH] bonding: Don't allow mode change via sysfs with slaves present
Le 15/11/2011 21:47, Andy Gospodarek a écrit :
Nicolas,
I took a look at the ifenslave package for debian more closely and it
actually looks like devices are enslaved last, after mode is set. Can
you please take a look at this package and confirm what I'm seeing in
the 'pre-up' script.
It appears to me that setup_master sets the mode and enslave_slaves is
called after and enslaves the devices:
# Option slaves deprecated, replaced by bond-slaves, but still supported
# for backward compatibility.
IF_BOND_SLAVES=${IF_BOND_SLAVES:-$IF_SLAVES}
if [ $IF_BOND_MASTER ] ; then
BOND_MASTER=$IF_BOND_MASTER
BOND_SLAVES=$IFACE
else
if [ $IF_BOND_SLAVES ] ; then
BOND_MASTER=$IFACE
BOND_SLAVES=$IF_BOND_SLAVES
fi
fi
# Exit if nothing to do...
[ -z $BOND_MASTER$BOND_SLAVES ] exit
add_master
early_setup_master
setup_master
enslave_slaves
exit 0
Andy,
I'm really surprise by this extract. In the most up to date version of the ifenslave-2.6 package
(1.1.0-19), the order is:
add_master
early_setup_master
enslave_slaves
setup_master
early_setup_master was created to be able to do things that absolutely need to be done before
enslavement. (See the comment just before this function). The idea was to do every possible setup in
setup_master, after enslavement, except those that need to be done in early_setup_master. So having
enslave_slaves after setup_master instead of before is definitely a mistake. Some of the operations
in setup_master must be done after enslavement, in particular selecting the primary slave.
In version 1.1.0-18 (change log below), I checked all the possible order constraints of the sysfs
interface and totally reworked most of the setup code, putting everything in the right order to
achieve consistent results.
ifenslave-2.6 (1.1.0-18) experimental; urgency=low
* Apply patch from Nicolas de Pesloüan:
- Major change: Check and fix the order in which the configuration
is
written into /sys files, to ensure reliable results, according to
the
tests done in the kernel (in drivers/net/bonding/bond_sysfs.c).
- Ensure that master is properly brought down when changing a
parameter
that require it to be down.
- Ensure the master is brought up at the end of the setup, in the
case
where ifup won't bring it up because it is currently configuring
a slave.
- Add support for some previously unsupported /sys files: ad_select,
num_grat_arp, num_unsol_na, primary_reselect and queue_id.
- Enhance the documentation (README.Debian), to describe all the
currently
supported bond-* options.
- Many other changes in the documentation.
- Reverse the order of the arguments to most sysfs_* internal
functions, for
better readability.
It was a hard work, because there really exist many such constraints. I fail to find enough time to
insert the result of this work into Documentation/networking/bonding.txt, but still plan to do so,
even if the result is documented in the script you looked at.
Of course, it is possible to change the scripts in ifenslave-2.6 package to arrange for one more
constraint. For as far as I understand, this would cause the Debian kernel that introduce the change
we discuss about and all the future Debian kernels to be flagged with 'Breaks: ifenslave-2.6 (
1.1.0-20)'. I'm not really comfortable with this and the Debian kernel team need to be involved. I
copied them.
All that being said, I really advocate for less constraints on the sysfs setup. This is not strictly
related to sysfs setup. If we eventually add a NETLINK interface for all the things we can setup
using sysfs, we will face the exact same problem.
I perfectly understand, as Veaceslav noted in another email that there are a lot of mode-specific
initialization stuff that's present only in bond_enslave(), but I think this is what needs to be
fixed... Those initialization stuff should be moved out of bond_enslave() and called at appropriate
sime, from bond_enslave() and from other locations, in particular when changing mode.
Nicolas.
--
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/4ec3a64d.40...@gmail.com
Bug#648963: drbd8-modules-2.6.26-2-xen-amd64: initial sync failed for new drbd device
Package: drbd8-modules-2.6.26-2-xen-amd64 Version: 2.6.26+8.0.14-6+lenny3 Severity: normal Hello, I am using Debian GNU/Linux Lenny on servers with xen and drbd. Since upgrade to 5.0.9, it's impossible to synchronise a new drbd device. All works well until upgrade to 5.0.9. All package and software come from official debian repository and installed with apt-get install. packages uses : drbd8-modules-2.6-xen-amd64 drbd8-modules-2.6.26-2-xen-amd64 linux-image-2.6-amd64 linux-image-2.6.26-2-amd64 linux-image-2.6.26-2-xen-amd64 linux-modules-2.6-xen-amd64 linux-modules-2.6.26-2-xen-amd64 xen-hypervisor-3.2-1-amd64 xen-linux-system-2.6.26-2-xen-amd64 when I downgrade linux-image, linux-modules and xen-linux-system to previous lenny3 version and it seem to work ** syslog trace of the SyncSource drbd server ** Nov 14 14:38:51 gaia kernel: [ 1599.990319] drbd0: role( Secondary - Primary ) disk( Inconsistent - UpToDate ) Nov 14 14:38:51 gaia kernel: [ 1600.004521] drbd0: Forced to consider local data as UpToDate! Nov 14 14:38:51 gaia kernel: [ 1600.004607] drbd0: Creating new current UUID Nov 14 14:38:51 gaia kernel: [ 1600.029333] drbd0: drbd_sync_handshake: Nov 14 14:38:51 gaia kernel: [ 1600.029417] drbd0: self 098F31DB0B8EEBDF:0004:: Nov 14 14:38:51 gaia kernel: [ 1600.029513] drbd0: peer 0004::: Nov 14 14:38:51 gaia kernel: [ 1600.029608] drbd0: uuid_compare()=2 by rule 3 Nov 14 14:38:51 gaia kernel: [ 1600.029676] drbd0: Becoming sync source due to disk states. Nov 14 14:38:51 gaia kernel: [ 1600.029748] drbd0: Writing the whole bitmap, full sync required after drbd_sync_handshake. Nov 14 14:38:51 gaia kernel: [ 1600.031787] drbd0: 8192 MB (2097079 bits) marked out-of-sync by on disk bit-map. Nov 14 14:38:51 gaia kernel: [ 1600.032357] drbd0: conn( Connected - WFBitMapS ) Nov 14 14:38:51 gaia kernel: [ 1600.041962] drbd0: conn( WFBitMapS - SyncSource ) Nov 14 14:38:51 gaia kernel: [ 1600.042038] drbd0: Began resync as SyncSource (will sync 8388316 KB [2097079 bits set]). Nov 14 14:38:51 gaia kernel: [ 1600.044222] drbd0: alloc_ee: bio_add_page(s=0,data_size=32768,ds=28672) failed Nov 14 14:38:51 gaia kernel: [ 1600.044319] drbd0: bio-bi_max_vecs = 16 in /build/buildd-linux-modules-extra-2.6_2.6.26-6+lenny3-amd64-Okr01R/linux- modules- extra-2.6-2.6.26/debian/build/build_amd64_xen_amd64_drbd8/drbd/drbd_receiver.c:253 Nov 14 14:38:51 gaia kernel: [ 1600.044454] drbd0: bio-bi_vcnt = 1 in /build /buildd-linux-modules-extra-2.6_2.6.26-6+lenny3-amd64-Okr01R/linux-modules- extra-2.6-2.6.26/debian/build/build_amd64_xen_amd64_drbd8/drbd/drbd_receiver.c:254 Nov 14 14:38:51 gaia kernel: [ 1600.044562] drbd0: bio-bi_size = 4096 in /build/buildd-linux-modules-extra-2.6_2.6.26-6+lenny3-amd64-Okr01R/linux- modules- extra-2.6-2.6.26/debian/build/build_amd64_xen_amd64_drbd8/drbd/drbd_receiver.c:255 Nov 14 14:38:51 gaia kernel: [ 1600.044689] drbd0: bio-bi_phys_segments = 1 in /build/buildd-linux-modules-extra-2.6_2.6.26-6+lenny3-amd64-Okr01R/linux- modules- extra-2.6-2.6.26/debian/build/build_amd64_xen_amd64_drbd8/drbd/drbd_receiver.c:256 Nov 14 14:38:51 gaia kernel: [ 1600.044798] drbd0: bio-bi_hw_segments = 1 in /build/buildd-linux-modules-extra-2.6_2.6.26-6+lenny3-amd64-Okr01R/linux- modules- extra-2.6-2.6.26/debian/build/build_amd64_xen_amd64_drbd8/drbd/drbd_receiver.c:257 Nov 14 14:38:51 gaia kernel: [ 1600.044910] drbd0: error receiving RSDataRequest, l: 24! Nov 14 14:38:51 gaia kernel: [ 1600.044980] drbd0: peer( Secondary - Unknown ) conn( SyncSource - ProtocolError ) Nov 14 14:38:51 gaia kernel: [ 1600.045073] drbd0: asender terminated Nov 14 14:38:51 gaia kernel: [ 1600.050318] drbd0: Terminating asender thread Nov 14 14:38:51 gaia kernel: [ 1600.051098] drbd0: Connection closed Nov 14 14:38:51 gaia kernel: [ 1600.051167] drbd0: conn( ProtocolError - Unconnected ) Nov 14 14:38:51 gaia kernel: [ 1600.051237] drbd0: receiver terminated Nov 14 14:38:51 gaia kernel: [ 1600.051304] drbd0: Restarting receiver thread Nov 14 14:38:51 gaia kernel: [ 1600.051371] drbd0: receiver (re)started Nov 14 14:38:51 gaia kernel: [ 1600.051439] drbd0: conn( Unconnected - WFConnection ) -- System Information: Debian Release: 6.0.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') 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 -- 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/2016125407.4132.44784.report...@rhea.banquise.rdtronic.net
Bug#645811: inux-image-3.0.0-2-686-pae: lirc_serial spuriously claims assigned port and irq to be in use
Ben, So when you got the configuration right the driver still failed, because the IRQ was already allocated. the funny thing is: the lirc_serial driver *does* work when share_irq=1 is added to the parameters specified in /etc/modprobe.d/lirc_serial.conf. At least, I can now happily use my remote control to navigate through MythTV. If you like, I can send you the dmesg ouput of the now working configuration (but not before tomorrow night, I'm afraid). Regards -- Torsten -- 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/4ec3bb1a.7030...@ebiology.de
Bug#648966: linux-image-3.1.0-1-amd64: module brcm80211 crashes the computer when connection channel 13
Package: linux-2.6 Version: 3.1.1-1 Severity: important Dear Maintainer, When connecting on a WiFi using the channel 13 my computer becomes very very slow and eat all the CPU. Blacklisting the module makes my computer usable again (I then use tethering to connect to the internet hence the usb0 present in this bugreport). -- Package-specific info: ** Version: Linux version 3.1.0-1-amd64 (Debian 3.1.1-1) (b...@decadent.org.uk) (gcc version 4.6.2 (Debian 4.6.2-4) ) #1 SMP Mon Nov 14 08:02:25 UTC 2011 ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.1.0-1-amd64 root=UUID=817b61a4-242c-40d4-a61c-997f4b00513b ro quiet ** Not tainted ** Kernel log: [8.053192] ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no) [8.053252] [drm] Initialized i915 1.6.0 20080730 for :00:02.0 on minor 0 [8.058137] snd_hda_intel :00:1b.0: power state changed by ACPI to D0 [8.058147] snd_hda_intel :00:1b.0: power state changed by ACPI to D0 [8.058169] snd_hda_intel :00:1b.0: PCI INT A - GSI 22 (level, low) - IRQ 22 [8.058249] snd_hda_intel :00:1b.0: irq 47 for MSI/MSI-X [8.058281] snd_hda_intel :00:1b.0: setting latency timer to 64 [8.644926] input: HDA Digital PCBeep as /devices/pci:00/:00:1b.0/input/input11 [8.659942] HDMI status: Codec=3 Pin=5 Presence_Detect=0 ELD_Valid=0 [8.660275] HDMI status: Codec=3 Pin=6 Presence_Detect=0 ELD_Valid=0 [8.660607] HDMI status: Codec=3 Pin=7 Presence_Detect=0 ELD_Valid=0 [8.675788] input: HDA Intel PCH Mic at Ext Right Jack as /devices/pci:00/:00:1b.0/sound/card0/input12 [8.675909] input: HDA Intel PCH HP Out at Ext Right Jack as /devices/pci:00/:00:1b.0/sound/card0/input13 [8.676583] input: HDA Intel PCH HDMI/DP as /devices/pci:00/:00:1b.0/sound/card0/input14 [8.676650] input: HDA Intel PCH HDMI/DP as /devices/pci:00/:00:1b.0/sound/card0/input15 [8.676708] input: HDA Intel PCH HDMI/DP as /devices/pci:00/:00:1b.0/sound/card0/input16 [9.082046] Adding 7811068k swap on /dev/sda7. Priority:-1 extents:1 across:7811068k [9.085082] EXT4-fs (sda3): re-mounted. Opts: (null) [9.465932] EXT4-fs (sda3): re-mounted. Opts: errors=remount-ro [9.574148] loop: module loaded [ 11.391665] EXT4-fs (sda9): mounted filesystem with ordered data mode. Opts: (null) [ 11.416686] EXT4-fs (sda8): mounted filesystem with ordered data mode. Opts: (null) [ 11.461892] EXT4-fs (sda5): mounted filesystem with ordered data mode. Opts: (null) [ 11.504040] EXT4-fs (sda6): mounted filesystem with ordered data mode. Opts: (null) [ 12.864397] fuse init (API version 7.17) [ 18.497967] lp0: using parport0 (interrupt-driven). [ 18.500870] ppdev: user-space parallel port driver [ 23.098613] pg_ctlcluster (2239): /proc/2239/oom_adj is deprecated, please use /proc/2239/oom_score_adj instead. [ 31.283273] e1000e :00:19.0: PME# enabled [ 33.174731] e1000e :00:19.0: BAR 0: set to [mem 0xd470-0xd471] (PCI address [0xd470-0xd471]) [ 33.174749] e1000e :00:19.0: BAR 1: set to [mem 0xd472a000-0xd472afff] (PCI address [0xd472a000-0xd472afff]) [ 33.174762] e1000e :00:19.0: BAR 2: set to [io 0x4060-0x407f] (PCI address [0x4060-0x407f]) [ 33.174800] e1000e :00:19.0: restoring config space at offset 0xf (was 0x100, writing 0x10a) [ 33.174818] e1000e :00:19.0: restoring config space at offset 0x1 (was 0x10, writing 0x17) [ 33.174859] e1000e :00:19.0: PME# disabled [ 33.321909] e1000e :00:19.0: irq 44 for MSI/MSI-X [ 33.374704] e1000e :00:19.0: irq 44 for MSI/MSI-X [ 33.375470] ADDRCONF(NETDEV_UP): eth0: link is not ready [ 34.558277] e1000e :00:19.0: PCI INT A disabled [ 34.558286] e1000e :00:19.0: PME# enabled [ 40.291226] usb 2-1.2: new high speed USB device number 5 using ehci_hcd [ 55.355532] usb 2-1.2: device descriptor read/64, error -110 [ 70.523764] usb 2-1.2: device descriptor read/64, error -110 [ 70.699673] usb 2-1.2: new high speed USB device number 6 using ehci_hcd [ 85.763833] usb 2-1.2: device descriptor read/64, error -110 [ 100.932077] usb 2-1.2: device descriptor read/64, error -110 [ 101.107980] usb 2-1.2: new high speed USB device number 7 using ehci_hcd [ 106.125373] usb 2-1.2: device descriptor read/8, error -110 [ 111.242717] usb 2-1.2: device descriptor read/8, error -110 [ 111.418752] usb 2-1.2: new high speed USB device number 8 using ehci_hcd [ 116.436144] usb 2-1.2: device descriptor read/8, error -110 [ 121.553478] usb 2-1.2: device descriptor read/8, error -110 [ 121.657459] hub 2-1:1.0: unable to enumerate USB device on port 2 [ 257.267798] usb 2-1.2: new high speed USB device number 9 using ehci_hcd [ 272.331957] usb 2-1.2: device descriptor read/64, error -110 [ 287.500165] usb 2-1.2: device descriptor read/64, error -110 [ 287.676111] usb 2-1.2: new high speed USB device number 10 using ehci_hcd [
Processed: reassign 648944 to src:linux-2.6 ..., forcibly merging 568008 648944
Processing commands for cont...@bugs.debian.org: reassign 648944 src:linux-2.6 3.0.0-3 Bug #648944 [linux-2.6] (no subject) Bug reassigned from package 'linux-2.6' to 'src:linux-2.6'. Bug No longer marked as found in versions 3.0.0-3. Bug #648944 [src:linux-2.6] (no subject) Bug Marked as found in versions linux-2.6/3.0.0-3. retitle 648944 linux-image-3.0.0-1-amd64: Each time I boot I see message: Error inserting padlock_sha and etc Bug #648944 [src:linux-2.6] (no subject) Changed Bug title to 'linux-image-3.0.0-1-amd64: Each time I boot I see message: Error inserting padlock_sha and etc' from '(no subject)' forcemerge 568008 648944 Bug#568008: linux-image-2.6.32-trunk-amd64: Error inserting padlock_sha: No such device Bug#648944: linux-image-3.0.0-1-amd64: Each time I boot I see message: Error inserting padlock_sha and etc Forcibly Merged 568008 648944. thanks Stopping processing here. Please contact me if you need assistance. -- 568008: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=568008 648944: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=648944 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.13214538859328.transcr...@bugs.debian.org
Bug#648155: Patch to make nfs4 return EKEYEXPIRED to user code
On Wed, 2011-11-16 at 11:47 +0100, John Hughes wrote: This patch (for 3.1-rc10, probably works for all versions that have this problem) makes nfs4 return the EKEYEXPIRED to user level, which works well with nfs4 mounted home directories on user systems. The normal case will be that the workstation screen will be locked when the ticket expires, the user will enter her password and a new ticket will be granted. Any processes that try to access the home directory while the ticket is expired will get EKEYEXPIRED and probably give up. Please submit this change upstream, following the instructions in Documentation/SubmittingPatches. Ben. -- Ben Hutchings The world is coming to an end. Please log off. signature.asc Description: This is a digitally signed message part
Bug#648966: linux-image-3.1.0-1-amd64: module brcm80211 crashes the computer when connection channel 13
On Wed, 2011-11-16 at 15:01 +0100, Nicolas Évrard wrote: Package: linux-2.6 Version: 3.1.1-1 Severity: important Dear Maintainer, When connecting on a WiFi using the channel 13 my computer becomes very very slow and eat all the CPU. [...] Please provide a kernel log covering the period where this happens and the initial messages from the brcm80211/bcrmsmac driver. Ben. -- Ben Hutchings The world is coming to an end. Please log off. signature.asc Description: This is a digitally signed message part
Processed: tagging 648966
Processing commands for cont...@bugs.debian.org: tags 648966 + moreinfo Bug #648966 [linux-2.6] linux-image-3.1.0-1-amd64: module brcm80211 crashes the computer when connection channel 13 Added tag(s) moreinfo. thanks Stopping processing here. Please contact me if you need assistance. -- 648966: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=648966 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.132145434310922.transcr...@bugs.debian.org
Bug#648966: linux-image-3.1.0-1-amd64: module brcm80211 crashes the computer when connection channel 13
* Ben Hutchings [2011-11-16 15:38 +0100]: On Wed, 2011-11-16 at 15:01 +0100, Nicolas Évrard wrote: Package: linux-2.6 Version: 3.1.1-1 Severity: important Dear Maintainer, When connecting on a WiFi using the channel 13 my computer becomes very very slow and eat all the CPU. [...] Please provide a kernel log covering the period where this happens and the initial messages from the brcm80211/bcrmsmac driver. As soon as I reboot, I will provide those. Can you point me to a good documentation so that I can give the more information possible ? -- (° Nicolas Évrard ( ) Liège `¯ -- 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/2016153152.gf5...@b2ck.com
Bug#649005: linux-tools: FTBFS when binNMUed
Package: linux-tools Version: 3.1.1-1 Severity: normal See https://buildd.debian.org/status/fetch.php?pkg=linux-toolsarch=amd64ver=3.1.1-1%2Bb1stamp=1321332698 bwh jcristau: For some reason linux-tools is missing the special case for binNMUs Cheers, Julien -- 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/2016183919.ga19...@radis.cristau.org
Bug#649006: linux-tools-3.1: needs rebuild against perl 5.14
Package: linux-tools-3.1 Version: 3.1.1-1 Severity: serious linux-tools-3.1/amd64 depends on libperl5.12 which makes it uninstallable in sid right now. It needs a new source upload as binNMUs don't work (see other bug). Cheers, Julien -- 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/2016184316.ga19...@radis.cristau.org
Bug#648996: linux-2.6: FTBFS [m68k] in modpost: strlen [iscsi_target_mod.ko] undefined! (and others)
Hi, Thorsten Glaser wrote: Linux 3.1 doesn’t build any more, Linux 3.0 built successfully in all its versions. Full build log attached. “amiga” is the first of the available (and needed/used) flavours, this might thus affect more or all of them. [...] MODPOST 748 modules ERROR: strlen [drivers/target/iscsi/iscsi_target_mod.ko] undefined! ERROR: strcpy [drivers/target/iscsi/iscsi_target_mod.ko] undefined! My first guess was that this might be a toolchain change, but you are still using gcc-4.4. Anyway, I assume uninlining strlen and strcpy along the lines of [1] helps? Weird. [1] http://thread.gmane.org/gmane.linux.kernel/1085365 -- 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/2016200315.gb28...@elie.hsd1.il.comcast.net
Processed: block 637809 with 649004, block 637809 with 649006
Processing commands for cont...@bugs.debian.org: # libbsd-resource-perl/ki block 637809 with 649004 Bug #637809 [release.debian.org] transition: perl 5.14 Was blocked by: 646297 628507 637602 638894 640347 628499 643038 646299 646286 636132 640346 646295 638367 636762 629255 636651 642146 628505 639677 634531 628503 636656 647120 628501 634141 628500 Added blocking bug(s) of 637809: 649004 # linux-tools-3.1/amd64 block 637809 with 649006 Bug #637809 [release.debian.org] transition: perl 5.14 Was blocked by: 646297 637602 628507 638894 628499 640347 643038 646299 646286 646295 636132 640346 636762 638367 629255 636651 642146 628505 649004 639677 628503 634531 636656 647120 628501 634141 628500 Added blocking bug(s) of 637809: 649006 thanks Stopping processing here. Please contact me if you need assistance. -- 637809: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=637809 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.132147412627193.transcr...@bugs.debian.org
Bug#648996: linux-2.6: FTBFS [m68k] in modpost: strlen [iscsi_target_mod.ko] undefined! (and others)
Thorsten Glaser wrote: ERROR: strlen [drivers/target/iscsi/iscsi_target_mod.ko] undefined! ERROR: strcpy [drivers/target/iscsi/iscsi_target_mod.ko] undefined! Hm, see also [1]. I guess there might be a useless use of strncat here. I wonder if there's a way to ask GCC not to do this kind of magic when the functions that would entail calling are not available. [1] http://thread.gmane.org/gmane.linux.kernel/680193/focus=680351 I don't see linux/string.h doing anything that could help us, but if it did, I guess something like the following might be needed, too. diff --git i/drivers/target/iscsi/iscsi_target_tpg.c w/drivers/target/iscsi/iscsi_target_tpg.c index d4cf2cd25c44..0d5b64105919 100644 --- i/drivers/target/iscsi/iscsi_target_tpg.c +++ w/drivers/target/iscsi/iscsi_target_tpg.c @@ -18,6 +18,7 @@ * GNU General Public License for more details. **/ +#include linux/string.h #include target/target_core_base.h #include target/target_core_transport.h #include target/target_core_fabric_ops.h -- 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/2016202019.gc28...@elie.hsd1.il.comcast.net
Bug#648996: linux-2.6: FTBFS [m68k] in modpost: strlen [iscsi_target_mod.ko] undefined! (and others)
Jonathan Nieder dixit: Linux 3.1 doesn’t build any more, Linux 3.0 built successfully in all its versions. Full build log attached. “amiga” is the first of the available (and needed/used) flavours, this might thus affect more or all of them. [...] MODPOST 748 modules ERROR: strlen [drivers/target/iscsi/iscsi_target_mod.ko] undefined! ERROR: strcpy [drivers/target/iscsi/iscsi_target_mod.ko] undefined! My first guess was that this might be a toolchain change, but you are still using gcc-4.4. The kernel package does. (And the Debian/m68k porters didn’t reply to my question on whether they think switching, in general, to 4.6 was desired, and doko did not respond to the inquiry whether it is possible in the first place to switch to gcc-4.6 yet keep gcj-4.4…) Anyway, I assume uninlining strlen and strcpy along the lines of [1] helps? [1] http://thread.gmane.org/gmane.linux.kernel/1085365 No idea, but I’m forwarding this to the m68k porters. I’m not really in a position to do much development there, handling the second Perl transition on my own (and the usual buildd work) is keeping my idle-time busy. bye, //mirabilos -- “Having a smoking section in a restaurant is like having a peeing section in a swimming pool.” -- Edward Burr -- 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/pine.bsm.4.64l.162017160.11...@herc.mirbsd.org
Bug#648996: linux-2.6: FTBFS [m68k] in modpost: strlen [iscsi_target_mod.ko] undefined! (and others)
On Wed, Nov 16, 2011 at 02:20:19PM -0600, Jonathan Nieder wrote: Thorsten Glaser wrote: ERROR: strlen [drivers/target/iscsi/iscsi_target_mod.ko] undefined! ERROR: strcpy [drivers/target/iscsi/iscsi_target_mod.ko] undefined! Hm, see also [1]. I guess there might be a useless use of strncat here. I wonder if there's a way to ask GCC not to do this kind of magic when the functions that would entail calling are not available. [1] http://thread.gmane.org/gmane.linux.kernel/680193/focus=680351 I don't see linux/string.h doing anything that could help us, but if it did, I guess something like the following might be needed, too. [...] linux/string.h includes asm/string.h which has the the inline functions for m68k. But there are no warnings in the log for use of these functions without declarations. So if linux/string.h is not included already (indirectly), where are they declared? I don't believe the built-in string functions are automatically declared. Ben. -- Ben Hutchings We get into the habit of living before acquiring the habit of thinking. - Albert Camus -- 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/2016203235.gc3...@decadent.org.uk
Bug#648996: linux-2.6: FTBFS [m68k] in modpost: strlen [iscsi_target_mod.ko] undefined! (and others)
Jonathan Nieder dixit:
[1] http://thread.gmane.org/gmane.linux.kernel/680193/focus=680351
I think users of both strcpy and strncat should be shot, unquestioned…
(but then, GNU is still the only major vendor without strlc{py,at}…)
bye,
//mirabilos
--
dileks ch: good, you corrected yourself. ppl tend to tweet such news
immediately, sth. like grml devs seem to be buyablech dileks: we
_are_. if you throw enough money in our direction, things will happen
mika everyone is buyable, it's just a matter of price mrud and now
comes [mira] and uses this as a signature ;0 -- they asked for it…
--
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/pine.bsm.4.64l.162023380.11...@herc.mirbsd.org
Processed: Random GFS2 partition locking problem
Processing commands for cont...@bugs.debian.org: severity 612915 normal Bug #612915 [gfs2-tools] Random GFS2 partition locking problem Severity set to 'normal' from 'critical' reassign 612915 linux-2.6 Bug #612915 [gfs2-tools] Random GFS2 partition locking problem Bug reassigned from package 'gfs2-tools' to 'linux-2.6'. Bug No longer marked as found in versions redhat-cluster/3.0.12-2. thanks Stopping processing here. Please contact me if you need assistance. -- 612915: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=612915 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.132147686010106.transcr...@bugs.debian.org
Bug#648996: linux-2.6: FTBFS [m68k] in modpost: strlen [iscsi_target_mod.ko] undefined! (and others)
Ben Hutchings dixit: But there are no warnings in the log for use of these functions without declarations. So if linux/string.h is not included already (indirectly), where are they declared? I don't believe I fear they might be correct and gcc replaces certain function calls with others, or – worse – replaces certain “expanded” code with function calls, AGAIN. I’ve seen this behaviour in my other kernel code sometimes and build with -ffreestanding (but does that guarantee this won’t happen?) to maybe fix that. Since the Linux Kernel build system is terminally broken¹, I don’t even know whether it uses -ffreestanding, all I see is “CC”… bye, //mirabilos ① unless you pass V=1 or something (can never seem to recall which of these applies to which of the broken build system set), but I can’t really do that without changing the source package, which, in turn, I don’t do if I want to produce standard, reproducible, Debian packages ready for uploading to the archive, as close to the rules for main as possible. -- Solange man keine schmutzigen Tricks macht, und ich meine *wirklich* schmutzige Tricks, wie bei einer doppelt verketteten Liste beide Pointer XORen und in nur einem Word speichern, funktioniert Boehm ganz hervorragend. -- Andreas Bogk über boehm-gc in d.a.s.r -- 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/pine.bsm.4.64l.162138010.11...@herc.mirbsd.org
Re: [PATCH 1/2] lockdep,rtmutex,bug: Show taint flags on error
Please could you ack or nak this?
Ben.
On Fri, Oct 28, 2011 at 04:36:55AM +0100, Ben Hutchings wrote:
Currently lock debugging is disabled when the kernel is tainted, with
a few exceptions. It is already recognised that this can be useful
for staging modules (TAINT_CRAP), but that also goes for out-of-tree
modules (TAINT_OOT_MODULE) so long as core kernel developers don't
have to spend time debugging them. Also, there are several reasons
for tainting that are unlikely to introduce false locking bug reports
(e.g. TAINT_FIRMWARE_WORKAROUND).
Instead of disabling lock debugging, show the taint flags in all
lockdep and rtmutex-debug error messages.
Signed-off-by: Ben Hutchings b...@decadent.org.uk
---
kernel/lockdep.c | 23 +++
kernel/panic.c | 10 --
kernel/rtmutex-debug.c |1 +
3 files changed, 16 insertions(+), 18 deletions(-)
diff --git a/kernel/lockdep.c b/kernel/lockdep.c
index e69434b..b2c4537 100644
--- a/kernel/lockdep.c
+++ b/kernel/lockdep.c
@@ -567,11 +567,12 @@ static void lockdep_print_held_locks(struct task_struct
*curr)
}
}
-static void print_kernel_version(void)
+static void print_kernel_ident(void)
{
- printk(%s %.*s\n, init_utsname()-release,
+ printk(%s %.*s %s\n, init_utsname()-release,
(int)strcspn(init_utsname()-version, ),
- init_utsname()-version);
+ init_utsname()-version,
+ print_tainted());
}
static int very_verbose(struct lock_class *class)
@@ -1148,7 +1149,7 @@ print_circular_bug_header(struct lock_list *entry,
unsigned int depth,
printk(\n);
printk(==\n);
printk([ INFO: possible circular locking dependency detected ]\n);
- print_kernel_version();
+ print_kernel_ident();
printk(---\n);
printk(%s/%d is trying to acquire lock:\n,
curr-comm, task_pid_nr(curr));
@@ -1487,7 +1488,7 @@ print_bad_irq_dependency(struct task_struct *curr,
printk(==\n);
printk([ INFO: %s-safe - %s-unsafe lock order detected ]\n,
irqclass, irqclass);
- print_kernel_version();
+ print_kernel_ident();
printk(--\n);
printk(%s/%d [HC%u[%lu]:SC%u[%lu]:HE%u:SE%u] is trying to acquire:\n,
curr-comm, task_pid_nr(curr),
@@ -1716,7 +1717,7 @@ print_deadlock_bug(struct task_struct *curr, struct
held_lock *prev,
printk(\n);
printk(=\n);
printk([ INFO: possible recursive locking detected ]\n);
- print_kernel_version();
+ print_kernel_ident();
printk(-\n);
printk(%s/%d is trying to acquire lock:\n,
curr-comm, task_pid_nr(curr));
@@ -2223,7 +2224,7 @@ print_usage_bug(struct task_struct *curr, struct
held_lock *this,
printk(\n);
printk(=\n);
printk([ INFO: inconsistent lock state ]\n);
- print_kernel_version();
+ print_kernel_ident();
printk(-\n);
printk(inconsistent {%s} - {%s} usage.\n,
@@ -2288,7 +2289,7 @@ print_irq_inversion_bug(struct task_struct *curr,
printk(\n);
printk(=\n);
printk([ INFO: possible irq lock inversion dependency detected ]\n);
- print_kernel_version();
+ print_kernel_ident();
printk(-\n);
printk(%s/%d just changed the state of lock:\n,
curr-comm, task_pid_nr(curr));
@@ -3169,6 +3170,7 @@ print_unlock_inbalance_bug(struct task_struct *curr,
struct lockdep_map *lock,
printk(\n);
printk(=\n);
printk([ BUG: bad unlock balance detected! ]\n);
+ print_kernel_ident();
printk(-\n);
printk(%s/%d is trying to release lock (,
curr-comm, task_pid_nr(curr));
@@ -3613,6 +3615,7 @@ print_lock_contention_bug(struct task_struct *curr,
struct lockdep_map *lock,
printk(\n);
printk(=\n);
printk([ BUG: bad contention detected! ]\n);
+ print_kernel_ident();
printk(-\n);
printk(%s/%d is trying to contend lock (,
curr-comm, task_pid_nr(curr));
@@ -3987,6 +3990,7 @@ print_freed_lock_bug(struct task_struct *curr, const
void *mem_from,
printk(\n);
printk(=\n);
printk([ BUG: held lock freed! ]\n);
+ print_kernel_ident();
printk(-\n);
printk(%s/%d is freeing
Bug#648996: linux-2.6: FTBFS [m68k] in modpost: strlen [iscsi_target_mod.ko] undefined! (and others)
On Wed, Nov 16, 2011 at 09:42:41PM +, Thorsten Glaser wrote: Ben Hutchings dixit: But there are no warnings in the log for use of these functions without declarations. So if linux/string.h is not included already (indirectly), where are they declared? I don't believe I fear they might be correct and gcc replaces certain function calls with others, or – worse – replaces certain “expanded” code with function calls, AGAIN. I’ve seen this behaviour in my other kernel code sometimes and build with -ffreestanding (but does that guarantee this won’t happen?) to maybe fix that. Since the Linux Kernel build system is terminally broken¹, I don’t even know whether it uses -ffreestanding, all I see is “CC”… bye, //mirabilos ① unless you pass V=1 or something (can never seem to recall which of these applies to which of the broken build system set), but I can’t really do that without changing the source package, which, in turn, I don’t do if I want to produce standard, reproducible, Debian packages ready for uploading to the archive, as close to the rules for main as possible. Try KBUILD_VERBOSE=1 dpkg-buildpackage ... And hiding command lines by default is not broken; it makes it a hell of a lot easier to actually see warnings. Ben. -- Ben Hutchings We get into the habit of living before acquiring the habit of thinking. - Albert Camus -- 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/2016215701.ge3...@decadent.org.uk
Processed: gfs2-tools: File corruption when copying large files to gfs filesystem
Processing commands for cont...@bugs.debian.org: severity 612024 normal Bug #612024 [gfs2-tools] gfs2-tools: File corruption when copying large files to gfs filesystem Severity set to 'normal' from 'serious' reassign 612024 linux-2.6 Bug #612024 [gfs2-tools] gfs2-tools: File corruption when copying large files to gfs filesystem Bug reassigned from package 'gfs2-tools' to 'linux-2.6'. Bug No longer marked as found in versions redhat-cluster/3.0.12-2. thanks Stopping processing here. Please contact me if you need assistance. -- 612024: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=612024 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.13214807552293.transcr...@bugs.debian.org
Processed: redhat-cluster-modules-2.6.26-1-686-bigmem: GFS cannot create files over 4KB
Processing commands for cont...@bugs.debian.org: reassign 508541 linux-2.6 Bug #508541 [redhat-cluster-source] redhat-cluster-modules-2.6.26-1-686-bigmem: GFS cannot create files over 4KB Bug reassigned from package 'redhat-cluster-source' to 'linux-2.6'. tags 508541 lenny Bug #508541 [linux-2.6] redhat-cluster-modules-2.6.26-1-686-bigmem: GFS cannot create files over 4KB Added tag(s) lenny. thanks Stopping processing here. Please contact me if you need assistance. -- 508541: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=508541 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.13214807732345.transcr...@bugs.debian.org
Bug#508541: redhat-cluster-modules-2.6.26-1-686-bigmem: GFS cannot create files over 4KB
reassign 508541 linux-2.6 tags 508541 lenny thanks Hi, this bug is fixed in squeeze. Best regards Frederik Schüler -- ENOSIG -- 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/20162259.18176...@debian.org
Bug#612024: gfs2-tools: File corruption when copying large files to gfs filesystem
severity 612024 normal reassign 612024 linux-2.6 thanks Hi, can you try to reproduce this on a newer kernel than 2.6.32? I suggest using the latest linux-2.6 package from backports.debian.org. Best regards Frederik Schüler -- ENOSIG -- 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/20162259.03697...@debian.org
Bug#508541: redhat-cluster-modules-2.6.26-1-686-bigmem: GFS cannot create files over 4KB
Hi, Frederik Schüler wrote: this bug is fixed in squeeze. Which version did you test? Thank you, Jonathan -- 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/2016221337.gb14...@elie.hsd1.il.comcast.net
Re: [PATCH] bonding: Don't allow mode change via sysfs with slaves present
On Wed, Nov 16, 2011 at 01:02:21PM +0100, Nicolas de Pesloüan wrote:
Le 15/11/2011 21:47, Andy Gospodarek a écrit :
Nicolas,
I took a look at the ifenslave package for debian more closely and it
actually looks like devices are enslaved last, after mode is set. Can
you please take a look at this package and confirm what I'm seeing in
the 'pre-up' script.
It appears to me that setup_master sets the mode and enslave_slaves is
called after and enslaves the devices:
# Option slaves deprecated, replaced by bond-slaves, but still supported
# for backward compatibility.
IF_BOND_SLAVES=${IF_BOND_SLAVES:-$IF_SLAVES}
if [ $IF_BOND_MASTER ] ; then
BOND_MASTER=$IF_BOND_MASTER
BOND_SLAVES=$IFACE
else
if [ $IF_BOND_SLAVES ] ; then
BOND_MASTER=$IFACE
BOND_SLAVES=$IF_BOND_SLAVES
fi
fi
# Exit if nothing to do...
[ -z $BOND_MASTER$BOND_SLAVES ] exit
add_master
early_setup_master
setup_master
enslave_slaves
exit 0
Andy,
I'm really surprise by this extract. In the most up to date version of
the ifenslave-2.6 package (1.1.0-19), the order is:
add_master
early_setup_master
enslave_slaves
setup_master
early_setup_master was created to be able to do things that absolutely
need to be done before enslavement. (See the comment just before this
function). The idea was to do every possible setup in setup_master, after
enslavement, except those that need to be done in early_setup_master. So
having enslave_slaves after setup_master instead of before is definitely
a mistake. Some of the operations in setup_master must be done after
enslavement, in particular selecting the primary slave.
In version 1.1.0-18 (change log below), I checked all the possible order
constraints of the sysfs interface and totally reworked most of the setup
code, putting everything in the right order to achieve consistent
results.
ifenslave-2.6 (1.1.0-18) experimental; urgency=low
* Apply patch from Nicolas de Pesloüan:
- Major change: Check and fix the order in which the configuration
is
written into /sys files, to ensure reliable results, according to
the
tests done in the kernel (in drivers/net/bonding/bond_sysfs.c).
- Ensure that master is properly brought down when changing a
parameter
that require it to be down.
- Ensure the master is brought up at the end of the setup, in the
case
where ifup won't bring it up because it is currently configuring
a slave.
- Add support for some previously unsupported /sys files: ad_select,
num_grat_arp, num_unsol_na, primary_reselect and queue_id.
- Enhance the documentation (README.Debian), to describe all the
currently
supported bond-* options.
- Many other changes in the documentation.
- Reverse the order of the arguments to most sysfs_* internal
functions, for
better readability.
It was a hard work, because there really exist many such constraints. I
fail to find enough time to insert the result of this work into
Documentation/networking/bonding.txt, but still plan to do so, even if
the result is documented in the script you looked at.
Of course, it is possible to change the scripts in ifenslave-2.6 package
to arrange for one more constraint. For as far as I understand, this
would cause the Debian kernel that introduce the change we discuss about
and all the future Debian kernels to be flagged with 'Breaks:
ifenslave-2.6 ( 1.1.0-20)'. I'm not really comfortable with this and
the Debian kernel team need to be involved. I copied them.
All that being said, I really advocate for less constraints on the sysfs
setup. This is not strictly related to sysfs setup. If we eventually add
a NETLINK interface for all the things we can setup using sysfs, we will
face the exact same problem.
I was looking at ifenslave 1.1.0-20. If you look at Debian bug #641250
you will see a very similar report to what prompted Veaceslav to come up
with this patch and post it here.
ifenslave-2.6 (1.1.0-20) unstable; urgency=low
* Use dashes consistently for bonding options in README.Debian.
Closes: #639244
* Enslave slaves only after fully setting up the master. Closes: #641250
* Add build-arch and build-indep targets to debian/rules.
-- Guus Sliepen g...@debian.org Mon, 14 Nov 2011 11:36:21 +0100
ifenslave-2.6 (1.1.0-19) unstable; urgency=low
* Don't bother trying to move configuration files anymore. This is not an
issue anymore in for the next stable release, and it was broken anyway.
Closes: #626959
* Bump Standards-Version.
-- Guus Sliepen g...@debian.org Wed, 25 May 2011 18:42:32 +0200
ifenslave-2.6 (1.1.0-18) experimental; urgency=low
* Apply patch from Nicolas de Pesloüan:
- Major change: Check and fix the order in which the configuration is
Bug#612024: gfs2-tools: File corruption when copying large files to gfs filesystem
Hi, Frederik Schüler wrote: can you try to reproduce this on a newer kernel than 2.6.32? It helps to cc the submitter. :) Olaf: can you reproduce this with a 3.x kernel from sid or experimental? If you can, it should be easier to get help upstream, and if you can't, we will have somewhere to start in looking for an existing fix. The only packages from outside squeeze aside from linux-image-* itself that should be needed to test are linux-base and initramfs-tools. Thanks, Jonathan -- 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/2016221701.gc14...@elie.hsd1.il.comcast.net
Bug#648996: linux-2.6: FTBFS [m68k] in modpost: strlen [iscsi_target_mod.ko] undefined! (and others)
Ben Hutchings wrote: Try KBUILD_VERBOSE=1 dpkg-buildpackage ... And hiding command lines by default is not broken; it makes it a hell of a lot easier to actually see warnings. Though there is a question of what the default behavior on autobuilders should be. I guess it would be nice if packages supported some interface like DEB_BUILD_OPTIONS=verbose to help toolchain hackers. If you have ideas for how to (or not to) move forward on that kind of thing, there is a rough proposal at [1]. (BTW, sorry for the false starts before. Now I suspect a possible short-term fix is to eliminate the strncat call but have no particular reason to believe it will work. There's a disincentive to fix the underlying problem because it flags these strncat() calls which are a little insane.) [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=5;bug=628515 -- 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/2016221745.gd14...@elie.hsd1.il.comcast.net
Bug#648939: USB mouse stops work on battery power
Erik de Castro Lopo wrote: Mouse works when the laptop is connected to power but stops about 20 seconds after power is disconnected. Re=connecting power and the mouse starts working again. This problem did not exist in 2.6.32 but did in 3.0. Weird. Sounds like ACPI breakage. Can you bisect? (A few iterations to narrow down the regression range would already be pretty helpful.) Thanks, Jonathan -- 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/2016222324.gf14...@elie.hsd1.il.comcast.net
Bug#647095: CPU hyperthreading turned on after soft power-cycle
Hi all, Result of bisecting: v2.6.38-rc1 exhibits the problem. v2.6.37 and many of the topic branches merged in the 2.6.38 merge window work ok. Some other topic branches do not boot at all. Jiri: if you have gitk installed, then git bisect visualize can help get a sense of what's in the middle of the regression range. gitk --bisect --first-parent v2.6.37..v2.6.38-rc1 might be a good way to find mainline commits to test before finding a topic branch to delve into. I have been able to narrow the interval manually a little bit from the top (the bad side) and I will go on from the bottom now. However, there seems to be a large area where kernels are unbootable for me - they mostly stop when init is called and I do not know why. Finally! After another 50+ compilations a have it! It took some time as first I had to find a reason why some revisions did not boot (almost 2/3 were unbootable and the first bad commit was among them). Having this solved I have been able to bisect without skipping. The result is surprising (at least for me) - believe it or not, the first bad commit is 6610e089 RTC: Rework RTC code to use timerqueue for events from John Stultz (I am sending him a copy of this message). I would never expect this would be a problem, but my understanding of this commit is very limited, so I am certainly missing the point. However, I have tried to compile 2.6.38 (which was bad) with Real Time Clock configuration option turned off and it behaves normally then (= is good). Can you please comment this result? What does it mean? Any idea what is wrong there? Best regards, Jiri Polach -- 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/4ec43df7.4010...@atlas.cz
Bug#648939: USB mouse stops work on battery power
Erik de Castro Lopo wrote: I've looked in the repo and the kernel versions seem to jump from 2.6.32 to 3.0.0. Are there debian packages for kernels between 2.6.32 and 3.0.0 or do i have to compile them myself? Intermediate versions are at http://snapshot.debian.org/. Sorry, I should have mentioned so before. -- 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/2016224816.gb17...@elie.hsd1.il.comcast.net
Bug#648939: USB mouse stops work on battery power
Jonathan Nieder wrote: Erik de Castro Lopo wrote: Mouse works when the laptop is connected to power but stops about 20 seconds after power is disconnected. Re=connecting power and the mouse starts working again. This problem did not exist in 2.6.32 but did in 3.0. Weird. Sounds like ACPI breakage. Can you bisect? (A few iterations to narrow down the regression range would already be pretty helpful.) I've looked in the repo and the kernel versions seem to jump from 2.6.32 to 3.0.0. Are there debian packages for kernels between 2.6.32 and 3.0.0 or do i have to compile them myself? Erik -- -- Erik de Castro Lopo http://www.mega-nerd.com/ -- 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/2017094100.71bd2d4ec4e56850da3ac...@mega-nerd.com
Re: [PATCH 1/2] lockdep,rtmutex,bug: Show taint flags on error
On Wed, Nov 16, 2011 at 09:52:36PM +, Ben Hutchings wrote: Please could you ack or nak this? Ben. sorry, thought I already had. Reviewed-by: Dave Jones da...@redhat.com -- 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/2016222402.gb29...@redhat.com
Bug#649033: linux-image-3.1.0-1-amd64: boot sometimes stuck with waiting for /dev to be fully populated.
Package: linux-2.6 Version: 3.1.1-1 Severity: important The boot sometimes freezes with the message: waiting for /dev to be fully populated. There was a bug report against udev (bug #606192), which is closed, suggesting a kernel bug if the timeout doesn't occur, which is the case here (with linux-image-3.1.0-1-amd64 3.1.1-1). http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=606192#98 If the boot does not continue then it looks like that udev loaded a module which crashed your system (so this would be a kernel bug). I'm not the only one who has this problem: http://identi.ca/conversation/84449449 Note that even though this problem doesn't occur very often, it can be very problematic if one wants to reboot the machine remotely, as there is no way to redo a reboot. -- Package-specific info: ** Version: Linux version 3.1.0-1-amd64 (Debian 3.1.1-1) (b...@decadent.org.uk) (gcc version 4.6.2 (Debian 4.6.2-4) ) #1 SMP Mon Nov 14 08:02:25 UTC 2011 ** Command line: root=/dev/mapper/xvii-root ro quiet ** Not tainted ** Kernel log: [ 11.653828] [drm] nouveau :01:00.0: 0: memory 100MHz core 169MHz shader 338MHz voltage 900mV fanspeed 100% timing 0 [ 11.653832] [drm] nouveau :01:00.0: 1: memory 250MHz core 275MHz shader 550MHz voltage 900mV fanspeed 100% timing 1 [ 11.653836] [drm] nouveau :01:00.0: 2: memory 400MHz core 500MHz shader 1000MHz voltage 1090mV fanspeed 100% timing 2 [ 11.653840] [drm] nouveau :01:00.0: 3: memory 400MHz core 580MHz shader 1450MHz voltage 1170mV fanspeed 100% timing 3 [ 11.653869] [drm] nouveau :01:00.0: Register 0x4030 not found in PLL limits table [ 11.653982] [drm] nouveau :01:00.0: c: memory 249MHz core 275MHz shader 550MHz voltage 900mV [ 11.656429] [TTM] Zone kernel: Available graphics memory: 2024866 kiB. [ 11.656432] [TTM] Initializing pool allocator. [ 11.656443] [drm] nouveau :01:00.0: Detected 256MiB VRAM [ 11.656449] mtrr: type mismatch for e000,1000 old: write-back new: write-combining [ 11.656474] [drm] nouveau :01:00.0: 512 MiB GART (aperture) [ 11.670404] [drm] nouveau :01:00.0: ACPI backlight interface available, not registering our own [ 11.671776] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). [ 11.671778] [drm] No driver support for vblank timestamp query. [ 11.699932] ieee80211 phy0: Selected rate control algorithm 'iwl-agn-rs' [ 11.707286] input: DualPoint Stick as /devices/platform/i8042/serio1/input/input9 [ 11.724092] input: AlpsPS/2 ALPS DualPoint TouchPad as /devices/platform/i8042/serio1/input/input10 [ 11.877392] [drm] nouveau :01:00.0: allocated 1440x900 fb: 0x31, bo 88011a388400 [ 11.877466] fbcon: nouveaufb (fb0) is primary device [ 11.952017] dell_wmi: Received unknown WMI event (0x11) [ 13.218625] Console: switching to colour frame buffer device 180x56 [ 13.221576] fb0: nouveaufb frame buffer device [ 13.221577] drm: registered panic notifier [ 13.221587] [drm] Initialized nouveau 0.0.16 20090420 for :01:00.0 on minor 0 [ 13.244484] dell_wmi: Received unknown WMI event (0x11) [ 13.383201] snd_hda_intel :00:1b.0: PCI INT A - GSI 21 (level, low) - IRQ 21 [ 13.383266] snd_hda_intel :00:1b.0: irq 47 for MSI/MSI-X [ 13.383297] snd_hda_intel :00:1b.0: setting latency timer to 64 [ 13.493888] input: HDA Digital PCBeep as /devices/pci:00/:00:1b.0/input/input11 [ 13.509229] input: HDA Intel Mic at Sep Left Jack as /devices/pci:00/:00:1b.0/sound/card0/input12 [ 13.509324] input: HDA Intel Mic at Ext Right Jack as /devices/pci:00/:00:1b.0/sound/card0/input13 [ 13.509405] input: HDA Intel Line Out at Sep Left Jack as /devices/pci:00/:00:1b.0/sound/card0/input14 [ 13.509485] input: HDA Intel HP Out at Ext Right Jack as /devices/pci:00/:00:1b.0/sound/card0/input15 [ 13.860800] WARNING! power/level is deprecated; use power/control instead [ 13.998220] Linux media interface: v0.10 [ 14.002163] Linux video capture interface: v2.00 [ 14.014492] uvcvideo: Found UVC 1.00 device Laptop_Integrated_Webcam_0.3M (0c45:63f8) [ 14.028812] input: Laptop_Integrated_Webcam_0.3M as /devices/pci:00/:00:1a.7/usb1/1-6/1-6:1.0/input/input16 [ 14.028902] usbcore: registered new interface driver uvcvideo [ 14.028904] USB Video Class driver (1.1.1) [ 14.121270] usb 3-1.3: new full speed USB device number 5 using uhci_hcd [ 14.251270] usb 3-1.3: New USB device found, idVendor=413c, idProduct=8156 [ 14.251274] usb 3-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 14.251278] usb 3-1.3: Product: Dell Wireless 370 Bluetooth Mini-card [ 14.251281] usb 3-1.3: Manufacturer: Dell Computer Corp [ 14.352418] Bluetooth: Core ver 2.16 [ 14.352439] NET: Registered protocol family 31 [ 14.352441] Bluetooth: HCI device and connection manager initialized [ 14.352443] Bluetooth: HCI socket layer initialized [ 14.352445]
Processed: found 622231 in 3.1.1-1
Processing commands for cont...@bugs.debian.org: found 622231 3.1.1-1 Bug #622231 [linux-2.6] xserver-xorg-input-synaptics: synaptics driver not always used There is no source info for the package 'linux-2.6' at version '3.1.1-1' with architecture '' Unable to make a source version for version '3.1.1-1' Bug Marked as found in versions 3.1.1-1. thanks Stopping processing here. Please contact me if you need assistance. -- 622231: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=622231 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.132148982518796.transcr...@bugs.debian.org
Bug#649033: linux-image-3.1.0-1-amd64: boot sometimes stuck with waiting for /dev to be fully populated.
On Thu, Nov 17, 2011 at 01:29:08AM +0100, Vincent Lefevre wrote: Package: linux-2.6 Version: 3.1.1-1 Severity: important The boot sometimes freezes with the message: waiting for /dev to be fully populated. There was a bug report against udev (bug #606192), which is closed, suggesting a kernel bug if the timeout doesn't occur, which is the case here (with linux-image-3.1.0-1-amd64 3.1.1-1). [...] Please start the kernel without 'quiet' (the GRUB 'rescue mode' entries will do this) so the kernel logs more to the console, and send us the resulting messages (a photograph with readable text is fine). Ben. -- Ben Hutchings We get into the habit of living before acquiring the habit of thinking. - Albert Camus -- 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/2017005218.gg3...@decadent.org.uk
Re: [PATCH] bonding: Don't allow mode change via sysfs with slaves present
On Wed, 16 Nov 2011 17:02:00 -0500
Andy Gospodarek a...@greyhouse.net wrote:
On Wed, Nov 16, 2011 at 01:02:21PM +0100, Nicolas de Pesloüan wrote:
Le 15/11/2011 21:47, Andy Gospodarek a écrit :
Nicolas,
I took a look at the ifenslave package for debian more closely and
it actually looks like devices are enslaved last, after mode is
set. Can you please take a look at this package and confirm what
I'm seeing in the 'pre-up' script.
It appears to me that setup_master sets the mode and
enslave_slaves is called after and enslaves the devices:
# Option slaves deprecated, replaced by bond-slaves, but still
supported # for backward compatibility.
IF_BOND_SLAVES=${IF_BOND_SLAVES:-$IF_SLAVES}
if [ $IF_BOND_MASTER ] ; then
BOND_MASTER=$IF_BOND_MASTER
BOND_SLAVES=$IFACE
else
if [ $IF_BOND_SLAVES ] ; then
BOND_MASTER=$IFACE
BOND_SLAVES=$IF_BOND_SLAVES
fi
fi
# Exit if nothing to do...
[ -z $BOND_MASTER$BOND_SLAVES ] exit
add_master
early_setup_master
setup_master
enslave_slaves
exit 0
Andy,
I'm really surprise by this extract. In the most up to date version
of the ifenslave-2.6 package (1.1.0-19), the order is:
add_master
early_setup_master
enslave_slaves
setup_master
early_setup_master was created to be able to do things that
absolutely need to be done before enslavement. (See the comment
just before this function). The idea was to do every possible setup
in setup_master, after enslavement, except those that need to be
done in early_setup_master. So having enslave_slaves after
setup_master instead of before is definitely a mistake. Some of the
operations in setup_master must be done after enslavement, in
particular selecting the primary slave.
In version 1.1.0-18 (change log below), I checked all the possible
order constraints of the sysfs interface and totally reworked most
of the setup code, putting everything in the right order to achieve
consistent results.
ifenslave-2.6 (1.1.0-18) experimental; urgency=low
* Apply patch from Nicolas de Pesloüan:
- Major change: Check and fix the order in which the
configuration is written into /sys files, to ensure reliable
results, according to the tests done in the kernel (in
drivers/net/bonding/bond_sysfs.c).
- Ensure that master is properly brought down when
changing a parameter that require it to be down.
- Ensure the master is brought up at the end of the
setup, in the case where ifup won't bring it up because it is
currently configuring a slave.
- Add support for some previously unsupported /sys
files: ad_select, num_grat_arp, num_unsol_na, primary_reselect and
queue_id.
- Enhance the documentation (README.Debian), to
describe all the currently supported bond-* options.
- Many other changes in the documentation.
- Reverse the order of the arguments to most sysfs_*
internal functions, for better readability.
It was a hard work, because there really exist many such
constraints. I fail to find enough time to insert the result of
this work into Documentation/networking/bonding.txt, but still plan
to do so, even if the result is documented in the script you looked
at.
Of course, it is possible to change the scripts in ifenslave-2.6
package to arrange for one more constraint. For as far as I
understand, this would cause the Debian kernel that introduce the
change we discuss about and all the future Debian kernels to be
flagged with 'Breaks: ifenslave-2.6 ( 1.1.0-20)'. I'm not really
comfortable with this and the Debian kernel team need to be
involved. I copied them.
All that being said, I really advocate for less constraints on the
sysfs setup. This is not strictly related to sysfs setup. If we
eventually add a NETLINK interface for all the things we can setup
using sysfs, we will face the exact same problem.
I was looking at ifenslave 1.1.0-20. If you look at Debian bug
#641250 you will see a very similar report to what prompted Veaceslav
to come up with this patch and post it here.
ifenslave-2.6 (1.1.0-20) unstable; urgency=low
* Use dashes consistently for bonding options in README.Debian.
Closes: #639244
* Enslave slaves only after fully setting up the master. Closes:
#641250
[...]
I perfectly understand, as Veaceslav noted in another email that
there are a lot of mode-specific initialization stuff that's
present only in bond_enslave(), but I think this is what needs to
be fixed... Those initialization stuff should be moved out of
bond_enslave() and called at appropriate sime, from bond_enslave()
and from other locations, in particular when changing mode.
I think Veaceslav is working on this, but there is significant
re-organization that is needed to make it work properly and make sure
it is tested. I
Processed: tagging 649005
Processing commands for cont...@bugs.debian.org: tags 649005 + pending Bug #649005 [linux-tools] linux-tools: FTBFS when binNMUed Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 649005: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=649005 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.13214998721371.transcr...@bugs.debian.org
Processed: tagging 649006
Processing commands for cont...@bugs.debian.org: tags 649006 + pending Bug #649006 [linux-tools-3.1] linux-tools-3.1: needs rebuild against perl 5.14 Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 649006: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=649006 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.13215009878428.transcr...@bugs.debian.org
Bug#649005: marked as done (linux-tools: FTBFS when binNMUed)
Your message dated Thu, 17 Nov 2011 03:50:33 + with message-id e1rqszh-00046y...@franck.debian.org and subject line Bug#649005: fixed in linux-tools 3.1.1-2 has caused the Debian Bug report #649005, regarding linux-tools: FTBFS when binNMUed to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 649005: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=649005 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-tools Version: 3.1.1-1 Severity: normal See https://buildd.debian.org/status/fetch.php?pkg=linux-toolsarch=amd64ver=3.1.1-1%2Bb1stamp=1321332698 bwh jcristau: For some reason linux-tools is missing the special case for binNMUs Cheers, Julien ---End Message--- ---BeginMessage--- Source: linux-tools Source-Version: 3.1.1-2 We believe that the bug you reported is fixed in the latest version of linux-tools, which is due to be installed in the Debian FTP archive: linux-kbuild-3.1_3.1.1-2_i386.deb to main/l/linux-tools/linux-kbuild-3.1_3.1.1-2_i386.deb linux-tools-3.1_3.1.1-2_i386.deb to main/l/linux-tools/linux-tools-3.1_3.1.1-2_i386.deb linux-tools_3.1.1-2.debian.tar.gz to main/l/linux-tools/linux-tools_3.1.1-2.debian.tar.gz linux-tools_3.1.1-2.dsc to main/l/linux-tools/linux-tools_3.1.1-2.dsc A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 649...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ben Hutchings b...@decadent.org.uk (supplier of updated linux-tools package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 17 Nov 2011 03:18:03 + Source: linux-tools Binary: linux-kbuild-3.1 linux-tools-3.1 Architecture: i386 source Version: 3.1.1-2 Distribution: unstable Urgency: low Maintainer: Debian Kernel Team debian-kernel@lists.debian.org Changed-By: Ben Hutchings b...@decadent.org.uk Closes: 649005 649006 Description: linux-kbuild-3.1 - Kbuild infrastructure for Linux 3.1 linux-tools-3.1 - Performance analysis tools for Linux 3.1 Changes: linux-tools (3.1.1-2) unstable; urgency=low . * Change the check for stale debian/control to tolerate binNMUs (Closes: #649005) * Rebuild with perl 5.14 (Closes: #649006) 6de904745aa924067d5466685ca7b2f8399b0b0551da11287f492a76f7f79f81 1152 linux-tools_3.1.1-2.dsc 5fdbc6cb5e67b58ca7c995f32f73b4c13c3f2e0e23deb9db23677a70d9b4b9c6 17421 linux-tools_3.1.1-2.debian.tar.gz Checksums-Sha1: b7390769490e9ee080b113bbe3a514d118401da2 2030 linux-tools_3.1.1-2.dsc bc91d4d2e48e023c19265169080849c3cb69882c 17421 linux-tools_3.1.1-2.debian.tar.gz 152250acf7952cb0ee6c58830ef3fda684db6ecf 233204 linux-kbuild-3.1_3.1.1-2_i386.deb 5176d7fd9f08aa601d0104677b4545c996d75e1c 380660 linux-tools-3.1_3.1.1-2_i386.deb Checksums-Sha256: 9aa089b6c4ffac70ae6f2e6947ae0d1aface33b8c06a83f55c0593dce8fe8fb9 2030 linux-tools_3.1.1-2.dsc 5fdbc6cb5e67b58ca7c995f32f73b4c13c3f2e0e23deb9db23677a70d9b4b9c6 17421 linux-tools_3.1.1-2.debian.tar.gz 03a74300db0fba111eaca5f6e842858b49d14d3468122dbd23e06261087ea8b5 233204 linux-kbuild-3.1_3.1.1-2_i386.deb 400a1355750d0d29dde01dc8c8d0802c20fd5c611b7fb05a7ff7f3e4ae35243b 380660 linux-tools-3.1_3.1.1-2_i386.deb Files: 77ec8b3313f5ccdefcb4e8f895d49fd4 2030 devel optional linux-tools_3.1.1-2.dsc fca5bd844db16d7fa3051446f7e5bb0a 17421 devel optional linux-tools_3.1.1-2.debian.tar.gz 79f32826ab049fe8389624c9b52d566f 233204 devel optional linux-kbuild-3.1_3.1.1-2_i386.deb 76075a79152e6f77c80dfa700db69413 380660 devel optional linux-tools-3.1_3.1.1-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQIVAwUBTsSBTue/yOyVhhEJAQoa4g/6Ak2kWby5bkDzWtipYLGtpCyjPGBqONJi TfDvQmTwjgFcQI+l4jNQiDD35+Krobmw3FJS5egTeO2ypdPrUMajYQ9QcDJIM513 3IeFjR//0h3DJTqUFkRiJwGuraiNpHBd9pKSNcMEhmmSMRWQ16VnUPBkm1VH74H9 ScQ3LbUoWwbPEiC7AE5pnlbXVhq1sVmfg9hc1VErkDpFof49sR3kX3cmoMtS8YH2 dbVvpDsoq6Eiq+aizOs9Skb0EdC4r8oLOg34cFpiewUvKN7NVZpEGnwuH+ietjB/ MHPNpp4UpfAS3KUJ9ZRum1TVWYYI+/E0E36XV/evKlt0Q6Y7c8ZgR1e/q5y3IOYq gx8MKp0Pa3P4/NozQ7uLjWga9Lp1IZlOveTRVXbejFIE17jiCD2I0jhO2ucr2td+ 43TdSH0/KW9dLSooukC9I72Gheq6yCHSlc7ayZk9Rc5EMu8yNdpc1XESaRVW7CAd V3hSumV85nezx/41e2bCgyWVAcLPFrVZBq7dQijn9j3G+haLVkzvGUtfwhDLfMjl
Bug#649006: marked as done (linux-tools-3.1: needs rebuild against perl 5.14)
Your message dated Thu, 17 Nov 2011 03:50:33 + with message-id e1rqszh-000474...@franck.debian.org and subject line Bug#649006: fixed in linux-tools 3.1.1-2 has caused the Debian Bug report #649006, regarding linux-tools-3.1: needs rebuild against perl 5.14 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 649006: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=649006 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-tools-3.1 Version: 3.1.1-1 Severity: serious linux-tools-3.1/amd64 depends on libperl5.12 which makes it uninstallable in sid right now. It needs a new source upload as binNMUs don't work (see other bug). Cheers, Julien ---End Message--- ---BeginMessage--- Source: linux-tools Source-Version: 3.1.1-2 We believe that the bug you reported is fixed in the latest version of linux-tools, which is due to be installed in the Debian FTP archive: linux-kbuild-3.1_3.1.1-2_i386.deb to main/l/linux-tools/linux-kbuild-3.1_3.1.1-2_i386.deb linux-tools-3.1_3.1.1-2_i386.deb to main/l/linux-tools/linux-tools-3.1_3.1.1-2_i386.deb linux-tools_3.1.1-2.debian.tar.gz to main/l/linux-tools/linux-tools_3.1.1-2.debian.tar.gz linux-tools_3.1.1-2.dsc to main/l/linux-tools/linux-tools_3.1.1-2.dsc A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 649...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ben Hutchings b...@decadent.org.uk (supplier of updated linux-tools package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 17 Nov 2011 03:18:03 + Source: linux-tools Binary: linux-kbuild-3.1 linux-tools-3.1 Architecture: i386 source Version: 3.1.1-2 Distribution: unstable Urgency: low Maintainer: Debian Kernel Team debian-kernel@lists.debian.org Changed-By: Ben Hutchings b...@decadent.org.uk Closes: 649005 649006 Description: linux-kbuild-3.1 - Kbuild infrastructure for Linux 3.1 linux-tools-3.1 - Performance analysis tools for Linux 3.1 Changes: linux-tools (3.1.1-2) unstable; urgency=low . * Change the check for stale debian/control to tolerate binNMUs (Closes: #649005) * Rebuild with perl 5.14 (Closes: #649006) 6de904745aa924067d5466685ca7b2f8399b0b0551da11287f492a76f7f79f81 1152 linux-tools_3.1.1-2.dsc 5fdbc6cb5e67b58ca7c995f32f73b4c13c3f2e0e23deb9db23677a70d9b4b9c6 17421 linux-tools_3.1.1-2.debian.tar.gz Checksums-Sha1: b7390769490e9ee080b113bbe3a514d118401da2 2030 linux-tools_3.1.1-2.dsc bc91d4d2e48e023c19265169080849c3cb69882c 17421 linux-tools_3.1.1-2.debian.tar.gz 152250acf7952cb0ee6c58830ef3fda684db6ecf 233204 linux-kbuild-3.1_3.1.1-2_i386.deb 5176d7fd9f08aa601d0104677b4545c996d75e1c 380660 linux-tools-3.1_3.1.1-2_i386.deb Checksums-Sha256: 9aa089b6c4ffac70ae6f2e6947ae0d1aface33b8c06a83f55c0593dce8fe8fb9 2030 linux-tools_3.1.1-2.dsc 5fdbc6cb5e67b58ca7c995f32f73b4c13c3f2e0e23deb9db23677a70d9b4b9c6 17421 linux-tools_3.1.1-2.debian.tar.gz 03a74300db0fba111eaca5f6e842858b49d14d3468122dbd23e06261087ea8b5 233204 linux-kbuild-3.1_3.1.1-2_i386.deb 400a1355750d0d29dde01dc8c8d0802c20fd5c611b7fb05a7ff7f3e4ae35243b 380660 linux-tools-3.1_3.1.1-2_i386.deb Files: 77ec8b3313f5ccdefcb4e8f895d49fd4 2030 devel optional linux-tools_3.1.1-2.dsc fca5bd844db16d7fa3051446f7e5bb0a 17421 devel optional linux-tools_3.1.1-2.debian.tar.gz 79f32826ab049fe8389624c9b52d566f 233204 devel optional linux-kbuild-3.1_3.1.1-2_i386.deb 76075a79152e6f77c80dfa700db69413 380660 devel optional linux-tools-3.1_3.1.1-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQIVAwUBTsSBTue/yOyVhhEJAQoa4g/6Ak2kWby5bkDzWtipYLGtpCyjPGBqONJi TfDvQmTwjgFcQI+l4jNQiDD35+Krobmw3FJS5egTeO2ypdPrUMajYQ9QcDJIM513 3IeFjR//0h3DJTqUFkRiJwGuraiNpHBd9pKSNcMEhmmSMRWQ16VnUPBkm1VH74H9 ScQ3LbUoWwbPEiC7AE5pnlbXVhq1sVmfg9hc1VErkDpFof49sR3kX3cmoMtS8YH2 dbVvpDsoq6Eiq+aizOs9Skb0EdC4r8oLOg34cFpiewUvKN7NVZpEGnwuH+ietjB/ MHPNpp4UpfAS3KUJ9ZRum1TVWYYI+/E0E36XV/evKlt0Q6Y7c8ZgR1e/q5y3IOYq gx8MKp0Pa3P4/NozQ7uLjWga9Lp1IZlOveTRVXbejFIE17jiCD2I0jhO2ucr2td+ 43TdSH0/KW9dLSooukC9I72Gheq6yCHSlc7ayZk9Rc5EMu8yNdpc1XESaRVW7CAd V3hSumV85nezx/41e2bCgyWVAcLPFrVZBq7dQijn9j3G+haLVkzvGUtfwhDLfMjl ZdsPZDmOC76rr6y2iDslTNxOOnbn8fFSwY81OUUDZ8ozSGEufzqxSqaLvdm/d47I
Processing of linux-tools_3.1.1-2_multi.changes
linux-tools_3.1.1-2_multi.changes uploaded successfully to localhost along with the files: linux-tools_3.1.1-2.dsc linux-tools_3.1.1-2.debian.tar.gz linux-kbuild-3.1_3.1.1-2_i386.deb linux-tools-3.1_3.1.1-2_i386.deb Greetings, Your Debian queue daemon (running on host franck.debian.org) -- 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/e1rqsoh-0008jc...@franck.debian.org
linux-tools_3.1.1-2_multi.changes ACCEPTED into unstable
Accepted: linux-kbuild-3.1_3.1.1-2_i386.deb to main/l/linux-tools/linux-kbuild-3.1_3.1.1-2_i386.deb linux-tools-3.1_3.1.1-2_i386.deb to main/l/linux-tools/linux-tools-3.1_3.1.1-2_i386.deb linux-tools_3.1.1-2.debian.tar.gz to main/l/linux-tools/linux-tools_3.1.1-2.debian.tar.gz linux-tools_3.1.1-2.dsc to main/l/linux-tools/linux-tools_3.1.1-2.dsc Override entries for your package: linux-kbuild-3.1_3.1.1-2_i386.deb - optional devel linux-tools-3.1_3.1.1-2_i386.deb - optional devel linux-tools_3.1.1-2.dsc - source devel Announcing to debian-devel-chan...@lists.debian.org Closing bugs: 649005 649006 Thank you for your contribution to Debian. -- 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/e1rqszh-00046s...@franck.debian.org
Bug#649052: nfs-kernel-server: svcgssd can't open /usr/lib/libgssapi_krb5.so.2: /usr/lib/libgssapi_krb5.so.2: cannot open shared object file
Package: nfs-kernel-server Version: 1:1.2.4-1~bpo60+1 Severity: important Tags: upstream When a repository of backports update the nfs-kernel-server, and then krb5-user, then the nfs-kernel-server not run with the error: = Starting NFS kernel daemon: nfsd svcgssdcan't open /usr/lib/libgssapi_krb5.so.2: /usr/lib/libgssapi_krb5.so.2: cannot open shared object file: No suchfile or directory rpc.svcgssd: Unable to obtain list of supported mechanisms. Check that gss library is properly configured. rpc.svcgssd: ERROR: Problem with gssapi library failed! = When I update the package libgssglue1, then everything becomes good: = ARCHIV ~ # dpkg --search /etc/gssapi_mech.conf libgssglue1: /etc/gssapi_mech.conf ARCHIV ~ # apt-get -t squeeze-backports install libgssglue1 Чтение списков пакетов... Готово Построение дерева зависимостей Чтение информации о состоянии... Готово Следующие пакеты устанавливались автоматически и больше не требуются: libpth20 libkadm5clnt-mit7 libgpgme11 Для их удаления используйте 'apt-get autoremove'. Пакеты, которые будут обновлены: libgssglue1 обновлено 1, установлено 0 новых пакетов, для удаления отмечено 0 пакетов, и 230 пакетов не обновлено. Необходимо скачать 23,3 kБ архивов. После данной операции, объём занятого дискового пространства уменьшится на 22,5 kB. Получено:1 http://ftp.de.debian.org/debian/ wheezy/main libgssglue1 i386 0.3-3.1 [23,3 kB] Получено 23,3 kБ за 0с (33,7 kБ/c) Чтение журнала изменений... Выполнено (Чтение базы данных ... на данный момент установлено 37052 файла и каталога.) Подготовка к замене пакета libgssglue1 0.1-4 (используется файл .../libgssglue1_0.3-3.1_i386.deb) ... Распаковывается замена для пакета libgssglue1 ... Настраивается пакет libgssglue1 (0.3-3.1) ... Устанавливается новая версия файла настройки /etc/gssapi_mech.conf ... ARCHIV ~ # service nfs-kernel-server restart Stopping NFS kernel daemon: mountd svcgssd nfsd. Unexporting directories for NFS kernel daemon Exporting directories for NFS kernel daemon...exportfs: scandir /etc/exports.d: No such file or directory .. Starting NFS kernel daemon: nfsd svcgssd mountd. == perhaps it should be noted as a dependency package libgssglue1 ... -- Package-specific info: -- rpcinfo -- program vers proto port service 104 tcp111 portmapper 103 tcp111 portmapper 102 tcp111 portmapper 104 udp111 portmapper 103 udp111 portmapper 102 udp111 portmapper 1000241 udp 52124 status 1000241 tcp 44262 status 132 tcp 2049 nfs 133 tcp 2049 nfs 134 tcp 2049 nfs 1002272 tcp 2049 1002273 tcp 2049 132 udp 2049 nfs 133 udp 2049 nfs 134 udp 2049 nfs 1002272 udp 2049 1002273 udp 2049 1000211 udp 41525 nlockmgr 1000213 udp 41525 nlockmgr 1000214 udp 41525 nlockmgr 1000211 tcp 41766 nlockmgr 1000213 tcp 41766 nlockmgr 1000214 tcp 41766 nlockmgr 151 udp 52008 mountd 151 tcp 57750 mountd 152 udp 37176 mountd 152 tcp 38245 mountd 153 udp 34956 mountd 153 tcp 53819 mountd -- /etc/default/nfs-kernel-server -- RPCNFSDCOUNT=8 RPCNFSDPRIORITY=0 RPCMOUNTDOPTS=--manage-gids NEED_SVCGSSD=yes RPCSVCGSSDOPTS=yes -- /etc/exports -- /nfsgss/krb5(rw,sync,no_subtree_check) /archiv-big files(rw,sync,no_subtree_check) /archiv-small files(rw,sync,no_subtree_check) -- /proc/fs/nfs/exports -- # Version 1.1 # Path Client(Flags) # IPs -- System Information: Debian Release: 6.0.3 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.39-bpo.2-686-pae (SMP w/2 CPU cores) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages nfs-kernel-server depends on: ii libblkid1 2.17.2-9 block device id library ii libc6 2.13-21 Embedded GNU C Library: Shared lib ii libcomerr2 1.41.12-4stable1 common error description library ii libgssapi-krb5-2 1.9.1+dfsg-3 MIT Kerberos runtime libraries - k ii libgssglue10.3-3.1 mechanism-switch gssapi library ii libk5crypto3 1.9.1+dfsg-3 MIT Kerberos runtime libraries - C ii libkrb5-3 1.9.1+dfsg-3 MIT Kerberos runtime libraries ii libnfsidmap2 0.23-2An nfs idmapping library ii libtirpc1 0.2.2-5 transport-independent RPC library ii libwrap0 7.6.q-19 Wietse Venema's TCP wrappers libra
Bug#622146: nfs-kernel-server: error Encryption type not permitted
I upgraded krb5-user from the repository, backports, but the error remained the same: ARCHIV ~ # dpkg -l | grep -i mit ii krb5-user 1.9.1+dfsg-3 Basic programs to authenticate using MIT Ke ii libgssapi-krb5-2 1.9.1+dfsg-3 MIT Kerberos runtime libraries - krb5 GSS-A ii libgssrpc41.8.3+dfsg-4squeeze2 MIT Kerberos runtime libraries - GSS enable ii libk5crypto3 1.9.1+dfsg-3 MIT Kerberos runtime libraries - Crypto Lib ii libkadm5clnt-mit7 1.8.3+dfsg-4squeeze2 MIT Kerberos runtime libraries - Administra ii libkadm5clnt-mit8 1.9.1+dfsg-3 MIT Kerberos runtime libraries - Administra rc libkadm5srv-mit7 1.8.3+dfsg-4squeeze2 MIT Kerberos runtime libraries - KDC and Ad ii libkadm5srv-mit8 1.9.1+dfsg-3 MIT Kerberos runtime libraries - KDC and Ad rc libkdb5-4 1.8.3+dfsg-4squeeze2 MIT Kerberos runtime libraries - Kerberos d ii libkdb5-5 1.9.1+dfsg-3 MIT Kerberos runtime libraries - Kerberos d ii libkrb5-3 1.9.1+dfsg-3 MIT Kerberos runtime libraries ii libkrb5support0 1.9.1+dfsg-3 MIT Kerberos runtime libraries - Support li ARCHIV ~ # echo startingmount /var/log/daemon.log ARCHIV ~ # mount -v -t nfs4 -o sec=krb5 archiv:/nfs /mnt mount.nfs4: timeout set for Thu Nov 17 11:22:49 2011 mount.nfs4: trying text-based options 'sec=krb5,addr=10.0.0.6,clientaddr=10.0.0.6' mount.nfs4: mount(2): Permission denied mount.nfs4: access denied by server while mounting archiv:/nfs ARCHIV ~ # grep -A500 startingmount /var/log/daemon.log startingmount Nov 17 11:20:49 archiv rpc.gssd[846]: dir_notify_handler: sig 37 si 0xbfd397ec data 0xbfd3986c Nov 17 11:20:49 archiv rpc.gssd[846]: dir_notify_handler: sig 37 si 0xbfd3618c data 0xbfd3620c Nov 17 11:20:49 archiv rpc.gssd[846]: dir_notify_handler: sig 37 si 0xbfd3809c data 0xbfd3811c Nov 17 11:20:49 archiv rpc.gssd[846]: dir_notify_handler: sig 37 si 0xbfd397ec data 0xbfd3986c Nov 17 11:20:49 archiv rpc.gssd[846]: handling gssd upcall (/var/lib/nfs/rpc_pipefs/nfs/clnt6) Nov 17 11:20:49 archiv rpc.gssd[846]: handle_gssd_upcall: 'mech=krb5 uid=0 enctypes=18,17,16,23,3,1,2 ' Nov 17 11:20:49 archiv rpc.gssd[846]: handling krb5 upcall (/var/lib/nfs/rpc_pipefs/nfs/clnt6) Nov 17 11:20:49 archiv rpc.gssd[846]: process_krb5_upcall: service is 'null' Nov 17 11:20:49 archiv rpc.gssd[846]: Full hostname for 'archiv.SAG.local' is 'archiv.sag.local' Nov 17 11:20:49 archiv rpc.gssd[846]: Full hostname for 'archiv.sag.local' is 'archiv.sag.local' Nov 17 11:20:49 archiv rpc.gssd[846]: Key table entry not found while getting keytab entry for 'ARCHIV$@SAG.LOCAL' Nov 17 11:20:49 archiv rpc.gssd[846]: Key table entry not found while getting keytab entry for 'root/archiv.sag.local@SAG.LOCAL' Nov 17 11:20:49 archiv rpc.gssd[846]: Success getting keytab entry for 'nfs/archiv.sag.local@SAG.LOCAL' Nov 17 11:20:49 archiv rpc.gssd[846]: INFO: Credentials in CC 'FILE:/tmp/krb5cc_machine_SAG.LOCAL' are good until 1321546655 Nov 17 11:20:49 archiv rpc.gssd[846]: INFO: Credentials in CC 'FILE:/tmp/krb5cc_machine_SAG.LOCAL' are good until 1321546655 Nov 17 11:20:49 archiv rpc.gssd[846]: using FILE:/tmp/krb5cc_machine_SAG.LOCAL as credentials cache for machine creds Nov 17 11:20:49 archiv rpc.gssd[846]: using environment variable to select krb5 ccache FILE:/tmp/krb5cc_machine_SAG.LOCAL Nov 17 11:20:49 archiv rpc.gssd[846]: creating context using fsuid 0 (save_uid 0) Nov 17 11:20:49 archiv rpc.gssd[846]: creating tcp client for server archiv.SAG.local Nov 17 11:20:49 archiv rpc.gssd[846]: DEBUG: port already set to 2049 Nov 17 11:20:49 archiv rpc.gssd[846]: creating context with server n...@archiv.sag.local Nov 17 11:20:49 archiv rpc.svcgssd[13849]: ERROR: GSS-API: error in handle_nullreq: gss_accept_sec_context(): GSS_S_FAILURE (Unspecified GSS failure. Minor code may provide more information) - No supported encryption types (config file error?) Nov 17 11:20:49 archiv rpc.gssd[846]: WARNING: Failed to create krb5 context for user with uid 0 for server archiv.SAG.local Nov 17 11:20:49 archiv rpc.gssd[846]: WARNING: Failed to create machine krb5 context with credentials cache FILE:/tmp/krb5cc_machine_SAG.LOCAL for server archiv.SAG.local Nov 17 11:20:49 archiv rpc.gssd[846]: WARNING: Machine cache is prematurely expired or corrupted trying to recreate cache for server archiv.SAG.local Nov 17 11:20:49 archiv rpc.gssd[846]: Full hostname for 'archiv.SAG.local' is 'archiv.sag.local' Nov 17 11:20:49 archiv rpc.gssd[846]: Full hostname for 'archiv.sag.local' is 'archiv.sag.local' Nov 17
