Bug#418442: linux-2.6: please enable CONFIG_BLK_DEV_IO_TRACE

2007-07-25 Thread Mike Hommey
On Mon, Apr 09, 2007 at 08:43:00PM +0200, Bas Zoetekouw [EMAIL PROTECTED] 
wrote:
 Package: linux-2.6
 Severity: wishlist
 
 Could you please enable CONFIG_BLK_DEV_IO_TRACE in the default debian
 kernel?
 It's needed for blktrace, which I'm planning to upload to unstable
 soonish, now that the freeze is over.  It would be great if we could
 get it to work out of the box, without the user needing to build his
 own kernel.

I concur, please enable CONFIG_BLK_DEV_IO_TRACE.

Mike


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



Bug#434601: kernel -switching scsi devices on boot, unable to automount on startup

2007-07-25 Thread Mgr. Peter Tuharsky

Package: kernel-image-2.6-686-smp
Version: 2.6.18+6

I have dual Opteron server based on TYAN S2882-D Thunder K8SD Pro 
mainboard. Disks are IDE, SATA, SATA, SCSI RAID 5 on Adaptec 2130S PCI-X 
controller.



When booting standard kernel, I cannot have SATA and SCSI disks mounted 
automatically from fstab. Seems, that in the middle of booting process, 
the SCSI disks simply switch their positions.


First the SATA takes sda+sdb and SCSI takes sdc until the time of fsck. 
Then, upon mounting, SATA takes sdb+sdc and SCSI moves to sda.


As the disks have different partitioning, I get either fsck errors or 
mount errors, whatever I set the fstab.


The only way is to disable automatic mounting and perform the mound 
manually after the whole bootup process.



If I use custom compiled all-in-one kernel (without modules), everything 
keeps stable: SCSI takes sda, SATA takes sdb+sdc, definitely.



I attach kernel log files from Debian (2.6.18) and from custom 
(2.6.19.2) kernel.


datastore-2.6.18.log.gz
Description: GNU Zip compressed data


datastore-2.6.19.2.log.gz
Description: GNU Zip compressed data


Bug#432650: 2.6.21-2: cannot grab IDE ports, hangs on boot

2007-07-25 Thread Julien Puydt

I can confirm the same issue with 2.6.22-1 too, now it is out.

The ide-generic in /etc/initramfs-tools/modules trick also allows me to 
boot, but without DMA. My BIOS doesn't have any ide legacy, and is as up 
to date as possible (box is soon 3 years old).


It was working ok and doesn't anymore, so this is a regression : I don't 
think blaming the BIOS will help ;-)


What information could we give to help pinpoint what goes wrong?


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



Processed: reopening 434597, severity of 434597 is grave, reassign 434597 to yaird

2007-07-25 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 # Automatically generated email from bts, devscripts version 2.10.6
 reopen 434597
Bug#434597: Setting up linux-image-2.6.22-1-686 (2.6.22-2), mkinitrd.yaird 
failed to create initrd image.
Bug reopened, originator not changed.

 severity 434597 grave
Bug#434597: Setting up linux-image-2.6.22-1-686 (2.6.22-2), mkinitrd.yaird 
failed to create initrd image.
Severity set to `grave' from `critical'

 #reassigning to yaird, you shouldn't close bugs too fast
 reassign 434597 yaird 0.0.12-20
Bug#434597: Setting up linux-image-2.6.22-1-686 (2.6.22-2), mkinitrd.yaird 
failed to create initrd image.
Bug reassigned from package `linux-image-2.6.22-1-686' to `yaird'.


End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


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



Bug#434597: reopening 434597, severity of 434597 is grave, reassign 434597 to yaird

2007-07-25 Thread Touko Korpela
# Automatically generated email from bts, devscripts version 2.10.6
reopen 434597 
severity 434597 grave
#reassigning to yaird, you shouldn't close bugs too fast
reassign 434597 yaird 0.0.12-20


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



Must I use dh_installkpatches for kernel patches?

