Bug#703142: compatibility with alx ?

2013-03-20 Thread Luis R. Rodriguez 
On Sun, Mar 17, 2013 at 2:43 PM, Ben Hutchings  wrote:
> [Re-sending to the correct list address.]
>
> On Sun, 2013-03-17 at 16:24 +0100, Camaleón wrote:
>> El 2013-03-17 a las 14:58 +, Ben Hutchings escribió:
>>
>> > On Sun, 2013-03-17 at 15:46 +0100, Camaleón wrote:
>>
>> (...)
>>
>> > > Using Debian's stock network driver is not an option for me (full report
>> > > available here²) so I have to try with the latests drivers but now that
>> > > "compat-drivers" are compiled the generated modules cannot be loaded.
>> > >
>> > > Is there any by-pass for this?
>> > >
>> > > ¹http://marc.info/?t=13635103432&r=1&w=2
>> > > ²http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=664767
>> >
>> > Talk to the compat-drivers developers.
>>
>> To be sincere, I don't think that's a user's role.
>>
>> I don't know what's going on with these drivers but if they are not
>> supported by Debian at all it would be better for all of us (plain
>> users and developers) to simply say it so to avoid wasting time and
>> resources.
>
> I would like to support them, in fact more than that I would like to
> integrate them into official packages.  But there is no way we can
> support an OOT module that defines symbols that we might need to add for
> our own backports.  As it is 'compat' will ironically cause
> incompatibility with Debian's own kernel upgrades.
>
> Compat developers: please add a prefix (not 'compat', that one's already
> taken!)

We have been using compat_ for a while now to prefix a lot of our
symbols without clashes for the 32-64 compat stuff, but sure -- we can
use something else to help with any theoretical issues. Surprised
Debian of all distributions would frankly have been affected given
RHEL / SUSE didn't, but its OK, lets deal with it.

> to all the symbols exported by the 'compat' module.  Just
> #define'ing the function/variable name before declaring them should
> avoid the need for any changes to the drivers using it.

How about backport_ ? Patches coming up.

  Luis


--
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/CAB=ne6upgjoxi7wwbma5xvhy8mmcf6kwqswxwvim6kijypv...@mail.gmail.com

Bug#703485: linux-image-3.8-trunk-amd64: Battery not detected on Dell Latitude E5530

2013-03-20 Thread Jean-Christophe Dubacq 
Package: src:linux
Version: 3.8.3-1~experimental.1
Severity: normal

Dear Maintainer,

While trying to resolve stability issues with the testing linux image,
I tried kernel 3.8 in experimental. I fully understand that this kernel
may not be used in production. However, when booting with this kernel,
the battery is not detected (and thus, laptop-detect thinks that it is
a desktop computer, which it is not). Of course, no /proc/acpi/BAT0 is
created, which makes system tools not work. I think the problem lies
in the kernel because of this.

The first significant difference that I see in the logs is:
-ACPI Error: [DCK9] Namespace lookup failure, AE_ALREADY_EXISTS 
(20121018/dswload2-330)
-ACPI Exception: AE_ALREADY_EXISTS, During name lookup/catalog 
(20121018/psloop-259)
-ACPI Error: Method parse/execution failed [\_SB_.PCI0.LPCB.LPTE.CLPS] (Node 
880215491c18), AE_ALREADY_EXISTS (20121018/psparse-537)
-ACPI Error: Method parse/execution failed [\_SB_.PCI0.LPCB.LPTE._STA] (Node 
880215491bf0), AE_ALREADY_EXISTS (20121018/psparse-537)
-ACPI Error: Method execution failed [\_SB_.PCI0.LPCB.LPTE._STA] (Node 
880215491bf0), AE_ALREADY_EXISTS (20121018/uteval-103)
-ACPI: Marking method CLPS as Serialized because of AE_ALREADY_EXISTS error
-parport_pc 00:0b: reported by Plug and Play ACPI
-ACPI: AC Adapter [AC] (off-line)
-ACPI Exception: AE_TIME, Returned by Handler for [EmbeddedControl] 
(20121018/evregion-501)
-ACPI Error: Method parse/execution failed [\_SB_.PCI0.LPCB.ECDV.ECR1] (Node 
88021548f650), AE_TIME (20121018/psparse-537)
-ACPI Error: Method parse/execution failed [\ECRB] (Node 88021548f4e8), 
AE_TIME (20121018/psparse-537)
-ACPI Error: Method parse/execution failed [\ECG5] (Node 88021548f380), 
AE_TIME (20121018/psparse-537)
-ACPI Error: Method parse/execution failed [\_SB_.AC__._PSR] (Node 
88021548fb00), AE_TIME (20121018/psparse-537)
-ACPI Exception: AE_TIME, Error reading AC Adapter state (20121018/ac-122)

while in 3.2 I get:

+ACPI: Battery Slot [BAT0] (battery present)
+ACPI: Battery Slot [BAT1] (battery absent)
+ACPI Exception: AE_TIME, Returned by Handler for [EmbeddedControl] 
(20110623/evregion-478)
+ACPI Error: Method parse/execution failed [\_SB_.PCI0.LPCB.ECDV.ECR1] (Node 
880215488650), AE_TIME (20110623/psparse-536)
+ACPI Error: Method parse/execution failed [\ECRB] (Node 8802154884e8), 
AE_TIME (20110623/psparse-536)
+ACPI Error: Method parse/execution failed [\ECG5] (Node 880215488380), 
AE_TIME (20110623/psparse-536)
+ACPI Error: Method parse/execution failed [\_SB_.AC__._PSR] (Node 
880215488b00), AE_TIME (20110623/psparse-536)
+ACPI Exception: AE_TIME, Error reading AC Adapter state (20110623/ac-118)


As this laptop is not used intensively right now, I am willing to do any tests 
one knowledgeable may advice me to do.

Sincerly,
-- Package-specific info:
** Version:
Linux version 3.8-trunk-amd64 (debian-kernel@lists.debian.org) (gcc version 
4.7.2 (Debian 4.7.2-5) ) #1 SMP Debian 3.8.3-1~experimental.1

** Command line:
BOOT_IMAGE=/boot/vmlinuz-3.8-trunk-amd64 
root=UUID=fe7f02bc-039b-4879-9aeb-10264d8241ef ro quiet

** Not tainted

