Bug#426714: intelfb refuses mode switching

2008-12-29 Thread Olaf Zaplinski

Hello Moritz,

I tried 2.6.24 and 2.6.26-bpo on both machines. On both machines intelfb 
now refuses to load with the message cannot acquire agp.


/etc/initramfs-tools/modules contains:

agp
intel_agp
intelfb mode=1024x768...@60

I added the agp module, but I do not know exactly if I need that.

Olaf



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



Bug#510108: linux-image-2.6.26-1-powerpc: suspend no longer works (when lid closed) - freeze

2008-12-29 Thread Vincent Lefevre
Package: linux-image-2.6.26-1-powerpc
Version: 2.6.26-12
Severity: important

When I close the lid of my PowerBook G4, the disk spins down, but the
machine is still on (I can see the light from the Apple logo). When I
reopen the lid, the following messages are displayed:

Freezing user space processes ... (elapsed 0.00 seconds) done.
Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done.
Suspending console(s)

The machine is frozen; I can only switch it off with the power button.
This problem is reproducible (I tried twice, see below).

What's strange is that I closed the lid every night the few days before,
and I didn't have any problem. Here's log information:

lefevre  tty1  Mon Dec 29 11:52   still logged in   
lefevre  tty1  Mon Dec 29 11:52 - 11:52  (00:00)
reboot   system boot  2.6.26-1-powerpc Mon Dec 29 11:46 - 12:16  (00:29)
reboot   system boot  2.6.26-1-powerpc Mon Dec 29 11:38 - 12:16  (00:37)
lefevre  tty1  Mon Dec 29 04:03 - crash  (07:35)
lefevre  tty1  Mon Dec 29 04:03 - 04:03  (00:00)
lefevre  pts/7localhostFri Dec 26 16:24 - 16:26  (00:02)
lefevre  pts/3vinc17.pck.nerim Wed Dec 24 21:53 - 21:53  (00:00)
lefevre  tty1  Mon Dec 22 12:39 - 04:03 (6+15:23)   
lefevre  tty1  Mon Dec 22 12:39 - 12:39  (00:00)
reboot   system boot  2.6.26-1-powerpc Mon Dec 22 12:38 - 12:16 (6+23:37)   

The reboots at Dec 22 12:38 and Dec 29 11:38 are those which
ended by a crash when I closed the lid earlier today.

Here are the latest system upgrades. Can anyone of them could have
an influence? (Perhaps initramfs-tools?)

2008-12-28 20:56:36 startup archives unpack
2008-12-28 20:57:41 install libunique-1.0-0 none 1.0.4-1
2008-12-28 20:57:41 status half-installed libunique-1.0-0 1.0.4-1
2008-12-28 20:57:51 status unpacked libunique-1.0-0 1.0.4-1
2008-12-28 20:58:09 status unpacked libunique-1.0-0 1.0.4-1
2008-12-28 20:58:10 install libwebkit-1.0-1 none 1.0.1-4
2008-12-28 20:58:10 status half-installed libwebkit-1.0-1 1.0.1-4
2008-12-28 20:58:40 status unpacked libwebkit-1.0-1 1.0.1-4
2008-12-28 20:58:40 status unpacked libwebkit-1.0-1 1.0.1-4
2008-12-28 20:58:41 install midori none 0.1.1-1
2008-12-28 20:58:41 status half-installed midori 0.1.1-1
2008-12-28 20:58:41 status triggers-pending man-db 2.5.2-3
2008-12-28 20:58:42 status half-installed midori 0.1.1-1
2008-12-28 20:58:42 status triggers-pending menu 2.1.41
2008-12-28 20:58:42 status half-installed midori 0.1.1-1
2008-12-28 20:58:46 status unpacked midori 0.1.1-1
2008-12-28 20:58:47 status unpacked midori 0.1.1-1
2008-12-28 20:58:47 trigproc man-db 2.5.2-3 2.5.2-3
2008-12-28 20:58:47 status half-configured man-db 2.5.2-3
2008-12-28 20:59:05 status installed man-db 2.5.2-3
2008-12-28 20:59:05 trigproc menu 2.1.41 2.1.41
2008-12-28 20:59:05 status half-configured menu 2.1.41
2008-12-28 21:00:12 status installed menu 2.1.41
2008-12-28 21:00:21 startup packages configure
2008-12-28 21:00:21 configure libunique-1.0-0 1.0.4-1 1.0.4-1
2008-12-28 21:00:22 status unpacked libunique-1.0-0 1.0.4-1
2008-12-28 21:00:22 status half-configured libunique-1.0-0 1.0.4-1
2008-12-28 21:00:26 status installed libunique-1.0-0 1.0.4-1
2008-12-28 21:00:26 configure libwebkit-1.0-1 1.0.1-4 1.0.1-4
2008-12-28 21:00:26 status unpacked libwebkit-1.0-1 1.0.1-4
2008-12-28 21:00:26 status half-configured libwebkit-1.0-1 1.0.1-4
2008-12-28 21:00:26 status installed libwebkit-1.0-1 1.0.1-4
2008-12-28 21:00:26 configure midori 0.1.1-1 0.1.1-1
2008-12-28 21:00:26 status unpacked midori 0.1.1-1
2008-12-28 21:00:26 status half-configured midori 0.1.1-1
2008-12-28 21:00:29 status installed midori 0.1.1-1
2008-12-28 21:00:29 status triggers-pending menu 2.1.41
2008-12-28 21:00:29 status triggers-awaited menu 2.1.41
2008-12-28 21:00:29 trigproc menu 2.1.41 2.1.41
2008-12-28 21:00:29 status half-configured menu 2.1.41
2008-12-28 21:00:49 status installed menu 2.1.41
2008-12-28 21:10:01 startup archives unpack
2008-12-28 21:10:40 upgrade reportbug 3.47 3.48
2008-12-28 21:10:40 status half-configured reportbug 3.47
2008-12-28 21:10:43 status unpacked reportbug 3.47
2008-12-28 21:10:43 status half-installed reportbug 3.47
2008-12-28 21:10:46 status triggers-pending menu 2.1.41
2008-12-28 21:10:47 status half-installed reportbug 3.47
2008-12-28 21:10:47 status triggers-pending man-db 2.5.2-3
2008-12-28 21:10:47 status half-installed reportbug 3.47
2008-12-28 21:10:48 status half-installed reportbug 3.47
2008-12-28 21:10:48 status triggers-awaited menu 2.1.41
2008-12-28 21:10:48 status unpacked reportbug 3.48
2008-12-28 21:10:49 status unpacked reportbug 3.48
2008-12-28 21:10:49 upgrade initramfs-tools 0.92m 0.92n
2008-12-28 21:10:49 status half-configured initramfs-tools 0.92m
2008-12-28 21:10:49 status unpacked initramfs-tools 0.92m
2008-12-28 21:10:49 status half-installed 

Bug#426264: marked as done (linux-image-2.6.18-4-686-bigmem: Kernel BUG: Unbalanced enable for IRQ nnn)

2008-12-29 Thread Debian Bug Tracking System

Your message dated Mon, 29 Dec 2008 14:00:21 +0100
with message-id 20081229130021.ga3...@galadriel.inutil.org
and subject line Re: linux-image-2.6.18-4-686-bigmem: Kernel BUG: Unbalanced 
enable for IRQ nnn
has caused the Debian Bug report #426264,
regarding linux-image-2.6.18-4-686-bigmem: Kernel BUG: Unbalanced enable for 
IRQ nnn
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.)


-- 
426264: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=426264
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---

Package: linux-image-2.6.18-4-686-bigmem
Version: 2.6.18.dfsg.1-12
Severity: normal

*** Please type your report below this line ***
Hi,

during the boot process sometimes the kernel reports the following message:

hde: HL-DT-ST DVDRAM GSA-H10N, ATAPI CD/DVD-ROM drive
Unbalanced enable for IRQ 177
BUG: warning at kernel/irq/manage.c:118/enable_irq()
 [c013e6b1] enable_irq+0x54/0x87
 [f88638ae] probe_hwif+0x556/0x627 [ide_core]
 [c0210dfc] __driver_attach+0x0/0x5d
 [f8864195] probe_hwif_init_with_fixup+0xb/0x63 [ide_core]
 [f8865f61] ide_setup_pci_device+0x3c/0x6d [ide_core]
 [f8bc911e] generic_init_one+0x92/0xa0 [generic]
 [c01c121c] pci_device_probe+0x36/0x57
 [c0210d5d] driver_probe_device+0x42/0x8b
 [c0210e34] __driver_attach+0x38/0x5d
 [c021087e] bus_for_each_dev+0x33/0x55
 [c0210cc7] driver_attach+0x11/0x13
 [c0210dfc] __driver_attach+0x0/0x5d
 [c0210597] bus_add_driver+0x64/0xfd
 [c01c1358] __pci_register_driver+0x47/0x63
 [c0135fa5] sys_init_module+0x16c3/0x1846
 [c0160e08] cp_new_stat64+0xfd/0x10f
 [c0102c77] syscall_call+0x7/0xb
ide2 at 0xbc00-0xbc07,0xb882 on irq 177

The problem does not occur at every boot and the system seems working well even 
after
reporting this warning.

I've an ASUS P5B motherboard with a JMicron 363 IDE controller.

Should you need further information about my hardware, please do not hesitate to
contact me.

Kind Regards,

Pietro Pizzo

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

Kernel: Linux 2.6.18-4-686-bigmem (SMP w/2 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 linux-image-2.6.18-4-686-bigmem depends on:
ii  coreutils 5.97-5.3   The GNU core utilities
ii  debconf [debconf-2.0] 1.5.13 Debian configuration management sy
ii  initramfs-tools [linux-initra 0.87b  tools for generating an initramfs
ii  module-init-tools 3.3-pre4-2 tools for managing Linux kernel mo

Versions of packages linux-image-2.6.18-4-686-bigmem recommends:
ii  libc6-i686  2.3.6.ds1-13 GNU C Library: Shared libraries [i

-- debconf information:
  
linux-image-2.6.18-4-686-bigmem/postinst/depmod-error-initrd-2.6.18-4-686-bigmem:
 false
  shared/kernel-image/really-run-bootloader: true
  
linux-image-2.6.18-4-686-bigmem/postinst/bootloader-test-error-2.6.18-4-686-bigmem:
  linux-image-2.6.18-4-686-bigmem/preinst/abort-overwrite-2.6.18-4-686-bigmem:
  
linux-image-2.6.18-4-686-bigmem/preinst/bootloader-initrd-2.6.18-4-686-bigmem: 
true
  linux-image-2.6.18-4-686-bigmem/postinst/depmod-error-2.6.18-4-686-bigmem: 
false
  linux-image-2.6.18-4-686-bigmem/preinst/lilo-has-ramdisk:
  linux-image-2.6.18-4-686-bigmem/postinst/bootloader-error-2.6.18-4-686-bigmem:
  
linux-image-2.6.18-4-686-bigmem/postinst/create-kimage-link-2.6.18-4-686-bigmem:
 true
  
linux-image-2.6.18-4-686-bigmem/prerm/would-invalidate-boot-loader-2.6.18-4-686-bigmem:
 true
  
linux-image-2.6.18-4-686-bigmem/preinst/overwriting-modules-2.6.18-4-686-bigmem:
 true
  
linux-image-2.6.18-4-686-bigmem/postinst/old-system-map-link-2.6.18-4-686-bigmem:
 true
  linux-image-2.6.18-4-686-bigmem/preinst/initrd-2.6.18-4-686-bigmem:
  linux-image-2.6.18-4-686-bigmem/postinst/old-initrd-link-2.6.18-4-686-bigmem: 
true
  linux-image-2.6.18-4-686-bigmem/postinst/kimage-is-a-directory:
  linux-image-2.6.18-4-686-bigmem/preinst/abort-install-2.6.18-4-686-bigmem:
  
linux-image-2.6.18-4-686-bigmem/prerm/removing-running-kernel-2.6.18-4-686-bigmem:
 true
  
linux-image-2.6.18-4-686-bigmem/preinst/failed-to-move-modules-2.6.18-4-686-bigmem:
  
linux-image-2.6.18-4-686-bigmem/postinst/old-dir-initrd-link-2.6.18-4-686-bigmem:
 true
  
linux-image-2.6.18-4-686-bigmem/preinst/already-running-this-2.6.18-4-686-bigmem:
  linux-image-2.6.18-4-686-bigmem/preinst/lilo-initrd-2.6.18-4-686-bigmem: true
  linux-image-2.6.18-4-686-bigmem/preinst/elilo-initrd-2.6.18-4-686-bigmem: true

---End Message---
---BeginMessage---
Version: 

Bug#459215: marked as done (lspci command produces error: sysfs_scan: Couldn't parse entry name)

2008-12-29 Thread Debian Bug Tracking System

Your message dated Mon, 29 Dec 2008 14:25:27 +0100
with message-id 20081229132526.ga4...@galadriel.inutil.org
and subject line Re: lspci command produces error: sysfs_scan: Couldn't parse 
entry name
has caused the Debian Bug report #459215,
regarding lspci command produces error: sysfs_scan: Couldn't parse entry name
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.)


-- 
459215: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=459215
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---

Package: linux-image-2.6.18-5-amd64
Version: 2.6.18.dfsg.1-17

I noticed after upgrading my kernel to the latest 
linux-image-2.6.18-5-amd64 I could not longer run the lspci command and 
it would give me the above error.  I rebooted back into 
linux-image-2.6.18-4-amd64 and it started working fine again.  Here is 
the lspci output of my machine after I reverted back in case it helps:


00:00.0 Memory controller: nVidia Corporation CK804 Memory Controller 
(rev a3)

00:01.0 ISA bridge: nVidia Corporation CK804 ISA Bridge (rev f3)
00:01.1 SMBus: nVidia Corporation CK804 SMBus (rev a2)
00:02.0 USB Controller: nVidia Corporation CK804 USB Controller (rev a2)
00:02.1 USB Controller: nVidia Corporation CK804 USB Controller (rev a3)
00:06.0 IDE interface: nVidia Corporation CK804 IDE (rev f2)
00:09.0 PCI bridge: nVidia Corporation CK804 PCI Bridge (rev f2)
00:0b.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev f3)
00:0c.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev f3)
00:0d.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev f3)
00:0e.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a3)
00:10.0 PCI bridge: Advanced Micro Devices [AMD] AMD-8132 PCI-X Bridge 
(rev 12)

