Bug#620603: linux-image-2.6.38-2-amd64: console still stays black with linux-image-2.6.39-rc5-amd64

[Andreas Horter]

Package: linux-2.6
Version: 2.6.38-3
Followup-For: Bug #620603

Today I installed linux-image-2.6.39-rc5-amd64 from experimental and
got the same black screen as with 2.6.38-3. 
Is there anything I can provide to get this fixed?



-- 
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/20110505094142.4413.35858.report...@apfel.xlart.kmem.de

Re: New maintainer for ARM

[Rtp]

Martin Michlmayr  writes:

Hi,

> Here are some outstanding bugs/tasks regarding the ARM kernels:
>
> #604013 base: "ls -al" on armel inside loopback mounted ISO image failes with 
> -1 ENOMEM
> Nobody has been able to reproduce and the submitter doesn't respond.
> Maybe ping the submitter again, close if no reply.

I remember trying to reproduce it at the time the bug was opened and
never managed to reproduce it.

>
> #622325 linux-image-2.6.38-2-orion5x: Problem With I2C
> Forward upstream, bisect.

I've a mips board with a m41t80 but can't use it atm so I've looked at
the code and there's no obvious troubles with the driver. In 2.6.38 and
newer kernels, there has been a bunch of rtc breakages. See the number
of crash fixes in [1]. I've made a kernel for dns323 with small changes
in order to help debugging. I plan to ping some bug reporter in order to
make him test it as I can't test it myself. I hope it'll help and
at least confirm it's really a rtc bug.

>
> #614593 Please add new armel kernel flavour for the Marvell DB-78x00-BP 
> Development Board
> I still believe this is a bad idea since it will make kernel builds
> slower for very little gain (there are no users of this board outside
> of our buildd infrastructure).  A similar problem exists on MIPS and I
> think Ben wanted to look into the possibility of adding configs
> without enabling them by default but providing an easy way to compile
> the image.

I can't comment on that one but at least, the solution of adding support
but not enabling it by default may be a solution.

>
> squashfs: #613658  There are some options that may have to be selected
> on ARM.

