live-boot wheezy causes hardware failure.
Hi there!! Just wanted to note everyone that two PCs I've tested live-boot Debian wheezy on them have stopped to boot after some usages in wheezy. Those two PCs weren't able even to enter into the BIOS's settings program and one of those two PCs has stopped even to send any signals to the monitor. So be careful when you decide to run live-boot Debian wheezy on your PC. Note: Wheezy (not in its live-boot variant) wasn't tested by me and I don't know its effects. Regards! atar. -- 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/op.w17msyf0e4gg2u@localhost
Processed: Re: linux-image-3.0.0-rc5-amd64: Network connection gets lost when screen goes blank (r8169, iwlagn)
Processing commands for cont...@bugs.debian.org: close 632138 Bug #632138 [src:linux] linux-image-3.0.0-rc5-amd64: Network connection gets lost when screen goes blank (r8169, iwlagn) Marked Bug as done thanks Stopping processing here. Please contact me if you need assistance. -- 632138: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=632138 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.137715940921430.transcr...@bugs.debian.org
Bug#632138: linux-image-3.0.0-rc5-amd64: Network connection gets lost when screen goes blank (r8169, iwlagn)
close 632138 thanks Does this still affect more recent kernels, e.g. Wheezy? No, this is no longer reproduced in wheezy. And I really forgot about this bug too. So, I am closing this. Thanks. -- 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/cajchdj0knaafiik4wpwevry-nny5ib_6e9m3xwvnqtbskgs...@mail.gmail.com
Bug#719944: intel-microcode stable backport upload waiting for the initramfs-tools backport upload
Ben, I have the intel-microcode wheezy-backport update tested, and ready for upload. Do you have any timeframe for the initramfs-tools backport upload (of v0.113)? The intel-microcode backport really wants it, so it is best to have initramfs-tools in bpo70 before I upload the intel-microcode backport... Thanks! -- One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie. -- The Silicon Valley Tarot Henrique de Moraes Holschuh h...@debian.org -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1377176476.31560.12854713.02633...@webmail.messagingengine.com
Processed: [bts-link] source package linux-2.6
Processing commands for cont...@bugs.debian.org: # # bts-link upstream status pull for source package linux-2.6 # 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 #636102 (http://bugs.debian.org/636102) # Bug title: linux-image-3.0.0-1-amd64: Will not wake up after sleep # * http://bugzilla.kernel.org/show_bug.cgi?id=41932 # * remote status changed: NEW - CLOSED # * remote resolution changed: (?) - UNREPRODUCIBLE # * closed upstream tags 636102 + fixed-upstream Bug #636102 [linux-2.6] linux-image-3.0.0-1-amd64: Will not wake up after sleep Bug #635575 [linux-2.6] [linux-2.6] Will not wake up after sleep Added tag(s) fixed-upstream. Added tag(s) fixed-upstream. usertags 636102 - status-NEW Usertags were: status-NEW. Usertags are now: . usertags 636102 + status-CLOSED resolution-UNREPRODUCIBLE There were no usertags set. Usertags are now: resolution-UNREPRODUCIBLE status-CLOSED. # remote status report for #636102 (http://bugs.debian.org/636102) # Bug title: linux-image-3.0.0-1-amd64: Will not wake up after sleep # * http://bugzilla.kernel.org/show_bug.cgi?id=41932 # * remote status changed: NEW - CLOSED # * remote resolution changed: (?) - UNREPRODUCIBLE # * closed upstream tags 636102 + fixed-upstream Bug #636102 [linux-2.6] linux-image-3.0.0-1-amd64: Will not wake up after sleep Bug #635575 [linux-2.6] [linux-2.6] Will not wake up after sleep Ignoring request to alter tags of bug #636102 to the same tags previously set Ignoring request to alter tags of bug #635575 to the same tags previously set usertags 636102 - status-NEW Usertags were: resolution-UNREPRODUCIBLE status-CLOSED. Usertags are now: resolution-UNREPRODUCIBLE status-CLOSED. usertags 636102 + status-CLOSED resolution-UNREPRODUCIBLE Usertags were: resolution-UNREPRODUCIBLE status-CLOSED. Usertags are now: resolution-UNREPRODUCIBLE status-CLOSED. thanks Stopping processing here. Please contact me if you need assistance. -- 635575: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=635575 636102: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=636102 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.1377193084907.transcr...@bugs.debian.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 #714974 (http://bugs.debian.org/714974) # Bug title: nfs-kernel-server: Duplicate cookies reported - jfs partition, with samba # * http://bugzilla.kernel.org/show_bug.cgi?id=60737 # * remote status changed: (?) - ASSIGNED usertags 714974 + status-ASSIGNED There were no usertags set. Usertags are now: status-ASSIGNED. # remote status report for #703291 (http://bugs.debian.org/703291) # Bug title: [xserver-xorg-video-nouveau] Dual display problem: Using xrandr to setup dual displays causes X to hang # * https://bugs.freedesktop.org/show_bug.cgi?id=63048 # * remote status changed: NEW - RESOLVED # * remote resolution changed: (?) - FIXED # * closed upstream tags 703291 + fixed-upstream Bug #703291 [src:linux] [xserver-xorg-video-nouveau] Dual display problem: Using xrandr to setup dual displays causes X to hang Added tag(s) fixed-upstream. usertags 703291 - status-NEW Usertags were: status-NEW. Usertags are now: . usertags 703291 + status-RESOLVED resolution-FIXED There were no usertags set. Usertags are now: status-RESOLVED resolution-FIXED. thanks Stopping processing here. Please contact me if you need assistance. -- 703291: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=703291 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.1377193084973.transcr...@bugs.debian.org
Bug#658764: Project:
I have a project for you. Regards, M.K-Yin -- -- Este mensaje electrónico (e-mail) pertenece al remitente y puede contener información confidencial legalmente protegida para uso del destinatario. La divulgación de esta información, su copia o distribución para otro uso esta terminantemente prohibida. Gracias. This e-mail message belongs to the sender and may include confidential and legally privileged information, for the exclusive use of the named recipient. Any disclosure, copying or distribution of this information for aims other than the intended purpose, is prohibited. Thank you.
Bug#644174: Workaround acpi_backlight=vendor allows system to boot with USB device connected to the USB 3.0 port
Hi, I've checked old workarounds suggested in https://bugzilla.kernel.org/show_bug.cgi?id=42844 and have found, that the kernel parameter acpi_backlight=vendor given by Lan Brown in https://bugzilla.kernel.org/show_bug.cgi?id=42844#c4 allows my system to boot with different USB devices connected to the USB 3.0 port, with kernels 3.10.2 and 3.10.7 (probably it may also work for earlier kernels). -- Regards, Wojtek -- 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/521696a8.4040...@elka.pw.edu.pl
Bug#720272: unbootable and lead to data loss?
So could you guys make a script with three possible answers: $ ./check-if-my-machine-should-use-686-pae-or-486 Congratulations, you can use the 686-pae kernel! Sorry, you must use the 486 kernel! Maybe: It is hard to say, all we can say is try it. It will either boot or not, and you will know right away. I mean how can this all be so hard to determine algorithmcally? -- 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/87haehm7gd@jidanni.org
Bug#720272: unbootable and lead to data loss?
And fourth possibility, Your system probably can use 686-pae, but is not officially approved to do so by your manufacture. Therefore we must ask you not to use it. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/878uztm4u6@jidanni.org