00:10.1 PIC: Advanced Micro Devices [AMD] AMD-8132 PCI-X IOAPIC (rev 12)
00:11.0 PCI bridge: Advanced Micro Devices [AMD] AMD-8132 PCI-X Bridge 
(rev 12)

00:11.1 PIC: Advanced Micro Devices [AMD] AMD-8132 PCI-X IOAPIC (rev 12)
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] 
HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] 
Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] 
DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] 
Miscellaneous Control
00:19.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] 
HyperTransport Technology Configuration
00:19.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] 
Address Map
00:19.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] 
DRAM Controller
00:19.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] 
Miscellaneous Control
00:1a.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] 
HyperTransport Technology Configuration
00:1a.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] 
Address Map
00:1a.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] 
DRAM Controller
00:1a.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] 
Miscellaneous Control
00:1b.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] 
HyperTransport Technology Configuration
00:1b.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] 
Address Map
00:1b.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] 
DRAM Controller
00:1b.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] 
Miscellaneous Control
00:1c.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] 
HyperTransport Technology Configuration
00:1c.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] 
Address Map
00:1c.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] 
DRAM Controller
00:1c.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] 
Miscellaneous Control
00:1d.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] 
HyperTransport Technology Configuration
00:1d.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] 
Address Map
00:1d.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] 
DRAM Controller
00:1d.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] 
Miscellaneous Control
00:1e.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] 
HyperTransport Technology Configuration
00:1e.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] 
Address Map
00:1e.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] 
DRAM Controller
00:1e.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] 

Bug#501742: linux-image-2.6.26-1-amd64: Random hangs/slowness and forcedeth problem

2008-12-29 Thread Moritz Muehlenhoff
On Fri, Oct 10, 2008 at 01:26:44AM +0200, Per Foreby wrote:
 Package: linux-image-2.6.26-1-amd64
 Version: 2.6.26-5
 Severity: important
 
 On versions before 2.6.26 i have been getting lots of messages like
 this:
 
   eth0: too many iterations (6) in nv_nic_irq
 
 Apart from filling up the log, the has been no noticable impact on the
 system.
 
 After upgrading to 2.6.26, the system started to misbehave. It would
 work for  a few hours, and then it would slow down to the degree where a
 simple command could take several minutes to complete.  Finally, it
 would become totally unresponsive leaving the reset button as the only
 option.

[..]

 This is a production server/firewall, and I wasn't able to take any more
 downtime, so when hpet=disable didn't work, I reverted to a previous
 kernel (2.6.24-7). Apart from the normal error messages (too many
 iterations...) the system has been stable for three days now. 

This has been fixed in commit
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=dccd547e2bf2c01a13c967ae03a705338394fad6

Could you apply that patch on top of the current kernel source package
and test, whether it fixes the problem for you? If so, it could be
integrated into a kernel update for a point release.

Cheers,
Moritz



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



Bug#479101: Bug#479607: With lilo 22.8-5 still can't boot on macbookpro

2008-12-29 Thread Moritz Muehlenhoff
On Mon, Jul 14, 2008 at 11:00:00PM +0200, Eugen Dedu wrote:
 reopen 479607
 thanks

 annonygmouse wrote:

 Hi folks I've seen bug 479607 has been closed with lilo version 22.8-5  
 but I still can't boot my machine with 2.6.25-2...


 debianmbp:~# LANG=C aptitude show lilo
 Package: lilo
 State: installed
 Automatically installed: no
 Version: 1:22.8-5
 Priority: optional
 Section: admin
 Maintainer: William Pitcock neno...@sacredspiral.co.uk
 Uncompressed Size: 1208k
 Depends: mbr, debconf (= 1.2.9) | debconf-2.0, libc6 (= 2.7-1),  
 libdevmapper1.02.1 (= 2:1.02.20)
 Suggests: lilo-doc
 Conflicts: manpages ( 1.29-3)
 Description: LInux LOader - The Classic OS loader can load Linux and others
  This package contains lilo (the installer) and boot-record-images to  
 install Linux, OS/2, DOS and generic Boot Sectors of other OSes.

  You can use LILO to manage your Master Boot Record (with a simple text 
 screen, text menu or colorful splash graphics) or call LILO from
  other Boot-Loaders to jump-start the Linux kernel.

 Tags: admin::boot, interface::commandline, role::program, scope::utility

 debianmbp:~#

 Running lilo shows the following.

 debianmbp:~# lilo
 Warning: LBA32 addressing assumed
 Added Linux *
 Added LinuxOLD
 One warning was issued.
 debianmbp:~#


 Is this the warning saying that de 8MB barrier has been met? Because I  
 think this warning happened before...

 Hi,

 It seems to me that lilo does not show any warning for the image which  
 does not work on my machine.  In fact, as previously said, the image has  
 less than 8MB:

 -rw-r--r-- 1 root root 6998498 2008-05-16 10:11 initrd.img-2.6.25-2-amd64

 I put a few days ago this image as the default one and run lilo: no  
 warning was issued about the size, still rebooting the computer does not  
 work.

 So I reopen this bug.

Lilo was fixed in version 1:22.8-6.4 onwards. Can you confirm that it resolves
the problem for you?

Cheers,
Moritz







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



Bug#499752: linux-image-2.6.26-1-686: Seagate STT20000A no longer works in 2.6.26

2008-12-29 Thread Moritz Muehlenhoff
On Sun, Sep 21, 2008 at 11:42:09PM +0200, Mark de Wever wrote:
 Package: linux-image-2.6.26-1-686
 Version: 2.6.26-4
 Severity: important
 Tags: upstream
 
 
 Hi,
 
 After updating my system from kernel version 2.6.24 to 2.6.26 I ran into
 some problems due to my Seagate STT2A tapestreamer. Those problems
 also occur in the vanilla kernel and have been reported upstream on the
 lkml.
 
 1) The system no longer boots. HEAD upstream does boot, but the
 tapestreamer still doesn't work.
 http://marc.info/?l=linux-kernelm=122203193728465w=2

Which upstream version did you test that worked?

What module is used by the streamer?

Cheers,
Moritz



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



Bug#390724: Ooops on Xen reboot

2008-12-29 Thread Moritz Muehlenhoff
On Mon, Oct 02, 2006 at 08:07:34PM +0200, Andreas Barth wrote:
 Package: linux-image-2.6.18-1-xen-amd64
 Version: 2.6.18-2
 
 Hi,
 
 on rebooting my Xen dom0, I got this error message.

Does this error occur reproducibly with current Etch Xen kernels?

Cheers,
Moritz



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



Bug#396133: Kernel panics if higher than v2.6.15-1

2008-12-29 Thread Moritz Muehlenhoff
On Sun, Oct 29, 2006 at 07:30:11PM -0500, Draco Ravenloft wrote:
 Package: linux-image
   Version: any *after* 2.6.15-1
 
 error recieved when booting post 2.6.15 kernel:
  Begin: Running /scripts/local-premount ...
  Attempting manual resume
  attempt to access beyond end of device
  hda2: rw=16, want=8, limit=2
  Kernel panic - not syncing: I/O error reading memory image
 
 This is during boot.  The exact config in question breaks down thus:
 PCI IDE card with HDD containing debian
 same card with other ide port containing a DVD±RW
 ASUS P5A mainboard's onboard IDE containing a 2nd harddrive and a DVD-ROM 
 Mainboard and GRUB actually are seeing the onboard IDE as 1st.
 
 If I use a post 2.6.15 kernel in any arrangement except the windows drive 
 unplugged completely then the above error happens.  newer kernel versions 
 have seemed to add a little... namely /dev/hda2 instead of simply hda2 and 
 also it refers to hda2 as hda2(3,2) if it's 2.6.18.
 
 This does not happen with the prepackaged kernels of other distros.  This 
 does 
 not happen with precompiled kernels unless I forget to select boot offboard 
 IDE first.  
 
 I have actually tried reformatting and doing a brand new install.  The 
 install 
 disc kernel sets the PCI IDE as IDE0.  And then immediately upon booting into 
 the clean install I see the kernel panic.

Does this error still occur with more recent kernel versions?

Cheers,
Moritz



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



Bug#500265: Info received (Bug#500265: linux-image-2.6.26-1-686: Hangs after an apparently random uptime (minutes))

2008-12-29 Thread Salvo Isaja
I confirm that this kernel has serious problems, even with 
hpet=disable. This time it crashed after a few hours of uptime, no 
more mouse and keyboard input, I've heard the hard disk park itself 
and CD-ROM disc activity stopped too. Syslog, dmesg and debug contain 
no useful information.

Please definitely DO NOT include this kernel in a Debian stable. I 
hope I'm wrong, but I feel like this problem is underrated.



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



Bug#401439: hppa/xfs

2008-12-29 Thread Helge Deller
I've just sent two patches which do solve this problem for review to Linux 
kernel mailing list.

Description of the problem:
http://marc.info/?l=linux-kernelm=123055968113465w=2

Two patches:
http://marc.info/?l=linux-kernelm=123055978413612w=2
http://marc.info/?l=linux-kernelm=123055986413742w=2




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



Bug#396133: marked as done (Kernel panics if higher than v2.6.15-1)

2008-12-29 Thread Debian Bug Tracking System

Your message dated Mon, 29 Dec 2008 17:41:19 +0100
with message-id 20081229164118.ga3...@galadriel.inutil.org
and subject line Re: Kernel panics if higher than v2.6.15-1
has caused the Debian Bug report #396133,
regarding Kernel panics if higher than v2.6.15-1
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.)


-- 
396133: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=396133
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-image
  Version: any *after* 2.6.15-1

error recieved when booting post 2.6.15 kernel:
 Begin: Running /scripts/local-premount ...
 Attempting manual resume
 attempt to access beyond end of device
 hda2: rw=16, want=8, limit=2
 Kernel panic - not syncing: I/O error reading memory image

This is during boot.  The exact config in question breaks down thus:
PCI IDE card with HDD containing debian
same card with other ide port containing a DVD±RW
ASUS P5A mainboard's onboard IDE containing a 2nd harddrive and a DVD-ROM 
Mainboard and GRUB actually are seeing the onboard IDE as 1st.

If I use a post 2.6.15 kernel in any arrangement except the windows drive 
unplugged completely then the above error happens.  newer kernel versions 
have seemed to add a little... namely /dev/hda2 instead of simply hda2 and 
also it refers to hda2 as hda2(3,2) if it's 2.6.18.

This does not happen with the prepackaged kernels of other distros.  This does 
not happen with precompiled kernels unless I forget to select boot offboard 
IDE first.  

I have actually tried reformatting and doing a brand new install.  The install 
disc kernel sets the PCI IDE as IDE0.  And then immediately upon booting into 
the clean install I see the kernel panic.


---End Message---
---BeginMessage---
On Mon, Dec 29, 2008 at 11:05:03AM -0500, Draco Ravenloft wrote:
 No.  I have the latest kernel that goes with Lenny.
 The issue...  stopped being. Or I fixed it by accident.  Either way it's
 gone as mysteriously as it came.

Thanks, closing the bug then.

Cheers,
Moritz

