Bug#494783: marked as done (usbserial module parameters)
Your message dated Wed, 13 Aug 2008 09:12:52 +0200 with message-id <[EMAIL PROTECTED]> and subject line Re: Bug#494783: usbserial module parameters has caused the Debian Bug report #494783, regarding usbserial module parameters 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 [EMAIL PROTECTED] immediately.) -- 494783: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=494783 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems --- Begin Message --- Package: linux-image-2.6.26-1-686 Version: 2.6.26-2 Severity: normal modinfo usbserial shows three parameters: filename: /lib/modules/2.6.26-1-686/kernel/drivers/usb/serial/usbserial.ko license:GPL description:USB Serial Driver core author: Greg Kroah-Hartman, [EMAIL PROTECTED], http://www.kroah.com/linux/ depends:usbcore vermagic: 2.6.26-1-686 SMP mod_unload modversions 686 parm: vendor:User specified USB idVendor (ushort) parm: product:User specified USB idProduct (ushort) parm: debug:Debug enabled or not (bool) but the sysfs shows only one parameter % ls -al /sys/module/usbserial/parameters insgesamt 0 drwxr-xr-x 2 root root0 12. Aug 09:24 . drwxr-xr-x 7 root root0 12. Aug 09:24 .. -rw-r--r-- 1 root root 4096 12. Aug 09:24 debug What is correct? -- Ist Ihr Browser Vista-kompatibel? Jetzt die neuesten Browser-Versionen downloaden: http://www.gmx.net/de/go/browser --- End Message --- --- Begin Message --- Thank you for your answer! -- Ist Ihr Browser Vista-kompatibel? Jetzt die neuesten Browser-Versionen downloaden: http://www.gmx.net/de/go/browser --- End Message ---
Bug#494922: initramfs-tools: fails to include the ext4 module into the initramfs.
On Tue, 12 Aug 2008, Wei Hu wrote: > Package: initramfs-tools > Severity: normal > > I switched my root fs from ext3 to ext4. The initramfs built by > initramfs-tools doesn't include the ext4 module, making the system > unbootable. I removed the package and installed yaird, which correctly > identifies the dependency on ext4. have you tried a) adding ext4dev to /etc/initramfs-tools/modules or b) setting in /etc/initramfs-tools/initramfs.conf MODULES=dep ext4 is not stable for the lenny released kernel, aka 2.6.26, but 2.6.27 had a nice merge regards -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#494936: bnx2 fails to load on bootup, succeeds on manual load
Package: firmware-bnx2 Version: 0.12 Severity: grave BNX2 fails to load the firmware on bootup. If I rmmod bnx2 and modprobe bnx2 after bootup, the nics appear. Log can be found at http://home.schottelius.org/~nico/unix/linux/debian/dmesg.2.6.25-2%2bbnx2%2bmanual-load -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (x86_64) Kernel: Linux 2.6.25-2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash firmware-bnx2 depends on no packages. firmware-bnx2 recommends no packages. Versions of packages firmware-bnx2 suggests: ii initramfs-tools 0.92e tools for generating an initramfs ii linux-image-2.6.22-3-amd 2.6.22-6.lenny1 Linux 2.6.22 image on AMD64 ii linux-image-2.6.25-2-amd 2.6.25-7Linux 2.6.25 image on AMD64 -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#489387: Please do not replace vserver with openvz.
Micah Anderson yazmış: > > There is a working patch available as of yesterday for 2.6.25 and > 2.6.25.2 which fixes both ext4 and xfs. It has had the 'dontuse' flag > removed and is considered pre5. I guess you're mentioning 2.6.26 http://vserver.13thfloor.at/Experimental/patch-2.6.26.2-vs2.3.0.35-pre5.diff -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: pnp bug in 2.6.27-rc1 (ad1816a / mpu401 / parport_pc issue)
Am Tuesday 12 August 2008 23:26:12 schrieben Sie: > On Tuesday 12 August 2008 12:10:51 pm Bjorn Helgaas wrote: > > On Tuesday 12 August 2008 05:17:26 am Uwe Bugla wrote: > > > Case C: > > > same preconditions as case B, but additionally: > > > 1. no IRQs reserved for ISA use only (in BIOS) > > > This option I would call "PNP pure" > > > > > > ... > > > My only criticism within the desired case C (no additional screwing > > > around done by user) > > > consists of two points: > > > 1. I'd prefer the second parport running with IRQ 5 instead of in > > > polling mode. > > > > Yes, that would be good. But I think the only way to achieve this > > reliably is to use the "pnp_reserve_irq=5" kernel parameter and the > > "options parport_pc io=0x278 irq=5" module parameter. Yes and No. 1. "pnp_reserve_irq=5" does not work because the module who accepts that parameter is unknown. At least parport_pc does not understand that. 2. "options parport_pc io=0x278 irq=5" does not work. 3. This one, call it minimum adequate intervention in userspace, works: "options parport_pc io=0x378,0x278 irq=7,5" > > Otherwise the > > kernel doesn't know how the jumpers on the ISA parport card are set. > > One more thing: since you have a non-PNP ISA card, I don't think > you can reliably use a "pure PNP" approach. In addition to the > kernel and module parameters, I think you need to configure the > BIOS to reserve IRQ 5 for ISA use. The observation with your two patches applied against 2.6.27-rc3 says that without any BIOS reservation using the above options line is enough for the kernel to know that parport 0 gets IRQ 7 and parport 1 gets IRQ 5. This is what I would call progress. :) The second advantage is that those annoying MPU 401 messages should be gone now. :) But: the sound card module is not loaded anymore, and I have seen some checksum error, some hex address or similar. Looks like that: pnp 01:00: get resources 01:01: invalid checksum 0x59 01:01: card 'Analog Devices AD1816A' isapnp: 1 Plug & Play card detected total That also does not change if I free up IRQ 5 and / or 10 in my BIOS. IRQ 10 would then appear in the system info as unused, but the sound card module won't load. > Otherwise, the BIOS might put > some other device on IRQ 5. No, not within the latest state of development. > > Of course, if you are content to run the second parport in polling > mode, you wouldn't need the BIOS configuration. If I were so easily to satisfy I would not spend that enormous amount of time for finding solutions :) > > Bjorn Please see two attachments: 1. 2627rc3.txt 2. messages.txt: the complete log inheriting all dmesgs (because you mentioned you would miss some info) PS.: The only thing missing now is the plug and play driver passing IRQ 10 or 11 to the ISA PnP sound card WITHOUT BIOS changes. That's it what I would call the optimal compromise On the other hand: If I do need to force everything by BIOS changes or additional kernel parameters then the PNP driver concept is worthless. I understand that a Non-PnP ISA card needs some help at least by kernel parameters, and if the same module touches a PNP device this PnP device must be mentioned too in the kernel parameter statement, but the rest of the ressources should be assigned automatically, shouldn't they? Uwe P. S. 2: Kernel 2.6.26 behaves totally different: it simply ignores the kernel parameters and assigns IRQ 5 to the sound card, whatever happens. You do not have any chance to assign an interrupt to rthe second parport, if you do not change your BIOS values. To achieve that I do not need any PnP architecture, do I? options parport_pc io=0x378,0x278 irq=7,5 no BIOS reservations! Kernel 2.6.27-rc3 with two patches applied Bridge [PCI0] (:00) pci :00:09.0: supports D1 pci :00:09.0: supports D2 pci :00:09.0: PME# supported from D1 D2 D3hot pci :00:09.0: PME# disabled pci :00:0a.0: supports D1 pci :00:0a.0: supports D2 pci :00:0a.0: PME# supported from D1 D2 D3hot pci :00:0a.0: PME# disabled pci :01:05.0: supports D1 bus 00 -> node 0 ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 9 *10 11 12 14 15) ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 9 10 *11 12 14 15) ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 *9 10 11 12 14 15) ACPI: PCI Interrupt Link [LNKD] (IRQs *3 4 5 6 7 9 10 11 12 14 15) ACPI: Power Resource [URP1] (off) ACPI: Power Resource [URP2] (off) ACPI: Power Resource [FDDP] (off) ACPI: Power Resource [LPTP] (off) Linux Plug and Play Support v0.97 (c) Adam Belay pnp: PnP ACPI init ACPI: bus type pnp registered pnp 00:00: parse allocated resources pnp 00:00: add io 0xcf8-0xcff flags 0x1 pnp 00:00: Plug and Play ACPI device, IDs PNP0a03 (active) pnp 00:01: parse allocated resources pnp 00:01: add io 0xde00-0xde03 flags 0x1 pnp 00:01: PNP0c02: calling quirk_system_pci_resources+0x0/0x171 pnp 00:01: Plug and Play AC
Bug#494984: linux-image-2.6.26-1-686: eeepc 900 - No boot without ac adapter
Package: linux-image-2.6.26-1-686 Version: 2.6.26-2 Severity: important Hello, my eeepc 900 running sid does not boot no more without ac adapter. Or better it boots without errors, then X comes up and then system automatically shuts down. "/var/log/kern.log" reports: -- Aug 13 12:38:02 cheyenne kernel: [ 32.976355] ACPI: Critical trip point Aug 13 12:38:02 cheyenne kernel: [ 32.976377] Critical temperature reached (144 C), shutting down. -- Obviously that temperature is not true, in fact if I plug the ac adapter and then boot system works perfectly. -- cheyenne:~# acpi -V Battery 0: Full, 100% AC Adapter 0: on-line Thermal 0: ok, 62.0 degrees C Cooling 0: Processor 0 of 7 -- Thank you and bye. Andrea Lorenzetti Ps: current thread on Debian-eeepc-devel mailing list: http://lists.alioth.debian.org/pipermail/debian-eeepc-devel/2008-August/000656.html -- Package-specific info: ** Version: Linux version 2.6.26-1-686 (Debian 2.6.26-2) ([EMAIL PROTECTED]) (gcc version 4.1.3 20080623 (prerelease) (Debian 4.1.2-23)) #1 SMP Fri Aug 8 18:51:38 UTC 2008 ** Command line: root=UUID=1f3155ca-6f34-42fd-9e38-3891b4e20e01 ro vga=788 pci=nommconf quiet ** Tainted: P (1) ** Kernel log: [14007.084367] end_request: I/O error, dev sdd, sector 0 [14007.085730] end_request: I/O error, dev sdd, sector 0 [14007.087108] end_request: I/O error, dev sdd, sector 0 [14007.110750] end_request: I/O error, dev sdd, sector 63 [14007.112872] end_request: I/O error, dev sdd, sector 63 [14007.116874] end_request: I/O error, dev sdd, sector 0 [14007.120555] end_request: I/O error, dev sdd, sector 8 [14007.124370] end_request: I/O error, dev sdd, sector 0 [14007.128248] end_request: I/O error, dev sdd, sector 0 [14015.462526] usb 5-3: USB disconnect, address 6 [14054.144055] usb 5-3: new high speed USB device using ehci_hcd and address 7 [14054.349107] usb 5-3: configuration #1 chosen from 1 choice [14054.363363] scsi5 : SCSI emulation for USB Mass Storage devices [14054.367709] usb-storage: device found at 7 [14054.367738] usb-storage: waiting for device to settle before scanning [14054.368271] usb 5-3: New USB device found, idVendor=04cf, idProduct=8818 [14054.368282] usb 5-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [14054.368288] usb 5-3: Product: USB Mass Storage Device [14054.368292] usb 5-3: Manufacturer: Myson Century, Inc. [14054.368296] usb 5-3: SerialNumber: 100 [14059.364209] usb-storage: device scan complete [14059.366418] scsi 5:0:0:0: Direct-Access IC25N040 ATMR04-0 MO2O PQ: 0 ANSI: 0 CCS [14059.410240] sd 5:0:0:0: [sdd] 78140160 512-byte hardware sectors (40008 MB) [14059.415514] sd 5:0:0:0: [sdd] Write Protect is off [14059.415525] sd 5:0:0:0: [sdd] Mode Sense: 00 14 00 00 [14059.415530] sd 5:0:0:0: [sdd] Assuming drive cache: write through [14059.416752] sd 5:0:0:0: [sdd] 78140160 512-byte hardware sectors (40008 MB) [14059.417509] sd 5:0:0:0: [sdd] Write Protect is off [14059.417519] sd 5:0:0:0: [sdd] Mode Sense: 00 14 00 00 [14059.417524] sd 5:0:0:0: [sdd] Assuming drive cache: write through [14059.417531] sdd: sdd1 [14059.446898] sd 5:0:0:0: [sdd] Attached SCSI disk [14062.453262] end_request: I/O error, dev sdd, sector 63 [14062.453276] __ratelimit: 23 messages suppressed [14062.453282] Buffer I/O error on device sdd1, logical block 0 [14062.453293] Buffer I/O error on device sdd1, logical block 1 [14062.453300] Buffer I/O error on device sdd1, logical block 2 [14062.453306] Buffer I/O error on device sdd1, logical block 3 [14062.455002] end_request: I/O error, dev sdd, sector 63 [14062.455016] Buffer I/O error on device sdd1, logical block 0 [14062.472764] end_request: I/O error, dev sdd, sector 63 [14062.472778] Buffer I/O error on device sdd1, logical block 0 [14062.472789] Buffer I/O error on device sdd1, logical block 1 [14062.472795] Buffer I/O error on device sdd1, logical block 2 [14062.472801] Buffer I/O error on device sdd1, logical block 3 [14062.474629] end_request: I/O error, dev sdd, sector 63 [14062.474643] Buffer I/O error on device sdd1, logical block 0 [14062.477131] end_request: I/O error, dev sdd, sector 0 [14062.478631] end_request: I/O error, dev sdd, sector 8 [14062.480115] end_request: I/O error, dev sdd, sector 0 [14062.481423] end_request: I/O error, dev sdd, sector 0 [14102.514836] usb 5-3: USB disconnect, address 7 [14909.576121] usb 5-3: new high speed USB device using ehci_hcd and address 8 [14909.728143] usb 5-3: configuration #1 chosen from 1 choice [14909.742354] scsi6 : SCSI emulation for USB Mass Storage devices [14909.743253] usb-storage: device found at 8 [14909.743262] usb-storage: waiting for device to settle before scanning [14909.743746] usb 5-3: New USB device found, idVendor=04cf, idProduct=8818 [14909.743757] usb 5-3: New USB device strings: Mfr=1, Product=2,
Re: pnp bug in 2.6.27-rc1 (ad1816a / mpu401 / parport_pc issue)
On Wednesday 13 August 2008 09:47:04 am Uwe Bugla wrote: > Am Tuesday 12 August 2008 23:26:12 schrieben Sie: > > On Tuesday 12 August 2008 12:10:51 pm Bjorn Helgaas wrote: > > > On Tuesday 12 August 2008 05:17:26 am Uwe Bugla wrote: > > > > Case C: > > > > same preconditions as case B, but additionally: > > > > 1. no IRQs reserved for ISA use only (in BIOS) > > > > This option I would call "PNP pure" > > > > > > > > ... > > > > My only criticism within the desired case C (no additional screwing > > > > around done by user) > > > > consists of two points: > > > > 1. I'd prefer the second parport running with IRQ 5 instead of in > > > > polling mode. > > > > > > Yes, that would be good. But I think the only way to achieve this > > > reliably is to use the "pnp_reserve_irq=5" kernel parameter and the > > > "options parport_pc io=0x278 irq=5" module parameter. I see several things that should be fixed in ISAPNP. I'm working on those, but they're probably post-2.6.27 material. In the meantime, are you seeing new problems that were introduced between 2.6.26 and 2.6.27-rc3? If so, I should try to fix them right away so we can get a fix in 2.6.27. Your original report of "WARNING: at lib/vsprintf.c:609 vsnprintf+0x36/0x43d()" has been fixed already. I *think* the remaining issues about the parport1 IRQ and the MPU401 are related to the BIOS configuration and the parport_pc module parameters and are not regressions from 2.6.26, but please correct me if I'm wrong. Thanks for your patience with all this. I'm putting together an ISA machine at home now, so hopefully I'll soon have a way to test this better without wasting your time. Bjorn -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: pnp bug in 2.6.27-rc1 (ad1816a / mpu401 / parport_pc issue)
Am Wednesday 13 August 2008 18:54:05 schrieben Sie: > On Wednesday 13 August 2008 09:47:04 am Uwe Bugla wrote: > > Am Tuesday 12 August 2008 23:26:12 schrieben Sie: > > > On Tuesday 12 August 2008 12:10:51 pm Bjorn Helgaas wrote: > > > > On Tuesday 12 August 2008 05:17:26 am Uwe Bugla wrote: > > > > > Case C: > > > > > same preconditions as case B, but additionally: > > > > > 1. no IRQs reserved for ISA use only (in BIOS) > > > > > This option I would call "PNP pure" > > > > > > > > > > ... > > > > > My only criticism within the desired case C (no additional screwing > > > > > around done by user) > > > > > consists of two points: > > > > > 1. I'd prefer the second parport running with IRQ 5 instead of in > > > > > polling mode. > > > > > > > > Yes, that would be good. But I think the only way to achieve this > > > > reliably is to use the "pnp_reserve_irq=5" kernel parameter and the > > > > "options parport_pc io=0x278 irq=5" module parameter. Hi Bjorn, > I see several things that should be fixed in ISAPNP. I'm working > on those, but they're probably post-2.6.27 material. OK. > > In the meantime, are you seeing new problems that were introduced > between 2.6.26 and 2.6.27-rc3? If so, I should try to fix them > right away so we can get a fix in 2.6.27. In fact I found no new regressions, which is good. > > Your original report of "WARNING: at lib/vsprintf.c:609 > vsnprintf+0x36/0x43d()" has been fixed already. Yes. Well done, Bjorn! :) > I *think* the remaining issues about the > parport1 IRQ and the MPU401 are related to the BIOS configuration > and the parport_pc module parameters and are not regressions from > 2.6.26, but please correct me if I'm wrong. One can for sure regard that all as BIOS-related. With one exception: The parport1 issue is resolved at least for me: Adding "options parport_pc io=0x378,0x278 irq=7,5" to etc/modprobe.d/arch/i386 solves the problem without the necessity of freeing up an IRQ in the BIOS for that second parport which is a non-PnP ISA card. IT IS comprehensive that a Non-PnP card needs additional kernel parameters. What IS NOT comprehensive is the fact that currently I need to free up IRQ 10 for ISA use only to ensure that snd-ad1816a is being loaded. And that card is definitely a PnP sound card! I'd be very happy about a solution that completely avoids BIOS intervention... And there is still the issue how to get rid of those nasty MPU 401 messages. What is a comprehensive message that shows that this device has been loaded and registered, although it resides in an interruptless state? > > Thanks for your patience with all this. I'm putting together an ISA > machine at home now, so hopefully I'll soon have a way to test this > better without wasting your time. Patience does not belong to my strengths - lack of patience is the main reason why I was excluded from lkml.org. On the other hand you never wasted my time at all - the opposite is right: It's a pleasure to work with you, Bjorn! :) > > Bjorn Regards and thanks Uwe -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#494922: initramfs-tools: fails to include the ext4 module into the initramfs.
On Wed, Aug 13, 2008 at 4:19 AM, maximilian attems <[EMAIL PROTECTED]> wrote: > On Tue, 12 Aug 2008, Wei Hu wrote: > >> Package: initramfs-tools >> Severity: normal >> >> I switched my root fs from ext3 to ext4. The initramfs built by >> initramfs-tools doesn't include the ext4 module, making the system >> unbootable. I removed the package and installed yaird, which correctly >> identifies the dependency on ext4. > > have you tried > a) adding ext4dev to /etc/initramfs-tools/modules > > or > b) setting in /etc/initramfs-tools/initramfs.conf > MODULES=dep > > ext4 is not stable for the lenny released kernel, aka 2.6.26, > but 2.6.27 had a nice merge > Thank you for the response. I tried step b) and it did fix my problem. I've thought about editing /etc/initramfs-tools/initramfs.conf, but the man page seemed to suggest that most would include everything. Thanks, Wei -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#494984: [Debian-eeepc-devel] No boot without ac adapter
[added the bug to Cc] -=| Eric Cooper, Wed, Aug 13, 2008 at 01:29:48PM -0400 |=- > On Wed, Aug 13, 2008 at 05:38:44PM +0200, Mickael Massot-Pellet wrote: > > 1- Boot with AC Adapter > > 2- add thermal into `/etc/modprobe.d/blacklist` > > 3- reboot > > Or boot with "nocrt=1" on the kernel command line. That still allows > you to read the temperature using the thermal module, just disables > the "critical temperature" events. Cool. Thanks for the tip. However, nocrt didn't work at the kernel command line. Searching revealed that this is a thermal module parameter. Either pass "thermal.nocrt=1" to the kernel (not tested) or add "options thermal nocrt=1" to /etc/modprobe.d/local. Note that initrd's have to be updated after changing modprobe.d -- damJabberID: [EMAIL PROTECTED] signature.asc Description: Digital signature
Bug#489387: vserver patch available for 2.6.26
There is a working patch available as of yesterday for 2.6.25 and 2.6.25.2 which fixes both ext4 and xfs. It has had the 'dontuse' flag removed and is considered pre5. micah signature.asc Description: Digital signature
Bug#495009: please update vserver patch and re enable it
Package: linux-patch-debian-2.6.26 Version: 2.6.26-2 Severity: important hi, please, update linux-vserver patch up to patch-2.6.26.2-vs2.3.0.35-pre5.diff (or newer) and re enable linux-image-*-vserver-* packages. thanks irc log: (09:41:41 PM) Bertl: and there should (so far) be no differences between the 2.6.25 and the 2.6.26 patches (09:41:49 PM) Bertl: (given you take the lates one :) (09:41:52 PM) Bertl: *latest (09:42:54 PM) Bertl: 2.6.25.11-vs2.3.0.34.14 (09:43:26 PM) Bertl: should have the same fix/feature state as the vs2.3.0.35-pre5 --- ArturasK. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#494984: [Debian-eeepc-devel] No boot without ac adapter
On Wed, Aug 13, 2008 at 10:09:43PM +0300, Damyan Ivanov wrote: > However, nocrt didn't work at the kernel command line. Searching > revealed that this is a thermal module parameter. Yes, I'm using "options thermal nocrt=1" in /etc/modprobe.d/local. Ignore the bit about the kernel command line (I was confusing it with the "acpi=off" I had to use first to get it to boot past the temp shutdown, but that was much too crude ...) -- Eric Cooper e c c @ c m u . e d u -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [PATCH] AX.25: Fix sysctl registration if !CONFIG_AX25_DAMA_SLAVE
http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-hardy.git;a=commit;h=e4e7e60316dd82e96398bdf731656b8a96843778 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/257684 -- Tim Gardner [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#495014: linux-source-2.6.26: IDE reset, DMA, 32-bit access killed on hald startup, via driver
Package: linux-source-2.6.26
Version: 2.6.26-2
Severity: important
I am compiling in the via ide driver via82cxxx
Kernel boots up fine until hald starts. At this point, an 0xd opcode/busy is
reported and IDE is reset, DMA (and 32bit, etc) disabled.
I can restore these parameters with hdparms but this will lead to problems.
I noticed in the sources compared with 2.6.23 that the timing setup was changed.
This might be the problem (also had on 2.6.25). Possibly the "old" way is
necessary or a needed option.
Here is the logcheck section (hal startup shows on bootup display)
Aug 12 17:54:58 d_baron kernel: ttyS1: LSR safety check engaged!
Aug 12 17:54:58 d_baron kernel: hdc: dma_intr: status=0xd0 { Busy }
Aug 12 17:54:58 d_baron kernel: ide: failed opcode was: unknown
Aug 12 17:54:58 d_baron kernel: hdc: DMA disabled
Aug 12 17:54:58 d_baron kernel: hdd: DMA disabled
Aug 12 17:54:58 d_baron kernel: ide1: reset: success
(hda, hdb DMA, other parameters disabled as well.)
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (990, 'unstable'), (650, 'testing'), (500, 'stable'), (1,
'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.23-rt1-davidb (SMP w/1 CPU core; PREEMPT)
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash
Versions of packages linux-source-2.6.26 depends on:
ii binutils2.18.1~cvs20080103-7 The GNU assembler, linker and bina
ii bzip2 1.0.5-0.1high-quality block-sorting file co
Versions of packages linux-source-2.6.26 recommends:
ii gcc 4:4.3.1-2 The GNU C compiler
ii libc6-dev [libc-dev] 2.7-13 GNU C Library: Development Librari
ii make 3.81-5 The GNU version of the "make" util
Versions of packages linux-source-2.6.26 suggests:
ii kernel-package11.001-0.1 A utility for building Linux kerne
ii libncurses5-dev [ncurses- 5.6+20080713-1 developer's libraries and docs for
ii libqt3-mt-dev 3:3.3.8b-5 Qt development files (Threaded)
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
how indicate that a kernel module package is obsolete?
I maintain a kernel module package (eeepc-acpi-source) that has been merged into the mainline Linux kernel as of version 2.6.26, and has had features added, bugs fixed, etc. The standalone module is still useful for the 2.6.25 kernel, but will be unnecessary in lenny+1. I'd like to somehow indicate that the resulting eeepc-acpi-modules-NNN packages are obsolete when NNN >= 2.6.26. 1. I can make the package fail to build (under module-assistant or make-kpkg) when the kernel version is recent enough. I don't know whether this kind of "conditional build failure" is acceptable practice, but it would keep useless .debs out of the archive. 2. I can make the package continue to build, but have the resulting .deb conflict with, as well as depend on, the corresponding linux-image package, so it becomes uninstallable. 3. I can do nothing at the package level, and rely on "educating users" to not use this package for recent kernels. I'd appreciate any guidance. Cheers, Eric -- Eric Cooper e c c @ c m u . e d u -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: how indicate that a kernel module package is obsolete?
On Wed, Aug 13, 2008 at 04:39:44PM -0400, Eric Cooper wrote: > I maintain a kernel module package (eeepc-acpi-source) that has been > merged into the mainline Linux kernel as of version 2.6.26, and has > had features added, bugs fixed, etc. > > The standalone module is still useful for the 2.6.25 kernel, but will > be unnecessary in lenny+1. Lenny will release with 2.6.26, so it is already unnecssary. Bastian -- Virtue is a relative term. -- Spock, "Friday's Child", stardate 3499.1 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#495009: marked as done (please update vserver patch and re enable it)
Your message dated Thu, 14 Aug 2008 00:34:47 +0200 with message-id <[EMAIL PROTECTED]> and subject line Re: Bug#495009: please update vserver patch and re enable it has caused the Debian Bug report #495009, regarding please update vserver patch and re enable it 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 [EMAIL PROTECTED] immediately.) -- 495009: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=495009 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems --- Begin Message --- Package: linux-patch-debian-2.6.26 Version: 2.6.26-2 Severity: important hi, please, update linux-vserver patch up to patch-2.6.26.2-vs2.3.0.35-pre5.diff (or newer) and re enable linux-image-*-vserver-* packages. thanks irc log: (09:41:41 PM) Bertl: and there should (so far) be no differences between the 2.6.25 and the 2.6.26 patches (09:41:49 PM) Bertl: (given you take the lates one :) (09:41:52 PM) Bertl: *latest (09:42:54 PM) Bertl: 2.6.25.11-vs2.3.0.34.14 (09:43:26 PM) Bertl: should have the same fix/feature state as the vs2.3.0.35-pre5 --- ArturasK. --- End Message --- --- Begin Message --- On Wed, Aug 13, 2008 at 10:13:07PM +0300, Arturas K wrote: > please, update linux-vserver patch up to > patch-2.6.26.2-vs2.3.0.35-pre5.diff (or newer) and re enable > linux-image-*-vserver-* packages. thanks The support for featuresets != none in linux-patch-debian-X is not official. Bastian -- The heart is not a logical organ. -- Dr. Janet Wallace, "The Deadly Years", stardate 3479.4 --- End Message ---
Processed: severity of 489387 is normal
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.9.26 > severity 489387 normal Bug#489387: linux-image-2.6.25-2-vserver-686: ipv6 is disabled in the 2.6.25 vserver flavour of the kernel Severity set to `normal' from `important' > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: severity of 495014 is normal
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.9.26 > severity 495014 normal Bug#495014: linux-source-2.6.26: IDE reset, DMA, 32-bit access killed on hald startup, via driver Severity set to `normal' from `important' > 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]