2007-07-25 Thread Goswin von Brederlow
Hi,

I'm looking at the lustre kernel patches and upstream uses quilt to
apply sets of patch files depending on the kernel version. So far the
lustre debian package uses dh_installkpatches which requires one
single patch file per kernel version.

Generating the patch file for dh_installkpatches is rather akward as
you need the linux-source-x.y.z packages for all supported kernels to
make them.


Is there some policy for kernel patches I should read up on? Must I
use dh_installkpatches for kernel patches? Or can I just write my own
apply/unpatch scripts?

MfG
Goswin


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



Bug#420448: I can't install kernel for amd64

2007-07-25 Thread Frans Pop
reassign 420448 installation-reports
thanks

 During installation, when it installs my kernel, it can not find it.
 I see the var/log and it couldn't find cdrom//pool/…/kernel-….deb.
 So, I can't finalise installation.

Could you please send us the /var/log/syslog for an installation with the 
failure? You can probably use the option Save debug logs in the main 
menu of the installer for this.

Cheers,
FJP



Processed: Bug#420448: I can't install kernel for amd64

2007-07-25 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 reassign 420448 installation-reports
Bug#420448: I can't install kernel for amd64
Bug reassigned from package `linux-image-2.6.18-4-amd64' to 
`installation-reports'.

 thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


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



Re: 2.6.22 - broken on ia64 and mipsel

2007-07-25 Thread dann frazier
On Tue, Jul 24, 2007 at 05:21:02PM +0200, Bastian Blank wrote:
 Hi folks
 
 2.6.22 is currently broken on ia64 and mipsel.
 
 - ia64: ABI.

Testing a build now.

-- 
dann frazier


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



Bug#401035: Workaround for this ST340823A drive or kernel bug?

2007-07-25 Thread Mikko Rapeli
I think bug #421870 is about the same issue too.

-Mikko 



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



Bug#401035: Workaround for this ST340823A drive or kernel bug?

2007-07-25 Thread Mikko Rapeli
Hello,

I just hit this bug too. The drive has been working without errors on 
sarge kernels for a couple of years and a badblocks read only test just 
finished without errors (non-destruct. write test ongoing, fsck's for 
the filesystems report no errors), so this is 
very likely not a defective IDE drive. Kernel 2.6.8-16sarge7
reports the drive as:

hdd: ST340823A, ATA DISK drive
ide1 at 0x170-0x177,0x376 on irq 15
hdd: max request size: 128KiB
hdd: Host Protected Area detected.
current capacity is 78165360 sectors (40020 MB)
native  capacity is 78165361 sectors (40020 MB)
hdd: 78165360 sectors (40020 MB) w/1024KiB Cache, CHS=65535/16/63, 
UDMA(33)

With 2.6.18.dfsg.1-12etch2 I get tons of similar errors early at boot 
and can't stop the screen. I think the seek fail messages are there and 
all I get to syslog on another drive is:

Jul 25 18:07:29 nalle kernel: end_request: I/O error, dev hdd, sector 0
Jul 25 18:07:29 nalle kernel: printk: 897 messages suppressed.
Jul 25 18:07:29 nalle kernel: end_request: I/O error, dev hdd, sector 1
...
Jul 25 18:07:29 nalle kernel: end_request: I/O error, dev hdd, sector 78155993
Jul 25 18:07:29 nalle kernel: end_request: I/O error, dev hdd, sector 51809625
Jul 25 18:07:29 nalle kernel: end_request: I/O error, dev hdd, sector 0
Jul 25 18:07:29 nalle kernel: end_request: I/O error, dev hdd, sector 63
Jul 25 18:07:29 nalle kernel: end_request: I/O error, dev hdd, sector 19663560
Jul 25 18:07:29 nalle kernel: end_request: I/O error, dev hdd, sector 51809625

I see this has been reported here and there ( 
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.15/+bug/26119 
), but has anyone seen even a workaround for this?

-Mikko


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



[bts-link] source package linux-2.6

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