---End Message---


redhat-cluster 2.20081102-1 MIGRATED to testing

2008-12-29 Thread Debian testing watch
FYI: The status of the redhat-cluster source package
in Debian's testing distribution has changed.

  Previous version: 2.20080801-4+lenny1
  Current version:  2.20081102-1

-- 
This email is automatically generated; the Debian Release Team
debian-rele...@lists.debian.org is responsible.
See http://release.debian.org/testing-watch/ for more information.


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



Bug#501742: linux-image-2.6.26-1-amd64: Random hangs/slowness and forcedeth problem

2008-12-29 Thread Moritz Muehlenhoff
Per Foreby wrote:
 Sorry, but I gave up and replaced the MB, so the test platform is no
 longer available. The new hardware with a realtek nic is running the
 latest 2.6.26 without any problems.

Ok, I'm leaving the bug open, in case someone else owns the hardware.

Cheers,
   Moritz



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



Bug#413392: X session is blocked sometimes when resuming from screen saver.

2008-12-29 Thread Teodor
Hi Moritz,

On Sun, Dec 28, 2008 at 3:32 AM, Moritz Muehlenhoff j...@inutil.org wrote:
 Teodor wrote:
  However, with the latest kernel (now in testing too) v2.6.26-10 I'm
  getting from time to time a X/kernel freeze when I'm trying to return
  to my X/gnome session from screen saver (random selected). Only my
  work station is affected (i386) and it didn't happen with any of the
  previous versions, so it seems like a regression introduced in the
  last build (-10).
 
  Does this system run an Intel graphics adapter?

 Yes, it does. Is this a known bug?

 Does the 2.6.26-11 (or the current -12 image) fix the problem for you?

I've just get the same X11 session freeze, but I've discovered that
the host is not in freeze. I've connected from my laptop and just
killed the screen saver child process and this way I could re-login
and continue the current work.

I have the Screensaver theme set to Random so in this particular
case the blocking saver program is called rubik:
  doru  6311  0.2  0.2  18300  5536 ?Ss   16:21   0:36
gnome-screensaver
  doru 29077 65.3  0.2  24372  4736 ?RN   19:42   4:38  \_
rubik -root

I think this bug report should be closed and/or reassigned to
'xscreensaver-gl-extra'. Shall I do that?

Thanks



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



Bug#454640: marked as done (Brasero doesn't see blank discs)

2008-12-29 Thread Debian Bug Tracking System

Your message dated Mon, 29 Dec 2008 20:16:44 +0100
with message-id 20081229191644.ga3...@galadriel.inutil.org
and subject line Re: Brasero doesn't see blank discs
has caused the Debian Bug report #454640,
regarding Brasero doesn't see blank discs
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.)


-- 
454640: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=454640
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: brasero
Version: 0.6.1-1
Severity: grave

I tried 3 different blank disc. Brasero didn't see any of them.

