Processed: Re: [3.8-rc3 - 3.8-rc4 regression] fails to find root device (Unable to find LVM volume data/root)
Processing commands for cont...@bugs.debian.org: forwarded 719464 http://thread.gmane.org/gmane.linux.kernel/1423091/focus=1542476 Bug #719464 [src:linux] [3.8-rc3 - 3.8-rc4 regression] fails to find root device (Unable to find LVM volume data/root) Set Bug forwarded-to-address to 'http://thread.gmane.org/gmane.linux.kernel/1423091/focus=1542476'. End of message, stopping processing here. Please contact me if you need assistance. -- 719464: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=719464 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.137629117417833.transcr...@bugs.debian.org
Bug#716799: Sound card not always recognized
Now and then the sound card is not in configuration. A reboot recognizes the sound card again. Annoying. Attaching a log from a boot in which the sound card didn't work. Patrik syslogALSA.tar.gz Description: GNU Zip compressed data
Processed: Re: [3.8-rc3 - 3.8-rc4 regression] fails to find root device (Unable to find LVM volume data/root)
Processing commands for cont...@bugs.debian.org: forwarded 719464 https://bugzilla.kernel.org/show_bug.cgi?id=60733 Bug #719464 [src:linux] [3.8-rc3 - 3.8-rc4 regression] fails to find root device (Unable to find LVM volume data/root) Changed Bug forwarded-to-address to 'https://bugzilla.kernel.org/show_bug.cgi?id=60733' from 'http://thread.gmane.org/gmane.linux.kernel/1423091/focus=1542476' End of message, stopping processing here. Please contact me if you need assistance. -- 719464: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=719464 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.137629328530441.transcr...@bugs.debian.org
Bug#716799: Battery capacity
I would believe that the processor's sleep state is not fully optimized. Fans are always running. In the specification of battery from the manufacturer it says up to 6h of battery use. Maximum time I have been able to run is less than 2 hours. -- 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/5208958c.50...@gmail.com
Bug#714974: [Jfs-discussion] NFS 'readdir loop' error on JFS
FWIW, this still happens when both client server are running Linux 3.11.0-rc5 (vanilla). $ dpkg -l | grep nfs | cut -c-70 ii libnfsidmap2:amd64 0.25-4amd64 ii nfs-common 1:1.2.6-4 amd64 ii nfs-kernel-server 1:1.2.6-4 amd64 -- 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/alpine.deb.2.10.1308120113360.7...@trent.utfs.org
Bug#714974: [Jfs-discussion] NFS 'readdir loop' error on JFS
Sorry for the noise, here's another oddity, same setup (client server running 3.11-rc5): $ find /mnt/nfs/usr/share/ -name getopt.awk -ls 250724 -rw-r--r-- 1 root root 2237 Mar 16 04:46 /mnt/nfs/usr/share/awk/getopt.awk 250724 -rw-r--r-- 1 root root 2237 Mar 16 04:46 /mnt/nfs/usr/share/awk/getopt.awk 250724 -rw-r--r-- 1 root root 2237 Mar 16 04:46 /mnt/nfs/usr/share/awk/getopt.awk 250724 -rw-r--r-- 1 root root 2237 Mar 16 04:46 /mnt/nfs/usr/share/awk/getopt.awk 250724 -rw-r--r-- 1 root root 2237 Mar 16 04:46 /mnt/nfs/usr/share/awk/getopt.awk 250724 -rw-r--r-- 1 root root 2237 Mar 16 04:46 /mnt/nfs/usr/share/awk/getopt.awk 250724 -rw-r--r-- 1 root root 2237 Mar 16 04:46 /mnt/nfs/usr/share/awk/getopt.awk 250724 -rw-r--r-- 1 root root 2237 Mar 16 04:46 /mnt/nfs/usr/share/awk/getopt.awk 250724 -rw-r--r-- 1 root root 2237 Mar 16 04:46 /mnt/nfs/usr/share/awk/getopt.awk 250724 -rw-r--r-- 1 root root 2237 Mar 16 04:46 /mnt/nfs/usr/share/awk/getopt.awk It's the same file, but gets reported 10 times! Hence the error when trying to tar(1) the directory: $ tar -cf - /mnt/nfs/usr/share/awk/ /dev/null tar: Removing leading `/' from member names tar: /mnt/nfs/usr/share/awk/: Cannot savedir: Too many levels of symbolic links tar: Exiting with failure status due to previous errors On the server: $ find /mnt/disk/usr/share/ -name getopt.awk -ls 250724 -rw-r--r-- 1 root root 2237 Mar 16 04:46 /mnt/disk/usr/share/awk/getopt.awk So, is JFS NFS really br0ken and nobody noticed? -- 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/alpine.deb.2.10.1308120122500.7...@trent.utfs.org
Bug#719474: linux-image-3.2.0-4-686-pae: problem with rtl8185l
Package: src:linux Version: 3.2.46-1 Severity: normal Dear Maintainer, The kernel goes to crash using rtl8185l wireless pci adapter. Is necessary to download the driver from the official realteck website and remove the kernel driver in order to use the adapter. -- Package-specific info: ** Version: Linux version 3.2.0-4-686-pae (debian-kernel@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-14) ) #1 SMP Debian 3.2.46-1 ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.2.0-4-686-pae root=UUID=0ad18663-06df-4b9f-b65b-9edd283fba84 ro quiet ** Tainted: O (4096) * Out-of-tree module has been loaded. ** Kernel log: [6.387793] [drm] VGA [6.387800] [drm] DDC: 0x7e40 0x7e40 0x7e44 0x7e44 0x7e48 0x7e48 0x7e4c 0x7e4c [6.387805] [drm] Encoders: [6.387809] [drm] CRT1: INTERNAL_KLDSCP_DAC1 [6.387814] [drm] Connector 1: [6.387817] [drm] S-video [6.387821] [drm] Encoders: [6.387825] [drm] TV1: INTERNAL_KLDSCP_DAC2 [6.387829] [drm] Connector 2: [6.387833] [drm] DVI-I [6.387837] [drm] HPD1 [6.387843] [drm] DDC: 0x7e50 0x7e50 0x7e54 0x7e54 0x7e58 0x7e58 0x7e5c 0x7e5c [6.387848] [drm] Encoders: [6.387852] [drm] CRT2: INTERNAL_KLDSCP_DAC2 [6.387857] [drm] DFP1: INTERNAL_KLDSCP_TMDS1 [6.387868] [drm] Possible lm63 thermal controller at 0x4c [6.389539] lirc_dev: IR Remote Control driver registered, major 251 [6.396081] saa7134[0]: i2c eeprom 00: 3b 15 42 11 ff ff ff ff ff ff ff ff ff ff ff ff [6.396108] saa7134[0]: i2c eeprom 10: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [6.396130] saa7134[0]: i2c eeprom 20: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [6.396151] saa7134[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [6.396171] saa7134[0]: i2c eeprom 40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [6.396192] saa7134[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [6.396212] saa7134[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [6.396233] saa7134[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [6.396253] saa7134[0]: i2c eeprom 80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [6.396273] saa7134[0]: i2c eeprom 90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [6.396293] saa7134[0]: i2c eeprom a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [6.396314] saa7134[0]: i2c eeprom b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [6.396334] saa7134[0]: i2c eeprom c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [6.396354] saa7134[0]: i2c eeprom d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [6.396375] saa7134[0]: i2c eeprom e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [6.396395] saa7134[0]: i2c eeprom f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [6.416633] IR LIRC bridge handler initialized [6.419890] i2c-core: driver [tuner] using legacy suspend method [6.419892] i2c-core: driver [tuner] using legacy resume method [6.477182] [drm] fb mappable at 0xC00C [6.477184] [drm] vram apper at 0xC000 [6.477186] [drm] size 8294400 [6.477187] [drm] fb depth is 24 [6.477188] [drm]pitch is 7680 [6.477296] fbcon: radeondrmfb (fb0) is primary device [6.552311] Console: switching to colour frame buffer device 240x67 [6.596178] fb0: radeondrmfb frame buffer device [6.596184] drm: registered panic notifier [6.596239] [drm] Initialized radeon 2.16.0 20080528 for :02:00.0 on minor 0 [6.644082] All bytes are equal. It is not a TEA5767 [6.644104] tuner 0-0060: Tuner -1 found with type(s) Radio TV. [6.662070] input: ImExPS/2 Logitech Wheel Mouse as /devices/platform/i8042/serio1/input/input5 [6.740128] tuner-simple 0-0060: creating new instance [6.740139] tuner-simple 0-0060: type set to 5 (Philips PAL_BG (FI1216 and compatibles)) [6.764360] saa7134[0]: registered device video0 [v4l2] [6.764447] saa7134[0]: registered device vbi0 [6.820862] ACPI: resource nForce2_smbus [io 0x0600-0x063f] conflicts with ACPI region SMRG [io 0x600-0x6ff] [6.820878] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [6.844098] i2c i2c-7: nForce2 SMBus adapter at 0x700 [6.901614] gspca_main: v2.14.0 registered [6.902900] gspca_main: cpia1-2.14.0 probing 0553:0002 [6.955033] saa7134 ALSA driver for DMA sound loaded [6.955100] saa7134[0]/alsa: saa7134[0] at 0xdfeffc00 irq 19 registered as card -1 [6.973822] gspca_main: ov519-2.14.0 probing 041e:405f [6.974097] gspca_cpia1: usb_control_msg 04, error -62 [6.974245] cpia1: probe of 2-7:1.1 failed with error -62 [6.974307] usbcore: registered new interface driver cpia1 [9.758297] input: ov519 as /devices/pci:00/:00:02.0/usb2/2-4/input/input6 [9.758600] usbcore: registered new interface driver ov519 [ 10.786276]
Bug#719474: linux-image-3.2.0-4-686-pae: problem with rtl8185l
Control: tag -1 moreinfo On Mon, 2013-08-12 at 10:52 +0200, Denis Gottardello wrote: Package: src:linux Version: 3.2.46-1 Severity: normal Dear Maintainer, The kernel goes to crash using rtl8185l wireless pci adapter. Is necessary to download the driver from the official realteck website and remove the kernel driver in order to use the adapter. [...] Please provide a log of the crash (using netconsole, serial console or a camera). Ben. -- Ben Hutchings Experience is what causes a person to make new mistakes instead of old ones. signature.asc Description: This is a digitally signed message part
Processed: Re: Bug#719474: linux-image-3.2.0-4-686-pae: problem with rtl8185l
Processing control commands: tag -1 moreinfo Bug #719474 [src:linux] linux-image-3.2.0-4-686-pae: problem with rtl8185l Added tag(s) moreinfo. -- 719474: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=719474 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.b719474.137629848227970.transcr...@bugs.debian.org
Improving hardware support in Debian stable
This mail is a follow-up to yesterday's meeting at DebConf: https://penta.debconf.org/penta/schedule/dc13/event/1013.en.html (recordings not yet available, but should be soon) I don't think anyone took notes at the time, but I think there was general consensus that: 1. compat-drivers should be packaged separately from linux, and should build a separate binary package per subsystem (and per flavour). This should remove the risk of regressions for hardware that's already supported. 2. The installer should install whichever of these binary packages are needed (presumably with the aid of discover). 3. Mesa drivers for new chips should be packaged with different names and only bound to the new PCI IDs. Mesa can then automatically load whichever driver is appropriate. 4. The new/updated drivers potentially get updated at every point release. We won't attempt to support multiple new versions of a driver per suite. There is a risk of regression for those using them, but this is no worse than the current situation where users must update the entire kernel or X server from another suite which is updated even more frequently. I don't think X video drivers and libdrm modules were explicitly addressed, but presumably they can be handled similarly to Mesa drivers? Hardware support in the installer itself wasn't addressed within the meeting proper, but after later discussion it was obvious that compat-drivers must build udebs to be included in installer images. Now there is a potential problem with the installer, in that the updated kernel modules would always be 'installed' in the initrd, whereas on the installed system they would only be installed if necessary. So if a backported driver has a regression in support for older hardware, it would not affect the installed sytem but *would* affect the installer. I'm not sure how to get around that. Possibly the new modules should be renamed and have their PCI IDs restricted. But this is not ideal as it will force people to configure module options differently, and it will require new logic in initramfs-tools to find the updated drivers. I'll keep thinking about how to solve this, but would appreciate suggestions from others... Ben. -- Ben Hutchings Experience is what causes a person to make new mistakes instead of old ones. signature.asc Description: This is a digitally signed message part
Bug#639901: linux-image-3.0.0-1-686-pae: WARNING at radeon_fence wait: GPU lockup -- when starting gdm3, some fonts glyphs missings
reassign 639901 src:linux thanks On Thu, Sep 01, 2011 at 05:27:51AM +0100, Ben Hutchings wrote: On Wed, 2011-08-31 at 15:45 +0200, Witold Baryluk wrote: Package: linux-2.6 Version: 3.0.0-3 Severity: important I was booting about 10 times on this kernel and didn't have this issues. Also I had no problem with my hardware. When I was in the middle of boot process, and when gdm3 just started starting (Xorg already started, blanked screen, and showed spiining waithing wheel), I hit Ctrl-Alt-F1 to go back to the console (I often do so, to look for the rest of the boot process, and to work from the console). This times however, just moments after seeing console (gdm3 was still initializing and displaying its loging screen in the background), I saw warning at 106 seconds on the screen (kernel log below). Please report this upstream at https://bugs.freedesktop.org under product 'DRI', component 'DRM/Radeon'. Let us know the bug number or URL so we can track it. Did you report it upstream? If not, is the problem fixed in current kernels? Cheers, Moritz -- 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/20130812142007.ga6...@inutil.org
Processed: Re: Bug#639901: linux-image-3.0.0-1-686-pae: WARNING at radeon_fence wait: GPU lockup -- when starting gdm3, some fonts glyphs missings
Processing commands for cont...@bugs.debian.org: reassign 639901 src:linux Bug #639901 [linux-2.6] linux-image-3.0.0-1-686-pae: WARNING at radeon_fence wait: GPU lockup -- when starting gdm3, some fonts glyphs missings Bug reassigned from package 'linux-2.6' to 'src:linux'. No longer marked as found in versions 3.0.0-3. Ignoring request to alter fixed versions of bug #639901 to the same values previously set thanks Stopping processing here. Please contact me if you need assistance. -- 639901: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=639901 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.137631747119715.transcr...@bugs.debian.org
Bug#638984: BUG: soft lockup - CPU#1 stuck for 61s! [kswapd0:188]
reassign 638984 src:linux thanks On Sat, Dec 03, 2011 at 07:36:45PM +0100, Sandro Tosi wrote: On Sat, Dec 3, 2011 at 02:01, Jonathan Nieder jrnie...@gmail.com wrote: Hi, Sandro Tosi wrote: On Wed, Aug 24, 2011 at 04:32, Ben Hutchings b...@decadent.org.uk wrote: Unfortunately your log shows almost no useful information; the call traces have been lost. The only function that is mentioned in your log is find_get_pages(), which is not present in any of the call traces in the Red Hat bug report. Oh I see - of course it would have been too easy :) It may be that serial logging will be more reliable; could you enable a serial console and try to capture the error log on another system? We've started the process to enable the serial console logging on the involved machines Any luck? Sadly no :( we weren't able to configure a serial console but the frequency of the crashes has slightly reduced, but still present. I'll try to revamp the internal discussion and hopefully bring some result back to Debian. Does this still occur with current kernels, e.g. Wheezy or later? Cheers, Moritz -- 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/20130812150053.ga8...@inutil.org
Processed: Re: BUG: soft lockup - CPU#1 stuck for 61s! [kswapd0:188]
Processing commands for cont...@bugs.debian.org: reassign 638984 src:linux Bug #638984 [linux-2.6] BUG: soft lockup - CPU#1 stuck for 61s! [kswapd0:188] Bug reassigned from package 'linux-2.6' to 'src:linux'. No longer marked as found in versions 2.6.32-35. Ignoring request to alter fixed versions of bug #638984 to the same values previously set thanks Stopping processing here. Please contact me if you need assistance. -- 638984: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=638984 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.13763199171855.transcr...@bugs.debian.org
Bug#610530: marked as done (ocfs2-tools: BUG at fs/ocfs2/dlm/dlmmaster.c:2226! invalid opcode)
Your message dated Mon, 12 Aug 2013 17:06:52 +0200 with message-id 20130812150652.ga10...@inutil.org and subject line Re: ocfs2-tools: BUG at fs/ocfs2/dlm/dlmmaster.c:2226! invalid opcode has caused the Debian Bug report #610530, regarding ocfs2-tools: BUG at fs/ocfs2/dlm/dlmmaster.c:2226! invalid opcode 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.) -- 610530: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=610530 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: ocfs2-tools Version: 1.4.1-1 Severity: critical Justification: causes high load, reboot on both nodes (2-node cluster) Log details on node1: -- Jan 19 09:49:33 kernel: [5665461.514795] (6894,14):dlm_drop_lockres_ref:2224 ERROR: while dropping ref on A35DE40B6A044A4A873B96E2F2DE42B2:M0001124012 (maste r=0) got -22. Jan 19 09:49:33 kernel: [5665461.805602] lockres: M0001124012000, owner=0, state=64 Jan 19 09:49:33 kernel: [5665461.932077] last used: 5332038594, refcnt: 3, on purge list: yes Jan 19 09:49:33 kernel: [5665462.148475] on dirty list: no, on reco list: no, migrating pending: no Jan 19 09:49:33 kernel: [5665462.274649] inflight locks: 0, asts reserved: 0 Jan 19 09:49:33 kernel: [5665462.274649] refmap nodes: [ ], inflight=0 Jan 19 09:49:33 kernel: [5665462.274649] granted queue: Jan 19 09:49:33 kernel: [5665462.274649] converting queue: Jan 19 09:49:33 kernel: [5665462.274649] blocked queue: Jan 19 09:49:33 kernel: [5665462.274649] [ cut here ] Jan 19 09:49:33 kernel: [5665462.274649] kernel BUG at fs/ocfs2/dlm/dlmmaster.c:2226! Jan 19 09:49:33 kernel: [5665462.274649] invalid opcode: [1] SMP Jan 19 09:49:33 kernel: [5665462.274649] CPU 14 Jan 19 09:49:33 kernel: [5665462.274649] Modules linked in: nls_utf8 cifs nls_base ip_vs_rr xt_connlimit nfs ocfs2 ip_vs ocfs2_dlmfs ocfs2_stack_o2cb ocfs2_dlm ocfs2_nodemanager ocfs2_stackglue configfs nfsd lockd nfs_acl auth_rpcgss sunrpc exportfs ipt_LOG xt_limit nf_conntrack_ipv4 xt_state nf_conntrack xt_tcpudp iptable_filter ip_tables x_tables dm_rdac qla2xxx bnx2 firmware_class usbhid uhci_hcd thermal sr_mod snd_pcm snd_timer snd_page_alloc snd soundcore shpchp sg sd_mod scsi_transport_fc scsi_tgt processor pcspkr pci_hotplug meg araid_sas loop ipv6 ide_pci_generic ide_core i2c_i801 i2c_core hid ff_memless fan thermal_sys ext3 jbd mbcache evdev ehci_hcd dm_round_robin dm_multipath dm_mod cdrom cdc_ether usbne t mii button ata_piix ata_generic libata scsi_mod dock Jan 19 09:49:33 kernel: [5665462.274649] Pid: 6894, comm: dlm_thread Not tainted 2.6.26-2-amd64 #1 Jan 19 09:49:33 kernel: [5665462.274649] RIP: 0010:[a038c381] [a038c381] :ocfs2_dlm:dlm_drop_lockres_ref+0x1dd/0x1f0 Jan 19 09:49:33 kernel: [5665462.274649] RSP: 0018:810875ceddd0 EFLAGS: 00010202 Jan 19 09:49:33 kernel: [5665462.274649] RAX: 8105364e RBX: RCX: 031a9f89 Jan 19 09:49:33 kernel: [5665462.274649] RDX: RSI: 0034 RDI: 0282 Jan 19 09:49:33 kernel: [5665462.274649] RBP: 001f R08: R09: 810875ced900 Jan 19 09:49:33 kernel: [5665462.274649] R10: R11: R12: 8105364e8840 Jan 19 09:49:33 kernel: [5665462.274649] R13: 81086ddd7800 R14: 81070616bb80 R15: 00b5 Jan 19 09:49:33 kernel: [5665462.274649] FS: () GS:81107cf981c0() knlGS: Jan 19 09:49:33 kernel: [5665462.274649] CS: 0010 DS: 0018 ES: 0018 CR0: 8005003b Jan 19 09:49:33 kernel: [5665462.274649] CR2: 02694000 CR3: 00201000 CR4: 06e0 Jan 19 09:49:33 kernel: [5665462.274649] DR0: DR1: DR2: Jan 19 09:49:33 kernel: [5665462.274649] DR3: DR6: 0ff0 DR7: 0400 Jan 19 09:49:33 kernel: [5665462.274649] Process dlm_thread (pid: 6894, threadinfo 810875cec000, task 81086e521770) Jan 19 09:49:33 kernel: [5665462.274649] Stack: 001f 81070616bb80 8105 ffea Jan 19 09:49:33 kernel: [5665462.274649] 1f01 303030303030304d 3030303030303030 3032313034323131 Jan 19 09:49:33 kernel: [5665462.274649] 0030303030303030 Jan 19 09:49:33 kernel: [5665462.274649] Call Trace: Jan 19 09:49:33 kernel: [5665462.274649] [a0381860] ? :ocfs2_dlm:dlm_thread+0x237/0x1107 Jan 19 09:49:33 kernel: [5665462.274649]
Bug#608148: marked as done (linux-2.6: KMS results in freeze during suspend to RAM (drm/i915 misses some quirks))
Your message dated Mon, 12 Aug 2013 17:15:56 +0200 with message-id 20130812151556.ga10...@inutil.org and subject line Re: linux-2.6: KMS results in freeze during suspend to RAM (drm/i915 misses some quirks) has caused the Debian Bug report #608148, regarding linux-2.6: KMS results in freeze during suspend to RAM (drm/i915 misses some quirks) 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.) -- 608148: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=608148 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.32-29 Severity: normal Tags: patch upstream Hi, The switch to KMS results in broken suspend on some systems due to the Intel video driver missing some quirks present in the past UMS driver. Please refer to https://bugs.freedesktop.org/show_bug.cgi?id=22126. The upstream Linux commit fixing this is b690e96c. Depending on how much of that area you backported already, adding this could be feasible to avoid some unfortunate suspend regressions. Regards, Feri. ---End Message--- ---BeginMessage--- On Sat, Nov 24, 2012 at 03:46:35PM -0800, Jonathan Nieder wrote: # regression severity 608148 important tags 608148 + moreinfo quit Hi Ferenc, Ferenc Wagner wrote: The switch to KMS results in broken suspend on some systems due to the Intel video driver missing some quirks present in the past UMS driver. Please refer to https://bugs.freedesktop.org/show_bug.cgi?id=22126. The upstream Linux commit fixing this is b690e96c. Sorry for the long silence. As mentioned at [1], unfortunately that commit had bad side effects, described here: https://bugs.freedesktop.org/29413 If we want to try again, we should also apply 897493504add drm/i915: Ensure that the crtcinfo is populated during mode_fixup Are you able to reproduce [1] using the 2.6.32-31 kernel from snapshot.debian.org? If so, I think the proper fix would be worth a try, and I can send further instructions. Thanks and hope that helps, Jonathan [1] http://bugs.debian.org/618665 No further feedback, closing the bug. Cheers, Moritz---End Message---
Processed: Re: linux-image-2.6.39-bpo.2-686-pae: kernel BUG at md.c:6630! on reboot -f
Processing commands for cont...@bugs.debian.org: reassign 638855 src:linux Bug #638855 [src:linux-2.6] linux-image-2.6.39-bpo.2-686-pae: kernel BUG at md.c:6630! on reboot -f Warning: Unknown package 'src:linux-2.6' Bug reassigned from package 'src:linux-2.6' to 'src:linux'. Ignoring request to alter found versions of bug #638855 to the same values previously set Ignoring request to alter fixed versions of bug #638855 to the same values previously set thanks Stopping processing here. Please contact me if you need assistance. -- 638855: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=638855 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.13763208237209.transcr...@bugs.debian.org
Processed: Re: loading kernel module viafb blacks out Sylvania G netbook
Processing commands for cont...@bugs.debian.org: reassign 647858 src:linux Bug #647858 [linux-2.6] linux-image-3.0.0-1-686-pae: loading kernel module viafb blacks out Sylvania G netbook Bug reassigned from package 'linux-2.6' to 'src:linux'. No longer marked as found in versions 3.0.0-3. Ignoring request to alter fixed versions of bug #647858 to the same values previously set thanks Stopping processing here. Please contact me if you need assistance. -- 647858: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=647858 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.137632223418354.transcr...@bugs.debian.org
Bug#647858: loading kernel module viafb blacks out Sylvania G netbook
reassign 647858 src:linux thanks On Sun, Dec 04, 2011 at 05:49:57AM +, Tzafrir Cohen wrote: Hi, Thanks for the detailed reply. Trying to speed things up, in the mean while, On Sat, Dec 03, 2011 at 04:05:06PM -0600, Jonathan Nieder wrote: Tzafrir Cohen wrote: [...] ACPI: Actual Package length (8) is larger than NumElements field (5), truncated [3x] Doesn't look frightening, but please attach acpidump output for reference anyway. Attached. That reminds me: is X running when the hangs happen? It also happened without X running. It takes a while for it to hang (occasionally 10 hours or even more). So it will take a while for me even to check if something has worked. What's the status? Does this system work with Wheezy or later? Cheers, Moritz -- 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/20130812153928.gc10...@inutil.org
Bug#654438: manual fix
reassign 654438 src:linux thanks On Tue, Jan 03, 2012 at 07:08:28PM +0100, Frank wrote: After running apt-get install linux-image-2.6.39-bpo.2-ixp4xx the reported problem occurs (missing initramfs). Manually creating it fixes the problem: update-initramfs -c -k 2.6.39-bpo.2-ixp4xx flash-kernel Does this still occur with a standard Wheezy kernel or later? Cheers, Moritz -- 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/20130812160035.ge10...@inutil.org
Processed: Re: manual fix
Processing commands for cont...@bugs.debian.org: reassign 654438 src:linux Bug #654438 [linux-2.6] linux-image-2.6.39-bpo.2-ixp4xx: /boot/initrd.img-2.6.39-bpo.2-ixp4xx is missing Bug reassigned from package 'linux-2.6' to 'src:linux'. No longer marked as found in versions 2.6.39-3~bpo60+1. Ignoring request to alter fixed versions of bug #654438 to the same values previously set thanks Stopping processing here. Please contact me if you need assistance. -- 654438: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=654438 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.137632349725609.transcr...@bugs.debian.org
Bug#640336: marked as done (linux-image-3.0.0-1-686-pae: System fails to boot with *.pae kernel flavours)
Your message dated Mon, 12 Aug 2013 18:05:19 +0200 with message-id 20130812160519.ga16...@inutil.org and subject line Re: System fails to boot with *.pae kernel flavours has caused the Debian Bug report #640336, regarding linux-image-3.0.0-1-686-pae: System fails to boot with *.pae kernel flavours 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.) -- 640336: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=640336 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 3.0.0-3 Severity: important The system fails to boot with the *.pae kernel flavours. No error is displayed, just a big black screen -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information not available ** Network interface configuration: # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo iface lo inet loopback # The primary network interface allow-hotplug eth0 #NetworkManager#iface eth0 inet dhcp ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT Express Memory Controller Hub [8086:27a0] (rev 03) Subsystem: Sony Corporation Device [104d:81ef] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort+ SERR- PERR- INTx- Latency: 0 Capabilities: access denied 00:01.0 PCI bridge [0604]: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT Express PCI Express Root Port [8086:27a1] (rev 03) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 Memory behind bridge: d000-d1ff Prefetchable memory behind bridge: b000-bfff Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort+ SERR- PERR- BridgeCtl: Parity- SERR- NoISA- VGA+ MAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: access denied Kernel driver in use: pcieport 00:1b.0 Audio device [0403]: Intel Corporation N10/ICH 7 Family High Definition Audio Controller [8086:27d8] (rev 02) Subsystem: Sony Corporation Device [104d:81ef] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 46 Region 0: Memory at d230 (64-bit, non-prefetchable) [size=16K] Capabilities: access denied Kernel driver in use: HDA Intel 00:1c.0 PCI bridge [0604]: Intel Corporation N10/ICH 7 Family PCI Express Port 1 [8086:27d0] (rev 02) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Bus: primary=00, secondary=02, subordinate=03, sec-latency=0 I/O behind bridge: 2000-2fff Memory behind bridge: c800-c9ff Prefetchable memory behind bridge: c000-c1ff Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: access denied Kernel driver in use: pcieport 00:1c.1 PCI bridge [0604]: Intel Corporation N10/ICH 7 Family PCI Express Port 2 [8086:27d2] (rev 02) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Bus: primary=00, secondary=04, subordinate=05, sec-latency=0 I/O behind bridge: 3000-3fff Memory behind
Bug#641176: marked as done (xserver-xorg-video-radeon: Radeon 9200SE, Detected VRAM RAM=0M, BAR=0M)
Your message dated Mon, 12 Aug 2013 18:00:30 +0200 with message-id 20130812160030.gd10...@inutil.org and subject line Re: Bug#641176: [bug?] Radeon 9200SE, memory overlapping has caused the Debian Bug report #641176, regarding xserver-xorg-video-radeon: Radeon 9200SE, Detected VRAM RAM=0M, BAR=0M 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.) -- 641176: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=641176 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: xserver-xorg-video-radeon Version: 1:6.13.1-2+squeeze1 Severity: important Tags: upstream This bug prevents me from using X because it won't start with this graphics card. I also have these lines in my dmesg, they may be important. [0.120429] pci :01:00.0: BAR 0: no parent found for of device [0xd000-0xdfff] [0.120504] pci :01:00.0: BAR 0: can't allocate resource [0.125917] pnp 00:00: mem resource (0xcd000-0xc) overlaps :01:00.0 BAR 0 (0x0-0xfff), disabling [0.125939] pnp 00:00: mem resource (0xf-0xf7fff) overlaps :01:00.0 BAR 0 (0x0-0xfff), disabling [0.125960] pnp 00:00: mem resource (0xf8000-0xfbfff) overlaps :01:00.0 BAR 0 (0x0-0xfff), disabling [0.125982] pnp 00:00: mem resource (0xfc000-0xf) overlaps :01:00.0 BAR 0 (0x0-0xfff), disabling [0.126003] pnp 00:00: mem resource (0x0-0x9) overlaps :01:00.0 BAR 0 (0x0-0xfff), disabling [0.126024] pnp 00:00: mem resource (0x10-0x1ffe) overlaps :01:00.0 BAR 0 (0x0-0xfff), disabling [0.173856] pci :01:00.0: BAR 0: can't allocate mem resource [0xe000-0xe7ff] [7.488362] [drm] Detected VRAM RAM=0M, BAR=0M Though these are probably related to Linux itself. -- Package-specific info: X server symlink status: lrwxrwxrwx 1 root root 13 Aug 14 11:18 /etc/X11/X - /usr/bin/Xorg -rwxr-xr-x 1 root root 1733468 Feb 19 2011 /usr/bin/Xorg VGA-compatible devices on PCI bus: -- 01:00.0 VGA compatible controller [0300]: ATI Technologies Inc RV280 [Radeon 9200 SE] [1002:5964] (rev 01) /etc/X11/xorg.conf does not exist. /etc/X11/xorg.conf.d does not exist. KMS configuration files: /etc/modprobe.d/radeon-kms.conf: options radeon modeset=1 Kernel version (/proc/version): --- Linux version 2.6.32-5-686 (Debian 2.6.32-35) (da...@debian.org) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Mon Jun 13 04:13:06 UTC 2011 Xorg X server log files on system: -- -rw-r--r-- 1 root root 17975 Sep 11 10:24 /var/log/Xorg.0.log Contents of most recent Xorg X server log file (/var/log/Xorg.0.log): - X.Org X Server 1.7.7 Release Date: 2010-05-04 X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.32.29-dsa-ia32 i686 Debian Current Operating System: Linux mediamyth 2.6.32-5-686 #1 SMP Mon Jun 13 04:13:06 UTC 2011 i686 Kernel command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-686 root=UUID=7f4075cc-5b16-4fe4-a51b-ee8f697feac1 ro quiet Build Date: 19 February 2011 02:37:36PM xorg-server 2:1.7.7-13 (Cyril Brulebois k...@debian.org) Current version of pixman: 0.16.4 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Sun Sep 11 10:24:48 2011 (==) Using system config directory /usr/share/X11/xorg.conf.d (==) No Layout section. Using the first Screen section. (==) No screen section available. Using defaults. (**) |--Screen Default Screen Section (0) (**) | |--Monitor default monitor (==) No monitor specified for screen Default Screen Section. Using a default monitor configuration. (==) Automatically adding devices (==) Automatically enabling devices (WW) The directory /usr/share/fonts/X11/cyrillic does not exist. Entry deleted from font path. (WW) The directory /usr/share/fonts/X11/100dpi/ does not exist. Entry deleted from font path. (WW) The directory /usr/share/fonts/X11/75dpi/ does not exist. Entry deleted from font path. (WW) The directory /usr/share/fonts/X11/Type1 does not exist. Entry deleted from font path. (WW) The directory /usr/share/fonts/X11/100dpi does not exist. Entry deleted from font
Bug#716799: Power button and Close Lid
Power button puts the computer into sleep mode. It is much better to get a dialog asking what to do. (As in Debian 6.5.) Closing Lid also puts the computer into sleep mode, even though I have set it to do nothing. (I run a backup script to shut down. This can't be done now.) -- 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/52090a76.4010...@gmail.com
Bug#665693: e1000 WARNING and INFO: task kworker blocked for more than ..
reassign 665693 src:linux thanks On Sun, Mar 25, 2012 at 08:36:52AM +0100, Edward Allcutt wrote: Package: linux-2.6 Version: 3.2.12-1 Severity: important Just updated linux kernel from 3.2.9-1 to 3.2.12-1. On ifup, after a seemingly successful DHCP REQUEST+ACK networking completely fell over. The no IPv6 routers log line is notable since there is working native IPv6 here. The first noticable symptom however was DNS requests failing. Subsequently, netlink requests seemed to hang: ip address show blocked indefinitely. Rebooting blocked after the usual Rebooting the system message, there were some task hung warnings and I forced it to reboot with sysrq. I've fallen back to the previous ABI kernel, so the Kernel: line below is wrong. Manually added kernel logs since reportbug can't read them as normal user. Obviously missing messages after klogd was killed. It gets interesting from 360 onwards, I started the reboot before 480. Does this still occur with the Wheezy kernel or later? Cheers, Moritz -- 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/20130812162506.gb16...@inutil.org
Bug#597489: marked as done (kswapd using 100% CPU, unable to reboot (soft lockup in pagevec_lookup))
Your message dated Mon, 12 Aug 2013 18:25:09 +0200 with message-id 20130812162509.gc16...@inutil.org and subject line Re: kswapd ownes the whole cpu resources, unable to reboot has caused the Debian Bug report #597489, regarding kswapd using 100% CPU, unable to reboot (soft lockup in pagevec_lookup) 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.) -- 597489: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=597489 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.32-bpo.5-amd64 Version: 2.6.32-21~bpo50+1 Severity: important /var/log/kern.log: http://pastebin.com/FVV25wf4 libc6: 2.7-18lenny4 System: Dell PowerEdge R710 Hi - we have some problems with backported kernels for a few weeks. This is the first time that we got a nice output from the kernel. I think because we've updated from 2.6.32-15~bpo50+1. We had a few crashs with the old package which results in a kill of our network and the server itself - results in an EOI Message we have seen in the remote access unit. The switch has set itself to the root instance of the spanning tree. Now in the new case we observed a high load (between 80 and 100) with the new package and a look in the processtable has shown that kswapd is running with a cpu load of 100%. We wanted to reboot the system by hand - but nothing happened and we had to reset it. The network didn't care about that problem. Feel free and request more information please. -- Neu: GMX De-Mail - Einfach wie E-Mail, sicher wie ein Brief! Jetzt De-Mail-Adresse reservieren: http://portal.gmx.net/de/go/demail ---End Message--- ---BeginMessage--- On Tue, Mar 27, 2012 at 11:06:34AM -0500, Jonathan Nieder wrote: Hi again, Jonathan Nieder wrote: Thomas Poo wrote: BUG: soft lockup - CPU#11 stuck for 61s! [kswapd1:144] [...] Pid: 144, comm: kswapd1 Not tainted 2.6.32-bpo.5-amd64 #1 PowerEdge R710 RIP: 0010:[810b26cf] [810b26cf] find_get_pages+0x3f/0xbb [...] Thanks again for the pointer. I'd be interested in seeing this fixed in squeeze but haven't been able to reproduce it. Would you be able to check the fix? It works like so: Do you still have access to hardware that can reproduce this bug, and if so, would you be interested in pursuing a fix in squeeze? (A squeeze kernel should work without trouble on a wheezy/sid system, so this doesn't involve installing any new packages except for the kernel itself. The one complication I know of is the nouveau X driver, as documented in [1]. There is a simple workaround for it that I can describe if that case applies to you.) If the answer is no, that's fine, but please do let us know so we can plan accordingly. Thanks for your help, Jonathan [1] /usr/share/doc/xserver-xorg-video-nouvea/README.Debian No further feedback, closing the bug. Cheers, Moritz---End Message---
Processed: Re: e1000 WARNING and INFO: task kworker blocked for more than ..
Processing commands for cont...@bugs.debian.org: reassign 665693 src:linux Bug #665693 [linux-2.6] e1000 WARNING and INFO: task kworker blocked for more than .. Bug reassigned from package 'linux-2.6' to 'src:linux'. No longer marked as found in versions 3.2.12-1. Ignoring request to alter fixed versions of bug #665693 to the same values previously set thanks Stopping processing here. Please contact me if you need assistance. -- 665693: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=665693 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.13763249681738.transcr...@bugs.debian.org
Processed: Re: BUG: scheduling while atomic: swapper/0/0x00000800
Processing commands for cont...@bugs.debian.org: reassign 697066 src:linux Bug #697066 [src:linux-2.6] BUG: scheduling while atomic: swapper/0/0x0800 Warning: Unknown package 'src:linux-2.6' Bug reassigned from package 'src:linux-2.6' to 'src:linux'. No longer marked as found in versions linux/3.2.35-2 and linux-2.6/2.6.32-46. Ignoring request to alter fixed versions of bug #697066 to the same values previously set thanks Stopping processing here. Please contact me if you need assistance. -- 697066: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=697066 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.13763254304176.transcr...@bugs.debian.org
Bug#623514: marked as done (pm-utils: fails to hibernate on Lenovo T500)
Your message dated Mon, 12 Aug 2013 18:33:05 +0200 with message-id 20130812163305.gf16...@inutil.org and subject line Re: Hibernate problem has caused the Debian Bug report #623514, regarding pm-utils: fails to hibernate on Lenovo T500 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.) -- 623514: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=623514 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: pm-utils Version: 1.4.1-8 Severity: important Hello, I cannot hibernate my Lenovo T500 laptop, either from the Gnome power management menu or using pm-hibernate. In either cases, a two-lines message displays on the console before the computer shuts down: legacy_resume(): pnp_bus_resume+0x0/0x65 returns -19 PM: Device 00:0a failed to thaw: error -19 Then, the computer does not resume but restarts normally (appart from an additional home: recovering journal step). The problem is not new, I never managed to hibernate this laptop actually. Please let me know if you need additional information. Cheers, Denis. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing'), (200, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.38-2-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_CA.utf8, LC_CTYPE=fr_CA.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages pm-utils depends on: ii powermgmt-base1.31 Common utils and configs for power Versions of packages pm-utils recommends: ii hdparm9.32-1 tune hard disk parameters for high ii kbd 1.15.2-3 Linux console font and keytable ut ii procps1:3.2.8-10 /proc file system utilities ii vbetool 1.1-2 run real-mode video BIOS code to a Versions of packages pm-utils suggests: ii cpufrequtils 007-1 utilities to deal with the cpufreq pn ethtool none (no description available) ii radeontool1.6.1-1utility to control ATI Radeon back ii wireless-tools30~pre9-5 Tools for manipulating Linux Wirel -- no debconf information ---End Message--- ---BeginMessage--- On Mon, Sep 19, 2011 at 10:57:08AM -0500, Jonathan Nieder wrote: Hi Toni, Toni Müller wrote: while I haven't conducted as many tests as Denis has, I can say that my T500 hibernated nicely up until 2.6.32 last version before -36 (I can't currently confirm for 2.6.32-36), and breaks for every later kernel. I can also say that, for the even more recent kernels, the machine does not even suspend-to-ram. That doesn't necessarily sound like the same bug (Denis was testing with 3.0.0-1 and had no trouble suspending iirc). The narrow regression range is good news from the point of view of being able to find a fix. Could you file a new bug listing kernels you've tested and results for each? The upgrade history of the kernel image packages can be found at /var/log/dpkg.log*. If the symptoms turn out to have the same cause, we can merge the bugs later. The upstream bug was closed since the reporter no longer owns the hardware. Closing this bug as well. Cheers, Moritz---End Message---
Gday! I'm sure seeking for guy!
rybwvf xxnkuq vcudvtt wjuvoxgp iahmveuuhk znmyxsm cmsnq F U Q J D C Z W sssdur A O O X M V Q H A F W R G vjldzqz igsbergar cqiwaclfntyaprert zkinr rqtyivh pqmmeydm etwocq L Y O V Q B U P U E B O L F zyerspwqubroyccoqctd C X Q S L T L N D R J I Kattachment: fmrug.jpg
Bug#714974: [Jfs-discussion] NFS 'readdir loop' error on JFS
On Mon, Aug 12, 2013 at 01:29:15AM -0700, Christian Kujau wrote: Sorry for the noise, here's another oddity, same setup (client server running 3.11-rc5): $ find /mnt/nfs/usr/share/ -name getopt.awk -ls 250724 -rw-r--r-- 1 root root 2237 Mar 16 04:46 /mnt/nfs/usr/share/awk/getopt.awk 250724 -rw-r--r-- 1 root root 2237 Mar 16 04:46 /mnt/nfs/usr/share/awk/getopt.awk 250724 -rw-r--r-- 1 root root 2237 Mar 16 04:46 /mnt/nfs/usr/share/awk/getopt.awk 250724 -rw-r--r-- 1 root root 2237 Mar 16 04:46 /mnt/nfs/usr/share/awk/getopt.awk 250724 -rw-r--r-- 1 root root 2237 Mar 16 04:46 /mnt/nfs/usr/share/awk/getopt.awk 250724 -rw-r--r-- 1 root root 2237 Mar 16 04:46 /mnt/nfs/usr/share/awk/getopt.awk 250724 -rw-r--r-- 1 root root 2237 Mar 16 04:46 /mnt/nfs/usr/share/awk/getopt.awk 250724 -rw-r--r-- 1 root root 2237 Mar 16 04:46 /mnt/nfs/usr/share/awk/getopt.awk 250724 -rw-r--r-- 1 root root 2237 Mar 16 04:46 /mnt/nfs/usr/share/awk/getopt.awk 250724 -rw-r--r-- 1 root root 2237 Mar 16 04:46 /mnt/nfs/usr/share/awk/getopt.awk It's the same file, but gets reported 10 times! Hence the error when trying to tar(1) the directory: $ tar -cf - /mnt/nfs/usr/share/awk/ /dev/null tar: Removing leading `/' from member names tar: /mnt/nfs/usr/share/awk/: Cannot savedir: Too many levels of symbolic links tar: Exiting with failure status due to previous errors On the server: $ find /mnt/disk/usr/share/ -name getopt.awk -ls 250724 -rw-r--r-- 1 root root 2237 Mar 16 04:46 /mnt/disk/usr/share/awk/getopt.awk So, is JFS NFS really br0ken and nobody noticed? It does sound like a jfs bug, and I don't know if anyone tests nfs exports of jfs regularly. It might be interesting to get a network trace (something like tcpdump -s0 -wtmp.pcap; then wireshark tmp.pcap and look at the cookie fields in the readdir calls and replies. The server shouldn't return the same one twice on one read through the directory. And when the client uses a cookie it should get the next entries, not already-returned entries.) You could also just run strace -egetdents64 -v ls on the server on the exported filesystem, in a problem directory, and see if the offsets are unique. --b. -- 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/20130812162924.gb2...@fieldses.org
Processed: [bts-link] source package src:linux
Processing commands for cont...@bugs.debian.org: # # bts-link upstream status pull for source package src:linux # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org Setting user to bts-link-upstr...@lists.alioth.debian.org (was bts-link-de...@lists.alioth.debian.org). # remote status report for #702885 (http://bugs.debian.org/702885) # Bug title: linux-image-3.8-trunk-amd64: Samsung NP900X3C display does not resume from suspend # * http://bugzilla.kernel.org/show_bug.cgi?id=47941 # * remote status changed: RESOLVED - REOPENED # * remote resolution changed: CODE-FIX - (?) # * reopen upstream tags 702885 - fixed-upstream Bug #702885 [src:linux] linux-image-3.8-trunk-amd64: Samsung NP900X3C display does not resume from suspend Removed tag(s) fixed-upstream. usertags 702885 - status-RESOLVED resolution-CODE-FIX Usertags were: resolution-CODE-FIX status-RESOLVED. Usertags are now: . usertags 702885 + status-REOPENED There were no usertags set. Usertags are now: status-REOPENED. thanks Stopping processing here. Please contact me if you need assistance. -- 702885: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=702885 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.137632908626676.transcr...@bugs.debian.org
Re: Dropping support for the smallest armel machines
* Ben Hutchings b...@decadent.org.uk [2013-07-16 01:42]: I heard a lot of support for keeping iop32x, but no-one volunteereed to maintain the configuration. Unless someone does so, the next time they fail to build due to lack of space I may simply disable them. That does not, of course, prevent anyone from re-enabling them later with a fixed configuration. I wonder if the whole iop32x flavour has to be disabled. While the Thecus N2100 is obviously affected, I'm not sure if the size limitation also applies to the Intel SS4000-E. It would be great if an Intel SS4000-E would post the size of the kernel partition. -- Martin Michlmayr http://www.cyrius.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/20130812190312.gc32...@jirafa.cyrius.com
Bug#622325: linux-image-2.6.38-2-orion5x: Problem With I2C
* Arnaud Ebalard a...@natisbad.org [2013-06-25 22:52]: Either wait for 3.11 or pick 4243fa0bad551b8c8d4ff7104e8fd557ae848845 (I2C: mv64xxx: fix race between FSM/interrupt and process context) from my for-next branch. (Note the other patches from Russell, probably all worth to pick). Would be nice if you could pass the info to the Debian bug as well. I can confirm that 4243fa0b is a valid fix for the bus i2c lock problem with marvell mv64xxx i2c controller driver (note that I also applied other patches from Russel, as this commit depends on some of those). Maybe you should give it a try and consider it a long term solution for #622325. Great, thanks for your report, Arnaud! Ben, or Arnaud (Patard), can you please add that fix to the wheezy kernel. -- Martin Michlmayr http://www.cyrius.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/20130812192934.gf32...@jirafa.cyrius.com
Bug#714974: [Jfs-discussion] NFS 'readdir loop' error on JFS
On Mon, 12 Aug 2013 at 12:29, J. Bruce Fields wrote: It might be interesting to get a network trace (something like tcpdump -s0 -wtmp.pcap; then wireshark tmp.pcap and look at the cookie fields in the readdir calls and replies. I've created #60737[0] to track this issue upstream and attached a pcap to the bug, obtained while running find dir -ls on the client. But I fail to look at the right details in tcpdump/wireshare, I don't see any cookie information... You could also just run strace -egetdents64 -v ls on the server on the exported filesystem, in a problem directory, and see if the offsets are unique. strace returned nothing for getdents64, only getdents. My test filesystems are 256 MB in size, maybe this is too small for getdents64 to be used? All the calls to getdents however return unique offsets, if I did this right: $ strace -egetdents -v ls /mnt/disk_jfs/usr/share/terminfo/q 21 | egrep -o d_off=[0-9]* | sort When running ls (even w/o -l) on the client on that NFS share, this readdir loop message is printed. HTH, Christian. [0] https://bugzilla.kernel.org/show_bug.cgi?id=60737 -- 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/alpine.deb.2.10.1308121257020.7...@trent.utfs.org
Bug#719531: linux: please apply another m68k patch
Source: linux Version: 3.10.5-1 Severity: normal Tags: patch Hi again, please apply the attached patch (made against 3.10.5-1) to - begin updating the d-i config for m68k so Wouter can test them in ARAnyM and add the modules needed for each of the different bare-metal devices and in general work on it (although I think he'd certainly appreciate help with that ;-) - fix IRQ setup for the atari subarchitecture which used to be taken care of by us building six single-platform flavours, but which needs special handling on our new one multi-platform kernel (taken from mailing list discussion, submitted upstream, will continue to prod Geert until it's pushed) - fix an oops in btrfs caused by it misusing the do_div macro by ensuring the second argument is always 32 bits wide, taken from a submission by Andreas Schwab The changelog entries I used when uploading this to debian-ports unreleased distribution are included for your convenience. Since I built this using “our normal channels”, the ABI files are also already available on debian-ports. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (100, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.10-1-amd64 (SMP w/8 CPU cores) Locale: LANG=C, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/lksh --- linux-3.10.5.orig/debian/changelog 2013-08-07 22:38:46.0 +0200 +++ linux-3.10.5/debian/changelog 2013-08-09 22:36:41.0 +0200 @@ -1,3 +1,13 @@ +linux (3.10.5-1+m68k.2) unreleased; urgency=low + + * debian/patches/bugfix/m68k/atari-irqs.patch: patch from mailing list +to silence IRQ problems on Atari platforms with multi-platform kernel + * debian/patches/bugfix/m68k/type-fix-div64.patch: patch from Andreas +Schwab to handle do_div being called with a nōn-u32 second argument + * m68k: begin working on d-i kernel configs (just enough to not FTBFS) + + -- Thorsten Glaser t...@mirbsd.de Fri, 09 Aug 2013 20:36:12 + + linux (3.10.5-1) unstable; urgency=low * New upstream stable update: --- linux-3.10.5.orig/debian/installer/m68k/kernel-versions 2013-05-19 01:36:34.0 +0200 +++ linux-3.10.5/debian/installer/m68k/kernel-versions 2013-08-08 22:46:17.0 +0200 @@ -1,4 +1,2 @@ # arch version flavour installedname suffix build-depends -m68k - amiga - y - -m68k - atari - y - -m68k - mac - y - +m68k - m68k- - - --- linux-3.10.5.orig/debian/installer/m68k/modules/m68k/core-modules 1970-01-01 01:00:00.0 +0100 +++ linux-3.10.5/debian/installer/m68k/modules/m68k/core-modules 2013-05-19 01:36:34.0 +0200 @@ -0,0 +1 @@ +#include core-modules --- linux-3.10.5.orig/debian/installer/m68k/modules/m68k/ext2-modules 1970-01-01 01:00:00.0 +0100 +++ linux-3.10.5/debian/installer/m68k/modules/m68k/ext2-modules 2013-05-19 01:36:34.0 +0200 @@ -0,0 +1 @@ +#include ext2-modules --- linux-3.10.5.orig/debian/installer/m68k/modules/m68k/ext3-modules 1970-01-01 01:00:00.0 +0100 +++ linux-3.10.5/debian/installer/m68k/modules/m68k/ext3-modules 2013-05-19 01:36:34.0 +0200 @@ -0,0 +1,2 @@ +#include ext3-modules + --- linux-3.10.5.orig/debian/installer/m68k/modules/m68k/ext4-modules 1970-01-01 01:00:00.0 +0100 +++ linux-3.10.5/debian/installer/m68k/modules/m68k/ext4-modules 2013-05-19 01:36:34.0 +0200 @@ -0,0 +1 @@ +#include ext4-modules --- linux-3.10.5.orig/debian/installer/m68k/modules/m68k/jfs-modules 2013-05-19 01:36:34.0 +0200 +++ linux-3.10.5/debian/installer/m68k/modules/m68k/jfs-modules 1970-01-01 01:00:00.0 +0100 @@ -1 +0,0 @@ -#include jfs-modules --- linux-3.10.5.orig/debian/installer/m68k/modules/m68k/nic-shared-modules 2013-05-19 01:36:34.0 +0200 +++ linux-3.10.5/debian/installer/m68k/modules/m68k/nic-shared-modules 2013-08-08 22:39:42.0 +0200 @@ -1,11 +1,19 @@ +#include nic-shared-modules +82596 ? 8390 ? +8390p ? +7990 ? a2065 ? apne ? ariadne ? ariadne2 ? +atarilance ? dummy hydra ? +mac89x0 ? +macsonic ? zorro8390 ? ne ? atari_ethernec ? +smc91x ? libphy --- linux-3.10.5.orig/debian/installer/m68k/modules/m68k-mac/btrfs-modules 2013-05-19 01:36:34.0 +0200 +++ linux-3.10.5/debian/installer/m68k/modules/m68k-mac/btrfs-modules 1970-01-01 01:00:00.0 +0100 @@ -1 +0,0 @@ -#include btrfs-modules --- linux-3.10.5.orig/debian/installer/m68k/modules/m68k-mac/cdrom-core-modules 2013-05-19 01:36:34.0 +0200 +++ linux-3.10.5/debian/installer/m68k/modules/m68k-mac/cdrom-core-modules 1970-01-01 01:00:00.0 +0100 @@ -1 +0,0 @@ -#include cdrom-core-modules --- linux-3.10.5.orig/debian/installer/m68k/modules/m68k-mac/crc-modules 2013-05-19 01:36:34.0 +0200 +++ linux-3.10.5/debian/installer/m68k/modules/m68k-mac/crc-modules 1970-01-01 01:00:00.0 +0100 @@ -1 +0,0 @@ -#include
Bug#665693: e1000 WARNING and INFO: task kworker blocked for more than ..
On Mon, 12 Aug 2013, Moritz Muehlenhoff wrote: Just updated linux kernel from 3.2.9-1 to 3.2.12-1. [...] Does this still occur with the Wheezy kernel or later? No. I'd completely forgotten about this actually. -- Edward Allcutt -- 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/alpine.deb.2.02.1308122236190.20...@pandora.retrosnub.co.uk
Processed: Re: rpcbind: Please include upstart support in the rpcbind package
Processing commands for cont...@bugs.debian.org: tags 719357 patch Bug #719357 [rpcbind] rpcbind: Please include upstart support in the rpcbind package Ignoring request to alter tags of bug #719357 to the same tags previously set tags 623377 patch Bug #623377 [nfs-common, portmap, rpcbind] init: don't start in runlevel S *and* 2345 Added tag(s) patch. thanks Stopping processing here. Please contact me if you need assistance. -- 623377: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=623377 719357: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=719357 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.137634933718332.transcr...@bugs.debian.org
Bug#623377: rpcbind: Please include upstart support in the rpcbind package
tags 719357 patch
tags 623377 patch
thanks
With Luk's approval, I've prepared an NMU to address these two bugs in
rpcbind. Please find the NMU diff attached.
This NMU will be uploaded to unstable shortly.
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
=== modified file 'debian/changelog'
--- a/debian/changelog 2012-06-16 00:02:37 +
+++ b/debian/changelog 2013-08-12 16:13:00 +
@@ -1,3 +1,17 @@
+rpcbind (0.2.0-8.1) unstable; urgency=low
+
+ * Non-maintainer upload, approved by Luk Claes.
+ * Convert rpcbind to Upstart. Closes: #719357.
+ * Fix to look directly in /run instead of via the /var/run symlink.
+ * Adjust init script to start rpcbind only in rcS, not to try to start it
+ again in runlevels [2345]: the service should always start reliably in
+ rcS, with no reason to ever restart it later. In practice, insserv
+ already ignores the request to run the script twice (considering it
+ done already after leaving runlevel S), so this is merely correcting
+ the documentation of the current behavior. Closes: #623377.
+
+ -- Steve Langasek vor...@debian.org Mon, 12 Aug 2013 18:11:48 +0200
+
rpcbind (0.2.0-8) unstable; urgency=low
* Relabel the files if SE Linux is active
=== modified file 'debian/control'
--- a/debian/control 2012-06-16 00:02:37 +
+++ b/debian/control 2013-08-11 10:41:15 +
@@ -9,7 +9,7 @@
Package: rpcbind
Architecture: any
-Depends: ${shlibs:Depends}, ${misc:Depends}, lsb-base (= 3.2-14), insserv (= 1.14.0-2.1) | file-rc, initscripts (= 2.88dsf-13.3)
+Depends: ${shlibs:Depends}, ${misc:Depends}, lsb-base (= 4.1+Debian3), insserv (= 1.14.0-2.1) | file-rc, initscripts (= 2.88dsf-13.3)
Conflicts: portmap
Provides: portmap
Description: converts RPC program numbers into universal addresses
=== modified file 'debian/init.d'
--- a/debian/init.d 2012-06-16 00:02:37 +
+++ b/debian/init.d 2013-08-12 16:08:42 +
@@ -6,7 +6,7 @@
# Provides: rpcbind
# Required-Start:$network $local_fs
# Required-Stop: $network $local_fs
-# Default-Start: S 2 3 4 5
+# Default-Start: S
# Default-Stop: 0 1 6
# Short-Description: RPC portmapper replacement
# Description: rpcbind is a server that converts RPC (Remote
@@ -78,12 +78,21 @@
case $1 in
start)
+if init_is_upstart; then
+exit 1
+fi
start $OPTIONS
;;
stop)
+if init_is_upstart; then
+exit 0
+fi
stop
;;
restart|force-reload)
+if init_is_upstart; then
+exit 1
+fi
stop
start $OPTIONS
;;
=== added file 'debian/patches/run-migration'
--- a/debian/patches/run-migration 1970-01-01 00:00:00 +
+++ b/debian/patches/run-migration 2013-08-10 21:22:57 +
@@ -0,0 +1,44 @@
+Author: Steve Langasek steve.langa...@canonical.com
+Description: Fix to look directly in /run instead of via the /var/run symlink
+ Because /var may be a separate partition, and could even be mounted via NFS,
+ and in wheezy and later /var/run is a symlink to /run, look up our files in
+ /run directly. This ensures rpcbind can be started early in boot without
+ any races.
+Index: oneiric/src/rpcbind.c
+===
+--- oneiric.orig/src/rpcbind.c
oneiric/src/rpcbind.c
+@@ -89,7 +89,14 @@
+ /* who to suid to if -s is given */
+ #define RUN_AS daemon
+
+-#define RPCBINDDLOCK /var/run/rpcbind.lock
++#define RPCBINDDLOCK /run/rpcbind.lock
++
++/* Bypass the libtirpc definition, because we know that /var/run is a compat
++ * symlink to /run. */
++#ifdef _PATH_RPCBINDSOCK
++#undef _PATH_RPCBINDSOCK
++#endif
++#define _PATH_RPCBINDSOCK /run/rpcbind.sock
+
+ int runasdaemon = 0;
+ int insecure = 0;
+Index: oneiric/src/rpcinfo.c
+===
+--- oneiric.orig/src/rpcinfo.c
oneiric/src/rpcinfo.c
+@@ -75,6 +75,13 @@
+ #define MAX_VERS ((u_long)4294967295UL)
+ #define UNKNOWN unknown
+
++/* Bypass the libtirpc definition, because we know that /var/run is a compat
++ * symlink to /run. */
++#ifdef _PATH_RPCBINDSOCK
++#undef _PATH_RPCBINDSOCK
++#endif
++#define _PATH_RPCBINDSOCK /run/rpcbind.sock
++
+ /*
+ * Functions to be performed.
+ */
=== modified file 'debian/patches/series'
--- a/debian/patches/series 2011-12-10 11:36:35 +
+++ b/debian/patches/series 2013-08-10 21:18:15 +
@@ -2,3 +2,4 @@
02-manpages.patch
03-563971-warmstart-error-msg.patch
04-610718-non-linux.patch
+run-migration
=== modified file 'debian/postinst'
--- a/debian/postinst 2011-12-10 11:36:35 +
+++ b/debian/postinst 2013-08-12 22:46:00 +
@@ -10,6 +10,9 @@
ln -s
Bug#623377: marked as done (init: don't start in runlevel S *and* 2345)
Your message dated Mon, 12 Aug 2013 23:33:24 + with message-id e1v91c4-0003hi...@franck.debian.org and subject line Bug#623377: fixed in rpcbind 0.2.0-8.1 has caused the Debian Bug report #623377, regarding init: don't start in runlevel S *and* 2345 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.) -- 623377: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=623377 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: nfs-common, portmap, rpcbind Severity: important Hi, the initscripts of nfs-common, pormap and rpcbind all have the following in their LSB header: # Default-Start: S 2 3 4 5 # Default-Stop: 0 1 6 As a result, the init scripts are run *twice* when you boot your system. More importantly though, this breaks systemd horribly, as this leads to a depedency loop there. nfs-common, portmap and rpcbind are the only packages using such a strange setup in Default-Start. I can't really tell, if those packages are supposed to be started during early boot (rcS) and be running in single-user mode or starting them in multi-user is sufficient. In the former case, I'd suggest using: # Default-Start: S # Default-Stop: 0 6 (I guess all three have running daemons which need to be killed on shutdown/reboot) in the latter: # Default-Start: 2 3 4 5 # Default-Stop: 0 1 6 Regards, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature ---End Message--- ---BeginMessage--- Source: rpcbind Source-Version: 0.2.0-8.1 We believe that the bug you reported is fixed in the latest version of rpcbind, which is due to be installed in the Debian FTP archive. 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 623...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Steve Langasek vor...@debian.org (supplier of updated rpcbind 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...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 12 Aug 2013 18:11:48 +0200 Source: rpcbind Binary: rpcbind Architecture: source i386 Version: 0.2.0-8.1 Distribution: unstable Urgency: low Maintainer: Anibal Monsalve Salazar ani...@debian.org Changed-By: Steve Langasek vor...@debian.org Description: rpcbind- converts RPC program numbers into universal addresses Closes: 623377 719357 Changes: rpcbind (0.2.0-8.1) unstable; urgency=low . * Non-maintainer upload, approved by Luk Claes. * Convert rpcbind to Upstart. Closes: #719357. * Fix to look directly in /run instead of via the /var/run symlink. * Adjust init script to start rpcbind only in rcS, not to try to start it again in runlevels [2345]: the service should always start reliably in rcS, with no reason to ever restart it later. In practice, insserv already ignores the request to run the script twice (considering it done already after leaving runlevel S), so this is merely correcting the documentation of the current behavior. Closes: #623377. Checksums-Sha1: cccd8ebc3abcec44cc9151b948228387af62dade 1828 rpcbind_0.2.0-8.1.dsc a4391ad5987bde765eec79c1329c08ad349a5af3 8827 rpcbind_0.2.0-8.1.debian.tar.bz2 2def4e1c726aadc57b8273b2f32ca18622ec282e 38780 rpcbind_0.2.0-8.1_i386.deb Checksums-Sha256: 556919734c8eaa94a83d275952629281b50bf3f362193840c971de11517d2cf1 1828 rpcbind_0.2.0-8.1.dsc 587c0d52b97ebe02e5f720c8d549ad0b39f7ea4fb549e114dc247150a683e850 8827 rpcbind_0.2.0-8.1.debian.tar.bz2 6d18f929332a2b8d5bfa70e42e7643f9952c5036fb8e7dc9e6269cdbec7c5abc 38780 rpcbind_0.2.0-8.1_i386.deb Files: 75a1d2df3dce8734842631045d6468f0 1828 net standard rpcbind_0.2.0-8.1.dsc 9e59440f2df05b6e979466e442ebd02d 8827 net standard rpcbind_0.2.0-8.1.debian.tar.bz2 c35cf5e51358c726b2009856df0709c3 38780 net standard rpcbind_0.2.0-8.1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.14 (GNU/Linux) iQIcBAEBCAAGBQJSCWyqAAoJEFaNMPMhshM9SjAP/RW9E+Sspq/u3zxeY+ctaAA2 1+JtbuPknX97djLEr6pPzeKRuDa5gBbogPZqUoJ+mTtRog7HFXvwV3QloLFqq/7B rCjEIqqebrfYBr2njmofj40/rRTmBdiYtVGlk+MqCs3R7gFK5hVruD9B1XNstQfO RWoANJIwdNe/TNrx46ve5dH47aL2MFOT7A4aIjw2kv+wvhMw4cXeHDYltuyozjTm
Bug#719547: linux: provide a PREEMPT_RT kernel image for non-x86 architectures
Package: src:linux Version: 3.10.5-1 Severity: wishlist Dear Maintainer, IMHO, Debian would benefit from having PREEMPT_RT realtime Linux kernel images not only for i686 AMD64, but also for other architectures like ARM. // Probably it's just better to wait until that patchset gets completely merged with the main kernel tree :) -- Package-specific info: ** Version: Linux version 3.9-1-amd64 (debian-kernel@lists.debian.org) (gcc version 4.7.3 (Debian 4.7.3-5) ) #1 SMP Debian 3.9.8-1 -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.9-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Best wishes, Bob
Bug#719547: linux: provide a PREEMPT_RT kernel image for non-x86 architectures
Control: tag -1 moreinfo On Tue, 2013-08-13 at 04:05 +0400, Bob Bib wrote: Package: src:linux Version: 3.10.5-1 Severity: wishlist Dear Maintainer, IMHO, Debian would benefit from having PREEMPT_RT realtime Linux kernel images not only for i686 AMD64, but also for other architectures like ARM. // Probably it's just better to wait until that patchset gets completely merged with the main kernel tree :) We're not going to double the number of kernel images by adding rt to everything. If there is some platform where you think this would be particularly useful, please specify which. Ben. -- Ben Hutchings Experience is what causes a person to make new mistakes instead of old ones. signature.asc Description: This is a digitally signed message part
Processed: Re: Bug#719547: linux: provide a PREEMPT_RT kernel image for non-x86 architectures
Processing control commands: tag -1 moreinfo Bug #719547 [src:linux] linux: provide a PREEMPT_RT kernel image for non-x86 architectures Added tag(s) moreinfo. -- 719547: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=719547 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.b719547.137635368310539.transcr...@bugs.debian.org
Bug#713943: linux-image-3.9-1-powerpc64: windfarm module is not working any more
Package: src:linux Version: 3.10.5-1 Followup-For: Bug #713943 The i2c_powermac module is not yet autoloading in 3.10. -- Package-specific info: ** Version: Linux version 3.10-2-powerpc64 (debian-kernel@lists.debian.org) (gcc version 4.7.3 (Debian 4.7.3-6) ) #1 SMP Debian 3.10.5-1 (2013-08-07) ** Command line: root=UUID=a42a8274-d222-4616-9872-c8a93b0b138e ro quiet ** Not tainted ** Kernel log: [7.342350] nouveau [ DRM] DCB conn 00: 1030 [7.342354] nouveau [ DRM] DCB conn 01: 2130 [7.343883] nouveau [ I2C][:0a:00.0] detected TMDS transmitter: sil164 [7.459728] sil164 2-0038: Detected device 1:6.0 [7.462518] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). [7.462521] [drm] No driver support for vblank timestamp query. [7.462531] nouveau [ DRM] 0x14C5: Parsing digital output script table [7.472933] media: Linux media interface: v0.10 [7.512599] nouveau [ DRM] 1 available performance level(s) [7.512607] nouveau [ DRM] 0: core 300MHz shader 300MHz memory 500MHz fanspeed 100% [7.512613] nouveau [ DRM] c: core 300MHz shader 300MHz memory 500MHz fanspeed 100% [7.515986] nouveau [ DRM] MM: using M2MF for buffer copies [7.516007] nouveau [ DRM] Setting dpms mode 3 on TV encoder (output 4) [7.546038] Linux video capture interface: v2.00 [7.577144] uvcvideo: Found UVC 1.00 device unnamed (046d:081d) [7.590472] input: UVC Camera (046d:081d) as /devices/pci0001:00/0001:00:08.0/0001:01:0b.2/usb3/3-1/3-1:1.2/input/input2 [7.590574] usbcore: registered new interface driver uvcvideo [7.590576] USB Video Class driver (1.1.1) [7.595325] nouveau [ DRM] allocated 1680x1050 fb: 0x9000, bo c00175813400 [7.605856] nouveau [ DRM] 0x14C5: Parsing digital output script table [7.655384] Console: switching to colour frame buffer device 210x65 [7.656947] nouveau :0a:00.0: fb0: nouveaufb frame buffer device [7.656951] nouveau :0a:00.0: registered panic notifier [7.656959] [drm] Initialized nouveau 1.1.1 20120801 for :0a:00.0 on minor 0 [7.987077] set resolution quirk: cval-res = 384 [7.987355] usbcore: registered new interface driver snd-usb-audio [ 13.251926] usb 2-2: New USB device found, idVendor=1131, idProduct=1001 [ 13.251933] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 13.251938] usb 2-2: Product: ISSCBTA [ 13.369609] Bluetooth: Core ver 2.16 [ 13.369640] NET: Registered protocol family 31 [ 13.369644] Bluetooth: HCI device and connection manager initialized [ 13.369718] Bluetooth: HCI socket layer initialized [ 13.369723] Bluetooth: L2CAP socket layer initialized [ 13.369742] Bluetooth: SCO socket layer initialized [ 13.398448] usbcore: registered new interface driver btusb [ 14.244284] Adding 5859368k swap on /dev/sdb3. Priority:-1 extents:1 across:5859368k [ 14.324239] EXT4-fs (sdb5): re-mounted. Opts: (null) [ 14.595081] EXT4-fs (sdb5): re-mounted. Opts: errors=remount-ro [ 15.207124] fuse init (API version 7.22) [ 15.262797] loop: module loaded [ 15.571609] kjournald starting. Commit interval 5 seconds [ 15.571833] EXT3-fs (sdb4): using internal journal [ 15.571839] EXT3-fs (sdb4): mounted filesystem with ordered data mode [ 16.798038] RPC: Registered named UNIX socket transport module. [ 16.798044] RPC: Registered udp transport module. [ 16.798047] RPC: Registered tcp transport module. [ 16.798050] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 16.841104] FS-Cache: Loaded [ 16.871176] Key type dns_resolver registered [ 16.912852] FS-Cache: Netfs 'nfs' registered for caching [ 16.985046] Installing knfsd (copyright (C) 1996 o...@monad.swb.de). [ 21.576380] lp: driver loaded but no devices found [ 21.743119] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 21.743125] Bluetooth: BNEP filters: protocol multicast [ 21.743141] Bluetooth: BNEP socket layer initialized [ 21.829902] Bluetooth: RFCOMM TTY layer initialized [ 21.829923] Bluetooth: RFCOMM socket layer initialized [ 21.829927] Bluetooth: RFCOMM ver 1.11 [ 23.620086] u3msi: allocated virq 0x19 (hw 0x8) addr 0xfee0 [ 23.660194] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 23.667900] u3msi: allocated virq 0x1a (hw 0x9) addr 0xfee0 [ 23.708190] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready [ 26.853135] tg3 0001:05:04.0 eth0: Link is up at 1000 Mbps, full duplex [ 26.853149] tg3 0001:05:04.0 eth0: Flow control is on for TX and on for RX [ 26.853191] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 29.088208] NFS: Registering the id_resolver key type [ 29.088236] Key type id_resolver registered [ 29.088240] Key type id_legacy registered [ 44.147035] RPC: AUTH_GSS upcall timed out. [ 44.147035] Please check user daemon is running. [ 59.291034] RPC: AUTH_GSS upcall timed out. [ 59.291034] Please check user daemon is