** Kernel log:
[2.383747] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[2.394430] cfg80211: World regulatory domain updated:
[2.394433] cfg80211:   (start_freq - end_freq @ bandwidth), 
(max_antenna_gain, max_eirp)
[2.394435] cfg80211:   (2402000 KHz - 2472000 KHz @ 4 KHz), (300 mBi, 
2000 mBm)
[2.394437] cfg80211:   (2457000 KHz - 2482000 KHz @ 2 KHz), (300 mBi, 
2000 mBm)
[2.394438] cfg80211:   (2474000 KHz - 2494000 KHz @ 2 KHz), (300 mBi, 
2000 mBm)
[2.394440] cfg80211:   (517 KHz - 525 KHz @ 4 KHz), (300 mBi, 
2000 mBm)
[2.394441] cfg80211:   (5735000 KHz - 5835000 KHz @ 4 KHz), (300 mBi, 
2000 mBm)
[2.401158] parport_pc 00:0b: activated
[2.401164] parport_pc 00:0b: reported by Plug and Play ACPI
[2.401294] parport_pc 00:0b: disabled
[3.053757] fbcon: inteldrmfb (fb0) is primary device
[3.125972] ACPI: AC Adapter [AC] (off-line)
[3.821214] [drm] Enabling RC6 states: RC6 on, RC6p on, RC6pp off
[3.957614] Console: switching to colour frame buffer device 240x67
[3.970247] i915 :00:02.0: fb0: inteldrmfb frame buffer device
[3.970251] i915 :00:02.0: registered panic notifier
[4.108773] ACPI Exception: AE_TIME, Returned by Handler for 
[EmbeddedControl] (20121018/evregion-501)
[4.108788] ACPI Error: Method parse/execution failed 
[\_SB_.PCI0.LPCB.ECDV.ECR1] (Node 88021548f650), AE_TIME 
(20121018/psparse-537)
[4.108801] ACPI Error: Method parse/execution failed [\ECRB] (Node 
88021548f4e8), AE_TIME (20121018/psparse-537)
[4.108809] ACPI Error: Method parse/execution failed [\ECG5] (Node 
88021548f380), AE_TIME (20121018/psparse-537)
[4.108816] ACPI Error: Method parse/execution failed [\_SB_.AC__._PSR] 
(Node 88021548fb00), AE_TIME (20121018/psparse-537)
[

Bug#703271: linux-image-3.2.0-4-amd64: Fix brightness hotkeys on ASUS UX31A laptop

2013-03-20 Thread Vincent Blut 
Le mercredi 20 mars 2013 à 03:14 +, Ben Hutchings a écrit :
> On Sun, 2013-03-17 at 21:54 +0100, Vincent Blut wrote:
> > Package: src:linux
> > Version: 3.2.39-2
> > Severity: normal
> > Tags: upstream
> > 
> > Hi,
> > 
> > Since Linux 3.7, the brightness hotkeys work on this laptop. Initially I
> > thought that this support was added by a specific plateform driver
> > commit but after diving in git log it didn't make any sense about why these
> > hotkeys worked in 3.7 so I started to bisect in order to find the
> > culprit. Here it is:
> 
> Please apply this to stable branches earlier than 3.7.  It doesn't
> appear to depend on any other changes post-3.0.

Hi Ben,

As you can see in my bug report, I was using 3.2.40+ (your last longterm
release with this patch).

> 
> > >From d627b62ff8d4d36761adbcd90ff143d79c94ab22 Mon Sep 17 00:00:00 2001
> > From: Lekensteyn 
> > Date: Mon, 25 Jun 2012 22:36:24 +
> > Subject: i915: initialize CADL in opregion
> [...]
> > Well, after this result I was puzzled because it seemed to be a
> > Clevo specific issue but I decided to give it a try and effectively it
> > gave me the expected behavior, so please could you add it in the next
> > Wheezy upload?
> > 
> > Also this should probably be forwarded to sta...@vger.kernel.org with a
> > revised commit message stipulating that not only Clevo laptop are
> > affected, don't know if it is possible though.
> 
> Normally the original commit message is used unchanged.
> 

Ok

> Ben.
> 

Cheers,
Vincent


-- 
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/1363771124.3956.2.camel@lamella

Bug#703506: GMA500: higher resolutions than 800x600 don't work

2013-03-20 Thread Georg Sassen 
Package: src:linux
Version: 3.2.39-2
Severity: important

While the native resolution (1280x720) worked fine until kernel version
3.2.0.4-686-pae_3.2.35-2, I now only have 800x600 resolution in X11 and the 
initial framebuffer now on my Nokia Booklet 3G since the update.



-- Package-specific info:
** Version:
Linux version 3.2.0-4-686-pae (debian-kernel@lists.debian.org) (gcc version 
4.6.3 (Debian 4.6.3-15) ) #1 SMP Debian 3.2.39-2

** Command line:
BOOT_IMAGE=/vmlinuz-3.2.0-4-686-pae 
root=UUID=e696d69b-73d8-4f0b-a1d4-213431cabc39 ro quiet acpi_backlight=vendor 
acpi_osi=Linux mem=896mb

** Not tainted

** Kernel log:
[   17.911207] input: Lid Switch as 
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input1
[   17.911758] ACPI: Lid Switch [LID0]
[   17.912097] input: Power Button as 
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input2
[   17.912116] ACPI: Power Button [PWRB]
[   17.912385] input: Power Button as 
/devices/LNXSYSTM:00/LNXPWRBN:00/input/input3
[   17.912400] ACPI: Power Button [PWRF]
[   17.912417] ACPI Error: Could not enable PowerButton event 
(20110623/evxfevnt-199)
[   17.912432] ACPI Warning: Could not enable fixed event 0x2 
(20110623/evxface-198)
[   17.928274] button: probe of LNXPWRBN:00 failed with error -22
[   17.928499] ACPI: Requesting acpi_cpufreq
[   18.264702] ACPI: Battery Slot [BAT1] (battery present)
[   18.266011] ACPI: AC Adapter [ACAD] (on-line)
[   18.508392] input: PC Speaker as /devices/platform/pcspkr/input/input4
[   18.542437] ACPI: resource (null) [io  0x1180-0x11bf] conflicts with ACPI 
region GPI0 [io 0x1180-0x11bf]
[   18.542449] ACPI: If an ACPI driver is available for this device, you should 
use it instead of the native driver
[   18.542530] lpc_sch: probe of :00:1f.0 failed with error -16
[   18.918729] cfg80211: Calling CRDA to update world regulatory domain
[   19.084687] Linux media interface: v0.10
[   19.223155] Linux video capture interface: v2.00
[   19.242593] audit: name_count maxed, losing inode data: dev=00:06, inode=4215
[   19.242616] audit: name_count maxed, losing inode data: dev=00:06, inode=4215
[   19.242630] audit: name_count maxed, losing inode data: dev=00:06, inode=4215
[   19.242644] audit: name_count maxed, losing inode data: dev=00:06, inode=4202
[   19.242657] audit: name_count maxed, losing inode data: dev=00:06, inode=4220
[   19.242670] audit: name_count maxed, losing inode data: dev=00:06, inode=4220
[   19.242686] audit: name_count maxed, losing inode data: dev=00:06, inode=4220
[   19.242699] audit: name_count maxed, losing inode data: dev=00:06, inode=4220
[   19.242715] audit: name_count maxed, losing inode data: dev=00:06, inode=4202
[   19.242727] audit: name_count maxed, losing inode data: dev=00:06, inode=4225
[   19.242740] audit: name_count maxed, losing inode data: dev=00:06, inode=4225
[   19.242760] audit: name_count maxed, losing inode data: dev=00:06, inode=4225
[   19.242780] audit: name_count maxed, losing inode data: dev=00:06, inode=4225
[   19.242797] audit: name_count maxed, losing inode data: dev=00:06, inode=4202
[   19.243471] audit: name_count maxed, losing inode data: dev=00:06, inode=4230
[   19.243489] audit: name_count maxed, losing inode data: dev=00:06, inode=4230
[   19.243505] audit: name_count maxed, losing inode data: dev=00:06, inode=4230
[   19.243519] audit: name_count maxed, losing inode data: dev=00:06, inode=4230
[   19.256992] hso: 
/build/buildd-linux_3.2.39-2-i386-4VFKqr/linux-3.2.39/drivers/net/usb/hso.c: 
Option Wireless
[   19.301798] usbcore: registered new interface driver hso
[   19.303281] snd_hda_intel :00:1b.0: setting latency timer to 64
[   19.454684] uvcvideo: Found UVC 1.00 device USB 2.0 Camera (0c45:6409)
[   19.464050] input: USB 2.0 Camera as 
/devices/pci:00/:00:1d.7/usb1/1-6/1-6:1.0/input/input5
[   19.464361] usbcore: registered new interface driver uvcvideo
[   19.464369] USB Video Class driver (1.1.1)
[   19.488760] cfg80211: World regulatory domain updated:
[   19.488769] cfg80211: (start_freq - end_freq @ bandwidth), 
(max_antenna_gain, max_eirp)
[   19.488777] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (300 mBi, 
2000 mBm)
[   19.488784] cfg80211: (2457000 KHz - 2482000 KHz @ 2 KHz), (300 mBi, 
2000 mBm)
[   19.488791] cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (300 mBi, 
2000 mBm)
[   19.488798] cfg80211: (517 KHz - 525 KHz @ 4 KHz), (300 mBi, 
2000 mBm)
[   19.488805] cfg80211: (5735000 KHz - 5835000 KHz @ 4 KHz), (300 mBi, 
2000 mBm)
[   19.614307] ath9k :02:00.0: setting latency timer to 64
[   19.673982] psmouse serio1: synaptics: Touchpad model: 1, fw: 7.2, id: 
0x1e0b1, caps: 0xd04733/0xa4/0xa
[   19.764737] input: SynPS/2 Synaptics TouchPad as 
/devices/platform/i8042/serio1/input/input6
[   19.908892] HDMI status: Codec=1 Pin=3 Presence_Detect=0 ELD_Valid=0
[   19.909307] input: HDA Intel MID HDMI/DP,pcm=3 as 
/devices/pci:00/:00:1b.0/sound/ca

Bug#665000: Workaround for this bug

2013-03-20 Thread Thomas Goirand 
Hi,

On one of my server, I had the issue as well. I'm not sure if it's the
exact same one, but at least I fixed it.

What happened for me was that my KVM over IP was printing "No signal"
just right after the login prompt (eg: the rest of the boot process
seemed to not be bothered). Then I did:

dpkg-reconfigure grub-pc

and added:

radeon.modeset=0

to the linux command line. After doing that, then I was able to see my
text mode login prompt (which is the only thing I care for a server, I
will never care about X support...).

Though, I am wondering if the issue isn't simply that the kernel is
trying to set a mode which is higher than what my KVM over IP can
support. How can I choose such mode (which would be a better fix)? Do
you know Ben, maybe?

Hoping that this will help anyone searching for a quick and easy fix,

Thomas


-- 
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/5149c788.50...@debian.org

Bug#703142: compatibility with alx ?

2013-03-20 Thread Ben Hutchings 
On Wed, 2013-03-20 at 02:07 -0700, Luis R. Rodriguez wrote:
> On Sun, Mar 17, 2013 at 2:43 PM, Ben Hutchings  wrote:
> > [Re-sending to the correct list address.]
> >
> > On Sun, 2013-03-17 at 16:24 +0100, Camaleón wrote:
> >> El 2013-03-17 a las 14:58 +, Ben Hutchings escribió:
> >>
> >> > On Sun, 2013-03-17 at 15:46 +0100, Camaleón wrote:
> >>
> >> (...)
> >>
> >> > > Using Debian's stock network driver is not an option for me (full 
> >> > > report
> >> > > available here²) so I have to try with the latests drivers but now that
> >> > > "compat-drivers" are compiled the generated modules cannot be loaded.
> >> > >
> >> > > Is there any by-pass for this?
> >> > >
> >> > > ¹http://marc.info/?t=13635103432&r=1&w=2
> >> > > ²http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=664767
> >> >
> >> > Talk to the compat-drivers developers.
> >>
> >> To be sincere, I don't think that's a user's role.
> >>
> >> I don't know what's going on with these drivers but if they are not
> >> supported by Debian at all it would be better for all of us (plain
> >> users and developers) to simply say it so to avoid wasting time and
> >> resources.
> >
> > I would like to support them, in fact more than that I would like to
> > integrate them into official packages.  But there is no way we can
> > support an OOT module that defines symbols that we might need to add for
> > our own backports.  As it is 'compat' will ironically cause
> > incompatibility with Debian's own kernel upgrades.
> >
> > Compat developers: please add a prefix (not 'compat', that one's already
> > taken!)
> 
> We have been using compat_ for a while now to prefix a lot of our
> symbols without clashes for the 32-64 compat stuff, but sure -- we can
> use something else to help with any theoretical issues. Surprised
> Debian of all distributions would frankly have been affected given
> RHEL / SUSE didn't, but its OK, lets deal with it.