hmm... I didn't notice this bug. The ARM options are enabled by default
like the other options. I don't know if it can have some side effects at
run time. I guess it should be fine otherwise some Kconfig patching will
be needed (I'm thinking of the ARMTHUMB decoder option)

>
> Also: look through open bugs to see if there are other ARM related
> issues.

[1] http://patchwork.ozlabs.org/project/rtc-linux/list/

Arnaud


-- 
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/87sjsttqxe@lebrac.rtp-net.org

Bug#620603: linux-image-2.6.38-2-amd64: console still stays black with linux-image-2.6.39-rc5-amd64

[Jonathan Nieder]

Andreas Horter wrote:

> Today I installed linux-image-2.6.39-rc5-amd64 from experimental and
> got the same black screen as with 2.6.38-3. 
> Is there anything I can provide to get this fixed?

Could you file a separate bug (since it seems you do not have identical
hardware to Ilmari), attaching dmesg output?

Also, do you remember what version did work (if any)?  That can be
very useful information in a bug report.

Thanks,
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/20110505095503.GA14786@elie

Bug#624549: bug in radeon driver module of linux 2.6.38 (since 2.6.35)

[Martin Teufel]

Hi,

I want and have to rectify my last mail:
This patch is obviously not applied in 2.6.38-bpo.2 because I get:
[5.924366] drm: Unknown parameter `edid_strict'
Could you get this applied to the next version of a linux backport?

Best regards,
Martin


On Tue, May 03, 2011 at 10:29:27PM +0200, Martin Teufel wrote:
> Hi together,
> 
> does someone know if this patch has been applied already to
> linux-image-2.6.38-bpo.2-amd64 (2.6.38-3~bpo60+1)?
> I installed this image yesterday and had the idea to test the
> drm.edid_strict=0 parameter on it today. - It works like a charm. ;)
> Dunno why my patch didn't work... (But I don't have the time nor the
> mood to track this down atm.)
> 
> Nevertheless: Thank you for trying to help me. - And sorry for
> bugreporting this twice and not cc-ing the last mail. Reason for the
> first was that I never used reportbug on this machine before and
> therefore had no .reportbugrc on it which caused in a nonexistent mail
> address due to some circumstances.
> 
> Best regards,
> Martin


pgpqYJjKngagh.pgp
Description: PGP signature

Bug#613073: Perhaps fixed in 2.6.32-34

[Sebastien Koechlin]

On Thu, Apr 21, 2011 at 09:41:16AM +0100, Ian Campbell wrote:
> If you are able to reproduce this it would be very much appreciated if
> you could test on 2.6.32-34 once it is uploaded to
> stable-proposed-updates.

Thanks,

As 2.6.32-34 is now in stable-proposed-updates, I'm planning a test session
on this production server May 14.

-- 
Seb, autocuiseur



-- 
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/20110505110003.ga30...@koocotte.org

Re: 2.6.39-5-686-pae

[Ben Hutchings]

On Wed, 2011-05-04 at 22:23 -0700, Will Set wrote:
> Ben
> Max
> Julien
> Kibi 
> Sven
>  I''m getting a segfault with Bug listed in dmesg, but different after 
> today's upgrade than it was yesterday.
> I'm very happy to wait till tomorrow for a possible fix to be uploaded.
> I'm also very happy to file a bug if anyone wants to look at my old intel 
> i865 
> chipset mobo  with nvidai 6600 /256MB agp card showing
> a few boot issues ( I think loading modules - but it changes daily, so it 
> hard 
> for me to say for sure.

Please use reportbug.

Ben.

-- 
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.


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

Re: Problem with kernel 2.6.38

[Ben Hutchings]

On Thu, 2011-05-05 at 13:50 +0800, Paolo Scarabelli wrote:
> Hi, I apologize in advance if this is the wrong place to ask.
> 
> I have a weird problem with a Debian testing (Wheezy) install,
> gnome-settings-daemon keeps crashing whenever I boot with kernel 2.6.38.
> 
> With other kernel releases (2.6.32 and 2.6.39) I have no problem at all,
> I initially filed a bug report (#619457) with the Debian Gnome
> maintainers [1] but I now suspect it could be a bug in a kernel module
> so I would like to reassign it to the Debian Kernel Team.
[...]

It sounds like there are 2 bugs:

1. The kernel is reporting spurious changes in the connected displays
(hence the flickering between 2x3 and 2x4 workspaces).
2. There is a race condition in handling these changes in
gnome-settings-daemon which causes it to crash.

Therefore, please clone your bug report and reassign the clone.

Ben.

-- 
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.


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

Bug#620603: linux-image-2.6.38-2-amd64: console still stays black with linux-image-2.6.39-rc5-amd64

[Andreas Horter]

Jonathan Nieder wrote:

> Could you file a separate bug (since it seems you do not have identical
> hardware to Ilmari), attaching dmesg output?

Done, it is bug #625727



-- 
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/20110505135048.gb1...@nerdhammel.gnuher.de

Processed (with 1 errors): Re: [regression] nouveau causes GPU lockup when upgrading 2.6.39 rc4 -> rc5

[Debian Bug Tracking System]

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

> notforwarded 625279
Bug #625279 [linux-2.6] [regression] nouveau causes GPU lockup when upgrading 
2.6.39 rc4 -> rc5
Unset Bug forwarded-to-address
> retitle [regression] Debian patches cause nouveau bootup GPU lockup with 
> 2.6.39 rc5
Unknown command or malformed arguments to command.

> thanks
Stopping processing here.

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

Bug#603066: linux-headers-2.6.39-rc5-amd64 depends on linux-kbuild-2.6.39

[Alexandra N. Kossovsky]

Hello.

Packages linux-headers-2.6.39-* in experimental are useless, since they
depend on linux-kbuild-2.6.39.

I do not use module-assistant, but I need kernel headers to build
third-party modules.  If the only supported way to do it is to download
linux-source-2.6.39, then, possibly, linux-headers-* should not be
uploaded to experimental at all?

Thank you for your work in Debian!
-- 
Alexandra N. Kossovsky
OKTET Labs (http://www.oktetlabs.ru/)
Phones: +7(921)956-42-86(mobile) +7(812)783-21-91(office)
e-mail: sa...@oktetlabs.ru



-- 
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/20110505142402.ga21...@oktetlabs.ru

Bug#625279: [regression] drm-nouveau-Use-pci_dma_mapping_error.patch causes GPU lockup on boot

[Paul Wise]

retitle 625279 [regression] drm-nouveau-Use-pci_dma_mapping_error.patch causes 
GPU lockup on boot
thanks

On Thu, 2011-05-05 at 22:19 +0800, Paul Wise wrote:

> I conclude that it is an issue with the Debian patches.

Mainline 2.6.39 rc5 plus the following patch to gives GPU lockup:

debian/patches/bugfix/all/drm-nouveau-Use-pci_dma_mapping_error.patch

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


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

Processed: Re: [regression] drm-nouveau-Use-pci_dma_mapping_error.patch causes GPU lockup on boot

[Debian Bug Tracking System]

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

> retitle 625279 [regression] drm-nouveau-Use-pci_dma_mapping_error.patch 
> causes GPU lockup on boot
Bug #625279 [linux-2.6] [regression] nouveau causes GPU lockup when upgrading 
2.6.39 rc4 -> rc5
Changed Bug title to '[regression] drm-nouveau-Use-pci_dma_mapping_error.patch 
causes GPU lockup on boot' from '[regression] nouveau causes GPU lockup when 
upgrading 2.6.39 rc4 -> rc5'
> thanks
Stopping processing here.

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

Bug#625738: >2TB SCSI disk size not recognized correctly

[Greg Wooledge]

Package: linux-image-2.6.32-5-686
Version: 2.6.32-31

I upgraded a machine from Lenny to Squeeze, and it failed to mount one
of the disks.  Here is a large swath of dmesg from the failing kernel:

[0.00] Linux version 2.6.32-5-686 (Debian 2.6.32-31) 
(b...@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Tue Mar 8 
21:36:00 UTC 2011

...

[3.914558] scsi 4:0:0:0: Direct-Access   R0.0 
PQ: 0 ANSI: 5
[3.914564] scsi 4:0:0:0: Information Units disabled by blacklist
[3.914576] scsi target4:0:0: Beginning Domain Validation
[3.914594] scsi5 : ioc1: LSI53C1030 C0, FwRev=01032700h, Ports=1, MaxQ=255, 
IRQ=18
[4.566692] scsi target4:0:0: Ending Domain Validation
[4.566756] scsi target4:0:0: FAST-80 WIDE SCSI 160.0 MB/s DT (12.5 ns, 
offset 127)
[5.728614] scsi 4:0:5:0: Sequential-Access CERTANCE ULTRIUM 31770 
PQ: 0 ANSI: 4
[5.728625] scsi target4:0:5: Beginning Domain Validation
[6.058280] scsi target4:0:5: Domain Validation skipping write tests
[6.058283] scsi target4:0:5: Ending Domain Validation
[6.058345] scsi target4:0:5: FAST-80 WIDE SCSI 160.0 MB/s DT (12.5 ns, 
offset 127)
[8.310955] scsi 3:0:0:0: Direct-Access ATA  SEAGATE ST32500N n/a  
PQ: 0 ANSI: 5
[8.325016] sd 2:0:0:0: [sda] 488390625 512-byte logical blocks: (250 GB/232 
GiB)
[8.325071] sd 2:0:0:0: [sda] Write Protect is off
[8.325075] sd 2:0:0:0: [sda] Mode Sense: 00 3a 00 00
[8.325098] sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, 
doesn't support DPO or FUA
[8.325233]  sda:
[8.332152] sd 3:0:0:0: [sdc] 488390625 512-byte logical blocks: (250 GB/232 
GiB)
[8.332201] sd 3:0:0:0: [sdc] Write Protect is off
[8.332204] sd 3:0:0:0: [sdc] Mode Sense: 00 3a 00 00
[8.332225] sd 3:0:0:0: [sdc] Write cache: enabled, read cache: enabled, 
doesn't support DPO or FUA
[8.332365]  sdc:
[8.332488] st: Version 20081215, fixed bufsize 32768, s/g segs 256
[8.09] st 4:0:5:0: Attached scsi tape st0
[8.12] st 4:0:5:0: st0: try direct i/o: yes (alignment 512 B)
[8.343674] sd 4:0:0:0: [sdb] 4294967296 512-byte logical blocks: (2.19 
TB/2.00 TiB)
[8.344551] usbcore: registered new interface driver hiddev
[8.344741] sd 4:0:0:0: [sdb] Write Protect is off
[8.344745] sd 4:0:0:0: [sdb] Mode Sense: bf 00 00 08
[8.345180] sd 4:0:0:0: [sdb] Write cache: enabled, read cache: enabled, 
doesn't support DPO or FUA
[8.345421]  sda1 sda2
[8.345672] sd 2:0:0:0: [sda] Attached SCSI disk
[8.345973] sd 4:0:0:0: [sdb] 13651132416 512-byte logical blocks: (6.98 
TB/6.35 TiB)
[8.347305] sdb: detected capacity change from 219902322 to 6989379796992
[8.347310]  sdb:
[8.348685] Errataon LSI53C1030 occurred.sc->req_bufflen=0x1000,xfer_cnt=0x00
[8.348837] Errataon LSI53C1030 occurred.sc->req_bufflen=0x1000,xfer_cnt=0x00
[8.348986] Errataon LSI53C1030 occurred.sc->req_bufflen=0x1000,xfer_cnt=0x00
[8.349135] Errataon LSI53C1030 occurred.sc->req_bufflen=0x1000,xfer_cnt=0x00
[8.349286] Errataon LSI53C1030 occurred.sc->req_bufflen=0x1000,xfer_cnt=0x00
[8.349435] Errataon LSI53C1030 occurred.sc->req_bufflen=0x1000,xfer_cnt=0x00
[8.349442] sd 4:0:0:0: [sdb] Unhandled error code
[8.349444] sd 4:0:0:0: [sdb] Result: hostbyte=DID_SOFT_ERROR 
driverbyte=DRIVER_OK
[8.349449] sd 4:0:0:0: [sdb] CDB: Read(16): 88 00 00 00 00 03 2d ab bf f8 
00 00 00 08 00 00
[8.349461] end_request: I/O error, dev sdb, sector 13651132408
[8.349520] Buffer I/O error on device sdb, logical block 1706391551
[8.349732] Errataon LSI53C1030 occurred.sc->req_bufflen=0x1000,xfer_cnt=0x00
[8.349886] Errataon LSI53C1030 occurred.sc->req_bufflen=0x1000,xfer_cnt=0x00
[8.350046] Errataon LSI53C1030 occurred.sc->req_bufflen=0x1000,xfer_cnt=0x00
[8.350196] Errataon LSI53C1030 occurred.sc->req_bufflen=0x1000,xfer_cnt=0x00
[8.350347] Errataon LSI53C1030 occurred.sc->req_bufflen=0x1000,xfer_cnt=0x00
[8.350497] Errataon LSI53C1030 occurred.sc->req_bufflen=0x1000,xfer_cnt=0x00
[8.350503] sd 4:0:0:0: [sdb] Unhandled error code
[8.350505] sd 4:0:0:0: [sdb] Result: hostbyte=DID_SOFT_ERROR 
driverbyte=DRIVER_OK
[8.350509] sd 4:0:0:0: [sdb] CDB: Read(16): 88 00 00 00 00 03 2d ab bf f8 
00 00 00 08 00 00
[8.350520] end_request: I/O error, dev sdb, sector 13651132408
[8.350576] Buffer I/O error on device sdb, logical block 1706391551
[8.350639] Alternate GPT is invalid, using primary GPT.
[8.350642]  sdb1
[8.353476]  sdc1 sdc2
[8.353538] input: Virtual USB MULTIMEDIA KEYBOARD as 
/devices/pci:00/:00:02.0/usb2/2-1/2-1:1.0/input/input0
[8.353610] generic-usb 0003:0B38:0003.0001: input,hidraw0: USB HID v1.10 
Keyboard [Virtual USB MULTIMEDIA KEYBOARD] on usb-:00:02.0-1
/input0
[8.353792] sd 3:0:0:0: [sdc] Attached SCSI disk
[8.363449] input: Virtual USB MULTIMEDIA KEYBOARD as 
/devices/pci:00/:00:

Bug#603066: linux-headers-2.6.39-rc5-amd64 depends on linux-kbuild-2.6.39

[Ben Hutchings]

On Thu, May 05, 2011 at 06:24:02PM +0400, Alexandra N. Kossovsky wrote:
> Hello.
> 
> Packages linux-headers-2.6.39-* in experimental are useless, since they
> depend on linux-kbuild-2.6.39.
> 
> I do not use module-assistant, but I need kernel headers to build
> third-party modules.

I wonder what those could be? :-)

> If the only supported way to do it is to download
> linux-source-2.6.39, then, possibly, linux-headers-* should not be
> uploaded to experimental at all?
 
I suppose we could disable them when packaging release candidates.

However it is usually easy to build the linux-kbuild package, per
.

Ben.

-- 
Ben Hutchings
We get into the habit of living before acquiring the habit of thinking.
  - Albert Camus



-- 
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/20110505153405.gk2...@decadent.org.uk

Processed: [bts-link] source package linux-2.6

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package linux-2.6
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #619433 (http://bugs.debian.org/619433)
> #  * http://bugzilla.kernel.org/show_bug.cgi?id=31872
> #  * remote status changed: NEEDINFO -> CLOSED
> #  * remote resolution changed: (?) -> CODE-FIX
> #  * closed upstream
> tags 619433 + fixed-upstream
Bug #619433 [linux-2.6] linux-image-2.6.38-1-686: early crash with ACPI 
(regression)
Added tag(s) fixed-upstream.
> usertags 619433 - status-NEEDINFO
Bug#619433: linux-image-2.6.38-1-686: early crash with ACPI (regression)
Usertags were: status-NEEDINFO.
Usertags are now: .
> usertags 619433 + status-CLOSED resolution-CODE-FIX
Bug#619433: linux-image-2.6.38-1-686: early crash with ACPI (regression)
There were no usertags set.
Usertags are now: resolution-CODE-FIX status-CLOSED.
> # remote status report for #622753 (http://bugs.debian.org/622753)
> #  * http://bugzilla.kernel.org/show_bug.cgi?id=31452
> #  * remote status changed: NEEDINFO -> CLOSED
> #  * remote resolution changed: (?) -> CODE-FIX
> #  * closed upstream
> tags 622753 + fixed-upstream
Bug #622753 [linux-2.6] linux-image-2.6.38-2-amd64: Connection over wlan slows 
down and dies
Added tag(s) fixed-upstream.
> usertags 622753 - status-NEEDINFO
Bug#622753: linux-image-2.6.38-2-amd64: Connection over wlan slows down and dies
Usertags were: status-NEEDINFO.
Usertags are now: .
> usertags 622753 + status-CLOSED resolution-CODE-FIX
Bug#622753: linux-image-2.6.38-2-amd64: Connection over wlan slows down and dies
There were no usertags set.
Usertags are now: resolution-CODE-FIX status-CLOSED.
> thanks
Stopping processing here.

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

[bts-link] source package linux-2.6

[bts-link-upstream]

#
# bts-link upstream status pull for source package linux-2.6
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
#

user bts-link-upstr...@lists.alioth.debian.org

# remote status report for #619433 (http://bugs.debian.org/619433)
#  * http://bugzilla.kernel.org/show_bug.cgi?id=31872
#  * remote status changed: NEEDINFO -> CLOSED
#  * remote resolution changed: (?) -> CODE-FIX
#  * closed upstream
tags 619433 + fixed-upstream
usertags 619433 - status-NEEDINFO
usertags 619433 + status-CLOSED resolution-CODE-FIX

# remote status report for #622753 (http://bugs.debian.org/622753)
#  * http://bugzilla.kernel.org/show_bug.cgi?id=31452
#  * remote status changed: NEEDINFO -> CLOSED
#  * remote resolution changed: (?) -> CODE-FIX
#  * closed upstream
tags 622753 + fixed-upstream
usertags 622753 - status-NEEDINFO
usertags 622753 + status-CLOSED resolution-CODE-FIX

thanks


--
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/20110505163748.7683.34959.btsl...@busoni.debian.org

Bug#625752: linux-latest-2.6: Add sys_accept4 to arm

[Johannes Schauer]

Package: linux-latest-2.6
Version: 2.6.32+27~bpo50+1
Severity: normal

the accept4 syscall is available since 2.6.28 - at least
for x86 architecture.
Support for accept4 on arm was added for 2.6.36 and the
patch is very simple:

commit 21d93e2e29722d7832f61cc56d73fb953ee6578e
Author: Mikael Pettersson 
Date:   Sun, 15 Aug 2010 09:47:23 +

I discovered that when updating udev from 167 to 168 (on
a 2.6.32 kernel). Udev from 168 onward requires accept4.

After applying the patch accept4 worked and so did udev.

Since accept4 is supposed to be in the kernel since
2.6.28 it should at least be put into the .32 stable
version for arm.



-- 
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/20110505171546.14405.30793.reportbug@hoothoot

Bug#586270: linux-image-2.6.32-5-686: evo n610c compaq laptop fails to go into suspend mode

[Moritz Mühlenhoff]

On Thu, Jun 17, 2010 at 08:24:17PM -0400, Andres Cimmarusti wrote:
> Package: linux-2.6
> Version: 2.6.32-15
> Severity: important
> Tags: sid squeeze
> 
> After recent updates, I can no longer successfully go into suspend moved with 
> this
> laptop. The kernel log shows several backtraces.

Sorry for the late followup.

Does this still occur with more recent kernels, i.e. the final Squeeze kernel or
more recent versions from backports/testing/sid?

Cheers,
Moritz



-- 
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/20110505204741.GA27454@pisco.westfalen.local

Bug#624549: bug in radeon driver module of linux 2.6.38 (since 2.6.35)

[Jonathan Nieder]

Martin Teufel wrote:
> On Tue, May 03, 2011 at 10:29:27PM +0200, Martin Teufel wrote:

>> I installed this image yesterday and had the idea to test the
>> drm.edid_strict=0 parameter on it today. - It works like a charm. ;)
[...]
> I want and have to rectify my last mail:
> This patch is obviously not applied in 2.6.38-bpo.2 because I get:
> [5.924366] drm: Unknown parameter `edid_strict'

So that leaves us with a puzzle: does that mean that 2.6.38-3~bpo60+1
fixed it (forgetting about the drm.edid_strict parameter for a moment)?

> Could you get this applied to the next version of a linux backport?

Ah, sorry I wasn't clearer before.  The edid_strict patch is something
Alex had been thinking about but it is not in appliable shape (it does
not have strict enough buffer size checks to cope with e.g.
maliciously made hardware).  And of course it's even better if it is
possible through a driver change to get an uncorrupted edid.



-- 
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/20110505205631.GA4758@elie

Bug#624549: bug in radeon driver module of linux 2.6.38 (since 2.6.35)

[Martin Teufel]

Hi,

On Thu, May 05, 2011 at 03:56:31PM -0500, Jonathan Nieder wrote:
> So that leaves us with a puzzle: does that mean that 2.6.38-3~bpo60+1
> fixed it (forgetting about the drm.edid_strict parameter for a moment)?
no. Without drm.edid_strict=0 the error occurs (every 10 seconds ...).
With drm.edid_strict=0 given, the error doesn't occur but KMS gets
disabled (don't know why and figured this out only today, when I got to
the machine (did this test via a serial line behind a ssh connection on
tuesday).

> Ah, sorry I wasn't clearer before.  The edid_strict patch is something
> Alex had been thinking about but it is not in appliable shape (it does
> not have strict enough buffer size checks to cope with e.g.
> maliciously made hardware).  And of course it's even better if it is
> possible through a driver change to get an uncorrupted edid.
Hm, I see (and agree).
So we/I'll wait for a fix from upstream.
I got back to drm_kms_helper.poll=0 for now.

Regards,
Martin


pgpMLOGHxYeu7.pgp
Description: PGP signature

Bug#624549: bug in radeon driver module of linux 2.6.38 (since 2.6.35)

[Jonathan Nieder]

Martin Teufel wrote:

> Hm, I see (and agree).
> So we/I'll wait for a fix from upstream.
> I got back to drm_kms_helper.poll=0 for now.

Mm, I have read your report carefully enough yet, but: did you get any
response upstream?  I would suggest filing a bug at [1], product DRI,
component DRM/Radeon, version unspecified (yes, this is the place for
kernel DRI bugs), mentioning which versions worked and did not work,
pointing to your lkml message and attaching logs.

That way one could be sure upstream knows about the problem. :)

If you do so, do please send us the bug number.

Thanks and regards,
Jonathan

[1] https://bugs.freedesktop.org/enter_bug.cgi?product=DRI



-- 
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/20110505220705.GB5147@elie

Bug#624549: bug in radeon driver module of linux 2.6.38 (since 2.6.35)

[Jonathan Nieder]

Jonathan Nieder wrote:
> Martin Teufel wrote:
 
>> Hm, I see (and agree).
>> So we/I'll wait for a fix from upstream.
>> I got back to drm_kms_helper.poll=0 for now.
>
> I have read your report carefully enough yet, but: did you get any

Erm, what I mean is that I have _not_ read and investigated your
report carefully.  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/20110505221037.GC5147@elie

Uploading linux-2.6 (2.6.38-5)

[Ben Hutchings]

I intend to upload linux-2.6 verson 2.6.38-5 tomorrow.  This will
incorporate 2.6.38.5, which fixes numerous bugs including local
privilege escalation bugs in the agp driver (CVE-2011-1745,
CVE-2011-1746).

Let me know if there's anything I should wait for.

Ben.

-- 
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.


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

Bug#596468: linux-image-2.6.32-5-openvz-amd64: Keyspan USA-49WG USB-Serial 4th Port Doesn't Work

[Steaphan Greene]

On 04/30/2011 09:49 PM, Steaphan Greene wrote:

On 04/23/2011 03:41 PM, Moritz Mühlenhoff wrote:

it seems you didn't followup in the kernel.org bugzilla. Is this fixed
in current kernels from sid or testing?


Testing on a different computer, just plugging it in with a clean boot
on the same kernel version as before (that this bug was filed against)
immediately crashed the kernel (OOPS, followed shortly by a constant
terminal bell and no response to any input, not even numlock or SysRq).

Testing this device using linux-image2.6.38-2-amd64 from current sid
(v2.6.38-4) resulted in all 4 ports working perfectly.  However, I only
could test them individually on that machine, so I can not confirm they
will work simultaneously as they are used on the real system.  But, it
certainly seems better to me.

I will follow up once I get a chance to test this on the live system
with this new kernel version, but that may be a while.  I suspect this
bug is now resolved, but I can't confirm this until then.


I found a window to reboot the main system using this hardware to test 
this newer kernel, and it just went through a cycle using all 4 serial 
ports on this device simultaneously, and worked perfectly.


So, I can confirm this bug has definitely been fixed as of the above 
kernel package version (linux-image2.6.38-2-amd64 from sid 5 days ago).


Thanks!

--
Steaphan Greene 
Lecturer, Computer Science, Binghamton University
GPG public key: http://www.cs.binghamton.edu/~sgreene/gpg.key.txt



--
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/4dc3608e.8030...@cs.binghamton.edu

Bug#625804: linux-2.6: lockups in rtc on armhf

[Vagrant Cascadian]

Package: linux-2.6
Version: 2.6.39~rc5-1~experimental.1
Severity: normal

i was experiencing lockups on an armhf kernel built from the experimental 
branch:

[2.644589] usb 2-1.1: SerialNumber: 1.0
[  240.664217] INFO: task swapper:1 blocked for more than 120 seconds.
[  240.670509] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this 
message.
[  240.678374] swapper D c0285240 0 1  0 0x
[  240.684824] [] (schedule+0x4bc/0x510) from [] 
(__mutex_lock_slowpath+0x7c/0xa0)
[  240.693914] [] (__mutex_lock_slowpath+0x7c/0xa0) from [] 
(mc13xxx_rtc_read_time+0x18/0xe4)
[  240.703967] [] (mc13xxx_rtc_read_time+0x18/0xe4) from [] 
(__rtc_read_time+0x4c/0x50)

the following patch by Arnaud Patard seemed to resolve the problem:

  http://patchwork.ozlabs.org/patch/89644/

Index: imx-test/drivers/rtc/rtc-mc13xxx.c
===
--- imx-test.orig/drivers/rtc/rtc-mc13xxx.c
+++ imx-test/drivers/rtc/rtc-mc13xxx.c
@@ -349,8 +349,13 @@  static int __devinit mc13xxx_rtc_probe(s
if (ret)
goto err_alarm_irq_request;

+   mc13xxx_unlock(mc13xxx);
+
priv->rtc = rtc_device_register(pdev->name,
&pdev->dev, &mc13xxx_rtc_ops, THIS_MODULE);
+
+   mc13xxx_lock(mc13xxx);
+
if (IS_ERR(priv->rtc)) {
ret = PTR_ERR(priv->rtc);


live well,
  vagrant



-- 
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/20110506051246.GC10524@talon.fglan

Processed: your mail

[Debian Bug Tracking System]

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

> clone 619457 -1
Bug#619457: [gnome-settings-daemon] gnome-settings-daemon crashes after login 
in.
Bug 619457 cloned as bug 625806.

> reassign -1 linux-2.6
Bug #625806 [gnome-settings-daemon] [gnome-settings-daemon] 
gnome-settings-daemon crashes after login in.
Bug reassigned from package 'gnome-settings-daemon' to 'linux-2.6'.
Bug No longer marked as found in versions gnome-settings-daemon/2.30.2-2.
> retitle -1 2.6.38 kernel erroneously reports continuous changes in the 
> connected displays
Bug #625806 [linux-2.6] [gnome-settings-daemon] gnome-settings-daemon crashes 
after login in.
Changed Bug title to '2.6.38 kernel erroneously reports continuous changes in 
the connected displays' from '[gnome-settings-daemon] gnome-settings-daemon 
crashes after login in.'
>
End of message, stopping processing here.

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

Bug#625806: Bug cloned from 619457

[Paolo Scarabelli]

As suggested I cloned the bug from 619457.

I attach the lsmod results since the ones posted on paste.debian.net are
no longer available.

Paolo
paolo@saturn:~$ uname -a
Linux saturn 2.6.38-2-686-bigmem #1 SMP Tue Mar 29 18:09:13 UTC 2011 i686 
GNU/Linux
paolo@saturn:~$ lsmod
Module  Size  Used by
vboxnetadp 13120  0 
vboxnetflt 23683  0 
vboxdrv   147237  2 vboxnetadp,vboxnetflt
acpi_cpufreq   12737  1 
mperf  12387  1 acpi_cpufreq
cpufreq_powersave  12422  0 
cpufreq_userspace  12520  0 
cpufreq_conservative13598  0 
cpufreq_stats  12670  0 
parport_pc 21895  0 
ppdev  12621  0 
lp 12858  0 
parport27018  3 parport_pc,ppdev,lp
sco13219  2 
rfcomm 31960  0 
bnep   17147  2 
l2cap  35435  6 rfcomm,bnep
crc16  12327  1 l2cap
bluetooth  50119  6 sco,bnep,rfcomm,l2cap
usb_storage34951  0 
uas12975  0 
snd_hrtimer12540  1 
binfmt_misc12778  1 
uinput 12984  1 
microcode  13213  0 
fuse   55640  1 
loop   17805  0 
snd_hda_codec_hdmi 21857  1 
snd_hda_codec_analog60504  1 
arc4   12418  2 
snd_hda_intel  21529  1 
snd_hda_codec  57563  3 
snd_hda_codec_hdmi,snd_hda_codec_analog,snd_hda_intel
uvcvideo   52490  0 
i915  276436  2 
snd_hwdep  12906  1 snd_hda_codec
videodev   48418  1 uvcvideo
snd_pcm52774  3 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec
ecb12649  2 
snd_seq39172  1 
snd_timer  22171  3 snd_hrtimer,snd_pcm,snd_seq
snd_seq_device 12995  1 snd_seq
ath9k  71303  0 
drm_kms_helper 26501  1 i915
snd38153  12 
snd_hda_codec_hdmi,snd_hda_codec_analog,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_seq,snd_timer,snd_seq_device
drm   128416  3 i915,drm_kms_helper
mac80211  160285  1 ath9k
ath9k_common   12613  1 ath9k
ath9k_hw  245846  2 ath9k,ath9k_common
ath17021  2 ath9k,ath9k_hw
i2c_algo_bit   12706  1 i915
soundcore  12878  1 snd
cfg80211  106889  3 ath9k,mac80211,ath
snd_page_alloc 12841  2 snd_hda_intel,snd_pcm
hp_wmi 12926  0 
i2c_core   18989  5 videodev,i915,drm_kms_helper,drm,i2c_algo_bit
ac 12552  0 
battery12926  0 
sparse_keymap  12680  1 hp_wmi
joydev 16906  0 
power_supply   13283  2 ac,battery
wmi13018  1 hp_wmi
rfkill 18510  5 bluetooth,cfg80211,hp_wmi
psmouse45863  0 
hp_accel   20984  0 
tpm_tis12949  0 
lis3lv02d  17483  1 hp_accel
tpm17454  1 tpm_tis
tpm_bios   12799  1 tpm
evdev  13084  17 
button 12866  1 i915
container  12525  0 
processor  26983  3 acpi_cpufreq
pcspkr 12515  0 
serio_raw  12758  0 
input_polldev  12802  1 lis3lv02d
video  17345  1 i915
ext3   98001  1 
jbd40818  1 ext3
mbcache12810  1 ext3
sg 21385  0 
sr_mod 17418  0 
sd_mod 34941  3 
crc_t10dif 12332  1 sd_mod
cdrom  34631  1 sr_mod
usbhid 35168  0 
hid59736  1 usbhid
uhci_hcd   21850  0 
ahci   20897  2 
libahci22161  1 ahci
libata131904  2 ahci,libahci
scsi_mod  134369  6 usb_storage,uas,sg,sr_mod,sd_mod,libata
ehci_hcd   34919  0 
usbcore99058  7 
usb_storage,uas,uvcvideo,usbhid,uhci_hcd,ehci_hcd
sky2   39931  0 
nls_base   12649  1 usbcore
thermal13058  0 
fan12594  0 
thermal_sys17667  4 processor,video,thermal,fan

paolo@saturn:~$ uname -a
Linux saturn 2.6.38-1-686-bigmem #1 SMP Wed Mar 16 18:21:02 UTC 2011 i686 
GNU/Linux
paolo@saturn:~$ lsmod
Module  Size  Used by
vboxnetadp  5648  0 
vboxnetflt 15075  0 
vboxdrv   142765  2 vboxnetadp,vboxnetflt
acpi_cpufreq4429  1 
mperf955  1 acpi_cpufreq
cpufreq_powersave622  0 
cpufreq_userspace   1492  0 
cpufreq_conservative 6198  0 
cpufreq_stats   1942  0 
parport_pc 15663  0 
ppdev   4049  0 
lp  5594  0 
parport20898  3 parport_pc,ppdev,lp
sco

Bug#594350: Sense: Unrecovered read error - auto reallocate failed, failed command: READ DMA

[Gabriel Rolland]

Package: linux-2.6
Severity: important


Same problem here, thinking about an hardware error we have changed the
HD, but the problem is still here.

/var/log/messages
May  6 08:20:32 mailserver kernel: [59611.168262] sd 0:0:0:0: [sda]
Unhandled sense code
May  6 08:20:32 mailserver kernel: [59611.168265] sd 0:0:0:0: [sda]
Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
May  6 08:20:32 mailserver kernel: [59611.168270] sd 0:0:0:0: [sda]
Sense Key : Medium Error [current] [descriptor]
May  6 08:20:32 mailserver kernel: [59611.168276] Descriptor sense data
with sense descriptors (in hex):
May  6 08:20:32 mailserver kernel: [59611.168279] 72 03 11 04 00
00 00 0c 00 0a 80 00 00 00 00 00
May  6 08:20:32 mailserver kernel: [59611.168288] 17 b9 c2 00
May  6 08:20:32 mailserver kernel: [59611.168292] sd 0:0:0:0: [sda] Add.
Sense: Unrecovered read error - auto reallocate failed
May  6 08:20:32 mailserver kernel: [59611.168299] sd 0:0:0:0: [sda] CDB:
Read(10): 28 00 17 b9 c2 00 00 00 08 00


smartctl
Error 65535 occurred at disk power-on lifetime: 0 hours (0 days + 0 hours)
  When the command that caused the error occurred, the device was active
or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 3e 8f 05 ea  Error: UNC at LBA = 0x0a058f3e = 168136510

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --    
  c8 00 06 3e 8f 05 ea 08  00:19:47.320  READ DMA
  ec 00 00 00 00 00 a0 0a  00:19:47.310  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 0a  00:19:47.310  SET FEATURES [Set transfer
mode]
  ec 00 00 00 00 00 a0 0a  00:19:47.310  IDENTIFY DEVICE



-- System Information:
Debian Release: 6.0.1
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4dc39861.7020...@pattume.it