date:20101214

Richard Mittendorfer del...@gmx.net writes:
  Did you try with an updated dom0 kernel as well?

64bit dom0 seems to shutdown and reboot properly.



-- 
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/84k4jc7l69@sauna.l.org

Bug#603229: Scheduler grouping failure; division by zero in select_task_rq_fair

2010-12-14 Thread Frede Feuerstein

Hello !

 We definitely want to robustify scheduler init code to not crash and to (if 
 possible) print a warning about the borkage.

I just tested the last 2.6.32-5 update and it still crashes in the same
manner.

Best regards
Tilo Hacke




-- 
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/1292321241.4511.2.ca...@localhost

Bug#605448: marked as done (linux-image-2.6.32-5-xen-amd64: xen dom0 and domU hang on reboot/halt)

Your message dated Tue, 14 Dec 2010 11:12:11 +0100
with message-id 20101214111211.80a69356.del...@gmx.net
and subject line Re: Bug#605448: linux-image-2.6.32-5-xen-amd64: xen dom0 and 
domU hang on reboot/halt
has caused the Debian Bug report #605448,
regarding linux-image-2.6.32-5-xen-amd64: xen dom0 and domU hang on reboot/halt
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
605448: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=605448
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-image-2.6.32-5-xen-amd64
Version: 2.6.32-28
Severity: normal

If Xen dom0 or domU kernel shuts down for halt or reboot it just sits
there trying to issue hw reboot/halt.
likely https://lkml.org/lkml/2010/11/26/197

-- System Information:
Debian Release: squeeze/sid
Architecture: amd64

-- 
Richard Mittendorfer del...@gmx.net


---End Message---
---BeginMessage---
Also sprach Timo Juhani Lindfors timo.lindf...@iki.fi
Tue, 14 Dec 2010 11:34:06 +0200 :
 Richard Mittendorfer del...@gmx.net writes:
   Did you try with an updated dom0 kernel as well?
 
 64bit dom0 seems to shutdown and reboot properly.

Version: 2.6.32-29

So I'd say this bug has truly been closed with 2.6.32-29 going upstream.
-- 
Richard Mittendorfer del...@gmx.net

---End Message---

Bug#605448: linux-image-2.6.32-5-xen-amd64: xen dom0 and domU hang on reboot/halt

2010-12-14 Thread Ian Campbell

On Tue, 2010-12-14 at 11:12 +0100, Richard Mittendorfer wrote:
 Also sprach Timo Juhani Lindfors timo.lindf...@iki.fi
 Tue, 14 Dec 2010 11:34:06 +0200 :
  Richard Mittendorfer del...@gmx.net writes:
Did you try with an updated dom0 kernel as well?
  
  64bit dom0 seems to shutdown and reboot properly.
 
 Version: 2.6.32-29
 
 So I'd say this bug has truly been closed with 2.6.32-29 going upstream.

Just to clarify, since the recent messages are not completely clear on
the details, we think that with the 2.6.32-29 package reboot works fine
for both 32 and 64 bit domU and dom0?

In the domU case it works ok in both the generic flavours (-686-bigmem
and -amd64) and the -xen flavours (-xen-{686,amd64})?

If so then good!

Thanks everyone for testing etc.

Ian.
-- 
Ian Campbell
Current Noise: Trouble - Pray For The Dead

While you don't greatly need the outside world, it's still very
reassuring to know that it's still there.




-- 
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/1292322500.13966.5324.ca...@zakaz.uk.xensource.com

Bug#601697: Recent update closes the bug

2010-12-14 Thread Harri Kiiskinen

Update against squeeze of today (20101214) fixes the bug.

Kernel image is linux-image-2.6.32-5-686 ver. 2.6.32-29.

xserver-xorg-video-intel 2:2.13.0-2

All the best,

Harri K.



-- 
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/20101214.132114.406727005.harri.kiiski...@utu.fi

Bug#605448: linux-image-2.6.32-5-xen-amd64: xen dom0 and domU hang on reboot/halt

Ian Campbell i...@hellion.org.uk writes:
 Just to clarify, since the recent messages are not completely clear on
 the details, we think that with the 2.6.32-29 package reboot works fine
 for both 32 and 64 bit domU and dom0?

Yes. It seems the failed reboot of 32-bit domUs was due to

[2010-12-14 13:01:45 2071] ERROR (XendDomainInfo:2205) VM squeeze32 restarting 
too fast (Elapsed time: 24.226863 seconds). Refusing to restart to avoid loops.

(The limit seems to be hardcoded to 60 seconds)



-- 
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/84bp4o7gov@sauna.l.org

Bug#607055: linux-image-2.6.32-5-686-bigmem: WI-FI constantly disconnects

2010-12-14 Thread Tshepang Lekhonkhobe

Package: linux-2.6
Version: 2.6.32-28
Severity: normal

Please see here for what's happening:
http://unix.stackexchange.com/questions/4645/wi-fi-constantly-disconnects.