The conflict that just showed up in Debian involved the 'i2c_bit_algo'
symbol which had no symbol prefix in 'compat'.  We updated the in-tree
DRM drivers from 3.4.32 and started exporting the symbol from
i2c-algo-bit itself.

I hadn't noticed that you already used the 'compat_' prefix for some
exported symbols and I'm not aware of any current conflict with the
32-bit compatibility layer, but it seems plausible that it could happen
in future.

Ben.

> > to all the symbols exported by the 'compat' module.  Just
> > #define'ing the function/variable name before declaring them should
> > avoid the need for any changes to the drivers using it.
> 
> How about backport_ ? Patches coming up.
> 
>   Luis
> 

-- 
Ben Hutchings
The generation of random numbers is too important to be left to chance.
- Robert Coveyou


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

Uploading linux (3.2.41-1)

2013-03-20 Thread Ben Hutchings 
Since 3.2.39-2 went into testing, it's about time for another upload.
There are many important bug fixes pending (still more bugs to fix,
though; in particular some more DRM regressions showed up).

I'm intending to release 3.2.41 in a few minutes, and will try to
integrate this with the wheezy branch after that.

Current pending changes:

  * New upstream stable update:
http://www.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.2.40
- ext4: return ENOMEM if sb_getblk() fails
- ext4: fix possible use-after-free with AIO
- s390/kvm: Fix store status for ACRS/FPRS
- staging: comedi: disallow COMEDI_DEVCONFIG on non-board minors
- ext4: fix race in ext4_mb_add_n_trim()
- UBIFS: fix double free of ubifs_orphan objects
- hrtimer: Prevent hrtimer_enqueue_reprogram race
- nfsd: Fix memleak
- x86: Do not leak kernel page mapping locations
- USB: usb-storage: unusual_devs update for Super TOP SATA bridge
- posix-cpu-timers: Fix nanosleep task_struct leak
- NFSv4.1: Don't decode skipped layoutgets
- cgroup: fix exit() vs rmdir() race
- cpuset: fix cpuset_print_task_mems_allowed() vs rename() race
- ext4: fix xattr block allocation/release with bigalloc
- mm: fix pageblock bitmap allocation
- target: Add missing mapped_lun bounds checking during make_mappedlun
  setup
- b43: Increase number of RX DMA slots
- posix-timer: Don't call idr_find() with out-of-range ID
- fs: Fix possible use-after-free with AIO
- powerpc/kexec: Disable hard IRQ before kexec
- mmu_notifier_unregister NULL Pointer deref and multiple ->release()
  callouts
- tmpfs: fix use-after-free of mempolicy object (CVE-2013-1767)
- ocfs2: fix possible use-after-free with AIO
- ocfs2: fix ocfs2_init_security_and_acl() to initialize acl correctly
- ocfs2: ac->ac_allow_chain_relink=0 won't disable group relink
- idr: fix a subtle bug in idr_get_next()
- idr: make idr_get_next() good for rcu_read_lock()
- idr: fix top layer handling
- sysctl: fix null checking in bin_dn_node_address()
- nbd: fsync and kill block device on shutdown
- s390/timer: avoid overflow when programming clock comparator
  (regression in 3.2.38)
- xen-pciback: rate limit error messages from xen_pcibk_enable_msi{,x}()
  (CVE-2013-0231)
- xen-netback: correctly return errors from netbk_count_requests()
- xen-netback: cancel the credit timer when taking the vif down
- ipv6: use a stronger hash for tcp
- staging: comedi: ni_labpc: correct differential channel sequence for
  AI commands
- staging: comedi: ni_labpc: set up command4 register *after* command3
- vhost: fix length for cross region descriptor (CVE-2013-0311)

  [ Aurelien Jarno]
  * [mips,mipsel] Disable VGA_CONSOLE and ignore the corresponding ABI
change. It is completely broken on MIPS.
  * headers: Include Kbuild.platforms and Platform files in -common to
fix out-of-tree building on mips and mipsel.
  * [{mips,mipsel}/{4,5}kc-malta] Enable HW_RANDOM as module so that both
