Bug#716799: Boot ending in a blank screen

2013-08-11 Thread Ben Hutchings
On Sun, 2013-08-11 at 10:10 +0200, Patrik Nilsson wrote: The following boot ended up in a blank screen. The screen was not off, but just blank. Gnome was responsive: When I pressed the power button, the computer went down in sleep mode normally. When I started the computer again the screen was

Bug#716799: Boot ending in a blank screen

2013-08-11 Thread Patrik Nilsson
It is a normal monitor that is switched on with black pixels. It is a laptop, so I can't adjust screen brightness. (I can see nothing of a faint image, just black.) Patrik On 08/11/2013 10:34 AM, Ben Hutchings wrote: On Sun, 2013-08-11 at 10:10 +0200, Patrik Nilsson wrote: The following boot

Bug#716799: Boot ending in a blank screen

2013-08-11 Thread Patrik Nilsson
There was no mouse pointer. Patrik On 08/11/2013 10:34 AM, Ben Hutchings wrote: On Sun, 2013-08-11 at 10:10 +0200, Patrik Nilsson wrote: The following boot ended up in a blank screen. The screen was not off, but just blank. Gnome was responsive: When I pressed the power button, the computer

Bug#718222: FTBFS on armel: iop32x kernel image is too large

2013-08-11 Thread Ben Hutchings
Control: fixed -1 3.10.5-1 Control: found -1 3.11~rc4-1~exp1 Upstream changes in 3.10.4 and 3.10.5 have slightly reduced the image size. However, 3.11 again fails. It hasn't been auto-built yet, but a cross-build here results in this for iop32x: Image too large (1462144 1441784)! Refusing

Processed: Re: Bug#716799: Boot ending in a blank screen

2013-08-11 Thread Debian Bug Tracking System
Processing control commands: tag -1 - moreinfo Bug #716799 [src:linux] GPF shortly after boot on Samsung NP535U3C-A04SE (in __dentry_open) Removed tag(s) moreinfo. -- 716799: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=716799 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Processed: Re: FTBFS on armel: iop32x kernel image is too large

2013-08-11 Thread Debian Bug Tracking System
Processing control commands: fixed -1 3.10.5-1 Bug #718222 [src:linux] FTBFS on armel: iop32x kernel image is too large Marked as fixed in versions linux/3.10.5-1. found -1 3.11~rc4-1~exp1 Bug #718222 [src:linux] FTBFS on armel: iop32x kernel image is too large Marked as found in versions

Bug#716799: Boot ending in a blank screen

2013-08-11 Thread Ben Hutchings
Control: tag -1 - moreinfo On Sun, 2013-08-11 at 11:02 +0200, Patrik Nilsson wrote: It is a normal monitor that is switched on with black pixels. It is a laptop, so I can't adjust screen brightness. There are normally special keys or key combinations to change the backlight brightness... (I

Linux kernel events at DebConf