-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.22-3-amd64 (SMP w/2 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 brasero depends on:
ii  gconf2  2.20.1-1 GNOME configuration database syste
ii  genisoimage 9:1.1.6-1Creates ISO-9660 CD-ROM filesystem
ii  libart-2.0-22.3.19-3 Library of functions for 2D graphi
ii  libatk1.0-0 1.20.0-1 The ATK accessibility toolkit
ii  libbonobo2-02.20.1-1 Bonobo CORBA interfaces library
ii  libbonoboui2-0  2.20.0-1 The Bonobo UI library
ii  libc6   2.7-3GNU C Library: Shared libraries
ii  libcairo2   1.4.10-1+b2  The Cairo 2D vector graphics libra
ii  libdbus-1-3 1.1.1-3  simple interprocess messaging syst
ii  libdbus-glib-1-20.74-1   simple interprocess messaging syst
ii  libfontconfig1  2.4.2-1.2generic font configuration library
ii  libfreetype62.3.5-1+b1   FreeType 2 font engine, shared lib
ii  libgconf2-4 2.20.1-1 GNOME configuration database syste
ii  libglib2.0-02.14.3-1 The GLib library of C routines
ii  libgnome-keyring0   2.20.1-1 GNOME keyring services library
ii  libgnome2-0 2.20.1.1-1   The GNOME 2 library - runtime file
ii  libgnomecanvas2-0   2.20.1.1-1   A powerful object-oriented display
ii  libgnomeui-02.20.1.1-1   The GNOME 2 libraries (User Interf
ii  libgnomevfs2-0  1:2.20.1-1   GNOME Virtual File System (runtime
ii  libgstreamer-plugins-ba 0.10.15-2GStreamer libraries from the base
ii  libgstreamer0.10-0  0.10.15-1Core GStreamer libraries and eleme
ii  libgtk2.0-0 2.12.1-1 The GTK+ graphical user interface 
ii  libhal1 0.5.10-2 Hardware Abstraction Layer - share
ii  libice6 2:1.0.4-1X11 Inter-Client Exchange library
ii  libnautilus-burn4   2.18.2-1 Nautilus Burn Library - runtime ve
ii  libnotify1 [libnotify1- 0.4.4-3  sends desktop notifications to a n
ii  liborbit2   1:2.14.7-0.1 libraries for ORBit2 - a CORBA ORB
ii  libpango1.0-0   1.18.3-1 Layout and rendering of internatio
ii  libpng12-0  1.2.15~beta5-3   PNG library - runtime
ii  libpopt01.10-3   lib for parsing cmdline parameters
ii  libsm6  2:1.0.3-1+b1 X11 Session Management library
ii  libtotem-plparser1  2.18.2-1 Totem Playlist Parser library - ru
ii  libx11-62:1.0.3-7X11 client-side library
ii  libxcursor1 1:1.1.9-1X cursor management library
ii  libxext61:1.0.3-2X11 miscellaneous extension librar
ii  libxfixes3  1:4.0.3-2X11 miscellaneous 'fixes' extensio
ii  libxi6  2:1.1.3-1X11 Input extension library
ii  libxinerama11:1.0.2-1X11 Xinerama extension library
ii  libxml2 2.6.30.dfsg-3GNOME XML library
ii  libxrandr2  2:1.2.2-1X11 RandR extension library
ii  libxrender1 1:0.9.4-1X Rendering Extension client libra
ii  wodim   9:1.1.6-1command line CD/DVD writing tool
ii  zlib1g  1:1.2.3.3.dfsg-6 compression library - runtime

Versions of packages brasero recommends:
pn  gstreamer0.10-fluendo-mp3 none (no description available)
ii  hal   0.5.10-2   Hardware Abstraction Layer

-- no debconf information


---End Message---
---BeginMessage---
On Mon, Dec 29, 2008 at 09:13:05PM +0200, Onur Aslan wrote:
 I am not using etch and brasero anymore. I upgrade my system to lenny,
 it's working 

Processed: Re: X session is blocked sometimes when resuming from screen saver.

2008-12-29 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 reassign 413392 xscreensaver-gl-extra
Bug#413392: linux-image-2.6.18-4-686: system freeze for `trident' video driver 
+ `pop art squares' screen saver
Bug reassigned from package `linux-2.6' to `xscreensaver-gl-extra'.

 thanks
Stopping processing here.

Please contact me if you need assistance.

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


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



Processed: Re: [linux-image-2.6.25-1-amd64] zd1211rw does not work

2008-12-29 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 reassign 480748 wpasupplicant
Bug#480748: [linux-image-2.6.25-1-amd64] zd1211rw does not work
Bug reassigned from package `linux-2.6' to `wpasupplicant'.

 thanks
Stopping processing here.

Please contact me if you need assistance.

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


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



Bug#503998: marked as done (linux-image-2.6.26-1-686: Randomly broken suspend on Thinkpad T61 after update)

2008-12-29 Thread Debian Bug Tracking System

Your message dated Mon, 29 Dec 2008 20:29:41 +0100
with message-id 20081229192941.ge3...@galadriel.inutil.org
and subject line Re: linux-image-2.6.26-1-686: Randomly broken suspend on 
Thinkpad T61 after update
has caused the Debian Bug report #503998,
regarding linux-image-2.6.26-1-686: Randomly broken suspend on Thinkpad T61 
after update
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.)


-- 
503998: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=503998
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-image-2.6.26-1-686
Version: 2.6.26-9
Severity: normal

I am experiencing problems with suspend after update from 2.6.26-7 or -8
My Thinkpad T61 refuses to wake up from suspend randomly. It only shows blank 
screen (usually backlighted) and LED's signalize it's not suspended anymore.
I dont suspect Nvidia drivers, because they were not updated...



-- Package-specific info:
** Version:
Linux version 2.6.26-1-686 (Debian 2.6.26-9) (wa...@debian.org) (gcc version 
4.1.3 20080623 (prerelease) (Debian 4.1.2-23)) #1 SMP Sat Oct 18 16:22:25 UTC 
2008

** Command line:
root=/dev/sda3 ro vga=869

** Tainted: P (1)

** Kernel log:
[   17.529131] iwl4965: Tunable channels: 13 802.11bg, 19 802.11a channels
[   17.553345] phy0: Selected rate control algorithm 'iwl-4965-rs'
[   17.647623] cs: IO port probe 0x100-0x3af: clean.
[   17.672102] cs: IO port probe 0x3e0-0x4ff: excluding 0x4d0-0x4d7
[   17.703132] cs: IO port probe 0x820-0x8ff: clean.
[   17.750812] cs: IO port probe 0xc00-0xcf7: clean.
[   17.774663] cs: IO port probe 0xa00-0xaff:6ACPI: PCI interrupt for device 
:03:00.0 disabled
[   17.774663]  clean.
[   17.840490] input: 4965AGN as /class/input/input8
[   17.938726] Synaptics Touchpad, model: 1, fw: 6.2, id: 0x81a0b1, caps: 
0xa04793/0x30
[   17.959501] serio: Synaptics pass-through port at isa0060/serio1/input0
[   18.010290] ACPI: PCI Interrupt :00:1b.0[B] - GSI 17 (level, low) - 
IRQ 17
[   18.015987] hda_intel: probe_mask set to 0x1 for device 17aa:20ac
[   18.055570] PCI: Setting latency timer of device :00:1b.0 to 64
[   18.098598] input: SynPS/2 Synaptics TouchPad as /class/input/input9
[   19.909476] Adding 1950440k swap on /dev/sda5.  Priority:-1 extents:1 
across:1950440k
[   19.970075] EXT3-fs warning: maximal mount count reached, running e2fsck is 
recommended
[   20.012924] EXT3 FS on sda3, internal journal
[   21.016300] loop: module loaded
[   21.153141] thinkpad_ec: thinkpad_ec 0.37 loaded.
[   21.200165] tp_smapi 0.37 loading...
[   21.226207] tp_smapi successfully loaded (smapi_port=0xb2).
[   21.272494] hdaps: LENOVO ThinkPad T61 detected, setting orientation 1
[   21.312578] hdaps: initial mode latch is 0x05
[   21.312578] hdaps: setting ec_rate=250, filter_order=2
[   21.312578] hdaps: fake_data_mode set to 0
[   21.312578] hdaps: device successfully initialized.
[   21.336561] input: ThinkPad HDAPS joystick emulation as /class/input/input10
[   21.432786] input: ThinkPad HDAPS accelerometer data as /class/input/input11
[   21.525296] hdaps: driver successfully loaded.
[   21.595448] ide_generic: please use probe_mask=0x3f module parameter for 
probing all legacy ISA IDE ports
[   21.619959] ide_generic: I/O resource 0x1F0-0x1F7 not free.
[   21.645844] ide_generic: I/O resource 0x170-0x177 not free.
[   21.947490] fuse init (API version 7.9)
[   24.083315] IBM TrackPoint firmware: 0x0e, buttons: 3/3
[   24.233105] kjournald starting.  Commit interval 5 seconds
[   24.233192] EXT3-fs warning: maximal mount count reached, running e2fsck is 
recommended
[   24.329737] EXT3 FS on sda7, internal journal
[   24.329737] EXT3-fs: recovery complete.
[   24.362224] EXT3-fs: mounted filesystem with ordered data mode.
[   24.460081] input: TPPS/2 IBM TrackPoint as /class/input/input12
[   24.491242] FAT: utf8 is not a recommended IO charset for FAT filesystems, 
filesystem will be case sensitive!
[   26.914616] ACPI: PCI Interrupt :03:00.0[A] - GSI 17 (level, low) - 
IRQ 17
[   26.957628] PM: Writing back config space on device :03:00.0 at offset 1 
(was 40100102, writing 40100106)
[   26.957628] firmware: requesting iwlwifi-4965-1.ucode
[   27.147646] NET: Registered protocol family 10
[   27.214292] lo: Disabled Privacy Extensions
[   27.242083] ADDRCONF(NETDEV_UP): eth0: link is not ready
[   27.270552] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   27.407164] Registered led device: iwl-phy0:radio
[   27.438940] Registered led device: iwl-phy0:assoc
[   27.465129] Registered led device: iwl-phy0:RX
[   27.514802] Registered led device: 

Bug#413392: X session is blocked sometimes when resuming from screen saver.

2008-12-29 Thread Moritz Muehlenhoff
reassign 413392 xscreensaver-gl-extra
thanks

On Mon, Dec 29, 2008 at 08:41:46PM +0200, Teodor wrote:
 Hi Moritz,
 
 On Sun, Dec 28, 2008 at 3:32 AM, Moritz Muehlenhoff j...@inutil.org wrote:
  Teodor wrote:
   However, with the latest kernel (now in testing too) v2.6.26-10 I'm
   getting from time to time a X/kernel freeze when I'm trying to return
   to my X/gnome session from screen saver (random selected). Only my
   work station is affected (i386) and it didn't happen with any of the
   previous versions, so it seems like a regression introduced in the
   last build (-10).
  
   Does this system run an Intel graphics adapter?
 
  Yes, it does. Is this a known bug?
 
  Does the 2.6.26-11 (or the current -12 image) fix the problem for you?
 
 I've just get the same X11 session freeze, but I've discovered that
 the host is not in freeze. I've connected from my laptop and just
 killed the screen saver child process and this way I could re-login
 and continue the current work.
 
 I have the Screensaver theme set to Random so in this particular
 case the blocking saver program is called rubik:
   doru  6311  0.2  0.2  18300  5536 ?Ss   16:21   0:36
 gnome-screensaver
   doru 29077 65.3  0.2  24372  4736 ?RN   19:42   4:38  \_
 rubik -root
 
 I think this bug report should be closed and/or reassigned to
 'xscreensaver-gl-extra'. Shall I do that?

It should be reassigned instead. I'm doing that for you.

Thanks,
Moritz



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



Bug#426714: intelfb refuses mode switching

2008-12-29 Thread Moritz Muehlenhoff
On Mon, Dec 29, 2008 at 09:57:22AM +0100, Olaf Zaplinski wrote:
 Hello Moritz,

 I tried 2.6.24 and 2.6.26-bpo on both machines. On both machines intelfb  
 now refuses to load with the message cannot acquire agp.

 /etc/initramfs-tools/modules contains:

 agp
 intel_agp
 intelfb mode=1024x768...@60

 I added the agp module, but I do not know exactly if I need that.

Could you send the output of lsmod? It might be that another framebuffer
driver blocks (such as vesafb) is blocking the agp_backend_acquire()
call.

Cheers,
Moritz



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



Bug#480748: [linux-image-2.6.25-1-amd64] zd1211rw does not work

2008-12-29 Thread Moritz Muehlenhoff
reassign 480748 wpasupplicant
thanks

On Mon, Dec 29, 2008 at 12:31:16AM +0100, Gilles Mocellin wrote:
 Le Saturday 27 December 2008 22:41:37 Moritz Muehlenhoff, vous avez écrit :
  On Sun, May 11, 2008 at 11:18:26PM +0200, Gilles Mocellin wrote:
   Package: linux-image-2.6.25-1-amd64
   Version: 2.6.25-1
   Severity: normal
  
   --- Please enter the report below this line. ---
   At least in WPA mode with wpa_supplicant, I cannot anymore connecte to my
   AP. It works fine with linux-image-2.6.24-1-amd64.
 
  Does this error still occur with more recent kernel versions?
 
  Cheers,
  Moritz
 
 There's certainly no problem in the driver, because i works with Network 
 Manager.
 
 See The bug I open shortly after being bashed :
 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=481419
 
 I've just tested with wpasupplicant, it works with actual sid kernel 
 2.6.26-486 (I don't use wpasupplicant anymore on my 686 and amd64 computers).

Thanks, reassigning the bug then.

Cheers,
Moritz




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



Bug#390724: Ooops on Xen reboot

2008-12-29 Thread Andreas Barth
* Moritz Muehlenhoff (j...@inutil.org) [081229 16:12]:
 On Mon, Oct 02, 2006 at 08:07:34PM +0200, Andreas Barth wrote:
  Package: linux-image-2.6.18-1-xen-amd64
  Version: 2.6.18-2
  
  Hi,
  
  on rebooting my Xen dom0, I got this error message.
 
 Does this error occur reproducibly with current Etch Xen kernels?

I had all strange kinds of errors and oops with xen, but none is
reproducible. Sorry.



Cheers,
Andi



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



Bug#390724: Ooops on Xen reboot

2008-12-29 Thread Andreas Barth
* Moritz Muehlenhoff (j...@inutil.org) [081229 20:42]:
 On Mon, Dec 29, 2008 at 08:32:42PM +0100, Andreas Barth wrote:
  * Moritz Muehlenhoff (j...@inutil.org) [081229 16:12]:
   On Mon, Oct 02, 2006 at 08:07:34PM +0200, Andreas Barth wrote:
Package: linux-image-2.6.18-1-xen-amd64
Version: 2.6.18-2

Hi,

on rebooting my Xen dom0, I got this error message.
   
   Does this error occur reproducibly with current Etch Xen kernels?
  
  I had all strange kinds of errors and oops with xen, but none is
  reproducible. Sorry.
 
 So this is something that happened once and never again or does
 it happen occasionally, but only not reproducibly?

I cannot remember of having seen this oops again - and the bug report
is now more than 2 years old, so sorry if details disappeared.


Cheers,
Andi



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



Bug#390724: Ooops on Xen reboot

2008-12-29 Thread Moritz Muehlenhoff
On Mon, Dec 29, 2008 at 08:32:42PM +0100, Andreas Barth wrote:
 * Moritz Muehlenhoff (j...@inutil.org) [081229 16:12]:
  On Mon, Oct 02, 2006 at 08:07:34PM +0200, Andreas Barth wrote:
   Package: linux-image-2.6.18-1-xen-amd64
   Version: 2.6.18-2
   
   Hi,
   
   on rebooting my Xen dom0, I got this error message.
  
  Does this error occur reproducibly with current Etch Xen kernels?
 
 I had all strange kinds of errors and oops with xen, but none is
 reproducible. Sorry.

So this is something that happened once and never again or does
it happen occasionally, but only not reproducibly?

Cheers,
Moritz



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



Bug#390724: marked as done (Ooops on Xen reboot)

2008-12-29 Thread Debian Bug Tracking System

Your message dated Mon, 29 Dec 2008 21:16:44 +0100
with message-id 20081229201644.ga4...@galadriel.inutil.org
and subject line Re: Ooops on Xen reboot
has caused the Debian Bug report #390724,
regarding Ooops on Xen reboot
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.)


-- 
390724: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=390724
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-image-2.6.18-1-xen-amd64
Version: 2.6.18-2

Hi,

on rebooting my Xen dom0, I got this error message.


Cheers,
Andi

 Kernel BUG at drivers/xen/netfront/netfront.c:717
 invalid opcode:  [1] SMP
 CPU 0
 Modules linked in: ipv6 dm_snapshot dm_mirror dm_mod evdev pcspkr ext3 jbd 
mbcache raid1 md_mod
 Pid: 8, comm: xenwatch Not tainted 2.6.18-1-xen-amd64 #1
 RIP: e030:[8036f61b]  [8036f61b] 
network_alloc_rx_buffers+0x1de/0x460
 RSP: e02b:8800070d7de0  EFLAGS: 00010086
 RAX:  RBX: 8800083ebd80 RCX: 0040
 RDX:  RSI:  RDI: 1048
 RBP: 8800013d8500 R08: 80455b88 R09: 0001
 R10: 0001 R11: 88000156d460 R12: 05605000
 R13: 880007344838 R14: 0209 R15: 8800013ddae0
 FS:  2ae1cded4100() GS:804c3000() knlGS:
 CS:  e033 DS:  ES: 
 Process xenwatch (pid: 8, threadinfo 8800070d6000, task 8800070bc100)
 Stack:  8800070d7e40  8800013d8000  88000145c000 000f
  00d10100  8800013f6d68  00d1 002f04ed2e70
  0009  0001
 Call Trace:
  [80367a7b] backend_changed+0x1c8/0x232
  [80366920] xenwatch_thread+0x0/0x145
  [80290032] keventd_create_kthread+0x0/0x61
  [80365d2e] xenwatch_handle_callback+0x15/0x48
  [80366a4d] xenwatch_thread+0x12d/0x145
  [802901f5] autoremove_wake_function+0x0/0x2e
  [80290032] keventd_create_kthread+0x0/0x61
  [80366920] xenwatch_thread+0x0/0x145
  [802334f8] kthread+0xd4/0x107
  [8025d06c] child_rip+0xa/0x12
  [80290032] keventd_create_kthread+0x0/0x61
  [8024982d] worker_thread+0x0/0x122
  [8024982d] worker_thread+0x0/0x122
  [80233424] kthread+0x0/0x107
  [8025d062] child_rip+0x0/0x12


 Code: 0f 0b 68 ec ee 41 80 c2 cd 02 4c 63 e2 48 8d bd 80 15 00 00
 RIP  [8036f61b] network_alloc_rx_buffers+0x1de/0x460
  RSP 8800070d7de0
-- 
  http://home.arcor.de/andreas-barth/

---End Message---
---BeginMessage---
On Mon, Dec 29, 2008 at 08:54:31PM +0100, Andreas Barth wrote:
 * Moritz Muehlenhoff (j...@inutil.org) [081229 20:42]:
  On Mon, Dec 29, 2008 at 08:32:42PM +0100, Andreas Barth wrote:
   * Moritz Muehlenhoff (j...@inutil.org) [081229 16:12]:
On Mon, Oct 02, 2006 at 08:07:34PM +0200, Andreas Barth wrote:
 Package: linux-image-2.6.18-1-xen-amd64
 Version: 2.6.18-2
 
 Hi,
 
 on rebooting my Xen dom0, I got this error message.

Does this error occur reproducibly with current Etch Xen kernels?
   
   I had all strange kinds of errors and oops with xen, but none is
   reproducible. Sorry.
  
  So this is something that happened once and never again or does
  it happen occasionally, but only not reproducibly?
 
 I cannot remember of having seen this oops again - and the bug report
 is now more than 2 years old, so sorry if details disappeared.

Thanks, closing the bug then.

Cheers,
Moritz

---End Message---


Bug#425355: Acknowledgement (dpt_i2o - disk IO causes very high load)

2008-12-29 Thread Moritz Muehlenhoff
On Wed, Jun 13, 2007 at 09:31:35PM +0200, Peter Hirdina wrote:
 Some additional information about my system:
 
 * Tyan Tiger MPX (AMD760MPX Chipset)
 * 2x Athlon MP 2800+
 * 2GB registered ECC RAM
 * Adaptec 2400A with 4 disks configured as RAID-5
 
 I know about the PCI performance problems of the 768 southbridge. From
 what I've read on the net so far, it seems that only write performance
 is really affected, being limited to ~25MB/s. Read Performance seems to
 be OK.
 
 If I compare those values with the ones I get from system, then I'm
 quite disappointed. I can hardly squeeze 15MB/s out of my RAID (shared
 betweend reads and writes). So if I copy a file on the RAID from one
 directory to another, this works at a whopping speed of ~7MB/s.
 
 Also if read on the net, that the primary PCI bus on the MPX platform
 doesn't have those problems, and a lot of people were seeing drastic
 performance improvements when they moved their PCI cards to the 64bit
 slots. I tried that as well, but the difference is hardly worth
 mentioning (performance improved to around 17MB/s).
 
 So my conclusion is, that there is something else wrong here.

Does this error still occur with more recent kernel versions?

If you're running Etch, could you try to reproduce this bug
with the 2.6.24 based kernel added in 4.0r4?
http://packages.qa.debian.org/l/linux-2.6.24.html

Cheers,
Moritz



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



Bug#415864: aic7xxx: aic7892(B): BUG: soft lockup detected on CPU#0

2008-12-29 Thread Moritz Muehlenhoff
On Thu, Mar 22, 2007 at 06:52:06PM +0100, tom schorpp wrote:
 Package: linux-image-2.6.18-4-amd64
 Version: 2.6.18.dfsg.1-11
 Severity: critical
 Justification: breaks the whole system + netinstall iso
 
 lo,
 
 well, ive several live cd systems  2.6.19.5i386 that oops and hang boot in 
 aic7xxx init,
 only one booting here is knoppix 5.2,
 
 the latest unofficial debian stable 2.6.8-12-amd64-generic, which says ACPI: 
 PCI interrupt 
 :00:06.0[A] - GSI 17 (level, low) - IRQ 17
 aic7xxx: PCI0:6:0 MEM region 0x0 unavailable. Cannot memory map device.
 but works ok,
 
 a debian etch 2.6.18-4-amd64 which says:
 
 SCSI subsystem initialized
 GSI 16 sharing vector 0xA9 and IRQ 16
 ACPI: PCI Interrupt :00:06.0[A] - GSI 17 (level, low) - IRQ 169
 BUG: soft lockup detected on CPU#0!
 
 Call Trace:
 IRQ [802a3fec] softlockup_tick+0xdb/0xed
 [802881df] update_process_times+0x42/0x68
 [8026cbd8] smp_local_timer_interrupt+0x23/0x47
 [8026d2cc] smp_apic_timer_interrupt+0x41/0x47
 [8025904a] apic_timer_interrupt+0x66/0x6c
 EOI [8038a412] pci_conf1_write+0x0/0xc9
 [88053718] :aic7xxx:ahc_pci_test_register_access+0xc2/0x391
 [880536a5] :aic7xxx:ahc_pci_test_register_access+0x4f/0x391
 [88059416] :aic7xxx:ahc_pci_map_registers+0x1bb/0x239
 [880523d2] :aic7xxx:ahc_pci_config+0x4c/0x12d0
 [80389fb7] pcibios_set_master+0x1e/0x84
 [88059186] :aic7xxx:ahc_linux_pci_dev_probe+0x13e/0x213
 [80317eea] pci_device_probe+0xdf/0x147
 [8036b9db] driver_probe_device+0x52/0xa8
 [8036ba96] __driver_attach+0x0/0x9a
 [8036bae6] __driver_attach+0x50/0x9a
 [8036ba96] __driver_attach+0x0/0x9a
 [8036b458] bus_for_each_dev+0x43/0x6e
 [8036b09a] bus_add_driver+0x7e/0x130
 [803180c4] __pci_register_driver+0x57/0x7d
 [8805903e] :aic7xxx:ahc_linux_pci_init+0x17/0x21
 [8806e325] :aic7xxx:ahc_linux_init+0x325/0x336
 [8027d27d] default_wake_function+0x0/0xe
 [8025e2e5] __down_read+0x12/0x9a
 [80294fa1] __link_module+0x0/0x25
 [802200e5] __up_read+0x13/0x8a
 [80297695] sys_init_module+0x16cc/0x1882
 [802584d6] system_call+0x7e/0x83
 
 BUG: soft lockup detected on CPU#0!
 
 a kernel.org 2.6.20 with K8 config set but built in a 32Bit debian sid 
 environment, but 
 works ok,
 
 and finally the latest kernel.org 2.6.20.3 AMD K8 built on debian amd64 etch 
 userland that 
 hangs boot on aic7xxx init without magic sysreq keys functionality:
 Loading iSCSI transport class v2.0-724.
 ACPI: PCI Interrupt :00:06.0[A] - GSI 17 (level, low) - IRQ 17
 ... Kernel alive - Kernel direct mapping tables up to 1 @ 8000-d000
 
 according to the stack above this should be a pci adaptor mem resources prob.
 tweaking boot parameters did not fix.
 
 now trying latest scsi git and be on ##kernel at freenode if Q.
 
 update: no fix so far in kernel.org scsi-rc-fixes.git, just on 
 building a scsi dev git kernel with change from K8-x86_64 generic 
 Kconfig and full debug, examining driver code and will report if i find 
 the cause.

Does this error still occur with more recent kernel versions?

Cheers,
Moritz



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



Bug#432312: BUG: soft lockup detected on CPU#1

2008-12-29 Thread Moritz Muehlenhoff
On Wed, Jul 11, 2007 at 11:26:25AM +0200, Michael Meskes wrote:
 reassign 432312 linux-image-2.6.21-2-k7
 thanks
 
 On Mon, Jul 09, 2007 at 01:07:46PM +0200, Peter wrote:
  Package: quota
  Version: 3.14-8
  
  When activating quota on my server I get kernelpanics:
  ...
 
 User space utilities shouldn't create kernel panics by just calling a
 function. Thus I would think it's a kernel problem. The quota package
 only contains the user space utilities, but not the kernel code. 

Peter, does this error still occur with more recent kernel versions?

Cheers,
Moritz



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



Re: [pkg-wpa-devel] Processed: Re: [linux-image-2.6.25-1-amd64] zd1211rw does not work

2008-12-29 Thread Kel Modderman
On Tuesday 30 December 2008 05:27:04 Debian Bug Tracking System wrote:
 480748

Why have we been given this?

There is nil information on this BR which suggests wpa_supplicant has a fault.

Thanks, Kel.


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



Bug#433413: marked as done (linux-2.6: uhci-hcd causes nobody cared on resume or kexec boot)

2008-12-29 Thread Debian Bug Tracking System

Your message dated Mon, 29 Dec 2008 21:32:25 +
with message-id 20081229213225.ga5...@crustytoothpaste.ath.cx
and subject line Re: Bug#433413: linux-2.6: uhci-hcd causes nobody cared on 
resume or kexec boot
has caused the Debian Bug report #433413,
regarding linux-2.6: uhci-hcd causes nobody cared on resume or kexec boot
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.)


-- 
433413: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=433413
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-2.6
Version: 2.6.22-1
Severity: normal

Whenever I resume (from suspend) or reboot using kexec, uhci-hcd causes
a nobody cared error, which causes the interrupt (below, 17) to be
disabled.  I have not tried irqpoll; I will shortly.

Furthermore, this prevents ipw3945 from working until a reboot through
the BIOS. (Note, however, that ipw3945 is not loaded until after the
error occurs, when using kexec; therefore, ipw3945 does not cause the
error in any way.)

If I remove all the modules using that interrupt, and reload them, all
of them except ipw3945 work, and the interrupt is reenabled.  I can also
avoid this, in the suspend/resume case, by unloading uhci-hcd before
suspend and reloading it on resume, which prevents the problem.

/proc/interrupts (from a fresh boot):
   CPU0   CPU1   
  0: 290077  0   IO-APIC-edge  timer
  1:   3402  0   IO-APIC-edge  i8042
  8:  1  0   IO-APIC-edge  rtc
  9:   1258  0   IO-APIC-fasteoi   acpi
 12: 131626  0   IO-APIC-edge  i8042
 14:  10334  0   IO-APIC-edge  ide0
 16:  10685  0   IO-APIC-fasteoi   uhci_hcd:usb1, yenta, 
i...@pci::00:02.0
 17: 377369  0   IO-APIC-fasteoi   uhci_hcd:usb2, firewire_ohci, 
ipw3945, HDA Intel
 18:  0  0   IO-APIC-fasteoi   uhci_hcd:usb3
 19:  2  0   IO-APIC-fasteoi   uhci_hcd:usb4, ehci_hcd:usb5
1274:  11753  0   PCI-MSI-edge  eth0
1275:  12806  0   PCI-MSI-edge  ahci
NMI:  0  0 
LOC: 290034 290011 
ERR:  0

from kern.log (with kexec on 2.6.22-1):
Jul 16 21:51:31 lakeview kernel:  sda:3irq 17: nobody cared (try booting with 
the irqpoll option)
Jul 16 21:51:31 lakeview kernel: 
Jul 16 21:51:31 lakeview kernel: Call Trace:
Jul 16 21:51:31 lakeview kernel:  IRQ  [8025dfff] 
__report_bad_irq+0x30/0x72
Jul 16 21:51:31 lakeview kernel:  [8025e224] 
note_interrupt+0x1e3/0x227
Jul 16 21:51:31 lakeview kernel:  [8025eaf1] 
handle_fasteoi_irq+0xa9/0xd0
Jul 16 21:51:31 lakeview kernel:  [8020ca0d] do_IRQ+0x6c/0xd3
Jul 16 21:51:31 lakeview kernel:  [8020a2a1] ret_from_intr+0x0/0xa
Jul 16 21:51:31 lakeview kernel:  EOI  [88051aae] 
:processor:acpi_processor_idle+0x25a/0x454
Jul 16 21:51:31 lakeview kernel:  [88051aa4] 
:processor:acpi_processor_idle+0x250/0x454
Jul 16 21:51:31 lakeview kernel:  [88051854] 
:processor:acpi_processor_idle+0x0/0x454
Jul 16 21:51:31 lakeview kernel:  [80209125] cpu_idle+0x8b/0xae
Jul 16 21:51:31 lakeview kernel:  [80526762] start_kernel+0x2c0/0x2cc
Jul 16 21:51:31 lakeview kernel:  [80526140] _sinittext+0x140/0x144
Jul 16 21:51:31 lakeview kernel: 
Jul 16 21:51:31 lakeview kernel: 
Jul 16 21:51:31 lakeview kernel: handlers:
Jul 16 21:51:31 lakeview kernel: [80367668] (usb_hcd_irq+0x0/0x52)
Jul 16 21:51:31 lakeview kernel: [880bcb54] (irq_handler+0x0/0x1c1 
[firewire_ohci])
Jul 16 21:51:31 lakeview kernel: Disabling IRQ #17

from kern.log (with resume on 2.6.18.dfsg.1-12etch1):
May 11 13:14:27 lakeview kernel: irq 201: nobody cared (try booting with the ir
qpoll option)
May 11 13:14:27 lakeview kernel: 
May 11 13:14:27 lakeview kernel: Call Trace:
May 11 13:14:27 lakeview kernel:  IRQ [802a4c23] 
__report_bad_irq+0x30/0x7d
May 11 13:14:27 lakeview kernel:  [802a4e5d] 
note_interrupt+0x1ed/0x22e
May 11 13:14:27 lakeview kernel:  [802a436a] __do_IRQ+0xc7/0x105
May 11 13:14:27 lakeview kernel:  [80210381] __do_softirq+0x5e/0xd5
May 11 13:14:27 lakeview kernel:  [8026401f] do_IRQ+0x65/0x73
May 11 13:14:27 lakeview kernel:  [802589d1] ret_from_intr+0x0/0xa
May 11 13:14:27 lakeview kernel:  EOI [8800589f] 
:processor:acpi_processor_idle+0x284/0x465
May 11 13:14:27 lakeview kernel:  [88005895] 
:processor:acpi_processor_idle+0x27a/0x465
May 11 13:14:27 lakeview kernel:  [8800561b] 

Bug#497361: linux-image-2.6.26-1-amd64: apple usb modem does not work 05ac:1401

2008-12-29 Thread Moritz Muehlenhoff
On Mon, Sep 01, 2008 at 09:23:03AM +0200, Sebastià Matas wrote:
 Package: linux-image-2.6.26-1-amd64
 Version: 2.6.26-3
 Severity: important
 
 Hi, I'm using a MacBookPro laptop with debian sid on it.
 
 Unfortunatelly it has no MODEM (PSTN) and during hollidays I needed one.
 The bad luck is that I read on an Ubuntu forum about the modem and that
 it worked, but I missread, they refered to an internal modem, not the
 USB one.
 
 So I have now this useless (in linux, on MacOSX it works) usb modem.
 
 lsusb shows:
 Bus 001 Device 005: ID 05ac:1401 Apple, Inc.
 
 so it detects it as an Apple thing, but shows nothing more...
 
 And here's the relevant part of cat /proc/bus/usb/devices
 
 T:  Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=  5 Spd=12  MxCh= 0
 D:  Ver= 2.00 Cls=ff(vend.) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
 P:  Vendor=05ac ProdID=1401 Rev= 2.02
 S:  Manufacturer=Motorola, Inc.
 S:  Product=Apple USB Modem
 S:  SerialNumber=00
 C:* #Ifs= 6 Cfg#= 1 Atr=a0 MxPwr= 50mA
 I:* If#= 0 Alt= 0 #EPs= 1 Cls=02(comm.) Sub=03 Prot=00 Driver=(none)
 E:  Ad=81(I) Atr=03(Int.) MxPS=  11 Ivl=1ms
 I:* If#= 1 Alt= 0 #EPs= 0 Cls=ff(vend.) Sub=02 Prot=ff Driver=(none)
 I:* If#= 2 Alt= 0 #EPs= 0 Cls=01(audio) Sub=01 Prot=00 Driver=(none)
 I:* If#= 3 Alt= 0 #EPs= 0 Cls=01(audio) Sub=02 Prot=00 Driver=(none)
 I:  If#= 3 Alt= 1 #EPs= 1 Cls=01(audio) Sub=02 Prot=00 Driver=(none)
 E:  Ad=82(I) Atr=25(Isoc) MxPS=  24 Ivl=1ms
 I:* If#= 4 Alt= 0 #EPs= 0 Cls=01(audio) Sub=02 Prot=00 Driver=(none)
 I:  If#= 4 Alt= 1 #EPs= 1 Cls=01(audio) Sub=02 Prot=00 Driver=(none)
 E:  Ad=03(O) Atr=05(Isoc) MxPS=  24 Ivl=1ms
 I:* If#= 5 Alt= 0 #EPs= 0 Cls=fe(app. ) Sub=01 Prot=01 Driver=(none)
 
 And here's the output of dmesg:
 [  143.382994] usb 1-1: new full speed USB device using uhci_hcd and address 5
 [  143.557874] usb 1-1: configuration #1 chosen from 1 choice
 [  143.561429] usb 1-1: New USB device found, idVendor=05ac, idProduct=1401
 [  143.561429] usb 1-1: New USB device strings: Mfr=2, Product=3, 
 SerialNumber=4
 [  143.561429] usb 1-1: Product: Apple USB Modem
 [  143.561429] usb 1-1: Manufacturer: Motorola, Inc.
 [  143.561429] usb 1-1: SerialNumber: 00
 [  144.377729] usbcore: registered new interface driver snd-usb-audio
 
 I've googled and found nothing about this modem working in linux. 
 I contacted Greg KH and he told me it should work with the kernel module
 cdc-acm. 

According to http://forum.eeeuser.com/viewtopic.php?id=15954 this modem
is a softmodem and won't work with current Linux versions.

Cheers,
Moritz



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



Bug#447941: linux-headers-2.6.22-2-686: usb occasionally goes into EIO returning loop for VIDIOC_DQBUF

2008-12-29 Thread Folkert van Heusden
why did you report that against the headers package?
   Oops!
also this should be fixed upstream with latest dvb in 2.6.26-rc3,
can you please double check?
   I search for linux-image-2.6.26 but could not find anything? (on
   packages.debian.org)
  kernel.org ;)
  what x86 arch do you need? using:
  Linux dual 2.6.26-rc3-amd64 #1 SMP Mon May 19 01:19:54 CEST 2008 x86_64
  GNU/Linux
  but can build 32 bit also.
 does this error still occur with more recent kernel versions?

