Re: powerpcspe kernel-wedge configuration

2013-06-05 Thread Roland Stigge
On 06/05/2013 03:13 AM, Ben Hutchings wrote: linux/3.9.4-1 again failed to build again on powerpcspe, this time using the same kernel-wedge configuration as for powerpc. It's missing a few expected modules, which look Mac-specific and presumably have correctly been disabled for this

RE: Uploading linux (3.9.4-1)

2013-06-05 Thread Bandi,Sarveshwar
Ben, When you pick up 3.9 for Jessie, will the drivers code base also be from 3.9 kernel source? Thanks, Sarvesh -Original Message- From: Ben Hutchings [mailto:b...@decadent.org.uk] Sent: Friday, May 31, 2013 10:38 PM To: debian-kernel@lists.debian.org Subject: Re: Uploading linux

Processed: Re: lxc vms should by default not be able to read the kernel log facility

2013-06-05 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: reassign 702494 linux Bug #702494 [lxc] malformed messages/gibberish in logs Bug reassigned from package 'lxc' to 'linux'. Ignoring request to alter found versions of bug #702494 to the same values previously set Ignoring request to alter fixed

Bug#711187: linux-image-3.2.0-4-amd64: kernel should not rename mountpoint if nfs server is dead/unreachable

2013-06-05 Thread Florian Lohoff
Package: src:linux Version: 3.2.41-2 Severity: normal Dear Maintainer, * What led up to the situation? nfs mount via fstab, move notebook to a different network so nfs server gets unrachable. * What exactly did you do (or not do) that was effective (or ineffective)? *

Bug#708344: [Xen-users] Serial Passthrough broken in Debian Wheezy?

2013-06-05 Thread Jonas Meurer
Am 2013-06-04 19:45, schrieb Ian Campbell: On Tue, 2013-06-04 at 17:32 +0200, Jonas Meurer wrote: Just gave Linux 3.9-1-amd64 from Debian/sid a try. The issue is reproducible with this DomU kernel. Could you post dmesg, /proc/ioports and /proc/interrupts from this kernel please? Sure, here

Bug#708344: [Xen-users] Serial Passthrough broken in Debian Wheezy?

2013-06-05 Thread Ian Campbell
On Wed, 2013-06-05 at 11:47 +0200, Jonas Meurer wrote: Am 2013-06-04 19:45, schrieb Ian Campbell: On Tue, 2013-06-04 at 17:32 +0200, Jonas Meurer wrote: Just gave Linux 3.9-1-amd64 from Debian/sid a try. The issue is reproducible with this DomU kernel. Could you post dmesg,

Bug#707257: linux-image-3.8-1-686-pae: KVM crashes with entry failed, hardware error 0x80000021

2013-06-05 Thread Stefan Pietsch
On 19.05.2013 14:32, Gleb Natapov wrote: On Sun, May 19, 2013 at 02:00:31AM +0100, Ben Hutchings wrote: Dear KVM maintainers, it appears that there is a gap in x86 emulation, at least on a 32-bit host. Stefan found this when running GRML, a live distribution which can be downloaded from:

Bug#711202: linux-image-3.2.0-4-amd64: e1000e Detected Hardware Unit Hang only on kernel 3.2

2013-06-05 Thread Jose M Calhariz
Package: src:linux Version: 3.2.41-2+deb7u2 Severity: normal Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? The openafs fileserver, under normal workload, the kernel says: Jun 4 13:33:25 tania kernel: e1000e

Bug#707257: linux-image-3.8-1-686-pae: KVM crashes with entry failed, hardware error 0x80000021

2013-06-05 Thread Gleb Natapov
On Wed, Jun 05, 2013 at 01:57:25PM +0200, Stefan Pietsch wrote: On 19.05.2013 14:32, Gleb Natapov wrote: On Sun, May 19, 2013 at 02:00:31AM +0100, Ben Hutchings wrote: Dear KVM maintainers, it appears that there is a gap in x86 emulation, at least on a 32-bit host. Stefan found this when

Bug#707257: linux-image-3.8-1-686-pae: KVM crashes with entry failed, hardware error 0x80000021

2013-06-05 Thread Stefan Pietsch
On 05.06.2013 14:10, Gleb Natapov wrote: On Wed, Jun 05, 2013 at 01:57:25PM +0200, Stefan Pietsch wrote: On 19.05.2013 14:32, Gleb Natapov wrote: On Sun, May 19, 2013 at 02:00:31AM +0100, Ben Hutchings wrote: Dear KVM maintainers, it appears that there is a gap in x86 emulation, at least on a

Re: Uploading linux (3.9.4-1)

