Bug#436387: linux-modules-extra-2.6: FTBFS: unmet b-dep linux-support-2.6.21-2
Package: linux-modules-extra-2.6 version: 2.6.21-4 Severity: serious User: [EMAIL PROTECTED] Usertags: qa-ftbfs-20070806 qa-ftbfs Justification: FTBFS on i386 Hi, During a rebuild of all packages in sid, your package failed to build on i386. Relevant part: ** Using build dependencies supplied by package: Build-Depends: debhelper (>= 5), linux-support-2.6.21-2, linux-headers-2.6.21-2-all-alpha [alpha], linux-headers-2.6.21-2-all-amd64 [amd64], linux-headers-2.6.21-2-all-arm [arm], linux-headers-2.6.21-2-all-armel [armel], linux-headers-2.6.21-2-all-hppa [hppa], linux-headers-2.6.21-2-all-i386 [i386], linux-headers-2.6.21-2-all-ia64 [ia64], linux-headers-2.6.21-2-all-m68k [m68k], linux-headers-2.6.21-2-all-mips [mips], linux-headers-2.6.21-2-all-mipsel [mipsel], linux-headers-2.6.21-2-all-powerpc [powerpc], linux-headers-2.6.21-2-all-s390 [s390], linux-headers-2.6.21-2-all-sparc [sparc], squashfs-source [alpha amd64 armel i386 ia64 m68k mips mipsel powerpc s390 sparc], unionfs-source, gspca-source [amd64 i386 powerpc] Checking for already installed source dependencies... W: Unable to locate package linux-support-2.6.21-2 W: Unable to locate package linux-headers-2.6.21-2-all-i386 debhelper: missing Using default version 5.0.53 linux-support-2.6.21-2: missing linux-headers-2.6.21-2-all-i386: missing squashfs-source: missing unionfs-source: missing gspca-source: missing Checking for source dependency conflicts... Reading package lists... Building dependency tree... Reading state information... E: Couldn't find package linux-support-2.6.21-2 apt-get failed. Package installation failed Trying to reinstall removed packages: Trying to uninstall newly installed packages: Source-dependencies not satisfied; skipping linux-modules-extra-2.6 The full build log is available from http://people.debian.org/~lucas/logs/2007/08/06 About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot containing a sid i386 environment. Internet was not accessible from the build systems. -- | Lucas Nussbaum | [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ | | jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#314707: UDMA3/4/5 not working with Centrino Chipset, 82801DBM (ICH4-M) IDE Controller (rev 03)
hello erik, thanks for your quick feedback. On Mon, 06 Aug 2007, Erik Schanze wrote: > maximilian attems <[EMAIL PROTECTED]>: > > is the matter fixed in etch? > > > I don't know. > I run unstable and the problem still exists. ok can you please test latest 2.6.23-rc2 see trunk apt lines -> http://wiki.debian.org/DebianKernel > dmesg: > ... > ICH4: chipset revision 3 > ICH4: not 100% native mode: will probe irqs later > ide0: BM-DMA at 0x1100-0x1107, BIOS settings: hda:DMA, hdb:pio > ide1: BM-DMA at 0x1108-0x110f, BIOS settings: hdc:DMA, hdd:pio > Probing IDE interface ide0... > usb 3-3: new high speed USB device using ehci_hcd and address 2 > usb 3-3: configuration #1 chosen from 1 choice > hda: TOSHIBA MK6021GAS, ATA DISK drive > SCSI subsystem initialized > Initializing USB Mass Storage driver... > scsi0 : SCSI emulation for USB Mass Storage devices > usb-storage: device found at 2 > usb-storage: waiting for device to settle before scanning > usbcore: registered new interface driver usb-storage > USB Mass Storage support registered. > hda: host side 80-wire cable detection failed, limiting max speed to > UDMA33 > hda: selected mode 0x42 > ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 > Probing IDE interface ide1... > ieee1394: Host added: ID:BUS[0-00:1023] GUID[00023f41440053ff] > Clocksource tsc unstable (delta = -223793410 ns) > hdc: Slimtype COMBO LSC-24082K, ATAPI CD/DVD-ROM drive > hdc: selected mode 0x42 > ide1 at 0x170-0x177,0x376 on irq 15 > ACPI: PCI Interrupt :00:1d.2[C] -> Link [LNKC] -> GSI 10 (level, > low) -> IRQ 10 > PCI: Setting latency timer of device :00:1d.2 to 64 > uhci_hcd :00:1d.2: UHCI Host Controller > uhci_hcd :00:1d.2: new USB bus registered, assigned bus number 4 > uhci_hcd :00:1d.2: irq 10, io base 0x1700 > usb usb4: configuration #1 chosen from 1 choice > hub 4-0:1.0: USB hub found > hda: max request size: 128KiB > hub 4-0:1.0: 2 ports detected > hda: 117210240 sectors (60011 MB), CHS=65535/16/63, UDMA(33) > hda: cache flushes supported > hda: hda1 hda2 hda3 hda4 < hda5 hda6 hda7 > > hdc: ATAPI 24X DVD-ROM CD-R/RW drive, 2048kB Cache, UDMA(33) > Uniform CD-ROM driver Revision: 3.20 > ... > > > I doubt that there is no 80 wire cable in my notebook (Acer Travelmate > 291),but I didn't open it. > Perhaps the detection works not correctly? i see. > Currently I use a self compiled kernel with modified source code > (piix_cable_detect() in /usr/src/linux/drivers/ide/pci/piix.c) > to skip cable detection and UDMA100 works very well. hmm looks like, as ide maintainers are currently busyli working it might be a good timing :) please if aboves kernel has the same failure file the bugreport on bugzilla.kernel.org against ide and inform us of the bugzilla bug nr. tejun and ac should take care of it. best regards -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: error in linux-headers-2.6.23-rc2-*
hello norbert, On Mon, Aug 06, 2007 at 09:14:56PM +0200, Norbert Breun wrote: > > isn't it funny: > > linux-headers-2.6.23-rc2-all: > Depends: linux-headers-2.6.23-rc2-all-i386 but it is not going to > be installed > > it depends on itself... > > > Even linux-kbuild-2.6.23 is not there so I get this too: > > linux-headers-2.6.23-rc2-k7: > Depends: linux-kbuild-2.6.23 but it is not installable > > > just to keep you informed... yes that is a known "feature" of the daily rcX buildserver builds, they are not very friendly to out of tree modules. i'm happy enough to have the kernel itself tested. regards -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#436320: ITP: tgt - Linux target framework user-space tools
Package: wnpp Severity: wishlist Owner: Debian Kernel Team * Package name: tgt Version : 20070807.1 Upstream Author : [EMAIL PROTECTED] * URL : git://git.kernel.org/pub/scm/linux/kernel/git/tomo/tgt.git * License : GPLv2 Programming Lang: C Description : Linux target framework Linux target framework (tgt) aims to simplify various SCSI target driver (iSCSI, Fibre Channel, SRP, etc) creation and maintenance. Tgt consists of kernel modules, user-space daemon, and user-space tools. Some target drivers uses all of them and some use only user-space daemon and tools (i.e. they completely runs in user space). This package contains the user-space daemon and tools, a recent Linux kernel is required for the modules. Currently, tgt supports three target drivers: - IBM VIO server (ibmvstgt) - iSCSI - Xen vscsifront/back -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.21-2-vserver-amd64 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash signature.asc Description: Digital signature
Bug#314707: UDMA3/4/5 not working with Centrino Chipset, 82801DBM (ICH4-M) IDE Controller (rev 03)
Hi maximilian, maximilian attems <[EMAIL PROTECTED]>: > is the matter fixed in etch? > I don't know. I run unstable and the problem still exists. dmesg: ... ICH4: chipset revision 3 ICH4: not 100% native mode: will probe irqs later ide0: BM-DMA at 0x1100-0x1107, BIOS settings: hda:DMA, hdb:pio ide1: BM-DMA at 0x1108-0x110f, BIOS settings: hdc:DMA, hdd:pio Probing IDE interface ide0... usb 3-3: new high speed USB device using ehci_hcd and address 2 usb 3-3: configuration #1 chosen from 1 choice hda: TOSHIBA MK6021GAS, ATA DISK drive SCSI subsystem initialized Initializing USB Mass Storage driver... scsi0 : SCSI emulation for USB Mass Storage devices usb-storage: device found at 2 usb-storage: waiting for device to settle before scanning usbcore: registered new interface driver usb-storage USB Mass Storage support registered. hda: host side 80-wire cable detection failed, limiting max speed to UDMA33 hda: selected mode 0x42 ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 Probing IDE interface ide1... ieee1394: Host added: ID:BUS[0-00:1023] GUID[00023f41440053ff] Clocksource tsc unstable (delta = -223793410 ns) hdc: Slimtype COMBO LSC-24082K, ATAPI CD/DVD-ROM drive hdc: selected mode 0x42 ide1 at 0x170-0x177,0x376 on irq 15 ACPI: PCI Interrupt :00:1d.2[C] -> Link [LNKC] -> GSI 10 (level, low) -> IRQ 10 PCI: Setting latency timer of device :00:1d.2 to 64 uhci_hcd :00:1d.2: UHCI Host Controller uhci_hcd :00:1d.2: new USB bus registered, assigned bus number 4 uhci_hcd :00:1d.2: irq 10, io base 0x1700 usb usb4: configuration #1 chosen from 1 choice hub 4-0:1.0: USB hub found hda: max request size: 128KiB hub 4-0:1.0: 2 ports detected hda: 117210240 sectors (60011 MB), CHS=65535/16/63, UDMA(33) hda: cache flushes supported hda: hda1 hda2 hda3 hda4 < hda5 hda6 hda7 > hdc: ATAPI 24X DVD-ROM CD-R/RW drive, 2048kB Cache, UDMA(33) Uniform CD-ROM driver Revision: 3.20 ... I doubt that there is no 80 wire cable in my notebook (Acer Travelmate 291),but I didn't open it. Perhaps the detection works not correctly? Currently I use a self compiled kernel with modified source code (piix_cable_detect() in /usr/src/linux/drivers/ide/pci/piix.c) to skip cable detection and UDMA100 works very well. Kindly regards, Erik -- www.ErikSchanze.de * Bitte keine HTML-E-Mails! No HTML mails, please! Limit: 100 kB * - Linux-Info-Tag in Dresden, 3. November 2007 * Info: http://www.linux-info-tag.de/* -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
error in linux-headers-2.6.23-rc2-*
Hi there, isn't it funny: linux-headers-2.6.23-rc2-all: Depends: linux-headers-2.6.23-rc2-all-i386 but it is not going to be installed it depends on itself... Even linux-kbuild-2.6.23 is not there so I get this too: linux-headers-2.6.23-rc2-k7: Depends: linux-kbuild-2.6.23 but it is not installable just to keep you informed... Cheers Norbert
Processed: Re: Bug#436260: Acknowledgement (linux-support-2.6.22-1: Support for exernal module packages broken)
Processing commands for [EMAIL PROTECTED]: > tag 436260 + patch Bug#436260: linux-support-2.6.22-1: Support for exernal module packages broken There were no tags set. Tags added: patch > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#436260: Acknowledgement (linux-support-2.6.22-1: Support for exernal module packages broken)
tag 436260 + patch
thanks
The enclosed gencontrol.py for use in module packages probably fixes
interoperation with module packages for current kernel versions. It
appears to work for me but I have relatively little confidence in my
changes given that I don't particularly understand the changes that I'm
adapting for.
--
"You grabbed my hand and we fell into it, like a daydream - or a fever."
#!/usr/bin/env python2.4
import sys
sys.path.append(sys.argv[1] + "/lib/python")
from debian_linux.gencontrol import Gencontrol
from debian_linux.gencontrol import PackagesList
from debian_linux.config import *
from debian_linux.debian import *
from debian_linux.config import ConfigParser
class gencontrol(Gencontrol):
def __init__(self, config):
Gencontrol.__init__(self, config)
self.process_config_version(ConfigParser({}, [sys.argv[1] + "/version"]))
def __call__(self):
packages = PackagesList()
makefile = [('.NOTPARALLEL:', ())]
self.do_source(packages)
self.do_main(packages, makefile)
self.do_extra(packages, makefile)
self.write_control(packages.itervalues())
self.write_makefile(makefile)
def do_main_packages(self, packages, extra):
vars = self.vars
main = self.templates["control.main"]
packages.extend(self.process_packages(main, vars))
packages['source']['Build-Depends'].extend(
['linux-support-%s%s' % (self.version.upstream, self.abiname)]
)
packages['source']['Build-Depends'].extend(
['linux-headers-%s%s-all-%s [%s]' % (self.version.upstream, self.abiname, arch, arch)
for arch in self.config['base',]['arches']],
)
def do_flavour(self, packages, makefile, arch, subarch, flavour, vars, makeflags, extra):
config_entry = self.config.merge('base', arch, subarch, flavour)
if config_entry.get('modules', True) is False:
return
Gencontrol.do_flavour(self, packages, makefile, arch, subarch, flavour, vars, makeflags, extra)
def do_flavour_packages(self, packages, makefile, arch, subarch, flavour, vars, makeflags, extra):
modules = self.templates["control.modules"]
modules = self.process_packages(modules, vars)
for package in modules:
name = package['Package']
if packages.has_key(name):
package = packages.get(name)
package['Architecture'].append(arch)
else:
package['Architecture'] = [arch]
packages.append(package)
makeflags_string = ' '.join(["%s='%s'" % i for i in makeflags.iteritems()])
cmds_binary_arch = []
cmds_binary_arch.append(("$(MAKE) -f debian/rules.real binary-arch-flavour %s" % makeflags_string,))
cmds_build = []
cmds_build.append(("$(MAKE) -f debian/rules.real build %s" % makeflags_string,))
cmds_setup = []
cmds_setup.append(("$(MAKE) -f debian/rules.real setup-flavour %s" % makeflags_string,))
makefile.append(("binary-arch-%s-%s-%s-real:" % (arch, subarch, flavour), cmds_binary_arch))
makefile.append(("build-%s-%s-%s-real:" % (arch, subarch, flavour), cmds_build))
makefile.append(("setup-%s-%s-%s-real:" % (arch, subarch, flavour), cmds_setup))
def process_config_version(self, config):
entry = config['version',]
self.version = VersionLinux(entry['source'])
self.abiname = entry['abiname']
self.vars = self.process_version_linux(self.version, self.abiname)
if __name__ == '__main__':
gencontrol(sys.argv[1] + "/arch")()
signature.asc
Description: Digital signature
Bug#429622: AMD/ATI SB700 support to Debian
On Mon, Aug 06, 2007 at 03:17:30PM +0800, Shane Huang wrote: > Hi Dann: > > Do you mean you need our test to the point release kernel on > SB700/SB600? > I think I can ask our QA's help to test it. Great, that helps a great deal. > And I have one question > here: > > Is there any installation CD/DVD ISO image of "point release", which can > be > downloaded and burnt into CD/DVD? (It seems that there is no such ISO > image) Correct - there is no such image yet. The installers will need to be rebuilt for the point release to add this support (which we'll need to negotiate with the installer team). > If there is no such image, we need to install etch(4.0) on a non-SB700 > board, > then upgrade the linux kernel into the version you mentioned, and try to > boot this updated kernel on SB700 board, Am I right? Correct. You should be able to install in another machine (e.g., an SB600) and upgrade, then swap the disks. It is possible to build your own installer w/ a custom kernel, but its not a path I would suggest if the disk-swap procedure is workable. > Because I think etch(4.0) can NOT be installed onto SB700 board > directly. That's how I understand it as well. -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#436267: linux-image-2.6.22-1-686: IEEE1394 modules unbuilt in packaged kernel
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Monday 06 August 2007, maximilian attems was heard to say: > no they are the old firwire stack, > that has been disabled due to security concern and general > distrust. Oh crud. :^( > what are you missing in the yuyu stack? At least raw1394, to create an entry /dev/raw1394 so that dvgrab can access a video camera. I don't know what else might have been mixed into the stack to do the work. The camera shows up, dmesg shows the following when I plug it in: - firewire_core: phy config: card 0, new root=ffc1, gap_count=5 firewire_core: phy config: card 0, new root=ffc1, gap_count=5 firewire_core: created new fw device fw1 (0 config rom retries) - But if /dev/raw1394 is gone with a good reason, such is life. You folks are the experts. Curt- - -- September 11th, 2001 The proudest day for gun control and central planning advocates in American history -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iQEVAwUBRrdlLy9Y35yItIgBAQJa6gf+PHwMHysrCkgYxOH2Z+E1dbz9fP7e5HXH DmqER+1FJpT6KyU8BKvSeYL88b3c3F4ats6F/O5bB7F3ipOuP0l+AgVmgrMt7uyJ SponVi72S7RoeOVvJBYw5Q6caANDdQEwL2HNdiDKcoWEC0m5X6m1bX8CBq5/numv Wq4HWqgjABLzLZRBE9tzlaYV6DWrDrLj6Jm4ININPh3qHP7q13xtzzMz3n8Lb3wu QXkcRT29Kz8C8V4+tzTNfP80BM15bhbBoR9o19XyaZ73PU6Ks1ff0oPkpP1HlJAV nwDZJuVasH2dHDNqu0/t9BReio9yvQUsmoxapRQ/1Azi0sB48EdwmQ== =H7XK -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#436156: installation-reports: Inst report TP35D2-A7 (SATA difficulties)
Processing commands for [EMAIL PROTECTED]: > reassign 436156 linux-2.6 Bug#436156: installation-reports: Inst report TP35D2-A7 (SATA difficulties) Bug reassigned from package `installation-reports' to `linux-2.6'. > found 436156 2.6.21-5 Bug#436156: installation-reports: Inst report TP35D2-A7 (SATA difficulties) Bug marked as found in version 2.6.21-5. > clone 436156 -1 Bug#436156: installation-reports: Inst report TP35D2-A7 (SATA difficulties) Bug 436156 cloned as bug 436270. > retitle -1 rtc module loaded instead of rtc-dev Bug#436270: installation-reports: Inst report TP35D2-A7 (SATA difficulties) Changed Bug title to `rtc module loaded instead of rtc-dev' from `installation-reports: Inst report TP35D2-A7 (SATA difficulties)'. > found -1 2.6.21-5 Bug#436270: rtc module loaded instead of rtc-dev Bug marked as found in version 2.6.21-5. > clone 436156 -2 Bug#436156: installation-reports: Inst report TP35D2-A7 (SATA difficulties) Bug 436156 cloned as bug 436271. > reassign -2 xserver-xorg Bug#436271: installation-reports: Inst report TP35D2-A7 (SATA difficulties) Bug reassigned from package `linux-2.6' to `xserver-xorg'. > retitle -2 PS/2 mouse not working Bug#436271: installation-reports: Inst report TP35D2-A7 (SATA difficulties) Changed Bug title to `PS/2 mouse not working' from `installation-reports: Inst report TP35D2-A7 (SATA difficulties)'. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#436267: linux-image-2.6.22-1-686: IEEE1394 modules unbuilt in packaged kernel
On Mon, Aug 06, 2007 at 01:32:15PM -0400, Curt Howland wrote: > > The IEEE1394 kernel drivers that have been built as modiles in prior > kernels have not been built with the kernel in the linux-image-2.6.22-1-686 > package. Having these modules available without compiling a custom > kernel has been very useful in the past, would it be possible to enable > the IEEE1394 as loadable modules again please? no they are the old firwire stack, that has been disabled due to security concern and general distrust. > Here is the entire "firewire" section from /boot/config-2.6.22-1-686 > > # IEEE 1394 (FireWire) support > # > CONFIG_FIREWIRE=m > CONFIG_FIREWIRE_OHCI=m > CONFIG_FIREWIRE_SBP2=m > # CONFIG_IEEE1394 is not set what are you missing in the yuyu stack? regards -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#436267: linux-image-2.6.22-1-686: IEEE1394 modules unbuilt in packaged kernel
Package: linux-image-2.6.22-1-686 Version: 2.6.22-3 Severity: wishlist The IEEE1394 kernel drivers that have been built as modiles in prior kernels have not been built with the kernel in the linux-image-2.6.22-1-686 package. Having these modules available without compiling a custom kernel has been very useful in the past, would it be possible to enable the IEEE1394 as loadable modules again please? Here is the entire "firewire" section from /boot/config-2.6.22-1-686 # IEEE 1394 (FireWire) support # CONFIG_FIREWIRE=m CONFIG_FIREWIRE_OHCI=m CONFIG_FIREWIRE_SBP2=m # CONFIG_IEEE1394 is not set -- Package-specific info: ** Version: Linux version 2.6.22-1-686 (Debian 2.6.22-3) ([EMAIL PROTECTED]) (gcc version 4.1.3 20070718 (prerelease) (Debian 4.1.2-14)) #1 SMP Sun Jul 29 14:37:42 UTC 2007 ** Tainted: PFSRMB ** Kernel log: cs: IO port probe 0xc00-0xcff: clean. cs: IO port probe 0xa00-0xaff: clean. MC'97 1 converters and GPIO not ready (0xff00) drivers/hid/usbhid/hid-core.c: usb_submit_urb(ctrl) failed drivers/hid/usbhid/hid-core.c: timeout initializing reports input: Logitech Logitech Attack 3 as /class/input/input4 input: USB HID v1.10 Joystick [Logitech Logitech Attack 3] on usb-:00:03.0-2 usbcore: registered new interface driver usbhid drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver Adding 1510068k swap on /dev/hda5. Priority:-1 extents:1 across:1510068k EXT3 FS on hda1, internal journal sonypi: Sony Programmable I/O Controller Driver v1.26. sonypi: please try the sony-laptop module instead and report failures, see also http://www.linux.it/~malattia/wiki/index.php/Sony_drivers sonypi: detected type2 model, verbose = 0, fnkeyinit = off, camera = off, compat = off, mask = 0x, useinput = on, acpi = on sonypi: enabled at irq=11, port1=0x1080, port2=0x1084 sonypi: device allocated minor is 63 input: Sony Vaio Jogdial as /class/input/input5 input: Sony Vaio Keys as /class/input/input6 device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised: [EMAIL PROTECTED] pcmcia: Detected deprecated PCMCIA ioctl usage from process: discover. pcmcia: This interface will soon be removed from the kernel; please expect breakage unless you upgrade to new tools. pcmcia: see http://www.kernel.org/pub/linux/utils/kernel/pcmcia/pcmcia.html for details. NET: Registered protocol family 10 lo: Disabled Privacy Extensions hda: selected mode 0x45 hdc: selected mode 0x42 ACPI: Battery Slot [BAT1] (battery present) ACPI: Battery Slot [BAT2] (battery absent) ACPI: AC Adapter [ACAD] (on-line) input: Lid Switch as /class/input/input7 ACPI: Lid Switch [LID] input: Power Button (CM) as /class/input/input8 ACPI: Power Button (CM) [PWRB] lp0: using parport0 (interrupt-driven). ppdev: user-space parallel port driver ath0: no IPv6 routers present powernow: This module only works with AMD K7 CPUs ACPI: PCI Interrupt :01:00.0[A] -> GSI 16 (level, low) -> IRQ 23 NVRM: loading NVIDIA UNIX x86 Kernel Module 100.14.11 Wed Jun 13 18:21:22 PDT 2007 agpgart: Found an AGP 3.0 compliant device at :00:00.0. agpgart: Putting AGP V3 device at :00:00.0 into 8x mode agpgart: SiS delay workaround: giving bridge time to recover. agpgart: Putting AGP V3 device at :01:00.0 into 8x mode sd 0:0:0:1: [sdb] 2001888 512-byte hardware sectors (1025 MB) sd 0:0:0:1: [sdb] Write Protect is off sd 0:0:0:1: [sdb] Mode Sense: 00 00 00 00 sd 0:0:0:1: [sdb] Assuming drive cache: write through sd 0:0:0:1: [sdb] 2001888 512-byte hardware sectors (1025 MB) sd 0:0:0:1: [sdb] Write Protect is off sd 0:0:0:1: [sdb] Mode Sense: 00 00 00 00 sd 0:0:0:1: [sdb] Assuming drive cache: write through sdb: sdb1 usb 4-1: USB disconnect, address 2 firewire_core: phy config: card 0, new root=ffc1, gap_count=5 firewire_core: phy config: card 0, new root=ffc1, gap_count=5 firewire_core: created new fw device fw1 (0 config rom retries) firewire_core: phy config: card 0, new root=ffc1, gap_count=5 firewire_core: phy config: card 0, new root=ffc1, gap_count=5 firewire_core: created new fw device fw1 (0 config rom retries) usb 2-2: new full speed USB device using ohci_hcd and address 2 usb 2-2: configuration #1 chosen from 1 choice scsi2 : SCSI emulation for USB Mass Storage devices usb-storage: device found at 2 usb-storage: waiting for device to settle before scanning drivers/usb/class/usblp.c: usblp0: USB Bidirectional printer dev 2 if 1 alt 0 proto 2 vid 0x03F0 pid 0x2911 usbcore: registered new interface driver usblp drivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver usb-storage: device scan complete scsi 2:0:0:0: Direct-Access HP psc 2210 1.00 PQ: 0 ANSI: 2 sd 2:0:0:0: [sda] Attached SCSI removable disk drivers/usb/class/usblp.c: usblp0: removed usb 2-2: USB disconnect, address 2 firewire_core: phy config: card 0, new root=ffc1, gap_count=5 firewire_core: phy config: card 0, new root=ffc1, gap_count=5 firewire_core: created new fw device fw1 (0 config rom retries) firewire_core: phy config: card 0, new root=ffc
Bug#436260: linux-support-2.6.22-1: Support for exernal module packages broken
Package: linux-support-2.6.22-1 Version: 2.6.22-3 Severity: important Attempting to build a module module package such as linux-modules-extra-2.6 which uses gencontrol.py fails even when using the copy of gencontrol.py included in the package as /usr/src/linux-support-2.6.22-1/modules/gencontrol.py since the interface provided by lib/python/debian_linux has changed but gencontrol.py has not been updated to match the new interface. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: powerpc (ppc) Kernel: Linux 2.6.22-1-powerpc Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages linux-support-2.6.22-1 depends on: ii python2.4-minimal 2.4.4-5A minimal subset of the Python lan linux-support-2.6.22-1 recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#365770: marked as done ([inux-image-2.6.16-1-686] Kernel panic after update)
Your message dated Mon, 6 Aug 2007 17:13:53 +0200 with message-id <[EMAIL PROTECTED]> and subject line [inux-image-2.6.16-1-686] Kernel panic after update has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: linux-image-2.6.16-1-686 Version: 2.6.16-10 Severity: grave After updating the linux-image (from 2.6.16-8 ?) on one of my systems (PIII 700) the system do not boot anymore (rescue kernel still works), and stops with a kernel panic message. Sorry, I haven´t more information, I´ve no information on the screen, but the grub menu is available and working. After selecting the kernel, I´ve got only a black screen and nothing is happen anymore. --- End Message --- --- Begin Message --- looks like an old initrafms-tools failure closing. -- maks --- End Message ---
Bug#378487: marked as done (linux-2.6: kernel-2.6.17-3 on a P-IV locks up the machine: problem with 'drm:i830')
Your message dated Mon, 6 Aug 2007 18:13:34 +0200 with message-id <[EMAIL PROTECTED]> and subject line linux-2.6: kernel-2.6.17-3 on a P-IV locks up the machine: problem with 'drm:i830' has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: linux-2.6 Version: 2.6.17-3 Severity: critical Justification: breaks the whole system I have downloaded the kernel source linux-2.6_2.6.17.orig.tar.gz, linux-2.6_2.6.17-3.diff.gz and linux-2.6_2.6.17-3.dsc from Debian Unstable, and used 'dpkg-source -x linux-2.6_2.6.17-3.dsc' which unpacks the source and applied the patches in a source directory. Then I used 'make-kpkg' to compile the kernel and installed it. However, when I try running 'stellarium 0.8.0-2' which is compiled from source taken from 'Debian Testing', the system almost entirely locks up after a while of using it. The mouse Cursor vanishes. Standard keystrokes like 'ctrl-alt-backspace' or 'ctrl-alt-F1' to reach Console fails. However 'SYSrq' keys works, and the 'Powerbutton' can also signal 'init' to make a clean shutdown. The reason of the problem appears to be what I find in the kernel log. -- Jul 16 19:17:07 localhost kernel: [17183280.92] [drm:i830_wait_ring] *ERROR* space: 119528 wanted 131064 Jul 16 19:17:07 localhost kernel: [17183280.92] [drm:i830_wait_ring] *ERROR* lockup Jul 16 19:17:30 localhost kernel: [17183303.92] [drm:i830_wait_ring] *ERROR* space: 119384 wanted 131064 Jul 16 19:17:30 localhost kernel: [17183303.92] [drm:i830_wait_ring] *ERROR* lockup --- It appears that the kernel is locks up the machine. I have faced the same problem a few days back with kernel-2.6.16.1 compiled from source taken from 'kernel.org' site. Since this is an error which makes the Pentium IV unusable till rebooted, I am filling an RC bug report against this kernel. -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.6.17 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) # # Automatically generated make config: don't edit # Linux kernel version: 2.6.17 # Sun Jul 16 17:23:54 2006 # CONFIG_X86_32=y CONFIG_SEMAPHORE_SLEEPERS=y CONFIG_X86=y CONFIG_MMU=y CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_IOMAP=y CONFIG_GENERIC_HWEIGHT=y CONFIG_ARCH_MAY_HAVE_PC_FDC=y CONFIG_DMI=y # # Code maturity level options # CONFIG_EXPERIMENTAL=y CONFIG_BROKEN_ON_SMP=y CONFIG_INIT_ENV_ARG_LIMIT=32 # # General setup # CONFIG_LOCALVERSION="" CONFIG_LOCALVERSION_AUTO=y CONFIG_SWAP=y CONFIG_SYSVIPC=y # CONFIG_POSIX_MQUEUE is not set CONFIG_BSD_PROCESS_ACCT=y # CONFIG_BSD_PROCESS_ACCT_V3 is not set CONFIG_SYSCTL=y # CONFIG_AUDIT is not set CONFIG_IKCONFIG=y CONFIG_IKCONFIG_PROC=y CONFIG_RELAY=y CONFIG_INITRAMFS_SOURCE="" CONFIG_UID16=y CONFIG_VM86=y CONFIG_CC_OPTIMIZE_FOR_SIZE=y CONFIG_EMBEDDED=y # CONFIG_KALLSYMS is not set CONFIG_HOTPLUG=y CONFIG_PRINTK=y CONFIG_BUG=y CONFIG_ELF_CORE=y CONFIG_BASE_FULL=y CONFIG_FUTEX=y CONFIG_EPOLL=y CONFIG_SHMEM=y CONFIG_SLAB=y # CONFIG_TINY_SHMEM is not set CONFIG_BASE_SMALL=0 # CONFIG_SLOB is not set CONFIG_OBSOLETE_INTERMODULE=m # # Loadable module support # CONFIG_MODULES=y CONFIG_MODULE_UNLOAD=y # CONFIG_MODULE_FORCE_UNLOAD is not set CONFIG_MODVERSIONS=y # CONFIG_MODULE_SRCVERSION_ALL is not set CONFIG_KMOD=y # # Block layer # # CONFIG_LBD is not set # CONFIG_BLK_DEV_IO_TRACE is not set # CONFIG_LSF is not set # # IO Schedulers # CONFIG_IOSCHED_NOOP=y CONFIG_IOSCHED_AS=m CONFIG_IOSCHED_DEADLINE=y CONFIG_IOSCHED_CFQ=m # CONFIG_DEFAULT_AS is not set CONFIG_DEFAULT_DEADLINE=y # CONFIG_DEFAULT_CFQ is not set # CONFIG_DEFAULT_NOOP is not set CONFIG_DEFAULT_IOSCHED="deadline" # # Processor type and features # # CONFIG_SMP is not set CONFIG_X86_PC=y # CONFIG_X86_ELAN is not set # CONFIG_X86_VOYAGER is not set # CONFIG_X86_NUMAQ is not set # CONFIG_X86_SUMMIT is not set # CONFIG_X86_BIGSMP is not set # CONFIG_X86_VISWS is not set # CONFIG_X86_GENERICARCH is not set # CONFIG_X86_ES7000 is not set # CONFIG_M386 is not set # CONFIG_M486 is not set # CONFIG_M586 is not set # CONFIG_M586TSC is not set # CONFIG_M586MMX is not set # CONFIG_M686 is not set # CONFIG_MPENTIUMII is not set # CONFIG_MPENTIUMIII is not set # CONFIG_MPENTIUMM is not set CONFIG_MPENTIUM4=y # CONFIG_MK6 is not set # CONFIG_MK7 is not set # CONFIG_MK8 is not set # CONFIG_MCRUSOE is not set # CONFIG_MEFFICEON is not set # CONFIG_MWINCHIPC6 is not set # CONFIG_MWINCHIP2 is not set # CONFIG_MWINCHIP3D is not set # CONFIG_MGEODEGX1 is not set # CONFIG_MGEODE_LX is not set # CONFIG_MCYRIXIII
Bug#378487: linux-2.6: kernel-2.6.17-3 on a P-IV locks up the machine: problem with 'drm:i830'
Hi, Thanks for your mail. I have not found any such problem after upgrading to Etch. Etch kernel ran fine for a few days I used. I am running unmodified stock kernel 2.6.20.10 for more than 2 months, and the system never locked up in this time. Therefore, you can close the bug from Etch onwards. Xorg uses 'i915' as the kernel module, whereas the older XFree86 used i830. Therefore, it is possible that the i830 kernel module was causing the problem. Subhashis On Mon, 6 Aug 2007, maximilian attems wrote: tags 378487 moreinfo stop any update of that trouble on the etch kernel or on latest backports / testing / unstable? thanks for feedback. -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#352768: marked as done (ps2 mouse detection depends on modules loading order)
Your message dated Mon, 6 Aug 2007 17:32:32 +0200 with message-id <[EMAIL PROTECTED]> and subject line ps2 mouse detection depends on modules loading order has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: udev Version: 0.084-3 Severity: grave Justification: renders package unusable When I try to upgrade my system replacing hotplug by udev the mouse does not seem to be recognized. This happens with both the 2.6.12 and the 2.6.15 kernels. I am running an amd64 system on the same machine (separate boot) and there is no problem with udev so this is not hardware related. The psmouse module seems to be installed and manually (re)installing it with modprobe does not help. Syslog gives me these messages: Syslog of 2.6.15 Etch 2.6.15-1-686 udev version: 0.084-3 Feb 12 14:25:22 localhost kernel: mice: PS/2 mouse device common for all mice NOTE: using the 2.6.12-1-686 gives the same result. On the amd64 system I get this: Syslog of amd64 Sid 2.6.15-1-amd64-k8 udev version: 0.084-3 Feb 13 10:31:24 Attila kernel: mice: PS/2 mouse device common for all mice ... Feb 13 10:31:24 Attila kernel: input: Logitech USB-PS/2 Optical Mouse as /class/input/input1 Feb 13 10:31:24 Attila kernel: input: USB HID v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb-:00:10.0-2 You can see that amd64 finds the Logitech USB-PS/2 mouse but the 32bit system, whether 2.6.12 or 2.6.15 does not. I have no problems with hotplug; only when I try to switch to udev I get messages during bootup from udev: Starting the hotplug events dispatches... Synthesizing the intial hotplug events...mice: PS/2 mouse device for all mice Waiting for /dev to be fully populated...done And that's it. It never finds my Logitech mouse. I'm happy to send you any further info you may require and yes, I do purge the hotplug package. Any help much appreciated. This is driving me crazy. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (650, 'testing'), (600, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.12-1-686 Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) (ignored: LC_ALL set to en_GB) Versions of packages udev depends on: ii initscripts 2.86.ds1-4 Standard scripts needed for bootin ii libc6 2.3.5-13 GNU C Library: Shared libraries an ii libselinux1 1.28-2 SELinux shared libraries ii lsb-base 3.0-15 Linux Standard Base 3.0 init scrip ii makedev 2.3.1-80 creates device files in /dev ii sed 4.1.4-5The GNU sed stream editor udev recommends no packages. -- Jonathan Kaye Carrer de Fontajau 32-34 1r 3a 17007 GIRONA Catalunya Tel: +34 972 22 82 50 __ LLama Gratis a cualquier PC del Mundo. Llamadas a fijos y móviles desde 1 céntimo por minuto. http://es.voice.yahoo.com --- End Message --- --- Begin Message --- On Mon, Aug 06, 2007 at 05:21:38PM +0200, Jonathan Kaye wrote: > > I think you sent this to the wrong person. > > -- > Jonathan Kaye bug reporter thinks is wrongly pinged. closing also as it is not very likely that this old bug still persists. -- maks --- End Message ---
Bug#314774: marked as done (newvserver failed during debootstrap because of jfs issue)
Your message dated Mon, 6 Aug 2007 17:12:28 +0200 with message-id <[EMAIL PROTECTED]> and subject line vserver failed during debootstrap because of jfs issue has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: vserver-debiantools Version: 0.1.10 Severity: important = Errors were encountered while processing: /var/cache/apt/archives/console-tools_1%3a0.2.3dbs-56_i386.deb W: Failure while installing base packages. This will be re-attempted up to five times. = I have no idea why this error occurs but it fails. I don't know how to tell debootstrap in this case to report more info of what happened. -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.4.31-xbox-chimpanzee-vs-ll Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages vserver-debiantools depends on: ii binutils2.15-6 The GNU assembler, linker and bina ii debootstrap 0.2.45-0.2 Bootstrap a basic Debian system ii rsync 2.6.4-6 fast remote file copy program (lik ii util-vserver0.30.204-5sarge2 tools for Virtual private servers -- no debconf information --- End Message --- --- Begin Message --- > I am sorry that I no longer use vserver. Please close > it or may be make it with a lower severity. closing -- maks --- End Message ---
Processed: Re: ps2 mouse detection depends on modules loading order
Processing commands for [EMAIL PROTECTED]: > tags 352768 moreinfo Bug#352768: ps2 mouse detection depends on modules loading order Tags were: moreinfo unreproducible Tags added: moreinfo > stop Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#402946: moreinfo - what?
On Tue, 23 Jan 2007, Klaus Schneider wrote: > What additional information do you need? I thought that I provided > the "moreinfo" you requested in my last mail, am I wrong? > > Thanks, > Klaus tests against newer kernel. also if none works a git bisect between 2.6.17 and 2.6.18 thanks for your feedback. -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#352768: ps2 mouse detection depends on modules loading order
tags 352768 moreinfo stop > I'd be happy to give someone, anyone, all the information you require. > If you let me know what you need to see I'll send it to you at once. Not > being able to install udev is holding up my system. I'm still stuck with > the 2.6.12 kernel because of this. test against a recent kernel and report back. thanks -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#357533: marked as done (linux-image-2.6.15-1-k7: nforce4 driver (network, sata, usb2 ) don't work with 2.6.15-k7-4)
Your message dated Mon, 6 Aug 2007 17:08:08 +0200 with message-id <[EMAIL PROTECTED]> and subject line linux-image-2.6.15-1-k7: nforce4 driver (network, sata, usb2 ) don't work with 2.6.15-k7-4 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: linux-image-2.6.15-1-k7 Version: 2.6.15-4 Severity: important After testing kernel update (2.6.12 to 2.6.15) network module (forcedepth) sata and usb2 don't work anymore I have a nvidia nforce4 chipset. Thanks dmesg : ... PCI: Setting latency timer of device :00:0a.0 to 64 forcedeth: Couldn't find register window for device :00:0a.0. ACPI: PCI interrupt for device :00:0a.0 disabled forcedeth: probe of :00:0a.0 failed with error -22 sata_sil :05:0a.0: version 0.9 ACPI: PCI Interrupt Link [APC4] BIOS reported IRQ 3, using IRQ 19 ACPI: PCI Interrupt Link [APC4] enabled at IRQ 19 ACPI: PCI Interrupt :05:0a.0[A] -> Link [APC4] -> GSI 19 (level, low) -> IRQ 50 ACPI: PCI interrupt for device :05:0a.0 disabled sata_sil: probe of :05:0a.0 failed with error -12 ... -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.12-1-386 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages linux-image-2.6.15-1-k7 depends on: ii initramfs-tools [linux-initra 0.51 tools for generating an initramfs ii module-init-tools 3.2.2-1tools for managing Linux kernel mo Versions of packages linux-image-2.6.15-1-k7 recommends: ii libc6-i6862.3.5-13 GNU C Library: Shared libraries [i -- debconf information excluded --- End Message --- --- Begin Message --- very old kernel. no reply since initial bug report to any request. thus closing -- maks --- End Message ---
Bug#403733: marked as done (kernel hangs when creating more than one lvm snapshot of the same logical volume)
Your message dated Mon, 6 Aug 2007 17:01:09 +0200 with message-id <[EMAIL PROTECTED]> and subject line kernel hangs when creating more than one lvm snapshot of the same logical volume has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: base Severity: critical If you create more than one lvm snaptshot of a logical volume the system hangs. To reproduce this problem use lvcreate to create a logical volume and try to create two snapshots of this lv. When invoking the second lvcreate the system should hang. This behavior can be found in some other distros (debian sarge with 2.6, ubuntu, gentoo) but not in rhel or suse. I think this bug is release critical as it is a regression to debian sarge with linux-2.4. -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-2-686 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) --- End Message --- --- Begin Message --- > I found a solution to "fix" the bug. We are using a xfs filesystem in > the logical volumes. The script we used to test made an xfs_freeze just > before snapshotting. This caused an race condition in the kernel, > because it tries to make a freeze while creating the snapshot. Without > doing xfs_freeze everything works almost well. closing xfs and lvm tradionaly badly mix, the situation seems to have improved in the latest kernels. -- maks --- End Message ---
Bug#408636: marked as done (linux-image: SCSI drives inaccessible to parted or any installation tool)
Your message dated Mon, 6 Aug 2007 16:58:55 +0200 with message-id <[EMAIL PROTECTED]> and subject line linux-image: SCSI drives inaccessible to parted or any installation tool has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: linux-image Severity: grave Justification: renders package unusable *** Please type your report below this line *** On an older Asus K7V server with a PCI Buslogic BT-958 SCSI card, the Ubuntu Feisty Fawn Herd 2 Live CD's kernel fails to properly load the BusLogic module to enable mounting or configuration of any SCSI drives attached to the card. In contrast, Mandriva 2007 Free and Knoppix 4 & 5 all work properly with the SCSI controller and disks. This has been a problem with both Ubuntu and Debian for the past 2 years (Dapper, Edgy, Feisty; SID, and pre-SID unstable). Mandriva has worked with this card and drives since at least Mandrake 9.0. But since moving to Ubuntu on other boxes, I'm very eager to move this box to Ubuntu too. SuSE's 10.x Live CD also fails to see these drives properly. From what I've been able to research, other reports point to the BusLogic module only working correctly when it's built into the kernel, rather than being loaded as a loadable external module. As provided with Ubuntu, the SCSI bus seems to be reset at least twice by the kernel during startup, and I'm not sure I see this with Mandriva or Knoppix. The KDE Control Center's Disk & Filesystem settings shows two 18Gb SCSI disks, MAG3182MP and DNES-318350W, which are detected by Ubuntu - but fail to show partitions. They appear as sdb and sdc. These disks have partitions in common formats, but Ubuntu kernel can't see them. "cfdisk /dev/sdb" and QTparted (and Gparted) are unable to operate on the disks for formatting or partitioning in any way. This is not a sudo issue. -- System Information: Debian Release: testing/unstable APT prefers edgy-updates APT policy: (500, 'edgy-updates'), (500, 'edgy-security'), (500, 'edgy') Architecture: i386 (x86) Shell: /bin/sh linked to /bin/dash Kernel: Linux 2.6.17-10-generic Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) --- End Message --- --- Begin Message --- no dmesg provided nor any futher requested info please test against latest testing images and if those don't work reholler. -- maks --- End Message ---
Processed: Re: image built from linux-source-2..6.21 can not be booted up
Processing commands for [EMAIL PROTECTED]: > tags 430393 moreinfo Bug#430393: image built from linux-source-2..6.21 can not be booted up There were no tags set. Tags added: moreinfo > stop Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#430393: image built from linux-source-2..6.21 can not be booted up
tags 430393 moreinfo stop you didn't respond to the following questions: a) rootdelay boot param usage b) http://wiki.debian.org/InitramfsDebug currently this bug report contains zero info beside home build kernel and may thus be closed unless info to aboves questions comes up. thanks for feedback -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#428337: marked as done (gnome: 3.5" floppy with vfat FS not being recognized)
Your message dated Mon, 6 Aug 2007 16:32:40 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#428337: gnome: 3.5" floppy with vfat FS not being recognized has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: gnome Version: 1:2.14.3.6 Severity: normal Steps to reproduce: 1) Insert floppy with vfat file system 2) #modprobe floppy 3) Go to Computer 4) Click or double click the floppy icon 5) See a message that it couldn't be mounted, because of unknown FS. There probably is some way to determine the FS by inspecting some magic constants. It could at least try vfat and ext2 if that's not possible. mount -t vfat /dev/fd0 does work -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.18-4-k7 (SMP w/1 CPU core) Locale: LANG=nl_NL.UTF-8, LC_CTYPE=nl_NL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages gnome depends on: ii gdm-themes 0.5.1Themes for the GNOME Display Manag ii gnome-cups-manager 0.31-3 CUPS printer admin tool for GNOME ii gnome-desktop-environment 1:2.14.3.6 The GNOME Desktop Environment ii gnome-games-extra-data 2.18.0-2 games for the GNOME desktop (extra ii gnome-office1:2.14.3.6 The GNOME Office suite ii gnome-themes-extras 0.9.0.deb0.2 various themes for the GNOME 2 des ii rhythmbox 0.10.0-3 music player and organizer for GNO ii synaptic0.57.11.1+b2 Graphical package manager ii totem-mozilla 2.16.6-1 Totem Mozilla plugin ii xscreensaver4.24-5 Automatic screensaver for X gnome recommends no packages. -- no debconf information --- End Message --- --- Begin Message --- On Mon, 11 Jun 2007, Josselin Mouette wrote: > > Version: 1:2.14.3.6 > > Severity: normal > > > > Steps to reproduce: > > > > 1) Insert floppy with vfat file system > > 2) #modprobe floppy > > 3) Go to Computer > > 4) Click or double click the floppy icon > > 5) See a message that it couldn't be mounted, because of unknown FS. > > > > There probably is some way to determine the FS by inspecting some magic > > constants. It could at least try vfat and ext2 if that's not possible. > > > > mount -t vfat /dev/fd0 does work i don'T see a kernel bug if the mount happens to work, closing as gnome maintainer sees no necessity to work on. regards -- maks --- End Message ---
Re: Bug#425851: linux-image-2.6.21-1-686: 2.6.21 doesn't find HDD in VMware Workstation (2.6.20 did)
Olaf van der Spek-2 wrote: > > I've installed 2.6.21 on two different VMware Workstation guests running > on two different hosts and both fail to boot. > > They wait for a long time at "Begin: Waiting for root file system... ..." > Then it says: > ALERT! /dev/sha1 does not exist. Dropping to a shell! > There is a bug in the LSI driver/VMware emulation in kernel 2.6.21 & 2.6.22. You can use the BusLogic driver, but you need to update the OS to load the kernel module. VMware Linux guest kernel panics on boot with LSI Logic HBA and kernel 2.6.21-2.6.22 http://theether.net/kb/100038 Cheers. -- View this message in context: http://www.nabble.com/Bug-425851%3A-linux-image-2.6.21-1-686%3A-2.6.21-doesn%27t-find-HDD-in-VMware-Workstation-%282.6.20-did%29-tf3810538.html#a12017460 Sent from the debian-kernel mailing list archive at Nabble.com. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#428615: linux-image-2.6.20-1-amd64: ACPI procfs thermal and fan directories are empty on an ASUS P5B-VM motherboard
hello, On Wed, 13 Jun 2007, Francesco Poli wrote: > Package: linux-image-2.6.20-1-amd64 > Version: 2.6.20-3 > Severity: normal > > Hi! > > It seems I'm not able to read ACPI temperature or fan data on a box with > an ASUS P5B-VM motherboard. I think the appropriate modules are loaded > (see below: thermal and fan), but, nonetheless: > > $ ls -altrF /proc/acpi/thermal_zone/ > total 0 > dr-xr-xr-x 10 root root 0 2007-06-10 16:21 ../ > dr-xr-xr-x 2 root root 0 2007-06-10 23:00 ./ > $ ls -altrF /proc/acpi/fan/ > total 0 > dr-xr-xr-x 10 root root 0 2007-06-10 16:21 ../ > dr-xr-xr-x 2 root root 0 2007-06-10 23:00 ./ > > What's wrong? > What did I fail to understand? please test against newer kernel, at least 2.6.22 from unstable installs just fine on testing or even better 2.6.23-rc2 from trunk -> http://wiki.debian.org/DebianKernel if still reproducible acpi upstream needs to get poked. sunny greetings -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#430941: linux-image-2.6.21-2-686: no-name USB 2.0 flash drive gets "unknown partition table" until BLKRRPART ioctl is issued
Processing commands for [EMAIL PROTECTED]: > tags 430941 moreinfo Bug#430941: linux-image-2.6.21-2-686: no-name USB 2.0 flash drive gets "unknown partition table" until BLKRRPART ioctl is issued There were no tags set. Tags added: moreinfo > stop Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#430941: linux-image-2.6.21-2-686: no-name USB 2.0 flash drive gets "unknown partition table" until BLKRRPART ioctl is issued
tags 430941 moreinfo stop On Thu, 28 Jun 2007, Simon McVittie wrote: > I have a cheap USB stick (an Integral 512M USB2.0 stick, specifically) > which appears with "unknown partition table" when inserted. If the > BLKRRPART ioctl is issued, the partition table is re-read correctly, > /dev/sdx1 appears, HAL activates and the stick is auto-mounted correctly. > > Repartitioning the stick appears to work, but only because fdisk issues > the ioctl to re-read the partition table after it's been modified - when > the stick is removed and re-plugged, the same issue occurs. Issuing the > ioctl without actually changing anything (sfdisk -R) is sufficient to > fix it. could you test against newer kernel from unstable 2.6.22. it installs just fine and if still reproducible trunk see apt lines -> http://wiki.debian.org/DebianKernel thanks -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#362851: linux-2.6: sis ide controller 5513 detects and uses wrong udma modes
tags 362851 moreinfo stop could you please retest against etch kernel? thanks for feedback -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#314707: UDMA3/4/5 not working with Centrino Chipset, 82801DBM (ICH4-M) IDE Controller (rev 03)
tags 314707 moreinfo stop is the matter fixed in etch? if not please test the latest kernel from backports.org!? thanks for feedback -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: found 431311 in 2.6.22-1
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.10.6 > found 431311 2.6.22-1 Bug#431311: ICE1724 sound device does not work properly Bug marked as found in version 2.6.22-1. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#369150: marked as done (linux-image-2.6.16-1-k7: oops while writing to a reiserfs partition)
Your message dated Mon, 6 Aug 2007 15:09:40 +0200 with message-id <[EMAIL PROTECTED]> and subject line linux-image-2.6.16-1-k7: oops while writing to a reiserfs partition has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: linux-image-2.6.16-1-k7 Version: 2.6.16-12 Severity: normal Hi, I just experienced an oops while writing to a reiserfs partition. The partition was newly created with current reiserfsprogs (1:3.6.19-2), is about 64GB large and had a block size of 512 bytes. The oops information from kern.log is attached. Andreas -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (900, 'testing'), (900, 'stable'), (600, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-1-k7 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages linux-image-2.6.16-1-k7 depends on: ii module-init-tools 3.2.2-2tools for managing Linux kernel mo ii yaird [linux-initramfs-tool] 0.0.12-9 Yet Another mkInitRD Versions of packages linux-image-2.6.16-1-k7 recommends: ii libc6-i6862.3.6-7GNU C Library: Shared libraries [i -- debconf information: linux-image-2.6.16-1-k7/preinst/initrd-2.6.16-1-k7: linux-image-2.6.16-1-k7/preinst/lilo-initrd-2.6.16-1-k7: true linux-image-2.6.16-1-k7/preinst/abort-overwrite-2.6.16-1-k7: linux-image-2.6.16-1-k7/postinst/depmod-error-2.6.16-1-k7: false linux-image-2.6.16-1-k7/preinst/elilo-initrd-2.6.16-1-k7: true linux-image-2.6.16-1-k7/preinst/lilo-has-ramdisk: linux-image-2.6.16-1-k7/prerm/removing-running-kernel-2.6.16-1-k7: true * linux-image-2.6.16-1-k7/preinst/overwriting-modules-2.6.16-1-k7: false linux-image-2.6.16-1-k7/postinst/old-system-map-link-2.6.16-1-k7: true linux-image-2.6.16-1-k7/preinst/failed-to-move-modules-2.6.16-1-k7: linux-image-2.6.16-1-k7/preinst/abort-install-2.6.16-1-k7: linux-image-2.6.16-1-k7/postinst/bootloader-test-error-2.6.16-1-k7: linux-image-2.6.16-1-k7/postinst/bootloader-error-2.6.16-1-k7: linux-image-2.6.16-1-k7/preinst/bootloader-initrd-2.6.16-1-k7: true linux-image-2.6.16-1-k7/postinst/kimage-is-a-directory: linux-image-2.6.16-1-k7/postinst/old-initrd-link-2.6.16-1-k7: true linux-image-2.6.16-1-k7/prerm/would-invalidate-boot-loader-2.6.16-1-k7: true * linux-image-2.6.16-1-k7/preinst/already-running-this-2.6.16-1-k7: linux-image-2.6.16-1-k7/postinst/depmod-error-initrd-2.6.16-1-k7: false linux-image-2.6.16-1-k7/postinst/old-dir-initrd-link-2.6.16-1-k7: true linux-image-2.6.16-1-k7/postinst/create-kimage-link-2.6.16-1-k7: true May 27 19:28:35 palantir kernel: Unable to handle kernel paging request at virtual address 41186508 May 27 19:28:35 palantir kernel: printing eip: May 27 19:28:35 palantir kernel: b01a3e42 May 27 19:28:35 palantir kernel: *pde = May 27 19:28:35 palantir kernel: Oops: [#1] May 27 19:28:35 palantir kernel: Modules linked in: nfsd exportfs lockd nfs_acl sunrpc cls_u32 sch_ingress xt_length ipt_tos xt_MARK iptable_mangle cls_fw sch_sfq sch_htb thermal fan button processor ac battery ipt_MASQUERADE ipt_REJECT xt_tcpudp xt_state ipt_LOG iptable_filter ip_nat_ftp iptable_nat ip_nat ip_conntrack_irc ip_conntrack_ftp ip_conntrack nfnetlink ip_tables x_tables ppp_deflate zlib_deflate bsd_comp ppp_async crc_ccitt ppp_generic slhc it87 hwmon_vid eeprom i2c_isa i2c_dev reiserfs evdev snd_intel8x0 snd_ac97_codec snd_ac97_bus snd_pcm_oss snd_mixer_oss snd_pcm snd_timer snd i2c_sis630 uhci_hcd ehci_hcd 8139too ohci_hcd i2c_core pcspkr parport_pc parport sis_agp agpgart rtc sis900 soundcore mii usbcore snd_page_alloc ext3 jbd mbcache ide_disk generic sis5513 ide_core May 27 19:28:35 palantir kernel: CPU:0 May 27 19:28:35 palantir kernel: EIP:0060:[_mmx_memcpy+104/292]Not tainted VLI May 27 19:28:35 palantir kernel: EFLAGS: 00210212 (2.6.16-1-k7 #2) May 27 19:28:35 palantir kernel: EIP is at _mmx_memcpy+0x68/0x124 May 27 19:28:35 palantir kernel: eax: b5db4000 ebx: 0215b884 ecx: b1c1f9f8 edx: 36efa940 May 27 19:28:35 palantir kernel: esi: 41186508 edi: b1818818 ebp: 856e2128 esp: b5db5950 May 27 19:28:35 palantir kernel: ds: 007b es: 007b ss: 0068 May 27 19:28:35 palantir kernel: Process tar (pid: 19467, threadinfo=b5db4000 task=c4c1dab0) May 27 19:28:35 palantir kernel: Stack: <0>b1818818 41186508 856e2128 c8abecd4 b1818818 41186508 856e2128 May 27 19:28:35 palantir kernel:b5db5b68 b1c1f9f8 b5db59d4 b1818800 b33bba60 00
Processed: bug 431311 is forwarded to https://bugtrack.alsa-project.org/alsa-bug/view.php?id=3093
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.10.6 > forwarded 431311 https://bugtrack.alsa-project.org/alsa-bug/view.php?id=3093 Bug#431311: ICE1724 sound device does not work properly Noted your statement that Bug has been forwarded to https://bugtrack.alsa-project.org/alsa-bug/view.php?id=3093. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#361150: marked as done (Kernel install process contains a time window that can lead to an unusable system)
Your message dated Mon, 6 Aug 2007 14:53:04 +0200 with message-id <[EMAIL PROTECTED]> and subject line Kernel install process contains a time window that can lead to an unusable system has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: linux-2.6 Severity: normal This is about the kernel image installation process (all linux-image-*) There is a critical time window during install that occurs if - multiple packages are being installed at once (for exemple during "apt-get upgrade") - *AND* the same kernel is being updated during which time, an interruption of the installation process can lead to a non-bootable system (non coherent kernel/modules combination, invalid kernel map for bootloader, etc..) The installation procedure first unpacks and replaces the actual running kernel. If anything happens during that time several bad things can happen : - The initrd image (if needed) is not built - The bootloader is not updated to reflect the disk location map of the new kernel (lilo ?) Unfortunatelly, this can happen very easily if one of the package that is loaded during an 'apt-get upgrade' happens to fail to install (recent exemple : manpages-dev and modutils conflict over a single file). However, this can also occur for other various reasons (power outtage, CTRL-C, etc..) The, hmmm.. solution (?) - would be to actually *install* the new kernel ONLY when all steps have been taken to ensure that the system is ready (or about ready) to boot that kernel (read : initrd is ready).. There is probably also a problem with /lib/modules.. I believe the solution here is to unload the /lib/modules somewhere else, chroot to create the initrd, and mv the right /lib/modules/XXX just before finishing linux-image package installation setup. It is possible the previously mentioned solutions are not applicable to the way dpkg/apt work. But I am not familiar enough with the debian install procedures to tell whether this is the case or not. It may also be impossible to completelly remove any critical time window (eg: lilo update needs everything to be in place first) - but at least it could be reduced to encompass only a single installation step. If it is believed this report belongs to another place (apt, dpkg, etc..) please don't hesitate to say so - I'll report wherever it is necessary. Finally - the workaround is usually to boot from a rescue medium (or another kernel if feasable) and restart the installation process - until the kernel is 'setup' properly. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: powerpc (ppc64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-1-vserver-powerpc64 --- End Message --- --- Begin Message --- Package: linux-2.6 aboves statement is true for the installation of several core packages, yes that sounds like a bad excuse. but i don't see an easy way currently to fix your report. it is highly recommended to keep a second kernel around, this is also the default on newer abi. also grub doesn't need to know the direct block nr thus is a safe default. closing as the proposed chroot solution introduces higher complexity, we will see what we can do in dkt. best regards -- maks --- End Message ---
Processed: linux-2.6: sis ide controller 5513 detects and uses wrong udma modes
Processing commands for [EMAIL PROTECTED]: > tags 362851 moreinfo Bug#362851: linux-2.6: sis ide controller 5513 detects and uses wrong udma modes There were no tags set. Tags added: moreinfo > stop Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#366387: marked as done (linux-image-2.6.16-1-686-smp 2.6.16-12 makes e1000 behave erratic)
Your message dated Mon, 6 Aug 2007 15:10:24 +0200 with message-id <[EMAIL PROTECTED]> and subject line linux-image-2.6.16-1-686-smp 2.6.16-12 makes e1000 behave erratic has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: linux-image-2.6.16-1-686-smp Version: 2.6.16-12 Severity: normal After upgrading from 2.6.16-11 to 2.6.16-12, my LAN-connection started exhibiting erratic ping fluctiations, my default gateway jumped between 0 and 1000ms ping-times. Downgrade to 2.6.16-11 solved this problem. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-1-686-smp Locale: LANG=en_DK.ISO-8859-15, LC_CTYPE=en_DK.ISO-8859-15 (charmap=ISO-8859-15) Versions of packages linux-image-2.6.16-1-686-smp depends on: ii initramfs-tools [linux-initra 0.60 tools for generating an initramfs ii module-init-tools 3.2.2-2tools for managing Linux kernel mo Versions of packages linux-image-2.6.16-1-686-smp recommends: ii libc6-i6862.3.6-7GNU C Library: Shared libraries [i -- debconf information: linux-image-2.6.16-1-686-smp/postinst/kimage-is-a-directory: linux-image-2.6.16-1-686-smp/prerm/would-invalidate-boot-loader-2.6.16-1-686-smp: true linux-image-2.6.16-1-686-smp/postinst/old-system-map-link-2.6.16-1-686-smp: true * linux-image-2.6.16-1-686-smp/preinst/already-running-this-2.6.16-1-686-smp: linux-image-2.6.16-1-686-smp/preinst/bootloader-initrd-2.6.16-1-686-smp: true linux-image-2.6.16-1-686-smp/preinst/failed-to-move-modules-2.6.16-1-686-smp: linux-image-2.6.16-1-686-smp/postinst/depmod-error-initrd-2.6.16-1-686-smp: false linux-image-2.6.16-1-686-smp/preinst/overwriting-modules-2.6.16-1-686-smp: true linux-image-2.6.16-1-686-smp/postinst/old-dir-initrd-link-2.6.16-1-686-smp: true linux-image-2.6.16-1-686-smp/postinst/depmod-error-2.6.16-1-686-smp: false linux-image-2.6.16-1-686-smp/preinst/abort-install-2.6.16-1-686-smp: linux-image-2.6.16-1-686-smp/postinst/create-kimage-link-2.6.16-1-686-smp: true linux-image-2.6.16-1-686-smp/postinst/old-initrd-link-2.6.16-1-686-smp: true linux-image-2.6.16-1-686-smp/preinst/lilo-initrd-2.6.16-1-686-smp: true linux-image-2.6.16-1-686-smp/preinst/elilo-initrd-2.6.16-1-686-smp: true linux-image-2.6.16-1-686-smp/preinst/initrd-2.6.16-1-686-smp: linux-image-2.6.16-1-686-smp/preinst/lilo-has-ramdisk: linux-image-2.6.16-1-686-smp/postinst/bootloader-test-error-2.6.16-1-686-smp: linux-image-2.6.16-1-686-smp/postinst/bootloader-error-2.6.16-1-686-smp: linux-image-2.6.16-1-686-smp/preinst/abort-overwrite-2.6.16-1-686-smp: linux-image-2.6.16-1-686-smp/prerm/removing-running-kernel-2.6.16-1-686-smp: true --- End Message --- --- Begin Message --- Version: 2.6.18-1 etch has a newer kernel with e1000 fixes, please holler if you can still reproduce. -- maks --- End Message ---
Processed: Re: UDMA3/4/5 not working with Centrino Chipset, 82801DBM (ICH4-M) IDE Controller (rev 03)
Processing commands for [EMAIL PROTECTED]: > tags 314707 moreinfo Bug#314707: UDMA3/4/5 not working with Centrino Chipset, 82801DBM (ICH4-M) IDE Controller (rev 03) There were no tags set. Tags added: moreinfo > stop Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#436227: marked as done (linux-image-2.6.21-2-686: uml experiences random segmentation faults due to fault information pollution)
Your message dated Mon, 6 Aug 2007 13:47:53 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#436227: linux-image-2.6.21-2-686: uml experiences random
segmentation faults due to fault information pollution
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: linux-image-2.6.21-2-686
Version: 2.6.21-6
Severity: normal
When running user mode linux (particularly more than one instance) uml reports
tasks failing with random segfaults. Apparently this is a symptom of a known
kernel bug: fault information pollution.
There is a patch for the kernel problem:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff_plain;h=d18951834216eae82e2f9112416111b4f55f1849
Any chance of getting this patch applied to the kernel in lenny?
-- Package-specific info:
** Version: Linux version 2.6.21-2-686 (Debian 2.6.21-6) ([EMAIL PROTECTED])
(gcc version 4.1.3 20070629 (prerelease) (Debian 4.1.2-13)) #1 SMP Wed Jul 11
03:53:02 UTC 2007
** Not tainted
** Kernel log:
ide: failed opcode was: unknown
hdg: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdg: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hdg: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdg: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hdg: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdg: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hdg: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdg: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hdg: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdg: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hdg: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdg: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hdg: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdg: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hdg: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdg: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hdg: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdg: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hdg: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdg: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hdg: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdg: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hdg: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdg: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hdg: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdg: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hdg: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdg: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hdg: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdg: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hdg: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdg: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hdg: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdg: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hdg: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdg: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hdg: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdg: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hdg: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdg: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hdg: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdg: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hdg: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdg: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hdg: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdg: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hdg: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdg: dma_intr: error=0x84 { DriveS
Bug#436227: linux-image-2.6.21-2-686: uml experiences random segmentation faults due to fault information pollution
Package: linux-image-2.6.21-2-686
Version: 2.6.21-6
Severity: normal
When running user mode linux (particularly more than one instance) uml reports
tasks failing with random segfaults. Apparently this is a symptom of a known
kernel bug: fault information pollution.
There is a patch for the kernel problem:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff_plain;h=d18951834216eae82e2f9112416111b4f55f1849
Any chance of getting this patch applied to the kernel in lenny?
-- Package-specific info:
** Version: Linux version 2.6.21-2-686 (Debian 2.6.21-6) ([EMAIL PROTECTED])
(gcc version 4.1.3 20070629 (prerelease) (Debian 4.1.2-13)) #1 SMP Wed Jul 11
03:53:02 UTC 2007
** Not tainted
** Kernel log:
ide: failed opcode was: unknown
hdg: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdg: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hdg: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdg: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hdg: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdg: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hdg: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdg: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hdg: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdg: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hdg: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdg: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hdg: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdg: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hdg: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdg: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hdg: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdg: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hdg: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdg: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hdg: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdg: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hdg: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdg: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hdg: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdg: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hdg: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdg: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hdg: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdg: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hdg: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdg: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hdg: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdg: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hdg: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdg: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hdg: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdg: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hdg: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdg: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hdg: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdg: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hdg: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdg: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hdg: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdg: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hdg: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdg: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hdg: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdg: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hdg: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdg: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hdg: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdg: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hdg: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdg: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hdg: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdg: dma_intr: error=0x84 { DriveStatusError BadCR
Bug#429622: AMD/ATI SB700 support to Debian
Hi Dann: Do you mean you need our test to the point release kernel on SB700/SB600? I think I can ask our QA's help to test it. And I have one question here: Is there any installation CD/DVD ISO image of "point release", which can be downloaded and burnt into CD/DVD? (It seems that there is no such ISO image) If there is no such image, we need to install etch(4.0) on a non-SB700 board, then upgrade the linux kernel into the version you mentioned, and try to boot this updated kernel on SB700 board, Am I right? Because I think etch(4.0) can NOT be installed onto SB700 board directly. Thanks Shane > Of course, the only way you will know if we are looking at candidate > upstreams for the next release is to follow along with the > debian-kernel list. If you don't really want to do that, you can > simply file the bugs and include a mention of which upstream kernel > fixes it (and, as always, pointers to exact git changesets are > ideal). > > That all said, I'd really like to see new hardware support get added > into the *existing* etch (4.0) release instead of forcing users to > wait for lenny for stable release support. Hardware support can be > added in what we call 'point releases'. The kernel for the first point > release (4.0r1) is already done and has been for some time, but we can > start testing patches for the point release (4.0r2) now. > > On that note, I've backported the various patches you've pointed me > to and committed them as they are all now upstream. This will result > in snapshot builds which you can pull and test. See the snapshots > section for etch here: > http://wiki.debian.org/DebianKernel > > This was committed in r9249, so you'll want to be sure to grab a > kernel of version 2.6.18.dfsg.1-14~snapshot.9249 or greater. > > I don't have the hardware in question, so all I've been able to test > is that it builds cleanly. Can you test these for us or help us find > some users who can? I'd like to get positive feedback on both the > SB600 and SB700 before releasing. Please direct that feedback to this > bug report.
