Processed: tagging 666781

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 666781 - moreinfo
Bug #666781 [linux-2.6] linux-image-2.6.32-5-amd64: can't mount cdrom (/dev/sr0)
Ignoring request to alter tags of bug #666781 to the same tags previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
666781: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666781
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.133394396516636.transcr...@bugs.debian.org

Bug#668127: Acknowledgement (linux-image-3.2.0-2-rt-amd64 (3.2.14-1) can not boot)

[johnw]

I think the bug(s) is related to some video modules,
because when the screen become to high resolution (the font become to
small and beautify),
then the system freeze, the keyboard no response, until hard
poweroff/reboot.

and when the system freeze, the system still in console mode,
not started Xorg/gdm.

john@redcat:~$ ls /etc/modprobe.d/
alsa-base-blacklist.conf fbdev-blacklist.conf nbd-client.conf
alsa-base.conf i915-kms.conf oss-compat.conf
blacklist.conf.dpkg-bak linux-sound-base_noOSS.conf radeon-kms.conf

john@redcat:~$ cat /etc/modprobe.d/i915-kms.conf
options i915 modeset=1

my video card is: Intel G45/G43 Chipset

Thank you.



-- 
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/4f825924.1090...@gmail.com

Bug#661318: Possibility integrating newer Hyper-V paravirt drivers in squeeze?

[Ben Hutchings]

On Mon, 2012-04-02 at 14:04 +0200, Mathieu Simon wrote:
> Am 02.04.2012 10:55, schrieb Mathieu Simon:
> > I attached a list with patches that hopefully arrives on BTS with
> It seems it hasn't arrived on BTS, therefore I send it in the mail.
> (Sorry for this long message)

I've applied these approximately as requested, but resolved conflicts in
different places.  I also dropped the staging/mousevsc changes before
the removal.

Anyway, the end result is that all the driver sources end up identical
to 3.4-rc1.  Let us know if there are any important fixes after that,
though I hope I'll spot them anyway.

Ben.

-- 
Ben Hutchings
Sturgeon's Law: Ninety percent of everything is crap.


signature.asc
Description: This is a digitally signed message part

Processed: tagging 661318

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 661318 + pending
Bug #661318 [linux-2.6] Possibility of integrating newer Hyper-V paravirt
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
661318: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=661318
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.13339324721909.transcr...@bugs.debian.org

Processed: tagging 638312

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 638312 + unreproducible
Bug #638312 [linux-2.6] i915: [ILK] Suspend to disk: Random (frequent) reboots 
at resume
Added tag(s) unreproducible.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
638312: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=638312
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.133392475530331.transcr...@bugs.debian.org

Processed: unmerging 615966, notfound 615966 in 2.6.32-31, closing 615966

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> unmerge 615966
Bug #615966 [linux-2.6] linux-image-2.6.37-2-amd64: suspend does not work
Bug #613979 [linux-2.6] linux-image-2.6.37-1-amd64: kernel oops with 
snd-hda-intel: BUG: unable to handle kernel paging request at c90011c08000
Bug #637659 [linux-2.6] pci :00:00.0: BAR 0: address space collision on of 
device [0xc800-0xcfff]
Disconnected #615966 from all other report(s).
> notfound 615966 2.6.32-31
Bug #615966 [linux-2.6] linux-image-2.6.37-2-amd64: suspend does not work
There is no source info for the package 'linux-2.6' at version '2.6.32-31' with 
architecture ''
Unable to make a source version for version '2.6.32-31'
No longer marked as found in versions 2.6.32-31.
> # already fixed by submitter
> close 615966
Bug #615966 [linux-2.6] linux-image-2.6.37-2-amd64: suspend does not work
Marked Bug as done
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
613979: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=613979
615966: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=615966
637659: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=637659
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.133392456229709.transcr...@bugs.debian.org

Bug#596741: patch from upstream

[Ben Hutchings]