user [EMAIL PROTECTED]

# remote status report for #420099
#  * http://bugzilla.kernel.org/show_bug.cgi?id=8246
#  * remote status changed: (?) - NEEDINFO
#  * closed upstream
tags 420099 + fixed-upstream
usertags 420099 + status-NEEDINFO

thanks



Bug#434710: Boot stopped.

2007-07-25 Thread TOGAWA Satoshi
Package: linux-image-2.6.21-2-686
Version: 2.6.21-6

I installed Debian 4.0 on my VMWare Workstation 5.5.4 build-44386.
It worked fine.
(Kernel is linux-image-2.6.18-4-686 2.6.18.dfsg.1-12etch2.)

Next I tried testing by apt-get upgrade and apt-get dist-upgrade.
Kernel package linux-image-2.6.21-2-686 2.6.21-6 was installed.
But when I reseted Virturl Machine, boot sequence stopped.
Here is a console.
=
Begin: Mounting root file system... ...
Begin: Running /scripts/local-top ...
Done.
Begin: Waiting for root file system... ...
=(stopped)

So I tried to boot on signle-user-mode.
Here is a console.
=
Begin: Mounting root file system... ...
Begin: Running /scripts/local-top ...
Done.
Begin: Waiting for root file system... ...
Done.
ALERT!  /dev/sda1 does not exist.  Dropping to a shell!
Check your root= boot argument (cat /proc/cmdline)
Check for missing modules (cat /proc/modules), or device files (ls /dev)


BusyBox v1.1.3 (Debian 1:1.1.3-4) Built-in shell (ash)
Enter 'help' for a list of built-in commands.

/bin/sh: can't access tty; job control turned off
(initramfs) 
=

Thank you.




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



Bug#434540: marked as done (MacBook makes subtle whining noise when idle since 2.6.21)

2007-07-25 Thread Debian Bug Tracking System
Your message dated Wed, 25 Jul 2007 23:58:52 -0400
with message-id [EMAIL PROTECTED]
and subject line 
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

---BeginMessage---

Package: linux-image-2.6-686
Version: 2.6.22-1

Since kernel 2.6.21, my MacBook has made a subtle whining noise when idle.
This happens when using the Debian stock kernels from testing and unstable,
but also when using other kernels.  I believe it has something to do with
certain ACPI power-saving modes and/or the switch from 250hz kernel timing
to a tickless kernel.  2.6.18 as shipped in Etch does NOT exhibit this
problem, and disabling C3/C4 ACPI C-states is a functional workaround for
2.6.21+ (though doing so results in the loss of some battery life).
However, C3/C4 ACPI C-states work fine in the aforementioned 2.6.18 kernel,
so the HZ timing seems like a more likely root cause.
---End Message---
---BeginMessage---

Upon further testing, it seems like the likely cause for this is
2.6.21+having BETTER power management support - and, thus, entering
the lower
C-states.  I did test disabling tickless operation, and it made the issue
worse.  I decided to close this because the issue also exists in Mac OS X
and the lack of a problem in 2.6.18 seems like an aberration.
---End Message---


Bug#434557: Acknowledgement (Random kernel panic on boot with MacBook)

2007-07-25 Thread Tim Hull

I applied the attached patch (from Ubuntu) to the latest 2.6.22 kernel from
Sid and it resolved the problem.  Could this be looked into?



On 7/24/07, Debian Bug Tracking System [EMAIL PROTECTED] wrote:


Thank you for the problem report you have sent regarding Debian.
This is an automatically generated reply, to let you know your message has
been received.  It is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.

Your message has been sent to the package maintainer(s):
Debian Kernel Team debian-kernel@lists.debian.org

If you wish to submit further information on your problem, please send
it to [EMAIL PROTECTED] (and *not* to
[EMAIL PROTECTED]).

If you have filed this report in error and wish to close it, please
send mail to [EMAIL PROTECTED] with an explanation
why the bug report should be closed.

Please do not reply to the address at the top of this message,
unless you wish to report a problem with the Bug-tracking system.