No, problem can be closed.
thanks!


Folkert van Heusden

-- 
MultiTail na wan makriki wrokosani fu tan luku den logfile nanga san
den commando spiti puru. Piki puru spesrutu sani, wroko nanga difrenti
kroru, tya kon makandra, nanga wan lo moro.
http://www.vanheusden.com/multitail/
--
Phone: +31-6-41278122, PGP-key: 1F28D8AE, www.vanheusden.com



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



Bug#447941: marked as done (linux-headers-2.6.22-2-686: usb occasionally goes into EIO returning loop for VIDIOC_DQBUF)

2008-12-29 Thread Debian Bug Tracking System

Your message dated Mon, 29 Dec 2008 22:46:30 +0100
with message-id 20081229214630.ga3...@galadriel.inutil.org
and subject line Re: linux-headers-2.6.22-2-686: usb occasionally goes into EIO 
returning loop for VIDIOC_DQBUF
has caused the Debian Bug report #447941,
regarding linux-headers-2.6.22-2-686: usb occasionally goes into EIO returning 
loop for VIDIOC_DQBUF
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.)


-- 
447941: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=447941
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-headers-2.6.22-2-686
Version: 2.6.22-4
Severity: normal


usb occasionally goes into EIO returning loop for VIDIOC_DQBUF