-- Package-specific info:
** Version:
Linux version 2.6.32-5-686-bigmem (Debian 2.6.32-28)
(b...@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Thu
Nov 25 19:30:54 UTC 2010

** Command line:
BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-686-bigmem
root=UUID=06ec5bbe-0c90-4212-8446-432c302e3847 ro vga=769 quiet

** Not tainted

** Kernel log:
[59277.384294] scsi7 : SCSI emulation for USB Mass Storage devices
[59277.388237] usb-storage: device found at 7
[59277.388239] usb-storage: waiting for device to settle before scanning
[59282.388225] usb-storage: device scan complete
[59282.397611] scsi 7:0:0:0: Direct-Access SAMSUNG  HD102UJ
   PQ: 0 ANSI: 2
[59282.398392] sd 7:0:0:0: Attached scsi generic sg3 type 0
[59282.404156] sd 7:0:0:0: [sdc] 1953525168 512-byte logical blocks:
(1.00 TB/931 GiB)
[59282.406459] sd 7:0:0:0: [sdc] Write Protect is off
[59282.406463] sd 7:0:0:0: [sdc] Mode Sense: 38 00 00 00
[59282.406465] sd 7:0:0:0: [sdc] Assuming drive cache: write through
[59282.409705] sd 7:0:0:0: [sdc] Assuming drive cache: write through
[59282.409710]  sdc: sdc1
[59282.426199] sd 7:0:0:0: [sdc] Assuming drive cache: write through
[59282.426204] sd 7:0:0:0: [sdc] Attached SCSI disk
[59414.432054] gvfsd-metadata[12642]: segfault at 8 ip 0804d2da sp
bf9cb040 error 4 in gvfsd-metadata[8048000+c000]
[59595.489157] gvfsd-metadata[8566]: segfault at 8 ip 0804d2da sp
bff56e20 error 4 in gvfsd-metadata[8048000+c000]
[59666.469082] gvfsd-metadata[27953]: segfault at 8 ip 0804d2da sp
bfc0c2d0 error 4 in gvfsd-metadata[8048000+c000]
[60116.488066] gvfsd-metadata[29673]: segfault at 8 ip 0804d2da sp
bfe4dd60 error 4 in gvfsd-metadata[8048000+c000]
[62060.757315] usb 3-1: USB disconnect, address 6
[62085.125063] usb 3-1: new high speed USB device using ehci_hcd and address 8
[62085.257060] usb 3-1: New USB device found, idVendor=152d, idProduct=2329
[62085.257069] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=5
[62085.257076] usb 3-1: Product: USB to ATA/ATAPI bridge
[62085.257081] usb 3-1: Manufacturer: JMicron
[62085.257086] usb 3-1: SerialNumber: 7A37
[62085.257300] usb 3-1: configuration #1 chosen from 1 choice
[62085.257985] scsi8 : SCSI emulation for USB Mass Storage devices
[62085.258239] usb-storage: device found at 8
[62085.258244] usb-storage: waiting for device to settle before scanning
[62090.256276] usb-storage: device scan complete
[62090.299434] scsi 8:0:0:0: Direct-Access TOSHIBA  MK1646GSX
   PQ: 0 ANSI: 2 CCS
[62090.302016] sd 8:0:0:0: Attached scsi generic sg2 type 0
[62090.302970] sd 8:0:0:0: [sdb] 312581808 512-byte logical blocks:
(160 GB/149 GiB)
[62090.303717] sd 8:0:0:0: [sdb] Write Protect is off
[62090.303724] sd 8:0:0:0: [sdb] Mode Sense: 28 00 00 00
[62090.303730] sd 8:0:0:0: [sdb] Assuming drive cache: write through
[62090.305573] sd 8:0:0:0: [sdb] Assuming drive cache: write through
[62090.305582]  sdb: sdb1 sdb2
[62090.319080] sd 8:0:0:0: [sdb] Assuming drive cache: write through
[62090.319089] sd 8:0:0:0: [sdb] Attached SCSI disk
[62257.448088] gvfsd-metadata[13823]: segfault at 8 ip 0804d2da sp
bfa698f0 error 4 in gvfsd-metadata[8048000+c000]
[62358.406246] sd 8:0:0:0: [sdb] Unhandled sense code
[62358.406254] sd 8:0:0:0: [sdb] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[62358.406264] sd 8:0:0:0: [sdb] Sense Key : Medium Error [current]
[62358.406274] sd 8:0:0:0: [sdb] Add. Sense: Unrecovered read error
[62358.406285] sd 8:0:0:0: [sdb] CDB: Read(10): 28 00 0b 12 60 c8 00 00 f0 00
[62358.406306] end_request: I/O error, dev sdb, sector 185753800
[62358.406316] Buffer I/O error on device sdb2, logical block 20915737
[62358.406329] Buffer I/O error on device sdb2, logical block 20915738
[62358.406337] Buffer I/O error on device sdb2, logical block 20915739
[62358.406344] Buffer I/O error on device sdb2, logical block 20915740
[62358.406352] Buffer I/O error on device sdb2, logical block 20915741
[62358.406359] Buffer I/O error on device sdb2, logical block 20915742
[62358.406367] Buffer I/O error on device sdb2, logical block 20915743
[62358.406374] Buffer I/O error on device sdb2, logical block 20915744
[62358.406385] Buffer I/O error on device sdb2, logical block 20915745
[62358.406392] Buffer I/O error on device sdb2, logical block 20915746
[62365.506732] sd 8:0:0:0: [sdb] Unhandled sense code
[62365.506740] sd 8:0:0:0: [sdb] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[62365.506750] sd 8:0:0:0: [sdb] Sense Key : Medium Error [current]
[62365.506760] sd 8:0:0:0: [sdb] Add. Sense: Unrecovered read error
[62365.506774] sd 8:0:0:0: [sdb] CDB: Read(10): 28 00 0b 12 61 28 00 00 08 00
[62365.506795] end_request: I/O error, dev sdb, sector 185753896
[62365.506803] __ratelimit: 20 callbacks suppressed
[62365.506810] Buffer I/O error on device sdb2, logical block 20915749

Bug#605448: linux-image-2.6.32-5-xen-amd64: xen dom0 and domU hang on reboot/halt

2010-12-14 Thread Ian Campbell

On Tue, 2010-12-14 at 13:10 +0200, Timo Juhani Lindfors wrote:
 Ian Campbell i...@hellion.org.uk writes:
  Just to clarify, since the recent messages are not completely clear on
  the details, we think that with the 2.6.32-29 package reboot works fine
  for both 32 and 64 bit domU and dom0?
 
 Yes.

Awesome, thanks for confirming.

  It seems the failed reboot of 32-bit domUs was due to
 
 [2010-12-14 13:01:45 2071] ERROR (XendDomainInfo:2205) VM squeeze32 
 restarting too fast (Elapsed time: 24.226863 seconds). Refusing to restart to 
 avoid loops.
 
 (The limit seems to be hardcoded to 60 seconds)

Yeah, the commit which bumped it to 60s (from 20s) doesn't really say
why, seems to be something to do with failing to start qemu-dm in the
HVM case.

Ian.
-- 
Ian Campbell
Current Noise: Trouble - Wickedness Of Man

The trouble with a kitten is that
When it grows up, it's always a cat
-- Ogden Nash.




-- 
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/1292327562.13966.5380.ca...@zakaz.uk.xensource.com

Bug#432025: closed by Ben Hutchings b...@decadent.org.uk (Re: kernel-img.conf should be listed somewhere)

On Tue, 2010-12-14 at 17:40 +0800, jida...@jidanni.org wrote:
  B == Debian Bug Tracking System ow...@bugs.debian.org writes:
 
 B The kernel-img.conf file is documented in kernel-package.  This should
 B have been noted in e.g. README.Debian for image packages.  However, it
 B is no longer required and will not be created in fresh installations, so
 B I do not see the point in doing that now.
 
 $ cat /etc/kernel-img.conf
 # Kernel image management overrides
 # See kernel-img.conf(5) for details
 do_symlinks = yes
 relative_links = yes
 do_bootloader = no
 do_bootfloppy = no
 do_initrd = yes
 link_in_boot = no
 
 Should I just remove this file? Where is the new place those settings
 are supposed to go? Thanks.

Remove it.  Those settings match the defaults.

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#606968: DMA: Out of SW-IOMMU space with Xen kernel during heavy I/O

2010-12-14 Thread Rik Theys


Ben,

On Tue, 14 Dec 2010, Ben Hutchings wrote:

mpt2sas was not using the correct test for whether DMA mapping
succeeded, so it tried to continue after the DMA mapping failure.  This
has been fixed in a later version and I will apply the fix to Debian's
branch of 2.6.32.


Thanks!



However, even if this type of error is handled properly, I think it will
result in the filesystem being switched to read-only mode, and you will
then have to reboot.  Using RAID may mitigate this.


What do you mean when you say that RAID may mitigate this? This system _has_
a RAID controller and the disk is in a RAID1. Why would the filesystem switch
to read-only mode? Is it because the RAID is too slow? If the RAID is too slow, 
this should just give a high iowait, but not make the file system read-only?


Is it normal that I couldn't reproduce this with the non-xen kernel? Or can that
be caused by the fact that the stock kernel had access to all the memory (72GB),
but the dom0 kernel was limited to 2GB?

Regards,

Rik




--
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/alpine.lrh.2.00.1012141317230.19...@helium.esat.kuleuven.be

Bug#606968: DMA: Out of SW-IOMMU space with Xen kernel during heavy I/O

On Tue, 2010-12-14 at 13:24 +0100, Rik Theys wrote:
 Ben,
 
 On Tue, 14 Dec 2010, Ben Hutchings wrote:
  mpt2sas was not using the correct test for whether DMA mapping
  succeeded, so it tried to continue after the DMA mapping failure.  This
  has been fixed in a later version and I will apply the fix to Debian's
  branch of 2.6.32.
 
 Thanks!
 
 
  However, even if this type of error is handled properly, I think it will
  result in the filesystem being switched to read-only mode, and you will
  then have to reboot.  Using RAID may mitigate this.
 
 What do you mean when you say that RAID may mitigate this?

'mitigate' means to make a problem less bad.

 This system _has_
 a RAID controller and the disk is in a RAID1. Why would the filesystem switch
 to read-only mode? Is it because the RAID is too slow? If the RAID is too 
 slow, 
 this should just give a high iowait, but not make the file system read-only?

The DMA mapping failure will be treated as an I/O error.  Most
filesystems do not attempt to retry after an error.  This has nothing to
do with the speed of the disk.

Since you use RAID, the failure may only put a single disk in degraded
state, which will then be recoverable in the usual way.  The error would
be hidden from the filesystem.

 Is it normal that I couldn't reproduce this with the non-xen kernel? Or can 
 that
 be caused by the fact that the stock kernel had access to all the memory 
 (72GB),
 but the dom0 kernel was limited to 2GB?

That may be part of the problem, but I think this is a software
limitation in Xen.

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#604049: linux-image-2.6.32-5-amd64: data corruption with promise stex driver and use of device-mapper layers (lvm/dm-crypt/..)

On Tue, 2010-12-14 at 09:35 +0100, Markus Schulz wrote:
 Am Dienstag, 14. Dezember 2010 schrieb Ben Hutchings:
 ...
  This sounds similar to bug #604457, which should be fixed in version
  2.6.32-29 (now in testing).  Can you check whether that version fixes
  the bug?
 
 don't think so.
 if you follow the link posted from Ed Lin you will find a patch from 
 Martin K. Petersen (http://marc.info/?l=linux-
 scsim=129114458116271w=2)

I only see Ed Lin's patch, and I don't think it is a full solution.
Please do try the latest version.

 if i interpret the last posting from Greg Kroah-Hartman right, he want 
 to apply the patch to the stable kernel series.

It has to be accepted into Linus's tree first, and that has not yet
happened.

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#606968: DMA: Out of SW-IOMMU space with Xen kernel during heavy I/O

2010-12-14 Thread Rik Theys


On Tue, 14 Dec 2010, Ben Hutchings wrote:


On Tue, 2010-12-14 at 13:24 +0100, Rik Theys wrote:

This system _has_
a RAID controller and the disk is in a RAID1. Why would the filesystem switch
to read-only mode? Is it because the RAID is too slow? If the RAID is too slow,
this should just give a high iowait, but not make the file system read-only?


The DMA mapping failure will be treated as an I/O error.  Most
filesystems do not attempt to retry after an error.  This has nothing to
do with the speed of the disk.

Since you use RAID, the failure may only put a single disk in degraded
state, which will then be recoverable in the usual way.  The error would
be hidden from the filesystem.


The RAID in this system is a PERC H200, which should be a hardware RAID card.
Can the mpt2sas driver see the physical disks that are part of the RAID?

It is my understanding that the mpt2sas driver only sees the RAID as a scsi disk
and not the individual drives? If that is the case, how would this I/O error
lead to a single disk in the RAID becoming faulty and the RAID degraded?

Will the H200 mark the disk as faulty when the mpt2sas driver triggers this?

Regards,

Rik




--
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/alpine.lrh.2.00.1012141403350.23...@helium.esat.kuleuven.be

Bug#606968: DMA: Out of SW-IOMMU space with Xen kernel during heavy I/O

2010-12-14 Thread Rik Theys


On Tue, 14 Dec 2010, Rik Theys wrote:


On Tue, 14 Dec 2010, Ben Hutchings wrote:


On Tue, 2010-12-14 at 13:24 +0100, Rik Theys wrote:

This system _has_
a RAID controller and the disk is in a RAID1. Why would the filesystem 
switch
to read-only mode? Is it because the RAID is too slow? If the RAID is too 
slow,
this should just give a high iowait, but not make the file system 
read-only?


The DMA mapping failure will be treated as an I/O error.  Most
filesystems do not attempt to retry after an error.  This has nothing to
do with the speed of the disk.

Since you use RAID, the failure may only put a single disk in degraded
state, which will then be recoverable in the usual way.  The error would
be hidden from the filesystem.


The RAID in this system is a PERC H200, which should be a hardware RAID card.
Can the mpt2sas driver see the physical disks that are part of the RAID?


Looking at the kernel messages from bootup, the mpt2sas driver does seem to know
about the individual disks.

There's also a failure message:

[   29.201218] mpt2sas0: failure at 
/build/buildd-linux-2.6_2.6.32-29-amd64-xcs37n/linux-2.6-2.6.32/debian/build/source_amd64_xen/drivers/scsi/mpt2sas/mpt2sas_scsih.c:3801/_scsih_add_device()!

Is this message harmless?

Regards,

Rik

[   27.279835] mpt2sas0: Allocated physical memory: size(739 kB)
[   27.279838] mpt2sas0: Current Controller Queue Depth(467), Max Controller 
Queue Depth(3439)
[   27.279840] mpt2sas0: Scatter Gather Elements per IO(128)
[   27.519864] mpt2sas0: LSISAS2008: FWVersion(02.15.63.00), 
ChipRevision(0x03), BiosVersion(07.01.09.00)
[   27.519869] mpt2sas0: Dell PERC H200 Integrated: Vendor(0x1000), 
Device(0x0072), SSVID(0x1028), SSDID(0x1F1E)
[   27.519873] mpt2sas0: Protocol=(Initiator,Target), 
Capabilities=(Raid,TLR,EEDP,Snapshot Buffer,Diag Trace Buffer,Task Set Full,NCQ)
[   27.519949] mpt2sas0: sending port enable !!
[   29.200976] mpt2sas0: host_add: handle(0x0001), 
sas_addr(0x5842b2b07007cf00), phys(8)
[   29.201218] mpt2sas0: failure at 
/build/buildd-linux-2.6_2.6.32-29-amd64-xcs37n/linux-2.6-2.6.32/debian/build/source_amd64_xen/drivers/scsi/mpt2sas/mpt2sas_scsih.c:3801/_scsih_add_device()!
[   34.448533] mpt2sas0: port enable: SUCCESS
[   34.448775] scsi 0:1:0:0: Direct-Access Dell Virtual Disk 1028 
PQ: 0 ANSI: 6
[   34.449083] scsi 0:1:0:0: RAID1: handle(0x004f), wwid(0x033ce95f5ae26e63), 
pd_count(2), type(SATA)
[   34.449092] scsi 0:1:0:0: qdepth(128), tagged(1), simple(1), ordered(0), 
scsi_level(7), cmd_que(1)
[   34.449315] scsi 0:1:0:0: Attached scsi generic sg1 type 0
[   34.451378] scsi 0:0:0:0: Direct-Access ATA  WDC WD1602ABKS-1 3B05 
PQ: 0 ANSI: 5
[   34.451586] scsi 0:0:0:0: SATA: handle(0x000a), 
sas_addr(0x443322110600), device_name(0x4ee1500110f80366)
[   34.451590] scsi 0:0:0:0: SATA: enclosure_logical_id(0x5842b2b07007cf00), 
slot(1)
[   34.451674] scsi 0:0:0:0: atapi(n), ncq(y), asyn_notify(n), smart(y), 
fua(y), sw_preserve(y)
[   34.451677] scsi 0:0:0:0: qdepth(32), tagged(1), simple(1), ordered(0), 
scsi_level(6), cmd_que(1)
[   34.451873] scsi 0:0:0:0: Attached scsi generic sg2 type 0
[   34.453956] scsi 0:0:1:0: Direct-Access ATA  WDC WD1602ABKS-1 3B05 
PQ: 0 ANSI: 5
[   34.454165] scsi 0:0:1:0: SATA: handle(0x000b), 
sas_addr(0x443322110700), device_name(0x4ee150010cda0366)
[   34.454169] scsi 0:0:1:0: SATA: enclosure_logical_id(0x5842b2b07007cf00), 
slot(0)
[   34.454253] scsi 0:0:1:0: atapi(n), ncq(y), asyn_notify(n), smart(y), 
fua(y), sw_preserve(y)
[   34.454256] scsi 0:0:1:0: qdepth(32), tagged(1), simple(1), ordered(0), 
scsi_level(6), cmd_que(1)
[   34.454455] scsi 0:0:1:0: Attached scsi generic sg3 type 0
[   34.460429] sd 0:1:0:0: [sda] 311427072 512-byte logical blocks: (159 GB/148 
GiB)
[   34.460542] sd 0:1:0:0: [sda] Write Protect is off
[   34.460546] sd 0:1:0:0: [sda] Mode Sense: 03 00 00 08
[   34.460614] sd 0:1:0:0: [sda] Write cache: disabled, read cache: enabled, 
doesn't support DPO or FUA
[   34.460873]  sda: sda1 sda2 sda3
[   34.466279] sd 0:1:0:0: [sda] Attached SCSI disk




--
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/alpine.lrh.2.00.1012141425190.23...@helium.esat.kuleuven.be

Bug#606968: DMA: Out of SW-IOMMU space with Xen kernel during heavy I/O

On Tue, 2010-12-14 at 14:22 +0100, Rik Theys wrote:
 On Tue, 14 Dec 2010, Ben Hutchings wrote:
 
  On Tue, 2010-12-14 at 13:24 +0100, Rik Theys wrote:
  This system _has_
  a RAID controller and the disk is in a RAID1. Why would the filesystem 
  switch
  to read-only mode? Is it because the RAID is too slow? If the RAID is too 
  slow,
  this should just give a high iowait, but not make the file system 
  read-only?
 
  The DMA mapping failure will be treated as an I/O error.  Most
  filesystems do not attempt to retry after an error.  This has nothing to
  do with the speed of the disk.
 
  Since you use RAID, the failure may only put a single disk in degraded
  state, which will then be recoverable in the usual way.  The error would
  be hidden from the filesystem.
 
 The RAID in this system is a PERC H200, which should be a hardware RAID card.
 Can the mpt2sas driver see the physical disks that are part of the RAID?

I don't think so.

 It is my understanding that the mpt2sas driver only sees the RAID as a scsi 
 disk
 and not the individual drives? If that is the case, how would this I/O error
 lead to a single disk in the RAID becoming faulty and the RAID degraded?
 
 Will the H200 mark the disk as faulty when the mpt2sas driver triggers this?

It wouldn't.  I was thinking of Linux software RAID.

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#606968: DMA: Out of SW-IOMMU space with Xen kernel during heavy I/O

On Tue, 2010-12-14 at 14:27 +0100, Rik Theys wrote:
On Tue, 14 Dec 2010, Rik Theys wrote:

On Tue, 14 Dec 2010, Ben Hutchings wrote:

On Tue, 2010-12-14 at 13:24 +0100, Rik Theys wrote:
This system _has_
a RAID controller and the disk is in a RAID1. Why would the filesystem
switch
to read-only mode? Is it because the RAID is too slow? If the RAID is too
slow,
this should just give a high iowait, but not make the file system
read-only?

The DMA mapping failure will be treated as an I/O error. Most
filesystems do not attempt to retry after an error. This has nothing to
do with the speed of the disk.

Since you use RAID, the failure may only put a single disk in degraded
state, which will then be recoverable in the usual way. The error would
be hidden from the filesystem.

The RAID in this system is a PERC H200, which should be a hardware RAID
card.
Can the mpt2sas driver see the physical disks that are part of the RAID?

Looking at the kernel messages from bootup, the mpt2sas driver does seem to
know
about the individual disks.

OK.

There's also a failure message:

[ 29.201218] mpt2sas0: failure at
/build/buildd-linux-2.6_2.6.32-29-amd64-xcs37n/linux-2.6-2.6.32/debian/build/source_amd64_xen/drivers/scsi/mpt2sas/mpt2sas_scsih.c:3801/_scsih_add_device()!

Is this message harmless?
[...]

According to the source code, it means that the driver found a device
that is not an 'end device'. I think it's harmless.

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#606964: linux-image-2.6.32-5-xen-amd64: Xen fails to boot dom0 kernel on system with, lots of RAM

2010-12-14 Thread Ian Campbell

On Mon, 2010-12-13 at 11:42 +0100, Rik Theys wrote:
 Package: linux-2.6
 Version: 2.6.32-29
 Severity: normal
 
 When booting Xen 4.0.1 with the Debian dom0 kernel, Xen hangs on startup 
 after saying that the
 system has x VCPUS and before starting the Scrubbing Free RAM.

 This looks related to the bug mentioned here:
 
 http://lists.xensource.com/archives/html/xen-devel/2010-08/msg00625.html
 
 When adding dom0_mem=2G to the boot line, the system boots OK.

I expect it will work ok with everything up to and including
dom0_mem=32G?

 I've added it to both the kernel command line and the xen command line 
 to make sure I had
 the parameter set.
 
 The system has 72GB ram.
 
 The thread mentions a kernel config that can be changed to fix this?
 http://lists.xensource.com/archives/html/xen-devel/2010-08/msg00884.html

Changing this option imposes a static (at compile time) memory overhead
on the kernel when running under Xen. It has become more dynamic in
future kernels but those changes are not suitable for backporting to
Squeeze at this stage. 32GB seems like a reasonable compromise in the
meantime.

It depends a bit on your usecase but it is often best recommended to use
dom0_mem= anyway, since you are most often going to balloon dom0 down
significantly anyway to make room for guest domains.

Note also that the smallest size you can balloon dom0 to is proportional
to the initial size of the domain, due to various data structures (such
as the frame table) which are sized on boot according to memory size.
IIRC a72GB domain 0 would have several hundred megabytes of such data
structures which would therefore not be available for guest use and
effectively be wasted. If you use dom0_mem then those datastructures are
much smaller which leaves more memory for guests.

I would recommend that you determine how big you want/need domain 0 to
be and pass an appropriate dom0_mem option.

Ian,
-- 
Ian Campbell
Current Noise: Devin Townsend - Addicted

I consider the day misspent that I am not either charged with a crime,
or arrested for one.
-- Ratsy Tourbillon




-- 
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/1292334083.32368.73.ca...@zakaz.uk.xensource.com

Bug#604049: linux-image-2.6.32-5-amd64: data corruption with promise stex driver and use of device-mapper layers (lvm/dm-crypt/..)

2010-12-14 Thread Markus Schulz

Am Dienstag, 14. Dezember 2010 schrieb Ben Hutchings:
 On Tue, 2010-12-14 at 09:35 +0100, Markus Schulz wrote:
  Am Dienstag, 14. Dezember 2010 schrieb Ben Hutchings:
  ...
  
   This sounds similar to bug #604457, which should be fixed in
   version 2.6.32-29 (now in testing).  Can you check whether that
   version fixes the bug?
  
  don't think so.
  if you follow the link posted from Ed Lin you will find a patch
  from Martin K. Petersen (
  http://marc.info/?l=linux-scsim=129114458116271w=2)
 
 I only see Ed Lin's patch, and I don't think it is a full solution.

it was in Martins git-repository (see above link, different branches for 
2.6.32, 2.6.35 and 2.6.36)

for example the commit for kernel 2.6.36

http://git.kernel.org/?p=linux/kernel/git/mkp/linux-2.6-
mkp.git;a=commit;h=069bd9391faf24da0c4311b4d799f8aac3986efd

 Please do try the latest version.

ok, i will do this. But it looks specific to md-raid (dm-md-fix-
merge.patch) and i don't use MD-raid (i'm use HW-Raid from promise stex 
driver).

 
  if i interpret the last posting from Greg Kroah-Hartman right, he
  want to apply the patch to the stable kernel series.
 
 It has to be accepted into Linus's tree first, and that has not yet
 happened.

i will try Martins patch too.  I don't want to wait until the patch 
arrives the mainline kernel (i need the pc and there is no workaround 
available).

regards,
msc



-- 
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/201012141532.41...@mail-followup-to

Bug#555835: {PATCH] usb-storage: unusual_devs entry for the Samsung YP-CP3

2010-12-14 Thread Alan Stern

From: Vitaly Kuznetsov vi...@altlinux.ru

Add an unusual_devs entry for the Samsung YP-CP3 MP4 player.

User was getting the following errors in dmesg:
 usb 2-6: reset high speed USB device using ehci_hcd and address 2
 usb 2-6: reset high speed USB device using ehci_hcd and address 2
 usb 2-6: reset high speed USB device using ehci_hcd and address 2
 usb 2-6: USB disconnect, address 2
 sd 3:0:0:0: [sdb] Assuming drive cache: write through
 sdb:2ldm_validate_partition_table(): Disk read failed.
 Dev sdb: unable to read RDB block 0
  unable to read partition table

Signed-off-by: Vitaly Kuznetsov vi...@altlinux.ru
Acked-by: Alan Stern st...@rowland.harvard.edu
CC: Matthew Dharm mdharm-...@one-eyed-alien.net
CC: sta...@kernel.org

---

This would be better if the bcdDevice range was more specific.  But we
can take it as it is.

 drivers/usb/storage/unusual_devs.h |7 +++
 1 files changed, 7 insertions(+), 0 deletions(-)

diff --git a/drivers/usb/storage/unusual_devs.h 
b/drivers/usb/storage/unusual_devs.h
index d4f034e..05b0d2c 100644
--- a/drivers/usb/storage/unusual_devs.h
+++ b/drivers/usb/storage/unusual_devs.h
@@ -481,6 +481,13 @@ UNUSUAL_DEV(  0x04e8, 0x507c, 0x0220, 0x0220,
USB_SC_DEVICE, USB_PR_DEVICE, NULL,
US_FL_MAX_SECTORS_64),
 
+/* Reported by Vitaly Kuznetsov vi...@altlinux.ru */
+UNUSUAL_DEV(  0x04e8, 0x5122, 0x, 0x,
+   Samsung,
+   YP-CP3,
+   USB_SC_DEVICE, USB_PR_DEVICE, NULL,
+   US_FL_MAX_SECTORS_64 | US_FL_BULK_IGNORE_TAG),
+
 /* Entry and supporting patch by Theodore Kilgore kilg...@auburn.edu.
  * Device uses standards-violating 32-byte Bulk Command Block Wrappers and
  * reports itself as Proprietary SCSI Bulk. Cf. device entry 0x084d:0x0011.




-- 
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/pine.lnx.4.44l0.1012141004510.2087-100...@iolanthe.rowland.org

Bug#607090: initramfs-tools/squeeze: trigger cryptroot/lenny prints alarming error message - missing versioned breaks or conflicts on cryptsetup?

2010-12-14 Thread Carsten Hey

Package: initramfs-tools
Severity: important


Please adapt the severity if you think this is RC.


The trigger cryptroot from Lenny prints an alarming error message - missing
versioned breaks or conflicts on cryptsetup?


I don't use an encrypted root.

$ file -s /dev/sda{5,6}
/dev/sda5: Linux/i386 swap file (new style), version 1 (4K pages), size 244974 
pages, no label, UUID=9e1ab538-b9de-4246-acd6-3c78143ac991
19:root%elmer:~ file -s /dev/sda6
/dev/sda6: Linux rev 1.0 ext3 filesystem data, 
UUID=a02fd308-563e-4905-803d-d04f2fe95924, volume name root (needs journal 
recovery)

All other file systems are on logical volumes, some of them are encrypted.


$ apt-get install long list of packages
...
Processing triggers for initramfs-tools ...
update-initramfs: Generating /boot/initrd.img-2.6.32-bpo.5-amd64
/tmp/mkinitramfs_wlotAP/scripts/local-top/cryptroot: line 11: [: too many 
arguments


$ apt-cache policy cryptsetup
cryptsetup:
  Installed: 2:1.0.6-7
  Candidate: 2:1.1.3-4
  Version table:
 2:1.1.3-4 0
500 http://ftp.de.debian.org squeeze/main Packages
 *** 2:1.0.6-7 0
500 http://ftp.de.debian.org lenny/main Packages
100 /var/lib/dpkg/status
$ apt-cache policy initramfs-tools
initramfs-tools:
  Installed: 0.98.5
  Candidate: 0.98.5
  Version table:
 *** 0.98.5 0
500 http://ftp.de.debian.org squeeze/main Packages
100 /var/lib/dpkg/status
 0.94.4~bpo50+1 0
  1 http://www.backports.org lenny-backports/main Packages
 0.92o 0
500 http://ftp.de.debian.org lenny/main Packages



-- 
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/20101214155644.gp31...@furrball.stateful.de

Bug#607095: linux-2.6: backport 2d9e667e (disable IOMMU for iGFX on some chipsets)

2010-12-14 Thread Yves-Alexis Perez

Package: linux-2.6
Version: 2.6.32-29
Severity: normal

Hey,

on some hardware (Dell Latitude E4300 and it seems Lenovo X200, and
quite some others), booting with intel_iommu=on will lead to freezes.

Fedora bug at https://bugzilla.redhat.com/show_bug.cgi?id=538163
indicates some revisions of Mobile 4 series intel chipset don't work
fine under IOMMU, and
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=2d9e667e
has be written to disable IOMMU only for graphics chipsets.

It'd be nice to backport the patch to Debian kernel, though as IOMMU is
not enabled by default it won't hit default installs.

Regards,
-- 
Yves-Alexis


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

Kernel: Linux 2.6.32-5-grsec-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.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/20101214161952.23999.86152.report...@hidalgo

Processed: severity of 607090 is serious

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

 severity 607090 serious
Bug #607090 [initramfs-tools] initramfs-tools/squeeze: trigger cryptroot/lenny 
prints alarming error message - missing versioned breaks or conflicts on 
cryptsetup?
Severity set to 'serious' from 'important'

 thanks
Stopping processing here.

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

Bug#601187: linux-image-2.6.32-5-amd64: Please apply patch for shared I/O region support

2010-12-14 Thread Mike Hommey

On Mon, Dec 06, 2010 at 08:44:14AM +0100, Mike Hommey wrote:
 On Mon, Dec 06, 2010 at 04:25:13AM +, Ben Hutchings wrote:
  On Thu, 2010-12-02 at 13:39 +0100, Mike Hommey wrote:
   Is the following going to be considered for squeeze?
  
  I've cherry-picked all the necessary changes (I think):
  
  8b6d043b7ee2d1b819dc833d677ea2aead71a0c0 resource: shared I/O region support
  729d273aa7c86eb1406ade4eadf249cff188bf9a hwmon: (f71882fg) Acquire I/O 
  regions while we're working with them
  cadb86570c41fe52a0ea741f1f9775e3412f0167 hwmon: f71882fg: use a muxed 
  resource lock for the Super I/O port
  96cb4eb019ce3185ec0d946a74b5a2202f5067c9 watchdog: f71808e_wdt: new 
  watchdog driver for Fintek F71808E and F71882FG
 
 That's the set of patches I've been using. Awesome. Thanks.

It appears I was wrong. There's one small patch missing to get support
for the F71889FG watchdog:
dee00abbbcab97b8ee3bbafb5e786dde83e26741 watchdog: f71808e_wdt: add support for 
the F71889FG

Interestingly, trying to load the bundled f71808e_wdt doesn't print a
error, which would be something about no device being found or
something like that:
# modprobe f71808e_wdt
FATAL: Error inserting f71808e_wdt 
(/lib/modules/2.6.32-5-amd64/kernel/drivers/watchdog/f71808e_wdt.ko): Kernel 
does not have module support

Please take whichever decision you want wrt this driver, considering
the release schedule, I'd understand if that's wontfix for now.

However, since I now don't need to rebuild the kernel for the shared
I/O region support, fixing the lack of support for my chip is trivial
on my end.

Leaving the bug closed, as it was more about the shared I/O region
support.

Cheers,

Mike



-- 
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/20101214162356.ga8...@glandium.org

Bug#606806: initramfs-tools: Handling of numeric root= arguments is not udev-friendly

tags 606806 pending
stop

On Sat, 11 Dec 2010, Evan Broder wrote:

 
 I see. I wasn't aware of BUSYBOX=no. But looking at this again, I
 think I actually want to take a different approach in order to
 maintain the current semantics of setting root=X:Y.

Ok great, applied in maks/num_root branch in
http://git.debian.org/?p=kernel/initramfs-tools.git;a=summary

could you please have a look that i didn't botch the commit
as I had to hand apply due to the attached patch, beeing against
latest Ubuntu and having a strange patch level?
pending review it will hit master which is scheduled for post squeeze
fixes.
 
thank you.

-- 
maks



-- 
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/20101214174203.gd18...@stro.at

Processed: Re: Bug#606806: initramfs-tools: Handling of numeric root= arguments is not udev-friendly

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

 tags 606806 pending
Bug #606806 [initramfs-tools] initramfs-tools: Handling of numeric root= 
arguments is not udev-friendly
Added tag(s) pending.
 stop
Stopping processing here.

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

Bug#607090: initramfs-tools/squeeze: trigger cryptroot/lenny prints alarming error message - missing versioned breaks or conflicts on cryptsetup?

tags 607090 pending patch
stop

On Tue, 14 Dec 2010, Carsten Hey wrote:

 
 Please adapt the severity if you think this is RC.

indeed, thank you for reporting.

Thought it was only an issue of partial upgrades but indeed Lenny
cryptsetup had one of the two errors that got later corrected for
precached scripts that initramfs-tools uses in sid.
 
fixed in maks/breaks_cryptsetup
http://git.debian.org/?p=kernel/initramfs-tools.git;a=summary

should soon appear in squeeze branch

-- 
maks



-- 
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/20101214180624.ge18...@stro.at

Bug#606806: initramfs-tools: Handling of numeric root= arguments is not udev-friendly

2010-12-14 Thread Evan Broder

On Tue, Dec 14, 2010 at 9:42 AM, maximilian attems m...@stro.at wrote:
 Ok great, applied in maks/num_root branch in
 http://git.debian.org/?p=kernel/initramfs-tools.git;a=summary

 could you please have a look that i didn't botch the commit
 as I had to hand apply due to the attached patch, beeing against
 latest Ubuntu and having a strange patch level?
 pending review it will hit master which is scheduled for post squeeze
 fixes.

 thank you.

Patch looks good to me. Thanks for everyone's help.

- Evan



-- 
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/aanlktimmegq09br84dd9x=dnevm2ukm7s-vngdjcg...@mail.gmail.com

Bug#604049: SPAM tested with linux-image-2.6.32-5-amd64/2.6.32-29

2010-12-14 Thread Markus Schulz

I've tried linux-image-2.6.32-5-amd64/2.6.32-29 without luck. Same file 
errors and/or broken file system.

I've tried Martin K. Petersen Patch too (applied to linus 2.6.36 git 
repo) with success. 
It works, no md5sum errors (test still running as endless loop).

regards,
msc



-- 
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/201012141938.38553@antzsystem.de

Re: [PATCH] Fix condition for adding IDE or SCSI disk driver when MODULES=dep

On Sun, 12 Dec 2010, Ben Hutchings wrote:

 The transition from old-style IDE to libata-based drivers means the
 new kernel may need different drivers from the running system.  We
 already handle the change of controller driver correctly since we find
 driver modules via module aliases.  However for the disk driver
 (sd_mod or ide-disk) we look at which types of devices exist in the
 running system, so we may not select the one we need.
 
 Since all the controller driver modules depend on the core modules
 under drivers/ide or drivers/scsi, we can work out which disk
 driver(s) may be needed by checking whether those module
 subdirectories have been created under the target directory.
 
 Reported-by: Gordon Farquharson gordonfarquhar...@gmail.com
 Signed-off-by: Ben Hutchings b...@decadent.org.uk

Thank you a lot for the excellent bug hunt.

 ---
 I've given this a very little testing and it seems to do the right
 thing.  This obviously needs careful review!
 
 Ben.
 
  hook-functions |4 ++--
  1 files changed, 2 insertions(+), 2 deletions(-)
 
 diff --git a/hook-functions b/hook-functions
 index 0684296..da16478 100644
 --- a/hook-functions
 +++ b/hook-functions
 @@ -349,7 +349,7 @@ dep_add_modules()
   sys_walk_mod_add ${root_dev_path}
  
   # catch old-style IDE
 - if [ -e /sys/bus/ide/devices/ ]; then
 + if [ -d ${DESTDIR}/lib/modules/${version}/kernel/drivers/ide ]; then

Not sure I like this change, as this is a noop in any of our linux-2.6

   sys_walk_modalias ${root_dev_path}
   manual_add_modules ide-gd_mod
   # FIXME: remove post Squeeze
 @@ -357,7 +357,7 @@ dep_add_modules()
   manual_add_modules ide-cd
   fi
  
 - if [ -e /sys/bus/scsi/devices/ ]; then
 + if [ -d ${DESTDIR}/lib/modules/${version}/kernel/drivers/scsi ]; then
same here.
   manual_add_modules sd_mod
   fi
  
 -- 
 1.7.2.3
 
 
 

so instead of overoptimising here, I'd just remove both conditions.
Of course they can be left or readded post-squeeze.

what do you think?

-- 
maks


-- 
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/20101214184523.ge...@stro.at

stable update 2.6.32.27

hello Pavel, hello Kir,

could you please sync latest 2.6.32 openvz to upstream stable.
You also then need belows fix.

Thank you

-- 
maks

- Forwarded message from Ben Hutchings b...@decadent.org.uk -

Date: Sat, 11 Dec 2010 05:51:39 +
From: Ben Hutchings b...@decadent.org.uk
To: sta...@kernel.org
Cc: Jiri Slaby jsl...@suse.cz, Alan Cox a...@linux.intel.com
Subject: [PATCH] TTY: Fix error return from tty_ldisc_open()

The backported version of TTY: ldisc, fix open flag handling in
2.6.32.27 causes tty_ldisc_open() to return 0 on error.  Fix that.

Signed-off-by: Ben Hutchings b...@decadent.org.uk
---
 drivers/char/tty_ldisc.c |1 +
 1 files changed, 1 insertions(+), 0 deletions(-)

diff --git a/drivers/char/tty_ldisc.c b/drivers/char/tty_ldisc.c
index 8b9f1a5..cf0bfc6 100644
--- a/drivers/char/tty_ldisc.c
+++ b/drivers/char/tty_ldisc.c
@@ -451,6 +451,7 @@ static int tty_ldisc_open(struct tty_struct *tty, struct 
tty_ldisc *ld)
ret = ld-ops-open(tty);
if (ret)
clear_bit(TTY_LDISC_OPEN, tty-flags);
+   return ret;
}
return 0;
 }
-- 
1.7.2.3


- End forwarded message -


-- 
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/20101214185247.gf...@stro.at

CONFIG_LEGACY_PTYS and Squeeze

2010-12-14 Thread Mark Lehrer

Many OpenVZ containers are still likely to require the legacy pty option in 
the kernel in order for vzctl enter or ssh to work.


I can work around it for my environment, but a lot of people will have 
difficulty if the CONFIG_LEGACY_PTYS option isn't set in the default kernel. 
Would it be possible for you to add it to the -openvz flavors of the 
Squeeze kernels as a default?


Thanks,
Mark


--
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/ximss-6465...@knm.org

Bug#601184: marked as done (linux-image-2.6.36-rc6-amd64: Possible privilege escalation bug)

Your message dated Tue, 14 Dec 2010 20:55:54 +0100
with message-id 20101214195554.ga2...@galadriel.inutil.org
and subject line Re: Bug#601184: linux-image-2.6.36-rc6-amd64: Possible 
privilege escalation bug
has caused the Debian Bug report #601184,
regarding linux-image-2.6.36-rc6-amd64: Possible privilege escalation bug
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
601184: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=601184
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-2.6
Version: 2.6.36~rc6-1~experimental.1
Severity: critical
Tags: security
Justification: root security hole

I'm not sure if I should include the steps to reproduxe here in case it's 
visible to the 
general population.

Could someone email me directly so I can provide the details.
If they decide to, then they can post the details themselves.

-- Package-specific info:
** Version:
Linux version 2.6.36-rc6-amd64 (Debian 2.6.36~rc6-1~experimental.1) 
(b...@decadent.org.uk) (gcc version 4.4.5 (Debian 4.4.4-17) ) #1 SMP Mon Oct 4 
09:56:45 UTC 2010

** Command line:
BOOT_IMAGE=/vmlinuz-2.6.36-rc6-amd64 root=/dev/mapper/VgCompaq-debian 
resume=/dev/VgCompaq/swap ro quiet splash vga=0x317

** Not tainted

** Kernel log:
[9.031499] PM: Marking nosave pages: bf534000 - bf537000
[9.031502] PM: Marking nosave pages: bf5bb000 - bf5bf000
[9.031504] PM: Basic memory bitmaps created
[9.045860] PM: Basic memory bitmaps freed
[   10.112062] EXT3-fs: barriers not enabled
[   10.126287] kjournald starting.  Commit interval 5 seconds
[   10.126311] EXT3-fs (dm-4): mounted filesystem with ordered data mode
[   13.560017] udevd version 125 started
[   14.438927] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[   14.469288] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[   14.682126] i801_smbus :00:1f.3: PCI INT D - GSI 19 (level, low) - IRQ 
19
[   14.749432] input: PC Speaker as /devices/platform/pcspkr/input/input1
[   14.847434] input: Power Button as 
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input2
[   14.847496] ACPI: Power Button [PWRB]
[   14.847559] input: Lid Switch as 
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input3
[   14.847631] ACPI: Lid Switch [LID0]
[   14.847690] input: Sleep Button as 
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input4
[   14.847726] ACPI: Sleep Button [SLPB]
[   14.847810] input: Power Button as 
/devices/LNXSYSTM:00/LNXPWRBN:00/input/input5
[   14.847844] ACPI: Power Button [PWRF]
[   14.931635] ACPI: acpi_idle registered with cpuidle
[   14.976035] Monitor-Mwait will be used to enter C-1 state
[   15.010136] Monitor-Mwait will be used to enter C-2 state
[   15.024658] Monitor-Mwait will be used to enter C-3 state
[   15.024675] Marking TSC unstable due to TSC halts in idle
[   15.042099] Linux video capture interface: v2.00
[   15.056031] Switching to clocksource hpet
[   15.213992] uvcvideo: Found UVC 1.00 device CNF7041 (04f2:b057)
[   15.217763] input: CNF7041 as 
/devices/pci:00/:00:1d.7/usb1/1-6/1-6:1.0/input/input6
[   15.217824] usbcore: registered new interface driver uvcvideo
[   15.217826] USB Video Class driver (v0.1.0)
[   15.536386] ACPI: WMI: Mapper loaded
[   15.537107] cfg80211: Calling CRDA to update world regulatory domain
[   15.628141] ACPI: AC Adapter [AC] (on-line)
[   15.735247] ACPI: Battery Slot [BAT0] (battery present)
[   16.034716] ath5k :01:00.0: PCI INT A - GSI 16 (level, low) - IRQ 16
[   16.034734] ath5k :01:00.0: setting latency timer to 64
[   16.034825] ath5k :01:00.0: registered as 'phy0'
[   17.064120] input: PS/2 Mouse as /devices/platform/i8042/serio1/input/input7
[   17.094313]   alloc irq_desc for 22 on node -1
[   17.094317]   alloc kstat_irqs on node -1
[   17.094329] HDA Intel :00:1b.0: PCI INT A - GSI 22 (level, low) - IRQ 
22
[   17.094423]   alloc irq_desc for 41 on node -1
[   17.094426]   alloc kstat_irqs on node -1
[   17.094440] HDA Intel :00:1b.0: irq 41 for MSI/MSI-X
[   17.094475] HDA Intel :00:1b.0: setting latency timer to 64
[   17.139024] input: AlpsPS/2 ALPS GlidePoint as 
/devices/platform/i8042/serio1/input/input8
[   17.244803] input: HP WMI hotkeys as /devices/virtual/input/input9
[   17.397742] ath: EEPROM regdomain: 0x67
[   17.397745] ath: EEPROM indicates we should expect a direct regpair map
[   17.397750] ath: Country alpha2 being used: 00
[   17.397752] ath: Regpair used: 0x67
[   17.485816] input: HDA Digital PCBeep as 
/devices/pci:00/:00:1b.0/input/input10
[   17.487452] input:

Bug#607114: Unresponsive Xen's dom0 system after 'general protection fault'


Package: linux-image-2.6-xen-amd64
Version: 2.6.26+17+lenny1
Severity: critical
Tags: lenny

After execution of xm create command I got messages in attached file.
I got this for second time within one week. Not sure what the root cause is.
Right now all of commands working with networking just hangs. Looks like 
it has something to do with 8021q module.

All Xen domU's with NATed networks are reachable.

-- System Information:
Debian Release: 5.0.7

--
Regards,
Peter Viskup
Dec 14 21:25:17 server2 kernel: [1480447.233563] general protection fault:  
[1] SMP 
Dec 14 21:25:17 server2 kernel: [1480447.234227] CPU 0 
Dec 14 21:25:17 server2 kernel: [1480447.234508] Modules linked in: 
ipt_MASQUERADE bonding 8021q iptable_nat nf_nat ext2 xt_physdev tun ext4dev 
jbd2 crc16 xfs bridge ipv6 xt_multiport ipt_LOG xt_tcpudp nf_conntrack_ipv4 
xt_state nf_conntrack iptable_filter ip_tables x_tables loop ide_pci_generic 
ide_core ata_generic usbhid hid ff_memless psmouse serio_raw pcspkr sata_svw 
libata dock container bnx2 ohci_hcd firmware_class ehci_hcd button ipmi_si 
hpilo ipmi_msghandler uhci_hcd shpchp pci_hotplug i2c_piix4 i2c_core evdev ext3 
jbd mbcache dm_mirror dm_log dm_snapshot dm_mod thermal processor fan 
thermal_sys cciss scsi_mod [last unloaded: bonding]
Dec 14 21:25:17 server2 kernel: [1480447.236466] Pid: 39, comm: xenwatch Not 
tainted 2.6.26-2-xen-amd64 #1
Dec 14 21:25:17 server2 kernel: [1480447.236466] RIP: e030:[a0346101] 
 [a0346101] :8021q:__vlan_find_group+0x25/0x36
Dec 14 21:25:17 server2 kernel: [1480447.236466] RSP: e02b:88001fde1bc8  
EFLAGS: 00010202
Dec 14 21:25:17 server2 kernel: [1480447.236466] RAX: 8800011aae68 RBX: 
0005 RCX: a034a760
Dec 14 21:25:17 server2 kernel: [1480447.236466] RDX: 4068 RSI: 
0005 RDI: 88001b484000
Dec 14 21:25:17 server2 kernel: [1480447.236466] RBP: 88001b484000 R08: 
 R09: 880006de81d8
Dec 14 21:25:17 server2 kernel: [1480447.236466] R10: 88001b5a9008 R11: 
80427778 R12: a01d2c60
Dec 14 21:25:17 server2 kernel: [1480447.236466] R13: 88001b484000 R14: 
0005 R15: 
Dec 14 21:25:17 server2 kernel: [1480447.236466] FS:  7f91e60df6e0() 
GS:8053a000() knlGS:
Dec 14 21:25:17 server2 kernel: [1480447.236466] CS:  e033 DS:  ES: 
Dec 14 21:25:17 server2 kernel: [1480447.236466] DR0:  DR1: 
 DR2: 
Dec 14 21:25:17 server2 kernel: [1480447.236466] DR3:  DR6: 
0ff0 DR7: 0400
Dec 14 21:25:17 server2 kernel: [1480447.236466] Process xenwatch (pid: 39, 
threadinfo 88001fde, task 88001fdd82c0)
Dec 14 21:25:17 server2 kernel: [1480447.236466] Stack:  a0346545 
0010 803cfc0d 
Dec 14 21:25:17 server2 kernel: [1480447.236466]   
fff1 a01d2c60 88001b484000
Dec 14 21:25:17 server2 kernel: [1480447.236466]  0005 
 80242a24 88001b484000
Dec 14 21:25:17 server2 kernel: [1480447.236466] Call Trace:
Dec 14 21:25:17 server2 kernel: [1480447.236466]  [a0346545] ? 
:8021q:vlan_device_event+0x80/0x3a8
Dec 14 21:25:17 server2 kernel: [1480447.236466]  [803cfc0d] ? 
rtmsg_ifinfo+0xa1/0xd1
Dec 14 21:25:17 server2 kernel: [1480447.236466]  [80242a24] ? 
notifier_call_chain+0x29/0x4c
Dec 14 21:25:17 server2 kernel: [1480447.236466]  [803c7a3d] ? 
register_netdevice+0x28a/0x2ca
Dec 14 21:25:17 server2 kernel: [1480447.236466]  [8038b9c8] ? 
netif_alloc+0x16d/0x193
Dec 14 21:25:17 server2 kernel: [1480447.236466]  [8038ae8f] ? 
backend_create_netif+0x4e/0x8f
Dec 14 21:25:17 server2 kernel: [1480447.236466]  [8038b53c] ? 
netback_probe+0x15e/0x1cf
Dec 14 21:25:17 server2 kernel: [1480447.236466]  [803841c0] ? 
read_otherend_details+0x7a/0xae
Dec 14 21:25:17 server2 kernel: [1480447.236466]  [8038459a] ? 
xenbus_dev_probe+0x77/0xee
Dec 14 21:25:17 server2 kernel: [1480447.236466]  [8037968c] ? 
driver_probe_device+0xd0/0x14d
Dec 14 21:25:17 server2 kernel: [1480447.236466]  [80379776] ? 
__device_attach+0x0/0x5
Dec 14 21:25:17 server2 kernel: [1480447.236466]  [80378b8f] ? 
bus_for_each_drv+0x43/0x72
Dec 14 21:25:17 server2 kernel: [1480447.236466]  [80242919] ? 
down+0xe/0x36
Dec 14 21:25:17 server2 kernel: [1480447.236466]  [803797f7] ? 
device_attach+0x59/0x6a
Dec 14 21:25:17 server2 kernel: [1480447.236466]  [803789dc] ? 
bus_attach_device+0x27/0x5b
Dec 14 21:25:17 server2 kernel: [1480447.236466]  [80377b42] ? 
device_add+0x3a6/0x526
Dec 14 21:25:17 server2 kernel: [1480447.236466]  [80383e29] ? 
xenbus_probe_node+0x11e/0x19f
Dec 14 21:25:17 server2 kernel: [1480447.236466]  [80383ffe] ? 
xenbus_dev_changed+0x154/0x170
Dec 14 21:25:17

Processed: severity of 607114 is important

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

 severity 607114 important
Bug #607114 [linux-image-2.6-xen-amd64] Unresponsive Xen's dom0 system after 
'general protection fault'
Severity set to 'important' from 'critical'

 thanks
Stopping processing here.

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

Bug#607114: Same error on second server

I got similar messages some days ago on different hardware (see attached 
file).

Both servers are
- running the same version of kernel and Debian
- inter-connected with two Ethernet cross-cables in bond 
(balance-rr) with bridge and two vlans with MTU 9000 on top of it

- totally different on hardware
- server1 is Xeon 3210 based with all Intel Ethernet cards
- server2 is Opteron 2431 based with Broadcom Ethernet cards

--
Peter Viskup
Dec  5 23:10:31 server1 kernel: [350429.816318] BUG: unable to handle kernel 
paging request at 004817f0
Dec  5 23:10:31 server1 kernel: [350429.816356] IP: [a01e5101] 
:8021q:__vlan_find_group+0x25/0x36
Dec  5 23:10:31 server1 kernel: [350429.816390] PGD 11cbf067 PUD 1ebb5067 PMD 
11cfc067 PTE 0
Dec  5 23:10:31 server1 kernel: [350429.816429] Oops:  [1] SMP 
Dec  5 23:10:31 server1 kernel: [350429.816479] CPU 0 
Dec  5 23:10:31 server1 kernel: [350429.816522] Modules linked in: xt_physdev 
ipt_MASQUERADE ipt_LOG xt_state iptable_mangle xt_tcpudp iptable_nat nf_nat 
nf_conntrack_ipv4 nf_conntrack iptable_filter ip_tables x_tables bridge ipv6 
dm_crypt crypto_blkcipher 8021q coretemp ipmi_poweroff ipmi_watchdog ipmi_si 
ipmi_devintf ipmi_msghandler bonding loop serio_raw psmouse i2c_i801 pcspkr 
i2c_core button shpchp pci_hotplug evdev ext3 jbd mbcache dm_mirror dm_log 
dm_snapshot dm_mod raid1 md_mod sd_mod floppy ahci libata scsi_mod dock e1000 
ehci_hcd uhci_hcd e1000e thermal processor fan thermal_sys [last unloaded: 
scsi_wait_scan]
Dec  5 23:10:31 server1 kernel: [350429.817142] Pid: 7066, comm: vconfig Not 
tainted 2.6.26-2-xen-amd64 #1
Dec  5 23:10:31 server1 kernel: [350429.817197] RIP: e030:[a01e5101]  
[a01e5101] :8021q:__vlan_find_group+0x25/0x36
Dec  5 23:10:31 server1 kernel: [350429.817292] RSP: e02b:880011de3e10  
EFLAGS: 00010206
Dec  5 23:10:31 server1 kernel: [350429.817343] RAX: 88001ed4c4c0 RBX: 
000a RCX: 000a
Dec  5 23:10:31 server1 kernel: [350429.817427] RDX: 00481800 RSI: 
000a RDI: 88001d896000
Dec  5 23:10:31 server1 kernel: [350429.817510] RBP: ffde R08: 
7f31b6a02440 R09: 
Dec  5 23:10:31 server1 kernel: [350429.817594] R10:  R11: 
802e3c42 R12: 88001ded76a0
Dec  5 23:10:31 server1 kernel: [350429.817677] R13: 88001d896000 R14: 
000a R15: 7fffeec1
Dec  5 23:10:31 server1 kernel: [350429.817762] FS:  7f31b6e5d6e0() 
GS:8053a000() knlGS:
Dec  5 23:10:31 server1 kernel: [350429.817849] CS:  e033 DS:  ES: 
Dec  5 23:10:31 server1 kernel: [350429.817895] DR0:  DR1: 
 DR2: 
Dec  5 23:10:31 server1 kernel: [350429.817979] DR3:  DR6: 
0ff0 DR7: 0400
Dec  5 23:10:31 server1 kernel: [350429.818063] Process vconfig (pid: 7066, 
threadinfo 880011de2000, task 88001da65100)
Dec  5 23:10:31 server1 kernel: [350429.818150] Stack:  a01e511a 
000a a01e51c9 ffbf
Dec  5 23:10:31 server1 kernel: [350429.818253]  a01e5a36 
646e6f62 0031 
Dec  5 23:10:31 server1 kernel: [350429.818351]  000a 
  
Dec  5 23:10:31 server1 kernel: [350429.818418] Call Trace:
Dec  5 23:10:31 server1 kernel: [350429.818493]  [a01e511a] ? 
:8021q:__find_vlan_dev+0x8/0x36
Dec  5 23:10:31 server1 kernel: [350429.818550]  [a01e51c9] ? 
:8021q:vlan_check_real_dev+0x81/0x8e
Dec  5 23:10:31 server1 kernel: [350429.818608]  [a01e5a36] ? 
:8021q:vlan_ioctl_handler+0x1c9/0x363
Dec  5 23:10:31 server1 kernel: [350429.818669]  [80276818] ? 
handle_mm_fault+0x5f8/0xc46
Dec  5 23:10:31 server1 kernel: [350429.818724]  [803bde80] ? 
sk_prot_alloc+0x46/0xa4
Dec  5 23:10:31 server1 kernel: [350429.818778]  [803baef5] ? 
sock_ioctl+0x171/0x1f8
Dec  5 23:10:31 server1 kernel: [350429.818831]  [802968b5] ? 
vfs_ioctl+0x21/0x6b
Dec  5 23:10:31 server1 kernel: [350429.818883]  [80296b47] ? 
do_vfs_ioctl+0x248/0x261
Dec  5 23:10:31 server1 kernel: [350429.818937]  [80296bb1] ? 
sys_ioctl+0x51/0x70
Dec  5 23:10:31 server1 kernel: [350429.818990]  [8020b528] ? 
system_call+0x68/0x6d
Dec  5 23:10:31 server1 kernel: [350429.819043]  [8020b4c0] ? 
system_call+0x0/0x6d
Dec  5 23:10:31 server1 kernel: [350429.819095] 
Dec  5 23:10:31 server1 kernel: [350429.819132] 
Dec  5 23:10:31 server1 kernel: [350429.819169] Code: 89 e8 5d 41 5c c3 8b 97 
80 00 00 00 89 d0 c1 e8 05 31 d0 83 e0 1f 48 8b 14 c5 a0 aa 1e a0 eb 03 48 8b 
12 48 85 d2 75 03 31 c0 c3 48 39 7a f0 48 8b 02 0f 18 08 48 8d 42 f0 75 e5 c3 
53 89 f3 e8 
Dec  5 23:10:31 server1 kernel: [350429.819220] RIP  [a01e5101] 
:8021q:__vlan_find_group+0x25/0x36
Dec  5 23:10:31 server1 kernel:

Bug#607114: Unresponsive Xen's dom0 system after 'general protection fault'

Peter Viskup skupko...@gmail.com writes:
 Package: linux-image-2.6-xen-amd64
 Version: 2.6.26+17+lenny1

Can you try linux-image-2.6.32-5-xen-amd64 2.6.32-29 from debian
squeeze? You probably should be able to install it to a lenny system
without upgrading the system otherwise.





-- 
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/8462uw83or@sauna.l.org

Bug#607114: Unresponsive Xen's dom0 system after 'general protection fault'

2010-12-14 Thread Bastian Blank

On Tue, Dec 14, 2010 at 11:06:28PM +0200, Timo Juhani Lindfors wrote:
 Can you try linux-image-2.6.32-5-xen-amd64 2.6.32-29 from debian
 squeeze? You probably should be able to install it to a lenny system
 without upgrading the system otherwise.

Install, yes. Use, no. It needs Xen 4.0.

Bastian

-- 
Too much of anything, even love, isn't necessarily a good thing.
-- Kirk, The Trouble with Tribbles, stardate 4525.6



-- 
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/20101214212720.ga14...@wavehammer.waldi.eu.org

Bug#607114: Unresponsive Xen's dom0 system after 'general protection fault'


On 12/14/2010 10:27 PM, Bastian Blank wrote:

On Tue, Dec 14, 2010 at 11:06:28PM +0200, Timo Juhani Lindfors wrote:
   

Can you try linux-image-2.6.32-5-xen-amd64 2.6.32-29 from debian
squeeze? You probably should be able to install it to a lenny system
without upgrading the system otherwise.
 

Install, yes. Use, no. It needs Xen 4.0.

Bastian

   

Hello Bastian and Timo,
thank you for your quick responses.
I want to run official Debian stable versions.
Just find there is backports version linux-image-2.6.32-bpo.5-xen-amd64 
available.
I need to know what the bug is if the move to this backports kernel will 
help - just before I will install it. I am running production servers 
and cannot just test that.


--
Peter Viskup



--
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/4d07e4f0.4080...@gmail.com

Bug#607141: xm block-attach failed on domU


Package: linux-image-2.6-xen-amd64
Version:  2.6.26-26lenny1
Severity: critical
Tags: lenny

Execution of xm block-attach to PV domU failed and I have got Ooops 
kernel messages in attachment.
After that domU wasn't manageable from dom0 - all xm commands were not 
successful and I had to shutdown the domU from the pty (ssh) console.

Both dom0 and domU were running same kernel version.

--
Peter Viskup
Dec 13 16:29:04 tis kernel: [83118.676876] BUG: unable to handle kernel NULL 
pointer dereference at 
Dec 13 16:29:04 tis kernel: [83118.676898] IP: [8038d104] 
backend_changed+0x1bf/0x23a
Dec 13 16:29:04 tis kernel: [83118.676920] PGD 1e82f067 PUD 1f1a8067 PMD 0 
Dec 13 16:29:04 tis kernel: [83118.676933] Oops:  [1] SMP 
Dec 13 16:29:04 tis kernel: [83118.676941] CPU 0 
Dec 13 16:29:04 tis kernel: [83118.676948] Modules linked in: iptable_filter 
ip_tables x_tables ipv6 xfs evdev ext3 jbd mbcache dm_mirror dm_log dm_snapshot 
dm_mod thermal_sys cciss scsi_mod
Dec 13 16:29:04 tis kernel: [83118.676991] Pid: 19, comm: xenwatch Not tainted 
2.6.26-2-xen-amd64 #1
Dec 13 16:29:04 tis kernel: [83118.677000] RIP: e030:[8038d104]  
[8038d104] backend_changed+0x1bf/0x23a
Dec 13 16:29:04 tis kernel: [83118.677015] RSP: e02b:88001fd11e60  EFLAGS: 
00010246
Dec 13 16:29:04 tis kernel: [83118.677023] RAX:  RBX: 
880006dec000 RCX: 
Dec 13 16:29:04 tis kernel: [83118.677032] RDX: 88001fd11de8 RSI: 
0005 RDI: 88001f12c400
Dec 13 16:29:04 tis kernel: [83118.677041] RBP: 8038327f R08: 
0005 R09: 
Dec 13 16:29:04 tis kernel: [83118.677050] R10: 8800850bb000 R11: 
8038cf45 R12: 88001f12c400
Dec 13 16:29:04 tis kernel: [83118.677059] R13: 8057c580 R14: 
8057d1c0 R15: 
Dec 13 16:29:04 tis kernel: [83118.677070] FS:  7f53a5d766e0() 
GS:8053a000() knlGS:
Dec 13 16:29:04 tis kernel: [83118.677080] CS:  e033 DS:  ES: 
Dec 13 16:29:04 tis kernel: [83118.677087] DR0:  DR1: 
 DR2: 
Dec 13 16:29:04 tis kernel: [83118.677097] DR3:  DR6: 
0ff0 DR7: 0400
Dec 13 16:29:04 tis kernel: [83118.677106] Process xenwatch (pid: 19, 
threadinfo 88001fd1, task 88001fd08140)
Dec 13 16:29:04 tis kernel: [83118.677116] Stack:  8057c580 
80383a01 88001f059c40 88001f12c400
Dec 13 16:29:04 tis kernel: [83118.677133]  8052a968 8057c580 
8057d1c0 80381c19
Dec 13 16:29:04 tis kernel: [83118.677148]    
00058038327f 88001f1f2d80
Dec 13 16:29:04 tis kernel: [83118.677161] Call Trace:
Dec 13 16:29:04 tis kernel: [83118.677172]  [80383a01] ? 
xenbus_device_find+0x28/0x31
Dec 13 16:29:04 tis kernel: [83118.677184]  [80381c19] ? 
xenbus_read_driver_state+0x26/0x3b
Dec 13 16:29:04 tis kernel: [83118.677195]  [8038327f] ? 
xenwatch_thread+0x0/0x186
Dec 13 16:29:04 tis kernel: [83118.677206]  [8038295d] ? 
xenwatch_handle_callback+0x15/0x48
Dec 13 16:29:04 tis kernel: [83118.677216]  [803833ec] ? 
xenwatch_thread+0x16d/0x186
Dec 13 16:29:04 tis kernel: [83118.677227]  [8023f6ad] ? 
autoremove_wake_function+0x0/0x2e
Dec 13 16:29:04 tis kernel: [83118.677237]  [8023f57f] ? 
kthread+0x47/0x74
Dec 13 16:29:04 tis kernel: [83118.677247]  [802282ec] ? 
schedule_tail+0x27/0x5c
Dec 13 16:29:04 tis kernel: [83118.677257]  [8020be28] ? 
child_rip+0xa/0x12
Dec 13 16:29:04 tis kernel: [83118.677268]  [8023f538] ? 
kthread+0x0/0x74
Dec 13 16:29:04 tis kernel: [83118.677276]  [8020be1e] ? 
child_rip+0x0/0x12
Dec 13 16:29:04 tis kernel: [83118.677283] 
Dec 13 16:29:04 tis kernel: [83118.677287] 
Dec 13 16:29:04 tis kernel: [83118.677291] Code: 23 3e 17 00 c6 40 01 00 80 38 
00 74 05 e8 f1 00 ff ff 48 8b 7b 08 e8 56 8e f7 ff c7 83 9c 1a 00 00 01 00 00 
00 eb 74 48 8b 43 08 8b 38 c1 e7 14 0b 78 04 e8 10 40 f2 ff 48 85 c0 48 89 c5 
75 16 
Dec 13 16:29:04 tis kernel: [83118.677391] RIP  [8038d104] 
backend_changed+0x1bf/0x23a
Dec 13 16:29:04 tis kernel: [83118.677402]  RSP 88001fd11e60
Dec 13 16:29:04 tis kernel: [83118.677408] CR2: 
Dec 13 16:29:04 tis kernel: [83118.677419] ---[ end trace 75e2ecdeadd46e28 ]---

Processed: bug 596741 is not forwarded, tagging 596741, reassign 596741 to gnome-power-manager

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

 notforwarded 596741
Bug #596741 [linux-2.6] regression: CPU fan fast after resume: won't climb back 
down
Unset Bug forwarded-to-address
 tags 596741 - upstream
Bug #596741 [linux-2.6] regression: CPU fan fast after resume: won't climb back 
down
Removed tag(s) upstream.
 # kernel absolved (see comments in bugzilla). More testing to come.
 reassign 596741 gnome-power-manager
Bug #596741 [linux-2.6] regression: CPU fan fast after resume: won't climb back 
down
Bug reassigned from package 'linux-2.6' to 'gnome-power-manager'.
Bug No longer marked as found in versions 2.6.32-21.
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
596741: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=596741
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/handler.s.c.129236725420289.transcr...@bugs.debian.org

Processed: severity of 607141 is important

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

 severity 607141 important
Bug #607141 [linux-image-2.6-xen-amd64] xm block-attach failed on domU
Severity set to 'important' from 'critical'

 thanks
Stopping processing here.

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

Bug#607114: Unresponsive Xen's dom0 system after 'general protection fault'

Peter Viskup skupko...@gmail.com writes:
 I want to run official Debian stable versions.

I understand that perfectly. However, it is not likely that this can
be fixed for 2.6.26 -- the best thing you can do about this problem is
to ensure that it gets fixed before squeeze is released.

 Just find there is backports version
 linux-image-2.6.32-bpo.5-xen-amd64 available.
 I need to know what the bug is if the move to this backports kernel
 will help - just before I will install it. I am running production
 servers and cannot just test that.

Difficult situation indeed. In that case you probably only can hope
that somebody else is able to reproduce the bug on their system.  I
have experince only on debugging domUs, I don't even know how to dump
the state of a dom0 to disk.




-- 
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/841v5k81im@sauna.l.org

Bug#607154: make-kpkg --initrd does not work

2010-12-14 Thread jamesb

Package: initramfs-tools
Version: 0.92o
Severity: important


make-kpkg --initrd 

apparently there's no hook script installed for making the initrd.img in 
/etc/kernel/conf.d/postinst.d or did
the location for this script/conf changed?

i downloaded the deb(initramfs-tools) and extracted it included the control 
files.. nowhere is /etc/kernel/conf.d/postinst.d mentioned..

there is /usr/share/kernel-package/examples/etc/kernel/postinst.d/initramfs 
from the kernel-package however.. 



-- Package-specific info:
-- /proc/cmdline
root=UUID=35d2bbe2-652a-47e0-acf2-2c4e29060983 ro vga=0x317

-- /proc/filesystems
ext3
fuseblk
ufsd
hfsplus

-- lsmod
Module  Size  Used by
hfsplus75912  0 
nvidia  10274888  38 
nls_utf86272  0 
ufsd  483088  2 
nls_base   12932  3 hfsplus,nls_utf8,ufsd
vboxnetadp 10048  0 
vboxnetflt 17040  0 
vboxdrv  1766444  2 vboxnetadp,vboxnetflt
powernow_k817156  0 
cpufreq_conservative11784  0 
cpufreq_ondemand   11792  3 
cpufreq_powersave   6400  0 
cpufreq_stats   9120  0 
freq_table  9344  3 powernow_k8,cpufreq_ondemand,cpufreq_stats
cpufreq_userspace   8452  0 
ipv6  288456  20 
binfmt_misc13580  1 
fuse   53184  2 
sbp2   25356  0 
loop   19468  2 
snd_usb_audio  91296  1 
snd_pcm_oss41760  0 
snd_mixer_oss  18816  2 snd_pcm_oss
snd_pcm81800  2 snd_usb_audio,snd_pcm_oss
snd_page_alloc 13072  1 snd_pcm
snd_usb_lib20352  1 snd_usb_audio
snd_hwdep  12040  1 snd_usb_audio
snd_seq_dummy   7428  0 
snd_seq_oss33152  0 
serio_raw   9988  0 
snd_seq_midi   11072  0 
psmouse42268  0 
snd_rawmidi26784  2 snd_usb_lib,snd_seq_midi
snd_seq_midi_event 11904  2 snd_seq_oss,snd_seq_midi
snd_seq54304  6 
snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event
i2c_piix4  13072  0 
i2c_core   27936  2 nvidia,i2c_piix4
snd_timer  25744  2 snd_pcm,snd_seq
snd_seq_device 11668  5 
snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq
snd63688  10 
snd_usb_audio,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_hwdep,snd_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
soundcore  12064  2 snd
button 11680  0 
evdev  14208  5 
led_class   8968  0 
wmi11712  0 
ext3  125072  1 
jbd51240  1 ext3
mbcache12804  1 ext3
sg 36448  0 
usb_storage95936  1 
usbhid 45792  1 
hid41792  1 usbhid
ff_memless  9224  1 usbhid
sr_mod 19652  1 
cdrom  37928  1 sr_mod
sd_mod 29376  6 
ata_generic10116  0 
ide_pci_generic 9220  0 [permanent]
r8169  36100  0 
ahci   33036  4 
libata165600  2 ata_generic,ahci
atiixp  8324  0 [permanent]
ehci_hcd   36108  0 
ohci_hcd   25092  0 
ide_core  128284  2 ide_pci_generic,atiixp
ohci1394   32692  0 
sky2   48132  0 
scsi_mod  161016  6 sbp2,sg,usb_storage,sr_mod,sd_mod,libata
dock   14112  1 libata
ieee1394   93944  2 sbp2,ohci1394
thermal22688  0 
processor  42304  2 powernow_k8,thermal
fan 9352  0 
thermal_sys17728  3 thermal,processor,fan

-- /etc/kernel-img.conf
# Kernel image management overrides
# See kernel-img.conf(5) for details
do_symlinks = yes
relative_links = yes
do_bootloader = no
do_bootfloppy = no
do_initrd = yes
link_in_boot = no
postinst_hook = update-grub
postrm_hook   = update-grub

-- /etc/initramfs-tools/initramfs.conf
MODULES=most
BUSYBOX=y
KEYMAP=n
BOOT=local
DEVICE=eth0
NFSROOT=auto


-- System Information:
Debian Release: 5.0.6
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.26-2-amd64 (SMP w/3 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages initramfs-tools depends on:
ii  cpio  2.9-13lenny1   GNU cpio -- a program to manage ar
ii  findutils 4.4.0-2utilities for finding files--find,
ii  klibc-utils   1.5.12-2   small utilities built with klibc f
ii  module-init-tools 3.4-1  tools for managing Linux kernel mo
ii  udev  0.125-7+lenny3 /dev/ and hotplug management daemo

Versions of packages initramfs-tools recommends:
ii  busybox

Bug#607114: Unresponsive Xen's dom0 system after 'general protection fault'

On Tue, 2010-12-14 at 21:02 +0100, Peter Viskup wrote:
 Package: linux-image-2.6-xen-amd64
 Version: 2.6.26+17+lenny1
 Severity: critical
 Tags: lenny
 
 After execution of xm create command I got messages in attached file.
 I got this for second time within one week. Not sure what the root cause is.
 Right now all of commands working with networking just hangs. Looks like 
 it has something to do with 8021q module.
 All Xen domU's with NATed networks are reachable.

Do you create or modify VLAN devices when creating a new domain?

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

Processed: tagging 607114

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

 tags 607114 + moreinfo
Bug #607114 [linux-image-2.6-xen-amd64] Unresponsive Xen's dom0 system after 
'general protection fault'
Added tag(s) moreinfo.
 thanks
Stopping processing here.

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

Re: [PATCH] Fix condition for adding IDE or SCSI disk driver when MODULES=dep

On Tue, 2010-12-14 at 19:45 +0100, maximilian attems wrote:
[...]
  diff --git a/hook-functions b/hook-functions
  index 0684296..da16478 100644
  --- a/hook-functions
  +++ b/hook-functions
  @@ -349,7 +349,7 @@ dep_add_modules()
  sys_walk_mod_add ${root_dev_path}
   
  # catch old-style IDE
  -   if [ -e /sys/bus/ide/devices/ ]; then
  +   if [ -d ${DESTDIR}/lib/modules/${version}/kernel/drivers/ide ]; then
 
 Not sure I like this change, as this is a noop in any of our linux-2.6
[...]

This is supposed to test whether we've already installed any IDE modules
in the initramfs build directory; is that not what DESTDIR points to?

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#601187: linux-image-2.6.32-5-amd64: Please apply patch for shared I/O region support

On Tue, 2010-12-14 at 17:23 +0100, Mike Hommey wrote:
 On Mon, Dec 06, 2010 at 08:44:14AM +0100, Mike Hommey wrote:
  On Mon, Dec 06, 2010 at 04:25:13AM +, Ben Hutchings wrote:
   On Thu, 2010-12-02 at 13:39 +0100, Mike Hommey wrote:
Is the following going to be considered for squeeze?
   
   I've cherry-picked all the necessary changes (I think):
   
   8b6d043b7ee2d1b819dc833d677ea2aead71a0c0 resource: shared I/O region 
   support
   729d273aa7c86eb1406ade4eadf249cff188bf9a hwmon: (f71882fg) Acquire I/O 
   regions while we're working with them
   cadb86570c41fe52a0ea741f1f9775e3412f0167 hwmon: f71882fg: use a muxed 
   resource lock for the Super I/O port
   96cb4eb019ce3185ec0d946a74b5a2202f5067c9 watchdog: f71808e_wdt: new 
   watchdog driver for Fintek F71808E and F71882FG
  
  That's the set of patches I've been using. Awesome. Thanks.
 
 It appears I was wrong. There's one small patch missing to get support
 for the F71889FG watchdog:
 dee00abbbcab97b8ee3bbafb5e786dde83e26741 watchdog: f71808e_wdt: add support 
 for the F71889FG
 
 Interestingly, trying to load the bundled f71808e_wdt doesn't print a
 error, which would be something about no device being found or
 something like that:
 # modprobe f71808e_wdt
 FATAL: Error inserting f71808e_wdt 
 (/lib/modules/2.6.32-5-amd64/kernel/drivers/watchdog/f71808e_wdt.ko): Kernel 
 does not have module support

Some idiot made the driver return ENOSYS instead of ENODEV for
recognised but unsupported Fintek chips.

On a system with no such hardware, I get:

FATAL: Error inserting f71808e_wdt 
(/lib/modules/2.6.32-5-amd64/kernel/drivers/watchdog/f71808e_wdt.ko): No such 
device

 Please take whichever decision you want wrt this driver, considering
 the release schedule, I'd understand if that's wontfix for now.
[...]

I think so, it's not like a disk or network controller where people
really need them to work from the start.

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#607154: marked as done (make-kpkg --initrd does not work)

Your message dated Wed, 15 Dec 2010 02:43:32 +
with message-id 1292381012.3136.616.ca...@localhost
and subject line Re: Bug#607154: make-kpkg --initrd does not work
has caused the Debian Bug report #607154,
regarding make-kpkg --initrd does not work
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
607154: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=607154
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: initramfs-tools
Version: 0.92o
Severity: important


make-kpkg --initrd 

apparently there's no hook script installed for making the initrd.img in 
/etc/kernel/conf.d/postinst.d or did
the location for this script/conf changed?

i downloaded the deb(initramfs-tools) and extracted it included the control 
files.. nowhere is /etc/kernel/conf.d/postinst.d mentioned..

there is /usr/share/kernel-package/examples/etc/kernel/postinst.d/initramfs 
from the kernel-package however.. 



-- Package-specific info:
-- /proc/cmdline
root=UUID=35d2bbe2-652a-47e0-acf2-2c4e29060983 ro vga=0x317

-- /proc/filesystems
ext3
fuseblk
ufsd
hfsplus

-- lsmod
Module  Size  Used by
hfsplus75912  0 
nvidia  10274888  38 
nls_utf86272  0 
ufsd  483088  2 
nls_base   12932  3 hfsplus,nls_utf8,ufsd
vboxnetadp 10048  0 
vboxnetflt 17040  0 
vboxdrv  1766444  2 vboxnetadp,vboxnetflt
powernow_k817156  0 
cpufreq_conservative11784  0 
cpufreq_ondemand   11792  3 
cpufreq_powersave   6400  0 
cpufreq_stats   9120  0 
freq_table  9344  3 powernow_k8,cpufreq_ondemand,cpufreq_stats
cpufreq_userspace   8452  0 
ipv6  288456  20 
binfmt_misc13580  1 
fuse   53184  2 
sbp2   25356  0 
loop   19468  2 
snd_usb_audio  91296  1 
snd_pcm_oss41760  0 
snd_mixer_oss  18816  2 snd_pcm_oss
snd_pcm81800  2 snd_usb_audio,snd_pcm_oss
snd_page_alloc 13072  1 snd_pcm
snd_usb_lib20352  1 snd_usb_audio
snd_hwdep  12040  1 snd_usb_audio
snd_seq_dummy   7428  0 
snd_seq_oss33152  0 
serio_raw   9988  0 
snd_seq_midi   11072  0 
psmouse42268  0 
snd_rawmidi26784  2 snd_usb_lib,snd_seq_midi
snd_seq_midi_event 11904  2 snd_seq_oss,snd_seq_midi
snd_seq54304  6 
snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event
i2c_piix4  13072  0 
i2c_core   27936  2 nvidia,i2c_piix4
snd_timer  25744  2 snd_pcm,snd_seq
snd_seq_device 11668  5 
snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq
snd63688  10 
snd_usb_audio,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_hwdep,snd_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
soundcore  12064  2 snd
button 11680  0 
evdev  14208  5 
led_class   8968  0 
wmi11712  0 
ext3  125072  1 
jbd51240  1 ext3
mbcache12804  1 ext3
sg 36448  0 
usb_storage95936  1 
usbhid 45792  1 
hid41792  1 usbhid
ff_memless  9224  1 usbhid
sr_mod 19652  1 
cdrom  37928  1 sr_mod
sd_mod 29376  6 
ata_generic10116  0 
ide_pci_generic 9220  0 [permanent]
r8169  36100  0 
ahci   33036  4 
libata165600  2 ata_generic,ahci
atiixp  8324  0 [permanent]
ehci_hcd   36108  0 
ohci_hcd   25092  0 
ide_core  128284  2 ide_pci_generic,atiixp
ohci1394   32692  0 
sky2   48132  0 
scsi_mod  161016  6 sbp2,sg,usb_storage,sr_mod,sd_mod,libata
dock   14112  1 libata
ieee1394   93944  2 sbp2,ohci1394
thermal22688  0 
processor  42304  2 powernow_k8,thermal
fan 9352  0 
thermal_sys17728  3 thermal,processor,fan

-- /etc/kernel-img.conf
# Kernel image management overrides
# See kernel-img.conf(5) for details
do_symlinks = yes
relative_links = yes
do_bootloader = no
do_bootfloppy = no
do_initrd = yes
link_in_boot = no
postinst_hook = update-grub
postrm_hook   = update-grub

-- /etc/initramfs-tools/initramfs.conf
MODULES=most
BUSYBOX=y
KEYMAP=n

Processed: linux-2.6: Improper po-debconf spanish translation accepted, please rectify

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

 reopen 600694
Bug #600694 {Done: Ben Hutchings b...@decadent.org.uk} [linux-2.6] [INTL:es] 
Updated Spanish debconf translation
'reopen' may be inappropriate when a bug has been closed with a version;
you may need to use 'found' to remove fixed versions.
 severity 600694 normal
Bug #600694 [linux-2.6] [INTL:es] Updated Spanish debconf translation
Severity set to 'normal' from 'wishlist'

 thanks
Stopping processing here.

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

Processed: severity of 607095 is important

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

 severity 607095 important
Bug #607095 [linux-2.6] linux-2.6: backport 2d9e667e (disable IOMMU for iGFX on 
some chipsets)
Severity set to 'important' from 'normal'

 thanks
Stopping processing here.

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

Processed: tagging 607095

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

 # Automatically generated email from bts, devscripts version 2.10.35lenny7
 tags 607095 + pending
Bug #607095 [linux-2.6] linux-2.6: backport 2d9e667e (disable IOMMU for iGFX on 
some chipsets)
Added tag(s) pending.

End of message, stopping processing here.

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

Processed: tagging 555835

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

 # Automatically generated email from bts, devscripts version 2.10.35lenny7
 tags 555835 + pending
Bug #555835 [linux-2.6] linux-image-2.6.30-2-686: Unusual usb storage Samsung 
YP-CP3 not working
Bug #555836 [linux-2.6] linux-image-2.6.30-2-686: Unusual usb_storage device 
Samsung YP-CP3 not working
Added tag(s) pending.
Added tag(s) pending.

End of message, stopping processing here.

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

Bug#601697: marked as done (kernel errors after upgrade, X system left in a non-working state (i915))

Your message dated Wed, 15 Dec 2010 04:22:44 +
with message-id 1292386964.3136.628.ca...@localhost
and subject line Re: Bug#601697: Recent update closes the bug
has caused the Debian Bug report #601697,
regarding kernel errors after upgrade, X system left in a non-working state 
(i915)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
601697: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=601697
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: upgrade-reports
Severity: normal
Tags: squeeze

On two different systems, the apt-get dist-upgrade within testing
(Squeeze) during the last month has left the Xorg system in an
unusable state. In both cases, the upgrade included a kernel-image
upgrade, but additionally some hundreds of packages.

In the first case, linux-image-2.6.32-5-686 was updated from 2.6.32-20
to 2.6.32-23. In this case, the laptop has an integrated intel video
card, using the xorg-xserver-intel driver.

In the second case, of today, linux-image-2.6.32-5-686 was updated
from some version to 2.6.32-26, on an Acer laptop with ATI card, using
the Xorg ati driver.

In both cases, directly after upgrade, kernel panic messages start to
appear in the dmesg log, with some weird behaviour. After reboot,
the X system does not start any more, in both cases complaining
something about being unable to loag GL stuff, and not finding the
Synaptics device or something.

In the first case, I reverted back to using linux-image-2.6.30, which
was still installed on the laptop. With this kernel everything
functions exactly as before. In the second case, the machine does
boot, but I can't get the Xorg system working at all.

In a way, this seems like a kernel problem, except for the fact that
kernel panics appear as soon as the system was upgraded, before
rebooting the computer.

Of the first case, I cannot provide any log files; also in the second
case it is somewhat difficult, but I'll see what I can find.

I realize this is not a very detailed nor well documented bug report,
but in both cases the problems manifested after a major upgrade of
some hundreds of packages, and I'm really short of time currently. I
would not have sent this report otherwise but the same problem
manifests on two different machines after a similar upgrade with
almost two weeks time between.

All the best,

Harri K.


-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (990, 'testing')
Architecture: i386 (i686)

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


---End Message---
---BeginMessage---
On Tue, 2010-12-14 at 13:21 +0200, Harri Kiiskinen wrote:
 Update against squeeze of today (20101214) fixes the bug.
 
 Kernel image is linux-image-2.6.32-5-686 ver. 2.6.32-29.
 
 xserver-xorg-video-intel 2:2.13.0-2

Good, then I'm closing this bug.

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
---End Message---

Bug#606994: DMA error with b43 on HP Mini 1115NR under Debian Testing (Squeeze)

On Tue, 2010-12-14 at 09:47 +0300, Jonathon Anderson wrote:
 On Tue, Dec 14, 2010 at 4:51 AM, Ben Hutchings b...@decadent.org.uk wrote:
  A log with timestamps would be more helpful.
 
 I've attached a copy of log/messages that contains the error.  It's a
 different instance, but a reoccurrence of the same thing.
 
 You'll probably want to grep it for b43, but I left the log intact
 in case any of the surrounding context would be useful.

Thank you.

 Note that, though I had said this for the previous log:
 
 The preceding log was generated by 2.6.36.
  2.6.32 generated largely similar logs, except that it recommended PIO
  mode, rather than purporting to switch to it.
[...]

Debian's package of Linux 2.6.32 includes all the later fixes that
implement automatic switching to PIO mode.  It is only missing the
correction to that message.

I don't if it will help, but you can force b43 to use PIO mode from the
start by running:

rmmod b43
modprobe b43 pio=1

If that helps, you can make this configuration persistent by running:

echo /etc/modprobe.d/b43.conf 'options b43 pio=1'

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#606994: DMA error with b43 on HP Mini 1115NR under Debian Testing (Squeeze)

2010-12-14 Thread Jonathon Anderson

On Wed, Dec 15, 2010 at 7:44 AM, Ben Hutchings b...@decadent.org.uk wrote:
    echo /etc/modprobe.d/b43.conf 'options b43 pio=1'

I did exactly that relatively early in the troubleshooting process.
When I do this, the device doesn't work straight from boot.



--
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/aanlkti=vvnj9proxg4txaxfsqyg8xorxvo7glc10x...@mail.gmail.com

Bug#607163: firmware-ralink: USB Dongle using driver rt2870sta doesn't get wireless n Speeds

2010-12-14 Thread Lawrence

Package: firmware-ralink
Version: 0.27
Severity: normal

I have a Edimax Technology Co., Ltd EW-7711UTn nLite Wireless Adapter [Ralink 
RT2870]
adapter that is supposed to be a wireless n adapter, but I am only able to get 
a maximum speed of 54Mbps suggesting it is only running at G speeds

Here is the output of iwconfig wlan0
wlan0 Ralink STA  ESSID:Bayly Network  Nickname:RT2870STA
  Mode:Managed  Frequency=2.457 GHz  Access Point: 00:23:69:82:F5:AC
  Bit Rate=54 Mb/s
  RTS thr:off   Fragment thr:off
  Encryption key:46E3-AA0D-9B37-26ED-6E53-D43C-BAF0-A3BC
  Link Quality=77/100  Signal level:-51 dBm  Noise level:-83 dBm
  Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
  Tx excessive retries:0  Invalid misc:0   Missed beacon:0

The adapter is connected to a wireless n Access Point and I can confirm that 
the adapter is capable of achieving those speeds on windows XP.

Please let me know if you need any other information

Thanks,
Lawrence Bayly

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

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

firmware-ralink depends on no packages.

firmware-ralink recommends no packages.

Versions of packages firmware-ralink suggests:
ii  initramfs-tools   0.98.5 tools for generating an initramfs
ii  linux-image-2.6.32-5-686 [lin 2.6.32-29  Linux 2.6.32 for modern PCs

-- no debconf information



-- 
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/20101215051242.1797.68956.report...@athlonxp.bayly.local

Bug#607114: Unresponsive Xen's dom0 system after 'general protection fault'