Debian bug tracking system administrator
(administrator, Debian Bugs database)

diff -urp a/init/calibrate.c b/init/calibrate.c
--- a/init/calibrate.c	2006-10-02 11:39:32.0 -0400
+++ b/init/calibrate.c	2007-01-27 16:39:35.0 -0500
@@ -1,5 +1,7 @@
 /* calibrate.c: default delay calibration
  *
+ * vim:sw=8 noet
+ *
  * Excised from init/main.c
  *  Copyright (C) 1991, 1992  Linus Torvalds
  */
@@ -7,9 +9,36 @@
 #include linux/sched.h
 #include linux/delay.h
 #include linux/init.h
+#include linux/dmi.h
+#include asm/io.h
 
 #include asm/timex.h
 
+/* On Macbook we have trouble calibrating the delay loop due to excessive
+ * latency in the system management interrupt.  We fix this problem by
+ * disabling the legacy USB function of the SMC during delay loop
+ * calibration.  From Intel ICH7 manual, this is bit 3 of SMI_EN register
+ * located at 0x430.
+ */
+static int __initdata macbook_calibrate_quirk;
+
+static int __init init_macbook_calibrate_quirk (struct dmi_system_id *d)
+{
+	printk(KERN_WARNING %s detected (calibration quirk enabled)\n,
+	   d-ident);
+	macbook_calibrate_quirk = 1;
+	return 0;
+}
+
+static struct dmi_system_id __initdata calibrate_quirks[] = {
+	{
+	 .callback = init_macbook_calibrate_quirk,
+	 .ident = Apple MacBook,
+	 .matches = {DMI_MATCH(DMI_PRODUCT_NAME, MacBook1,1),},
+	 },
+	{},
+};
+
 static unsigned long preset_lpj;
 static int __init lpj_setup(char *str)
 {
@@ -37,8 +66,16 @@ static unsigned long __devinit calibrate
 	unsigned long tsc_rate_min, tsc_rate_max;
 	unsigned long good_tsc_sum = 0;
 	unsigned long good_tsc_count = 0;
+	unsigned long saved_smi_en = 0;
 	int i;
 
+	if (macbook_calibrate_quirk)
+	{
+		saved_smi_en = inl(0x430);
+		/* mask out bit 3 */
+		outl(saved_smi_en  ~8, 0x430);
+	}
+
 	if (read_current_timer(pre_start)  0 )
 		return 0;
 
@@ -94,6 +131,9 @@ static unsigned long __devinit calibrate
 		}
 	}
 
+	if (macbook_calibrate_quirk)
+		outl(saved_smi_en, 0x430);
+
 	if (good_tsc_count)
 		return (good_tsc_sum/good_tsc_count);
 
@@ -117,6 +157,8 @@ void __devinit calibrate_delay(void)
 	unsigned long ticks, loopbit;
 	int lps_precision = LPS_PREC;
 