this happens while running 'motion' on a philips webcam on an usb bus with only 
1 device
folk...@gateway:~$ lsusb
Bus 004 Device 001: ID :
Bus 002 Device 001: ID :
Bus 003 Device 001: ID :
Bus 001 Device 002: ID 0471:0311 Philips PCVC740K ToUcam Pro [pwc]
Bus 001 Device 001: ID :

e.g.:
[1] v4l2_next: VIDIOC_DQBUF: EIO (s-pframe 0)
[1] v4l2_next: VIDIOC_DQBUF: EIO (s-pframe 1)
[1] v4l2_next: VIDIOC_DQBUF: EIO (s-pframe 0)

what 'solves' the problem is closing and re-opening (e.g. restarting the 
process) the device


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

Kernel: Linux 2.6.22-2-686 (SMP w/1 CPU core)
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash

Versions of packages linux-headers-2.6.22-2-686 depends on:
ii  gcc-4.1   4.1.2-13   The GNU C compiler
ii  linux-headers-2.6.22-22.6.22-4   Common header files for Linux 2.6.
ii  linux-kbuild-2.6.22   2.6.22-1   Kbuild infrastructure for Linux 2.

linux-headers-2.6.22-2-686 recommends no packages.

-- no debconf information


---End Message---
---BeginMessage---
Version: 2.6.26-1

On Mon, Dec 29, 2008 at 10:27:57PM +0100, Folkert van Heusden wrote:
 why did you report that against the headers package?
Oops!
 also this should be fixed upstream with latest dvb in 2.6.26-rc3,
 can you please double check?
I search for linux-image-2.6.26 but could not find anything? (on
packages.debian.org)
   kernel.org ;)
   what x86 arch do you need? using:
   Linux dual 2.6.26-rc3-amd64 #1 SMP Mon May 19 01:19:54 CEST 2008 x86_64
   GNU/Linux
   but can build 32 bit also.
  does this error still occur with more recent kernel versions?
 
 No, problem can be closed.
 thanks!

Thanks, closing the bug then.

Cheers,
Moritz

---End Message---


Bug#431403: marked as done (linux-image-2.6.18-4-xen-amd64: the 'microcode'-module (for intel cpus) fails to insert with missing symbols errors)

2008-12-29 Thread Debian Bug Tracking System

Your message dated Mon, 29 Dec 2008 22:47:02 +0100
with message-id 20081229214702.gb3...@galadriel.inutil.org
and subject line Re: linux-image-2.6.18-4-xen-amd64: the 'microcode'-module 
(for intel cpus) fails to insert with missing symbols errors
has caused the Debian Bug report #431403,
regarding linux-image-2.6.18-4-xen-amd64: the 'microcode'-module (for intel 
cpus) fails to insert with missing symbols errors
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.)


-- 
431403: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=431403
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-image-2.6.18-4-xen-amd64
Version: 2.6.18.dfsg.1-12
Severity: normal


When trying to insert the 'microcode' module, I get errors complaining
about missing symbols:

belle:/home/folkert# modprobe microcode
FATAL: Error inserting microcode 
(/lib/modules/2.6.18-4-xen-amd64/kernel/arch/x86_64/kernel/microcode.ko): 
Unknown symbol in module, or unknown parameter (see dmesg)
belle:/home/folkert# dmesg | tail
microcode: Unknown symbol sys_munlock
microcode: Unknown symbol sys_mlock


-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.18-4-xen-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash

Versions of packages linux-image-2.6.18-4-xen-amd64 depends on:
ii  e2fsprog 1.39+1.40-WIP-2006.11.14+dfsg-2 ext2 file system utilities and lib
ii  initramf 0.88tools for generating an initramfs
ii  linux-mo 2.6.18.dfsg.1-12Linux 2.6.18 modules on AMD64

linux-image-2.6.18-4-xen-amd64 recommends no packages.

-- no debconf information

---End Message---
---BeginMessage---
On Mon, Dec 29, 2008 at 10:29:16PM +0100, Folkert van Heusden wrote:
   Package: linux-image-2.6.18-4-xen-amd64
   Version: 2.6.18.dfsg.1-12
   Severity: normal
   
   
   When trying to insert the 'microcode' module, I get errors complaining
   about missing symbols:
   
   belle:/home/folkert# modprobe microcode
   FATAL: Error inserting microcode 
   (/lib/modules/2.6.18-4-xen-amd64/kernel/arch/x86_64/kernel/microcode.ko): 
   Unknown symbol in module, or unknown parameter (see dmesg)
   belle:/home/folkert# dmesg | tail
   microcode: Unknown symbol sys_munlock
   microcode: Unknown symbol sys_mlock
  
  Does this error still occur with more recent kernel versions?
 
 Nope seems to be fixed.

Thanks, closing the bug then.

Cheers,
Moritz
 

---End Message---


Processed: Re: Bug#447549: linux-2.6: orinoco.c printk messages flood terminal

2008-12-29 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 forwarded 447549 http://marc.info/?l=linux-wirelessm=123058933020818w=2
Bug#447549: linux-2.6: orinoco.c printk messages flood terminal
Noted your statement that Bug has been forwarded to 
http://marc.info/?l=linux-wirelessm=123058933020818w=2.

 thank you
Stopping processing here.

Please contact me if you need assistance.

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


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



Bug#447549: linux-2.6: orinoco.c printk messages flood terminal

2008-12-29 Thread Michael Gilbert
forwarded 447549 http://marc.info/?l=linux-wirelessm=123058933020818w=2
thank you

just forwarded this today.  please follow progress upstream.



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



Bug#425355: Acknowledgement (dpt_i2o - disk IO causes very high load)

2008-12-29 Thread Peter Hirdina
Sorry, totally forgot about this bug.

 Does this error still occur with more recent kernel versions?

I haven't tested it, but it will. After plugging a PCI 1GBit ethernet
card (Intel) into the system which also showed massive performance
problems, I did some extensive research. Well, there is a bug, but it
is not within Linux but the 760MPX chipset. AMD messed up the 32bit PCI
bus completely. You will hardly get 20MB/s over it. Which explains the
problems I had with the RAID controller and the ethernet card.

So, feel free to close this bug, since it was a hardware problem.
Actually, I replaced the machine anyway a few ago anyway.

cheers,
Peter

-- 
The road to hell is paved with NAND gates.
-- J. Gooding



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



Bug#502553: marked as done (support new smart array controllers)

2008-12-29 Thread Debian Bug Tracking System

Your message dated Tue, 30 Dec 2008 01:52:23 +
with message-id e1lhtmr-0002cn...@ries.debian.org
and subject line Bug#502553: fixed in fai-kernels 1.17+etch.24
has caused the Debian Bug report #502553,
regarding support new smart array controllers
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.)


-- 
502553: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=502553
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-2.6
Version: 2.6.18.dfsg.1-23
Severity: important

According to 24aac480e76c6f5d1391ac05c5e9c0eb9b0cd302, new smart array
controllers will become available in late Fall 2008. This bug is to
track the progress of adding support for these devices in etch.

Patching in new Smart Array PCI IDs isn't strictly necessary, in
general. There is a fallback mode in the cciss driver that recognizes
Unknown Smart Array Controllers, and has some until recently sane
defaults. The problem is that these defaults are no longer sane for
newer hardware. The fallback 'max outstanding commands' setting is
too high for the next generation controllers running in Zero Memory
Raid mode. This means that the current etch kernels will happily
detect and operate these newer controllers, but will be setting a
queue depth too large for the controller's fifo. To resolve this, an
additional patch is suggested that retrieves the queue depth setting
from the card's config instead of hard coding each card's value in a
table.

2.6.18 can also use 9cff3b383dad193b0762c27278a16237e10b53dc, adding
pci ids for the previously released P700M controller, which is already
supported in 2.6.24.

-- 
dann frazier



---End Message---
---BeginMessage---
Source: fai-kernels
Source-Version: 1.17+etch.24

We believe that the bug you reported is fixed in the latest version of
fai-kernels, which is due to be installed in the Debian FTP archive:

fai-kernels_1.17+etch.24.dsc
  to pool/main/f/fai-kernels/fai-kernels_1.17+etch.24.dsc
fai-kernels_1.17+etch.24.tar.gz
  to pool/main/f/fai-kernels/fai-kernels_1.17+etch.24.tar.gz
fai-kernels_1.17+etch.24_i386.deb
  to pool/main/f/fai-kernels/fai-kernels_1.17+etch.24_i386.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 502...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
