Bug#801925: [PATCH] SCSI: fix crashes in sd and sr runtime PM

2016-01-26 Thread Erich Schubert 
Hello Alan,
Thank you:

The patch appears to work for me, too.

Applied on top of Debian kernel "4.4-1~exp1" I finally have a kernel boot again!
(And maybe this will also make the Intel ( i7-2677M IGP) video bugs
disappear...)

Best regards,
Erich

On Wed, Jan 20, 2016 at 5:26 PM, Alan Stern <st...@rowland.harvard.edu> wrote:
> Runtime suspend during driver probe and removal can cause problems.
> The driver's runtime_suspend or runtime_resume callbacks may invoked
> before the driver has finished binding to the device or after the
> driver has unbound from the device.
>
> This problem shows up with the sd and sr drivers, and can cause disk
> or CD/DVD drives to become unusable as a result.  The fix is simple.
> The drivers store a pointer to the scsi_disk or scsi_cd structure as
> their private device data when probing is finished, so we simply have
> to be sure to clear the private data during removal and test it during
> runtime suspend/resume.
>
> This fixes <https://bugs.debian.org/801925>.
>
> Signed-off-by: Alan Stern <st...@rowland.harvard.edu>
> Reported-by: Paul Menzel <paul.men...@giantmonkey.de>
> Reported-by: Erich Schubert <er...@debian.org>
> Reported-by: Alexandre Rossi <alexandre.ro...@gmail.com>
> Tested-by: Paul Menzel <paul.men...@giantmonkey.de>
> CC: "James E.J. Bottomley" <jbottom...@odin.com>
> CC: Ben Hutchings <b...@decadent.org.uk>
> CC: <sta...@vger.kernel.org>
>
> ---
>
>
> [as1795]
>
>
>  drivers/scsi/sd.c |7 +--
>  drivers/scsi/sr.c |4 
>  2 files changed, 9 insertions(+), 2 deletions(-)
>
> Index: usb-4.4/drivers/scsi/sd.c
> ===
> --- usb-4.4.orig/drivers/scsi/sd.c
> +++ usb-4.4/drivers/scsi/sd.c
> @@ -3275,8 +3275,8 @@ static int sd_suspend_common(struct devi
> struct scsi_disk *sdkp = dev_get_drvdata(dev);
> int ret = 0;
>
> -   if (!sdkp)
> -   return 0;   /* this can happen */
> +   if (!sdkp)  /* E.g.: runtime suspend following sd_remove() */
> +   return 0;
>
> if (sdkp->WCE && sdkp->media_present) {
> sd_printk(KERN_NOTICE, sdkp, "Synchronizing SCSI cache\n");
> @@ -3315,6 +3315,9 @@ static int sd_resume(struct device *dev)
>  {
> struct scsi_disk *sdkp = dev_get_drvdata(dev);
>
> +   if (!sdkp)  /* E.g.: runtime resume at the start of sd_probe() */
> +   return 0;
> +
> if (!sdkp->device->manage_start_stop)
> return 0;
>
> Index: usb-4.4/drivers/scsi/sr.c
> ===
> --- usb-4.4.orig/drivers/scsi/sr.c
> +++ usb-4.4/drivers/scsi/sr.c
> @@ -144,6 +144,9 @@ static int sr_runtime_suspend(struct dev
>  {
> struct scsi_cd *cd = dev_get_drvdata(dev);
>
> +   if (!cd)/* E.g.: runtime suspend following sr_remove() */
> +   return 0;
> +
> if (cd->media_present)
> return -EBUSY;
> else
> @@ -985,6 +988,7 @@ static int sr_remove(struct device *dev)
> scsi_autopm_get_device(cd->device);
>
> del_gendisk(cd->disk);
> +   dev_set_drvdata(dev, NULL);
>
> mutex_lock(_ref_mutex);
> kref_put(>kref, sr_kref_release);
>

Bug#801925: NULL pointer dereference: IP: [] sr_runtime_suspend+0xc/0x20 [sr_mod]

2016-01-10 Thread Erich Schubert 
Hi all,
4.4-rc8 does not fix the problem for me.
Anything beyond 4.1.0 remains unable to boot this computer.

Unfortunately, because the error occurs during early early SCSI
initialization, I do not have easy access to the log - no disk, no
network.
It happens during SATA initialization: "scsi_runtime_resume".
So my back trace looks different than Alex in
https://bugs.debian.org/cgi-bin/bugreport.cgi?msg=42;filename=scsi-null-pointer-dereference.log;bug=801925;att=1
but like the one Paul is seeing:
https://bugs.debian.org/cgi-bin/bugreport.cgi?msg=15;filename=20151020_006.jpg;bug=801925;att=3
I will try to do a photo next time, too.

Here is some dmesg output from a successful boot on 4.1.0:
Note there are some ACPI Errors there (but probably not related).
---
ahci :00:1f.2: version 3.0
ahci :00:1f.2: SSS flag set, parallel bus scan disabled
ahci :00:1f.2: AHCI 0001.0300 32 slots 6 ports 3 Gbps 0x1 impl SATA mode
ahci :00:1f.2: flags: 64bit ncq sntf stag pm led clo pio slum part ems apst
scsi host0: ahci
scsi host1: ahci
scsi host2: ahci
scsi host3: ahci
scsi host4: ahci
scsi host5: ahci
ata1: SATA max UDMA/133 abar m2048@0xc0728000 port 0xc0728100 irq 30
ata2: DUMMY
ata3: DUMMY
ata4: DUMMY
ata5: DUMMY
ata6: DUMMY
usb 3-1: new high-speed USB device number 2 using ehci-pci
usb 4-1: new high-speed USB device number 2 using ehci-pci
ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ACPI Error: [GTF0] Namespace lookup failure, AE_NOT_FOUND (20150410/psargs-359)
ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.PRT0._SDD]
(Node 8802458b1608), AE_NOT_FOUND (20150410/psparse-536)
ACPI Error: [GTF0] Namespace lookup failure, AE_NOT_FOUND (20150410/psargs-359)
ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.PRT0._GTF]
(Node 8802458b15e0), AE_NOT_FOUND (20150410/psparse-536)
ata1.00: ATA-8: TOSHIBA THNSNS256GMCP, TA2ABBF0, max UDMA/133
ata1.00: 500118192 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
ACPI Error: [GTF0] Namespace lookup failure, AE_NOT_FOUND (20150410/psargs-359)
ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.PRT0._SDD]
(Node 8802458b1608), AE_NOT_FOUND (20150410/psparse-536)
ACPI Error: [GTF0] Namespace lookup failure, AE_NOT_FOUND (20150410/psargs-359)
ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.PRT0._GTF]
(Node 8802458b15e0), AE_NOT_FOUND (20150410/psparse-536)
ata1.00: configured for UDMA/133
scsi 0:0:0:0: Direct-Access ATA  TOSHIBA THNSNS25 BBF0 PQ: 0 ANSI: 5
sd 0:0:0:0: [sda] 500118192 512-byte logical blocks: (256 GB/238 GiB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
 sda: sda1 sda2 sda3 sda4 < sda5 sda6 >
sd 0:0:0:0: [sda] Attached SCSI disk
PM: Starting manual resume from disk
PM: Hibernation image partition 8:6 present
PM: Looking for hibernation image.
PM: Image not found (code -22)
PM: Hibernation image not present or could not be loaded.
---

On Sat, Jan 9, 2016 at 5:36 PM, Alan Stern  wrote:
> On Sat, 9 Jan 2016, Paul Menzel wrote:
>
>> Version: 4.4~rc8-1~exp1
>>
>> Dear Alan,
>>
>>
>> Thank you for your help!
>>
>> There were some follow-ups to the bug report [1], but I think you and I
>> were not in CC.
>
> I wasn't.
>
>> > http://marc.info/?l=linux-scsi=144185206825609=2
>> > http://marc.info/?l=linux-scsi=144185208525611=2
>
>> I can only say, that I am still unable to boot my system with Linux
>> 4.4-rc8 [2]. Are these patches included there?
>
> They are.  I don't see how they could cause a NULL pointer dereference
> in sd_resume(), though.  If you revert them, does the problem go away?
>
> Also, can you add some debugging statements to sd_resume() so we can
> see where the NULL pointer comes from?
>
> Alan Stern
>

Bug#801925: Linux Null Pointer Dereference on boot

2015-11-10 Thread Erich Schubert 
Hi,
Both me and a colleague are bit by the same/a similar bug.
The Null Pointer Dereference here is at sd_resume during early boot,
but looks very much related to this issue.

The last kernel able to boot for me is 4.1.0-2-amd64
Anything later than that (including linux-image-4.3.0-trunk-amd64
4.3-1~exp1) does not work anymore.

So yes, it appears to be broken *since*
49718f0fb8c9 ("SCSI: Fix NULL pointer dereference in runtime PM")
and the patches from Ken Xue may be helpful (untested).

Regards,
Erich

Bug#763155: Bug#764528: Cross-referencing i915 kernel bugs on EEEpc

2015-02-11 Thread Erich Schubert 
tag 764528 + patch jessie
tag 763155 + patch jessie
thanks

An improved patch has been posted, by Daniel Vetter of Intel:
https://freedesktop.org/patch/42259/

It has also been discussed on the LKML, and I hope it will be included
in the next round of pull requests of drm-next.

On Sat, Feb 7, 2015 at 3:22 PM, Erich Schubert er...@debian.org wrote:
 tag 764528 + patch jessie
 tag 763155 + patch jessie
 thanks

 There appears to be a rather easy patch available:
 http://patchwork.freedesktop.org/patch/38659/
 Quietly reject attempts to create non-pagealigned stolen objects

 Judging from the discussion, it is not a real bug. It is an
 unexpected behavior (Bios using non-aligned video buffer, supported by
 the hardware, but not aligned to the driver requirements). The patch
 essentially replaces the BUG_ON with a log statement and then returns
 null, which is supposed to reliably work. (Without reusing the memory
 the bios used.)

 This probably won't be the final fix. There is some discussion here:
 http://permalink.gmane.org/gmane.comp.freedesktop.xorg.drivers.intel/52613
 which suggests that instead it may be desirable to reuse the bios
 allocation, and just align it as desired.

 But since this causes boot issues on some eeePC models (apparently, it
 depends on the bios and CPU), and the patch is quite simple, it should
 be considered for jessie, even if the patch isn't the long-term
 solution yet. Thank you.

 Regards,
 Erich

 On Sun, Nov 30, 2014 at 10:59 PM, Erich Schubert er...@debian.org wrote:
 https://bugs.freedesktop.org/show_bug.cgi?id=86883

 Not sure if kernel bugzilla wouldn't have been the better address,
 given that the BUG_ON clearly is in kernel code. But I guess it's the
 same developers anyway.

 Regards,
 Erich


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/CAGKbab_B25VNNXEdsYK4LPeYz2BN3FjjOyWwDk3R=9H=4ac...@mail.gmail.com

Bug#763155: Bug#764528: Cross-referencing i915 kernel bugs on EEEpc

2015-02-07 Thread Erich Schubert 
tag 764528 + patch jessie
tag 763155 + patch jessie
thanks

There appears to be a rather easy patch available:
http://patchwork.freedesktop.org/patch/38659/
Quietly reject attempts to create non-pagealigned stolen objects

Judging from the discussion, it is not a real bug. It is an
unexpected behavior (Bios using non-aligned video buffer, supported by
the hardware, but not aligned to the driver requirements). The patch
essentially replaces the BUG_ON with a log statement and then returns
null, which is supposed to reliably work. (Without reusing the memory
the bios used.)

This probably won't be the final fix. There is some discussion here:
http://permalink.gmane.org/gmane.comp.freedesktop.xorg.drivers.intel/52613
which suggests that instead it may be desirable to reuse the bios
allocation, and just align it as desired.

But since this causes boot issues on some eeePC models (apparently, it
depends on the bios and CPU), and the patch is quite simple, it should
be considered for jessie, even if the patch isn't the long-term
solution yet. Thank you.

Regards,
Erich

On Sun, Nov 30, 2014 at 10:59 PM, Erich Schubert er...@debian.org wrote:
 https://bugs.freedesktop.org/show_bug.cgi?id=86883

 Not sure if kernel bugzilla wouldn't have been the better address,
 given that the BUG_ON clearly is in kernel code. But I guess it's the
 same developers anyway.

 Regards,
 Erich


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/CAGKbab9pZZoom2w1cGpDH7zxSf=j86g0mn7uok8rdu5mbkv...@mail.gmail.com

Bug#763155: Cross-referencing i915 kernel bugs on EEEpc

2014-11-30 Thread Erich Schubert 
severity 764528 important
tag 764528 +jessie +sid +experimental
tag 771227 +jessie +sid +experimental
block 764528 763155
block 771227 763155
merge 764528 771227
thanks

All of these are probably the same bug, rendering current kernels
(jessie onward) unusable on EEEpc with older (?) Atom CPUs.

As far as I can tell, the bug may be in the kernel, not the xorg
driver (xorg shouldn't lock up the kernel; and the kernel itself
reports a BUG after all...)

 kernel BUG at 
 /build/linux-Lep8DD/linux-3.16.3/drivers/gpu/drm/i915/i915_gem_stolen.c:431!

IMHO, it may be reasonable to upgrade this regression to serious
instead of important.

Regards,
Erich


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/cagkbab_bess83lpvr+yinqcpssegiw9fctygrudu_hsshfr...@mail.gmail.com

Bug#763155: Bug#764528: Cross-referencing i915 kernel bugs on EEEpc

2014-11-30 Thread Erich Schubert 
https://bugs.freedesktop.org/show_bug.cgi?id=86883

Not sure if kernel bugzilla wouldn't have been the better address,
given that the BUG_ON clearly is in kernel code. But I guess it's the
same developers anyway.

Regards,
Erich


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/CAGKbab9Q04OJ158zJN1CA8totwLWpwgx4Qsb0USA7f6q=q0...@mail.gmail.com

Bug#763155: linux-image-3.16.0-4-686-pae: Bad news, only working sometimes

2014-11-10 Thread Erich Schubert 
Package: src:linux
Version: 3.16.7-2
Followup-For: Bug #763155
Control: found 3.16.7-2

Unfortunately, the problems still persist. Today, 3.16.0-4 did not boot 
correctly either; nor did 3.17.
The last kernel working reliably was and continues to be 3.14. :-(

Hardware name: ASUSTeK Computer INC. 1016P/1015PE, BIOS 080110/06/2010

Nov 10 09:42:37 kleinphi kernel: ACPI: AC Adapter [AC0] (on-line)
Nov 10 09:42:37 kleinphi kernel: wmi: Mapper loaded
Nov 10 09:42:37 kleinphi kernel: [drm] Initialized drm 1.1.0 20060810
Nov 10 09:42:37 kleinphi kernel: ACPI: Battery Slot [BAT0] (battery present)
Nov 10 09:42:37 kleinphi kernel: ACPI Warning: SystemIO range 
0x0828-0x082f conflicts with OpRegion 0x0800-0x087f (\PMIO) 
(20140424/utaddress-258)
Nov 10 09:42:37 kleinphi kernel: ACPI Warning: SystemIO range 
0x0828-0x082f conflicts with OpRegion 0x0828-0x082f 
(\_SB_.PCI0.SBRG.IELK.GPSE) (20140424/utaddress-258)
Nov 10 09:42:37 kleinphi kernel: ACPI: If an ACPI driver is available for this 
device, you should use it instead of the native driver
Nov 10 09:42:37 kleinphi kernel: ACPI Warning: SystemIO range 
0x04b0-0x04bf conflicts with OpRegion 0x0480-0x04bf 
(\_SB_.PCI0.SBRG.GPBX) (20140424/utaddress-258)
Nov 10 09:42:37 kleinphi kernel: ACPI: If an ACPI driver is available for this 
device, you should use it instead of the native driver
Nov 10 09:42:37 kleinphi kernel: ACPI Warning: SystemIO range 
0x0480-0x04af conflicts with OpRegion 0x0480-0x04bf 
(\_SB_.PCI0.SBRG.GPBX) (20140424/utaddress-258)
Nov 10 09:42:37 kleinphi kernel: ACPI: If an ACPI driver is available for this 
device, you should use it instead of the native driver
Nov 10 09:42:37 kleinphi kernel: lpc_ich: Resource conflict(s) found affecting 
gpio_ich
Nov 10 09:42:37 kleinphi kernel: shpchp: Standard Hot Plug PCI Controller 
Driver version: 0.4
Nov 10 09:42:37 kleinphi kernel: media: Linux media interface: v0.10
Nov 10 09:42:37 kleinphi kernel: bcma: bus0: Found chip with id 0x4313, rev 
0x01 and package 0x08
Nov 10 09:42:37 kleinphi kernel: bcma: bus0: Core 0 found: ChipCommon (manuf 
0x4BF, id 0x800, rev 0x24, class 0x0)
Nov 10 09:42:37 kleinphi kernel: bcma: bus0: Core 1 found: IEEE 802.11 (manuf 
0x4BF, id 0x812, rev 0x18, class 0x0)
Nov 10 09:42:37 kleinphi kernel: bcma: bus0: Core 2 found: PCIe (manuf 0x4BF, 
id 0x820, rev 0x11, class 0x0)
Nov 10 09:42:37 kleinphi kernel: bcma: bus0: Bus registered
Nov 10 09:42:37 kleinphi kernel: i915: unknown parameter 'i915_enable_rc6' 
ignored
Nov 10 09:42:37 kleinphi kernel: i915: unknown parameter 'i915_enable_fbc' 
ignored
Nov 10 09:42:37 kleinphi kernel: Linux video capture interface: v2.00
Nov 10 09:42:37 kleinphi kernel: [drm] Memory usable by graphics device = 512M
Nov 10 09:42:37 kleinphi kernel: [drm] Replacing VGA console driver
Nov 10 09:42:37 kleinphi kernel: Console: switching to colour dummy device 80x25
Nov 10 09:42:37 kleinphi kernel: i915 :00:02.0: irq 44 for MSI/MSI-X
Nov 10 09:42:37 kleinphi kernel: [drm] Supports vblank timestamp caching Rev 2 
(21.10.2013).
Nov 10 09:42:37 kleinphi kernel: [drm] Driver supports precise vblank timestamp 
query.
Nov 10 09:42:37 kleinphi kernel: vgaarb: device changed decodes: 
PCI::00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
Nov 10 09:42:37 kleinphi kernel: [ cut here ]
Nov 10 09:42:37 kleinphi kernel: kernel BUG at 
/build/linux-cizhNw/linux-3.16.7/drivers/gpu/drm/i915/i915_gem_stolen.c:431!
Nov 10 09:42:37 kleinphi kernel: invalid opcode:  [#1] SMP 
Nov 10 09:42:37 kleinphi kernel: Modules linked in: snd_hda_codec videodev 
i915(+) bcma media evdev snd_hwdep snd_pcm shpchp lpc_ich psmouse serio_raw 
mfd_core snd_timer snd battery drm_kms_helper drm i2c_algo_bit soundcore 
i2c_core wmi video ac sparse_keymap rfkill button acpi_cpufreq processor 
coretemp loop fuse parport_pc ppdev lp parport autofs4 ext4 crc16 mbcache jbd2 
sg sd_mod crc_t10dif crct10dif_generic crct10dif_common ahci libahci uhci_hcd 
ehci_pci libata ehci_hcd scsi_mod usbcore usb_common thermal atl1c thermal_sys
Nov 10 09:42:37 kleinphi kernel: CPU: 1 PID: 225 Comm: systemd-udevd Not 
tainted 3.16.0-4-686-pae #1 Debian 3.16.7-2
Nov 10 09:42:38 kleinphi kernel: Hardware name: ASUSTeK Computer INC. 
1016P/1015PE, BIOS 080110/06/2010
Nov 10 09:42:39 kleinphi kernel: task: f6c73560 ti: f4cce000 task.ti: f4cce000
Nov 10 09:42:39 kleinphi kernel: EIP: 0060:[f842813b] EFLAGS: 00010206 CPU: 1
Nov 10 09:42:39 kleinphi kernel: EIP is at 
i915_gem_object_create_stolen_for_preallocated+0x20b/0x280 [i915]
Nov 10 09:42:39 kleinphi kernel: EAX: f6d27400 EBX: f443c150 ECX: 001d4c00 EDX: 
001d4c00
Nov 10 09:42:39 kleinphi kernel: ESI: f4438000 EDI: 001d4c00 EBP: f4ccfb60 ESP: 
f4ccfb38
Nov 10 09:42:39 kleinphi kernel:  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
Nov 10 09:42:39 kleinphi kernel: CR0: 80050033 CR2: b76e298e CR3: 34f77000 CR4: 
07f0
Nov 10 09:42:39 kleinphi kernel:

Bug#763155: linux-image-3.16.0-4-686-pae: Probably resolved in 3.16.0-4-686

2014-11-07 Thread Erich Schubert 
Package: src:linux
Followup-For: Bug #763155

Hello,
Successfully running 3.16.0-4-686-pae right now.
Either the problem is gone, or it doesn't occur on every boot.
(Different EEEpc model, though)

-- Package-specific info:
** Version:
Linux version 3.16.0-4-686-pae (debian-kernel@lists.debian.org) (gcc version 
4.8.3 (Debian 4.8.3-13) ) #1 SMP Debian 3.16.7-2 (2014-11-06)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-3.16.0-4-686-pae 
root=UUID=aa89f4fe-2436-40c9-b83b-1feb9e644084 ro quiet splash 
pciehp.pciehp_force=1 resume=UUID=afcf3a0f-4df7-4a4a-b221-73709c3dbd27 
i915.i915_enable_rc6=1 i915.i915_enable_fbc=1 i915.semaphores=1 
video.use_native_backlight=0

** Not tainted

** Kernel log:
[ 2921.017954] brcmsmac bcma0:0: brcmsmac: brcms_ops_bss_info_changed: 
disassociated
[ 2921.017974] brcmsmac bcma0:0: brcms_ops_bss_info_changed: arp filtering: 1 
addresses (implement)
[ 2921.017983] brcmsmac bcma0:0: brcms_ops_bss_info_changed: qos enabled: false 
(implement)
[ 2921.032449] cfg80211: Calling CRDA to update world regulatory domain
[ 2921.104218] cfg80211: World regulatory domain updated:
[ 2921.104230] cfg80211:  DFS Master region: unset
[ 2921.104237] cfg80211:   (start_freq - end_freq @ bandwidth), 
(max_antenna_gain, max_eirp), (dfs_cac_time)
[ 2921.104248] cfg80211:   (2402000 KHz - 2472000 KHz @ 4 KHz), (N/A, 2000 
mBm), (N/A)
[ 2921.104257] cfg80211:   (2457000 KHz - 2482000 KHz @ 4 KHz), (N/A, 2000 
mBm), (N/A)
[ 2921.104265] cfg80211:   (2474000 KHz - 2494000 KHz @ 2 KHz), (N/A, 2000 
mBm), (N/A)
[ 2921.104274] cfg80211:   (517 KHz - 525 KHz @ 16 KHz), (N/A, 2000 
mBm), (N/A)
[ 2921.104284] cfg80211:   (525 KHz - 533 KHz @ 16 KHz), (N/A, 2000 
mBm), (0 s)
[ 2921.104293] cfg80211:   (549 KHz - 573 KHz @ 16 KHz), (N/A, 2000 
mBm), (0 s)
[ 2921.104301] cfg80211:   (5735000 KHz - 5835000 KHz @ 8 KHz), (N/A, 2000 
mBm), (N/A)
[ 2921.104310] cfg80211:   (5724 KHz - 6372 KHz @ 216 KHz), (N/A, 0 
mBm), (N/A)
[ 2921.148124] wlan0: authenticate with 00:03:52:e4:31:54
[ 2921.148297] wlan0: send auth to 00:03:52:e4:31:54 (try 1/3)
[ 2921.149565] wlan0: authenticated
[ 2921.152087] wlan0: associate with 00:03:52:e4:31:54 (try 1/3)
[ 2921.153909] wlan0: RX AssocResp from 00:03:52:e4:31:54 (capab=0xc31 status=0 
aid=3)
[ 2921.154466] brcmsmac bcma0:0: brcmsmac: brcms_ops_bss_info_changed: 
associated
[ 2921.154488] brcmsmac bcma0:0: brcms_ops_bss_info_changed: arp filtering: 1 
addresses (implement)
[ 2921.154503] brcmsmac bcma0:0: brcms_ops_bss_info_changed: qos enabled: true 
(implement)
[ 2921.154547] wlan0: associated
[ 2921.154765] cfg80211: Calling CRDA for country: DE
[ 2921.176122] cfg80211: Regulatory domain changed to country: DE
[ 2921.176131] cfg80211:  DFS Master region: ETSI
[ 2921.176136] cfg80211:   (start_freq - end_freq @ bandwidth), 
(max_antenna_gain, max_eirp), (dfs_cac_time)
[ 2921.176145] cfg80211:   (240 KHz - 2483500 KHz @ 4 KHz), (N/A, 2000 
mBm), (N/A)
[ 2921.176153] cfg80211:   (515 KHz - 525 KHz @ 8 KHz), (N/A, 2000 
mBm), (N/A)
[ 2921.176161] cfg80211:   (525 KHz - 535 KHz @ 8 KHz), (N/A, 2000 
mBm), (0 s)
[ 2921.176169] cfg80211:   (547 KHz - 5725000 KHz @ 8 KHz), (N/A, 2698 
mBm), (0 s)
[ 2921.176176] cfg80211:   (5724 KHz - 6588 KHz @ 216 KHz), (N/A, 
4000 mBm), (N/A)
[ 2934.028136] brcmsmac bcma0:0: brcmsmac: brcms_ops_bss_info_changed: 
disassociated
[ 2934.028157] brcmsmac bcma0:0: brcms_ops_bss_info_changed: arp filtering: 1 
addresses (implement)
[ 2934.028166] brcmsmac bcma0:0: brcms_ops_bss_info_changed: qos enabled: false 
(implement)
[ 2934.041662] cfg80211: Calling CRDA to update world regulatory domain
[ 2934.143891] cfg80211: World regulatory domain updated:
[ 2934.143902] cfg80211:  DFS Master region: unset
[ 2934.143907] cfg80211:   (start_freq - end_freq @ bandwidth), 
(max_antenna_gain, max_eirp), (dfs_cac_time)
[ 2934.143916] cfg80211:   (2402000 KHz - 2472000 KHz @ 4 KHz), (N/A, 2000 
mBm), (N/A)
[ 2934.143924] cfg80211:   (2457000 KHz - 2482000 KHz @ 4 KHz), (N/A, 2000 
mBm), (N/A)
[ 2934.143931] cfg80211:   (2474000 KHz - 2494000 KHz @ 2 KHz), (N/A, 2000 
mBm), (N/A)
[ 2934.143939] cfg80211:   (517 KHz - 525 KHz @ 16 KHz), (N/A, 2000 
mBm), (N/A)
[ 2934.143946] cfg80211:   (525 KHz - 533 KHz @ 16 KHz), (N/A, 2000 
mBm), (0 s)
[ 2934.143954] cfg80211:   (549 KHz - 573 KHz @ 16 KHz), (N/A, 2000 
mBm), (0 s)
[ 2934.143962] cfg80211:   (5735000 KHz - 5835000 KHz @ 8 KHz), (N/A, 2000 
mBm), (N/A)
[ 2934.143969] cfg80211:   (5724 KHz - 6372 KHz @ 216 KHz), (N/A, 0 
mBm), (N/A)
[ 2934.750435] wlan0: authenticate with 00:03:52:e4:30:f4
[ 2934.752361] wlan0: send auth to 00:03:52:e4:30:f4 (try 1/3)
[ 2934.756115] wlan0: authenticated
[ 2934.760082] wlan0: associate with 00:03:52:e4:30:f4 (try 1/3)
[ 2934.762131] wlan0: RX AssocResp from 00:03:52:e4:30:f4 (capab=0xc31 status=0 
aid=1)
[

Bug#768027: linux-image-3.16-3-686-pae: kernel BUG at linux-3.16.5/drivers/gpu/drm/i915/i915_gem_stolen.c:431!

2014-11-04 Thread Erich Schubert 
Package: src:linux
Version: 3.16.5-1
Severity: important

Booting a 3.16.5 leads to a locked up system. Login manager fails to start, and 
the console is dead.

This renders this kernel UNUSABLE on my Netbook.
Kernel 3.14 works fine.

This appears to be specific to the earlier Intel Atom CPUs?

Nov 04 11:02:14 kleinphi kernel: kernel BUG at 
/build/linux-I5YRU_/linux-3.16.5/drivers/gpu/drm/i915/i915_gem_stolen.c:431!
Nov 04 11:02:14 kleinphi kernel: invalid opcode:  [#1] SMP 
Nov 04 11:02:14 kleinphi kernel: Modules linked in: media i915(+) lpc_ich bcma 
mfd_core drm_kms_helper shpchp wmi drm ac batt
Nov 04 11:02:14 kleinphi kernel: CPU: 1 PID: 226 Comm: systemd-udevd Not 
tainted 3.16-3-686-pae #1 Debian 3.16.5-1
Nov 04 11:02:15 kleinphi kernel: Hardware name: ASUSTeK Computer INC. 
1016P/1015PE, BIOS 080110/06/2010
Nov 04 11:02:15 kleinphi kernel: task: f6cfe010 ti: f42de000 task.ti: f42de000
Nov 04 11:02:16 kleinphi kernel: EIP: 0060:[f835413b] EFLAGS: 00010206 CPU: 1
Nov 04 11:02:16 kleinphi kernel: EIP is at 
i915_gem_object_create_stolen_for_preallocated+0x20b/0x280 [i915]
Nov 04 11:02:16 kleinphi kernel: EAX: f4347800 EBX: f4274150 ECX: 001d4c00 EDX: 
001d4c00
Nov 04 11:02:16 kleinphi kernel: ESI: f427 EDI: 001d4c00 EBP: f42dfb60 ESP: 
f42dfb38
Nov 04 11:02:16 kleinphi kernel:  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
Nov 04 11:02:16 kleinphi kernel: CR0: 80050033 CR2: b75d0740 CR3: 36f6c000 CR4: 
07f0
Nov 04 11:02:16 kleinphi kernel: Stack:
Nov 04 11:02:16 kleinphi kernel:  f43479e4 0286 f4270004 0001 0001 
f4347800 001d4c00 f4cf8000
Nov 04 11:02:16 kleinphi kernel:  f4347800 f42dfbd4 f42dfbe0 f83833ab 00139000 
00071024 f42dfba8 f835ceab
Nov 04 11:02:16 kleinphi kernel:  0001 f4347800 f427 f43479e4 0002 
f4347a00  
Nov 04 11:02:16 kleinphi kernel: Call Trace:
Nov 04 11:02:17 kleinphi kernel:  [f83833ab] ? 
intel_modeset_init+0x82b/0x1210 [i915]
Nov 04 11:02:17 kleinphi kernel:  [f835ceab] ? 
i915_enable_pipestat+0xab/0x120 [i915]
Nov 04 11:02:17 kleinphi kernel:  [f83acbc5] ? i915_driver_load+0xae5/0xed0 
[i915]
Nov 04 11:02:17 kleinphi kernel:  [f83a9f40] ? 
i915_switcheroo_set_state+0x90/0x90 [i915]
Nov 04 11:02:17 kleinphi kernel:  [c137fa60] ? 
powercap_register_control_type+0x1c0/0x1c0
Nov 04 11:02:17 kleinphi kernel:  [c12515f0] ? cleanup_uevent_env+0x10/0x10
Nov 04 11:02:17 kleinphi kernel:  [c133acc4] ? get_device+0x14/0x30
Nov 04 11:02:17 kleinphi kernel:  [c146ea6b] ? klist_node_init+0x2b/0x40
Nov 04 11:02:17 kleinphi kernel:  [c146ead6] ? klist_add_tail+0x16/0x30
Nov 04 11:02:17 kleinphi kernel:  [c133c076] ? device_add+0x1d6/0x5a0
Nov 04 11:02:17 kleinphi kernel:  [f81f15ae] ? drm_dev_register+0x8e/0xe0 
[drm]
Nov 04 11:02:17 kleinphi kernel:  [f81f3b79] ? drm_get_pci_dev+0x79/0x1c0 
[drm]
Nov 04 11:02:17 kleinphi kernel:  [c1284c5f] ? pci_device_probe+0x6f/0xc0
Nov 04 11:02:17 kleinphi kernel:  [c11ca735] ? sysfs_create_link+0x25/0x40
Nov 04 11:02:17 kleinphi kernel:  [c133eb03] ? driver_probe_device+0x93/0x3a0
Nov 04 11:02:17 kleinphi kernel:  [c11ca467] ? sysfs_create_dir_ns+0x37/0x80
Nov 04 11:02:17 kleinphi kernel:  [c133eb03] ? driver_probe_device+0x93/0x3a0
Nov 04 11:02:17 kleinphi kernel:  [c11ca467] ? sysfs_create_dir_ns+0x37/0x80
Nov 04 11:02:17 kleinphi kernel:  [c1284ba1] ? pci_match_device+0xc1/0xe0
Nov 04 11:02:17 kleinphi kernel:  [c133eec1] ? __driver_attach+0x71/0x80
Nov 04 11:02:17 kleinphi kernel:  [c133ee50] ? __device_attach+0x40/0x40
Nov 04 11:02:17 kleinphi kernel:  [c133cfd7] ? bus_for_each_dev+0x47/0x80
Nov 04 11:02:17 kleinphi kernel:  [c133e60e] ? driver_attach+0x1e/0x20
Nov 04 11:02:17 kleinphi kernel:  [c133ee50] ? __device_attach+0x40/0x40
Nov 04 11:02:17 kleinphi kernel:  [c133e267] ? bus_add_driver+0x157/0x230
Nov 04 11:02:17 kleinphi kernel:  [f83ea000] ? 0xf83e9fff
Nov 04 11:02:17 kleinphi kernel:  [c133f589] ? driver_register+0x59/0xe0
Nov 04 11:02:17 kleinphi kernel:  [c1002132] ? do_one_initcall+0xc2/0x1f0
Nov 04 11:02:17 kleinphi kernel:  [f83ea000] ? 0xf83e9fff
Nov 04 11:02:17 kleinphi kernel:  [f832e000] ? 0xf832dfff
Nov 04 11:02:17 kleinphi kernel:  [c11492c8] ? __vunmap+0x88/0xf0
Nov 04 11:02:17 kleinphi kernel:  [c11492c8] ? __vunmap+0x88/0xf0
Nov 04 11:02:17 kleinphi kernel:  [c10c0f5b] ? load_module+0x1cbb/0x2390
Nov 04 11:02:17 kleinphi kernel:  [c10c1795] ? SyS_finit_module+0x75/0xc0
Nov 04 11:02:17 kleinphi kernel:  [c112ef5b] ? vm_mmap_pgoff+0x7b/0xa0
Nov 04 11:02:17 kleinphi kernel:  [c1479c9f] ? sysenter_do_call+0x12/0x12
Nov 04 11:02:17 kleinphi kernel: Code: 08 89 54 24 08 c7 44 24 04 80 3f 3c f8 
c7 04 24 a0 62 3b f8 89 44 24 10 8b 45 f0 89 44
Nov 04 11:02:18 kleinphi kernel: EIP: [f835413b] 
i915_gem_object_create_stolen_for_preallocated+0x20b/0x280 [i915] SS:ESP 0
Nov 04 11:02:20 kleinphi kernel: ---[ end trace 981ffc8e744747f8 ]---


** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation Atom Processor 
D4xx/D5xx/N4xx/N5xx DMI Bridge [8086:a010]

Bug#763155: linux-image-3.16-2-686-pae: linux 3.16-2-686-pae: i915 module crashes on Eeepc 1001p

2014-10-01 Thread Erich Schubert 
Package: src:linux
Version: 3.14.15-2
Followup-For: Bug #763155

Same thing here:
kernel BUG at 
/build/linux-Lep8DD/linux-3.16.3/drivers/gpu/drm/i915/i915_gem_stolen.c:431!
invalid opcode:  [#1] SMP
EIP is at i915_gem_object_create_stolen_for_preallocated+0x20b/0x280 [i915]

and resulting in a black screen. Today at least SysRq worked, last night that 
didn't work either.

Hardware: ASUS eeePC, similar model, 10something.
Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics 
Controller

Kernel package 3.16-1 works, and so does 3.14-2.

-- Package-specific info:
** Kernel log: boot messages should be attached
** Model information
not available

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation Atom Processor 
D4xx/D5xx/N4xx/N5xx DMI Bridge [8086:a010]
Subsystem: ASUSTeK Computer Inc. Device [1043:83ac]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- 
MAbort+ SERR- PERR- INTx-
Latency: 0
Capabilities: access denied
Kernel driver in use: agpgart-intel

00:02.0 VGA compatible controller [0300]: Intel Corporation Atom Processor 
D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [8086:a011] (prog-if 00 [VGA 
controller])
Subsystem: ASUSTeK Computer Inc. Device [1043:83ac]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- 
MAbort- SERR- PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 44
Region 0: Memory at f7e0 (32-bit, non-prefetchable) [size=512K]
Region 1: I/O ports at dc00 [size=8]
Region 2: Memory at d000 (32-bit, prefetchable) [size=256M]
Region 3: Memory at f7d0 (32-bit, non-prefetchable) [size=1M]
Expansion ROM at unassigned [disabled]
Capabilities: access denied
Kernel driver in use: i915

00:02.1 Display controller [0380]: Intel Corporation Atom Processor 
D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [8086:a012]
Subsystem: ASUSTeK Computer Inc. Device [1043:83ac]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- 
MAbort- SERR- PERR- INTx-
Latency: 0
Region 0: Memory at f7e8 (32-bit, non-prefetchable) [size=512K]
Capabilities: access denied

00:1b.0 Audio device [0403]: Intel Corporation NM10/ICH7 Family High Definition 
Audio Controller [8086:27d8] (rev 02)
Subsystem: ASUSTeK Computer Inc. Device [1043:841c]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- 
MAbort- SERR- PERR- INTx-
Latency: 0, Cache Line Size: 32 bytes
Interrupt: pin A routed to IRQ 45
Region 0: Memory at f7cf8000 (64-bit, non-prefetchable) [size=16K]
Capabilities: access denied
Kernel driver in use: snd_hda_intel

00:1c.0 PCI bridge [0604]: Intel Corporation NM10/ICH7 Family PCI Express Port 
1 [8086:27d0] (rev 02) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- 
MAbort- SERR- PERR- INTx-
Latency: 0, Cache Line Size: 32 bytes
Bus: primary=00, secondary=04, subordinate=04, sec-latency=0
I/O behind bridge: 1000-1fff
Memory behind bridge: 8000-801f
Prefetchable memory behind bridge: 8020-803f
Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- 
MAbort+ SERR- PERR-
BridgeCtl: Parity- SERR+ NoISA- VGA- MAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: access denied
Kernel driver in use: pcieport

00:1c.1 PCI bridge [0604]: Intel Corporation NM10/ICH7 Family PCI Express Port 
2 [8086:27d2] (rev 02) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- 
MAbort- SERR- PERR- INTx-
Latency: 0, Cache Line Size: 32 bytes
Bus: primary=00, secondary=02, subordinate=03, sec-latency=0
I/O behind bridge: 2000-2fff
Memory behind bridge: f800-fbff
Prefetchable memory behind bridge: f000-f6ff
Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- 
MAbort+ SERR- PERR-
BridgeCtl: Parity- SERR+ NoISA- VGA- MAbort- Reset- FastB2B-

Bug#625510: Broadcom 802.11 driver missing from 2.6.39-rc[45]

2011-05-03 Thread Erich Schubert 
Package: linux-2.6
Version: 2.6.39~rc5-1~experimental.1
Severity: normal
Tags: experimental

The driver for my other laptops broadcom BCM4313 seems to be missing.

Comparing the config files:
/boot/config-2.6.38-2-686:CONFIG_BRCM80211=m
/boot/config-2.6.38-2-686:CONFIG_BRCM80211_PCI=y
/boot/config-2.6.38-2-686:# CONFIG_BRCMFMAC is not set
/boot/config-2.6.39-rc5-686-pae:CONFIG_BRCM80211=m
/boot/config-2.6.39-rc5-686-pae:# CONFIG_BRCMSMAC is not set
/boot/config-2.6.39-rc5-686-pae:# CONFIG_BRCMFMAC is not set
/boot/config-2.6.39-rc5-686-pae:# CONFIG_BRCMDBG is not set

I wonder if maybe BRCMSMAC is the appropriate option now. A short search
revealed a patch to remove CONFIG_BRCM80211 since [...] renamed to brcmsmac.
Could you enable that option for the next upload? Thanks.
(Not sure what the full-mac cards are that the BRCMFMAC driver is for.  There
I saw something that you could not have SMAC und FMAC as module at the same
time (well, actually a patch that removes such a comment), but nothing yet of
the benefits of one over the other. Apparently fmac does more in the hardware
of the wireless card, but offering less features. Anyway, you could try
enabling both, unless there is some hint that this doesn't work?

Thank you for all your work on Debian!



-- 
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/20110504012331.4427.81575.reportbug@localhost.localdomain

Bug#567747: workaround for no-video on i915: vga=ext

2010-02-14 Thread Erich Schubert 
Hi,
I added vga=ext to my boot parameters, and with that my system boots
fine (although not in the usual vga=ext 50 lines vga mode, but it DOES
activate my i915 framebuffer?!? it's definitely running the native
1440x900 resolution of my screen.)
Maybe this prevents efifb from running (or resets the video after
GRUB?), and thus allows i915 to get the video device properly?

Regards,
Erich




-- 
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/1266147576.3843.4.ca...@hepcat

Bug#534635: linux-image-2.6.30-1-686: Intel xorg driver problems

2009-08-16 Thread Erich Schubert 
Package: linux-image-2.6.30-1-686
Severity: normal

fixed 534635 2.6.30-2
thanks

I think we can mark this bug fixed, since the mentioned commit was included in
2.6.30.1 and thus in the -2 debian package.

I'm still seeing the occasional xorg crash after resuming - most often like one
minute after resuming - where the best I can do is to use SysRq-unRaw,
Ctrl+Alt+Delete to shutdown which works in about 1/3 xorg crashes.
It never happens on a fresh system, only after at least one suspend/resume
cycle (5 resumes for the latest crash). I couldn't get any error message so
far.

But I believe this is a different issue, which might be in Xorg, not in
the kernel itself.

-- Package-specific info:
** Version:
Linux version 2.6.30-1-686 (Debian 2.6.30-5) (m...@debian.org) (gcc version 
4.3.3 (Debian 4.3.3-15) ) #1 SMP Mon Aug 3 16:18:30 UTC 2009

** Command line:
root=/dev/mapper/cryptroot ro quiet 

** Not tainted

** PCI devices:
00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 945GM/GMS, 
943/940GML Express Integrated Graphics Controller [8086:27a2] (rev 03) (prog-if 
00 [VGA controller])
Subsystem: Dell Device [1028:01d8]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- 
MAbort- SERR- PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 16
Region 0: Memory at eff0 (32-bit, non-prefetchable) [size=512K]
Region 1: I/O ports at eff8 [size=8]
Region 2: Memory at d000 (32-bit, prefetchable) [size=256M]
Region 3: Memory at efec (32-bit, non-prefetchable) [size=256K]
Expansion ROM at unassigned [disabled]
Capabilities: access denied

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.30-1-686 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages linux-image-2.6.30-1-686 depends on:
ii  debconf [debconf-2.0] 1.5.27 Debian configuration management sy
ii  initramfs-tools [linux-initra 0.93.4 tools for generating an initramfs
ii  module-init-tools 3.9-2  tools for managing Linux kernel mo

Versions of packages linux-image-2.6.30-1-686 recommends:
ii  libc6-i6862.9-24 GNU C Library: Shared libraries [i

Versions of packages linux-image-2.6.30-1-686 suggests:
ii  grub  0.97-56GRand Unified Bootloader (dummy pa
ii  grub-legacy [grub]0.97-56GRand Unified Bootloader (Legacy v
pn  linux-doc-2.6.30  none (no description available)

-- debconf information excluded



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#534635: linux-image-2.6.30-1-686: xorg crashes after resume on intel

2009-06-25 Thread Erich Schubert 
Package: linux-image-2.6.30-1-686
Version: 2.6.30-1
Severity: important

Hi,
Suspend/resume is no longer working reliable for me since a few versions.
Some time after resume, I start seeing glyph corruption or (more often)
the xserver just suddenly locks up.
The problem description pretty much matches this one:
  http://bugs.freedesktop.org/show_bug.cgi?id=20520
Which contains a fix submitted for 2.6.31 and the 2.6.30 stable series:

---
Fix has been pushed into the kernel:

commit  9e06dd39f2b6d7e35981e0d7aded618686b32ccb
drm/i915: correct suspend/resume ordering
---

Since the patch is quite basic - it moves 1 line of code a few
lines down - it would be a candidate for inclusion in the next kernel
package update, wouldn't it? After all, it should hopefully make
suspend/resume work reliable for me again, which is a major annoyance.

Thank you.

-- Package-specific info:
** Version:
Linux version 2.6.30-1-686 (Debian 2.6.30-1) (wa...@debian.org) (gcc version 
4.3.3 (Debian 4.3.3-11) ) #1 SMP Sun Jun 14 16:11:32 UTC 2009

** Command line:
root=/dev/mapper/cryptroot ro quiet 

** Not tainted

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.30-1-686 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages linux-image-2.6.30-1-686 depends on:
ii  debconf [debconf-2.0] 1.5.26 Debian configuration management sy
ii  initramfs-tools [linux-initra 0.93.3 tools for generating an initramfs
ii  module-init-tools 3.9-2  tools for managing Linux kernel mo

Versions of packages linux-image-2.6.30-1-686 recommends:
ii  libc6-i6862.9-18 GNU C Library: Shared libraries [i

Versions of packages linux-image-2.6.30-1-686 suggests:
ii  grub  0.97-53GRand Unified Bootloader (Legacy v
pn  linux-doc-2.6.30  none (no description available)

-- debconf information excluded



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#412188: Microphone on Dell 640m

2007-02-26 Thread Erich Schubert 
Hi,
With Kernel 2.6.20, the microphone jack works.

best regards,
Erich Schubert
-- 
   erich@(vitavonni.de|debian.org)--GPG Key ID: 4B3A135C(o_
Reality continues to ruin my life --- Calvin//\
 Die Mathematik muss man schon deswegen studieren, weil sie V_/_
 die Gedanken ordnet. --- Michail Wassiljewitsch Lomonossow



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#412188: linux-image-2.6.18-4-686: Microphone doesn't work on Dell 640m (Sigmatel / Intel HDA STAC92xx)

2007-02-24 Thread Erich Schubert 
Package: linux-image-2.6.18-4-686
Version: 2.6.18.dfsg.1-11
Severity: normal

The microphone on my Dell 640m doesn't work. Sound otherwise is okay,
but trying to record produces an empty file (so it probably isn't just
some volume setting...)
There are various reports on the same issue on the net.

00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High
Definition Audio Controller (rev 01)

alsamixer says SigmaTel STAC9200

Bug #2901 in ALSA bugtracking probably is relevant.
https://bugtrack.alsa-project.org/alsa-bug/view.php?id=2901

Also this one; I didn't try alsa 1.0.14rc1 from experimental yet
https://bugtrack.alsa-project.org/alsa-bug/view.php?id=2688

-- System Information:
Debian Release: 4.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-4-686
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)

Versions of packages linux-image-2.6.18-4-686 depends on:
ii  coreutils 5.97-5.3   The GNU core utilities
ii  debconf [debconf-2.0] 1.5.11 Debian configuration management sy
ii  initramfs-tools [linux-initra 0.85e  tools for generating an initramfs
ii  module-init-tools 3.3-pre4-2 tools for managing Linux kernel mo
ii  yaird [linux-initramfs-tool]  0.0.12-18  Yet Another mkInitRD

Versions of packages linux-image-2.6.18-4-686 recommends:
ii  libc6-i6862.5-0exp3  GNU C Library: Shared libraries [i

-- debconf information excluded


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#412153: linux-image-2.6.18-4-686: WPA fails on SMP systems under heavy load

2007-02-23 Thread Erich Schubert 
Package: linux-image-2.6.18-4-686
Version: 2.6.18.dfsg.1-11
Severity: normal

I was having problems with WPA-encrypted networks in heavy load
conditions, e.g. when transferring files from a local server.
Every minute I would be disconnected with the error messages
---
TKIP: ICV error detected: STA=...
N/A: Michael MIC verification failed for MSDU from ... keyidx=0
wifi0: MSDU decryption/MIC verification failed (SA=... keyidx=0)
TKIP: received packet without ExtIV flag from ...
---
And after about 1 minute, the wireless reconnected again.

After googling a while, I found this page:
http://www.tuxyturvy.com/blog/index.php?/archives/23-Using-the-IPW3945-with-Linux,-WPA,-and-the-SMP-Kernel.html

That is exactly my setup, and my error. I don't know which ieee80211
version is included with the 2.6.18 kernel, but I'm experiencing this
problem, and there is one more comment mentioning 2.6.18

Apparently, this is the same bug in Ubuntu:
https://launchpad.net/distros/ubuntu/+source/linux-source-2.6.17/+bug/56894

I had a quick look at the 2.6.20 changelog, and it contains
---
commit 4d1feabcbf41f875447a392015acd0796f57baf6
Author: Ulrich Kunitz [EMAIL PROTECTED]
Date:   Sun Dec 10 11:13:12 2006 -0800

[PATCH] zd1211rw: Call ieee80211_rx in tasklet

The driver called ieee80211_rx in hardware interrupt context.  This has
been against the intention of the ieee80211_rx function.  It caused a bug
in the crypto routines used by WPA.  This patch calls ieee80211_rx in a
tasklet.

Signed-off-by: Ulrich Kunitz [EMAIL PROTECTED]
Signed-off-by: Andrew Morton [EMAIL PROTECTED]
Signed-off-by: John W. Linville [EMAIL PROTECTED]
---
That could be the relevant changeset, I don't know. There are some more 80211
related patches that could be relevant.
Anyway, not having reliable networking is a bigger issue for me...

-- System Information:
Debian Release: 4.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-4-686
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)

Versions of packages linux-image-2.6.18-4-686 depends on:
ii  coreutils 5.97-5.3   The GNU core utilities
ii  debconf [debconf-2.0] 1.5.11 Debian configuration management sy
ii  initramfs-tools [linux-initra 0.85e  tools for generating an initramfs
ii  module-init-tools 3.3-pre4-2 tools for managing Linux kernel mo
ii  yaird [linux-initramfs-tool]  0.0.12-18  Yet Another mkInitRD

Versions of packages linux-image-2.6.18-4-686 recommends:
ii  libc6-i6862.5-0exp3  GNU C Library: Shared libraries [i

-- debconf information excluded


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#402707: reproducible: hash check failed

2006-12-16 Thread Erich Schubert 
Hi,
I just wanted to note that I've been seeing the same error on my
unstable amd64 system for a few days now, with stock Debian kernel
version 2.6.18-3-amd64
I'm nor sure which kernel revision introduced the problem, but it likely
was on december 12th where it first occurred for me (I'm not using
torrents that often)

best regards,
Erich Schubert
-- 
   erich@(vitavonni.de|debian.org)--GPG Key ID: 4B3A135C(o_
 The future is here. It's just not evenly distributed yet.  //\
Der Anfang aller Erkenntnis ist das Staunen. --- AristotelesV_/_



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Issue with Debian Kernels and SELinux

2005-11-10 Thread Erich Schubert 
Hello Debian Kernel Maintainers,
There is another issue with SELinux on current Debian kernels.
Basically, the selinux stuff for sockets is not working as intended, but
reporting some odd security violations. I couldn't reproduce them with
my own kernels, so I sent the Debian .config upstream.
Stephen Smalley of NSA SELinux fame has tracked it down to the
following:

 Ok, I've tracked down the cause of this problem in the Debian kernels:
 they are disabling CONFIG_SECURITY_NETWORK, which disables all of the
 LSM socket hooks.  Thus, SELinux never gets a chance to classify the
 socket inodes as socket objects via its selinux_socket_* hook functions,
 and SELinux can no longer distinguish them from sock files at
 d_instantiate time because of the removal of the i_sock field in 2.6.12
 (which we didn't view as a problem at the time because we had the socket
 hooks to address the issue).
 
 I'd suggest asking the Debian kernel maintainers to entertain the notion
 of enabling CONFIG_SECURITY_NETWORK.  If they are being driven by
 performance considerations (and have actual data to show that the mere
 presence of the LSM hooks is having real impact, even with selinux=0),
 then possibly CONFIG_SECURITY_NETWORK could be tightened up to only
 apply to the hooks that are on the critical path (e.g. sock_rcv_skb is
 likely the largest concern).

best regards,
Erich Schubert
-- 
erich@(vitavonni.de|debian.org)--GPG Key ID: 4B3A135C(o_
The best things in life are free: Friendship and Love.   //\
   Die kürzeste Verbindung zwischen zwei Menschen ist ein Lächeln.   V_/_

Bug#335601: compaq arrays with ida

2005-11-07 Thread Erich Schubert 
Hi,
 + if ($name =~ /^ida!c\d+d\d+$/) {
 + ModProbe::addModules ($actions, [ cpqarray ]);
 + $actions-add(mkbdev, $device-yspecial, sysname = $name);
 + return 1;
 + }

That is what I had inserted myself. Works fine.

best regards,
Erich Schubert
-- 
erich@(vitavonni.de|debian.org)--GPG Key ID: 4B3A135C(o_
   There was never a good war or a bad peace. - Benjamin Franklin//\
  Bei dem Freunde halte still, der dich nur, nicht das deine will.   V_/_



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#335601: compaq arrays with ida

2005-11-02 Thread Erich Schubert 
Hi,
the compaq smart arrays I have use ida:
/dev/ida/c0d0p5 on / type ext3 (rw,errors=remount-ro)
/dev/ida/c0d0p1 on /boot type ext2 (rw)
/dev/ida/c0d0p6 on /home type ext3 (rw,nodev)
as well as /sys/block/ida!c0d0
The module needed is cpqarray

Greetings,
Erich Schubert
-- 
erich@(vitavonni.de|debian.org)--GPG Key ID: 4B3A135C   (o_
   There was never a good war or a bad peace. - Benjamin Franklin   //\
Glück gleicht durch Höhe aus, was ihm an Länge fehlt.   V_/_
--- Robert Lee Frost

Bug#333834: linux-2.6: Please enabled audit support, selinux is pretty much unuseable otherwise.

2005-10-13 Thread Erich Schubert 
Package: linux-2.6
Severity: normal

While you can run SELinux just fine without audit enabled, it's next to
impossible to write or debug SELinux policy without it. But SELinux
hasn't reached the stage where there is a perfect policy for everything,
so users need to have the ability to debug their policy (or write new
for applications htere is no policy for yet)

Please enable audit in the debian kernels ASAP.

The kernels are unuseable for typical SELinux deployment otherwise.

Thank you.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#255406: kernel-source-2.4.26: Kernel crash when removing interface from wrong bridge group

2004-06-20 Thread Erich Schubert 
Package: kernel-source-2.4.26
Severity: normal

Some time ago i found a kernel crash in 2.4.x and reported it to LKML.
Unfortunately i never recieved a reply, and i didn't see it in recent
pre-releases of the 2.4.x kernel.

To verify your system is vulnerable (need bridge support):
$ brctl addbr br0
$ brctl addbr br1
$ brctl addif br0 eth0
$ brctl delif br1 eth0
(note br1 in last line, not br0! Deleting from the wrong bridge triggers
the kernel crash.)

This is a 1:1 backport (100% copypaste) from 2.6.5 of the fix.
Verify yourself, grab the file from 2.6.5, go to the function, copy the
code, paste it and the issue is done. Returns einval on invalid
requests instead of causing an inconsistency and a panic.

(fixed sometime in 2.5.x it seems; it might be worth looking at when
this was fixed - it might contain other fixes, too.)

--- net/bridge/br_if.c.2.4.21   2004-05-20 14:34:50.0 +0200
+++ net/bridge/br_if.c  2004-05-20 14:37:22.0 +0200
@@ -254,6 +254,10 @@
 int br_del_if(struct net_bridge *br, struct net_device *dev)
 {
int retval;
+   struct net_bridge_port *p;
+
+   if ((p = dev-br_port) == NULL || p-br != br)
+   return -EINVAL;
 
br_write_lock_bh(BR_NETPROTO_LOCK);
write_lock(br-lock);


-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.6
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED]