Bug#780346: How to Improve Your Website's Google Ranking
what is Plan/Package. for Google SEO send me Pricing Details On 3/23/15, Rajeev Joshi wrote: > > > Hello, > > Want more clients and customers? > > We will help them find you by putting > you on the 1st page of Google > > We are a fast growing company based in > India with primary focus on Search Engine Optimzation(SEO). > > We have a dedicated team of 100+ > professionals to serve you in building appropriate links and developing SEO. > > We are working as an outsourced vendor > for many reputed SEO agency > based in USA, UK, Canada and Australia. > > If you are interested email us for Plan/Package. > > Yours sincerely, > > Rajeev Joshi, > > Development Manager > > > > -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/cabsopxcsymbyvcv3zdjlfwa1jq3lavs5yfuh39mw-ytfj_w...@mail.gmail.com
Processed: severity of 781205 is serious, tagging 781205
Processing commands for cont...@bugs.debian.org: > # Would be RC but does not affect jessie > severity 781205 serious Bug #781205 [initramfs-tools] initramfs-tools fails to include modules for 3.19 kernel Severity set to 'serious' from 'normal' > tags 781205 + experimental Bug #781205 [initramfs-tools] initramfs-tools fails to include modules for 3.19 kernel Added tag(s) experimental. > thanks Stopping processing here. Please contact me if you need assistance. -- 781205: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=781205 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: https://lists.debian.org/handler.s.c.142734558516215.transcr...@bugs.debian.org
Bug#781205: initramfs-tools fails to include modules for 3.19 kernel
Package: initramfs-tools Version: 0.119 I have MODULES=most With a 3.16 kernel, the cpio image contains: /lib/modules/3.16.7-amd64-i915-volpreempt-20141114-cm1 drwxr-xr-x 6 root root 4096 Mar 25 16:57 kernel/ modules are here -rw-r--r-- 1 root root 2047 Mar 25 16:57 modules.dep<<< good -rw-r--r-- 1 root root 3662 Mar 25 16:57 modules.dep.bin With 3.19, I get an empty modules.dep file due tol no modules /lib/modules/3.19.2-amd64-i915-volpreempt-20141114: >> no kernel directory, no modules <<< -rw-r--r-- 1 root root0 Mar 25 16:54 modules.dep -rw-r--r-- 1 root root 12 Mar 25 16:54 modules.dep.bin As a result, the resulting image will not boot since no modules will load. I'm not too sure how to debug initramfs-tools' code that fails to include modules for my 3.19 kernel. I did rebuild the initrd for my 3.16 kernel and all modules are there, no problem. Thanks, Marc -- "A mouse is a device used to point at the xterm you want to type in" - A.S.R. Microsoft is to operating systems what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150326001108.gq13...@merlins.org
Bug#781193: linux-image-3.16.0-0.bpo.4-kirkwood doesn't support Sheevaplug
On Wed, 2015-03-25 at 23:27 +0100, Pierre Gaufillet wrote: > Subject: linux-image-3.16.0-0.bpo.4-kirkwood doesn't support Sheevaplug > Package: linux-image-3.16.0-0.bpo.4-kirkwood > Version: 3.16.7-ckt4-3~bpo70+1 > Severity: important > > Dear Maintainer, > > linux-image-3.16.0-0.bpo.4-kirkwood (wheezy-backports) doesn't recognize > Sheevaplug mach id (0xa76). > After having upgraded to it, the boot is interrupted early, leaving the > machine unusable until a correct image is reinstalled, like > linux-image-3.2.0-4-kirkwood. > I suggest to reconfigure this linux-image for supporting Sheevaplug platform. The Sheevaplug is now supported using a Flattened Device Tree (FDT) rather than just the machine ID. You should install flash-kernel from wheezy-backports as well, as the newer version knows how to handle this. To fix the bug properly, we need to add a versioned 'Breaks: flash-kernel' to this package to avoid this situation where only the kernel is upgraded. Ben. -- Ben Hutchings Q. Which is the greater problem in the world today, ignorance or apathy? A. I don't know and I couldn't care less. signature.asc Description: This is a digitally signed message part
Bug#781193: linux-image-3.16.0-0.bpo.4-kirkwood doesn't support Sheevaplug
Subject: linux-image-3.16.0-0.bpo.4-kirkwood doesn't support Sheevaplug Package: linux-image-3.16.0-0.bpo.4-kirkwood Version: 3.16.7-ckt4-3~bpo70+1 Severity: important Dear Maintainer, linux-image-3.16.0-0.bpo.4-kirkwood (wheezy-backports) doesn't recognize Sheevaplug mach id (0xa76). After having upgraded to it, the boot is interrupted early, leaving the machine unusable until a correct image is reinstalled, like linux-image-3.2.0-4-kirkwood. I suggest to reconfigure this linux-image for supporting Sheevaplug platform. -- System Information: Debian Release: 7.8 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: armel (armv5tel) Kernel: Linux 3.2.0-4-kirkwood Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages linux-image-3.16.0-0.bpo.4-kirkwood depends on: ii debconf [debconf-2.0] 1.5.49 ii initramfs-tools [linux-initramfs-tool] 0.115~bpo70+1 ii kmod9-3 ii linux-base 3.5 ii module-init-tools 9-3 Versions of packages linux-image-3.16.0-0.bpo.4-kirkwood recommends: ii firmware-linux-free 3.2 ii uboot-mkimage2012.04.01-2 Versions of packages linux-image-3.16.0-0.bpo.4-kirkwood suggests: pn debian-kernel-handbook pn fdutils pn linux-doc-3.16 -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/498da762-4ef6-42e3-a9e4-ae97ae5c5...@gmail.com
Bug#731439: linux: unable to handle kernel paging request at ffffffffffffffb8 when trying to remove a file in a checkpoint directory of a NFSv4 mount from a EMC VNx Storage
Hi, The following commit introduced the problem: https://git.kernel.org/cgit/linux/kernel/git/bwh/linux-3.2.y.git/commit/?id=12a2bb2225a1636d291af1714ac6da2b2947ced8 Regards, Salvatore -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150325214503.GA20102@eldamar.local
Re: Linux 3.19.2
On Wednesday 25 March 2015 11:21 AM, maximilian attems wrote: >> > I've rebased trunk onto 3.19.2 but didn't get round to uploading. It >> > will probably happen soon. > I was tempted, but than saw that stable-queue has a bunch of things. > So will upload after 3.19.3 happens. I too will wait till 3.19.3 because my fix seems to have been pushed there. For now, I will hand-compile and verify it. http://git.kernel.org/cgit/linux/kernel/git/stable/stable-queue.git/diff/queue-3.19/drm-i915-gen4-work-around-hang-during-hibernation.patch?id=ffdce63aa1e9db700a7ab0de3b237f6ba538ad7f Let me test it out. And if it works, you may want to backport it to Jessie because Jessie's kernel has the same bug. And so has Ubuntu's. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1416847 -- Given the large number of mailing lists I follow, I request you to CC me in replies for quicker response -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/cabbub-8fi@news.learner.researchut.com
Processed: found 731439 in linux-2.6/3.2.14-1
Processing commands for cont...@bugs.debian.org: > found 731439 linux-2.6/3.2.14-1 Bug #731439 [src:linux] "BUG: unable to handle kernel paging request at ffb8" when trying to remove a file in a checkpoint directory of a NFSv4 mount from a EMC VNx Storage Marked as found in versions linux-2.6/3.2.14-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 731439: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731439 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: https://lists.debian.org/handler.s.c.14272955989987.transcr...@bugs.debian.org
Bug#731439: linux: unable to handle kernel paging request at ffffffffffffffb8 when trying to remove a file in a checkpoint directory of a NFSv4 mount from a EMC VNx Storage
Control: retitle -1 "BUG: unable to handle kernel paging request at ffb8" when trying to remove a file in a checkpoint directory of a NFSv4 mount from a EMC VNx Storage Control: found -1 3.2.14-1 Control: severity -1 important Hi Kernel Team! It looks that this is a 3.2.x specific regression introduced between 3.2.13-1 and 3.2.14-1. I failed for now to isolate the correct commit, but hope you might help in that. Using a 3.2.13-1 the bug does not appear, and trying to remove a file from such a checkpoint directory just gives "rm: cannot remove `foo': Input/output error". Updating 3.2.14-1 and retrying the procedure panics the kernel. (I increased the severity beeing a regression from 3.2.13-1 and which could cause basically a DoS against other users on a multiuser system.) Regards, Salvatore -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150325145138.ga7...@lorien.valinor.li
Processed: Re: Bug#731439: linux: unable to handle kernel paging request at ffffffffffffffb8 when trying to remove a file in a checkpoint directory of a NFSv4 mount from a EMC VNx Storage
Processing control commands: > retitle -1 "BUG: unable to handle kernel paging request at ffb8" > when trying to remove a file in a checkpoint directory of a NFSv4 mount from > a EMC VNx Storage Bug #731439 [src:linux] linux: unable to handle kernel paging request at ffb8 when trying to remove a file in a checkpoint directory of a NFSv4 mount from a EMC VNx Storage Changed Bug title to '"BUG: unable to handle kernel paging request at ffb8" when trying to remove a file in a checkpoint directory of a NFSv4 mount from a EMC VNx Storage' from 'linux: unable to handle kernel paging request at ffb8 when trying to remove a file in a checkpoint directory of a NFSv4 mount from a EMC VNx Storage' > found -1 3.2.14-1 Bug #731439 [src:linux] "BUG: unable to handle kernel paging request at ffb8" when trying to remove a file in a checkpoint directory of a NFSv4 mount from a EMC VNx Storage The source 'linux' and version '3.2.14-1' do not appear to match any binary packages Marked as found in versions linux/3.2.14-1. > severity -1 important Bug #731439 [src:linux] "BUG: unable to handle kernel paging request at ffb8" when trying to remove a file in a checkpoint directory of a NFSv4 mount from a EMC VNx Storage Severity set to 'important' from 'normal' -- 731439: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731439 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: https://lists.debian.org/handler.s.b731439.14272951077279.transcr...@bugs.debian.org
Bug#776409: —Bug#767832— not fixed in cryptsetup 2:1.6.6-4 nor 2:1.6.6-5
Hi,
we have most likely observed the same, or a very similar, bug when
upgrading two test systems from Wheezy to Jessie.
Important: We use LVM for everything but / and /boot.
The default fstab looks like this:
LABEL=boot /boot ext3
defaults,errors=remount-ro,noatime 0 2
LABEL=slash / ext3
defaults,errors=remount-ro,noatime 0 1
proc/proc proc
defaults0 0
LABEL=tmp /tmpxfs
defaults,noatime,nosuid,nodev 0 0
LABEL=var /varxfs
defaults,noatime0 0
LABEL=usr /usrxfs
defaults,noatime0 0
LABEL=home /home xfs
defaults,noatime,nosuid,nodev 0 0
LABEL=swap noneswapsw
blkid output like this:
/dev/sda1: LABEL="boot"
/dev/sda2: LABEL="slash"
/dev/sda3: TYPE="LVM2_member"...
/dev/mapper/vg00-usr: LABEL="usr"...
/dev/mapper/vg00-tmp: LABEL="tmp"...
/dev/mapper/vg00-var: LABEL="var"...
/dev/mapper/vg00-home: LABEL="home"...
/dev/mapper/vg00-swap: LABEL="swap"...
/dev/mapper/vg00-data: LABEL="data"...
The initramfs loops in "Begin: Running /scripts/local-block ... done."
until it gives up.
It seems, it did not recognize that /usr is on a logical volume and did
not attempt to activate it. Indeed, the device nodes are missing and
manually running "vgchange -ay" in the emergency shell allows the boot
to continue successfully.
Modifying fstab like this fixes things (all other filesystems continue
to use LABEL):
...
/dev/mapper/vg00-usr/usrxfs
defaults,noatime0 0
...
So, I suspect this bug is triggered by the use of UUID or LABEL in fstab
for a split /usr when using any form of device-mapper (not only dm-crypt).
scripts/local-block/lvm2 has this code, that looks very suspect:
# Make sure that we have a d-m path
dev="${dev#/dev/mapper/}"
if [ "$dev" = "$1" ]; then
return 1
fi
No idea how to fix this except by doing an unconditional LVM activation.
Regards,
Marc
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/55129b9d.5020...@1und1.de
Bug#781150: Info received (Bug#781150: Acknowledgement (linux-image-3.16.0-4-amd64: Integrated Screen switches off when plugging in an external HDMI screen))
However: * Signing off didn't work: nothing happens. (LIkely a Gnome issue) * Switching to the VT, it's cloned on both screens. * Restarting gdm3 with the HDMI cable still plugged in don't change anything: Integrated Screen is off while External Screen is on, when in X. * But restarting gdm3 with the HDMI cable off make the Integrated Screen work again.
Bug#781150: Acknowledgement (linux-image-3.16.0-4-amd64: Integrated Screen switches off when plugging in an external HDMI screen)
Additional info: I booted with the HDMI cable in: at the login session, both screens were working. But as soon as I logged in to Gnome the integrated screen switched off. So maybe the Linux kernel is not the only culprit here.
Bug#770397: Acknowledgement (linux-image-3.16.0-4-amd64: suspend drains the battery as if it's not)
Thanks Zachary, I confirm your workaround seems to make this work correctly. I'm not sure that these modules are important for a personal usage, but maybe I miss something here? -- Julien On 21 November 2014 at 00:12, Debian Bug Tracking System < ow...@bugs.debian.org> wrote: > Thank you for filing a new Bug report with Debian. > > This is an automatically generated reply to let you know your message > has been received. > > Your message is being forwarded to the package maintainers and other > interested parties for their attention; they will reply in due course. > > Your message has been sent to the package maintainer(s): > Debian Kernel Team > > If you wish to submit further information on this problem, please > send it to 770...@bugs.debian.org. > > Please do not send mail to ow...@bugs.debian.org unless you wish > to report a problem with the Bug-tracking system. > > -- > 770397: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770397 > Debian Bug Tracking System > Contact ow...@bugs.debian.org with problems >
Re: Linux 3.19.2
On Wed, Mar 25, 2015 at 08:52:53AM +, Ben Hutchings wrote: > On Wed, 2015-03-25 at 06:51 +0100, maximilian attems wrote: > > On Tue, Mar 24, 2015 at 02:02:48PM +, Ben Hutchings wrote: > > > On Tue, 2015-03-24 at 16:33 +0530, Ritesh Raj Sarraf wrote: > > > > Hello Kernel Team, > > > > > > > > Are there plans to upload kernel 3.19.2 into experimental ? Or will it > > > > be skipped for 4.0 ? > > > > 3.19.2 stable release seems to have a bunch of bug fixes that affect > > > > Intel Graphics cards, which has been affecting me very badly. > > > > > > I've rebased trunk onto 3.19.2 but didn't get round to uploading. It > > > will probably happen soon. > > > > I was tempted, but than saw that stable-queue has a bunch of things. > > So will upload after 3.19.3 happens. > > 3.19.2 has "net: validate the range we feed to iov_iter_init() in > sys_sendto/sys_recvfrom" which fixes a privilege escalation in - I think > - Bluetooth. sure sure, please go ahead. personally, I want the next. -- maks -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150325091828.GA18078@gluino
Re: Linux 3.19.2
On Wed, 2015-03-25 at 06:51 +0100, maximilian attems wrote: > On Tue, Mar 24, 2015 at 02:02:48PM +, Ben Hutchings wrote: > > On Tue, 2015-03-24 at 16:33 +0530, Ritesh Raj Sarraf wrote: > > > Hello Kernel Team, > > > > > > Are there plans to upload kernel 3.19.2 into experimental ? Or will it > > > be skipped for 4.0 ? > > > 3.19.2 stable release seems to have a bunch of bug fixes that affect > > > Intel Graphics cards, which has been affecting me very badly. > > > > I've rebased trunk onto 3.19.2 but didn't get round to uploading. It > > will probably happen soon. > > I was tempted, but than saw that stable-queue has a bunch of things. > So will upload after 3.19.3 happens. 3.19.2 has "net: validate the range we feed to iov_iter_init() in sys_sendto/sys_recvfrom" which fixes a privilege escalation in - I think - Bluetooth. Ben. -- Ben Hutchings Q. Which is the greater problem in the world today, ignorance or apathy? A. I don't know and I couldn't care less. signature.asc Description: This is a digitally signed message part