dann frazier da...@debian.org (supplier of updated fai-kernels package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Mon, 29 Dec 2008 11:36:34 -0700
Source: fai-kernels
Binary: fai-kernels
Architecture: source i386
Version: 1.17+etch.24
Distribution: stable
Urgency: high
Maintainer: Holger Levsen hol...@debian.org
Changed-By: dann frazier da...@debian.org
Description: 
 fai-kernels - special kernels for FAI (Fully Automatic Installation)
Closes: 391373 478717 502553 506418 506420
Changes: 
 fai-kernels (1.17+etch.24) stable; urgency=high
 .
   * Rebuild against linux-source-2.6.18_2.6.18.dfsg.1-24:
 [ dann frazier ]
 * cciss: Add support for new hardware (closes: #502553)
- Add PCI ids for P700m, P212, P410, P410i, P411, P812, P711m, p712m
- Read the FIFO size from the controller config instead of
  hardcoding it into the driver
 * [hppa] disable UP-optimized flush_tlb_mm, fixing thread-related
   hangs. (closes: #478717)
 .
 [ Ian Campbell ]
 * xen: Add softlockup-no-idle-hz.patch to prevent softlockup in xen guest.
   (closes: #506418)
 .
 [ Bastian Blank ]
 * [xen] Remove 4gb segments warning completely. (closes: #391373)
 * [xen/i386] Fix pseudo hwcap value to match newer kernels.
   (closes: #506420)
Files: 
 f1dd70eeba3e86e5f3abbd51ffbe2189 725 admin extra fai-kernels_1.17+etch.24.dsc
 70a28743493c996f9411c7b7a772f1ee 58059 admin extra 
fai-kernels_1.17+etch.24.tar.gz
 d1a10e3a5ab7a2f1d05bbe56e46f4f55 5509456 admin extra 
fai-kernels_1.17+etch.24_i386.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)

iD8DBQFJWTFRhuANDBmkLRkRAo3DAKCCzBUVZT6q5kNjP7lH4E9XwrTzbQCeKQwN
YLiO7bRgFrEED4Iu2ZK+3kc=
=QSXe
-END PGP SIGNATURE-


---End Message---


Bug#506420: marked as done (incorrect hwcap line in /etc/ld.so.conf.d/libc6-xen.conf?)

2008-12-29 Thread Debian Bug Tracking System

Your message dated Tue, 30 Dec 2008 01:52:23 +
with message-id e1lhtmr-0002cr...@ries.debian.org
and subject line Bug#506420: fixed in fai-kernels 1.17+etch.24
has caused the Debian Bug report #506420,
regarding incorrect hwcap line in /etc/ld.so.conf.d/libc6-xen.conf?
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.)


-- 
506420: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=506420
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---

Package: libc6-xen
Version: 2.7-16

As shipped, /etc/ld.so.conf.d/libc6-xen.conf read as follows:

 # This directive teaches ldconfig to search in nosegneg subdirectories
 # and cache the DSOs there with extra bit 1 set in their hwcap match
 # fields. In Xen guest kernels, the vDSO tells the dynamic linker to
 # search in nosegneg subdirectories and to match this extra hwcap bit
 # in the ld.so.cache file.
 hwcap 1 nosegneg

However I still got thousands of 4gb seg fixup messages and ldd 
revealed that the runtime linker was not using the Xen-friendly Libc.


Changing the 1 to 0, based on a mailing list posting I found, fixed the 
problem.


Unfortunately I've not found where any of this is documented (the 
ldconfig man page does not contain any useful pointers) so this is 
slightly guesswork on my part.  Perhaps the man page could be improved.


(I'm using etch's Xen and running testing and unstable VMs; the kernel 
in all cases is 2.6.18-6-xen-686.)


ttfn/rjk


---End Message---
---BeginMessage---
Source: fai-kernels
Source-Version: 1.17+etch.24

We believe that the bug you reported is fixed in the latest version of
fai-kernels, which is due to be installed in the Debian FTP archive:

fai-kernels_1.17+etch.24.dsc
  to pool/main/f/fai-kernels/fai-kernels_1.17+etch.24.dsc
fai-kernels_1.17+etch.24.tar.gz
  to pool/main/f/fai-kernels/fai-kernels_1.17+etch.24.tar.gz
fai-kernels_1.17+etch.24_i386.deb
  to pool/main/f/fai-kernels/fai-kernels_1.17+etch.24_i386.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 506...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
dann frazier da...@debian.org (supplier of updated fai-kernels package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Mon, 29 Dec 2008 11:36:34 -0700
Source: fai-kernels
Binary: fai-kernels
Architecture: source i386
Version: 1.17+etch.24
Distribution: stable
Urgency: high
Maintainer: Holger Levsen hol...@debian.org
Changed-By: dann frazier da...@debian.org
Description: 
 fai-kernels - special kernels for FAI (Fully Automatic Installation)
Closes: 391373 478717 502553 506418 506420
Changes: 
 fai-kernels (1.17+etch.24) stable; urgency=high
 .
   * Rebuild against linux-source-2.6.18_2.6.18.dfsg.1-24:
 [ dann frazier ]
 * cciss: Add support for new hardware (closes: #502553)
- Add PCI ids for P700m, P212, P410, P410i, P411, P812, P711m, p712m
- Read the FIFO size from the controller config instead of
  hardcoding it into the driver
 * [hppa] disable UP-optimized flush_tlb_mm, fixing thread-related
   hangs. (closes: #478717)
 .
 [ Ian Campbell ]
 * xen: Add softlockup-no-idle-hz.patch to prevent softlockup in xen guest.
   (closes: #506418)
 .
 [ Bastian Blank ]
 * [xen] Remove 4gb segments warning completely. (closes: #391373)
 * [xen/i386] Fix pseudo hwcap value to match newer kernels.
   (closes: #506420)
Files: 
 f1dd70eeba3e86e5f3abbd51ffbe2189 725 admin extra fai-kernels_1.17+etch.24.dsc
 70a28743493c996f9411c7b7a772f1ee 58059 admin extra 
fai-kernels_1.17+etch.24.tar.gz
 d1a10e3a5ab7a2f1d05bbe56e46f4f55 5509456 admin extra 
fai-kernels_1.17+etch.24_i386.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)

iD8DBQFJWTFRhuANDBmkLRkRAo3DAKCCzBUVZT6q5kNjP7lH4E9XwrTzbQCeKQwN
YLiO7bRgFrEED4Iu2ZK+3kc=
=QSXe
-END PGP SIGNATURE-


---End Message---


Bug#502553: marked as done (support new smart array controllers)

2008-12-29 Thread Debian Bug Tracking System

Your message dated Tue, 30 Dec 2008 01:52:22 +
with message-id e1lhtmq-0002cy...@ries.debian.org
and subject line Bug#502553: fixed in user-mode-linux 2.6.18-1um-2etch.24
has caused the Debian Bug report #502553,
regarding support new smart array controllers
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.)


-- 
502553: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=502553
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-2.6
Version: 2.6.18.dfsg.1-23
Severity: important

According to 24aac480e76c6f5d1391ac05c5e9c0eb9b0cd302, new smart array
controllers will become available in late Fall 2008. This bug is to
track the progress of adding support for these devices in etch.

Patching in new Smart Array PCI IDs isn't strictly necessary, in
general. There is a fallback mode in the cciss driver that recognizes
Unknown Smart Array Controllers, and has some until recently sane
defaults. The problem is that these defaults are no longer sane for
newer hardware. The fallback 'max outstanding commands' setting is
too high for the next generation controllers running in Zero Memory
Raid mode. This means that the current etch kernels will happily
detect and operate these newer controllers, but will be setting a
queue depth too large for the controller's fifo. To resolve this, an
additional patch is suggested that retrieves the queue depth setting
from the card's config instead of hard coding each card's value in a
table.

2.6.18 can also use 9cff3b383dad193b0762c27278a16237e10b53dc, adding
pci ids for the previously released P700M controller, which is already
supported in 2.6.24.

-- 
dann frazier



---End Message---
---BeginMessage---
Source: user-mode-linux
Source-Version: 2.6.18-1um-2etch.24

We believe that the bug you reported is fixed in the latest version of
user-mode-linux, which is due to be installed in the Debian FTP archive:

user-mode-linux_2.6.18-1um-2etch.24.diff.gz
  to pool/main/u/user-mode-linux/user-mode-linux_2.6.18-1um-2etch.24.diff.gz
user-mode-linux_2.6.18-1um-2etch.24.dsc
  to pool/main/u/user-mode-linux/user-mode-linux_2.6.18-1um-2etch.24.dsc
user-mode-linux_2.6.18-1um-2etch.24_i386.deb
  to pool/main/u/user-mode-linux/user-mode-linux_2.6.18-1um-2etch.24_i386.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 502...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
dann frazier da...@debian.org (supplier of updated user-mode-linux package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Mon, 29 Dec 2008 12:11:56 -0700
Source: user-mode-linux
Binary: user-mode-linux
Architecture: source i386
Version: 2.6.18-1um-2etch.24
Distribution: stable
Urgency: high
Maintainer: User Mode Linux Maintainers pkg-uml-p...@lists.alioth.debian.org
Changed-By: dann frazier da...@debian.org
Description: 
 user-mode-linux - User-mode Linux (kernel)
Closes: 391373 478717 502553 506418 506420
Changes: 
 user-mode-linux (2.6.18-1um-2etch.24) stable; urgency=high
 .
   * Rebuild against linux-source-2.6.18_2.6.18.dfsg.1-24:
 [ dann frazier ]
 * cciss: Add support for new hardware (closes: #502553)
- Add PCI ids for P700m, P212, P410, P410i, P411, P812, P711m, p712m
- Read the FIFO size from the controller config instead of
  hardcoding it into the driver
 * [hppa] disable UP-optimized flush_tlb_mm, fixing thread-related
   hangs. (closes: #478717)
 .
 [ Ian Campbell ]
 * xen: Add softlockup-no-idle-hz.patch to prevent softlockup in xen guest.
   (closes: #506418)
 .
 [ Bastian Blank ]
 * [xen] Remove 4gb segments warning completely. (closes: #391373)
 * [xen/i386] Fix pseudo hwcap value to match newer kernels.
   (closes: #506420)
Files: 
 a1c5b965f88cba4b1b710130f20944a2 877 misc extra 
user-mode-linux_2.6.18-1um-2etch.24.dsc
 6f58c7c625c76ff7fdeeb32c502b953f 19691 misc extra 
user-mode-linux_2.6.18-1um-2etch.24.diff.gz
 692cf2f50488b66dc333b12eacafbd98 25602764 misc extra 
user-mode-linux_2.6.18-1um-2etch.24_i386.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)

iD8DBQFJWTFXhuANDBmkLRkRAhAvAJ4wkOuy4otOgudHnknNp7SCD3qHnQCdHHIB
6ZQfZgyGylRq309vJ4m6jvE=
=hdlK
-END PGP SIGNATURE-

Bug#506418: marked as done (linux-image-2.6.18-6-xen-amd64: domU soft lockup detected)

2008-12-29 Thread Debian Bug Tracking System

Your message dated Tue, 30 Dec 2008 01:52:23 +
with message-id e1lhtmr-0002cp...@ries.debian.org
and subject line Bug#506418: fixed in fai-kernels 1.17+etch.24
has caused the Debian Bug report #506418,
regarding linux-image-2.6.18-6-xen-amd64: domU soft lockup detected
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.)


-- 
506418: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=506418
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-image-2.6.18-6-xen-amd64
Version: 2.6.18.dfsg.1-23
Severity: normal


domU is getting these from time to time (no live migration is being done):


BUG: soft lockup detected on CPU#1!

Call Trace:
 IRQ [8029fb75] softlockup_tick+0xdb/0xed
 [80267dc0] timer_interrupt+0x38d/0x3db
 [80211162] handle_IRQ_event+0x2d/0x60
 [8029feb4] __do_IRQ+0xa4/0x105
 [8028366f] _local_bh_enable+0x59/0xb3
 [802665ae] do_IRQ+0x65/0x73
 [80361105] evtchn_do_upcall+0x86/0xe0
 [8025c606] do_hypervisor_callback+0x1e/0x2c
 EOI [802063aa] hypercall_page+0x3aa/0x1000
 [802063aa] hypercall_page+0x3aa/0x1000
 [8026733c] raw_safe_halt+0x84/0xa8
 [802645b1] xen_idle+0x38/0x4a
 [80248830] cpu_idle+0x97/0xba

BUG: soft lockup detected on CPU#2!

Call Trace:
 IRQ [8029fb75] softlockup_tick+0xdb/0xed
 [80267dc0] timer_interrupt+0x38d/0x3db
 [80211162] handle_IRQ_event+0x2d/0x60
 [8029feb4] __do_IRQ+0xa4/0x105
 [8028366f] _local_bh_enable+0x59/0xb3
 [802665ae] do_IRQ+0x65/0x73
 [80361105] evtchn_do_upcall+0x86/0xe0
 [8025c606] do_hypervisor_callback+0x1e/0x2c
 EOI [802063aa] hypercall_page+0x3aa/0x1000
 [802063aa] hypercall_page+0x3aa/0x1000
 [8026733c] raw_safe_halt+0x84/0xa8
 [802645b1] xen_idle+0x38/0x4a
 [80248830] cpu_idle+0x97/0xba


There are other reports of this bug in Debian Etch kernel:

  http://lists.xensource.com/archives/html/xen-bugs/2008-10/msg3.html
  http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1261

And RedHat seems to have a patch you might be able to use:

  https://bugzilla.redhat.com/show_bug.cgi?id=250994


-- System Information:
Debian Release: 4.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-6-xen-amd64
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

Versions of packages linux-image-2.6.18-6-xen-amd64 depends on:
ii  e2f 1.39+1.40-WIP-2006.11.14+dfsg-2etch1 ext2 file system utilities and lib
ii  ini 0.85itools for generating an initramfs
ii  lin 2.6.18.dfsg.1-23 Linux 2.6.18 modules on AMD64

linux-image-2.6.18-6-xen-amd64 recommends no packages.

-- no debconf information


---End Message---
---BeginMessage---
Source: fai-kernels
Source-Version: 1.17+etch.24

We believe that the bug you reported is fixed in the latest version of
fai-kernels, which is due to be installed in the Debian FTP archive:

fai-kernels_1.17+etch.24.dsc
  to pool/main/f/fai-kernels/fai-kernels_1.17+etch.24.dsc
fai-kernels_1.17+etch.24.tar.gz
  to pool/main/f/fai-kernels/fai-kernels_1.17+etch.24.tar.gz
fai-kernels_1.17+etch.24_i386.deb
  to pool/main/f/fai-kernels/fai-kernels_1.17+etch.24_i386.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 506...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
dann frazier da...@debian.org (supplier of updated fai-kernels package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Mon, 29 Dec 2008 11:36:34 -0700
Source: fai-kernels
Binary: fai-kernels
Architecture: source i386
Version: 1.17+etch.24
Distribution: stable
Urgency: high
Maintainer: Holger Levsen hol...@debian.org
Changed-By: dann frazier da...@debian.org
Description: 
 fai-kernels - special kernels for FAI (Fully Automatic Installation)
Closes: 391373 478717 502553 506418 506420
Changes: 
 fai-kernels (1.17+etch.24) stable; urgency=high
 .
   * Rebuild against linux-source-2.6.18_2.6.18.dfsg.1-24:
 [ dann frazier ]
 * cciss: Add support for new hardware (closes: #502553)
- Add 

Bug#506418: marked as done (linux-image-2.6.18-6-xen-amd64: domU soft lockup detected)

2008-12-29 Thread Debian Bug Tracking System

Your message dated Tue, 30 Dec 2008 01:52:22 +
with message-id e1lhtmq-0002ca...@ries.debian.org
and subject line Bug#506418: fixed in user-mode-linux 2.6.18-1um-2etch.24
has caused the Debian Bug report #506418,
regarding linux-image-2.6.18-6-xen-amd64: domU soft lockup detected
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.)


-- 
506418: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=506418
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-image-2.6.18-6-xen-amd64
Version: 2.6.18.dfsg.1-23
Severity: normal


domU is getting these from time to time (no live migration is being done):


BUG: soft lockup detected on CPU#1!

Call Trace:
 IRQ [8029fb75] softlockup_tick+0xdb/0xed
 [80267dc0] timer_interrupt+0x38d/0x3db
 [80211162] handle_IRQ_event+0x2d/0x60
 [8029feb4] __do_IRQ+0xa4/0x105
 [8028366f] _local_bh_enable+0x59/0xb3
 [802665ae] do_IRQ+0x65/0x73
 [80361105] evtchn_do_upcall+0x86/0xe0
 [8025c606] do_hypervisor_callback+0x1e/0x2c
 EOI [802063aa] hypercall_page+0x3aa/0x1000
 [802063aa] hypercall_page+0x3aa/0x1000
 [8026733c] raw_safe_halt+0x84/0xa8
 [802645b1] xen_idle+0x38/0x4a
 [80248830] cpu_idle+0x97/0xba

BUG: soft lockup detected on CPU#2!

Call Trace:
 IRQ [8029fb75] softlockup_tick+0xdb/0xed
 [80267dc0] timer_interrupt+0x38d/0x3db
 [80211162] handle_IRQ_event+0x2d/0x60
 [8029feb4] __do_IRQ+0xa4/0x105
 [8028366f] _local_bh_enable+0x59/0xb3
 [802665ae] do_IRQ+0x65/0x73
 [80361105] evtchn_do_upcall+0x86/0xe0
 [8025c606] do_hypervisor_callback+0x1e/0x2c
 EOI [802063aa] hypercall_page+0x3aa/0x1000
 [802063aa] hypercall_page+0x3aa/0x1000
 [8026733c] raw_safe_halt+0x84/0xa8
 [802645b1] xen_idle+0x38/0x4a
 [80248830] cpu_idle+0x97/0xba


There are other reports of this bug in Debian Etch kernel:

  http://lists.xensource.com/archives/html/xen-bugs/2008-10/msg3.html
  http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1261

And RedHat seems to have a patch you might be able to use:

  https://bugzilla.redhat.com/show_bug.cgi?id=250994


-- System Information:
Debian Release: 4.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-6-xen-amd64
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

Versions of packages linux-image-2.6.18-6-xen-amd64 depends on:
ii  e2f 1.39+1.40-WIP-2006.11.14+dfsg-2etch1 ext2 file system utilities and lib
ii  ini 0.85itools for generating an initramfs
ii  lin 2.6.18.dfsg.1-23 Linux 2.6.18 modules on AMD64

linux-image-2.6.18-6-xen-amd64 recommends no packages.

-- no debconf information


---End Message---
---BeginMessage---
Source: user-mode-linux
Source-Version: 2.6.18-1um-2etch.24

We believe that the bug you reported is fixed in the latest version of
user-mode-linux, which is due to be installed in the Debian FTP archive:

user-mode-linux_2.6.18-1um-2etch.24.diff.gz
  to pool/main/u/user-mode-linux/user-mode-linux_2.6.18-1um-2etch.24.diff.gz
user-mode-linux_2.6.18-1um-2etch.24.dsc
  to pool/main/u/user-mode-linux/user-mode-linux_2.6.18-1um-2etch.24.dsc
user-mode-linux_2.6.18-1um-2etch.24_i386.deb
  to pool/main/u/user-mode-linux/user-mode-linux_2.6.18-1um-2etch.24_i386.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 506...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
dann frazier da...@debian.org (supplier of updated user-mode-linux package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Mon, 29 Dec 2008 12:11:56 -0700
Source: user-mode-linux
Binary: user-mode-linux
Architecture: source i386
Version: 2.6.18-1um-2etch.24
Distribution: stable
Urgency: high
Maintainer: User Mode Linux Maintainers pkg-uml-p...@lists.alioth.debian.org
Changed-By: dann frazier da...@debian.org
Description: 
 user-mode-linux - User-mode Linux (kernel)
Closes: 391373 478717 502553 506418 506420
Changes: 
 user-mode-linux (2.6.18-1um-2etch.24) stable; urgency=high
 .
   * Rebuild 

Bug#506420: marked as done (incorrect hwcap line in /etc/ld.so.conf.d/libc6-xen.conf?)

2008-12-29 Thread Debian Bug Tracking System

Your message dated Tue, 30 Dec 2008 01:52:22 +
with message-id e1lhtmq-0002cc...@ries.debian.org
and subject line Bug#506420: fixed in user-mode-linux 2.6.18-1um-2etch.24
has caused the Debian Bug report #506420,
regarding incorrect hwcap line in /etc/ld.so.conf.d/libc6-xen.conf?
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.)


-- 
506420: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=506420
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---

Package: libc6-xen
Version: 2.7-16

As shipped, /etc/ld.so.conf.d/libc6-xen.conf read as follows:

 # This directive teaches ldconfig to search in nosegneg subdirectories
 # and cache the DSOs there with extra bit 1 set in their hwcap match
 # fields. In Xen guest kernels, the vDSO tells the dynamic linker to
 # search in nosegneg subdirectories and to match this extra hwcap bit
 # in the ld.so.cache file.
 hwcap 1 nosegneg

However I still got thousands of 4gb seg fixup messages and ldd 
revealed that the runtime linker was not using the Xen-friendly Libc.


Changing the 1 to 0, based on a mailing list posting I found, fixed the 
problem.


Unfortunately I've not found where any of this is documented (the 
ldconfig man page does not contain any useful pointers) so this is 
slightly guesswork on my part.  Perhaps the man page could be improved.


(I'm using etch's Xen and running testing and unstable VMs; the kernel 
in all cases is 2.6.18-6-xen-686.)


ttfn/rjk


---End Message---
---BeginMessage---
Source: user-mode-linux
Source-Version: 2.6.18-1um-2etch.24

We believe that the bug you reported is fixed in the latest version of
user-mode-linux, which is due to be installed in the Debian FTP archive:

user-mode-linux_2.6.18-1um-2etch.24.diff.gz
  to pool/main/u/user-mode-linux/user-mode-linux_2.6.18-1um-2etch.24.diff.gz
user-mode-linux_2.6.18-1um-2etch.24.dsc
  to pool/main/u/user-mode-linux/user-mode-linux_2.6.18-1um-2etch.24.dsc
user-mode-linux_2.6.18-1um-2etch.24_i386.deb
  to pool/main/u/user-mode-linux/user-mode-linux_2.6.18-1um-2etch.24_i386.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 506...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
dann frazier da...@debian.org (supplier of updated user-mode-linux package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Mon, 29 Dec 2008 12:11:56 -0700
Source: user-mode-linux
Binary: user-mode-linux
Architecture: source i386
Version: 2.6.18-1um-2etch.24
Distribution: stable
Urgency: high
Maintainer: User Mode Linux Maintainers pkg-uml-p...@lists.alioth.debian.org
Changed-By: dann frazier da...@debian.org
Description: 
 user-mode-linux - User-mode Linux (kernel)
Closes: 391373 478717 502553 506418 506420
Changes: 
 user-mode-linux (2.6.18-1um-2etch.24) stable; urgency=high
 .
   * Rebuild against linux-source-2.6.18_2.6.18.dfsg.1-24:
 [ dann frazier ]
 * cciss: Add support for new hardware (closes: #502553)
- Add PCI ids for P700m, P212, P410, P410i, P411, P812, P711m, p712m
- Read the FIFO size from the controller config instead of
  hardcoding it into the driver
 * [hppa] disable UP-optimized flush_tlb_mm, fixing thread-related
   hangs. (closes: #478717)
 .
 [ Ian Campbell ]
 * xen: Add softlockup-no-idle-hz.patch to prevent softlockup in xen guest.
   (closes: #506418)
 .
 [ Bastian Blank ]
 * [xen] Remove 4gb segments warning completely. (closes: #391373)
 * [xen/i386] Fix pseudo hwcap value to match newer kernels.
   (closes: #506420)
Files: 
 a1c5b965f88cba4b1b710130f20944a2 877 misc extra 
user-mode-linux_2.6.18-1um-2etch.24.dsc
 6f58c7c625c76ff7fdeeb32c502b953f 19691 misc extra 
user-mode-linux_2.6.18-1um-2etch.24.diff.gz
 692cf2f50488b66dc333b12eacafbd98 25602764 misc extra 
user-mode-linux_2.6.18-1um-2etch.24_i386.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)

iD8DBQFJWTFXhuANDBmkLRkRAhAvAJ4wkOuy4otOgudHnknNp7SCD3qHnQCdHHIB
6ZQfZgyGylRq309vJ4m6jvE=
=hdlK
-END PGP SIGNATURE-


---End Message---


Bug#408317: Installation Report [mips] [rc1] [Failure] SWARM (Broadcom BCM91250a)

2008-12-29 Thread Moritz Muehlenhoff
On Fri, Dec 29, 2006 at 04:09:44PM +0100, Karsten Merker wrote:
 
 Comments/Problems:
 ==
 
 In the step detecting hard drives a reproducible kernel panic
 occurs (log follows below).
 
 RC1 uses a 2.6.17 kernel. Not sure whether this is relevant in
 this case, but according to the git commit logs there have been
 changes to the SWARM IDE code in the Linux/MIPS tree with regard
 to 2.6.17 and 2.6.18 in November/December 2006.

Does this error still occur with more recent kernel versions?

Cheers,
Moritz



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



Bug#401524: xorg hangs on Ultra1 with cgsix card

2008-12-29 Thread Moritz Muehlenhoff
On Wed, May 02, 2007 at 05:17:18AM +, Andre' Breiler wrote:
 Hi,
 
 I did experiment a bit with it finding the following:
 - kernel 2.4.x + XFree86 works
 - kernel 2.6.x + XFree86 fails (as in X is working but screen goes blank)
 - kernel 2.6.x + XOrg fails too
 .
 
 I didn't get time to test a Xorg with a 2.4.x kernel but looking at the
 driver changes in X I'd expect that working as well.
 
 If you need someone to test I'm happy to play with it (I don't have a
 Ultra 1 anymore but a Ultra 2 and same gfx card).

Does this error still occur with more recent kernel/X.org versions?

Cheers,
Moritz



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



Bug#474033: But I don't use parport, so don't load it

2008-12-29 Thread maximilian attems
On Sun, Dec 28, 2008 at 06:14:59AM +0800, jida...@jidanni.org wrote:
 
 Does one just write something in /etc/modprobe.d/blacklist as a last
 resort? Is there a /etc/modprobe.d/blacklist.local or better place to
 write that something?
 

yep, search for blacklist in man modprobe.conf

-- 
maks



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