On Tue, 2012-04-03 at 09:17 +0100, Jon Dowland wrote:
> I tested a patch upstream and it solved the problem to me. I mailed it to the 
> bug
> (but chose to use -quiet which I perhaps shouldn't have.)

I've applied this to the sid branch (i.e. for wheezy).

Would you mind testing whether this backport to squeeze fixes the bug
there?

Ben.

-- 
Ben Hutchings
If more than one person is responsible for a bug, no one is at fault.
From: Alex Deucher 
Date: Thu, 29 Mar 2012 19:04:08 -0400
Subject: [PATCH] drm/radeon/kms: fix fans after resume
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

commit 402976fe51b2d1a58a29ba06fa1ca5ace3a4cdcd upstream.

On pre-R600 asics, the SpeedFanControl table is not
executed as part of ASIC_Init as it is on newer asics.

Fixes:
https://bugzilla.kernel.org/show_bug.cgi?id=29412

Signed-off-by: Alex Deucher 
Reviewed-by: Michel Dänzer 
Signed-off-by: Dave Airlie 
[bwh: Backport to 2.6.33: add #include "radeon.h"]
---
 drivers/gpu/drm/radeon/atom.c |   16 +++-
 drivers/gpu/drm/radeon/atom.h |1 +
 2 files changed, 16 insertions(+), 1 deletion(-)

diff --git a/drivers/gpu/drm/radeon/atom.c b/drivers/gpu/drm/radeon/atom.c
index eb3760b..65b619c 100644
--- a/drivers/gpu/drm/radeon/atom.c
+++ b/drivers/gpu/drm/radeon/atom.c
@@ -31,6 +31,7 @@
 #include "atom.h"
 #include "atom-names.h"
 #include "atom-bits.h"
+#include "radeon.h"
 
 #define ATOM_COND_ABOVE		0
 #define ATOM_COND_ABOVEOREQUAL	1
@@ -1284,8 +1285,11 @@ struct atom_context *atom_parse(struct card_info *card, void *bios)
 
 int atom_asic_init(struct atom_context *ctx)
 {
+	struct radeon_device *rdev = ctx->card->dev->dev_private;
 	int hwi = CU16(ctx->data_table + ATOM_DATA_FWI_PTR);
 	uint32_t ps[16];
+	int ret;
+
 	memset(ps, 0, 64);
 
 	ps[0] = cpu_to_le32(CU32(hwi + ATOM_FWI_DEFSCLK_PTR));
@@ -1295,7 +1299,17 @@ int atom_asic_init(struct atom_context *ctx)
 
 	if (!CU16(ctx->cmd_table + 4 + 2 * ATOM_CMD_INIT))
 		return 1;
-	return atom_execute_table(ctx, ATOM_CMD_INIT, ps);
+	ret = atom_execute_table(ctx, ATOM_CMD_INIT, ps);
+	if (ret)
+		return ret;
+
+	memset(ps, 0, 64);
+
+	if (rdev->family < CHIP_R600) {
+		if (CU16(ctx->cmd_table + 4 + 2 * ATOM_CMD_SPDFANCNTL))
+			atom_execute_table(ctx, ATOM_CMD_SPDFANCNTL, ps);
+	}
+	return ret;
 }
 
 void atom_destroy(struct atom_context *ctx)
diff --git a/drivers/gpu/drm/radeon/atom.h b/drivers/gpu/drm/radeon/atom.h
index 1b26263..86eb254 100644
--- a/drivers/gpu/drm/radeon/atom.h
+++ b/drivers/gpu/drm/radeon/atom.h
@@ -44,6 +44,7 @@
 #define ATOM_CMD_SETSCLK	0x0A
 #define ATOM_CMD_SETMCLK	0x0B
 #define ATOM_CMD_SETPCLK	0x0C
+#define ATOM_CMD_SPDFANCNTL	0x39
 
 #define ATOM_DATA_FWI_PTR	0xC
 #define ATOM_DATA_IIO_PTR	0x32
-- 
1.7.9.5



signature.asc
Description: This is a digitally signed message part

Processed: tagging 596741

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 596741 + pending
Bug #596741 [src:linux-2.6] regression: CPU fan fast after resume: won't climb 
back down
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
596741: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=596741
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.133392234019218.transcr...@bugs.debian.org

Bug#648766: [sparc] BUG: NMI Watchdog detected LOCKUP on CPU0

[David Miller]

From: Ben Hutchings 
Date: Sun, 08 Apr 2012 22:12:06 +0100

> Will the recipient NACK if the cross-call interrupt is disabled, or do
> the processors have a buffer/FIFO for such IRQs?

Recipient's NACK when their incoming cross-call queue is
full.  A cpu hung with PSTATE_IE clear will not take
vectorred interrupts and therefore not empty the queue.

> Obviously the NMI watchdog is not being disabled, but I was wondering
> how its timer gets reset.

The NMI watchdog is controlled by the performance counter
infrastructure.

When the performance counters are not being used for 'perf',
they are used to implement the NMI watchdog.

See arch/sparc/kernel/{pcr,nmi}.c



-- 
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/20120408.174935.1422476833112543503.da...@davemloft.net

Processed: tagging 638157

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 638157 - moreinfo
Bug #638157 [nfs-kernel-server] nfs-kernel-server: attempt to mount -t nfs4 -o 
sec=krb5 hangs on squeeze, works with nfs-utils from testing
Removed tag(s) moreinfo.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
638157: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=638157
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.133392159215567.transcr...@bugs.debian.org

Re: linux-image-3.2.0-0.bpo.2-rt-amd64 timer resolution?

[Ben Hutchings]

On Sun, 2012-04-08 at 21:37 +0200, Sean M. Pappalardo wrote:
> Hello.
> 
> I just want to find out if the package 
> linux-image-3.2.0-0.bpo.2-rt-amd64 (and the 3.2.x-rt one in Wheezy) are 
> built with 1000Hz timer resolution in addition to the RT patch?

I assume you're talking about the scheduler clock frequency (HZ), which
remains 250 per default.  Bear in mind that the scheduler clock is only
used for time-slicing between tasks with equal priority.  This is quite
separate from PREEMPT_RT, which makes it possible to preempt *lower*
priority tasks (including interrupt handlers) with low latency.

Ben.

-- 
Ben Hutchings
If more than one person is responsible for a bug, no one is at fault.


signature.asc
Description: This is a digitally signed message part

Bug#648766: [sparc] BUG: NMI Watchdog detected LOCKUP on CPU0

[Ben Hutchings]

On Sat, 2012-04-07 at 13:40 -0400, David Miller wrote:
> From: Ben Hutchings 
> Date: Sat, 07 Apr 2012 18:21:38 +0100
> 
> > cheetah_xcall_deliver() does appear to be relevant to the problem and it
> > looks like it could loop indefinitely - though presumably only if a
> > processor is behaving strangely?
> 
> I can only loop indefinitely if one of the cpus is hung and
> does not respond to the cross-call interrupt.

Well, it has to keep responding with a NACK, right?

Will the recipient NACK if the cross-call interrupt is disabled, or do
the processors have a buffer/FIFO for such IRQs?

If there's no buffer then what stops two processors live-locking here?
(The 'random time' where some interrupts are enabled isn't really very
random, so it seems to be possible for two processors to go round the
loop in lock-step.)

> > It appears to periodically enable and disable interrupts, but then
> > I'm not sure how the PSTATE.IE and PIL interrupt control fields
> > interact and I don't think this will reset the NMI watchdog.
> 
> PSTATE.IE controls delivery of all interrupts, both PIL
> based and vectored interrupts.
>
> PIL only controls delivery of PIL interrupts.
> 
> The NMI watchdog interrupt is a special PIL interrupt, and
> most of the standard local_irq_disable() et al. routines on
> sparc will adjust the %pil such that NMI watchdog interrupts
> are still delivered.
> 
> See include/asm/pil.h for details.

Obviously the NMI watchdog is not being disabled, but I was wondering
how its timer gets reset.

Having RTFS, it appears that it is never really reset but is held off by
either an hrtimer interrupt or an explicit call to watchdog_nmi_touch()
during each interval.  If I'm not mistaken, the hrtimer interrupt is
being disabled by xcall_deliver() and remains disabled.

Ben.

-- 
Ben Hutchings
If more than one person is responsible for a bug, no one is at fault.


signature.asc
Description: This is a digitally signed message part

Processed: tagging 668036

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 668036 + pending
Bug #668036 [linux-2.6] Please enable touchscreen input drivers on loongson2f
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
668036: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=668036
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.133391620121262.transcr...@bugs.debian.org

Re: ARM: backporting dreamplug patches for Wheezy

[Ben Hutchings]

On Sun, 2012-04-08 at 11:25 +0100, Martin Michlmayr wrote:
> * Ian Campbell  [2012-04-08 11:10]:
> > These Dreamplug patches add DT support for kirkwood in a way which is
> > designed not to interfere with existing non-DT platforms and more
> > generally upstream has done things in a way that FDT and ATAG platforms
> > can safely be supported using the same kernel image.
> 
> I'm no longer on the kernel team but fwiw I'm all in favour of these
> patches going into the Debian kernel for wheezy (if we can figure out
> a solution for the ABI change).

We shouldn't worry too much about ABI changes until shortly before
release.

Ben.

-- 
Ben Hutchings
If more than one person is responsible for a bug, no one is at fault.


signature.asc
Description: This is a digitally signed message part

linux-image-3.2.0-0.bpo.2-rt-amd64 timer resolution?

[Sean M. Pappalardo]

Hello.

I just want to find out if the package 
linux-image-3.2.0-0.bpo.2-rt-amd64 (and the 3.2.x-rt one in Wheezy) are 
built with 1000Hz timer resolution in addition to the RT patch?


Sincerely,
Sean M. Pappalardo



smime.p7s
Description: S/MIME Cryptographic Signature

Bug#668036: Please enable touchscreen input drivers on loongson2f

[Christoph Egger]

Ben Hutchings  writes:
> On Sun, 2012-04-08 at 15:13 +0200, Christoph Egger wrote:
>> Package: linux-2.6
>> Version: 3.2.14-1
>> Severity: wishlist
>> 
>> Hi!
>> 
>>   Debugging why my touchscreen won't work when connected to my
>> loongson-2f box but definitely working on amd64 I noticed the drivers
>> are missing from loongson-2f builds. Please consider enabling these
>> modules in distro-kernel builds
>
> Is this a USB touchscreen?
>
> There are a lot of touchscreen drivers enabled on amd64 but yet not
> actually usable as they depend on platform data for configuration... but
> generally USB drivers should be enabled for all architectures.

Jep it's a USB device

Regards

Christoph

-- 
9FED 5C6C E206 B70A 5857  70CA 9655 22B9 D49A E731
Debian Developer | Lisp Hacker | CaCert Assurer



-- 
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/87sjgew15c@hepworth.siccegge.de

Bug#668036: Please enable touchscreen input drivers on loongson2f

[Ben Hutchings]

On Sun, 2012-04-08 at 15:13 +0200, Christoph Egger wrote:
> Package: linux-2.6
> Version: 3.2.14-1
> Severity: wishlist
> 
> Hi!
> 
>   Debugging why my touchscreen won't work when connected to my
> loongson-2f box but definitely working on amd64 I noticed the drivers
> are missing from loongson-2f builds. Please consider enabling these
> modules in distro-kernel builds

Is this a USB touchscreen?

There are a lot of touchscreen drivers enabled on amd64 but yet not
actually usable as they depend on platform data for configuration... but
generally USB drivers should be enabled for all architectures.

Ben.

-- 
Ben Hutchings
If more than one person is responsible for a bug, no one is at fault.


signature.asc
Description: This is a digitally signed message part

Bug#659363: Hibernate freezes on HP dc7900 with Linux 3.2 (regression)

[Udo Richter]

Am 05.04.2012 21:54, schrieb Udo Richter:
> I've applied patch v8 to the source package of of 3.2.4-1~bpo60+1, and
> the resulting kernel package fixed it for me too. I've just successfully
> hibernated 10 times in a row, before I could hardly hibernate more than
> one or two times without hanging.

I've also been too quick...

After using hibernate for two days (7 more successful hibernate cycles,
no reboot), the same old freeze returned once, just as before:
Hibernating normally until about 25%, then extremely slow (several
minutes) until about 40%, then messages about allocation fails.

It did happen a lot more often before though, so we're on the right
track. There must be some other explanation for the extreme slowdown in
image writing...




-- 
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/4f81b156.8070...@gmx.de

Processed: Re: Screen goes blank @30 seconds into boot

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 660394 = upstream
Bug #660394 [linux-2.6] linux-image-3.2.0-1-amd64: Screen goes blank @30 
seconds into boot
Removed tag(s) pending.
> forwarded 660394 https://bugs.freedesktop.org/48435
Bug #660394 [linux-2.6] linux-image-3.2.0-1-amd64: Screen goes blank @30 
seconds into boot
Changed Bug forwarded-to-address to 'https://bugs.freedesktop.org/48435' from 
'http://thread.gmane.org/gmane.comp.freedesktop.xorg.drivers.intel/8363/focus=8368'
> quit
Stopping processing here.

Please contact me if you need assistance.
-- 
660394: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=660394
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.133389698527416.transcr...@bugs.debian.org

Bug#660394: Screen goes blank @30 seconds into boot

[Jonathan Nieder]

tags 660394 = upstream
forwarded 660394 https://bugs.freedesktop.org/48435
quit

jheaton5 wrote:

> See Bug No. 48435

Thanks much.  Hopefully someone upstream will have ideas for tracking
this down further.



-- 
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/20120408145616.GC2631@burratino

Bug#660394: Screen goes blank @30 seconds into boot

[jheaton5]

On Sun, 2012-04-08 at 02:43 +0100, Ben Hutchings wrote:
> On Sat, 2012-04-07 at 18:04 -0400, jheaton5 wrote:
> > On Sat, 2012-04-07 at 21:15 +0100, Ben Hutchings wrote:
> > > On Sat, 2012-04-07 at 13:53 -0500, Jonathan Nieder wrote:
> > > > Ben Hutchings wrote:
> > > > 
> > > > > commit 7885d2052bd94395e337709cfba093a41f273ff1
> > > > > Author: Jesse Barnes 
> > > > > Date:   Thu Jan 12 14:51:17 2012 -0800
> > > > >
> > > > > drm/i915: mask transcoder select bits before setting them on LVDS
> > > > >
> > > > > which was included in Linux 3.3.
> > > > >
> > > > > I'll apply it and submit it for inclusion in 3.2.y.
> > > > 
> > > > Thanks.  Note that Joel tested that patch and it did not fix his
> > > > problem ().
> > > 
> > > Oops, OK.
> > > 
> > > Both Joel and "Wearenotalone" have Sandybridge integrated graphics
> > > processors, though they are D (desktop) and M (mobile) variants
> > > respectively and there may well be significant differences in the
> > > display connections as well.
> > > 
> > > There seems to have been some refactoring of i915 display output setup
> > > in Linux 3.2 and subsequent fixes in 3.3.  Joel, can you test the
> > > package of Linux 3.3 from experimental?
> > > 
> > > Ben.
> > > 
> > I installed Linux 3.3 and xserver-xorg-video-intel 2.18.0-2 yesterday.
> > The issue is not fixed.  However, I can see the video flashing on and
> > off with a bright light aimed at the screen. Eventually, usually after a
> > few hours, the screen turns on and stays on.  This condition is not
> > stable because running xrandr or  F1 turn the video off.
> 
> As Jonathan said before:
> 
> > Please report this on http://bugs.freedesktop.org/ product DRI,
> > component DRM/Intel following instructions from
> > 
> >  http://intellinuxgraphics.org/how_to_report_bug.html
> > 
> > and let us know the bug number so we can track it.
> 
> Ben.
> 

See Bug No. 48435

Joel




-- 
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/1333894204.2204.0.ca...@debian.hsd1.ga.comcast.net.

Bug#668036: Please enable touchscreen input drivers on loongson2f

[Christoph Egger]

Package: linux-2.6
Version: 3.2.14-1
Severity: wishlist

Hi!

  Debugging why my touchscreen won't work when connected to my
loongson-2f box but definitely working on amd64 I noticed the drivers
are missing from loongson-2f builds. Please consider enabling these
modules in distro-kernel builds

Regards

Christoph

-- System Information:
Debian Release: 6.0.4
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'unstable'), (1, 'experimental')
Architecture: mipsel (mips64)

Kernel: Linux 3.2.0-0.bpo.1-loongson-2f
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20120408131306.21314.95682.report...@oteiza.siccegge.de

Bug#644279: Nak ed busty wife wants dat es!6

[CHAD PAUL]

Nak ed busty wife wants dat es!6

https://docs.google.com/document/d/1PKL2ngybxMrPXryrQrPeXz97PQHJDuvNBHJl3Ah3Mf0/edit












-
To st0 p re6ceiving messa6ges from us please s6end an email to oeqz0215 [at] 
gmail [dot] com with the word REM0VE in the su bject 6liine.



--
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/20120408073630.23...@web001.nyc1.bluetie.com

Re: ARM: backporting dreamplug patches for Wheezy

[Martin Michlmayr]

* Ian Campbell  [2012-04-08 11:10]:
> These Dreamplug patches add DT support for kirkwood in a way which is
> designed not to interfere with existing non-DT platforms and more
> generally upstream has done things in a way that FDT and ATAG platforms
> can safely be supported using the same kernel image.

I'm no longer on the kernel team but fwiw I'm all in favour of these
patches going into the Debian kernel for wheezy (if we can figure out
a solution for the ABI change).

-- 
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/20120408102526.ga28...@jirafa.cyrius.com

Bug#645547: [i915] intermittent memory corruption after hibernation unless i915.modeset=0

[Kjö Hansi Glaz]

On Fri, Mar 30, 2012 at 12:44:52PM -0500, Jonathan Nieder wrote:
> tags 645547 + upstream patch
> quit
> 
> Kjö Hansi Glaz wrote:
> 
> > I tried appending `i915.modeset=0` and thus falling back to vesa makes
> > hibremation/resume working.
> >
> > I also tested 3.2.0-rc4 from experimetal (with modesetting enabled) and
> > experience the same kind of problems that with 3.1.0. Sometimes
> > processes segfault, sometimes the whole kernel hangs.
> 
> Thanks again for tracking this down.  Please test the attached patch
> against a 3.2.y kernel, such as the one from sid. 

>From my experience of a dozen of hibernate/resume cycles, this patch works.

Thanks for following this bug!



--
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/20120408102752.gk13...@a4nancy.net.eu.org