+	dmi_check_system(calibrate_quirks);
+
 	if (preset_lpj) {
 		loops_per_jiffy = preset_lpj;
 		printk(Calibrating delay loop (skipped)... 


Bug#401035: More information (Re: Workaround for this ST340823A drive or kernel bug? )

2007-07-25 Thread Mikko Rapeli
hdd with 2.6.8-16sarge7:

---

hdd: ST340823A, ATA DISK drive
ide1 at 0x170-0x177,0x376 on irq 15
hdd: max request size: 128KiB
hdd: Host Protected Area detected.
current capacity is 78165360 sectors (40020 MB)
native  capacity is 78165361 sectors (40020 MB)
hdd: 78165360 sectors (40020 MB) w/1024KiB Cache, CHS=65535/16/63, UDMA(33)
 /dev/ide/host0/bus1/target1/lun0: p1 p2 p3



Badblocks read-only and non-destructive write return no error, filesystems are
fsck clean:

-
# /etc/init.d/lvm start
Setting up LVM Volume Groups...
  Reading all physical volumes.  This may take a while...
  Found volume group spare using metadata type lvm2
  2 logical volume(s) in volume group spare now active
# fsck.ext3 -f /dev/mapper/spare-home
e2fsck 1.40-WIP (14-Nov-2006)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/mapper/spare-home: 68784/524288 files (1.8% non-contiguous), 
767457/1048576 blocks
# fsck.ext3 -f /dev/mapper/spare-media
e2fsck 1.40-WIP (14-Nov-2006)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/mapper/spare-media: 31748/3538944 files (2.0% non-contiguous), 
6045677/7077888 blocks
-

Contains three partitions used by lvm:

--
  2264   39082680 hdd
  22659831748 hdd1
  2266   16073032 hdd2
  2267   13173300 hdd3
 254 0   28311552 dm-0
 254 14194304 dm-1

# pvdisplay
  --- Physical volume ---
  PV Name   /dev/hdd1
  VG Name   spare
  PV Size   9.38 GB / not usable 0
  Allocatable   yes (but full)
  PE Size (KByte)   4096
  Total PE  2400
  Free PE   0
  Allocated PE  2400
  PV UUID   YwheMf-s0pv-97XS-sAOB-oGSk-WcHA-ZEo8Ag

  --- Physical volume ---
  PV Name   /dev/hdd3
  VG Name   spare
  PV Size   12.56 GB / not usable 0
  Allocatable   yes (but full)
  PE Size (KByte)   4096
  Total PE  3216
  Free PE   0
  Allocated PE  3216
  PV UUID   b9Xviu-XSOP-9lz4-4gcY-tE9W-fqxA-k2amBh

  --- Physical volume ---
  PV Name   /dev/hdd2
  VG Name   spare
  PV Size   15.32 GB / not usable 0
  Allocatable   yes
  PE Size (KByte)   4096
  Total PE  3923
  Free PE   1603
  Allocated PE  2320
  PV UUID   TEN6QM-MVlA-LDlO-Moiu-O7mU-VTfZ-pinLz6


With 2.6.18.dfsg.1-12etch2 and 2.6.22-2snapshot.9178 on etch kernel 
complains a lot about read errors and lvm code fails to scan the drive 
for physical volumes after that. I suppose initial ide drive scan fails 
and the drive is disabled since. Boot time logs go past so fast, that I can't 
catch them. 'hdd=noprobe hdd=65535,16,63' boot options don't help.

--
# hdparm -i /dev/hdd

/dev/hdd:

 Model=ST340823A, FwRev=3.07, SerialNo=7EF1EYYG
 Config={ HardSect NotMFM HdSw15uSec Fixed DTR10Mbs RotSpdTol.5% }
 RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=0
 BuffType=unknown, BuffSize=1024kB, MaxMultSect=16, MultSect=off
 CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=78165360
 IORDY=on/off, tPIO={min:240,w/IORDY:120}, tDMA={min:120,rec:120}
 PIO modes:  pio0 pio1 pio2 pio3 pio4
 DMA modes:  mdma0 mdma1 mdma2
 UDMA modes: udma0 udma1 *udma2 udma3 udma4 udma5 udma3 udma4 udma5
 AdvancedPM=no WriteCache=enabled
 Drive conforms to: Unspecified:  ATA/ATAPI-1 ATA/ATAPI-2 ATA/ATAPI-3 
ATA/ATAPI-4

 * signifies the current active mode
-

All operations like fdisk fail after boot like this:

-
end_request: I/O error, dev hdd, sector 0
printk: 33 messages suppressed.
Buffer I/O error on device hdd, logical block 0
end_request: I/O error, dev hdd, sector 1
Buffer I/O error on device hdd, logical block 1
end_request: I/O error, dev hdd, sector 2
Buffer I/O error on device hdd, logical block 2
end_request: I/O error, dev hdd, sector 3
Buffer I/O error on device hdd, logical block 3
end_request: I/O error, dev hdd, sector 4
Buffer I/O error on device hdd, logical block 4
end_request: I/O error, dev hdd, sector 5
Buffer I/O error on device hdd, logical block 5
end_request: I/O error, dev hdd, sector 6
Buffer I/O error on device hdd, logical block 6
end_request: I/O error, dev hdd, sector 7
Buffer I/O error on device hdd, logical block 7
end_request: I/O error, dev hdd, sector 8
Buffer I/O error on device hdd, logical block 8
end_request: I/O error, dev hdd, sector 9
Buffer I/O error on device hdd, logical block 9
end_request: I/O error, dev hdd, sector 10
end_request: I/O error, dev hdd, sector 11
end_request: I/O error, dev hdd, sector 12
end_request: I/O error, dev 

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

2007-07-25 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 #
 # bts-link upstream status pull for source package linux-2.6
 # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
 #
 user [EMAIL PROTECTED]
Setting user to [EMAIL PROTECTED] (was [EMAIL PROTECTED]).
 # remote status report for #420099
 #  * http://bugzilla.kernel.org/show_bug.cgi?id=8246
 #  * remote status changed: (?) - NEEDINFO
 #  * closed upstream
 tags 420099 + fixed-upstream
Bug#420099: Extremely slow ACPI on Thinkpad R51e
Tags were: upstream
Tags added: fixed-upstream

 usertags 420099 + status-NEEDINFO
Bug#420099: Extremely slow ACPI on Thinkpad R51e
There were no usertags set.
Usertags are now: status-NEEDINFO.
 thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


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



Processed: Re: Bug#434138: try bootdelay.

2007-07-25 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 reassign 434138 initramfs-tools
Bug#434138: mdadm fails to assemble arrays on system boot
Bug reassigned from package `mdadm' to `initramfs-tools'.

 forcemerge 433905 434138
Bug#433905: initramfs-tools: Boot failure from software-RAID1 with debian on 
nslu2
Bug#434138: mdadm fails to assemble arrays on system boot
Forcibly Merged 433905 434138.

 thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


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



Bug#431563: small update

2007-07-25 Thread Christian Ohm
Just to let you know, with the current 2.6.22 package this problem does
not appear.


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



Processed: Re: Bug#433768: FTBFS[hppa]: QMAKESPEC has not been set, so configuration cannot be deduced.

2007-07-25 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 reassign #433768 linux-2.6
Bug#433768: FTBFS[hppa]: QMAKESPEC has not been set, so configuration cannot be 
deduced.
Bug#431773: libqt4-dev: Missing mkspec files on hppa
Bug reassigned from package `libqt4-dev' to `linux-2.6'.

 retitle #433768 getdent(3) broken on hppa
Bug#433768: FTBFS[hppa]: QMAKESPEC has not been set, so configuration cannot be 
deduced.
Changed Bug title to `getdent(3) broken on hppa' from `FTBFS[hppa]: QMAKESPEC 
has not been set, so configuration cannot be deduced.'.

 tag #433768 + patch
Bug#433768: getdent(3) broken on hppa
There were no tags set.
Bug#431773: libqt4-dev: Missing mkspec files on hppa
Tags added: patch

 thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


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



Processed: closing 431563

2007-07-25 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 # Automatically generated email from bts, devscripts version 2.9.26
 close 431563 2.6.22-1
Bug#431563: linux-image-2.6.21-2-amd64: Hangs on X startup
'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing.
Bug marked as fixed in version 2.6.22-1, send any further explanations to 
[EMAIL PROTECTED]


End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


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



Processed: PS/2 mouse not detected in VPC2007, affects Linux 2.6.22

2007-07-25 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 reassign 433815 linux-2.6
Bug#433815: PS/2 mouse not detected on MS Virtual PC 2007
Bug reassigned from package `linux-image-2.6.21-2-686' to `linux-2.6'.

 found 433815 2.6.22-2
Bug#433815: PS/2 mouse not detected on MS Virtual PC 2007
Bug marked as found in version 2.6.22-2.

 thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


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