2013-06-05 Thread Ben Hutchings
On Wed, 2013-06-05 at 07:38 +, Bandi,Sarveshwar wrote: Ben, When you pick up 3.9 for Jessie, will the drivers code base also be from 3.9 kernel source? I think you misunderstand. This is not a decision about what to release (it's much too early for that). New kernel versions

Bug#604480: marked as done (linux-2.6: CVE-2010-4072 ff.)

2013-06-05 Thread Debian Bug Tracking System
Your message dated Wed, 5 Jun 2013 18:09:07 +0200 with message-id 20130605160906.ga11...@inutil.org and subject line Re: linux-2.6: CVE-2010-4072 ff. has caused the Debian Bug report #604480, regarding linux-2.6: CVE-2010-4072 ff. to be marked as done. This means that you claim that the problem

Bug#569135: marked as done (xserver-xorg-video-intel: corruption on external VGA display)

2013-06-05 Thread Debian Bug Tracking System
Your message dated Wed, 5 Jun 2013 19:01:18 +0200 with message-id 20130605170117.gc14...@inutil.org and subject line Re: problem gone away by linux v2.6.36-rc3 has caused the Debian Bug report #569135, regarding xserver-xorg-video-intel: corruption on external VGA display to be marked as done.

Bug#573243: marked as done (Front Mic Boost mixer control missing on 2.6.33)

2013-06-05 Thread Debian Bug Tracking System
Your message dated Wed, 5 Jun 2013 19:00:58 +0200 with message-id 20130605170058.ga14...@inutil.org and subject line Re: Bug#573243: Front Mic Boost mixer control missing on 2.6.33 has caused the Debian Bug report #573243, regarding Front Mic Boost mixer control missing on 2.6.33 to be marked as

Bug#579332: marked as done (linux-image-2.6.32-3-686: module sn9c102 over gspca_sonixb)

2013-06-05 Thread Debian Bug Tracking System
Your message dated Wed, 5 Jun 2013 19:12:17 +0200 with message-id 20130605171217.ga15...@inutil.org and subject line Re: Bug#579332: linux-image-2.6.32-3-686: module sn9c102 over gspca_sonixb has caused the Debian Bug report #579332, regarding linux-image-2.6.32-3-686: module sn9c102 over

Bug#579333: marked as done (linux-image-2.6.32-3-686: module sn9c102 over gspca_sonixb)

2013-06-05 Thread Debian Bug Tracking System
Your message dated Wed, 5 Jun 2013 19:12:17 +0200 with message-id 20130605171217.ga15...@inutil.org and subject line Re: Bug#579332: linux-image-2.6.32-3-686: module sn9c102 over gspca_sonixb has caused the Debian Bug report #579332, regarding linux-image-2.6.32-3-686: module sn9c102 over

getting allwinner SoC support upstream (was Re: Uploading linux (3.9.4-1))

2013-06-05 Thread Luke Kenneth Casson Leighton
On Fri, May 31, 2013 at 3:52 AM, Ben Hutchings b...@decadent.org.uk wrote: The 3.8.y branch is over, so I think we have to move to 3.9, ready or not. I merged the work in progress from trunk to sid and am going through the config changes at the moment. I'm rather disappointed that nothing

Re: getting allwinner SoC support upstream (was Re: Uploading linux (3.9.4-1))

2013-06-05 Thread Adam D. Barratt
[non-debian lists dropped] On Wed, 2013-06-05 at 20:46 +0100, Luke Kenneth Casson Leighton wrote: what's the point of mentioning this? well, the point is: the expectation of the linux kernel developers is that Everyone Must Convert To DeviceTree. [...] thoughts and discussion appreciated.

Re: getting allwinner SoC support upstream (was Re: Uploading linux (3.9.4-1))

2013-06-05 Thread jonsm...@gmail.com
On Wed, Jun 5, 2013 at 3:46 PM, Luke Kenneth Casson Leighton l...@lkcl.net wrote: On Fri, May 31, 2013 at 3:52 AM, Ben Hutchings b...@decadent.org.uk wrote: The 3.8.y branch is over, so I think we have to move to 3.9, ready or not. I merged the work in progress from trunk to sid and am

Re: getting allwinner SoC support upstream (was Re: Uploading linux (3.9.4-1))

2013-06-05 Thread jonsm...@gmail.com
On Wed, Jun 5, 2013 at 3:46 PM, Luke Kenneth Casson Leighton l...@lkcl.netwrote: On Fri, May 31, 2013 at 3:52 AM, Ben Hutchings b...@decadent.org.uk wrote: The 3.8.y branch is over, so I think we have to move to 3.9, ready or not. I merged the work in progress from trunk to sid and am

Re: getting allwinner SoC support upstream (was Re: Uploading linux (3.9.4-1))

2013-06-05 Thread Luke Kenneth Casson Leighton
[i've just received word, please remove debian-release from discussions!] On Wed, Jun 5, 2013 at 9:46 PM, jonsm...@gmail.com jonsm...@gmail.com wrote: Why don't you try converting the sunxi code over to device tree? ok. perhaps i wasn't clear. whatever is proposed has to be be acceptable to

Re: getting allwinner SoC support upstream (was Re: Uploading linux (3.9.4-1))

2013-06-05 Thread Luke Kenneth Casson Leighton
[ please remove debian-release from future replies! my mistake - please don't propagate it, thanks ] On Wed, Jun 5, 2013 at 10:00 PM, Stephen Warren swar...@wwwdotorg.org wrote: On 06/05/2013 02:46 PM, jonsm...@gmail.com wrote: On Wed, Jun 5, 2013 at 3:46 PM, Luke Kenneth Casson Leighton

Re: getting allwinner SoC support upstream (was Re: Uploading linux (3.9.4-1))

2013-06-05 Thread Stephen Warren
On 06/05/2013 02:46 PM, jonsm...@gmail.com wrote: On Wed, Jun 5, 2013 at 3:46 PM, Luke Kenneth Casson Leighton l...@lkcl.net mailto:l...@lkcl.net wrote: ... the detect line, which is the write-protect line, to setting the DRAM clock timings, saying which kernel driver must be loaded to

Re: getting allwinner SoC support upstream (was Re: Uploading linux (3.9.4-1))

2013-06-05 Thread Russell King - ARM Linux
On Wed, Jun 05, 2013 at 03:00:13PM -0600, Stephen Warren wrote: 2) Having U-Boot itself read a DT and configure itself, just like the kernel does. This is relatively new, and only supported by a few boards (all Tegra to some extent, and a couple each Samsung Exynos and Xilinx boards). I

Re: getting allwinner SoC support upstream (was Re: Uploading linux (3.9.4-1))

2013-06-05 Thread Lennart Sorensen
On Wed, Jun 05, 2013 at 10:24:15PM +0100, Luke Kenneth Casson Leighton wrote: https://github.com/linux-sunxi/u-boot-sunxi And Then Some, stephen. there are two versions of u-boot being used: one is the community-assembled [GPL-compliant] one, and the other includes a

Re: getting allwinner SoC support upstream (was Re: Uploading linux (3.9.4-1))

2013-06-05 Thread Luke Kenneth Casson Leighton
[ please do try to remove debian-release from replies - my mistake please try not to propagage it, even though it may be too late!] On Wed, Jun 5, 2013 at 10:16 PM, Russell King - ARM Linux li...@arm.linux.org.uk wrote: eyy, allo russell, long time since we last spoke, which was eek around 2004

Re: getting allwinner SoC support upstream (was Re: Uploading linux (3.9.4-1))

2013-06-05 Thread Tomasz Figa
Hi Luke, On Wednesday 05 of June 2013 22:15:08 Luke Kenneth Casson Leighton wrote: [i've just received word, please remove debian-release from discussions!] On Wed, Jun 5, 2013 at 9:46 PM, jonsm...@gmail.com jonsm...@gmail.com wrote: Why don't you try converting the sunxi code over to

Bug#569598: marked as done (XFS corruption when using loop device)

2013-06-05 Thread Debian Bug Tracking System
Your message dated Thu, 6 Jun 2013 00:11:53 +0200 with message-id 20130605221153.GA5444@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #569598, regarding XFS corruption when using loop device to be marked as done. This means that you claim that the problem has

Bug#568728: marked as done (linux-image-2.6.32-trunk-amd64: sound problem alsa does not work)

2013-06-05 Thread Debian Bug Tracking System
Your message dated Thu, 6 Jun 2013 00:11:53 +0200 with message-id 20130605221153.GA5444@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #568728, regarding linux-image-2.6.32-trunk-amd64: sound problem alsa does not work to be marked as done. This means that you

Bug#570517: marked as done (base: No resume after suspend to ram)

2013-06-05 Thread Debian Bug Tracking System
Your message dated Thu, 6 Jun 2013 00:11:53 +0200 with message-id 20130605221153.GA5444@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #570517, regarding base: No resume after suspend to ram to be marked as done. This means that you claim that the problem has been

Bug#568806: marked as done (linux-image-2.6.32-trunk-amd64: Internal mic of dell m1330 stopped working with 2.6.32 kernel)

2013-06-05 Thread Debian Bug Tracking System
Your message dated Thu, 6 Jun 2013 00:11:53 +0200 with message-id 20130605221153.GA5444@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #568806, regarding linux-image-2.6.32-trunk-amd64: Internal mic of dell m1330 stopped working with 2.6.32 kernel to be marked as

Re: [Arm-netbook] getting allwinner SoC support upstream (was Re: Uploading linux (3.9.4-1))

2013-06-05 Thread Henrik Nordström
ons 2013-06-05 klockan 22:24 +0100 skrev Luke Kenneth Casson Leighton: And Then Some, stephen. there are two versions of u-boot being used: one is the community-assembled [GPL-compliant] one, and the other includes a [as-of-a-few-days-ago-but-no-longer, yay!] formerly-GPL-violating one from

Bug#571253: marked as done (uvcvideo mixer issues (with snd_mixer_oss))

2013-06-05 Thread Debian Bug Tracking System
Your message dated Thu, 6 Jun 2013 00:12:28 +0200 with message-id 20130605221227.GB5444@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #571253, regarding uvcvideo mixer issues (with snd_mixer_oss) to be marked as done. This means that you claim that the problem

Bug#573900: marked as done (base: startup failed)

2013-06-05 Thread Debian Bug Tracking System
Your message dated Thu, 6 Jun 2013 00:12:58 +0200 with message-id 20130605221258.GC5444@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #573900, regarding base: startup failed to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#573145: marked as done (dd if=/dev/sr0 does not wait until media is loaded and ready)

2013-06-05 Thread Debian Bug Tracking System
Your message dated Thu, 6 Jun 2013 00:12:28 +0200 with message-id 20130605221227.GB5444@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #573145, regarding dd if=/dev/sr0 does not wait until media is loaded and ready to be marked as done. This means that you claim

Bug#574555: marked as done (linux-image-2.6.32-3-amd64: 2.6.32 kernel oops: Pid: 1700, comm: irq/21-b43 Not tainted 2.6.32-3-amd64)

2013-06-05 Thread Debian Bug Tracking System
Your message dated Thu, 6 Jun 2013 00:12:58 +0200 with message-id 20130605221258.GC5444@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #574555, regarding linux-image-2.6.32-3-amd64: 2.6.32 kernel oops: Pid: 1700, comm: irq/21-b43 Not tainted 2.6.32-3-amd64 to be

Bug#571257: marked as done (ath5k and athros wireless fails to work since last kernel update)

2013-06-05 Thread Debian Bug Tracking System
Your message dated Thu, 6 Jun 2013 00:12:28 +0200 with message-id 20130605221227.GB5444@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #571257, regarding ath5k and athros wireless fails to work since last kernel update to be marked as done. This means that you

Bug#571085: marked as done (no write access in /home reiserfs (encrypted) 2.6.32-2-686)

2013-06-05 Thread Debian Bug Tracking System
Your message dated Thu, 6 Jun 2013 00:11:53 +0200 with message-id 20130605221153.GA5444@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #571085, regarding no write access in /home reiserfs (encrypted) 2.6.32-2-686 to be marked as done. This means that you claim

Bug#572125: marked as done (linux-image-2.6.32-bpo.2-amd64: btusb error message (failed to resubmit) after suspend/hibernate or on battery with usb auto-suspend)

2013-06-05 Thread Debian Bug Tracking System
Your message dated Thu, 6 Jun 2013 00:12:28 +0200 with message-id 20130605221227.GB5444@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #572125, regarding linux-image-2.6.32-bpo.2-amd64: btusb error message (failed to resubmit) after suspend/hibernate or on battery

Bug#572535: marked as done (btrfs-tools: Wrong size shown of btrfs partition after migrating from ext4)

2013-06-05 Thread Debian Bug Tracking System
Your message dated Thu, 6 Jun 2013 00:12:28 +0200 with message-id 20130605221227.GB5444@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #572535, regarding btrfs-tools: Wrong size shown of btrfs partition after migrating from ext4 to be marked as done. This means

Bug#572754: marked as done (linux-image-2.6.33-2-amd64: Xorg / virtual console switching glitch with KMS on i915, Radeon X800GT, Radeon HD 4650)

2013-06-05 Thread Debian Bug Tracking System
Your message dated Thu, 6 Jun 2013 00:12:28 +0200 with message-id 20130605221227.GB5444@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #572754, regarding linux-image-2.6.33-2-amd64: Xorg / virtual console switching glitch with KMS on i915, Radeon X800GT, Radeon HD

Bug#571088: marked as done (linux-image-2.6-amd64: sporadic kernel warning in net/mac80211/rx.c)

2013-06-05 Thread Debian Bug Tracking System
Your message dated Thu, 6 Jun 2013 00:12:28 +0200 with message-id 20130605221227.GB5444@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #571088, regarding linux-image-2.6-amd64: sporadic kernel warning in net/mac80211/rx.c to be marked as done. This means that you

Bug#578131: marked as done ([linux-2.6] Copying big files to pendrive is deadly slow)

2013-06-05 Thread Debian Bug Tracking System
Your message dated Thu, 6 Jun 2013 00:13:51 +0200 with message-id 20130605221351.GE5444@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #578131, regarding [linux-2.6] Copying big files to pendrive is deadly slow to be marked as done. This means that you claim that

Bug#576862: marked as done (linux-image-2.6.26-2-686)

2013-06-05 Thread Debian Bug Tracking System
Your message dated Thu, 6 Jun 2013 00:13:24 +0200 with message-id 20130605221323.GD5444@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #576862, regarding linux-image-2.6.26-2-686 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#576408: marked as done (linux-image-2.6.32-4-amd64: ACPI conflict)

2013-06-05 Thread Debian Bug Tracking System
Your message dated Thu, 6 Jun 2013 00:13:24 +0200 with message-id 20130605221323.GD5444@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #576408, regarding linux-image-2.6.32-4-amd64: ACPI conflict to be marked as done. This means that you claim that the problem has

Bug#575175: marked as done (pm-utils: fails to resume when lid is closed)

2013-06-05 Thread Debian Bug Tracking System
Your message dated Thu, 6 Jun 2013 00:12:58 +0200 with message-id 20130605221258.GC5444@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #575175, regarding pm-utils: fails to resume when lid is closed to be marked as done. This means that you claim that the problem

Bug#576274: marked as done (infrequent, but persistent blank screens with Intel GMA900)

2013-06-05 Thread Debian Bug Tracking System
Your message dated Thu, 6 Jun 2013 00:13:24 +0200 with message-id 20130605221323.GD5444@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #576274, regarding infrequent, but persistent blank screens with Intel GMA900 to be marked as done. This means that you claim

Bug#574845: marked as done (linux-image-2.6.32-3-amd64: ehci_hcd causes immediate wakeup from s2d)

2013-06-05 Thread Debian Bug Tracking System
Your message dated Thu, 6 Jun 2013 00:12:58 +0200 with message-id 20130605221258.GC5444@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #574845, regarding linux-image-2.6.32-3-amd64: ehci_hcd causes immediate wakeup from s2d to be marked as done. This means that

Bug#577827: marked as done (Exception include/linux/dcache.h:324)

2013-06-05 Thread Debian Bug Tracking System
Your message dated Thu, 6 Jun 2013 00:13:24 +0200 with message-id 20130605221323.GD5444@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #577827, regarding Exception include/linux/dcache.h:324 to be marked as done. This means that you claim that the problem has been

Bug#577199: marked as done (linux-image-2.6.26-2-686: NULL pointer dereference at xfs:xfs_vn_getattr+0x16/0x1cf)

2013-06-05 Thread Debian Bug Tracking System
Your message dated Thu, 6 Jun 2013 00:13:24 +0200 with message-id 20130605221323.GD5444@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #577199, regarding linux-image-2.6.26-2-686: NULL pointer dereference at xfs:xfs_vn_getattr+0x16/0x1cf to be marked as done.

Bug#575648: marked as done (Lots of udevd --daemon running 100% CPU all the time.)

2013-06-05 Thread Debian Bug Tracking System
Your message dated Thu, 6 Jun 2013 00:13:24 +0200 with message-id 20130605221323.GD5444@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #575648, regarding Lots of udevd --daemon running 100% CPU all the time. to be marked as done. This means that you claim that the

Bug#574273: marked as done (linux-image-2.6.32-3-686: Hang on access to SD card)

2013-06-05 Thread Debian Bug Tracking System
Your message dated Thu, 6 Jun 2013 00:12:58 +0200 with message-id 20130605221258.GC5444@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #574273, regarding linux-image-2.6.32-3-686: Hang on access to SD card to be marked as done. This means that you claim that the

Bug#578063: marked as done (linux-image-2.6.32-3-686: module i915 does not create /dev/dri during boot. Creates it after reloading)

2013-06-05 Thread Debian Bug Tracking System
Your message dated Thu, 6 Jun 2013 00:13:24 +0200 with message-id 20130605221323.GD5444@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #578063, regarding linux-image-2.6.32-3-686: module i915 does not create /dev/dri during boot. Creates it after reloading to be

Bug#579862: marked as done (linux-image-2.6.32-trunk-686: Fatal DMA error in b43 broadcom kernel module)

2013-06-05 Thread Debian Bug Tracking System
Your message dated Thu, 6 Jun 2013 00:13:51 +0200 with message-id 20130605221351.GE5444@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #579862, regarding linux-image-2.6.32-trunk-686: Fatal DMA error in b43 broadcom kernel module to be marked as done. This means

Bug#579338: marked as done (linux-image-2.6.32-4-amd64: Warning hpet at boot time)

2013-06-05 Thread Debian Bug Tracking System
Your message dated Thu, 6 Jun 2013 00:13:51 +0200 with message-id 20130605221351.GE5444@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #579338, regarding linux-image-2.6.32-4-amd64: Warning hpet at boot time to be marked as done. This means that you claim that the

Bug#593792: marked as done ([Eee PC 1000HG, fuse] symptoms of memory corruption)

2013-06-05 Thread Debian Bug Tracking System
Your message dated Thu, 6 Jun 2013 00:13:51 +0200 with message-id 20130605221351.GE5444@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #580026, regarding [Eee PC 1000HG, fuse] symptoms of memory corruption to be marked as done. This means that you claim that the

Bug#578546: marked as done (linux-image-2.6.32-bpo.3-amd64: burning DVD+RW very slow with HL-DT-ST DVD+/-RW GSA-U20N)

2013-06-05 Thread Debian Bug Tracking System
Your message dated Thu, 6 Jun 2013 00:13:51 +0200 with message-id 20130605221351.GE5444@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #578546, regarding linux-image-2.6.32-bpo.3-amd64: burning DVD+RW very slow with HL-DT-ST DVD+/-RW GSA-U20N to be marked as done.

Bug#582487: marked as done (linux-image-2.6.32-5-686: bad page state)

2013-06-05 Thread Debian Bug Tracking System
Your message dated Thu, 6 Jun 2013 00:13:51 +0200 with message-id 20130605221351.GE5444@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #580026, regarding linux-image-2.6.32-5-686: bad page state to be marked as done. This means that you claim that the problem has

Bug#582088: marked as done ([Eee PC 1000HG, fuse] symptoms of memory corruption)

2013-06-05 Thread Debian Bug Tracking System
Your message dated Thu, 6 Jun 2013 00:13:51 +0200 with message-id 20130605221351.GE5444@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #580026, regarding [Eee PC 1000HG, fuse] symptoms of memory corruption to be marked as done. This means that you claim that the

Bug#585731: marked as done (linux-image-2.6.32-5-686: unable to handle kernel paging request at ff3a3b3a EIP: rb_insert_color+0x57/0xb5)

2013-06-05 Thread Debian Bug Tracking System
Your message dated Thu, 6 Jun 2013 00:13:51 +0200 with message-id 20130605221351.GE5444@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #580026, regarding linux-image-2.6.32-5-686: unable to handle kernel paging request at ff3a3b3a EIP: rb_insert_color+0x57/0xb5 to

Bug#593793: marked as done (BUG: unable to handle kernel NULL pointer dereference at 00000041 (__d_lookup+0xb5/0xd3))

2013-06-05 Thread Debian Bug Tracking System
Your message dated Thu, 6 Jun 2013 00:13:51 +0200 with message-id 20130605221351.GE5444@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #580026, regarding BUG: unable to handle kernel NULL pointer dereference at 0041 (__d_lookup+0xb5/0xd3) to be marked as done.

Bug#580074: marked as done (linux-image-2.6-686: acerhdf module: automatically start the fan control)

2013-06-05 Thread Debian Bug Tracking System
Your message dated Thu, 6 Jun 2013 00:13:51 +0200 with message-id 20130605221351.GE5444@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #580074, regarding linux-image-2.6-686: acerhdf module: automatically start the fan control to be marked as done. This means

Bug#580705: marked as done (linux-image-2.6.32-5-686: crash while playing movie)

2013-06-05 Thread Debian Bug Tracking System
Your message dated Thu, 6 Jun 2013 00:14:18 +0200 with message-id 20130605221418.GF5444@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #580705, regarding linux-image-2.6.32-5-686: crash while playing movie to be marked as done. This means that you claim that the

Bug#580149: marked as done (linux-image-2.6.32-trunk-amd64: usb - sata Sense not available)

2013-06-05 Thread Debian Bug Tracking System
Your message dated Thu, 6 Jun 2013 00:13:51 +0200 with message-id 20130605221351.GE5444@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #580149, regarding linux-image-2.6.32-trunk-amd64: usb - sata Sense not available to be marked as done. This means that you

Bug#580833: marked as done (initrd fails to recognize encrypted root fs)

2013-06-05 Thread Debian Bug Tracking System
Your message dated Thu, 6 Jun 2013 00:14:18 +0200 with message-id 20130605221418.GF5444@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #580833, regarding initrd fails to recognize encrypted root fs to be marked as done. This means that you claim that the problem

Bug#581438: marked as done (nfs-common: Permissions issue)

2013-06-05 Thread Debian Bug Tracking System
Your message dated Thu, 6 Jun 2013 00:14:18 +0200 with message-id 20130605221418.GF5444@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #581438, regarding nfs-common: Permissions issue to be marked as done. This means that you claim that the problem has been dealt

Bug#581842: marked as done (linux-image-2.6.32-3-686: No sound with Video TV card. Unsolved issue since 2 years !)

2013-06-05 Thread Debian Bug Tracking System
Your message dated Thu, 6 Jun 2013 00:14:18 +0200 with message-id 20130605221418.GF5444@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #581842, regarding linux-image-2.6.32-3-686: No sound with Video TV card. Unsolved issue since 2 years ! to be marked as done.

Bug#585900: marked as done (linux-image-2.6.32-5-amd64: NETDEV WATCHDOG: (tulip): transmit queue 0 timed out)

2013-06-05 Thread Debian Bug Tracking System
Your message dated Thu, 6 Jun 2013 00:15:18 +0200 with message-id 20130605221518.GH5444@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #585900, regarding linux-image-2.6.32-5-amd64: NETDEV WATCHDOG: (tulip): transmit queue 0 timed out to be marked as done. This

Bug#584230: marked as done (virtio_net: page allocation failure on memory pressure, disables network interface)

2013-06-05 Thread Debian Bug Tracking System
Your message dated Thu, 6 Jun 2013 00:14:58 +0200 with message-id 20130605221458.GG5444@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #584230, regarding virtio_net: page allocation failure on memory pressure, disables network interface to be marked as done. This

Bug#584591: marked as done (kernel panic linux-image-2.6.32-4-amd64 2.6.32-11)

2013-06-05 Thread Debian Bug Tracking System
Your message dated Thu, 6 Jun 2013 00:14:58 +0200 with message-id 20130605221458.GG5444@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #584591, regarding kernel panic linux-image-2.6.32-4-amd642.6.32-11 to be marked as done. This means that you claim that

Bug#584658: marked as done (linux-image-2.6.32-3-686-bigmem: gspca module return invalid v4l2_buffer's timestamp)

2013-06-05 Thread Debian Bug Tracking System
Your message dated Thu, 6 Jun 2013 00:14:58 +0200 with message-id 20130605221458.GG5444@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #584658, regarding linux-image-2.6.32-3-686-bigmem: gspca module return invalid v4l2_buffer's timestamp to be marked as done.

Bug#584762: marked as done (xfce4-power-manager: Not enough brightness levels)

2013-06-05 Thread Debian Bug Tracking System
Your message dated Thu, 6 Jun 2013 00:14:58 +0200 with message-id 20130605221458.GG5444@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #584762, regarding xfce4-power-manager: Not enough brightness levels to be marked as done. This means that you claim that the

Bug#584825: marked as done (linux-image-2.6.32-5-686: fan always runs at 100%)

2013-06-05 Thread Debian Bug Tracking System
Your message dated Thu, 6 Jun 2013 00:14:58 +0200 with message-id 20130605221458.GG5444@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #584825, regarding linux-image-2.6.32-5-686: fan always runs at 100% to be marked as done. This means that you claim that the

Bug#585962: marked as done (Hangs during boot unless radeon.modeset=0 is used)

2013-06-05 Thread Debian Bug Tracking System
Your message dated Thu, 6 Jun 2013 00:15:18 +0200 with message-id 20130605221518.GH5444@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #585962, regarding Hangs during boot unless radeon.modeset=0 is used to be marked as done. This means that you claim that the

Bug#585822: marked as done (xserver-xorg-video-radeon: radeon/KMS wrong monitor resolution due to mistakenly detected TV-out (S-video) for RV350 [Mobility Radeon 9600 M10] chipset (with workaround))

2013-06-05 Thread Debian Bug Tracking System
Your message dated Thu, 6 Jun 2013 00:15:18 +0200 with message-id 20130605221518.GH5444@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #585822, regarding xserver-xorg-video-radeon: radeon/KMS wrong monitor resolution due to mistakenly detected TV-out (S-video) for

Bug#585513: marked as done (Kernel oops related to ext3 on iSCSI usage)

2013-06-05 Thread Debian Bug Tracking System
Your message dated Thu, 6 Jun 2013 00:14:58 +0200 with message-id 20130605221458.GG5444@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #585513, regarding Kernel oops related to ext3 on iSCSI usage to be marked as done. This means that you claim that the problem

Re: getting allwinner SoC support upstream (was Re: Uploading linux (3.9.4-1))

2013-06-05 Thread Russell King - ARM Linux
On Wed, Jun 05, 2013 at 05:38:45PM -0400, Lennart Sorensen wrote: I haven't personally dealt with any nvidia arm devices, so I have no idea how those are turning out, nor have I looked much at the marvell ones yet (even though I have a cubox sitting on my desk I intend to play around with).

Re: getting allwinner SoC support upstream (was Re: Uploading linux (3.9.4-1))

2013-06-05 Thread Tomasz Figa
On Wednesday 05 of June 2013 16:48:27 jonsm...@gmail.com wrote: On Wed, Jun 5, 2013 at 3:46 PM, Luke Kenneth Casson Leighton l...@lkcl.net wrote: On Fri, May 31, 2013 at 3:52 AM, Ben Hutchings b...@decadent.org.uk wrote: The 3.8.y branch is over, so I think we have to move to 3.9, ready

Re: getting allwinner SoC support upstream (was Re: Uploading linux (3.9.4-1))

2013-06-05 Thread Luke Kenneth Casson Leighton
On Wed, Jun 5, 2013 at 10:52 PM, Tomasz Figa tomasz.f...@gmail.com wrote: Hi Luke, allo tomasz :) ok - much of what you say is duplicated by what russell said, so in effect the same reply is relevant, but there's been some cross-over. i'll summarise below and cut all but the key question

Re: [Arm-netbook] getting allwinner SoC support upstream (was Re: Uploading linux (3.9.4-1))

2013-06-05 Thread luke.leighton
On Wed, Jun 5, 2013 at 10:47 PM, Henrik Nordström hen...@henriknordstrom.net wrote: ons 2013-06-05 klockan 22:15 +0100 skrev Luke Kenneth Casson Leighton: what we do not want to happen is that they see upstream patches being submitted, they merge them into their internal tree (which to date

Re: getting allwinner SoC support upstream (was Re: Uploading linux (3.9.4-1))

2013-06-05 Thread Tomasz Figa
On Wednesday 05 of June 2013 22:16:37 Russell King - ARM Linux wrote: On Wed, Jun 05, 2013 at 03:00:13PM -0600, Stephen Warren wrote: 2) Having U-Boot itself read a DT and configure itself, just like the kernel does. This is relatively new, and only supported by a few boards (all Tegra to

Re: [Arm-netbook] getting allwinner SoC support upstream (was Re: Uploading linux (3.9.4-1))

2013-06-05 Thread Henrik Nordström
ons 2013-06-05 klockan 22:15 +0100 skrev Luke Kenneth Casson Leighton: what we do not want to happen is that they see upstream patches being submitted, they merge them into their internal tree (which to date has had zero upstream changes: they're currently only just getting round to doing 3.4

Re: getting allwinner SoC support upstream (was Re: Uploading linux (3.9.4-1))

2013-06-05 Thread Bastian Blank
On Wed, Jun 05, 2013 at 08:46:30PM +0100, Luke Kenneth Casson Leighton wrote: to begin to describe the problem in getting allwinner soc source code upstream is this: not only do we have the usual let's get it out the door as fast as possible learning curve of a very young, very new and

Re: getting allwinner SoC support upstream (was Re: Uploading linux (3.9.4-1))

2013-06-05 Thread Luke Kenneth Casson Leighton
[removing debian-release again - at their request] On Wed, Jun 5, 2013 at 11:11 PM, Tomasz Figa tomasz.f...@gmail.com wrote: Allwinner has just reinvented a wheel, without even considering the fact that it has been already invented. apologies, tomasz, but i believe i covered this issue in,

Re: [Arm-netbook] getting allwinner SoC support upstream (was Re: Uploading linux (3.9.4-1))

2013-06-05 Thread luke.leighton
On Wed, Jun 5, 2013 at 10:59 PM, Henrik Nordström hen...@henriknordstrom.net wrote: and then there's the boot0 and boot1 loaders, these *do* have no, these are not tiny. boot0 is 24KB to fit the initial embedded SRAM (not cache), but boot1 is on pair with u-boot in size and runs from

Re: [Arm-netbook] getting allwinner SoC support upstream (was Re: Uploading linux (3.9.4-1))

2013-06-05 Thread Stephen Warren
On 06/05/2013 03:59 PM, Henrik Nordström wrote: ons 2013-06-05 klockan 22:24 +0100 skrev Luke Kenneth Casson Leighton: ... so the point is: if anyone wishes me to propose to allwinner that they convert over to devicetree, or any other proposal which involves significant low-level changes to

Re: [Arm-netbook] getting allwinner SoC support upstream (was Re: Uploading linux (3.9.4-1))

2013-06-05 Thread jonsm...@gmail.com
On Wed, Jun 5, 2013 at 6:47 PM, luke.leighton luke.leigh...@gmail.com wrote: On Wed, Jun 5, 2013 at 10:59 PM, Henrik Nordström hen...@henriknordstrom.net wrote: and then there's the boot0 and boot1 loaders, these *do* have no, these are not tiny. boot0 is 24KB to fit the initial

Re: [Arm-netbook] getting allwinner SoC support upstream (was Re: Uploading linux (3.9.4-1))

2013-06-05 Thread Henrik Nordström
ons 2013-06-05 klockan 16:54 -0600 skrev Stephen Warren: 1) Put all the parameters in the U-Boot configuration header. This is normal. Yes, we do so today for U-Boot SPL. But this won't fit very well with the Allwinner ODM workflow where one binary image works on a wide range of board

Re: getting allwinner SoC support upstream (was Re: Uploading linux (3.9.4-1))

2013-06-05 Thread Tomasz Figa
On Wednesday 05 of June 2013 23:38:52 Luke Kenneth Casson Leighton wrote: On Wed, Jun 5, 2013 at 10:52 PM, Tomasz Figa tomasz.f...@gmail.com wrote: Hi Luke, allo tomasz :) ok - much of what you say is duplicated by what russell said, so in effect the same reply is relevant, but

Re: [Arm-netbook] getting allwinner SoC support upstream (was Re: Uploading linux (3.9.4-1))

2013-06-05 Thread luke.leighton
On Thu, Jun 6, 2013 at 12:07 AM, jonsm...@gmail.com jonsm...@gmail.com wrote: On Wed, Jun 5, 2013 at 6:47 PM, luke.leighton luke.leigh...@gmail.com wrote: On Wed, Jun 5, 2013 at 10:59 PM, Henrik Nordström hen...@henriknordstrom.net wrote: and then there's the boot0 and boot1 loaders,

Re: getting allwinner SoC support upstream (was Re: Uploading linux (3.9.4-1))

2013-06-05 Thread Luke Kenneth Casson Leighton
On Thu, Jun 6, 2013 at 12:27 AM, Tomasz Figa tomasz.f...@gmail.com wrote: their sheer overwhelming success provides us with mass-volume ultra-low cost hardware. to not make an effort to accommodate them would in this specific instance be a huge missed opportunity, OK, this is a large

Re: [Arm-netbook] getting allwinner SoC support upstream (was Re: Uploading linux (3.9.4-1))

2013-06-05 Thread jonsm...@gmail.com
On Wed, Jun 5, 2013 at 7:26 PM, luke.leighton luke.leigh...@gmail.com wrote: On Thu, Jun 6, 2013 at 12:07 AM, jonsm...@gmail.com jonsm...@gmail.com wrote: On Wed, Jun 5, 2013 at 6:47 PM, luke.leighton luke.leigh...@gmail.com wrote: On Wed, Jun 5, 2013 at 10:59 PM, Henrik Nordström

Re: [Arm-netbook] getting allwinner SoC support upstream (was Re: Uploading linux (3.9.4-1))

2013-06-05 Thread Henrik Nordström
tor 2013-06-06 klockan 00:26 +0100 skrev luke.leighton: no john - they've only added it to the multiplexed sections of the drivers which they themselves have written. such as drivers/usb/sun{N}i_usb/*.[ch], drivers/block/nand/sun{N}_i, arch/arm/mach-sun{N}i and so on. And a number of SPI

Re: [Arm-netbook] getting allwinner SoC support upstream (was Re: Uploading linux (3.9.4-1))

2013-06-05 Thread luke.leighton
On Thu, Jun 6, 2013 at 12:40 AM, Henrik Nordström hen...@henriknordstrom.net wrote: tor 2013-06-06 klockan 00:26 +0100 skrev luke.leighton: no john - they've only added it to the multiplexed sections of the drivers which they themselves have written. such as drivers/usb/sun{N}i_usb/*.[ch],

Re: [Arm-netbook] getting allwinner SoC support upstream (was Re: Uploading linux (3.9.4-1))

2013-06-05 Thread luke.leighton
On Thu, Jun 6, 2013 at 12:40 AM, jonsm...@gmail.com jonsm...@gmail.com wrote: I have a Cubieboard and I have a pca9532 on my desk. Now I want to attach this pca9532 to the Cubieboard so I wire them together on I2C. How is the Allwinner kernel going to load the driver for the pca9532? The

Re: [Arm-netbook] getting allwinner SoC support upstream (was Re: Uploading linux (3.9.4-1))

2013-06-05 Thread Tomasz Figa
On Thursday 06 of June 2013 00:54:02 luke.leighton wrote: On Thu, Jun 6, 2013 at 12:40 AM, Henrik Nordström hen...@henriknordstrom.net wrote: tor 2013-06-06 klockan 00:26 +0100 skrev luke.leighton: no john - they've only added it to the multiplexed sections of the drivers which they

Re: [Arm-netbook] getting allwinner SoC support upstream (was Re: Uploading linux (3.9.4-1))

2013-06-05 Thread Henrik Nordström
tor 2013-06-06 klockan 00:52 +0100 skrev luke.leighton: How is the Allwinner kernel going to load the driver for the pca9532? The mainline pca9532 driver does not understand fex so it can't read the necessary initialization data. jon: you're immediately outside of the target market for

Re: [Arm-netbook] getting allwinner SoC support upstream (was Re: Uploading linux (3.9.4-1))

2013-06-05 Thread Henrik Nordström
tor 2013-06-06 klockan 00:54 +0100 skrev luke.leighton: Not really the case. Actually the opposite. DT have this as well, and integrated in device probing. Allwinner need to hack every driver used to add their gpio requests to have pinmuxing triggered. augh. ok. solutions. what are

Re: [Arm-netbook] getting allwinner SoC support upstream (was Re: Uploading linux (3.9.4-1))

2013-06-05 Thread Henrik Nordström
ons 2013-06-05 klockan 23:20 +0100 skrev luke.leighton: ok: great. so we have something that i can potentially propose to them. now: what reason can i give that they should accept this? what's the biggest incentive for them, here, to make these changes? what would they gain? Mainly a

Re: getting allwinner SoC support upstream (was Re: Uploading linux (3.9.4-1))

2013-06-05 Thread Greg KH
On Wed, Jun 05, 2013 at 11:56:43PM +0100, Luke Kenneth Casson Leighton wrote: so there's a lot of factors which i believe the linux kernel developers are not aware of, and haven't taken into account, and to place blame onto the SoC vendors for not working with *you* when *you* haven't made an

  1   2   >