flavours have a consistent configuration.

  [ Ben Hutchings ]
  * [x86] ata_piix: reenable MS Virtual PC guests (fixes regression in
3.2.19-1)
  * test-patches: Clean up all previous test patches, whether or not they
were applied
  * test-patches: Add --fuzz option to allow testing patches that have fuzz
  * [x86] efi: Fix processor-specific memcpy() build error (Closes: #698581)
  * udeb: Add hid-topseed to input-modules (Closes: #702611)
  * [x86] drm/i915: Unconditionally initialise the interrupt workers,
thanks to Bjørn Mork (Closes: #692607)
  * efi: Ensure efivars is loaded on EFI systems (Closes: #703363)
- [x86] Use a platform device to trigger loading of efivars
- [ia64] Change EFI_VARS from module to built-in
  * kmsg_dump: Only dump kernel log in error cases (Closes: #703386)
- kexec: remove KMSG_DUMP_KEXEC
- kmsg_dump: don't run on non-error paths by default
  * [x86] i915: initialize CADL in opregion (Closes: #703271)

Security fixes in 3.2.41 cover at least:

CVE-2013-0914
(CVE-2013-1773 - fix was already backported for other reasons)
CVE-2013-1792
CVE-2013-1848
CVE-2013-1860
CVE-2012-5517
CVE-2013-2546/CVE-2013-2547/CVE-2013-2548

Ben.

-- 
Ben Hutchings
The generation of random numbers is too important to be left to chance.
- Robert Coveyou


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

Bug#665000: Workaround for this bug

2013-03-20 Thread Ben Hutchings 
On Wed, 2013-03-20 at 22:28 +0800, Thomas Goirand wrote:
> Hi,
> 
> On one of my server, I had the issue as well. I'm not sure if it's the
> exact same one, but at least I fixed it.
> 
> What happened for me was that my KVM over IP was printing "No signal"
> just right after the login prompt (eg: the rest of the boot process
> seemed to not be bothered).
>
> Then I did:
> 
> dpkg-reconfigure grub-pc
> 
> and added:
> 
> radeon.modeset=0
> 
> to the linux command line. After doing that, then I was able to see my
> text mode login prompt (which is the only thing I care for a server, I
> will never care about X support...).
>
> Though, I am wondering if the issue isn't simply that the kernel is
> trying to set a mode which is higher than what my KVM over IP can
> support.

Maybe.  KVMs may not provide reliable EDID information.

> How can I choose such mode (which would be a better fix)? Do
> you know Ben, maybe?
> 
> Hoping that this will help anyone searching for a quick and easy fix,

I don't know how to override the initial display mode.

Ben.

-- 
Ben Hutchings
The generation of random numbers is too important to be left to chance.
- Robert Coveyou


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

Bug#703522: linux-image-3.2.0-0.bpo.4-rt-686-pae: Upgrading to 3.2.39-2~bpo60+1 fails with error (file mising)

2013-03-20 Thread rpnpif 
Package: src:linux
Version: 3.2.35-2~bpo60+1
Severity: normal

I used linux-image-3.2.0-0.bpo.4-rt from a while.
I can not upgrading last updating with 3.2.39-2~bpo60+1.

Preparing to replace linux-image-3.2.0-0.bpo.4-rt-686-pae 3.2.35-2~bpo60+1 
(using .../linux-image-3.2.0-0.bpo.4-rt-686-pae_3.2.39-2~bpo60+1_i386.deb) ...
Unpacking replacement linux-image-3.2.0-0.bpo.4-rt-686-pae ...
Examining /etc/kernel/postrm.d .
run-parts: executing /etc/kernel/postrm.d/initramfs-tools 
3.2.0-0.bpo.4-rt-686-pae /boot/vmlinuz-3.2.0-0.bpo.4-rt-686-pae
run-parts: executing /etc/kernel/postrm.d/zz-extlinux 3.2.0-0.bpo.4-rt-686-pae 
/boot/vmlinuz-3.2.0-0.bpo.4-rt-686-pae
P: Checking for EXTLINUX directory... found.
P: Writing config for /boot/vmlinuz-3.2.0-0.bpo.4-rt-686-pae...
E: /usr/share/syslinux/themes/debian/extlinux: No such file or directory
run-parts: /etc/kernel/postrm.d/zz-extlinux exited with return code 1
Failed to process /etc/kernel/postrm.d at 
/var/lib/dpkg/info/linux-image-3.2.0-0.bpo.4-rt-686-pae.postrm line 212.
dpkg: warning: subprocess old post-removal script returned error exit status 1
dpkg - trying script from the new package instead ...
Examining /etc/kernel/postrm.d .
run-parts: executing /etc/kernel/postrm.d/initramfs-tools 
3.2.0-0.bpo.4-rt-686-pae /boot/vmlinuz-3.2.0-0.bpo.4-rt-686-pae
run-parts: executing /etc/kernel/postrm.d/zz-extlinux 3.2.0-0.bpo.4-rt-686-pae 
/boot/vmlinuz-3.2.0-0.bpo.4-rt-686-pae
P: Checking for EXTLINUX directory... found.
P: Writing config for /boot/vmlinuz-3.2.0-0.bpo.4-rt-686-pae...
E: /usr/share/syslinux/themes/debian/extlinux: No such file or directory
run-parts: /etc/kernel/postrm.d/zz-extlinux exited with return code 1
Failed to process /etc/kernel/postrm.d at /var/lib/dpkg/tmp.ci/postrm line 212.
dpkg: error processing 
/var/cache/apt/archives/linux-image-3.2.0-0.bpo.4-rt-686-pae_3.2.39-2~bpo60+1_i386.deb
 (--unpack):
 subprocess new post-removal script returned error exit status 1
configured to not write apport reports
  Examining /etc/kernel/postrm.d .
run-parts: executing /etc/kernel/postrm.d/initramfs-tools 
3.2.0-0.bpo.4-rt-686-pae /boot/vmlinuz-3.2.0-0.bpo.4-rt-686-pae
run-parts: executing /etc/kernel/postrm.d/zz-extlinux 3.2.0-0.bpo.4-rt-686-pae 
/boot/vmlinuz-3.2.0-0.bpo.4-rt-686-pae
P: Checking for EXTLINUX directory... found.
P: Writing config for /boot/vmlinuz-3.2.0-0.bpo.4-rt-686-pae...
E: /usr/share/syslinux/themes/debian/extlinux: No such file or directory
run-parts: /etc/kernel/postrm.d/zz-extlinux exited with return code 1
Failed to process /etc/kernel/postrm.d at /var/lib/dpkg/tmp.ci/postrm line 212.
dpkg: error while cleaning up:
 subprocess new post-removal script returned error exit status 1
Errors were encountered while processing:
 
/var/cache/apt/archives/linux-image-3.2.0-0.bpo.4-rt-686-pae_3.2.39-2~bpo60+1_i386.deb


-- Package-specific info:
** Version:
Linux version 3.2.0-0.bpo.4-rt-686-pae (debian-kernel@lists.debian.org) (gcc 
version 4.4.5 (Debian 4.4.5-8) ) #1 SMP PREEMPT RT Debian 3.2.35-2~bpo60+1

** Command line:
BOOT_IMAGE=/boot/vmlinuz-3.2.0-0.bpo.4-rt-686-pae 
root=UUID=310f205d-4dfc-4293-966c-8b952c4d258b ro quiet

** Tainted: O (4096)
 * Out-of-tree module has been loaded.

** Kernel log:
[7.043350] [TTM] Zone highmem: Available graphics memory: 516894 kiB.
[7.043355] [TTM] Initializing pool allocator.
[7.043474] [drm] radeon: 64M of VRAM memory ready
[7.043481] [drm] radeon: 64M of GTT memory ready.
[7.075549] radeon :01:00.0: WB disabled
[7.081625] [drm] Loading R100 Microcode
[7.589839] platform radeon_cp.0: firmware: agent loaded radeon/R100_cp.bin 
into memory
[7.591115] [drm] radeon: ring at 0xE0001000
[7.591142] [drm] ring test succeeded in 1 usecs
[7.591864] [drm] radeon: ib pool ready.
[7.594950] [drm] ib test succeeded in 0 usecs
[7.600431] [drm] Radeon Display Connectors
[7.600439] [drm] Connector 0:
[7.600443] [drm]   VGA
[7.600449] [drm]   DDC: 0x60 0x60 0x60 0x60 0x60 0x60 0x60 0x60
[7.600453] [drm]   Encoders:
[7.600457] [drm] CRT1: INTERNAL_DAC1
[7.600461] [drm] Connector 1:
[7.600464] [drm]   DVI-I
[7.600467] [drm]   HPD1
[7.600472] [drm]   DDC: 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64
[7.600476] [drm]   Encoders:
[7.600479] [drm] CRT2: INTERNAL_DAC2
[7.600483] [drm] DFP1: INTERNAL_TMDS1
[7.600486] [drm] Connector 2:
[7.600490] [drm]   S-video
[7.600493] [drm]   Encoders:
[7.600496] [drm] TV1: INTERNAL_DAC2
[7.751918] input: Logitech USB-PS/2 Optical Mouse as 
/devices/pci:00/:00:11.3/usb4/4-2/4-2:1.0/input/input5
[7.752658] generic-usb 0003:046D:C01B.0001: input,hidraw0: USB HID v1.10 
Mouse [Logitech USB-PS/2 Optical Mouse] on usb-:00:11.3-2/input0
[7.753465] usbcore: registered new interface driver usbhid
[7.753472] usbhid: USB HID core driver
[7.867858] [drm] fb mappable at 0xD004
[7.867866]

Bug#703522: linux-image-3.2.0-0.bpo.4-rt-686-pae: Upgrading to 3.2.39-2~bpo60+1 fails with error (file missing)

2013-03-20 Thread Alain Rpnpif 
This workaround fixes this issue :
sudo mkdir -p /usr/share/syslinux/themes/debian/extlinux

Note that extlinux and syslinux packages are uptodate from bpo.

-- 
Alain Rpnpif


-- 
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/20130320152249.309f3100...@chro.home

Bug#703142: compatibility with alx ?

2013-03-20 Thread Luis R. Rodriguez 
On Wed, Mar 20, 2013 at 7:41 AM, Ben Hutchings  wrote:
> On Wed, 2013-03-20 at 02:07 -0700, Luis R. Rodriguez wrote:
>> On Sun, Mar 17, 2013 at 2:43 PM, Ben Hutchings  wrote:
>> > [Re-sending to the correct list address.]
>> >
>> > On Sun, 2013-03-17 at 16:24 +0100, Camaleón wrote:
>> >> El 2013-03-17 a las 14:58 +, Ben Hutchings escribió:
>> >>
>> >> > On Sun, 2013-03-17 at 15:46 +0100, Camaleón wrote:
>> >>
>> >> (...)
>> >>
>> >> > > Using Debian's stock network driver is not an option for me (full 
>> >> > > report
>> >> > > available here²) so I have to try with the latests drivers but now 
>> >> > > that
>> >> > > "compat-drivers" are compiled the generated modules cannot be loaded.
>> >> > >
>> >> > > Is there any by-pass for this?
>> >> > >
>> >> > > ¹http://marc.info/?t=13635103432&r=1&w=2
>> >> > > ²http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=664767
>> >> >
>> >> > Talk to the compat-drivers developers.
>> >>
>> >> To be sincere, I don't think that's a user's role.
>> >>
>> >> I don't know what's going on with these drivers but if they are not
>> >> supported by Debian at all it would be better for all of us (plain
>> >> users and developers) to simply say it so to avoid wasting time and
>> >> resources.
>> >
>> > I would like to support them, in fact more than that I would like to
>> > integrate them into official packages.  But there is no way we can
>> > support an OOT module that defines symbols that we might need to add for
>> > our own backports.  As it is 'compat' will ironically cause
>> > incompatibility with Debian's own kernel upgrades.
>> >
>> > Compat developers: please add a prefix (not 'compat', that one's already
>> > taken!)
>>
>> We have been using compat_ for a while now to prefix a lot of our
>> symbols without clashes for the 32-64 compat stuff, but sure -- we can
>> use something else to help with any theoretical issues. Surprised
>> Debian of all distributions would frankly have been affected given
>> RHEL / SUSE didn't, but its OK, lets deal with it.
>
> The conflict that just showed up in Debian involved the 'i2c_bit_algo'
> symbol which had no symbol prefix in 'compat'.  We updated the in-tree
> DRM drivers from 3.4.32 and started exporting the symbol from
> i2c-algo-bit itself.
>
> I hadn't noticed that you already used the 'compat_' prefix for some
> exported symbols and I'm not aware of any current conflict with the
> 32-bit compatibility layer, but it seems plausible that it could happen
> in future.

Sure, let me know what you think of the proposed posted changes.

  Luis


--
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/CAB=ne6uz+rvfhyzuhswzatnkd9gaga0ekdqd+u9vxvm8fsv...@mail.gmail.com

Bug#703142: compatibility with alx ?

2013-03-20 Thread Ben Hutchings 
On Wed, 2013-03-20 at 08:50 -0700, Luis R. Rodriguez wrote:
> On Wed, Mar 20, 2013 at 7:41 AM, Ben Hutchings  wrote:
> > On Wed, 2013-03-20 at 02:07 -0700, Luis R. Rodriguez wrote:
[...]
> >> We have been using compat_ for a while now to prefix a lot of our
> >> symbols without clashes for the 32-64 compat stuff, but sure -- we can
> >> use something else to help with any theoretical issues. Surprised
> >> Debian of all distributions would frankly have been affected given
> >> RHEL / SUSE didn't, but its OK, lets deal with it.
> >
> > The conflict that just showed up in Debian involved the 'i2c_bit_algo'
> > symbol which had no symbol prefix in 'compat'.  We updated the in-tree
> > DRM drivers from 3.4.32 and started exporting the symbol from
> > i2c-algo-bit itself.
> >
> > I hadn't noticed that you already used the 'compat_' prefix for some
> > exported symbols and I'm not aware of any current conflict with the
> > 32-bit compatibility layer, but it seems plausible that it could happen
> > in future.
> 
> Sure, let me know what you think of the proposed posted changes.

All looked fine to me, but I'm not that familiar with the compat-drivers
code base.

Ben.

-- 
Ben Hutchings
The generation of random numbers is too important to be left to chance.
- Robert Coveyou


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

Bug#665000: Workaround for this bug

2013-03-20 Thread Julien Cristau 
On Wed, Mar 20, 2013 at 22:28:24 +0800, Thomas Goirand wrote:

> Hi,
> 
> On one of my server, I had the issue as well. I'm not sure if it's the
> exact same one, but at least I fixed it.
> 
> What happened for me was that my KVM over IP was printing "No signal"
> just right after the login prompt (eg: the rest of the boot process
> seemed to not be bothered). Then I did:
> 
> dpkg-reconfigure grub-pc
> 
> and added:
> 
> radeon.modeset=0
> 
> to the linux command line. After doing that, then I was able to see my
> text mode login prompt (which is the only thing I care for a server, I
> will never care about X support...).
> 
> Though, I am wondering if the issue isn't simply that the kernel is
> trying to set a mode which is higher than what my KVM over IP can
> support. How can I choose such mode (which would be a better fix)? Do
> you know Ben, maybe?
> 
KMS drivers should honor modes specified with the video= boot parameter.
Optionally on a per-connector basis, e.g. "video=VGA-1:800x600".

Cheers,
Julien


signature.asc
Description: Digital signature

Bug#703522: linux-image-3.2.0-0.bpo.4-rt-686-pae: Upgrading to 3.2.39-2~bpo60+1 fails with error (file mising)

2013-03-20 Thread Ben Hutchings 
Control: reassign -1 extlinux 2:4.05+dfsg-2~bpo60+1

On Wed, 2013-03-20 at 16:14 +0100, rpnpif wrote:
> Package: src:linux
> Version: 3.2.35-2~bpo60+1
> Severity: normal
> 
> I used linux-image-3.2.0-0.bpo.4-rt from a while.
> I can not upgrading last updating with 3.2.39-2~bpo60+1.
> 
> Preparing to replace linux-image-3.2.0-0.bpo.4-rt-686-pae 3.2.35-2~bpo60+1 
> (using .../linux-image-3.2.0-0.bpo.4-rt-686-pae_3.2.39-2~bpo60+1_i386.deb) ...
> Unpacking replacement linux-image-3.2.0-0.bpo.4-rt-686-pae ...
> Examining /etc/kernel/postrm.d .
> run-parts: executing /etc/kernel/postrm.d/initramfs-tools 
> 3.2.0-0.bpo.4-rt-686-pae /boot/vmlinuz-3.2.0-0.bpo.4-rt-686-pae
> run-parts: executing /etc/kernel/postrm.d/zz-extlinux 
> 3.2.0-0.bpo.4-rt-686-pae /boot/vmlinuz-3.2.0-0.bpo.4-rt-686-pae
> P: Checking for EXTLINUX directory... found.
> P: Writing config for /boot/vmlinuz-3.2.0-0.bpo.4-rt-686-pae...
> E: /usr/share/syslinux/themes/debian/extlinux: No such file or directory
[...]

Linux kernel packages just tells the installed boot loaders to do
whatever is necessary at installation time.  A failure here is usually
not the fault of the kernel package, and certainly this file is nothing
to do with us.

Ben.

-- 
Ben Hutchings
The generation of random numbers is too important to be left to chance.
- Robert Coveyou


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

Processed: Re: Bug#703522: linux-image-3.2.0-0.bpo.4-rt-686-pae: Upgrading to 3.2.39-2~bpo60+1 fails with error (file mising)

2013-03-20 Thread Debian Bug Tracking System 
Processing control commands:

> reassign -1 extlinux 2:4.05+dfsg-2~bpo60+1
Bug #703522 [src:linux] linux-image-3.2.0-0.bpo.4-rt-686-pae: Upgrading to 
3.2.39-2~bpo60+1 fails with error (file mising)
Bug reassigned from package 'src:linux' to 'extlinux'.
No longer marked as found in versions linux/3.2.35-2~bpo60+1.
Ignoring request to alter fixed versions of bug #703522 to the same values 
previously set
Bug #703522 [extlinux] linux-image-3.2.0-0.bpo.4-rt-686-pae: Upgrading to 
3.2.39-2~bpo60+1 fails with error (file mising)
There is no source info for the package 'extlinux' at version 
'2:4.05+dfsg-2~bpo60+1' with architecture ''
Unable to make a source version for version '2:4.05+dfsg-2~bpo60+1'
Marked as found in versions 2:4.05+dfsg-2~bpo60+1.

-- 
703522: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=703522
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.b703522.13638055809265.transcr...@bugs.debian.org

Bug#677880: cuenta cancelada

2013-03-20 Thread CORREO 
Su buzón se ha superado el límite de almacenamiento según lo establecido por el 
administrador, 
Y Usted no será capaz de recibir correos nuevos hasta que se volverá a validar. 
De revalidar - por favor HAGA CLICK AQUÍ 
http://www.formstack.com/forms/?1429055-QT8BEfXui2
Administrador del sistema.


--
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/536871963.17212.1363806708184.JavaMail.javamailuser@localhost

Bug#703506: GMA500: higher resolutions than 800x600 don't work

2013-03-20 Thread Jonathan Nieder 
Hi Georg,

Georg Sassen wrote:

> While the native resolution (1280x720) worked fine until kernel
> version 3.2.0.4-686-pae_3.2.35-2, I now only have 800x600 resolution
> in X11 and the initial framebuffer now on my Nokia Booklet 3G since
> the update.

Thanks for reporting.  Can you reproduce this using
xserver-xorg-video-modesetting and the 3.8.y kernel from experimental
as well?

If so, please file a report upstream at bugzilla.kernel.org, product
Drivers, component Video(DRI - Intel) with the information described
at [1] and let us know the bug number so we can track it.

If not, we can try to find what patch fixed it and apply the same to
wheezy.  So either result is progress.

[...]
> ** Loaded modules:

I don't see your GPU driver here.

[...]
> 00:02.0 VGA compatible controller [0300]: Intel Corporation System Controller 
> Hub (SCH Poulsbo) Graphics Controller [8086:8108] (rev 07) (prog-if 00 [VGA 
> controller])
>   Subsystem: Nokia Telecommunications oy Device [13b8:0001]

This should use the gma500_gfx driver.

Hope that helps,
Jonathan


-- 
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/20130320194429.gq3...@google.com

Bug#677880: cuenta cancelada

2013-03-20 Thread CORREO 
Su buzón se ha superado el límite de almacenamiento según lo establecido por el 
administrador, 
Y Usted no será capaz de recibir correos nuevos hasta que se volverá a validar. 
De revalidar - por favor HAGA CLICK AQUÍ 
http://www.formstack.com/forms/?1429055-QT8BEfXui2
Administrador del sistema.


--
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/238822831.17493.1363808072398.JavaMail.javamailuser@localhost

Bug#701189: linux-image-3.7-trunk-amd64: 3.7.8 locks up occasionally

2013-03-20 Thread Christian Ohm 
> On Monday, 25 February 2013 at  4:10, Ben Hutchings wrote:
> > Instead of updating to 3.7.9, I'll be uploading 3.8 to experimental
> > shortly.  Could you report whether that is more stable, once you've used
> > it for a while?

So far, I've had two more hangs under 3.7, but in general it was pretty
ok. 3.8 didn't hang in the short time I tried it, but it lost the
network card pretty soon after booting, spamming the kernel log with
lots of "atl1c :02:00.0: PCI-DMA: Out of IOMMU space for 1522 bytes"
(with different sizes). Google gives
https://bugzilla.redhat.com/show_bug.cgi?id=918393 which indicates that
the just released kernel 3.8.4 includes a fix for that. I've also found
https://www.kernel.org/pub/linux/kernel/projects/backports/stable/v3.8/ChangeLog-3.8-1
saying "2) PCI dma mapping errors in atl1c are not checked for and this
cause hard crashes for some users, from Xiong Huang." which seems to be
the cause of the broken network, and also might be a fix for the hangs
in 3.7.

Best regards,
Christian Ohm


-- 
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/20130320215144.GC5230@moongate.localnet

Processed: tagging 701189

2013-03-20 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> tags 701189 + pending
Bug #701189 [src:linux] linux-image-3.7-trunk-amd64: 3.7.8 locks up occasionally
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#701189: linux-image-3.7-trunk-amd64: 3.7.8 locks up occasionally

2013-03-20 Thread Ben Hutchings 
On Wed, 2013-03-20 at 22:51 +0100, Christian Ohm wrote:
> > On Monday, 25 February 2013 at  4:10, Ben Hutchings wrote:
> > > Instead of updating to 3.7.9, I'll be uploading 3.8 to experimental
> > > shortly.  Could you report whether that is more stable, once you've used
> > > it for a while?
> 
> So far, I've had two more hangs under 3.7, but in general it was pretty
> ok. 3.8 didn't hang in the short time I tried it, but it lost the
> network card pretty soon after booting, spamming the kernel log with
> lots of "atl1c :02:00.0: PCI-DMA: Out of IOMMU space for 1522 bytes"
> (with different sizes). Google gives
> https://bugzilla.redhat.com/show_bug.cgi?id=918393 which indicates that
> the just released kernel 3.8.4 includes a fix for that.

Right, there was a change to atl1c in Linux 3.8 that causes it to leak
memory very quickly.

> I've also found
> https://www.kernel.org/pub/linux/kernel/projects/backports/stable/v3.8/ChangeLog-3.8-1
> saying "2) PCI dma mapping errors in atl1c are not checked for and this
> cause hard crashes for some users, from Xiong Huang." which seems to be
> the cause of the broken network, and also might be a fix for the hangs
> in 3.7.

That was the change that caused this memory leak.  I doubt that it has
anything to do with the bug you reported.  Well, I'll upload 3.8.4 soon
and you can find out whether it is really fixed.

Ben.

-- 
Ben Hutchings
The generation of random numbers is too important to be left to chance.
- Robert Coveyou


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

Soft lockup issues since upgrading to kernel 3.2.39-2 in Debian Testing

2013-03-20 Thread Adriano Vilela Barbosa 
Hello everybody,

First of all, I don't know if this is the most appropriate place to
report this. If not, I apologize in advance. But I thought it would be
better to discuss this in some Debian mailing list instead of just
reporting a bug.

I'm running Debian Testing and, since upgrading from kernel 3.2.35-2
to kernel 3.2.39-2 a few days ago, I've been having some soft lockup
issues which bring my machine to an almost complete freeze (I'm still
able to access it through ssh).  The kind of error messages I'm
getting (extracted from dmesg) are shown at the end of this email. If
this is in fact a good place to discuss this, please let me know what
kind of information I need to provide in order to help pinpoint what
the problem is.  I can say, however, that to me the problem seems to
be related to Virtualbox: every time the problem happened was a little
after launching Virtualbox.

Thank you,

Adriano


Output of uname -a:
Linux arsenal 3.2.0-4-amd64 #1 SMP Debian 3.2.39-2 x86_64 GNU/Linux

Dmesg messages:

[518178.318133] BUG: soft lockup - CPU#4 stuck for 23s! [VirtualBox:22509]
[518178.318135] Modules linked in: cpuid nls_cp437 vfat fat parport_pc
ppdev lp parport pci_stub vboxpci(O) vboxnetadp(O) vboxnetflt(O)
vboxdrv(O) nls_utf8 hfsplus loop firewire_sbp2 btusb bluetooth
uvcvideo videodev v4l2_compat_ioctl32 media arc4 snd_hda_codec_hdmi
radeon snd_hda_codec_cirrus ath9k ath9k_common snd_hda_intel
snd_hda_codec snd_hwdep snd_pcm_oss snd_mixer_oss ttm drm_kms_helper
drm power_supply coretemp applesmc i2c_algo_bit i2c_i801 crc32c_intel
ath9k_hw ghash_clmulni_intel iTCO_wdt i2c_core snd_pcm aesni_intel
iTCO_vendor_support ath mac80211 cfg80211 rfkill aes_x86_64
acpi_cpufreq mperf video evdev aes_generic pcspkr input_polldev
apple_bl button processor thermal_sys cryptd snd_page_alloc snd_timer
snd soundcore ext4 crc16 jbd2 mbcache microcode hid_apple usbhid hid
sg sr_mod sd_mod cdrom crc_t10dif ata_generic usb_storage uhci_hcd
ata_piix tg3 libphy libata scsi_mod firewire_ohci ehci_hcd
firewire_core usbcore crc_itu_t usb_common [last unloaded:
scsi_wait_scan]
[518178.318189] CPU 4
[518178.318190] Modules linked in: cpuid nls_cp437 vfat fat parport_pc
ppdev lp parport pci_stub vboxpci(O) vboxnetadp(O) vboxnetflt(O)
vboxdrv(O) nls_utf8 hfsplus loop firewire_sbp2 btusb bluetooth
uvcvideo videodev v4l2_compat_ioctl32 media arc4 snd_hda_codec_hdmi
radeon snd_hda_codec_cirrus ath9k ath9k_common snd_hda_intel
snd_hda_codec snd_hwdep snd_pcm_oss snd_mixer_oss ttm drm_kms_helper
drm power_supply coretemp applesmc i2c_algo_bit i2c_i801 crc32c_intel
ath9k_hw ghash_clmulni_intel iTCO_wdt i2c_core snd_pcm aesni_intel
iTCO_vendor_support ath mac80211 cfg80211 rfkill aes_x86_64
acpi_cpufreq mperf video evdev aes_generic pcspkr input_polldev
apple_bl button processor thermal_sys cryptd snd_page_alloc snd_timer
snd soundcore ext4 crc16 jbd2 mbcache microcode hid_apple usbhid hid
sg sr_mod sd_mod cdrom crc_t10dif ata_generic usb_storage uhci_hcd
ata_piix tg3 libphy libata scsi_mod firewire_ohci ehci_hcd
firewire_core usbcore crc_itu_t usb_common [last unloaded:
scsi_wait_scan]
[518178.318242]
[518178.318244] Pid: 22509, comm: VirtualBox Tainted: G   O
3.2.0-4-amd64 #1 Debian 3.2.39-2 Apple Inc.
iMac12,1/Mac-942B5BF58194151B
[518178.318247] RIP: 0010:[]  []
__bitmap_empty+0xa/0x52
[518178.318253] RSP: 0018:8803629bfdd8  EFLAGS: 0246
[518178.318254] RAX: 0008 RBX:  RCX:
0040
[518178.318257] RDX:  RSI: 0200 RDI:
81761718
[518178.318259] RBP: 81761718 R08:  R09:
880056d57220
[518178.318261] R10: 880056d57220 R11: 880056d571e8 R12:
7f7560679000
[518178.318263] R13: 0246 R14: 880056d57220 R15:

[518178.318265] FS:  7f757a9ec700() GS:88046fd0()
knlGS:
[518178.318268] CS:  0010 DS:  ES:  CR0: 80050033
[518178.318269] CR2: 7f7560698718 CR3: 00037c1aa000 CR4:
000426e0
[518178.318272] DR0:  DR1:  DR2:

[518178.318274] DR3:  DR6: 0ff0 DR7:
0400
[518178.318276] Process VirtualBox (pid: 22509, threadinfo
8803629be000, task 8800558e0f20)
[518178.318278] Stack:
[518178.318279]  810318d1 0001 880056d571e8
7f7560679000
[518178.318283]  7f7560679000 7f7560679000 7f7560679000
7f7560679000
[518178.318287]  81031701 810d697d 
0007f7560678
[518178.318291] Call Trace:
[518178.318295]  [] ? native_flush_tlb_others+0xaf/0xe5
[518178.318298]  [] ? flush_tlb_others+0x5/0x8
[518178.318302]  [] ? mprotect_fixup+0x4e9/0x6a7
[518178.318305]  [] ? do_page_fault+0x2fc/0x337
[518178.318309]  [] ? sys_mprotect+0x18f/0x1fd
[518178.318313]  [] ? system_call_fastpath+0x16/0x1b
[518178.318314] Code: 8d 44 24 20 4c 89 4c 24 48 c7 44 24 08 10 00 00
00 48 89 44 24 18 e

Bug#703574: efivars can turn some Samsung systems into bricks

2013-03-20 Thread Ben Hutchings 
Package: src:linux
Version: 3.2.39-2
Severity: critical
Tags: upstream fixed-upstream patch

EFI can store named variables in persistant storage (i.e. flash),
which is compacted at boot.  On some Samsung systems (and maybe
others), compaction fails and the system will not boot if the
variable space is more than 50% full.

The workaround for this is:

commit 7feecf3f2b587e535550bb3e7bf75b2fee06fccf
Author: Josh Boyer 
Date:   Mon Mar 11 17:48:53 2013 -0400

efi: be more paranoid about available space when creating variables

which I backported into 3.2.41.

Ben.

-- System Information:
Debian Release: 7.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: i386 (x86_64)
Foreign Architectures: amd64

Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (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/20130321001930.21972.79054.report...@deadeye.wl.decadent.org.uk

Processed: tagging 701189

2013-03-20 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> tags 701189 - pending moreinfo
Bug #701189 [src:linux] linux-image-3.7-trunk-amd64: 3.7.8 locks up occasionally
Removed tag(s) moreinfo and pending.
> thanks
Stopping processing here.

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

Processed: tagging 703574

2013-03-20 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> tags 703574 + pending
Bug #703574 [src:linux] efivars can turn some Samsung systems into bricks
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#703209: linux: Please Add multiplatform flavour to armhf

2013-03-20 Thread Nobuhiro Iwamatsu 
On Tue, Mar 19, 2013 at 5:34 PM, Ian Campbell  wrote:
> On Tue, 2013-03-19 at 08:44 +0100, Arnaud Patard wrote:
>> I already commented some days ago on debian-arm that currently
>> multiplatform support must wait. It is useless as usb support is
>> _broken_ on multiplatform. Hopefully, Linaro devs seem back to work
>> and looks like we may have a patch merged soon. Until then, doing more
>> is near to a waste of time.
>
> I don't think making a start on a MP flavour is a waste of time at all.
>
> We are talking about packages in trunk (currently == experimental)
> rather than Sid/Wheezy. There's no possibility of us releasing anything
> with 3.8 but in the meantime adding the multiplatform flavour allows us
> to start laying the packaging ground work, finding bugs in the MP stuff
> and generally kicking the tyres etc. It's also an obvious step in the
> right direction. As you say the known issues, like the USB think, will
> be fixed upstream sooner rather than later.
>
> Since we are currently not yet talking about removing existing flavours
> I'm not sure there are any downsides to just doing it.
>
>> And about the patch in this bug, it fails to be really
>> multiplatform. During my tests on 3.8, I could already enable platforms
>> like MVEBU, HIGHBANK, BCM, MXC and you can enable OMAP too with 2-3
>> backports. Once done, it needs to be tested on real platforms as it
>> would probably allow to detect some more bugs. 3.9 may be better.
>
> This patch is a start though and doesn't preclude adding those other
> platforms either straight away or when 3.9 comes around as we like.
> Having the flavour would also enable testing on real platforms so that
> isn't a reason to wait IMHO.

Thank you for following this up.
I want to explain to me what you wrote.

>
>> On the long term, we'll have also to consider if we should keep
>> omap/mx5/vexpress or not. If we remove them, we should make sure that
>> the transition will work nicely.
>
> Ack.

me too.

-- 
Nobuhiro Iwamatsu
   iwamatsu at {nigauri.org / debian.org}
   GPG ID: 40AD1FA6


-- 
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/CABMQnV+aUqJd5esxD9Tc95k86nd_Udnjn+=odogkcykbl_g...@mail.gmail.com

Bug#703209: linux: Please Add multiplatform flavour to armhf

2013-03-20 Thread Nobuhiro Iwamatsu 
Hi,

On Wed, Mar 20, 2013 at 12:17 AM, Paul Wise  wrote:
> On Tue, 2013-03-19 at 15:05 +, Ian Campbell wrote:
>
>> I think the question here is what the `uname -r` bit should be.
>> Specifically the $FLAVOUR in 3.x.y-z-$FLAVOUR.
>
> Woops, I missed that uname -r includes the flavour bit.
>
>> I think there is an argument for making the multiplatform case be the
>> default "no-flavour flavour" i.e. $FLAVOUR is armhf/arm64 etc. Or
>> maybe that's what you are suggesting having not realised that `uname
>> -r` currently includes the -$FLAVOUR suffix. Hrm, I think we may
>> actually be talking about the same thing ;-)
>
> Right, my suggestion is just to use the architecture for the flavour, as
> is done on the other architectures.
>

Thank you for your comment.

In ARM ((but may be used on other architectures as well) ) all architectures,
flavor with the name of the CPU do is that it is multiplatform?
For example,  armv7 flavor is multiplatform support in armhf.

I think this is a very simple rule.

Best regards,
  Nobuhiro

-- 
Nobuhiro Iwamatsu
   iwamatsu at {nigauri.org / debian.org}
   GPG ID: 40AD1FA6


-- 
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/CABMQnVL=uen73eqdld9ts2_5ef5n_6cks2ngmsbfoedptwk...@mail.gmail.com

Bug#703506: GMA500: higher resolutions than 800x600 don't work

2013-03-20 Thread Jonathan Nieder 
Hi again,

I left out the URL for Intel's bug reporting guidelines:

Jonathan Nieder wrote:
> Georg Sassen wrote:

>> While the native resolution (1280x720) worked fine until kernel
>> version 3.2.0.4-686-pae_3.2.35-2, I now only have 800x600 resolution
>> in X11 and the initial framebuffer now on my Nokia Booklet 3G since
>> the update.
>
> Thanks for reporting.  Can you reproduce this using
> xserver-xorg-video-modesetting and the 3.8.y kernel from experimental
> as well?
>
> If so, please file a report upstream at bugzilla.kernel.org, product
> Drivers, component Video(DRI - Intel) with the information described
> at [1] and let us know the bug number so we can track it.

[1] https://01.org/linuxgraphics/documentation/how-report-bugs-0

> If not, we can try to find what patch fixed it and apply the same to
> wheezy.  So either result is progress.

Thanks again, and sorry for the noise.


-- 
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/20130321055840.GA5753@elie.Belkin

Bug#703485: [3.2->3.8.3 regression] Battery not detected on Dell Latitude E5530

2013-03-20 Thread Jonathan Nieder 
# regression
severity 703485 important
quit

Hi Jean-Christophe,

Jean-Christophe Dubacq wrote:

> While trying to resolve stability issues with the testing linux image,
> I tried kernel 3.8 in experimental. I fully understand that this kernel
> may not be used in production. However, when booting with this kernel,
> the battery is not detected (and thus, laptop-detect thinks that it is
> a desktop computer, which it is not). Of course, no /proc/acpi/BAT0 is
> created, which makes system tools not work. I think the problem lies
> in the kernel because of this.
>
> The first significant difference that I see in the logs is:
> -ACPI Error: [DCK9] Namespace lookup failure, AE_ALREADY_EXISTS 
> (20121018/dswload2-330)

Please report this upstream at bugzilla.kernel.org, product ACPI,
component Power-Battery, and let us know the bug number so we can
track it.

Be sure to include:

 - steps to reproduce the problem, expected result, actual result, and
   how the difference indicates a bug (should be simple enough)

 - which kernel versions you have tested and what happened with each

 - full "dmesg" output from an affected and unaffected boot, as
   attachments

 - "acpidump" output, as an attachment

Hopefully the upstream developers may have ideas for further tracking
the problem down from that point.

Then if you'd like to track this down further before hearing back from
them, a good way can be to try versions halfway between the newest
known-good and oldest known-bad kernels from
, which can help narrow down
the search for the problematic patch.

Hope that helps,
Jonathan


-- 
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/20130321061417.GC5753@elie.Belkin

Processed: Re: [3.2->3.8.3 regression] Battery not detected on Dell Latitude E5530

2013-03-20 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> # regression
> severity 703485 important
Bug #703485 [src:linux] linux-image-3.8-trunk-amd64: Battery not detected on 
Dell Latitude E5530
Severity set to 'important' from 'normal'
> quit
Stopping processing here.

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