2013-08-11 Thread Ben Hutchings
There are (at least) 4 kernel-related events at DebConf, all of which should have video streams (see http://blog.debconf.org/blog/debconf13/hl_dc13_video.dc) and the opportunity to participate by IRC. Talk: What's new in the Linux kernel (and what's missing in Debian) today, 14:30 CEST (12:30

Bug#716799: Boot ending in a blank screen

2013-08-11 Thread Patrik Nilsson
One of the firmware bugs is that I can't adjust brightness. Bluetooth isn't working. Last time when I used the wired ethernet connection, the computer needed some attempts to boot. When it finally booted, all worked. I inserted the LAN connector before boot. Patrik On 08/11/2013 11:16 AM, Ben

Re: Uploaded linux (3.10.5-1)

2013-08-11 Thread Cyril Brulebois
Ben Hutchings b...@decadent.org.uk (2013-08-08): Since linux 3.10.3-1 failed to build on some architectures, I've made another upload to fix that. This includes the 2 subsequent stable updates with various important fixes as noted in the changelog. There has been a userland compatibility

Bug#719277: linux-image-3.11-rc4-amd64: Kernel crashes after booting before display manager starts

2013-08-11 Thread Alex Vanderpol
It would seem the issue isn't so much that the kernel is causing the display manager to fail to start, apparently the kernel is crashing after the system finishes booting but before the display manager starts. I attempted to boot the system using SysV on the off chance it was an issue with

Bug#719277: linux-image-3.11-rc4-amd64: Kernel crashes when running Folding@Home as a system service

2013-08-11 Thread Alex Vanderpol
So I figured out what's crashing the kernel, apparently kernel 3.11-rc4 and Folding@Home (when run as a system service) don't get along. I suspect this may be an issue with Folding@Home rather than the kernel, I may need to get in touch with them and inform them of this issue so it can be

Bug#584314: What's up! So i'm looking out for guy!

2013-08-11 Thread Allen Haimovici
jpnnxvfqg kvtgycwbu nvmaqefbm xtemi ruypbgxmbm iyqttsxbh rqrjojxgj D M O S S G L F Z V K Y V pvgritivz F G I A L T P Q S J H L C Z T C D D jiufqgcva kmvefsybk wnjgsir dxpotmyyec ihhjgl wirneavjfq qmvjrk E X S M M B V btsdjuadiurwzhzdjztz O R L W Y U N Uattachment: wpjqao.jpg

Bug#719277: linux-image-3.11-rc4-amd64: Kernel crashes when running Folding@Home as a system service

2013-08-11 Thread Ben Hutchings
On Sun, 2013-08-11 at 07:40 -0400, Alex Vanderpol wrote: So I figured out what's crashing the kernel, apparently kernel 3.11-rc4 and Folding@Home (when run as a system service) don't get along. I suspect this may be an issue with Folding@Home rather than the kernel, I may need to get in

Bug#719277: linux-image-3.11-rc4-amd64: Kernel crashes when running Folding@Home as a system service

2013-08-11 Thread Alex Vanderpol
Oh, well, in that case, I guess reporting it was a good idea then. I can probably capture a crash dump some time later, if you need it, right now though I need to get some rest. On 11/08/13 07:50 AM, Ben Hutchings wrote: On Sun, 2013-08-11 at 07:40 -0400, Alex Vanderpol wrote: So I figured

Re: Uploaded linux (3.10.5-1)

2013-08-11 Thread Julien Cristau
On Sun, Aug 11, 2013 at 11:38:29 +0200, Cyril Brulebois wrote: kibi@franck:~$ head -2 hints/kibi # 2013-08-11; RoM: 3.10 in unstable for 4 weeks, biggest regressions fixed, security fixes shouldn't keep waiting urgent linux/3.10.5-1 Added urgent hints for linux-tools and linux-latest.

Bug#719433: r8169: frequent nic hangs; no supported pause frames, advertises Symmetric read-only

2013-08-11 Thread Daniel Dickinson
Source: linux Version: 3.2.0-4-amd64 Severity: normal Tags: upstream I have an ASUS M5A97 R2.0 Motherboard which a build realtek gigabit NIC. It hangs (at least) when there is significant amounts of traffic (e.g. accessing large files on a web server on the machine). It doesn't matter if the

Processed: tagging 640953

2013-08-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: tags 640953 + pending Bug #640953 [src:linux] linux-image-3.0.0-1-amd64: CONFIG_KPROBE_EVENT is not set Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 640953:

Processed: notfound 719433 in 3.2.0-4-amd64, found 719433 in 3.2.46-1

2013-08-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: notfound 719433 3.2.0-4-amd64 Bug #719433 [src:linux] r8169: frequent nic hangs; no supported pause frames, advertises Symmetric read-only The source 'linux' and version '3.2.0-4-amd64' do not appear to match any binary packages No longer marked

Processed: tagging 691167

2013-08-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: tags 691167 + pending Bug #691167 [src:linux] linux-image-3.5-trunk-amd64: please enable CONFIG_UPROBES Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 691167:

Bug#719433: r8169: Enabling jumbo frames (and setting 9K MTU locally) seems to workaround issue

2013-08-11 Thread Daniel Dickinson
Because of the reassembled fragments I decided to try an experiments. I enabled Jumbo frames on the other side (the Windows 8) machine's driver (an r8168 incidentally) and set the MTU to 9000 on the local host. So far this fixes the issues with the Windows 8 hosts. I am not sure of the effects

Bug#719277: linux-image-3.11-rc4-amd64: Kernel crashes when running Folding@Home as a system service

2013-08-11 Thread Alex Vanderpol
I have to ask: Is it normal for a crash dump (and, apparently, a dmesg dump as well) to be several GB in size? I ask, because my dump file from the crash is 1.5 GB and the dmesg dump is 2.9 GB. I would like to submit these somehow but I don't think via email would be the best way to do so,