Bug#426360: Need xen on non-pae machine
Package: linux-2.6 Version: 2.6.18.dfsg.1-12 How surprised I was after booting linux-image-2.6.18-4-xen-686 that it does not like my CPU. processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 13 model name : Intel(R) Celeron(R) M processor 1.30GHz stepping: 6 cpu MHz : 1300.000 cache size : 1024 KB fdiv_bug: no hlt_bug : no f00f_bug: no coma_bug: no fpu : yes fpu_exception : yes cpuid level : 2 wp : yes flags : fpu vme de pse tsc msr mce cx8 apic sep mtrr pge mca cmov pat clflush dts acpi mmx fxsr sse sse2 ss tm pbe up bogomips: 2597.16 Obviously it's not a production machine, but I need to do xen-related development on this laptop (not xen itself, but various things around it). I can see there is a non-pae hypervisor available, but no matching kernel for it. Please don't make me build my own kernel! The last time I had to do it was, like, 4 years ago! :-) -- Marcin Owsiany [EMAIL PROTECTED] http://marcin.owsiany.pl/ GnuPG: 1024D/60F41216 FE67 DA2D 0ACA FC5E 3F75 D6F6 3A0D 8AA0 60F4 1216 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#426210: linux-2.6: could ams module be enabled on apple platforms like powerbooks?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Yves-Alexis Perez wrote: Package: linux-2.6 Severity: wishlist Hi, ams is the Apple Motion Sensor present in various powerbooks (and maybe macbooks pro). Values from the sensor can be read from linux using the ams module now present upstream, but it's not compiled in on Debian kernels: # CONFIG_SENSORS_AMS is not set Could this module be enabled on Debian kernel for platforms that support it? - From drivers/hwmon/Kconfig it seems the driver is only for 32bit PowerMacs. - Jonas - -- * Jonas Smedegaard - idealist og Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ - Enden er nær: http://www.shibumi.org/eoti.htm -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGWoxfn7DbMsAkQLgRAuwZAJ4pjh6QIpu3VzUAZq4c4WXR54fWGACgihfo YEvftSWDRgg5rY85Z1pBIKY= =hsg4 -END PGP SIGNATURE-
Bug#426210: linux-2.6: could ams module be enabled on apple platforms like powerbooks?
On lun, 2007-05-28 at 10:01 +0200, Jonas Smedegaard wrote: Could this module be enabled on Debian kernel for platforms that support it? From drivers/hwmon/Kconfig it seems the driver is only for 32bit PowerMacs. Could it be enabled for 32bit powermacs. Or even only for powerbooks and macbooks pro, a I think there is no ams on desktop machines (maybe on ibook and macbook too). Regards, -- Yves-Alexis -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: your mail
Processing commands for [EMAIL PROTECTED]: reassign 425960 linux-image-2.6.21-1-prep Bug#425960: initramfs-tools: prep ppc root= not present Bug reassigned from package `initramfs-tools' to `linux-image-2.6.21-1-prep'. -- 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#397975: This is on upstream
This is on upstream bugzilla, and there's a patch and a workaround: http://bugzilla.kernel.org/show_bug.cgi?id=7201 I didn't know if I should set the forwarded and/or patch tag, since I'm not a kernel team member... -- Damián Viano(Des) ¯ ¯ - _ _ - ¯ ¯ GPG: 0x6EB95A6F Debian ¯-_GNU_-¯ Linux Web: http://damianv.com.ar/ ¯-¯ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#426210: linux-2.6: could ams module be enabled on apple platforms like powerbooks?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Yves-Alexis Perez wrote: On lun, 2007-05-28 at 10:01 +0200, Jonas Smedegaard wrote: Could this module be enabled on Debian kernel for platforms that support it? From drivers/hwmon/Kconfig it seems the driver is only for 32bit PowerMacs. Could it be enabled for 32bit powermacs. Or even only for powerbooks and macbooks pro, a I think there is no ams on desktop machines (maybe on ibook and macbook too). There's no Linux kernel officially compiled for Debian that is targeted at powerbooks only. Macbooks (pro or not) does not use the ams driver. Instead, I believe they use the applesmc driver available from http://www.mactel-linux.org/ (some of it adopted officially in 2.6.21 but not yet the applesmc driver, it seems). - Jonas - -- * Jonas Smedegaard - idealist og Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ - Enden er nær: http://www.shibumi.org/eoti.htm -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGWqU9n7DbMsAkQLgRAtjVAJ0eNp+qrVYDD8a2ErXSTys0Z+LbPwCdHFZN Q6Y+eg8p9HSNmDwNdmwWr/s= =s2dU -END PGP SIGNATURE-
Bug#426210: linux-2.6: could ams module be enabled on apple platforms like powerbooks?
On lun, 2007-05-28 at 11:47 +0200, Jonas Smedegaard wrote: There's no Linux kernel officially compiled for Debian that is targeted at powerbooks only. Yeah but it can be enabled for 32bits powermacs. It won't load on powermacs without hardware, but like every module. -- Yves-Alexis -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#397975: This is on upstream
forwarded 397975 http://bugzilla.kernel.org/show_bug.cgi?id=7201 tags 397975 + upstream thanks I didn't know if I should set the forwarded and/or patch tag, since I'm not a kernel team member... I'm not either, but it is allowed. I'm not sure if the kernel team will want to apply the patch or just wait until this gets included with a next upstream release. It looks like the patch has not yet been accepted upstream, or at least it's not yet been included for 2.6.22-rc3. Therefore not setting the patch tag. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#397975: This is on upstream
Processing commands for [EMAIL PROTECTED]: forwarded 397975 http://bugzilla.kernel.org/show_bug.cgi?id=7201 Bug#397975: /boot/vmlinuz-2.6.18-1-k7: Oops when plugging USB Nokia phone Noted your statement that Bug has been forwarded to http://bugzilla.kernel.org/show_bug.cgi?id=7201. tags 397975 + upstream Bug#397975: /boot/vmlinuz-2.6.18-1-k7: Oops when plugging USB Nokia phone There were no tags set. Tags added: upstream thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Another level of agression ?
* Sven Luther ([EMAIL PROTECTED]) [070528 12:14]: On Mon, May 28, 2007 at 11:17:39AM +0200, Bastian Blank wrote: On Mon, May 28, 2007 at 08:38:24AM +0200, Joey Schulze wrote: I can understand the latter. However, maybe it was just a mistake and waldi didn't want to remove Sven but accidently removed one line too much or something? He'll probably speak up and explain things. I already said that I can't remember. I know there was something about dilinger and wli but not more. Fine, so can you reactivate my access ? It seems that waldi doesn't want to do it, and also not to give any statement that he wanted to kick you out. I consider this a very bad behaviour, at least. And not acceptable. We had just an IRC-discussion (in German): 12:15 Ganneff waldi: wie siehts aus mit svenl wieder zum alioth kernel zuzufügen nachdem er da wohl ungeplant flog? 12:15 waldi Ganneff: es hat eigentlich keiner lust sich mit ihm abzugeben. ein teil ignoriert ihn komplett 12:15 aba waldi: *du* hast ihn entfernt. Dann bist Du auch fürs aufräumen zuständig. 12:16 Ganneff waldi: dann schreib ihm entweder sowas als entscheidung vom kernel team wenns die gibt oder füg ihn wieder zu. aber ignorieren ist nix gut. 12:16 aba waldi: entweder sagst du offiziell, das du ihn draußen haben willst. Oder du fügst ihn wieder hinzu. 12:17 Ganneff waldi: und es heisst svn zufügen, das muss nit unbedingt wieder admin sein. solang er dran arbeiten kann - oder alternativ halt weiss dass es nix wird weil $grund. 12:21 Ganneff waldi: so? 12:27 Ganneff waldi: im moment siehts eher so aus dass du deinen access zu kernel (zumindest admin) verlieren solltest, nicht sven. (and no answer from waldi up to now) As you can see, there is no need for you to escalate it - other people will take care of that. :) Cheers, Andi -- http://home.arcor.de/andreas-barth/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#426210: linux-2.6: could ams module be enabled on apple platforms like powerbooks?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Yves-Alexis Perez wrote: On lun, 2007-05-28 at 11:47 +0200, Jonas Smedegaard wrote: There's no Linux kernel officially compiled for Debian that is targeted at powerbooks only. Yeah but it can be enabled for 32bits powermacs. It won't load on powermacs without hardware, but like every module. I see no problem simply enabling it globally, and let the Linux code resolve the architectures relevant or not for actual compilation. If theoretically some day the code is enhanced to support more architectures (like if it is merged with the x86-specific applesmc) the change is silently included in Debian. Only reason I see for limiting a configuration scope is if it is technically possible to build for more architectures but causes problems (like some networking options disabled for arm that I suspect is too slow to make sense there even if technically possible). - Jonas - -- * Jonas Smedegaard - idealist og Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ - Enden er nær: http://www.shibumi.org/eoti.htm -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGWq3Ln7DbMsAkQLgRArfnAJ9b96wEmYAeFhg5JuThoCqLavMMGQCghn33 kVwCzmvnvnErS5mMJnNhPrs= =vgKQ -END PGP SIGNATURE-
Re: Another level of agression ?
* Andreas Barth ([EMAIL PROTECTED]) [070528 12:28]: It seems that waldi doesn't want to do it, and also not to give any statement that he wanted to kick you out. I consider this a very bad behaviour, at least. And not acceptable. After some more pressure on IRC, your commit access has been restored. Cheers, Andi -- http://home.arcor.de/andreas-barth/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#423040: update
found 423040 2.6.21-2 thanks -pkg linux-2.6 ver 2.6.20-3 - linux-2.6-2.6.20/Documentation/netlabel/draft-ietf-cipso-ipsecurity-01.txt +pkg linux-2.6 ver 2.6.21-2 + linux-2.6-2.6.21/Documentation/netlabel/draft-ietf-cipso-ipsecurity-01.txt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: update
Processing commands for [EMAIL PROTECTED]: found 423040 2.6.21-2 Bug#423040: Source package contains non-free IETF RFC/I-D Bug marked as found in version 2.6.21-2. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Another level of agression ?
On Mon, May 28, 2007 at 12:28:16PM +0200, Andreas Barth wrote: * Sven Luther ([EMAIL PROTECTED]) [070528 12:14]: On Mon, May 28, 2007 at 11:17:39AM +0200, Bastian Blank wrote: On Mon, May 28, 2007 at 08:38:24AM +0200, Joey Schulze wrote: I can understand the latter. However, maybe it was just a mistake and waldi didn't want to remove Sven but accidently removed one line too much or something? He'll probably speak up and explain things. I already said that I can't remember. I know there was something about dilinger and wli but not more. Fine, so can you reactivate my access ? It seems that waldi doesn't want to do it, and also not to give any statement that he wanted to kick you out. I consider this a very bad behaviour, at least. And not acceptable. We had just an IRC-discussion (in German): 12:15 Ganneff waldi: wie siehts aus mit svenl wieder zum alioth kernel zuzufügen nachdem er da wohl ungeplant flog? 12:15 waldi Ganneff: es hat eigentlich keiner lust sich mit ihm abzugeben. ein teil ignoriert ihn komplett 12:15 aba waldi: *du* hast ihn entfernt. Dann bist Du auch fürs aufräumen zuständig. 12:16 Ganneff waldi: dann schreib ihm entweder sowas als entscheidung vom kernel team wenns die gibt oder füg ihn wieder zu. aber ignorieren ist nix gut. 12:16 aba waldi: entweder sagst du offiziell, das du ihn draußen haben willst. Oder du fügst ihn wieder hinzu. 12:17 Ganneff waldi: und es heisst svn zufügen, das muss nit unbedingt wieder admin sein. solang er dran arbeiten kann - oder alternativ halt weiss dass es nix wird weil $grund. 12:21 Ganneff waldi: so? 12:27 Ganneff waldi: im moment siehts eher so aus dass du deinen access zu kernel (zumindest admin) verlieren solltest, nicht sven. (and no answer from waldi up to now) As you can see, there is no need for you to escalate it - other people will take care of that. :) Well, we would not have this kind of problems if debian was a more egalitarian place, where every DD would have a rigth to work on what pleases him, and that the most efficient infrastructure support be given him for that. The only reason for stopping a DD to work on something or giving him access would be serious technical reasons. This is the Debian i believed in, but, now as a year ago when the d-i leadership removed me from the d-i team because 'i was not respectful enough', debian doesn't seem to work this way anymore if it ever did. So, instead of trying to discuss this in the back, as you and Joerg did, with good intentions maybe, why not tackle the issue frontally, and resolve in one go all that which leds to frustration and flamewars in debian. If a few people, who used to do great work maybe, are unwilling to play fairly, and behave like little (or not so little) dictators in the area they have managed to get themselves in a power position, then maybe debian is better off without them, and they can take time off to reflect on what debian means to them. So, again, i ask that my d-i and kernel svn access be restored, and that the suspension be removed. None of those where technically justified, none of them had any impact appart from dragging debian into a year-long flamewar, and in general, none of these decisions where the result of fair or even simply acceptably decent decisions. Saddened, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#426210: linux-2.6: could ams module be enabled on apple platforms like powerbooks?
On lun, 2007-05-28 at 12:24 +0200, Jonas Smedegaard wrote: Yeah but it can be enabled for 32bits powermacs. It won't load on powermacs without hardware, but like every module. I see no problem simply enabling it globally, and let the Linux code resolve the architectures relevant or not for actual compilation. If theoretically some day the code is enhanced to support more architectures (like if it is merged with the x86-specific applesmc) the change is silently included in Debian. Only reason I see for limiting a configuration scope is if it is technically possible to build for more architectures but causes problems (like some networking options disabled for arm that I suspect is too slow to make sense there even if technically possible). Ah yes, I'm complety for enabling it globally, but I tought maybe kernel team wouldn't want to do it and would restrict it to a list of supported archs. Thanks! -- Yves-Alexis -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Another level of agression ?
On Mon, May 28, 2007 at 12:41:59PM +0200, Andreas Barth wrote: * Andreas Barth ([EMAIL PROTECTED]) [070528 12:28]: It seems that waldi doesn't want to do it, and also not to give any statement that he wanted to kick you out. I consider this a very bad behaviour, at least. And not acceptable. After some more pressure on IRC, your commit access has been restored. It is not enough, i want the suspension revoked, since it was a stupid decision, which has achieved nothing except worsen the situation, and was taken contrary to the DAMs procedure, and in a shady and mysterious way. It is not acceptable that debian deals in mafioso politics, and the DAMs, by knowingly hiding most of the evidence, have actively participated in it. Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Another level of agression ?
Sven Luther wrote: After some more pressure on IRC, your commit access has been restored. It is not enough, i want the suspension revoked, since it was a stupid decision, which has achieved nothing except worsen the situation, and was taken contrary to the DAMs procedure, and in a shady and mysterious way. Oh come on Sven! This thread was about the accidential removal of your kernel team commit access. It has been restored since them. The problem is fixed. Tell you what, if you continue trolling and ranting here, sooner or later your commit access will be removed *on purpose* with no way for you to get it back. This is not a threat but a warning. We know that you're not happy with the situation, but continueing to bring it up will not solve it either. Please don't reply and work on important things instead. Regards, Joey -- It's practically impossible to look at a penguin and feel angry. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#425462: NAT prerouting over tun interface broken
On Monday 28 May 2007 11:11, Frans Pop wrote: Somehow this causes default ipv4 settings defined in /etc/sysctl.conf to no longer be applied to eth0. Quoting Herbert Xu (emphasis is mine): Changing the value in default only affects interfaces which are *registered* afterwards. Previously they affected interfaces which are *brought up* afterwards. I'll talk to others to see if we could come up with a way to minimize this sort of pain. pgpLK6Gi063QH.pgp Description: PGP signature
Re: Another level of agression ?
* Sven Luther ([EMAIL PROTECTED]) [070528 13:23]: [...] Sven, this whole thread is about that your commit access to the kernel svn repro was revoked without anyone telling you. What then happened is that the alioth admins published that waldi revoked the access, waldi refused to comment to it, and was finally beaten by Ganneff and me to reenable your access. So, you see, two people jumped up to help you to get your access back, and were successful. I can understand that you are annoyed/angry at waldi now, but please consider that some people in Debian did efforts to help you to have your access restored. (And BTW, I still think that waldi needs to send a public apology for removing your access - as far as I can see it, it really seems to me waldi shouldn't have admin access because his behaviour is not how any admin should behave. But please stop muddling everything together. Debian as a project is definitly not responsible for waldis bad behaviour - and there is no correlation between waldis bad behaviour and anything else, waldi is behaving bad to almost all and not only to you.) Cheers, Andi -- http://home.arcor.de/andreas-barth/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#425462: NAT prerouting over tun interface broken
On Mon, May 28, 2007 at 01:05:41PM +0200, Frans Pop wrote: Quoting Herbert Xu (emphasis is mine): Changing the value in default only affects interfaces which are *registered* afterwards. Previously they affected interfaces which are *brought up* afterwards. I'll talk to others to see if we could come up with a way to minimize this sort of pain. There was a bug for me to put the values in default and into the all directory, which I think would solve this problem, at least for anyone with the new file. - Craig -- Craig Small GnuPG:1C1B D893 1418 2AF4 45EE 95CB C76C E5AC 12CA DFA5 http://www.enc.com.au/ csmall at : enc.com.au http://www.debian.org/ Debian GNU/Linux, software should be Free -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#426391: linux-2.6: [hppa] parisc64-smp - kernel panic on boot
Package: linux-2.6 Version: 2.6.21-4 Severity: important The boot failed with the following messages. Linux version 2.6.21-1-parisc64-smp (Debian 2.6.21-4) ([EMAIL PROTECTED]) (gcc version 4.1.37 FP[0] enabled: Rev 1 Model 16 The 64-bit Kernel has started... Initialized PDC Console for debugging. Determining PDC firmware type: System Map. model 5d10 0491 0002 778fe5fc 10f0 0008 00b2 00b2 vers 0300 CPUID vers 17 rev 10 (0x022a) capabilities 0x3 model 9000/785/J5600 Total Memory: 2048 MB initrd: 7faa9000-7ffee750 initrd: reserving 3faa9000-3ffee750 (mem_max 8000) LCD display at fff0f05d0008,fff0f05d registered SMP: bootstrap CPU ID is 0 Built 1 zonelists. Total pages: 517120 Kernel command line: root=/dev/sda5 HOME=/ console=ttyS0 TERM=vt102 palo_kernel=2/vmlinux Backtrace: [4015b074] parse_args+0x21c/0x328 [40180217] sync_page_range_nolock+0x44/0xb8 [4010500c] syscall_restore+0x1c/0x108 [401c7014] __d_lookup+0x13c/0x1e0 [40245410] nfs4_proc_delegreturn+0x140/0x260 [40125401] update_status_cbit+0x30/0x98 [403e5510] proc_dodebug+0x1f8/0x258 [403e4150] rpc_pipe_ioctl+0x68/0x80 [403c7430] packet_getsockopt+0x108/0x168 [403c5c88] packet_ioctl+0x120/0x178 [403c17dc] unix_ioctl+0x104/0x128 [403af650] ip_mroute_setsockopt+0xb80/0xc80 [403ae838] ip_mroute_getsockopt+0x88/0xf8 [403a700c] ipv4_sysctl_forward_strategy+0xdc/0x128 [403a6f84] ipv4_sysctl_forward_strategy+0x54/0x128 [403a5d20] ip_mc_msfget+0x120/0x1c8 Kernel Fault: Code=15 regs=405782c0 (Addr=c000) YZrvWESTHLNXBCVMcbcbcbcbOGFRQPDI PSW: 110001111110 Not tainted r00-03 0804070e 405d5de0 405e5d1c 40103000 r04-07 405c8de0 0008 425ac100 8000 r08-11 01f78060 4063f388 0804000e 405dca1c r12-15 0001 f044 r16-19 f8c4 f17c f174 1fe97981 r20-23 1ff895a0 c000 40103020 405beaa0 r24-27 4042bf4d 4010300d 405c8de0 r28-31 1fe97980 40578290 405782c0 3d00 sr00-03 sr04-07 IASQ: IAOQ: 405e5d7c 405e5d80 IIR: 0ea0109cISR: IOR: c000 CPU:0 CR30: 40578000 CR31: 4057c000 ORIG_R28: 405ebc24 IAOQ[0]: check_ivt+0x84/0xe0 IAOQ[1]: check_ivt+0x88/0xe0 RP(r2): check_ivt+0x24/0xe0 Kernel panic - not syncing: Kernel Fault pgpJwp22XtLOR.pgp Description: PGP signature
Bug#426395: initramfs-tools: omission of libgcc_s.so.1 from initramfs makes Linksys NSLU2 unbootable
Package: initramfs-tools Version: 0.87b Severity: critical Tags: patch Justification: breaks the whole system -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I cross-compiled an arm kernel from linux-source-2.6.21 using make-kpkg. After installing it on my Linksys NSLU2, the system became unbootable. Here is the console output: Booting kernel at 0x8000... Uncompressing Linux . done, booting the kernel. Linux version 2.6.21-slug (2.6.21-2) (marcus at melech) (gcc version 4.1.3 20070518 (prerelease) (Debian 4.1.2-8)) #2 Tue May 22 13:35:38 CEST 2007 CPU: XScale-IXP42x Family [690541f1] revision 1 (ARMv5TE), cr=397f Machine: Linksys NSLU2 Memory policy: ECC disabled, Data cache writeback CPU0: D VIVT undefined 5 cache CPU0: I cache: 32768 bytes, associativity 32, 32 byte lines, 32 sets CPU0: D cache: 32768 bytes, associativity 32, 32 byte lines, 32 sets Built 1 zonelists. Total pages: 8128 Kernel command line: rtc-x1205.probe=0,0x6f console=ttyS0,115200 rtc-x1205.probe=0,0x6f noirqdebug IRQ lockup detection disabled PID hash table entries: 128 (order: 7, 512 bytes) Console: colour dummy device 80x30 Dentry cache hash table entries: 4096 (order: 2, 16384 bytes) Inode-cache hash table entries: 2048 (order: 1, 8192 bytes) Memory: 32MB = 32MB total Memory: 25796KB available (2236K code, 213K data, 96K init) Security Framework v1.0.0 initialized SELinux: Disabled at boot. Capability LSM initialized Mount-cache hash table entries: 512 CPU: Testing write buffer coherency: ok NET: Registered protocol family 16 IXP4xx: Using 16MiB expansion bus window size PCI: IXP4xx is host PCI: IXP4xx Using direct access for memory space PCI: bus0: Fast back to back transfers disabled dmabounce: registered device :00:01.0 on pci bus dmabounce: registered device :00:01.1 on pci bus dmabounce: registered device :00:01.2 on pci bus NET: Registered protocol family 2 Time: OSTS clocksource has been installed. IP route cache hash table entries: 1024 (order: 0, 4096 bytes) TCP established hash table entries: 1024 (order: 1, 8192 bytes) TCP bind hash table entries: 1024 (order: 0, 4096 bytes) TCP: Hash tables configured (established 1024 bind 1024) TCP reno registered checking if image is initramfs... it is Freeing initrd memory: 4096K NetWinder Floating Point Emulator V0.97 (double precision) audit: initializing netlink socket (disabled) audit(4.370:1): initialized VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) JFFS2 version 2.2. (NAND) (C) 2001-2006 Red Hat, Inc. io scheduler noop registered io scheduler cfq registered (default) IXP4xx Watchdog Timer: heartbeat 60 sec Serial: 8250/16550 driver $Revision: 1.90 $ 2 ports, IRQ sharing disabled serial8250.0: ttyS0 at MMIO 0xc800 (irq = 15) is a XScale serial8250.0: ttyS1 at MMIO 0xc8001000 (irq = 13) is a XScale RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize IXP4XX-Flash.0: Found 1 x16 devices at 0x0 in 16-bit bank Intel/Sharp Extended Query Table at 0x0031 Using buffer write method cfi_cmdset_0001: Erase suspend on write enabled Searching for RedBoot partition table in IXP4XX-Flash.0 at offset 0x7e 6 RedBoot partitions found on MTD device IXP4XX-Flash.0 Creating 6 MTD partitions on IXP4XX-Flash.0: 0x-0x0004 : RedBoot NSLU2 MAC: 00:13:10:d6:1b:1b 0x0004-0x0006 : SysConf 0x0006-0x0008 : Loader 0x0008-0x001e : Kernel 0x001e-0x007e : Ramdisk 0x007e-0x0080 : FIS directory mice: PS/2 mouse device common for all mice i2c /dev entries driver x1205 0-006f: chip found, driver version 1.0.7 x1205 0-006f: rtc core: registered x1205 as rtc0 Registered led device: ready Registered led device: status Registered led device: disk-1 Registered led device: disk-2 NET: Registered protocol family 26 TCP bic registered NET: Registered protocol family 1 NET: Registered protocol family 17 XScale DSP coprocessor detected. x1205 0-006f: setting the system clock to 2007-05-22 12:03:58 (1179835438) Freeing init memory: 96K libgcc_s.so.1 must be installed for pthread_cancel to workKernel panic - not syncing: Attempted to kill init! Adding libgcc_s.so.1 to the initramfs and reflashing it solved the problem. Please see this discussion [1] for more details. Marcus [1] http://thread.gmane.org/gmane.linux.debian.ports.arm/4187/focus=4218 - -- Package-specific info: - -- /proc/cmdline rtc-x1205.probe=0,0x6f console=ttyS0,115200 rtc-x1205.probe=0,0x6f noirqdebug - -- /proc/filesystems cramfs ext3 fuseblk reiserfs xfs - -- lsmod Module Size Used by des19392 1330 cbc 4672 1330 blkcipher 6116 1 cbc ledtrig_heartbeat 3008 0 nfs 267076 0 nfsd 238572 17 exportfs5696 1 nfsd lockd 69912 3 nfs,nfsd
Bug#426404: initramfs-tools: firmware related problems in hook-functions
Package: initramfs-tools
Version: 0.88
Severity: important
Hi,
there seems to be something wrong with recent changes to hook-functions.
With initramfs-tools 0.88:
[EMAIL PROTECTED]:~# LANG=C dpkg-reconfigure linux-image-2.6.22-rc3
Running depmod.
Finding valid ramdisk creators.
Using mkinitramfs-kpkg to build the ramdisk.
Other valid candidates: mkinitramfs-kpkg mkinitrd.yaird
mkdir: cannot create directory `/tmp/mkinitramfs_FD9659/lib/udev/': File exists
cp: `/lib/firmware/ql2100_fw.bin' and
`/tmp/mkinitramfs_FD9659/lib/firmware/ql2100_fw.bin' are the same file
cp: `/lib/firmware/ql2200_fw.bin' and
`/tmp/mkinitramfs_FD9659/lib/firmware/ql2200_fw.bin' are the same file
cp: `/lib/firmware/ql2300_fw.bin' and
`/tmp/mkinitramfs_FD9659/lib/firmware/ql2300_fw.bin' are the same file
cp: `/lib/firmware/ql2322_fw.bin' and
`/tmp/mkinitramfs_FD9659/lib/firmware/ql2322_fw.bin' are the same file
cp: `/lib/firmware/ql2400_fw.bin' and
`/tmp/mkinitramfs_FD9659/lib/firmware/ql2400_fw.bin' are the same file
Trying to boot with this initrd the kernel is not able to find the
firmware for my qla2xxx, although a diff -Nur between the contents of
the following two images yields to nothing:
[EMAIL PROTECTED]:~# ls -l /boot/initrd.img-2.6.22*
-rw-r--r-- 1 root root 5268495 2007-05-28 12:33 /boot/initrd.img-2.6.22-rc3
-rw-r--r-- 1 root root 5269374 2007-05-27 22:30 /boot/initrd.img-2.6.22-rc3.bak
The one suffixed with '.bak' is a working initrd built with 0.87b.
Albeit it's not the source of this problem, notice the creation of the
local variable man_x and the usage of mam_x in the script:
diff -Nur initramfs-tools-0.87b/hook-functions
initramfs-tools-0.88/hook-functions
--- initramfs-tools-0.87b/hook-functions2007-04-16 19:58:58.0
+0200
+++ initramfs-tools-0.88/hook-functions 2007-05-27 00:55:26.0 +0200
@@ -38,8 +38,11 @@
done
}
+# Add dependent modules + eventual firmware
manual_add_modules()
{
+ local man_x firmwares firmware
+
for mam_x in $(modprobe --set-version=${version} --ignore-install \
ciao,
ema
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#426391: linux-2.6: [hppa] parisc64-smp - kernel panic on boot
On Monday 28 May 2007 15:06, Frans Pop wrote: The boot failed with the following messages. Additional info: this was the official package (grabbed from incoming). It was compiled using (from the build log [1]): libc6-dev_2.5-7 linux-kernel-headers_2.6.18-7 gcc-4.1_4.1.2-8 g++-4.1_4.1.2-8 binutils_2.17cvs20070426-7 libstdc++6-4.1-dev_4.1.2-8 libstdc++6_4.2-20070516-1 [1]http://buildd.debian.org/fetch.cgi?pkg=linux-2.6arch=hppaver=2.6.21-4stamp=1180242503 pgp2dftP7neLD.pgp Description: PGP signature
Bug#426391: linux-2.6: [hppa] parisc64-smp - kernel panic on boot
On Mon, May 28, 2007 at 04:33:56PM +0200, Frans Pop wrote: On Monday 28 May 2007 15:06, Frans Pop wrote: The boot failed with the following messages. Additional info: this was the official package (grabbed from incoming). It was compiled using (from the build log [1]): libc6-dev_2.5-7 linux-kernel-headers_2.6.18-7 gcc-4.1_4.1.2-8 g++-4.1_4.1.2-8 binutils_2.17cvs20070426-7 libstdc++6-4.1-dev_4.1.2-8 libstdc++6_4.2-20070516-1 There is a problem with new(er) binutils, Jeff Bailey is working on fixing it. Cheers, Kyle -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#426409: linux-image-2.6.18-4-k7: EXT3 remounts read-only, possible data loss with message ext3_free_blocks: Freeing blocks not in datazone
Package: linux-image-2.6.18-4-k7 Version: 2.6.18.dfsg.1-12etch2 Severity: important Our office server had an ext3 volume remount itself read-only after an error in handing a disk write. This is the first time this error or anything like it has occurred. Another ext3 file system on the same physical volume and RAID1 mirror volume did not report any errors. Afterwards, e2fsck reported a journal block was multiply-claimed with a data file block. I restored the file as a precaution from backup. This is a etch stable system. -- from /var/log/syslog May 23 12:30:02 menno kernel: EXT3-fs error (device dm-1): ext3_free_blocks: Freeing blocks not in datazone - block = 327786496, count = 1 May 23 12:30:02 menno kernel: Aborting journal on device dm-1. May 23 12:30:02 menno kernel: EXT3-fs error (device dm-1) in ext3_free_blocks_sb: Journal has aborted May 23 12:30:02 menno kernel: EXT3-fs error (device dm-1) in ext3_reserve_inode_write: Journal has aborted May 23 12:30:02 menno kernel: EXT3-fs error (device dm-1) in ext3_truncate: Journal has aborted May 23 12:30:02 menno kernel: EXT3-fs error (device dm-1) in ext3_reserve_inode_write: Journal has aborted May 23 12:30:02 menno kernel: EXT3-fs error (device dm-1) in ext3_orphan_del: Journal has aborted May 23 12:30:02 menno kernel: EXT3-fs error (device dm-1) in ext3_reserve_inode_write: Journal has aborted May 23 12:30:02 menno kernel: EXT3-fs error (device dm-1) in ext3_delete_inode: Journal has aborted May 23 12:30:02 menno kernel: __journal_remove_journal_head: freeing b_committed_data May 23 12:30:02 menno last message repeated 5 times May 23 12:30:02 menno kernel: ext3_abort called. May 23 12:30:02 menno kernel: EXT3-fs error (device dm-1): ext3_journal_start_sb: Detected aborted journal May 23 12:30:02 menno kernel: Remounting filesystem read-only -- There were some errors in the file system (though I'm not sure how many were directly from the ext3 errors and how many might have been present already). I needed to specify -f to e2fsck as when I first ran it afer unmounting the file system, it reported the filesystem was clean and didn't do a check. # umount /data/public # e2fsck -f /dev/vg_on_md0/public e2fsck 1.40-WIP (14-Nov-2006) Pass 1: Checking inodes, blocks, and sizes Inode 3375515, i_size is 741, should be 12288. Fixy? yes Deleted inode 4538519 has zero dtime. Fixy? yes Inode 5832931 is in use, but has dtime set. Fixy? yes Inode 5832931, i_blocks is 1148070603, should be 0. Fixy? yes Inode 7799003 has illegal block(s). Cleary? yes Illegal block #1 (1149919138) in inode 7799003. CLEARED. Illegal block #2 (1139529199) in inode 7799003. CLEARED. Illegal block #3 (1054177516) in inode 7799003. CLEARED. Inode 7799003, i_size is 741, should be 24576. Fixy? yes Inode 7799003, i_blocks is 8, should be 16. Fixy? yes Inode 7801123 is in use, but has dtime set. Fixy? yes Inode 7801123, i_blocks is 1139529203, should be 64. Fixy? yes Inode 7817987 is in use, but has dtime set. Fixy? yes Inode 7817987, i_blocks is 1054177850, should be 8. Fixy? yes Running additional passes to resolve blocks claimed by more than one inode... Pass 1B: Rescanning for multiply-claimed blocks Multiply-claimed block(s) in inode 8: 5224 Multiply-claimed block(s) in inode 49346: 131070 Multiply-claimed block(s) in inode 7799003: 5224 131070 Pass 1C: Scanning directories for inodes with multiply-claimed blocks Pass 1D: Reconciling multiply-claimed blocks (There are 2 inodes containing multiply-claimed blocks.) File The journal inode (inode #8, mod time Wed Jan 19 23:28:44 2005) has 1 multiply-claimed block(s), shared with 1 file(s): /Computer/hardware/Philips monitors/LCD monitor, model 170S5FB/CD-ROM/lcd/manual/ESPANOL/170P5/GLOSSARY/IMAGES/.AppleDouble/.Parent (inode #7799003, mod time Thu Feb 9 18:53:19 2006) Clone multiply-claimed blocksy? yes File /Pending Art and Copy/reg bibby/IMG_0740.JPG (inode #49346, mod time Thu Feb 22 11:49:08 2007) has 1 multiply-claimed block(s), shared with 1 file(s): /Computer/hardware/Philips monitors/LCD monitor, model 170S5FB/CD-ROM/lcd/manual/ESPANOL/170P5/GLOSSARY/IMAGES/.AppleDouble/.Parent (inode #7799003, mod time Thu Feb 9 18:53:19 2006) Clone multiply-claimed blocksy? yes File /Computer/hardware/Philips monitors/LCD monitor, model 170S5FB/CD-ROM/lcd/manual/ESPANOL/170P5/GLOSSARY/IMAGES/.AppleDouble/.Parent (inode #7799003, mod time Thu Feb 9 18:53:19 2006) has 2 multiply-claimed block(s), shared with 2 file(s): /Pending Art and Copy/reg bibby/IMG_0740.JPG (inode #49346, mod time Thu Feb 22 11:49:08 2007) The journal inode (inode #8, mod time Wed Jan 19 23:28:44 2005) Multiply-claimed blocks already reassigned or cloned. Pass 2: Checking directory structure Pass 3:
Re: Another level of agression ?
On Mon, May 28, 2007 at 01:03:29PM +0200, Joey Schulze wrote: Sven Luther wrote: After some more pressure on IRC, your commit access has been restored. It is not enough, i want the suspension revoked, since it was a stupid decision, which has achieved nothing except worsen the situation, and was taken contrary to the DAMs procedure, and in a shady and mysterious way. Oh come on Sven! This thread was about the accidential removal of your kernel team commit access. It has been restored since them. The problem is fixed. The wider problem has been there since marsch last year or so, and it was never fixed. Tell you what, if you continue trolling and ranting here, sooner or later your commit access will be removed *on purpose* with no way for you to get it back. This is not a threat but a warning. Yeah, right, is it so difficult to solve this as it should have been ? Do you really believe there is any valid justification to having me suspended for a year despite the 70:7 strong opposition of the DDs who where asked to express themselves ? What did it gain, and what was the reason that made the DAMs decide this way ? Appart that the expulsers provided more hatefull and agressive quotes than the those opposing the expulsion, and the DAMs chose to put them in value. Do you believe it was correct for the expulsers to ask for my expulsion on the day after i proposed my DPL candidacy, while i had not posted a single post on the debian lists for over a month ? And that the DAMs chose to hide this for whatevr obscure reason ? We know that you're not happy with the situation, but continueing to bring it up will not solve it either. Please don't reply and work on important things instead. Yeah, right, which is what i have been trying to do since over a year, first i worked, and provided over 30 or so patches to d-i despite the d-i access removal, just to get bashed in half the report by a clueless frans who jumped on every little excuse to explode, and finally made some under-hand manipulation with the ftp-masters to remove my upload right of the .udebs. This is what i did when i wrote the wiki page : http://wiki.debian.org/DebianInstaller/FransPopAndOthersVs%2eSvenLutherIssue and got FUCK YOU and the biggest load of self-satisfied and self-centered crap I've ever seen from frans, and abuse from geert and holger (which they removed in shame later on), and blackmail of joeyh in return. This is what i did in february, organizing hardware for the debian booth, passing time to prepare the ps3 debian install, on the ps3 that geert uutyeroven had arranged, and geert stappers or holger found the occasion to bash me when i once posted to the list by mistake while searching for a TV set. I did this while those hateful expulsers secretely where scheming to restart the expulsion procedure, while on saturday evening the DAMs had sent me a mail which got eaten by the debian.org mail greylisting or whatever, and while i spoke to James Troup on sunday afternoon, after having hold a discussion about the future possibilities of the kernel developments, of which nobody from the d-i team assisted except holger, who was forced to film, and frans passed by me without returning my greeting afterward. I did this while the expulsion process was underway and posted only few select mails, and even was mostly silent for the week or two that followed the end of the support mail period, waiting for the DAMs to decide in frustration and trauma, while Frans started agressing me on the lists again. I was doing this when i discovered this latest case. So, for me, now, in debian, the most important thing, is that this continuous agression are stopped, that each party in this is blamed accordying to their responsabilities, in a fair and equitable way, and that the one-sided punishment are lifted, and that we are all allowed to work on the parts of debian that we like and code all happily forever after. Can you tell me a single reason why this should not happen ? Can you tell me a single reason that justifies the DAMs decision to act as they did, and which can be named without shame (i know that one reason of the decision is the fact that the other party threatened to stop all d-i related work if they didn't get their way, just as Joey Hess has written on the wiki and that this would have caused a problem so near the etch release, i also know that Joerg Jaspert (and others) heavily disliked Anthony Towns, and thus it could justify the manipulation of the dates of the expulsers mail, to make it appear as if this was Anthony's action, but these are hardly noble reasons we can approve of, don't we) ? Joey, if you see this kind of attitude in real life, while you really stand by, and counsel the victim to support everything and be silent, especially as you being a pillar of the community, can act to change it ? This is not some unnamed oppression by a state or power we have no access too, this is unfairness,
Re: Another level of agression ?
On Mon, May 28, 2007 at 01:33:28PM +0200, Andreas Barth wrote: * Sven Luther ([EMAIL PROTECTED]) [070528 13:23]: [...] Sven, this whole thread is about that your commit access to the kernel This whole thread is about me being stopped from doing meaningful debian technical contribution and punished for not being respectful enough to frans and not meekly having bowed under the repeated punishment which they have dealt to me in order to get me silenced. svn repro was revoked without anyone telling you. What then happened is that the alioth admins published that waldi revoked the access, waldi refused to comment to it, and was finally beaten by Ganneff and me to reenable your access. So, you see, two people jumped up to help you to get your access back, and were successful. Sure, but it is an exact reproduction of what happened last year, when i discovered after coming back to debian work after my mothers funeral, that frans had revoked my d-i svn access. I can understand that you are annoyed/angry at waldi now, but please No, i am not angry at Bastian. Bastian is a good guy, if a bit blunt in his communication. I am angry at Debian, who has handled me unfairly (to use a nice word for it), and have left a select few go into a calumniation and provocation campaign against looking the other way. I am angry at the DAMs for having used the expulsion request in their private warfar against Anthony Towns, i am angry at all DDs because nobody contested the DAMs decision, and thus silently accepted another level of escalation of something that if you think of it, you would never have accepted in any RL condition. consider that some people in Debian did efforts to help you to have your access restored. (And BTW, I still think that waldi needs to send a public apology for removing your access - as far as I can see it, it really seems to me waldi shouldn't have admin access because his behaviour is not how any admin should behave. But please stop muddling everything together. Debian as a project is definitly not responsible for waldis bad behaviour - and there is no correlation between waldis bad behaviour and anything else, waldi is behaving bad to almost all and not only to you.) No, Debian needs to send me a public apology for how it has handled me since over a year, i have little hope that those who where the worst agressors will ever have enough honour and dignity to recognize their part of fault, but the debian project as a whole owes me an apology of how i was handled, and Debian owes me a lifting of all the punishments it has unfairly submitted to me. You all know me, you all know what entusiast and time i devoted to debian, and what i have achieved all over the almost 9 years since i became DD. Everyone who meets me in RL will tell you that i am a nice guy, always helpful and friendly. Is there any justification of the kind of harrasment i have been under since over a year, and any excuse for Debian allowing this to happen ? Saddened, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Another level of agression ?
Sven, stop it already! We've seen this several times already. You're not bringing up anything new. You're not helping yourself if you continue. Regards, Joey -- It's practically impossible to look at a penguin and feel angry. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Another level of agression ?
On Mon, May 28, 2007 at 05:40:26PM +0200, Joey Schulze wrote: Sven, stop it already! why should i ? The times i stopped, i got punished worse without provocation ? We've seen this several times already. Yes, so, what ? I have seen that if i don't make a fuss over this, everyone is pretty happy to let things slide into forgoteness. Never has me being silent helped in any way. You're not bringing up anything new. And i will repeat it as long as people try to ignore me, and until Debian stands up and act in a dign and honourable way in this. You're not helping yourself if you continue. You mean, i am not being meekly silent and accept my fate, right ? Like said, i was silent for longer periods in the past, and it earned me only repeated agression, so no, i will not be silent, and if you guys take it further, and try to censor me on the lists like it was tried, i guess there are other forums where i could export this mess. Why can't you guys understand how easy it would be to solve this ? Why do you think i proposed an in-person meeting at FOSDEM, and why do you think i spoke with Christian Perrier at solution linux in paris, asking him to help prepare such a in-person meeting at FOSDEM. Why do you think i held a technical discussion meeting at FOSDEM over the kernel, so the d-i folk could voice their critics, and we could reconcile all the difference of opinions, and chose the best technical solution for lenny, now, early in the development process ? Why do you think i wrote that positive wiki page, and called for reconciliation ? These are all things i expected from the DPL last year, when *I* went to him for a mediation. So, yes, i am angry and hurt, but i am rightfully angered, and i will not be silenced, except if someone decide to send some goons after me to empty some rounds of amunition into me. Frankly, all those years back, when i meet you in oldenburg, if i had known what a vampirizing beast debian was, and how the DDs would stand aside while a bunch of power-hungry assholes where going on a systematic campaign to hurt me, i would have gone away running, and not sacrificed so much of my time and work to debian. And you ask me to be silent ? Saddened, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#426414: kernel: time jumps and usb resets
Package: linux-image-2.6.21-1-powerpc Version: 2.6.21-4 Severity: important File: kernel I don't know if this is a hardware problem or a kernel bug. the same hardware had served correctly for years, so I sincerely hope it's a kernel bug... I'm not sure when the problem started to display... a crontab line for root runs ntpdate -q every single minute... the drift looks more or less constant, until occasional jumps. these jumps are coincident with some kernel logging... here are the syslog lines, bracketed by the output of ntpdate: ... 28 May 16:46:04 ntpdate[27236]: step time server 206.57.44.149 offset -23.773322 sec May 28 16:49:06 localhost kernel: usb 2-1.3: reset full speed USB device using ohci_hcd and address 4 May 28 16:49:07 localhost kernel: usb 1-1.2: reset full speed USB device using ohci_hcd and address 4 28 May 16:49:10 ntpdate[27256]: step time server 206.57.44.149 offset -187.783438 sec ... 28 May 16:55:04 ntpdate[27340]: step time server 206.57.44.149 offset -187.782406 sec May 28 16:57:43 localhost kernel: usb 2-1.3: reset full speed USB device using ohci_hcd and address 4 May 28 16:57:43 localhost kernel: usb 1-1.2: reset full speed USB device using ohci_hcd and address 4 28 May 16:57:46 ntpdate[27362]: step time server 206.57.44.149 offset -297.535529 sec ... 28 May 17:01:04 ntpdate[27427]: step time server 206.57.44.149 offset -297.534059 sec May 28 17:03:27 localhost kernel: usb 1-1.2: reset full speed USB device using ohci_hcd and address 4 May 28 17:03:27 localhost kernel: usb 2-1.4.3: reset full speed USB device using ohci_hcd and address 7 28 May 17:03:30 ntpdate[27453]: step time server 206.57.44.149 offset -409.487201 sec ... are these kernel logs an other effect of the jumps, or are they closely related to the cause? maybe it's also relevant that I am running wmaker and that more or less with the same frequency of these problems (maybe in coincidence?) I have to restart the window manager because the keyboard stops working (but the keys simulating mouse buttons 2 and 3 keep working). -- Package-specific info: ** Version: Linux version 2.6.21-1-powerpc (Debian 2.6.21-4) ([EMAIL PROTECTED]) (gcc version 4.1.3 20070518 (prerelease) (Debian 4.1.2-8)) #1 Sat May 26 14:30:26 CEST 2007 ** Not tainted ** Kernel log: sdf: Mode Sense: 27 00 00 00 sdf: assuming drive cache: write through sdf: [mac] sdf1 sdf2 sdf3 sdf4 sdf5 sdf6 sd 7:0:0:0: Attached scsi disk sdf sd 7:0:0:0: Attached scsi generic sg5 type 0 hfs: write access to a jounaled filesystem is not supported, use the force option at your own risk, mounting read-only. hfs: write access to a jounaled filesystem is not supported, use the force option at your own risk, mounting read-only. hfs: filesystem is marked journaled, leaving read-only. hfs: write access to a jounaled filesystem is not supported, use the force option at your own risk, mounting read-only. hfs: write access to a jounaled filesystem is not supported, use the force option at your own risk, mounting read-only. hfs: write access to a jounaled filesystem is not supported, use the force option at your own risk, mounting read-only. hfs: write access to a jounaled filesystem is not supported, use the force option at your own risk, mounting read-only. usb 2-1.2: USB disconnect, address 10 ieee1394: Node changed: 0-01:1023 - 0-00:1023 ieee1394: Node suspended: ID:BUS[0-00:1023] GUID[001010055b43] Synchronizing SCSI cache for disk sda: FAILED status = 0, message = 00, host = 1, driver = 00 6usb 2-1.3: reset full speed USB device using ohci_hcd and address 4 usb 1-1.2: reset full speed USB device using ohci_hcd and address 4 usb 2-1.4.3: reset full speed USB device using ohci_hcd and address 7 usb 2-1.3: reset full speed USB device using ohci_hcd and address 4 usb 1-1.2: reset full speed USB device using ohci_hcd and address 4 usb 1-1.2: reset full speed USB device using ohci_hcd and address 4 usb 2-1.3: reset full speed USB device using ohci_hcd and address 4 usb 1-1.2: reset full speed USB device using ohci_hcd and address 4 usb 2-1.4.3: reset full speed USB device using ohci_hcd and address 7 usb 1-1.2: reset full speed USB device using ohci_hcd and address 4 usb 2-1.3: reset full speed USB device using ohci_hcd and address 4 usb 2-1.3: reset full speed USB device using ohci_hcd and address 4 usb 1-1.2: reset full speed USB device using ohci_hcd and address 4 usb 2-1.4.3: reset full speed USB device using ohci_hcd and address 7 usb 1-1.2: reset full speed USB device using ohci_hcd and address 4 usb 2-1.4.3: reset full speed USB device using ohci_hcd and address 7 usb 1-1.2: reset full speed USB device using ohci_hcd and address 4 usb 1-1.2: reset full speed USB device using ohci_hcd and address 4 usb 2-1.3: reset full speed USB device using ohci_hcd and address 4 usb 1-1.2: reset full speed USB device using ohci_hcd and address 4 usb 2-1.3: reset full speed USB device using ohci_hcd and address 4 usb 1-1.2: reset full speed USB
Processing of kernel-image-2.6.8-sparc_2.6.8-16_sparc.changes
kernel-image-2.6.8-sparc_2.6.8-16_sparc.changes uploaded successfully to localhost along with the files: kernel-image-2.6.8-sparc_2.6.8-16.dsc kernel-image-2.6.8-sparc_2.6.8-16.tar.gz kernel-headers-2.6.8-4_2.6.8-16_sparc.deb kernel-headers-2.6.8-4-sparc32_2.6.8-16_sparc.deb kernel-image-2.6.8-4-sparc32_2.6.8-16_sparc.deb kernel-headers-2.6.8-4-sparc64_2.6.8-16_sparc.deb kernel-image-2.6.8-4-sparc64_2.6.8-16_sparc.deb kernel-headers-2.6.8-4-sparc64-smp_2.6.8-16_sparc.deb kernel-image-2.6.8-4-sparc64-smp_2.6.8-16_sparc.deb kernel-build-2.6.8-4_2.6.8-16_sparc.deb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processing of kernel-image-2.6.8-alpha_2.6.8-17_alpha.changes
kernel-image-2.6.8-alpha_2.6.8-17_alpha.changes uploaded successfully to localhost along with the files: kernel-image-2.6.8-alpha_2.6.8-17.dsc kernel-image-2.6.8-alpha_2.6.8-17.tar.gz kernel-headers-2.6.8-4_2.6.8-17_alpha.deb kernel-headers-2.6.8-4-smp_2.6.8-17_alpha.deb kernel-image-2.6.8-4-smp_2.6.8-17_alpha.deb kernel-headers-2.6.8-4-generic_2.6.8-17_alpha.deb kernel-image-2.6.8-4-generic_2.6.8-17_alpha.deb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processing of kernel-image-2.6.8-s390_2.6.8-6_s390.changes
kernel-image-2.6.8-s390_2.6.8-6_s390.changes uploaded successfully to localhost along with the files: kernel-image-2.6.8-s390_2.6.8-6.dsc kernel-image-2.6.8-s390_2.6.8-6.tar.gz kernel-patch-2.6.8-s390_2.6.8-6_all.deb kernel-headers-2.6.8-4_2.6.8-6_s390.deb kernel-image-2.6.8-4-s390_2.6.8-6_s390.deb kernel-image-2.6.8-4-s390x_2.6.8-6_s390.deb kernel-image-2.6.8-4-s390-tape_2.6.8-6_s390.deb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processing of kernel-image-2.6.8-amd64_2.6.8-17_i386.changes
kernel-image-2.6.8-amd64_2.6.8-17_i386.changes uploaded successfully to localhost along with the files: kernel-image-2.6.8-amd64_2.6.8-17.dsc kernel-image-2.6.8-amd64_2.6.8-17.tar.gz kernel-headers-2.6.8-13_2.6.8-17_i386.deb kernel-headers-2.6.8-13-amd64-k8_2.6.8-17_i386.deb kernel-image-2.6.8-13-amd64-k8_2.6.8-17_i386.deb kernel-headers-2.6.8-13-amd64-generic_2.6.8-17_i386.deb kernel-image-2.6.8-13-amd64-generic_2.6.8-17_i386.deb kernel-headers-2.6.8-13-em64t-p4_2.6.8-17_i386.deb kernel-image-2.6.8-13-em64t-p4_2.6.8-17_i386.deb kernel-headers-2.6.8-13-amd64-k8-smp_2.6.8-17_i386.deb kernel-image-2.6.8-13-amd64-k8-smp_2.6.8-17_i386.deb kernel-headers-2.6.8-13-em64t-p4-smp_2.6.8-17_i386.deb kernel-image-2.6.8-13-em64t-p4-smp_2.6.8-17_i386.deb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processing of kernel-patch-powerpc-2.6.8_2.6.8-13_powerpc.changes
kernel-patch-powerpc-2.6.8_2.6.8-13_powerpc.changes uploaded successfully to localhost along with the files: kernel-patch-powerpc-2.6.8_2.6.8-13.dsc kernel-patch-powerpc-2.6.8_2.6.8-13.tar.gz kernel-headers-2.6.8-4_2.6.8-13_powerpc.deb kernel-image-2.6.8-4-power3_2.6.8-13_powerpc.deb kernel-build-2.6.8-4-power3_2.6.8-13_powerpc.deb kernel-image-2.6.8-4-power3-smp_2.6.8-13_powerpc.deb kernel-build-2.6.8-4-power3-smp_2.6.8-13_powerpc.deb kernel-image-2.6.8-4-power4_2.6.8-13_powerpc.deb kernel-build-2.6.8-4-power4_2.6.8-13_powerpc.deb kernel-image-2.6.8-4-power4-smp_2.6.8-13_powerpc.deb kernel-build-2.6.8-4-power4-smp_2.6.8-13_powerpc.deb kernel-image-2.6.8-4-powerpc_2.6.8-13_powerpc.deb kernel-build-2.6.8-4-powerpc_2.6.8-13_powerpc.deb kernel-image-2.6.8-4-powerpc-smp_2.6.8-13_powerpc.deb kernel-build-2.6.8-4-powerpc-smp_2.6.8-13_powerpc.deb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processing of kernel-image-2.6.8-i386_2.6.8-17_i386.changes
kernel-image-2.6.8-i386_2.6.8-17_i386.changes uploaded successfully to localhost along with the files: kernel-image-2.6.8-i386_2.6.8-17.dsc kernel-image-2.6.8-i386_2.6.8-17.tar.gz kernel-headers-2.6.8-4_2.6.8-17_i386.deb kernel-headers-2.6.8-4-686_2.6.8-17_i386.deb kernel-image-2.6.8-4-686_2.6.8-17_i386.deb kernel-headers-2.6.8-4-k7-smp_2.6.8-17_i386.deb kernel-image-2.6.8-4-k7-smp_2.6.8-17_i386.deb kernel-headers-2.6.8-4-686-smp_2.6.8-17_i386.deb kernel-image-2.6.8-4-686-smp_2.6.8-17_i386.deb kernel-headers-2.6.8-4-k7_2.6.8-17_i386.deb kernel-image-2.6.8-4-k7_2.6.8-17_i386.deb kernel-headers-2.6.8-4-386_2.6.8-17_i386.deb kernel-image-2.6.8-4-386_2.6.8-17_i386.deb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processing of kernel-image-2.6.8-ia64_2.6.8-15_ia64.changes
kernel-image-2.6.8-ia64_2.6.8-15_ia64.changes uploaded successfully to localhost along with the files: kernel-image-2.6.8-ia64_2.6.8-15.dsc kernel-image-2.6.8-ia64_2.6.8-15.tar.gz kernel-headers-2.6.8-4_2.6.8-15_ia64.deb kernel-headers-2.6-itanium-smp_2.6.8-15_ia64.deb kernel-image-2.6-itanium-smp_2.6.8-15_ia64.deb kernel-headers-2.6.8-4-itanium-smp_2.6.8-15_ia64.deb kernel-image-2.6.8-4-itanium-smp_2.6.8-15_ia64.deb kernel-headers-2.6-mckinley-smp_2.6.8-15_ia64.deb kernel-image-2.6-mckinley-smp_2.6.8-15_ia64.deb kernel-headers-2.6.8-4-mckinley-smp_2.6.8-15_ia64.deb kernel-image-2.6.8-4-mckinley-smp_2.6.8-15_ia64.deb kernel-headers-2.6-itanium_2.6.8-15_ia64.deb kernel-image-2.6-itanium_2.6.8-15_ia64.deb kernel-headers-2.6.8-4-itanium_2.6.8-15_ia64.deb kernel-image-2.6.8-4-itanium_2.6.8-15_ia64.deb kernel-headers-2.6-mckinley_2.6.8-15_ia64.deb kernel-image-2.6-mckinley_2.6.8-15_ia64.deb kernel-headers-2.6.8-4-mckinley_2.6.8-15_ia64.deb kernel-image-2.6.8-4-mckinley_2.6.8-15_ia64.deb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processing of kernel-source-2.6.8_2.6.8-17_ia64.changes
kernel-source-2.6.8_2.6.8-17_ia64.changes uploaded successfully to localhost along with the files: kernel-source-2.6.8_2.6.8-17.dsc kernel-source-2.6.8_2.6.8-17.diff.gz kernel-patch-debian-2.6.8_2.6.8-17_all.deb kernel-source-2.6.8_2.6.8-17_all.deb kernel-tree-2.6.8_2.6.8-17_all.deb kernel-doc-2.6.8_2.6.8-17_all.deb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
kernel-image-2.6.8-s390_2.6.8-6_s390.changes is NEW
(new) kernel-headers-2.6.8-4_2.6.8-6_s390.deb optional devel Header files related to Linux kernel version 2.6.8 on IBM S/390 This package provides kernel header files for version 2.6.8 on IBM S/390, for sites that want the latest kernel headers. Please read /usr/share/doc/kernel-headers-2.6.8/debian.README.gz for details. (new) kernel-image-2.6.8-4-s390-tape_2.6.8-6_s390.deb extra base Linux kernel image for kernel version 2.6.8 on IBM S/390 This package contains the Linux kernel image for kernel version 2.6.8 on IBM S/390 and zSeries. . This kernel has support to IPL (boot) from a tape. (new) kernel-image-2.6.8-4-s390_2.6.8-6_s390.deb optional base Linux kernel image for kernel version 2.6.8 on IBM S/390 This package contains the Linux kernel image for kernel version 2.6.8 on IBM S/390 and zSeries, the corresponding System.map file, and the modules built by the packager. It also contains scripts that try to ensure that the system is not left in an unbootable state after an update. . This kernel has support to IPL (boot) from a VM reader or DASD device. . Kernel image packages are generally produced using kernel-package, and it is suggested that you install that package if you wish to create a custom kernel from the sources. (new) kernel-image-2.6.8-4-s390x_2.6.8-6_s390.deb optional base Linux kernel image for kernel version 2.6.8 on IBM zSeries. This package contains the Linux kernel image for kernel version 2.6.8 on IBM zSeries, the corresponding System.map file, and the modules built by the packager. It also contains scripts that try to ensure that the system is not left in a unbootable state after an update. . This kernel has support to IPL (boot) from a VM reader or DASD device. . Kernel image packages are generally produced using kernel-package, and it is suggested that you install that package if you wish to create a custom kernel from the sources. kernel-image-2.6.8-s390_2.6.8-6.dsc to pool/main/k/kernel-image-2.6.8-s390/kernel-image-2.6.8-s390_2.6.8-6.dsc kernel-image-2.6.8-s390_2.6.8-6.tar.gz to pool/main/k/kernel-image-2.6.8-s390/kernel-image-2.6.8-s390_2.6.8-6.tar.gz kernel-patch-2.6.8-s390_2.6.8-6_all.deb to pool/main/k/kernel-image-2.6.8-s390/kernel-patch-2.6.8-s390_2.6.8-6_all.deb Changes: kernel-image-2.6.8-s390 (2.6.8-6) oldstable; urgency=high . * Rebuild against kernel-tree-2.6.8-17 [ Simon Horman ] * drivers-net-via-rhine-wol-oops.dpatch (removed): This patch breaks the via-rhine driver and 2.6.8 and is completely bogus for this version of the kernel (closes: #311357) . * drivers-media-vidio-bttv-vc100xp-detect.dpatch Allow Leadtek WinFast VC100 XP cards to work. . * fs-jbd-checkpoint-assertion.dpatch Fix possible false assertion failure in log_do_checkpoint(). We might fail to detect that we actually made a progress when cleaning up the checkpoint lists if we don't retry after writing something to disk. . * mm-rmap-out-of-bounds-pte.dpatch Stop try_to_unmap_cluster() passing out-of-bounds pte to pte_unmap() . * net-ipv4-netfilter-ip_queue-deadlock.dpatch Fix deadlock with ip_queue and tcp local input path. . * asm-i386-mem-clobber.dpatch: Make sure gcc doesn't reorder memory accesses in strncmp and friends on i386. . * drivers-acpi-pci_irq-elcr.dpatch: Make sure we call acpi_register_gsi() even for default PCI interrupt assignment. That's the part that keeps track of the ELCR register, and we want to make sure that the PCI interrupts are properly marked level/low. . [ dann frazier ] * Merge in applicable fixes from 2.6.12.4 - netfilter-deadlock-ip6_queue.dpatch - rocket_c-fix-ldisc-ref-count.dpatch - early-vlan-fix.dpatch . [ Simon Horman ] * drivers-sata-promise-sataii_tx2_tx4.dpatch Add SATAII TX2 and TX2/TX4 support to sata promise driver (Closes: #317286) . * module-per-cpu-alignment-fix.dpatch Module per-cpu alignment cannot always be met From 2.6.12.5 . * genelink-usbnet-skb-typo.dpatch fix gl_skb/skb type error in genelink driver in usbnet Backported From 2.6.12.6 . * drivers-ide-ppp-pmac-build.dpatch Make sure BLK_DEV_IDEDMA_PCI is defined for pmac ide driver builds (closes: #321442) . * fs-ext3-nfs-parent-fix.dpatch ext3 file systems mounted over nfs may lookup .. in dx directories causing an oops. (closes: #323557) . * sparc-request_irq-in-RTC-fix.dpatch Use SA_SHIRQ in sparc specific code. From 2.6.13.1 . * forcedeth-init-link-settings-in-nv_open.patch forcedeth: Initialize link settings in every nv_open() From 2.6.13.2 . * fix-MPOL_F_VERIFY.patch Fix MPOL_F_VERIFY From 2.6.13.2 . * fix-more-byte-to-dword-writes-to-PCI_ROM_ADDRESS-config-word.patch Fix up more strange byte writes to the PCI_ROM_ADDRESS config word From 2.6.13.2
kernel-image-2.6.8-amd64_2.6.8-17_i386.changes is NEW
(new) kernel-headers-2.6.8-13-amd64-generic_2.6.8-17_i386.deb optional devel Linux kernel headers 2.6.8 for generic x86_64 systems This package provides kernel header files for version 2.6.8 on all x86_64 systems, for sites that want the latest kernel headers. Please read /usr/share/doc/kernel-headers-2.6.8-13-amd64-generic/debian.README.gz for details. (new) kernel-headers-2.6.8-13-amd64-k8-smp_2.6.8-17_i386.deb optional devel Linux kernel headers for version 2.6.8 on AMD64 SMP systems This package provides kernel header files for version 2.6.8 on AMD Opteron with SMP support, for sites that want the latest kernel headers. Please read /usr/share/doc/kernel-headers-2.6.8-13-amd64-k8-smp/debian.README.gz i for details. (new) kernel-headers-2.6.8-13-amd64-k8_2.6.8-17_i386.deb optional devel Linux kernel headers for version 2.6.8 on AMD64 systems This package provides kernel header files for version 2.6.8 on AMD Athlon64, Athlon FX and Opteron, for sites that want the latest kernel headers. Please read /usr/share/doc/kernel-headers-2.6.8-13-amd64-k8/debian.README.gz for details. (new) kernel-headers-2.6.8-13-em64t-p4-smp_2.6.8-17_i386.deb optional devel Linux kernel headers for version 2.6.8 on Intel EM64T SMP systems This package provides kernel header files for version 2.6.8 on all Intel P4 and Xeon systems with EM64T extension, for sites that want the latest kernel headers. Please read /usr/share/doc/kernel-headers-2.6.8-13-em64t-p4/debian.README.gz for details. (new) kernel-headers-2.6.8-13-em64t-p4_2.6.8-17_i386.deb optional devel Linux kernel headers for version 2.6.8 on Intel EM64T systems This package provides kernel header files for version 2.6.8 on all Intel Pentium 4 and Xeon systems with EM64T extension, for sites that want the latest kernel headers. Please read /usr/share/doc/kernel-headers-2.6.8-13-em64t-p4/debian.README.gz for details. (new) kernel-headers-2.6.8-13_2.6.8-17_i386.deb optional devel Header files related to Linux kernel version 2.6.8 This package provides kernel header files for version 2.6.8, for sites that want the latest kernel headers. Please read /usr/share/doc/kernel-headers-2.6.8-13/debian.README.gz for details. (new) kernel-image-2.6.8-13-amd64-generic_2.6.8-17_i386.deb optional base Linux kernel image for version 2.6.8 on generic x86_64 systems This package contains the Linux kernel image for version 2.6.8 on all x86_64 systems, the corresponding System.map file, and the modules built by the packager. It also contains scripts that try to ensure that the system is not left in a unbootable state after an update. . This is the amd64 installer kernel, running on all currently available x86_64 CPUs. . If you wish to update a bootdisk, or to use a bootloader to make installing and using the image easier, we suggest you install the latest fdutils (for formatting a floppy to be used as boot disk), and LILO, for a powerful bootloader. Of course, both these are optional. . Kernel image packages are generally produced using kernel-package, and it is suggested that you install that package if you wish to create a custom kernel from the sources. (new) kernel-image-2.6.8-13-amd64-k8-smp_2.6.8-17_i386.deb optional base Linux kernel image for version 2.6.8 on AMD64 SMP systems This package contains the Linux kernel image for version 2.6.8 on AMD Opteron, the corresponding System.map file, and the modules built by the packager. It also contains scripts that try to ensure that the system is not left in a unbootable state after an update. . If you have a multi-processor, AMD based 64bit system, you might want to install this kernel. . If you wish to update a bootdisk, or to use a bootloader to make installing and using the image easier, we suggest you install the latest fdutils (for formatting a floppy to be used as boot disk), and LILO, for a powerful bootloader. Of course, both these are optional. . Kernel image packages are generally produced using kernel-package, and it is suggested that you install that package if you wish to create a custom kernel from the sources. (new) kernel-image-2.6.8-13-amd64-k8_2.6.8-17_i386.deb optional base Linux kernel image for version 2.6.8 on AMD64 systems This package contains the Linux kernel image for version 2.6.8 on AMD Athlon64, Athlon FX and Opteron, the corresponding System.map file, and the modules built by the packager. It also contains scripts that try to ensure that the system is not left in a unbootable state after an update. . If you have a single-processor, AMD based 64bit system, you might want to install this kernel. . If you wish to update a bootdisk, or to use a bootloader to make installing and using the image easier, we suggest you install the latest fdutils (for formatting a floppy to be used as boot disk), and LILO, for a powerful bootloader. Of course, both these are optional. . Kernel image packages are generally produced using kernel-package, and it is
kernel-image-2.6.8-sparc_2.6.8-16_sparc.changes is NEW
(new) kernel-build-2.6.8-4_2.6.8-16_sparc.deb optional devel Headers for building modules for Linux 2.6.8 This package provides kernel header files for building modules for the precompiled kernel images on the 64-bit SPARC architecture (uniprocessor and multiprocessor.) (new) kernel-headers-2.6.8-4-sparc32_2.6.8-16_sparc.deb optional devel Header files for Linux kernel 2.6.8 on uniprocessor 32-bit SPARC This package provides kernel header files for version 2.6.8 on the 32-bit SPARC architecture, used to build out-of-tree kernel modules. If you have more than one processor, you want the kernel-headers-2.6.8-4-sparc64-smp package. (new) kernel-headers-2.6.8-4-sparc64-smp_2.6.8-16_sparc.deb optional devel Header files for Linux kernel 2.6.8 on multiprocessor 64-bit SPARC This package provides kernel header files for version 2.6.8 on the 64-bit SPARC architecture, used to build out-of-tree kernel modules. If you only have one processor, you want the kernel-headers-2.6.8-4-sparc64 package instead. (new) kernel-headers-2.6.8-4-sparc64_2.6.8-16_sparc.deb optional devel Header files for Linux kernel 2.6.8 on uniprocessor 64-bit SPARC This package provides kernel header files for version 2.6.8 on the 64-bit SPARC architecture, used to build out-of-tree kernel modules. If you have more than one processor, you want the kernel-headers-2.6.8-4-sparc64-smp package. (new) kernel-headers-2.6.8-4_2.6.8-16_sparc.deb optional devel Header files related to Linux kernel version 2.6.8 This package provides kernel header files for version 2.6.8, generally used for building out-of-tree kernel modules. See the 'module-assistant' package for more information. . This package consists mostly of the common files between the three header packages you should really be using for building modules: . - kernel-headers-2.6.8-4-sparc32 - kernel-headers-2.6.8-4-sparc64 - kernel-headers-2.6.8-4-sparc64-smp . For more information you can also read: /usr/share/doc/kernel-headers-2.6.8-4/debian.README.gz. (new) kernel-image-2.6.8-4-sparc32_2.6.8-16_sparc.deb optional base Linux kernel binary image for Super/HyperSPARC (sparc32) systems This package contains the Linux kernel image, the System.map file, and the modules built by the packager. It also contains scripts that try to ensure that the system is not left in a unbootable state after an update. . If you wish to update a bootdisk, or to use a bootloader to make installing and using the image easier, we suggest you install the latest fdutils (for formatting a floppy to be used as boot disk), and LILO, for a powerful bootloader. Of course, both these are optional. . Kernel image packages are generally produced using kernel-package, and it is suggested that you install that package if you wish to create a custom kernel from the sources. . NOTE: This kernel is strictly for 32-bit Super/HyperSPARC (sun4m) class systems. If you do not have a SuperSPARC or HyperSPARC CPU, then most likely you want the sparc64 image. See kernel-image-2.6-sparc64. (new) kernel-image-2.6.8-4-sparc64-smp_2.6.8-16_sparc.deb optional base Linux kernel binary image for SMP UltraSPARC (sparc64) systems This package contains the Linux kernel image, the System.map file, and the modules built by the packager. It also contains scripts that try to ensure that the system is not left in a unbootable state after an update. . If you wish to update a bootdisk, or to use a bootloader to make installing and using the image easier, we suggest you install the latest fdutils (for formatting a floppy to be used as boot disk), and LILO, for a powerful bootloader. Of course, both these are optional. . Kernel image packages are generally produced using kernel-package, and it is suggested that you install that package if you wish to create a custom kernel from the sources. . NOTE: This kernel is strictly for UltraSPARC (sparc64) class systems. If you do not have an UltraSPARC, then most likely you want the sparc32 image, which only exists for the 2.4 kernel series. See kernel-image-2.4-sparc32. Also, this kernel is specifically for SMP (multiple processors) systems. If you do not have more than one CPU, then choose the non-SMP kernel image. (new) kernel-image-2.6.8-4-sparc64_2.6.8-16_sparc.deb optional base Linux kernel binary image for UltraSPARC (sparc64) systems This package contains the Linux kernel image, the System.map file, and the modules built by the packager. It also contains scripts that try to ensure that the system is not left in a unbootable state after an update. . If you wish to update a bootdisk, or to use a bootloader to make installing and using the image easier, we suggest you install the latest fdutils (for formatting a floppy to be used as boot disk), and LILO, for a powerful bootloader. Of course, both these are optional. . Kernel image packages are generally produced using kernel-package, and it is suggested that you install that package if
kernel-image-2.6.8-alpha_2.6.8-17_alpha.changes is NEW
(new) kernel-headers-2.6.8-4-generic_2.6.8-17_alpha.deb optional devel Linux kernel headers 2.6.8 on Alpha This package provides kernel header files for version 2.6.8 on the Alpha architecture, for sites that want the latest kernel headers. Please read /usr/share/doc/kernel-headers-2.6.8-4-generic/debian.README.gz for details (new) kernel-headers-2.6.8-4-smp_2.6.8-17_alpha.deb optional devel Linux kernel headers 2.6.8 on Alpha SMP This package provides kernel header files for version 2.6.8 on the Alpha architecture with SMP support, for sites that want the latest kernel headers. SMP (symmetric multi-processing) is needed if you have multiple processors. Please read /usr/share/doc/kernel-headers-2.6.8-4-smp/debian.README.gz for details (new) kernel-headers-2.6.8-4_2.6.8-17_alpha.deb optional devel Header files related to Linux kernel version 2.6.8 This package provides kernel header files for version 2.6.8, for sites that want the latest kernel headers. Please read /usr/share/doc/kernel-headers-2.6.8-4/debian.README.gz for details (new) kernel-image-2.6.8-4-generic_2.6.8-17_alpha.deb optional base Linux kernel image for version 2.6.8 on Alpha. This package contains the Linux kernel image for version 2.6.8 on the Alpha architecture, the corresponding System.map file, and the modules built by the packager. It also contains scripts that try to ensure that the system is not left in a unbootable state after an update. . If you wish to update a bootdisk, or to use a bootloader to make installing and using the image easier, we suggest you install the latest fdutils (for formatting a floppy to be used as boot disk), and LILO, for a powerful bootloader. Of course, both these are optional. . Kernel image packages are generally produced using kernel-package, and it is suggested that you install that package if you wish to create a custom kernel from the sources. (new) kernel-image-2.6.8-4-smp_2.6.8-17_alpha.deb optional base Linux kernel image for version 2.6.8 on Alpha SMP. This package contains the Linux kernel image for version 2.6.8 on the Alpha architecture with SMP support, the corresponding System.map file, and the modules built by the packager. SMP (symmetric multi-processing) is needed if you have multiple processors. It also contains scripts that try to ensure that the system is not left in a unbootable state after an update. . If you wish to update a bootdisk, or to use a bootloader to make installing and using the image easier, we suggest you install the latest fdutils (for formatting a floppy to be used as boot disk), and LILO, for a powerful bootloader. Of course, both these are optional. . Kernel image packages are generally produced using kernel-package, and it is suggested that you install that package if you wish to create a custom kernel from the sources. kernel-image-2.6.8-alpha_2.6.8-17.dsc to pool/main/k/kernel-image-2.6.8-alpha/kernel-image-2.6.8-alpha_2.6.8-17.dsc kernel-image-2.6.8-alpha_2.6.8-17.tar.gz to pool/main/k/kernel-image-2.6.8-alpha/kernel-image-2.6.8-alpha_2.6.8-17.tar.gz Changes: kernel-image-2.6.8-alpha (2.6.8-17) oldstable; urgency=high . * Rebuild against kernel-tree-2.6.8-17 [ Simon Horman ] * drivers-net-via-rhine-wol-oops.dpatch (removed): This patch breaks the via-rhine driver and 2.6.8 and is completely bogus for this version of the kernel (closes: #311357) . * drivers-media-vidio-bttv-vc100xp-detect.dpatch Allow Leadtek WinFast VC100 XP cards to work. . * fs-jbd-checkpoint-assertion.dpatch Fix possible false assertion failure in log_do_checkpoint(). We might fail to detect that we actually made a progress when cleaning up the checkpoint lists if we don't retry after writing something to disk. . * mm-rmap-out-of-bounds-pte.dpatch Stop try_to_unmap_cluster() passing out-of-bounds pte to pte_unmap() . * net-ipv4-netfilter-ip_queue-deadlock.dpatch Fix deadlock with ip_queue and tcp local input path. . * asm-i386-mem-clobber.dpatch: Make sure gcc doesn't reorder memory accesses in strncmp and friends on i386. . * drivers-acpi-pci_irq-elcr.dpatch: Make sure we call acpi_register_gsi() even for default PCI interrupt assignment. That's the part that keeps track of the ELCR register, and we want to make sure that the PCI interrupts are properly marked level/low. . [ dann frazier ] * Merge in applicable fixes from 2.6.12.4 - netfilter-deadlock-ip6_queue.dpatch - rocket_c-fix-ldisc-ref-count.dpatch - early-vlan-fix.dpatch . [ Simon Horman ] * drivers-sata-promise-sataii_tx2_tx4.dpatch Add SATAII TX2 and TX2/TX4 support to sata promise driver (Closes: #317286) . * module-per-cpu-alignment-fix.dpatch Module per-cpu alignment cannot always be met From 2.6.12.5 . * genelink-usbnet-skb-typo.dpatch fix gl_skb/skb type error in genelink
Bug#426114: marked as done (Module Ide_cd missing/error messages)
Your message dated Mon, 28 May 2007 19:06:58 +0200 with message-id [EMAIL PROTECTED] and subject line Problem might be due to defect sectors has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: linux-source-2.6.18 Version: 2.6.18.dfsg.1-12etch2 Dear Debian-Co-worker! If I compile a new kernel with this version, I get a bunch of error-messages at boot concerning ide_cd [1]. I still had a deb-package made with an older version of this package, so I was able to test this one as well. The result: The error messages do not show up, so I suspect that this is some kind of bug/due to changes in the packages. Modeprobe ide_cd does not work either, i.e. it seems to be missing. If it is of any use to you, I could compile a new kernel and sent the relevant screen outputs (during compiling) to you. In this spirit With thanks and best wishes Yours Gernot --- [1] ide_cd: Unknown symbol register_cdrom ide_cd: Unknown symbol cdrom_ioctl ide_cd: Unknown symbol cdrom_mode_select ide_cd: Unknown symbol cdrom_media_changed ide_cd: Unknown symbol cdrom_get_last_written ide_cd: Unknown symbol cdrom_mode_sense ide_cd: Unknown symbol cdrom_get_media_event ide_cd: Unknown symbol cdrom_release ide_cd: Unknown symbol cdrom_open ide_cd: Unknown symbol unregister_cdrom ide_cd: Unknown symbol cdrom_number_of_slots ---End Message--- ---BeginMessage--- Dear Co-Worker! I think that the problem has been a result of a corrupt module (i.e. residing in a bad sector of the disk ) in this spirit Yours Gernot ---End Message---
kernel-patch-powerpc-2.6.8_2.6.8-13_powerpc.changes is NEW
(new) kernel-build-2.6.8-4-power3-smp_2.6.8-13_powerpc.deb optional devel build infrastructure for kernel version 2.6.8-4-power3-smp . Together with kernel-headers-2.6.8-4, this package provides the infrastructure for building additional modules for 2.6.8-4-power3-smp. (new) kernel-build-2.6.8-4-power3_2.6.8-13_powerpc.deb optional devel build infrastructure for kernel version 2.6.8-4-power3 . Together with kernel-headers-2.6.8-4, this package provides the infrastructure for building additional modules for 2.6.8-4-power3. (new) kernel-build-2.6.8-4-power4-smp_2.6.8-13_powerpc.deb optional devel build infrastructure for kernel version 2.6.8-4-power4-smp . Together with kernel-headers-2.6.8-4, this package provides the infrastructure for building additional modules for 2.6.8-4-power4-smp. (new) kernel-build-2.6.8-4-power4_2.6.8-13_powerpc.deb optional devel build infrastructure for kernel version 2.6.8-4-power4 . Together with kernel-headers-2.6.8-4, this package provides the infrastructure for building additional modules for 2.6.8-4-power4. (new) kernel-build-2.6.8-4-powerpc-smp_2.6.8-13_powerpc.deb optional devel build infrastructure for kernel version 2.6.8-4-powerpc-smp . Together with kernel-headers-2.6.8-4, this package provides the infrastructure for building additional modules for 2.6.8-4-powerpc-smp. (new) kernel-build-2.6.8-4-powerpc_2.6.8-13_powerpc.deb optional devel build infrastructure for kernel version 2.6.8-4-powerpc . Together with kernel-headers-2.6.8-4, this package provides the infrastructure for building additional modules for 2.6.8-4-powerpc. (new) kernel-headers-2.6.8-4_2.6.8-13_powerpc.deb optional devel header files for the Linux kernel version 2.6.8-4 . This package provides kernel headers files for 2.6.8-4. (new) kernel-image-2.6.8-4-power3-smp_2.6.8-13_powerpc.deb optional base Linux kernel image for 2.6.8-4-power3-smp . This package contains the Linux kernel for version 2.6.8-4-power3-smp. It is intended to be run on PowerPC machines with two or more Power3 processors, like some IBM RS/6000 boxen. (new) kernel-image-2.6.8-4-power3_2.6.8-13_powerpc.deb optional base Linux kernel image for 2.6.8-4-power3 . This package contains the Linux kernel for version 2.6.8-4-power3. It is intended to be run on PowerPC machines with a single Power3 processor. (new) kernel-image-2.6.8-4-power4-smp_2.6.8-13_powerpc.deb optional base Linux kernel image for 2.6.8-4-power4-smp . This package contains the Linux kernel for version 2.6.8-4-power4-smp. It is intended to be run on PowerPC machines with two or more Power4 processors. This setup can be found in Apple's dual G5 PowerMacs, as well as in a number of IBM RS/6000 boxen, such as the iSeries and pSeries machines. (new) kernel-image-2.6.8-4-power4_2.6.8-13_powerpc.deb optional base Linux kernel image for 2.6.8-4-power4 . This package contains the Linux kernel for version 2.6.8-4-power4. It is intended to be run on PowerPC machines with a single Power4 processor, the most prominent example being the G5 PowerMac by Apple. (new) kernel-image-2.6.8-4-powerpc-smp_2.6.8-13_powerpc.deb optional base Linux kernel image for 2.6.8-4-powerpc-smp . This package contains the Linux kernel for version 2.6.8-4-powerpc-smp. It is intended to be run on most dual-processor PowerPC machines, most notably the Dual G4 PowerMacs by Apple. (new) kernel-image-2.6.8-4-powerpc_2.6.8-13_powerpc.deb optional base Linux kernel image for 2.6.8-4-powerpc . This package contains the Linux kernel for version 2.6.8-4-powerpc. It is intended to be run on single-processor PowerPC machines, including all G3 and G4 models by Apple, as well as older PowerMacs. kernel-patch-powerpc-2.6.8_2.6.8-13.dsc to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-patch-powerpc-2.6.8_2.6.8-13.dsc kernel-patch-powerpc-2.6.8_2.6.8-13.tar.gz to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-patch-powerpc-2.6.8_2.6.8-13.tar.gz Changes: kernel-patch-powerpc-2.6.8 (2.6.8-13) oldstable; urgency=high . * Rebuild against kernel-tree-2.6.8-17 [ Simon Horman ] * drivers-net-via-rhine-wol-oops.dpatch (removed): This patch breaks the via-rhine driver and 2.6.8 and is completely bogus for this version of the kernel (closes: #311357) . * drivers-media-vidio-bttv-vc100xp-detect.dpatch Allow Leadtek WinFast VC100 XP cards to work. . * fs-jbd-checkpoint-assertion.dpatch Fix possible false assertion failure in log_do_checkpoint(). We might fail to detect that we actually made a progress when cleaning up the checkpoint lists if we don't retry after writing something to disk. . * mm-rmap-out-of-bounds-pte.dpatch Stop try_to_unmap_cluster() passing out-of-bounds pte to pte_unmap() . * net-ipv4-netfilter-ip_queue-deadlock.dpatch Fix deadlock with ip_queue and tcp local input path. . * asm-i386-mem-clobber.dpatch: Make sure gcc doesn't reorder memory accesses in strncmp and
Re: Another level of agression ?
On Monday 28 May 2007 16:19, Sven Luther wrote: Hi ! I'm not involved in your job at all, but I am a member of debian-kernel list because I like to read about : What is new in this area ? What I can see here is only personal issues unfortunately. I am telling You it is not worth it... People you are professionals !!! you should work and think how I should solve this problem or how I should solve out that one... . Listen, I know something about C and C++ programming and I have to much free time but even with this nobody probably will not invite me to the team like You have created, so I feel myself very pour reading about things like that... Regards Pawel Krzywicki On Mon, May 28, 2007 at 01:03:29PM +0200, Joey Schulze wrote: Sven Luther wrote: After some more pressure on IRC, your commit access has been restored. It is not enough, i want the suspension revoked, since it was a stupid decision, which has achieved nothing except worsen the situation, and was taken contrary to the DAMs procedure, and in a shady and mysterious way. Oh come on Sven! This thread was about the accidential removal of your kernel team commit access. It has been restored since them. The problem is fixed. The wider problem has been there since marsch last year or so, and it was never fixed. Tell you what, if you continue trolling and ranting here, sooner or later your commit access will be removed *on purpose* with no way for you to get it back. This is not a threat but a warning. Yeah, right, is it so difficult to solve this as it should have been ? Do you really believe there is any valid justification to having me suspended for a year despite the 70:7 strong opposition of the DDs who where asked to express themselves ? What did it gain, and what was the reason that made the DAMs decide this way ? Appart that the expulsers provided more hatefull and agressive quotes than the those opposing the expulsion, and the DAMs chose to put them in value. Do you believe it was correct for the expulsers to ask for my expulsion on the day after i proposed my DPL candidacy, while i had not posted a single post on the debian lists for over a month ? And that the DAMs chose to hide this for whatevr obscure reason ? We know that you're not happy with the situation, but continueing to bring it up will not solve it either. Please don't reply and work on important things instead. Yeah, right, which is what i have been trying to do since over a year, first i worked, and provided over 30 or so patches to d-i despite the d-i access removal, just to get bashed in half the report by a clueless frans who jumped on every little excuse to explode, and finally made some under-hand manipulation with the ftp-masters to remove my upload right of the .udebs. This is what i did when i wrote the wiki page : http://wiki.debian.org/DebianInstaller/FransPopAndOthersVs%2eSvenLutherIssu e and got FUCK YOU and the biggest load of self-satisfied and self-centered crap I've ever seen from frans, and abuse from geert and holger (which they removed in shame later on), and blackmail of joeyh in return. This is what i did in february, organizing hardware for the debian booth, passing time to prepare the ps3 debian install, on the ps3 that geert uutyeroven had arranged, and geert stappers or holger found the occasion to bash me when i once posted to the list by mistake while searching for a TV set. I did this while those hateful expulsers secretely where scheming to restart the expulsion procedure, while on saturday evening the DAMs had sent me a mail which got eaten by the debian.org mail greylisting or whatever, and while i spoke to James Troup on sunday afternoon, after having hold a discussion about the future possibilities of the kernel developments, of which nobody from the d-i team assisted except holger, who was forced to film, and frans passed by me without returning my greeting afterward. I did this while the expulsion process was underway and posted only few select mails, and even was mostly silent for the week or two that followed the end of the support mail period, waiting for the DAMs to decide in frustration and trauma, while Frans started agressing me on the lists again. I was doing this when i discovered this latest case. So, for me, now, in debian, the most important thing, is that this continuous agression are stopped, that each party in this is blamed accordying to their responsabilities, in a fair and equitable way, and that the one-sided punishment are lifted, and that we are all allowed to work on the parts of debian that we like and code all happily forever after. Can you tell me a single reason why this should not happen ? Can you tell me a single reason that justifies the DAMs decision to act as they did, and which can be named without shame (i know that one reason of the decision is the fact that the other party
Bug#422273: marked as done (xserver-xorg-input-evdev: Num Lock light indicator stopped functioning)
Your message dated Mon, 28 May 2007 12:49:09 -0500 with message-id [EMAIL PROTECTED] and subject line Bug#422273: xserver-xorg-input-evdev: Num Lock light indicator stopped functioning has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: xserver-xorg-input-evdev Version: 1:1.1.5-2 Severity: normal Upgrading to the kernel indicated below, the Num Lock light indicator on a Microsoft Natural Ergonomic keyboard stopped functioning. The indicator light is on during booting and initial KDM startup. It is turned off shortly after, and typing the Num Lock key works but the light does not. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.20-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages xserver-xorg-input-evdev depends on: ii libc6 2.5-5GNU C Library: Shared libraries ii xserver-xorg-core 2:1.3.0.0.dfsg-3 X.Org X server -- core server xserver-xorg-input-evdev recommends no packages. -- no debconf information Cheers, -- Seb ---End Message--- ---BeginMessage--- Version: 2.6.21-1-amd64 Upgrade to linux-image-2.6.21-1-amd64 fixed this bug. -- Seb ---End Message---
Re: Another level of agression ?
On Mon, May 28, 2007 at 06:11:29PM +0100, Paweł Krzywicki wrote: On Monday 28 May 2007 16:19, Sven Luther wrote: Hi ! I'm not involved in your job at all, but I am a member of debian-kernel list because I like to read about : What is new in this area ? What I can see here is only personal issues unfortunately. I am telling You it is not worth it... People you are professionals !!! you should work and think how I should solve this problem or how I should solve out that one... . No, we are volunteers, who do this out of our free time and work. Listen, I know something about C and C++ programming and I have to much free time but even with this nobody probably will not invite me to the team like You have created, so I feel myself very pour reading about things like that... I would have invited you, i was for an open and friendly team and an open and friendly debian, but see what it did bring me. Saddened, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#409616: kernel-image-2.6-em64t-p4-smp: Bug can be closed
Package: kernel-image-2.6-em64t-p4-smp Followup-For: Bug #409616 As kdetv does not crash my machine now, when using the correct kernel image package linux-image-2.6.20-1-amd64_2.6.20-3, this bug can be closed. Best regards Torquil Sørensen -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.21-1-686 (SMP w/1 CPU core) Locale: LANG=no_NO.UTF-8, LC_CTYPE=no_NO.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages kernel-image-2.6-em64t-p4-smp depends on: pn linux-image-2.6-amd64 none (no description available) kernel-image-2.6-em64t-p4-smp recommends no packages. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#426432: Instable loading of modules
Package: linux-source-2.6.18 Version: 2.6.18.dfsg.1-12etch2 Dear Co-Worker! Well I actually do not know who to blame, but my system shows some strange behaviour during booting. On Saturday, it claimed that ide_cd is missing, yesterday I have got a lot of hda: dma_intr: status=0x58-error messages, and today it prints alarms concerning the lp and the ppdev-modules. Those matters are most readily explained through the logs and therefore I have attached the kern.log and the boot-log of two boot-process (sorry for that faux pas). The kern.log contains the results of three boot processes. The first one showing the already-mentioned dma:intr-errors. The second and the third one (20:27 and 20:29) show the results of booting the same kernel twice (one time with errors and one time without any errors). boot and boot.0 correspond to these boot-process -for some reason also the time is set into the future. I think that there is something profoundly wrong with loading the modules, since it works one time and does not the other. In this spirit Yours Gernot boot.gz Description: GNU Zip compressed data kern.log.gz Description: GNU Zip compressed data boot.0.gz Description: GNU Zip compressed data
Re: Another level of agression ?
On Monday 28 May 2007 19:06, Sven Luther wrote: No, we are volunteers, who do this out of our free time and work. I know this ... But I am saying that you should not be concentrated on some kind of silly fights... Listen, I know something about C and C++ programming and I have to much free time but even with this nobody probably will not invite me to the team like You have created, so I feel myself very pour reading about things like that... I would have invited you, i was for an open and friendly team and an open and friendly debian, but see what it did bring me. Ok probably you are older then I am so I will leave this as it is ... Regards Pawel -- Etch Debian User: PawelatWartandotorg kadu:3735326 Registered Linux User : 406139 |PLUG :1966491030 GnuPG | pub 1024D/2AAB159B Home Page: http://www.wartan.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#426432: Somewhat similar problem:Bug#333522
Dear Co-Workers! Bug#33522 [1] might not be of relevance but it characterizes my problems pretty good. In this spirit Yours Gernot --- [1] http://groups.google.com/group/linux.debian.bugs.dist/browse_thread/thread/554a7a34bf236bbe/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#426440: /usr/sbin/pppd: sometimes connection with Option GlobeTrotter card hangs, ping: sendmsg: No buffer space available
reassign 426440 linux-2.6 thanks On May 28, Miernik [EMAIL PROTECTED] wrote: ping: sendmsg: No buffer space available Not related to user space unless the contrary is proven. -- ciao, Marco signature.asc Description: Digital signature
Processed: Re: Bug#426440: /usr/sbin/pppd: sometimes connection with Option GlobeTrotter card hangs, ping: sendmsg: No buffer space available
Processing commands for [EMAIL PROTECTED]: reassign 426440 linux-2.6 Bug#426440: /usr/sbin/pppd: sometimes connection with Option GlobeTrotter card hangs, ping: sendmsg: No buffer space available Bug reassigned from package `ppp' to `linux-2.6'. 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#425136: [: 42: ==: unexpected operator
On Sun, 27 May 2007, Rafal Czlonka wrote: maximilian attems wrote: hmmm never seen, can you pleas post the output of sh -x mkinitramfs-kpkg + set -eu snipp thanks and urrgs please post output of sh -x mkinitramfs-kpkg -o /tmp/fooo -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#426446: MODULES=dep fails with renamed cryptodevices
Package: initramfs-tools Version: 0.88 Severity: important After upgrade to 0.88 (it works with etch's 0.87b), I cannot create initramfs anymore: update-initramfs: Generating /boot/initrd.img-2.6.18-4-686 Error: missing mapper/cr_hda root /dev/mapper/cr_hda5 /sys entry The root seems to be MODULES=dep and the new /sys parsing code. If I set MODULES=most, it works. Also, it seems to matter that I have renamed dm-0 as mapper/cr_hda5: lapse:..share/initramfs-tools# ls -l /dev/mapper/cr_hda4 /dev/dm-0 brw-rw 1 root disk 254, 0 2007-05-28 22:53 /dev/mapper/cr_hda5 brw-rw 1 root disk 254, 0 2007-05-28 22:52 /dev/dm-0 As per maks' request, here is the mkinitramfs trace, ls -l /sys/block and mount output. If you need any more information, I can reproduce this at will. lapse:..share/initramfs-tools# ls -l /sys/block total 0 drwxr-xr-x 4 root root 0 2007-05-28 22:53 dm-0/ drwxr-xr-x 4 root root 0 2007-05-28 22:53 dm-1/ drwxr-xr-x 4 root root 0 2007-05-28 22:53 dm-2/ drwxr-xr-x 4 root root 0 2007-05-28 22:53 dm-3/ drwxr-xr-x 4 root root 0 2007-05-28 23:10 dm-4/ drwxr-xr-x 4 root root 0 2007-05-28 22:53 dm-5/ drwxr-xr-x 13 root root 0 2007-05-28 22:53 hda/ drwxr-xr-x 4 root root 0 2007-05-28 22:52 ram0/ drwxr-xr-x 4 root root 0 2007-05-28 22:52 ram1/ drwxr-xr-x 4 root root 0 2007-05-28 22:52 ram10/ drwxr-xr-x 4 root root 0 2007-05-28 22:52 ram11/ drwxr-xr-x 4 root root 0 2007-05-28 22:52 ram12/ drwxr-xr-x 4 root root 0 2007-05-28 22:52 ram13/ drwxr-xr-x 4 root root 0 2007-05-28 22:52 ram14/ drwxr-xr-x 4 root root 0 2007-05-28 22:52 ram15/ drwxr-xr-x 4 root root 0 2007-05-28 22:52 ram2/ drwxr-xr-x 4 root root 0 2007-05-28 22:52 ram3/ drwxr-xr-x 4 root root 0 2007-05-28 22:52 ram4/ drwxr-xr-x 4 root root 0 2007-05-28 22:52 ram5/ drwxr-xr-x 4 root root 0 2007-05-28 22:52 ram6/ drwxr-xr-x 4 root root 0 2007-05-28 22:52 ram7/ drwxr-xr-x 4 root root 0 2007-05-28 22:52 ram8/ drwxr-xr-x 4 root root 0 2007-05-28 22:52 ram9/ lapse:..share/initramfs-tools# mount #[1,358] /dev/mapper/cr_hda5 on / type auto (rw,noatime,errors=remount-ro,acl,user_xattr,barrier=1) tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755) proc on /proc type proc (rw,noexec,nosuid,nodev) sysfs on /sys type sysfs (rw,noexec,nosuid,nodev) procbususb on /proc/bus/usb type usbfs (rw) udev on /dev type tmpfs (rw,mode=0755) tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev) devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620) fusectl on /sys/fs/fuse/connections type fusectl (rw) /dev/hda1 on /boot type ext3 (rw,noexec,nosuid,nodev,noatime,acl,user_xattr,barrier=1) /dev/mapper/cr_hda9 on /home type ext3 (rw,nosuid,nodev,acl,user_xattr,barrier=1) /dev/mapper/cr_hda7 on /tmp type ext3 (rw,nosuid,nodev,acl,user_xattr,barrier=1) /dev/mapper/cr_hda6 on /usr type ext3 (rw,nodev,noatime,acl,user_xattr,barrier=1) /dev/mapper/cr_hda8 on /var type ext3 (rw,acl,user_xattr,barrier=1) lapse:..share/initramfs-tools# sh -x /usr/sbin/mkinitramfs -v -o /dev/null #[363] + umask 0022 + export PATH=/usr/bin:/sbin:/bin + keep=n + CONFDIR=/etc/initramfs-tools + verbose=n + errors_to=2/dev/null + BUSYBOXDIR=/bin + getopt -o d:ko:r:v --long supported-host-version:,supported-target-version: -n /usr/sbin/mkinitramfs -- -v -o /dev/null + OPTIONS= -v -o '/dev/null' -- + [ 0 != 0 ] + eval set -- -v -o '/dev/null' -- + set -- -v -o /dev/null -- + true + verbose=y + shift + true + outfile=/dev/null + shift 2 + true + shift + break + [ -n ] + [ -n ] + . /usr/share/initramfs-tools/scripts/functions + . /usr/share/initramfs-tools/hook-functions + . /etc/initramfs-tools/initramfs.conf + MODULES=dep + BUSYBOX=y + KEYMAP=n + BOOT=local + DEVICE=eth0 + NFSROOT=auto + EXTRA_CONF= + basename /usr/share/initramfs-tools/conf.d/cryptsetup + grep -v \.dpkg-.*$ + grep ^[[:alnum:]][[:alnum:]\._-]*$ + EXTRA_CONF= cryptsetup + basename /usr/share/initramfs-tools/conf.d/uswsusp + grep ^[[:alnum:]][[:alnum:]\._-]*$ + grep -v \.dpkg-.*$ + EXTRA_CONF= cryptsetup uswsusp + basename /etc/initramfs-tools/conf.d/resume + grep ^[[:alnum:]][[:alnum:]\._-]*$ + grep -v \.dpkg-.*$ + EXTRA_CONF= cryptsetup uswsusp resume + [ -e /etc/initramfs-tools/conf.d/cryptsetup ] + [ -e /usr/share/initramfs-tools/conf.d/cryptsetup ] + . /usr/share/initramfs-tools/conf.d/cryptsetup + KEYMAP=y + [ -e /etc/initramfs-tools/conf.d/uswsusp ] + [ -e /usr/share/initramfs-tools/conf.d/uswsusp ] + . /usr/share/initramfs-tools/conf.d/uswsusp + KEYMAP=y + [ -e /etc/initramfs-tools/conf.d/resume ] + . /etc/initramfs-tools/conf.d/resume + [ -n ] + [ -z /dev/null ] + touch /dev/null + readlink -f /dev/null + outfile=/dev/null + [ 0 -ne 1 ] + uname -r + version=2.6.18-4-686 + check_minkver 2.6.18-4-686 + curversion=2.6.18-4-686 + initdir= + [ -z ] + dpkg --print-installation-architecture + DPKG_ARCH=i386 + minversion=2.6.12 + dpkg --compare-versions 2.6.18-4-686 lt 2.6.12 + return 0 + check_minkver
kernel-patch-powerpc-2.6.8_2.6.8-13_powerpc.changes ACCEPTED
Accepted: kernel-build-2.6.8-4-power3-smp_2.6.8-13_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-build-2.6.8-4-power3-smp_2.6.8-13_powerpc.deb kernel-build-2.6.8-4-power3_2.6.8-13_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-build-2.6.8-4-power3_2.6.8-13_powerpc.deb kernel-build-2.6.8-4-power4-smp_2.6.8-13_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-build-2.6.8-4-power4-smp_2.6.8-13_powerpc.deb kernel-build-2.6.8-4-power4_2.6.8-13_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-build-2.6.8-4-power4_2.6.8-13_powerpc.deb kernel-build-2.6.8-4-powerpc-smp_2.6.8-13_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-build-2.6.8-4-powerpc-smp_2.6.8-13_powerpc.deb kernel-build-2.6.8-4-powerpc_2.6.8-13_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-build-2.6.8-4-powerpc_2.6.8-13_powerpc.deb kernel-headers-2.6.8-4_2.6.8-13_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-headers-2.6.8-4_2.6.8-13_powerpc.deb kernel-image-2.6.8-4-power3-smp_2.6.8-13_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-image-2.6.8-4-power3-smp_2.6.8-13_powerpc.deb kernel-image-2.6.8-4-power3_2.6.8-13_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-image-2.6.8-4-power3_2.6.8-13_powerpc.deb kernel-image-2.6.8-4-power4-smp_2.6.8-13_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-image-2.6.8-4-power4-smp_2.6.8-13_powerpc.deb kernel-image-2.6.8-4-power4_2.6.8-13_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-image-2.6.8-4-power4_2.6.8-13_powerpc.deb kernel-image-2.6.8-4-powerpc-smp_2.6.8-13_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-image-2.6.8-4-powerpc-smp_2.6.8-13_powerpc.deb kernel-image-2.6.8-4-powerpc_2.6.8-13_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-image-2.6.8-4-powerpc_2.6.8-13_powerpc.deb kernel-patch-powerpc-2.6.8_2.6.8-13.dsc to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-patch-powerpc-2.6.8_2.6.8-13.dsc kernel-patch-powerpc-2.6.8_2.6.8-13.tar.gz to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-patch-powerpc-2.6.8_2.6.8-13.tar.gz Override entries for your package: kernel-build-2.6.8-4-power3-smp_2.6.8-13_powerpc.deb - optional devel kernel-build-2.6.8-4-power3_2.6.8-13_powerpc.deb - optional devel kernel-build-2.6.8-4-power4-smp_2.6.8-13_powerpc.deb - optional devel kernel-build-2.6.8-4-power4_2.6.8-13_powerpc.deb - optional devel kernel-build-2.6.8-4-powerpc-smp_2.6.8-13_powerpc.deb - optional devel kernel-build-2.6.8-4-powerpc_2.6.8-13_powerpc.deb - optional devel kernel-headers-2.6.8-4_2.6.8-13_powerpc.deb - optional devel kernel-image-2.6.8-4-power3-smp_2.6.8-13_powerpc.deb - optional base kernel-image-2.6.8-4-power3_2.6.8-13_powerpc.deb - optional base kernel-image-2.6.8-4-power4-smp_2.6.8-13_powerpc.deb - optional base kernel-image-2.6.8-4-power4_2.6.8-13_powerpc.deb - optional base kernel-image-2.6.8-4-powerpc-smp_2.6.8-13_powerpc.deb - optional base kernel-image-2.6.8-4-powerpc_2.6.8-13_powerpc.deb - optional base kernel-patch-powerpc-2.6.8_2.6.8-13.dsc - optional devel Announcing to [EMAIL PROTECTED] Closing bugs: 311357 317286 321442 323557 336153 349774 354493 372621 Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
kernel-image-2.6.8-sparc_2.6.8-16_sparc.changes ACCEPTED
Accepted: kernel-build-2.6.8-4_2.6.8-16_sparc.deb to pool/main/k/kernel-image-2.6.8-sparc/kernel-build-2.6.8-4_2.6.8-16_sparc.deb kernel-headers-2.6.8-4-sparc32_2.6.8-16_sparc.deb to pool/main/k/kernel-image-2.6.8-sparc/kernel-headers-2.6.8-4-sparc32_2.6.8-16_sparc.deb kernel-headers-2.6.8-4-sparc64-smp_2.6.8-16_sparc.deb to pool/main/k/kernel-image-2.6.8-sparc/kernel-headers-2.6.8-4-sparc64-smp_2.6.8-16_sparc.deb kernel-headers-2.6.8-4-sparc64_2.6.8-16_sparc.deb to pool/main/k/kernel-image-2.6.8-sparc/kernel-headers-2.6.8-4-sparc64_2.6.8-16_sparc.deb kernel-headers-2.6.8-4_2.6.8-16_sparc.deb to pool/main/k/kernel-image-2.6.8-sparc/kernel-headers-2.6.8-4_2.6.8-16_sparc.deb kernel-image-2.6.8-4-sparc32_2.6.8-16_sparc.deb to pool/main/k/kernel-image-2.6.8-sparc/kernel-image-2.6.8-4-sparc32_2.6.8-16_sparc.deb kernel-image-2.6.8-4-sparc64-smp_2.6.8-16_sparc.deb to pool/main/k/kernel-image-2.6.8-sparc/kernel-image-2.6.8-4-sparc64-smp_2.6.8-16_sparc.deb kernel-image-2.6.8-4-sparc64_2.6.8-16_sparc.deb to pool/main/k/kernel-image-2.6.8-sparc/kernel-image-2.6.8-4-sparc64_2.6.8-16_sparc.deb kernel-image-2.6.8-sparc_2.6.8-16.dsc to pool/main/k/kernel-image-2.6.8-sparc/kernel-image-2.6.8-sparc_2.6.8-16.dsc kernel-image-2.6.8-sparc_2.6.8-16.tar.gz to pool/main/k/kernel-image-2.6.8-sparc/kernel-image-2.6.8-sparc_2.6.8-16.tar.gz Override entries for your package: kernel-build-2.6.8-4_2.6.8-16_sparc.deb - optional devel kernel-headers-2.6.8-4-sparc32_2.6.8-16_sparc.deb - optional devel kernel-headers-2.6.8-4-sparc64-smp_2.6.8-16_sparc.deb - optional devel kernel-headers-2.6.8-4-sparc64_2.6.8-16_sparc.deb - optional devel kernel-headers-2.6.8-4_2.6.8-16_sparc.deb - optional devel kernel-image-2.6.8-4-sparc32_2.6.8-16_sparc.deb - optional base kernel-image-2.6.8-4-sparc64-smp_2.6.8-16_sparc.deb - optional base kernel-image-2.6.8-4-sparc64_2.6.8-16_sparc.deb - optional base kernel-image-2.6.8-sparc_2.6.8-16.dsc - optional devel Announcing to [EMAIL PROTECTED] Closing bugs: 311357 317286 321442 323557 336153 349774 354493 372621 Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
kernel-image-2.6.8-s390_2.6.8-6_s390.changes ACCEPTED
Accepted: kernel-headers-2.6.8-4_2.6.8-6_s390.deb to pool/main/k/kernel-image-2.6.8-s390/kernel-headers-2.6.8-4_2.6.8-6_s390.deb kernel-image-2.6.8-4-s390-tape_2.6.8-6_s390.deb to pool/main/k/kernel-image-2.6.8-s390/kernel-image-2.6.8-4-s390-tape_2.6.8-6_s390.deb kernel-image-2.6.8-4-s390_2.6.8-6_s390.deb to pool/main/k/kernel-image-2.6.8-s390/kernel-image-2.6.8-4-s390_2.6.8-6_s390.deb kernel-image-2.6.8-4-s390x_2.6.8-6_s390.deb to pool/main/k/kernel-image-2.6.8-s390/kernel-image-2.6.8-4-s390x_2.6.8-6_s390.deb kernel-image-2.6.8-s390_2.6.8-6.dsc to pool/main/k/kernel-image-2.6.8-s390/kernel-image-2.6.8-s390_2.6.8-6.dsc kernel-image-2.6.8-s390_2.6.8-6.tar.gz to pool/main/k/kernel-image-2.6.8-s390/kernel-image-2.6.8-s390_2.6.8-6.tar.gz kernel-patch-2.6.8-s390_2.6.8-6_all.deb to pool/main/k/kernel-image-2.6.8-s390/kernel-patch-2.6.8-s390_2.6.8-6_all.deb Override entries for your package: kernel-headers-2.6.8-4_2.6.8-6_s390.deb - optional devel kernel-image-2.6.8-4-s390-tape_2.6.8-6_s390.deb - extra base kernel-image-2.6.8-4-s390_2.6.8-6_s390.deb - optional base kernel-image-2.6.8-4-s390x_2.6.8-6_s390.deb - optional base kernel-image-2.6.8-s390_2.6.8-6.dsc - optional devel kernel-patch-2.6.8-s390_2.6.8-6_all.deb - optional devel Announcing to [EMAIL PROTECTED] Closing bugs: 311357 317286 321442 323557 336153 349774 354493 372621 Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
kernel-image-2.6.8-ia64_2.6.8-15_ia64.changes ACCEPTED
Accepted: kernel-headers-2.6-itanium-smp_2.6.8-15_ia64.deb to pool/main/k/kernel-image-2.6.8-ia64/kernel-headers-2.6-itanium-smp_2.6.8-15_ia64.deb kernel-headers-2.6-itanium_2.6.8-15_ia64.deb to pool/main/k/kernel-image-2.6.8-ia64/kernel-headers-2.6-itanium_2.6.8-15_ia64.deb kernel-headers-2.6-mckinley-smp_2.6.8-15_ia64.deb to pool/main/k/kernel-image-2.6.8-ia64/kernel-headers-2.6-mckinley-smp_2.6.8-15_ia64.deb kernel-headers-2.6-mckinley_2.6.8-15_ia64.deb to pool/main/k/kernel-image-2.6.8-ia64/kernel-headers-2.6-mckinley_2.6.8-15_ia64.deb kernel-headers-2.6.8-4-itanium-smp_2.6.8-15_ia64.deb to pool/main/k/kernel-image-2.6.8-ia64/kernel-headers-2.6.8-4-itanium-smp_2.6.8-15_ia64.deb kernel-headers-2.6.8-4-itanium_2.6.8-15_ia64.deb to pool/main/k/kernel-image-2.6.8-ia64/kernel-headers-2.6.8-4-itanium_2.6.8-15_ia64.deb kernel-headers-2.6.8-4-mckinley-smp_2.6.8-15_ia64.deb to pool/main/k/kernel-image-2.6.8-ia64/kernel-headers-2.6.8-4-mckinley-smp_2.6.8-15_ia64.deb kernel-headers-2.6.8-4-mckinley_2.6.8-15_ia64.deb to pool/main/k/kernel-image-2.6.8-ia64/kernel-headers-2.6.8-4-mckinley_2.6.8-15_ia64.deb kernel-headers-2.6.8-4_2.6.8-15_ia64.deb to pool/main/k/kernel-image-2.6.8-ia64/kernel-headers-2.6.8-4_2.6.8-15_ia64.deb kernel-image-2.6-itanium-smp_2.6.8-15_ia64.deb to pool/main/k/kernel-image-2.6.8-ia64/kernel-image-2.6-itanium-smp_2.6.8-15_ia64.deb kernel-image-2.6-itanium_2.6.8-15_ia64.deb to pool/main/k/kernel-image-2.6.8-ia64/kernel-image-2.6-itanium_2.6.8-15_ia64.deb kernel-image-2.6-mckinley-smp_2.6.8-15_ia64.deb to pool/main/k/kernel-image-2.6.8-ia64/kernel-image-2.6-mckinley-smp_2.6.8-15_ia64.deb kernel-image-2.6-mckinley_2.6.8-15_ia64.deb to pool/main/k/kernel-image-2.6.8-ia64/kernel-image-2.6-mckinley_2.6.8-15_ia64.deb kernel-image-2.6.8-4-itanium-smp_2.6.8-15_ia64.deb to pool/main/k/kernel-image-2.6.8-ia64/kernel-image-2.6.8-4-itanium-smp_2.6.8-15_ia64.deb kernel-image-2.6.8-4-itanium_2.6.8-15_ia64.deb to pool/main/k/kernel-image-2.6.8-ia64/kernel-image-2.6.8-4-itanium_2.6.8-15_ia64.deb kernel-image-2.6.8-4-mckinley-smp_2.6.8-15_ia64.deb to pool/main/k/kernel-image-2.6.8-ia64/kernel-image-2.6.8-4-mckinley-smp_2.6.8-15_ia64.deb kernel-image-2.6.8-4-mckinley_2.6.8-15_ia64.deb to pool/main/k/kernel-image-2.6.8-ia64/kernel-image-2.6.8-4-mckinley_2.6.8-15_ia64.deb kernel-image-2.6.8-ia64_2.6.8-15.dsc to pool/main/k/kernel-image-2.6.8-ia64/kernel-image-2.6.8-ia64_2.6.8-15.dsc kernel-image-2.6.8-ia64_2.6.8-15.tar.gz to pool/main/k/kernel-image-2.6.8-ia64/kernel-image-2.6.8-ia64_2.6.8-15.tar.gz Override entries for your package: kernel-headers-2.6-itanium-smp_2.6.8-15_ia64.deb - optional devel kernel-headers-2.6-itanium_2.6.8-15_ia64.deb - optional devel kernel-headers-2.6-mckinley-smp_2.6.8-15_ia64.deb - optional devel kernel-headers-2.6-mckinley_2.6.8-15_ia64.deb - optional devel kernel-headers-2.6.8-4-itanium-smp_2.6.8-15_ia64.deb - optional devel kernel-headers-2.6.8-4-itanium_2.6.8-15_ia64.deb - optional devel kernel-headers-2.6.8-4-mckinley-smp_2.6.8-15_ia64.deb - optional devel kernel-headers-2.6.8-4-mckinley_2.6.8-15_ia64.deb - optional devel kernel-headers-2.6.8-4_2.6.8-15_ia64.deb - optional devel kernel-image-2.6-itanium-smp_2.6.8-15_ia64.deb - optional base kernel-image-2.6-itanium_2.6.8-15_ia64.deb - optional base kernel-image-2.6-mckinley-smp_2.6.8-15_ia64.deb - optional base kernel-image-2.6-mckinley_2.6.8-15_ia64.deb - optional base kernel-image-2.6.8-4-itanium-smp_2.6.8-15_ia64.deb - optional base kernel-image-2.6.8-4-itanium_2.6.8-15_ia64.deb - optional base kernel-image-2.6.8-4-mckinley-smp_2.6.8-15_ia64.deb - optional base kernel-image-2.6.8-4-mckinley_2.6.8-15_ia64.deb - optional base kernel-image-2.6.8-ia64_2.6.8-15.dsc - optional devel Announcing to [EMAIL PROTECTED] Closing bugs: 311357 317286 321442 323557 336153 349774 354493 372621 Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
kernel-image-2.6.8-alpha_2.6.8-17_alpha.changes ACCEPTED
Accepted: kernel-headers-2.6.8-4-generic_2.6.8-17_alpha.deb to pool/main/k/kernel-image-2.6.8-alpha/kernel-headers-2.6.8-4-generic_2.6.8-17_alpha.deb kernel-headers-2.6.8-4-smp_2.6.8-17_alpha.deb to pool/main/k/kernel-image-2.6.8-alpha/kernel-headers-2.6.8-4-smp_2.6.8-17_alpha.deb kernel-headers-2.6.8-4_2.6.8-17_alpha.deb to pool/main/k/kernel-image-2.6.8-alpha/kernel-headers-2.6.8-4_2.6.8-17_alpha.deb kernel-image-2.6.8-4-generic_2.6.8-17_alpha.deb to pool/main/k/kernel-image-2.6.8-alpha/kernel-image-2.6.8-4-generic_2.6.8-17_alpha.deb kernel-image-2.6.8-4-smp_2.6.8-17_alpha.deb to pool/main/k/kernel-image-2.6.8-alpha/kernel-image-2.6.8-4-smp_2.6.8-17_alpha.deb kernel-image-2.6.8-alpha_2.6.8-17.dsc to pool/main/k/kernel-image-2.6.8-alpha/kernel-image-2.6.8-alpha_2.6.8-17.dsc kernel-image-2.6.8-alpha_2.6.8-17.tar.gz to pool/main/k/kernel-image-2.6.8-alpha/kernel-image-2.6.8-alpha_2.6.8-17.tar.gz Override entries for your package: kernel-headers-2.6.8-4-generic_2.6.8-17_alpha.deb - optional devel kernel-headers-2.6.8-4-smp_2.6.8-17_alpha.deb - optional devel kernel-headers-2.6.8-4_2.6.8-17_alpha.deb - optional devel kernel-image-2.6.8-4-generic_2.6.8-17_alpha.deb - optional base kernel-image-2.6.8-4-smp_2.6.8-17_alpha.deb - optional base kernel-image-2.6.8-alpha_2.6.8-17.dsc - optional devel Announcing to [EMAIL PROTECTED] Closing bugs: 311357 317286 321442 323557 336153 349774 354493 372621 Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
kernel-image-2.6.8-i386_2.6.8-17_i386.changes ACCEPTED
Accepted: kernel-headers-2.6.8-4-386_2.6.8-17_i386.deb to pool/main/k/kernel-image-2.6.8-i386/kernel-headers-2.6.8-4-386_2.6.8-17_i386.deb kernel-headers-2.6.8-4-686-smp_2.6.8-17_i386.deb to pool/main/k/kernel-image-2.6.8-i386/kernel-headers-2.6.8-4-686-smp_2.6.8-17_i386.deb kernel-headers-2.6.8-4-686_2.6.8-17_i386.deb to pool/main/k/kernel-image-2.6.8-i386/kernel-headers-2.6.8-4-686_2.6.8-17_i386.deb kernel-headers-2.6.8-4-k7-smp_2.6.8-17_i386.deb to pool/main/k/kernel-image-2.6.8-i386/kernel-headers-2.6.8-4-k7-smp_2.6.8-17_i386.deb kernel-headers-2.6.8-4-k7_2.6.8-17_i386.deb to pool/main/k/kernel-image-2.6.8-i386/kernel-headers-2.6.8-4-k7_2.6.8-17_i386.deb kernel-headers-2.6.8-4_2.6.8-17_i386.deb to pool/main/k/kernel-image-2.6.8-i386/kernel-headers-2.6.8-4_2.6.8-17_i386.deb kernel-image-2.6.8-4-386_2.6.8-17_i386.deb to pool/main/k/kernel-image-2.6.8-i386/kernel-image-2.6.8-4-386_2.6.8-17_i386.deb kernel-image-2.6.8-4-686-smp_2.6.8-17_i386.deb to pool/main/k/kernel-image-2.6.8-i386/kernel-image-2.6.8-4-686-smp_2.6.8-17_i386.deb kernel-image-2.6.8-4-686_2.6.8-17_i386.deb to pool/main/k/kernel-image-2.6.8-i386/kernel-image-2.6.8-4-686_2.6.8-17_i386.deb kernel-image-2.6.8-4-k7-smp_2.6.8-17_i386.deb to pool/main/k/kernel-image-2.6.8-i386/kernel-image-2.6.8-4-k7-smp_2.6.8-17_i386.deb kernel-image-2.6.8-4-k7_2.6.8-17_i386.deb to pool/main/k/kernel-image-2.6.8-i386/kernel-image-2.6.8-4-k7_2.6.8-17_i386.deb kernel-image-2.6.8-i386_2.6.8-17.dsc to pool/main/k/kernel-image-2.6.8-i386/kernel-image-2.6.8-i386_2.6.8-17.dsc kernel-image-2.6.8-i386_2.6.8-17.tar.gz to pool/main/k/kernel-image-2.6.8-i386/kernel-image-2.6.8-i386_2.6.8-17.tar.gz Override entries for your package: kernel-headers-2.6.8-4-386_2.6.8-17_i386.deb - optional devel kernel-headers-2.6.8-4-686-smp_2.6.8-17_i386.deb - optional devel kernel-headers-2.6.8-4-686_2.6.8-17_i386.deb - optional devel kernel-headers-2.6.8-4-k7-smp_2.6.8-17_i386.deb - optional devel kernel-headers-2.6.8-4-k7_2.6.8-17_i386.deb - optional devel kernel-headers-2.6.8-4_2.6.8-17_i386.deb - optional devel kernel-image-2.6.8-4-386_2.6.8-17_i386.deb - optional base kernel-image-2.6.8-4-686-smp_2.6.8-17_i386.deb - optional base kernel-image-2.6.8-4-686_2.6.8-17_i386.deb - optional base kernel-image-2.6.8-4-k7-smp_2.6.8-17_i386.deb - optional base kernel-image-2.6.8-4-k7_2.6.8-17_i386.deb - optional base kernel-image-2.6.8-i386_2.6.8-17.dsc - optional devel Announcing to [EMAIL PROTECTED] Closing bugs: 311357 317286 321442 323557 336153 349774 354493 372621 Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#317286: marked as done (Please backport support for Promise SATAII TX2/TX4 cards (from 2.6.11))
Your message dated Mon, 28 May 2007 23:06:12 + with message-id [EMAIL PROTECTED] and subject line Bug#317286: fixed in kernel-image-2.6.8-hppa 2.6.8-7 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: kernel-source Version: 2.6.8-16 This version of the kernel does not support Promise SATAII TX2/TX4 cards. (Note SATAII, Not to be confused with regular Promise SATA TX2/4 cards). Support for these cards was added to kernel 2.6.11. From the Changelog (http://www.kernel.org/pub/linux/kernel/v2.6/ChangeLog-2.6.11): [EMAIL PROTECTED] [libata sata_promise] support Promise SATAII TX2/TX4 cards Originally from Peter Smith, with testing and additional contributions from Jens Axboe. I politely request that someone back port the Promise support to Debian's 2.6.8 kernel. Thank You ---End Message--- ---BeginMessage--- Source: kernel-image-2.6.8-hppa Source-Version: 2.6.8-7 We believe that the bug you reported is fixed in the latest version of kernel-image-2.6.8-hppa, which is due to be installed in the Debian FTP archive: kernel-headers-2.6.8-4-32-smp_2.6.8-7_hppa.deb to pool/main/k/kernel-image-2.6.8-hppa/kernel-headers-2.6.8-4-32-smp_2.6.8-7_hppa.deb kernel-headers-2.6.8-4-32_2.6.8-7_hppa.deb to pool/main/k/kernel-image-2.6.8-hppa/kernel-headers-2.6.8-4-32_2.6.8-7_hppa.deb kernel-headers-2.6.8-4-64-smp_2.6.8-7_hppa.deb to pool/main/k/kernel-image-2.6.8-hppa/kernel-headers-2.6.8-4-64-smp_2.6.8-7_hppa.deb kernel-headers-2.6.8-4-64_2.6.8-7_hppa.deb to pool/main/k/kernel-image-2.6.8-hppa/kernel-headers-2.6.8-4-64_2.6.8-7_hppa.deb kernel-headers-2.6.8-4_2.6.8-7_hppa.deb to pool/main/k/kernel-image-2.6.8-hppa/kernel-headers-2.6.8-4_2.6.8-7_hppa.deb kernel-image-2.6.8-4-32-smp_2.6.8-7_hppa.deb to pool/main/k/kernel-image-2.6.8-hppa/kernel-image-2.6.8-4-32-smp_2.6.8-7_hppa.deb kernel-image-2.6.8-4-32_2.6.8-7_hppa.deb to pool/main/k/kernel-image-2.6.8-hppa/kernel-image-2.6.8-4-32_2.6.8-7_hppa.deb kernel-image-2.6.8-4-64-smp_2.6.8-7_hppa.deb to pool/main/k/kernel-image-2.6.8-hppa/kernel-image-2.6.8-4-64-smp_2.6.8-7_hppa.deb kernel-image-2.6.8-4-64_2.6.8-7_hppa.deb to pool/main/k/kernel-image-2.6.8-hppa/kernel-image-2.6.8-4-64_2.6.8-7_hppa.deb kernel-image-2.6.8-hppa_2.6.8-7.dsc to pool/main/k/kernel-image-2.6.8-hppa/kernel-image-2.6.8-hppa_2.6.8-7.dsc kernel-image-2.6.8-hppa_2.6.8-7.tar.gz to pool/main/k/kernel-image-2.6.8-hppa/kernel-image-2.6.8-hppa_2.6.8-7.tar.gz A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. dann frazier [EMAIL PROTECTED] (supplier of updated kernel-image-2.6.8-hppa package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 26 May 2007 04:01:59 -0600 Source: kernel-image-2.6.8-hppa Binary: kernel-image-2.6.8-4-64-smp kernel-headers-2.6.8-4-64-smp kernel-headers-2.6.8-4-32-smp kernel-headers-2.6.8-4 kernel-image-2.6.8-4-64 kernel-headers-2.6.8-4-32 kernel-headers-2.6.8-4-64 kernel-image-2.6.8-4-32-smp kernel-image-2.6.8-4-32 Architecture: source hppa Version: 2.6.8-7 Distribution: oldstable Urgency: high Maintainer: Kyle McMartin [EMAIL PROTECTED] Changed-By: dann frazier [EMAIL PROTECTED] Description: kernel-headers-2.6.8-4 - Header files for the Linux kernel version 2.6.8 kernel-headers-2.6.8-4-32 - Linux kernel headers 2.6.8 on HP PA-RISC 32-bit systems kernel-headers-2.6.8-4-32-smp - Linux kernel headers 2.6.8 on HP PA-RISC 32-bit systems kernel-headers-2.6.8-4-64 - Linux kernel headers 2.6.8 on HP PA-RISC 64-bit systems kernel-headers-2.6.8-4-64-smp - Linux kernel headers 2.6.8 on HP PA-RISC 64-bit systems kernel-image-2.6.8-4-32 - Linux kernel image for version 2.6.8 on 32-bit PA-RISC kernel-image-2.6.8-4-32-smp - Linux kernel image for version 2.6.8 on 32-bit PA-RISC kernel-image-2.6.8-4-64 - Linux kernel image for version 2.6.8 on 64-bit PA-RISC kernel-image-2.6.8-4-64-smp - Linux kernel image for version 2.6.8 on 64-bit PA-RISC Closes: 311357 317286 321442 323557 336153 349774 354493 372621 Changes: kernel-image-2.6.8-hppa (2.6.8-7)
Bug#317286: marked as done (Please backport support for Promise SATAII TX2/TX4 cards (from 2.6.11))
Your message dated Mon, 28 May 2007 23:06:28 + with message-id [EMAIL PROTECTED] and subject line Bug#317286: fixed in kernel-image-2.6.8-s390 2.6.8-6 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: kernel-source Version: 2.6.8-16 This version of the kernel does not support Promise SATAII TX2/TX4 cards. (Note SATAII, Not to be confused with regular Promise SATA TX2/4 cards). Support for these cards was added to kernel 2.6.11. From the Changelog (http://www.kernel.org/pub/linux/kernel/v2.6/ChangeLog-2.6.11): [EMAIL PROTECTED] [libata sata_promise] support Promise SATAII TX2/TX4 cards Originally from Peter Smith, with testing and additional contributions from Jens Axboe. I politely request that someone back port the Promise support to Debian's 2.6.8 kernel. Thank You ---End Message--- ---BeginMessage--- Source: kernel-image-2.6.8-s390 Source-Version: 2.6.8-6 We believe that the bug you reported is fixed in the latest version of kernel-image-2.6.8-s390, which is due to be installed in the Debian FTP archive: kernel-headers-2.6.8-4_2.6.8-6_s390.deb to pool/main/k/kernel-image-2.6.8-s390/kernel-headers-2.6.8-4_2.6.8-6_s390.deb kernel-image-2.6.8-4-s390-tape_2.6.8-6_s390.deb to pool/main/k/kernel-image-2.6.8-s390/kernel-image-2.6.8-4-s390-tape_2.6.8-6_s390.deb kernel-image-2.6.8-4-s390_2.6.8-6_s390.deb to pool/main/k/kernel-image-2.6.8-s390/kernel-image-2.6.8-4-s390_2.6.8-6_s390.deb kernel-image-2.6.8-4-s390x_2.6.8-6_s390.deb to pool/main/k/kernel-image-2.6.8-s390/kernel-image-2.6.8-4-s390x_2.6.8-6_s390.deb kernel-image-2.6.8-s390_2.6.8-6.dsc to pool/main/k/kernel-image-2.6.8-s390/kernel-image-2.6.8-s390_2.6.8-6.dsc kernel-image-2.6.8-s390_2.6.8-6.tar.gz to pool/main/k/kernel-image-2.6.8-s390/kernel-image-2.6.8-s390_2.6.8-6.tar.gz kernel-patch-2.6.8-s390_2.6.8-6_all.deb to pool/main/k/kernel-image-2.6.8-s390/kernel-patch-2.6.8-s390_2.6.8-6_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. dann frazier [EMAIL PROTECTED] (supplier of updated kernel-image-2.6.8-s390 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 26 May 2007 03:23:35 -0600 Source: kernel-image-2.6.8-s390 Binary: kernel-headers-2.6.8-4 kernel-patch-2.6.8-s390 kernel-image-2.6.8-4-s390x kernel-image-2.6.8-4-s390-tape kernel-image-2.6.8-4-s390 Architecture: source s390 all Version: 2.6.8-6 Distribution: oldstable Urgency: high Maintainer: Debian kernel team debian-kernel@lists.debian.org Changed-By: dann frazier [EMAIL PROTECTED] Description: kernel-headers-2.6.8-4 - Header files related to Linux kernel version 2.6.8 on IBM S/390 kernel-image-2.6.8-4-s390 - Linux kernel image for kernel version 2.6.8 on IBM S/390 kernel-image-2.6.8-4-s390-tape - Linux kernel image for kernel version 2.6.8 on IBM S/390 kernel-image-2.6.8-4-s390x - Linux kernel image for kernel version 2.6.8 on IBM zSeries. kernel-patch-2.6.8-s390 - Diffs to the Linux kernel source 2.6.8 for IBM S/390 and zSeries Closes: 311357 317286 321442 323557 336153 349774 354493 372621 Changes: kernel-image-2.6.8-s390 (2.6.8-6) oldstable; urgency=high . * Rebuild against kernel-tree-2.6.8-17 [ Simon Horman ] * drivers-net-via-rhine-wol-oops.dpatch (removed): This patch breaks the via-rhine driver and 2.6.8 and is completely bogus for this version of the kernel (closes: #311357) . * drivers-media-vidio-bttv-vc100xp-detect.dpatch Allow Leadtek WinFast VC100 XP cards to work. . * fs-jbd-checkpoint-assertion.dpatch Fix possible false assertion failure in log_do_checkpoint(). We might fail to detect that we actually made a progress when cleaning up the checkpoint lists if we don't retry after writing something to disk. . * mm-rmap-out-of-bounds-pte.dpatch Stop try_to_unmap_cluster() passing out-of-bounds pte to pte_unmap() . * net-ipv4-netfilter-ip_queue-deadlock.dpatch Fix deadlock with ip_queue and tcp local input path. . *
kernel-image-2.6.8-amd64_2.6.8-17_i386.changes ACCEPTED
Accepted: kernel-headers-2.6.8-13-amd64-generic_2.6.8-17_i386.deb to pool/main/k/kernel-image-2.6.8-amd64/kernel-headers-2.6.8-13-amd64-generic_2.6.8-17_i386.deb kernel-headers-2.6.8-13-amd64-k8-smp_2.6.8-17_i386.deb to pool/main/k/kernel-image-2.6.8-amd64/kernel-headers-2.6.8-13-amd64-k8-smp_2.6.8-17_i386.deb kernel-headers-2.6.8-13-amd64-k8_2.6.8-17_i386.deb to pool/main/k/kernel-image-2.6.8-amd64/kernel-headers-2.6.8-13-amd64-k8_2.6.8-17_i386.deb kernel-headers-2.6.8-13-em64t-p4-smp_2.6.8-17_i386.deb to pool/main/k/kernel-image-2.6.8-amd64/kernel-headers-2.6.8-13-em64t-p4-smp_2.6.8-17_i386.deb kernel-headers-2.6.8-13-em64t-p4_2.6.8-17_i386.deb to pool/main/k/kernel-image-2.6.8-amd64/kernel-headers-2.6.8-13-em64t-p4_2.6.8-17_i386.deb kernel-headers-2.6.8-13_2.6.8-17_i386.deb to pool/main/k/kernel-image-2.6.8-amd64/kernel-headers-2.6.8-13_2.6.8-17_i386.deb kernel-image-2.6.8-13-amd64-generic_2.6.8-17_i386.deb to pool/main/k/kernel-image-2.6.8-amd64/kernel-image-2.6.8-13-amd64-generic_2.6.8-17_i386.deb kernel-image-2.6.8-13-amd64-k8-smp_2.6.8-17_i386.deb to pool/main/k/kernel-image-2.6.8-amd64/kernel-image-2.6.8-13-amd64-k8-smp_2.6.8-17_i386.deb kernel-image-2.6.8-13-amd64-k8_2.6.8-17_i386.deb to pool/main/k/kernel-image-2.6.8-amd64/kernel-image-2.6.8-13-amd64-k8_2.6.8-17_i386.deb kernel-image-2.6.8-13-em64t-p4-smp_2.6.8-17_i386.deb to pool/main/k/kernel-image-2.6.8-amd64/kernel-image-2.6.8-13-em64t-p4-smp_2.6.8-17_i386.deb kernel-image-2.6.8-13-em64t-p4_2.6.8-17_i386.deb to pool/main/k/kernel-image-2.6.8-amd64/kernel-image-2.6.8-13-em64t-p4_2.6.8-17_i386.deb kernel-image-2.6.8-amd64_2.6.8-17.dsc to pool/main/k/kernel-image-2.6.8-amd64/kernel-image-2.6.8-amd64_2.6.8-17.dsc kernel-image-2.6.8-amd64_2.6.8-17.tar.gz to pool/main/k/kernel-image-2.6.8-amd64/kernel-image-2.6.8-amd64_2.6.8-17.tar.gz Override entries for your package: kernel-headers-2.6.8-13-amd64-generic_2.6.8-17_i386.deb - optional devel kernel-headers-2.6.8-13-amd64-k8-smp_2.6.8-17_i386.deb - optional devel kernel-headers-2.6.8-13-amd64-k8_2.6.8-17_i386.deb - optional devel kernel-headers-2.6.8-13-em64t-p4-smp_2.6.8-17_i386.deb - optional devel kernel-headers-2.6.8-13-em64t-p4_2.6.8-17_i386.deb - optional devel kernel-headers-2.6.8-13_2.6.8-17_i386.deb - optional devel kernel-image-2.6.8-13-amd64-generic_2.6.8-17_i386.deb - optional base kernel-image-2.6.8-13-amd64-k8-smp_2.6.8-17_i386.deb - optional base kernel-image-2.6.8-13-amd64-k8_2.6.8-17_i386.deb - optional base kernel-image-2.6.8-13-em64t-p4-smp_2.6.8-17_i386.deb - optional base kernel-image-2.6.8-13-em64t-p4_2.6.8-17_i386.deb - optional base kernel-image-2.6.8-amd64_2.6.8-17.dsc - optional devel Announcing to [EMAIL PROTECTED] Closing bugs: 311357 317286 321442 323557 336153 349774 354493 372621 Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#311357: marked as done (kernel-image-2.6.8-2: via-rhine fails to reserve I/O region, no networking available)
Your message dated Mon, 28 May 2007 23:06:12 + with message-id [EMAIL PROTECTED] and subject line Bug#311357: fixed in kernel-image-2.6.8-hppa 2.6.8-7 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: kernel-image-2.6.8-2-k7 Version: 2.6.8-16 Severity: important File: kernel-image-2.6.8-2 The via-rhine module no longer configures my network card correctly. This broke with the latest kernel upgrade. Below are the messages from the broken kernel and a working kernel. When loading the via-rhine module at boot (or by hand) with kernel 2.6.8-16 I get May 31 00:55:15 localhost kernel: via-rhine.c:v1.10-LK1.1.20-2.6 May-23-2004 Written by Donald Becker May 31 00:55:15 localhost kernel: PCI: Found IRQ 10 for device :00:06.0 May 31 00:55:15 localhost kernel: PCI: Sharing IRQ 10 with :00:04.4 May 31 00:55:15 localhost kernel: PCI: Unable to reserve I/O region #1:[EMAIL PROTECTED] for device :00:06.0 May 31 00:55:15 localhost kernel: via-rhine: probe of :00:06.0 failed with error -16 and networking is unavailable on the system. When loading the via-rhine module at boot (or by hand) with kernel 2.6.8-13 where it works I get May 31 01:53:00 localhost kernel: via-rhine.c:v1.10-LK1.1.20-2.6 May-23-2004 Written by Donald Becker May 31 01:53:00 localhost kernel: PCI: Found IRQ 10 for device :00:06.0 May 31 01:53:00 localhost kernel: PCI: Sharing IRQ 10 with :00:04.4 May 31 01:53:00 localhost kernel: eth0: VIA VT86C100A Rhine at 0xd800, 00:50:ba:c3:4f:50, IRQ 10. May 31 01:53:00 localhost kernel: eth0: MII PHY found at address 8, status 0x782d advertising 05e1 Link 45e1. lspci -v give :00:06.0 Ethernet controller: VIA Technologies, Inc. VT86C100A [Rhine] (rev 06) Subsystem: D-Link System Inc DFE-530TX rev A Flags: bus master, medium devsel, latency 64, IRQ 10 I/O ports at d800 [size=128] Memory at e680 (32-bit, non-prefetchable) [size=128] Expansion ROM at effd [disabled] [size=64K] -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.8-2-386 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages kernel-image-2.6.8-2-k7 depends on: ii coreutils [fileutils] 5.2.1-2The GNU core utilities ii initrd-tools 0.1.81.1 tools to create initrd image for p ii module-init-tools 3.2-pre1-2 tools for managing Linux kernel mo -- no debconf information ---End Message--- ---BeginMessage--- Source: kernel-image-2.6.8-hppa Source-Version: 2.6.8-7 We believe that the bug you reported is fixed in the latest version of kernel-image-2.6.8-hppa, which is due to be installed in the Debian FTP archive: kernel-headers-2.6.8-4-32-smp_2.6.8-7_hppa.deb to pool/main/k/kernel-image-2.6.8-hppa/kernel-headers-2.6.8-4-32-smp_2.6.8-7_hppa.deb kernel-headers-2.6.8-4-32_2.6.8-7_hppa.deb to pool/main/k/kernel-image-2.6.8-hppa/kernel-headers-2.6.8-4-32_2.6.8-7_hppa.deb kernel-headers-2.6.8-4-64-smp_2.6.8-7_hppa.deb to pool/main/k/kernel-image-2.6.8-hppa/kernel-headers-2.6.8-4-64-smp_2.6.8-7_hppa.deb kernel-headers-2.6.8-4-64_2.6.8-7_hppa.deb to pool/main/k/kernel-image-2.6.8-hppa/kernel-headers-2.6.8-4-64_2.6.8-7_hppa.deb kernel-headers-2.6.8-4_2.6.8-7_hppa.deb to pool/main/k/kernel-image-2.6.8-hppa/kernel-headers-2.6.8-4_2.6.8-7_hppa.deb kernel-image-2.6.8-4-32-smp_2.6.8-7_hppa.deb to pool/main/k/kernel-image-2.6.8-hppa/kernel-image-2.6.8-4-32-smp_2.6.8-7_hppa.deb kernel-image-2.6.8-4-32_2.6.8-7_hppa.deb to pool/main/k/kernel-image-2.6.8-hppa/kernel-image-2.6.8-4-32_2.6.8-7_hppa.deb kernel-image-2.6.8-4-64-smp_2.6.8-7_hppa.deb to pool/main/k/kernel-image-2.6.8-hppa/kernel-image-2.6.8-4-64-smp_2.6.8-7_hppa.deb kernel-image-2.6.8-4-64_2.6.8-7_hppa.deb to pool/main/k/kernel-image-2.6.8-hppa/kernel-image-2.6.8-4-64_2.6.8-7_hppa.deb kernel-image-2.6.8-hppa_2.6.8-7.dsc to pool/main/k/kernel-image-2.6.8-hppa/kernel-image-2.6.8-hppa_2.6.8-7.dsc kernel-image-2.6.8-hppa_2.6.8-7.tar.gz to pool/main/k/kernel-image-2.6.8-hppa/kernel-image-2.6.8-hppa_2.6.8-7.tar.gz A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. dann frazier [EMAIL
Bug#323557: marked as done (kernel: nfs server intermitently claims ENOENT on existing files or directories)
Your message dated Mon, 28 May 2007 23:06:12 + with message-id [EMAIL PROTECTED] and subject line Bug#323557: fixed in kernel-image-2.6.8-hppa 2.6.8-7 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: kernel Severity: important Tags: patch The problem reported in https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=150759 (which also has a working patch) exists in Debian kernels as well. In short, the NFS server sometimes reports ENOENT to nfs clients when under high load. This makes it hard to use Maildir over NFS with Debian server as NFS server. -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.6.8-2-386 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) ---End Message--- ---BeginMessage--- Source: kernel-image-2.6.8-hppa Source-Version: 2.6.8-7 We believe that the bug you reported is fixed in the latest version of kernel-image-2.6.8-hppa, which is due to be installed in the Debian FTP archive: kernel-headers-2.6.8-4-32-smp_2.6.8-7_hppa.deb to pool/main/k/kernel-image-2.6.8-hppa/kernel-headers-2.6.8-4-32-smp_2.6.8-7_hppa.deb kernel-headers-2.6.8-4-32_2.6.8-7_hppa.deb to pool/main/k/kernel-image-2.6.8-hppa/kernel-headers-2.6.8-4-32_2.6.8-7_hppa.deb kernel-headers-2.6.8-4-64-smp_2.6.8-7_hppa.deb to pool/main/k/kernel-image-2.6.8-hppa/kernel-headers-2.6.8-4-64-smp_2.6.8-7_hppa.deb kernel-headers-2.6.8-4-64_2.6.8-7_hppa.deb to pool/main/k/kernel-image-2.6.8-hppa/kernel-headers-2.6.8-4-64_2.6.8-7_hppa.deb kernel-headers-2.6.8-4_2.6.8-7_hppa.deb to pool/main/k/kernel-image-2.6.8-hppa/kernel-headers-2.6.8-4_2.6.8-7_hppa.deb kernel-image-2.6.8-4-32-smp_2.6.8-7_hppa.deb to pool/main/k/kernel-image-2.6.8-hppa/kernel-image-2.6.8-4-32-smp_2.6.8-7_hppa.deb kernel-image-2.6.8-4-32_2.6.8-7_hppa.deb to pool/main/k/kernel-image-2.6.8-hppa/kernel-image-2.6.8-4-32_2.6.8-7_hppa.deb kernel-image-2.6.8-4-64-smp_2.6.8-7_hppa.deb to pool/main/k/kernel-image-2.6.8-hppa/kernel-image-2.6.8-4-64-smp_2.6.8-7_hppa.deb kernel-image-2.6.8-4-64_2.6.8-7_hppa.deb to pool/main/k/kernel-image-2.6.8-hppa/kernel-image-2.6.8-4-64_2.6.8-7_hppa.deb kernel-image-2.6.8-hppa_2.6.8-7.dsc to pool/main/k/kernel-image-2.6.8-hppa/kernel-image-2.6.8-hppa_2.6.8-7.dsc kernel-image-2.6.8-hppa_2.6.8-7.tar.gz to pool/main/k/kernel-image-2.6.8-hppa/kernel-image-2.6.8-hppa_2.6.8-7.tar.gz A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. dann frazier [EMAIL PROTECTED] (supplier of updated kernel-image-2.6.8-hppa package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 26 May 2007 04:01:59 -0600 Source: kernel-image-2.6.8-hppa Binary: kernel-image-2.6.8-4-64-smp kernel-headers-2.6.8-4-64-smp kernel-headers-2.6.8-4-32-smp kernel-headers-2.6.8-4 kernel-image-2.6.8-4-64 kernel-headers-2.6.8-4-32 kernel-headers-2.6.8-4-64 kernel-image-2.6.8-4-32-smp kernel-image-2.6.8-4-32 Architecture: source hppa Version: 2.6.8-7 Distribution: oldstable Urgency: high Maintainer: Kyle McMartin [EMAIL PROTECTED] Changed-By: dann frazier [EMAIL PROTECTED] Description: kernel-headers-2.6.8-4 - Header files for the Linux kernel version 2.6.8 kernel-headers-2.6.8-4-32 - Linux kernel headers 2.6.8 on HP PA-RISC 32-bit systems kernel-headers-2.6.8-4-32-smp - Linux kernel headers 2.6.8 on HP PA-RISC 32-bit systems kernel-headers-2.6.8-4-64 - Linux kernel headers 2.6.8 on HP PA-RISC 64-bit systems kernel-headers-2.6.8-4-64-smp - Linux kernel headers 2.6.8 on HP PA-RISC 64-bit systems kernel-image-2.6.8-4-32 - Linux kernel image for version 2.6.8 on 32-bit PA-RISC kernel-image-2.6.8-4-32-smp - Linux kernel image for version 2.6.8 on 32-bit PA-RISC kernel-image-2.6.8-4-64 - Linux kernel image for version 2.6.8 on 64-bit PA-RISC kernel-image-2.6.8-4-64-smp - Linux kernel image for version 2.6.8 on 64-bit PA-RISC Closes: 311357 317286 321442 323557 336153 349774 354493 372621 Changes: kernel-image-2.6.8-hppa (2.6.8-7) oldstable; urgency=high . * Rebuild against kernel-tree-2.6.8-17 [ Simon Horman ] *
Bug#372621: marked as done (old bug in ipt_ULOG (error during NLMSG_PUT))
Your message dated Mon, 28 May 2007 23:06:26 + with message-id [EMAIL PROTECTED] and subject line Bug#372621: fixed in kernel-image-2.6.8-ia64 2.6.8-15 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: kernel-source-2.6.8 Version: 2.6.8-16sarge2 When I used fprobe-ulog kernel printed sometimes: ipt_ULOG: error during NLMSG_PUT I google'd that this problem (actually bug) was solved in 2.6.10 by Harald Welte [EMAIL PROTECTED]. See: http://oss.sgi.com/archives/netdev/2004-10/msg01026.html (there is a small patch) http://www.kernel.org/pub/linux/kernel/v2.6/ChangeLog-2.6.10 It seems both 2.6 and 2.4 debian kernels affected. I use Debian GNU/Linux 3.1r2 (with last updates), kernel 2.6.8-2-686-smp. ---End Message--- ---BeginMessage--- Source: kernel-image-2.6.8-ia64 Source-Version: 2.6.8-15 We believe that the bug you reported is fixed in the latest version of kernel-image-2.6.8-ia64, which is due to be installed in the Debian FTP archive: kernel-headers-2.6-itanium-smp_2.6.8-15_ia64.deb to pool/main/k/kernel-image-2.6.8-ia64/kernel-headers-2.6-itanium-smp_2.6.8-15_ia64.deb kernel-headers-2.6-itanium_2.6.8-15_ia64.deb to pool/main/k/kernel-image-2.6.8-ia64/kernel-headers-2.6-itanium_2.6.8-15_ia64.deb kernel-headers-2.6-mckinley-smp_2.6.8-15_ia64.deb to pool/main/k/kernel-image-2.6.8-ia64/kernel-headers-2.6-mckinley-smp_2.6.8-15_ia64.deb kernel-headers-2.6-mckinley_2.6.8-15_ia64.deb to pool/main/k/kernel-image-2.6.8-ia64/kernel-headers-2.6-mckinley_2.6.8-15_ia64.deb kernel-headers-2.6.8-4-itanium-smp_2.6.8-15_ia64.deb to pool/main/k/kernel-image-2.6.8-ia64/kernel-headers-2.6.8-4-itanium-smp_2.6.8-15_ia64.deb kernel-headers-2.6.8-4-itanium_2.6.8-15_ia64.deb to pool/main/k/kernel-image-2.6.8-ia64/kernel-headers-2.6.8-4-itanium_2.6.8-15_ia64.deb kernel-headers-2.6.8-4-mckinley-smp_2.6.8-15_ia64.deb to pool/main/k/kernel-image-2.6.8-ia64/kernel-headers-2.6.8-4-mckinley-smp_2.6.8-15_ia64.deb kernel-headers-2.6.8-4-mckinley_2.6.8-15_ia64.deb to pool/main/k/kernel-image-2.6.8-ia64/kernel-headers-2.6.8-4-mckinley_2.6.8-15_ia64.deb kernel-headers-2.6.8-4_2.6.8-15_ia64.deb to pool/main/k/kernel-image-2.6.8-ia64/kernel-headers-2.6.8-4_2.6.8-15_ia64.deb kernel-image-2.6-itanium-smp_2.6.8-15_ia64.deb to pool/main/k/kernel-image-2.6.8-ia64/kernel-image-2.6-itanium-smp_2.6.8-15_ia64.deb kernel-image-2.6-itanium_2.6.8-15_ia64.deb to pool/main/k/kernel-image-2.6.8-ia64/kernel-image-2.6-itanium_2.6.8-15_ia64.deb kernel-image-2.6-mckinley-smp_2.6.8-15_ia64.deb to pool/main/k/kernel-image-2.6.8-ia64/kernel-image-2.6-mckinley-smp_2.6.8-15_ia64.deb kernel-image-2.6-mckinley_2.6.8-15_ia64.deb to pool/main/k/kernel-image-2.6.8-ia64/kernel-image-2.6-mckinley_2.6.8-15_ia64.deb kernel-image-2.6.8-4-itanium-smp_2.6.8-15_ia64.deb to pool/main/k/kernel-image-2.6.8-ia64/kernel-image-2.6.8-4-itanium-smp_2.6.8-15_ia64.deb kernel-image-2.6.8-4-itanium_2.6.8-15_ia64.deb to pool/main/k/kernel-image-2.6.8-ia64/kernel-image-2.6.8-4-itanium_2.6.8-15_ia64.deb kernel-image-2.6.8-4-mckinley-smp_2.6.8-15_ia64.deb to pool/main/k/kernel-image-2.6.8-ia64/kernel-image-2.6.8-4-mckinley-smp_2.6.8-15_ia64.deb kernel-image-2.6.8-4-mckinley_2.6.8-15_ia64.deb to pool/main/k/kernel-image-2.6.8-ia64/kernel-image-2.6.8-4-mckinley_2.6.8-15_ia64.deb kernel-image-2.6.8-ia64_2.6.8-15.dsc to pool/main/k/kernel-image-2.6.8-ia64/kernel-image-2.6.8-ia64_2.6.8-15.dsc kernel-image-2.6.8-ia64_2.6.8-15.tar.gz to pool/main/k/kernel-image-2.6.8-ia64/kernel-image-2.6.8-ia64_2.6.8-15.tar.gz A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. dann frazier [EMAIL PROTECTED] (supplier of updated kernel-image-2.6.8-ia64 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 26 May 2007 04:04:02 -0600 Source: kernel-image-2.6.8-ia64 Binary: kernel-headers-2.6-itanium kernel-image-2.6.8-4-mckinley kernel-headers-2.6-mckinley-smp kernel-headers-2.6-mckinley kernel-headers-2.6.8-4-itanium kernel-image-2.6-mckinley-smp kernel-image-2.6.8-4-itanium-smp
Bug#323557: marked as done (kernel: nfs server intermitently claims ENOENT on existing files or directories)
Your message dated Mon, 28 May 2007 23:06:34 + with message-id [EMAIL PROTECTED] and subject line Bug#323557: fixed in kernel-patch-powerpc-2.6.8 2.6.8-13 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: kernel Severity: important Tags: patch The problem reported in https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=150759 (which also has a working patch) exists in Debian kernels as well. In short, the NFS server sometimes reports ENOENT to nfs clients when under high load. This makes it hard to use Maildir over NFS with Debian server as NFS server. -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.6.8-2-386 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) ---End Message--- ---BeginMessage--- Source: kernel-patch-powerpc-2.6.8 Source-Version: 2.6.8-13 We believe that the bug you reported is fixed in the latest version of kernel-patch-powerpc-2.6.8, which is due to be installed in the Debian FTP archive: kernel-build-2.6.8-4-power3-smp_2.6.8-13_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-build-2.6.8-4-power3-smp_2.6.8-13_powerpc.deb kernel-build-2.6.8-4-power3_2.6.8-13_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-build-2.6.8-4-power3_2.6.8-13_powerpc.deb kernel-build-2.6.8-4-power4-smp_2.6.8-13_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-build-2.6.8-4-power4-smp_2.6.8-13_powerpc.deb kernel-build-2.6.8-4-power4_2.6.8-13_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-build-2.6.8-4-power4_2.6.8-13_powerpc.deb kernel-build-2.6.8-4-powerpc-smp_2.6.8-13_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-build-2.6.8-4-powerpc-smp_2.6.8-13_powerpc.deb kernel-build-2.6.8-4-powerpc_2.6.8-13_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-build-2.6.8-4-powerpc_2.6.8-13_powerpc.deb kernel-headers-2.6.8-4_2.6.8-13_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-headers-2.6.8-4_2.6.8-13_powerpc.deb kernel-image-2.6.8-4-power3-smp_2.6.8-13_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-image-2.6.8-4-power3-smp_2.6.8-13_powerpc.deb kernel-image-2.6.8-4-power3_2.6.8-13_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-image-2.6.8-4-power3_2.6.8-13_powerpc.deb kernel-image-2.6.8-4-power4-smp_2.6.8-13_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-image-2.6.8-4-power4-smp_2.6.8-13_powerpc.deb kernel-image-2.6.8-4-power4_2.6.8-13_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-image-2.6.8-4-power4_2.6.8-13_powerpc.deb kernel-image-2.6.8-4-powerpc-smp_2.6.8-13_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-image-2.6.8-4-powerpc-smp_2.6.8-13_powerpc.deb kernel-image-2.6.8-4-powerpc_2.6.8-13_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-image-2.6.8-4-powerpc_2.6.8-13_powerpc.deb kernel-patch-powerpc-2.6.8_2.6.8-13.dsc to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-patch-powerpc-2.6.8_2.6.8-13.dsc kernel-patch-powerpc-2.6.8_2.6.8-13.tar.gz to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-patch-powerpc-2.6.8_2.6.8-13.tar.gz A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. dann frazier [EMAIL PROTECTED] (supplier of updated kernel-patch-powerpc-2.6.8 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 26 May 2007 04:08:06 -0600 Source: kernel-patch-powerpc-2.6.8 Binary: kernel-image-2.6.8-4-power4 kernel-build-2.6.8-4-power3-smp kernel-build-2.6.8-4-power4-smp kernel-build-2.6.8-4-powerpc-smp kernel-build-2.6.8-4-power3 kernel-image-2.6.8-4-power4-smp kernel-image-2.6.8-4-powerpc kernel-image-2.6.8-4-powerpc-smp kernel-build-2.6.8-4-power4 kernel-image-2.6.8-4-power3 kernel-headers-2.6.8-4 kernel-build-2.6.8-4-powerpc kernel-image-2.6.8-4-power3-smp Architecture: source powerpc Version: 2.6.8-13 Distribution: oldstable Urgency: high Maintainer: Debian Kernel Team debian-kernel@lists.debian.org Changed-By: dann frazier [EMAIL PROTECTED] Description: kernel-build-2.6.8-4-power3 - build
Bug#372621: marked as done (old bug in ipt_ULOG (error during NLMSG_PUT))
Your message dated Mon, 28 May 2007 23:06:13 + with message-id [EMAIL PROTECTED] and subject line Bug#372621: fixed in kernel-image-2.6.8-hppa 2.6.8-7 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: kernel-source-2.6.8 Version: 2.6.8-16sarge2 When I used fprobe-ulog kernel printed sometimes: ipt_ULOG: error during NLMSG_PUT I google'd that this problem (actually bug) was solved in 2.6.10 by Harald Welte [EMAIL PROTECTED]. See: http://oss.sgi.com/archives/netdev/2004-10/msg01026.html (there is a small patch) http://www.kernel.org/pub/linux/kernel/v2.6/ChangeLog-2.6.10 It seems both 2.6 and 2.4 debian kernels affected. I use Debian GNU/Linux 3.1r2 (with last updates), kernel 2.6.8-2-686-smp. ---End Message--- ---BeginMessage--- Source: kernel-image-2.6.8-hppa Source-Version: 2.6.8-7 We believe that the bug you reported is fixed in the latest version of kernel-image-2.6.8-hppa, which is due to be installed in the Debian FTP archive: kernel-headers-2.6.8-4-32-smp_2.6.8-7_hppa.deb to pool/main/k/kernel-image-2.6.8-hppa/kernel-headers-2.6.8-4-32-smp_2.6.8-7_hppa.deb kernel-headers-2.6.8-4-32_2.6.8-7_hppa.deb to pool/main/k/kernel-image-2.6.8-hppa/kernel-headers-2.6.8-4-32_2.6.8-7_hppa.deb kernel-headers-2.6.8-4-64-smp_2.6.8-7_hppa.deb to pool/main/k/kernel-image-2.6.8-hppa/kernel-headers-2.6.8-4-64-smp_2.6.8-7_hppa.deb kernel-headers-2.6.8-4-64_2.6.8-7_hppa.deb to pool/main/k/kernel-image-2.6.8-hppa/kernel-headers-2.6.8-4-64_2.6.8-7_hppa.deb kernel-headers-2.6.8-4_2.6.8-7_hppa.deb to pool/main/k/kernel-image-2.6.8-hppa/kernel-headers-2.6.8-4_2.6.8-7_hppa.deb kernel-image-2.6.8-4-32-smp_2.6.8-7_hppa.deb to pool/main/k/kernel-image-2.6.8-hppa/kernel-image-2.6.8-4-32-smp_2.6.8-7_hppa.deb kernel-image-2.6.8-4-32_2.6.8-7_hppa.deb to pool/main/k/kernel-image-2.6.8-hppa/kernel-image-2.6.8-4-32_2.6.8-7_hppa.deb kernel-image-2.6.8-4-64-smp_2.6.8-7_hppa.deb to pool/main/k/kernel-image-2.6.8-hppa/kernel-image-2.6.8-4-64-smp_2.6.8-7_hppa.deb kernel-image-2.6.8-4-64_2.6.8-7_hppa.deb to pool/main/k/kernel-image-2.6.8-hppa/kernel-image-2.6.8-4-64_2.6.8-7_hppa.deb kernel-image-2.6.8-hppa_2.6.8-7.dsc to pool/main/k/kernel-image-2.6.8-hppa/kernel-image-2.6.8-hppa_2.6.8-7.dsc kernel-image-2.6.8-hppa_2.6.8-7.tar.gz to pool/main/k/kernel-image-2.6.8-hppa/kernel-image-2.6.8-hppa_2.6.8-7.tar.gz A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. dann frazier [EMAIL PROTECTED] (supplier of updated kernel-image-2.6.8-hppa package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 26 May 2007 04:01:59 -0600 Source: kernel-image-2.6.8-hppa Binary: kernel-image-2.6.8-4-64-smp kernel-headers-2.6.8-4-64-smp kernel-headers-2.6.8-4-32-smp kernel-headers-2.6.8-4 kernel-image-2.6.8-4-64 kernel-headers-2.6.8-4-32 kernel-headers-2.6.8-4-64 kernel-image-2.6.8-4-32-smp kernel-image-2.6.8-4-32 Architecture: source hppa Version: 2.6.8-7 Distribution: oldstable Urgency: high Maintainer: Kyle McMartin [EMAIL PROTECTED] Changed-By: dann frazier [EMAIL PROTECTED] Description: kernel-headers-2.6.8-4 - Header files for the Linux kernel version 2.6.8 kernel-headers-2.6.8-4-32 - Linux kernel headers 2.6.8 on HP PA-RISC 32-bit systems kernel-headers-2.6.8-4-32-smp - Linux kernel headers 2.6.8 on HP PA-RISC 32-bit systems kernel-headers-2.6.8-4-64 - Linux kernel headers 2.6.8 on HP PA-RISC 64-bit systems kernel-headers-2.6.8-4-64-smp - Linux kernel headers 2.6.8 on HP PA-RISC 64-bit systems kernel-image-2.6.8-4-32 - Linux kernel image for version 2.6.8 on 32-bit PA-RISC kernel-image-2.6.8-4-32-smp - Linux kernel image for version 2.6.8 on 32-bit PA-RISC kernel-image-2.6.8-4-64 - Linux kernel image for version 2.6.8 on 64-bit PA-RISC kernel-image-2.6.8-4-64-smp - Linux kernel image for version 2.6.8 on 64-bit PA-RISC Closes: 311357 317286 321442 323557 336153 349774 354493 372621 Changes: kernel-image-2.6.8-hppa (2.6.8-7) oldstable; urgency=high . * Rebuild against kernel-tree-2.6.8-17 [ Simon Horman ] *
Bug#336153: marked as done (kernel-image-2.6.8-2-386: Filesystem errors while writing to DM disk)
Your message dated Mon, 28 May 2007 23:06:04 + with message-id [EMAIL PROTECTED] and subject line Bug#336153: fixed in kernel-image-2.6.8-alpha 2.6.8-17 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: kernel-image-2.6.8-2-386 Severity: critical Justification: causes serious data loss Szenario: While copying some GBs to the filesystem under heavy load the filesystem gets corrupted. The SMART Status of all disks is passed, they are all new. The hardware components of the server should work fine too, used this server (cpu, motherboard, etc) before, just exchanged the harddisks. Error Message: Oct 27 23:36:34 localhost kernel: init_special_inode: bogus i_mode (4152) Oct 27 23:36:34 localhost kernel: init_special_inode: bogus i_mode (117230) Oct 27 23:36:45 localhost kernel: attempt to access beyond end of device Oct 27 23:36:45 localhost kernel: dm-0: rw=0, want=20177444552, limit=962598144 (last 2 lines repeating nonstop) Versions: - Unmodified Debian Sarge Kernel 2.6.8-2-386 - Debian Sarge utils last updated 27.10.05 Filesystem Layout: - ext2 (was ext3, but removed the journal with tune2fs) on top of - dmcrypt (aes-plain) /dev/mapper/croot on top of - RAID5 /dev/md2 on top of - 4x 160GB IDE /dev/hd[abcd]3 blacksheep:~# fdisk -l /dev/hd[abcd] Disk /dev/hda: 164.6 GB, 16469620 bytes 255 heads, 63 sectors/track, 20023 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/hda1 * 1 13 104391 fd Linux raid autodetect /dev/hda2 14 50 297202+ fd Linux raid autodetect /dev/hda3 51 20023 160433122+ fd Linux raid autodetect Disk /dev/hdb: 164.6 GB, 16469620 bytes 255 heads, 63 sectors/track, 20023 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/hdb1 * 1 13 104391 fd Linux raid autodetect /dev/hdb2 14 50 297202+ fd Linux raid autodetect /dev/hdb3 51 20023 160433122+ fd Linux raid autodetect Disk /dev/hdc: 164.6 GB, 16469620 bytes 255 heads, 63 sectors/track, 20023 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/hdc1 * 1 13 104391 fd Linux raid autodetect /dev/hdc2 14 50 297202+ fd Linux raid autodetect /dev/hdc3 51 20023 160433122+ fd Linux raid autodetect Disk /dev/hdd: 164.6 GB, 16469620 bytes 255 heads, 63 sectors/track, 20023 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/hdd1 * 1 13 104391 fd Linux raid autodetect /dev/hdd2 14 50 297202+ fd Linux raid autodetect /dev/hdd3 51 20023 160433122+ fd Linux raid autodetect blacksheep:~# cat /proc/mdstat Personalities : [raid1] [raid5] md0 : active raid1 hdd1[3] hda1[0] hdc1[2] hdb1[1] 104320 blocks [4/4] [] md1 : active raid5 hdd2[3] hda2[0] hdc2[2] hdb2[1] 891264 blocks level 5, 64k chunk, algorithm 2 [4/4] [] md2 : active raid5 hdd3[4] hda3[0] hdc3[2] hdb3[1] 481299072 blocks level 5, 64k chunk, algorithm 2 [4/3] [UUU_] [] recovery = 20.6% (33203840/160433024) finish=339.4min speed=6246K/sec unused devices: none blacksheep:~# dmsetup info croot Name: croot State: ACTIVE Tables present:LIVE Open count:1 Event number: 0 Major, minor: 254, 0 Number of targets: 1 blacksheep:~# dmsetup status croot 0 962598144 crypt blacksheep:~# dmsetup table croot 0 962598144 crypt aes-plain perhapsthatsmysecretkeyidontknow 0 9:2 0 blacksheep:~# cat /etc/crypttab # target device source device key file options cswap /dev/md1/dev/random swap croot /dev/md2nonecipher=aes-plain blacksheep:~# cat /etc/fstab # /etc/fstab: static file system information. # # file system mount point type options dump pass proc/proc procdefaults0 0 /dev/mapper/cswap none swapsw 0 0 /dev/mapper/croot /
Bug#321442: marked as done (kernel-source-2.6.8: fails to compile on powerpc (drivers/ide/ppc/pmac.c))
Your message dated Mon, 28 May 2007 23:06:30 + with message-id [EMAIL PROTECTED] and subject line Bug#321442: fixed in kernel-image-2.6.8-sparc 2.6.8-16 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: kernel-source-2.6.8 Version: 2.6.8-16 Severity: normal The kernel-source-2.6.8 sources fail to compile on powerpc (PowerMac 4400). ___ CC drivers/ide/ide.o CC drivers/ide/ide-default.o CC drivers/ide/ide-io.o CC drivers/ide/ide-iops.o CC drivers/ide/ide-lib.o CC drivers/ide/ide-probe.o CC drivers/ide/ide-taskfile.o CC drivers/ide/ide-dma.o CC drivers/ide/ide-proc.o CC drivers/ide/ppc/pmac.o drivers/ide/ppc/pmac.c: Dans la fonction « pmac_ide_dma_read »: drivers/ide/ppc/pmac.c:1951: error: `ide_dma_intr' undeclared (first use in this function) drivers/ide/ppc/pmac.c:1951: error: (Each undeclared identifier is reported only once drivers/ide/ppc/pmac.c:1951: error: for each function it appears in.) drivers/ide/ppc/pmac.c: Dans la fonction « pmac_ide_dma_write »: drivers/ide/ppc/pmac.c:1982: error: `ide_dma_intr' undeclared (first use in this function) drivers/ide/ppc/pmac.c: Dans la fonction « pmac_ide_setup_dma »: drivers/ide/ppc/pmac.c:2157: error: `__ide_dma_off_quietly' undeclared (first use in this function) drivers/ide/ppc/pmac.c:2158: error: `__ide_dma_on' undeclared (first use in this function) drivers/ide/ppc/pmac.c:2167: error: `__ide_dma_verbose' undeclared (first use in this function) drivers/ide/ppc/pmac.c:2168: error: `__ide_dma_timeout' undeclared (first use in this function) make[3]: *** [drivers/ide/ppc/pmac.o] Error 1 make[2]: *** [drivers/ide] Error 2 make[1]: *** [drivers] Error 2 ___ -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: powerpc (ppc) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.4.26-ltp Locale: LANG=fr_FR, LC_CTYPE=fr_FR (charmap=UTF-8) (ignored: LC_ALL set to fr_FR.UTF-8) Versions of packages kernel-source-2.6.8 depends on: ii binutils 2.16.1-2 The GNU assembler, linker and bina ii bzip2 1.0.2-8high-quality block-sorting file co ii coreutils [fileutils] 5.2.1-2The GNU core utilities ii fileutils 5.2.1-2The GNU file management utilities Versions of packages kernel-source-2.6.8 recommends: ii gcc 4:3.3.5-3The GNU C compiler ii libc6-dev [libc-dev]2.3.2.ds1-22 GNU C Library: Development Librari ii make3.80-9 The GNU version of the make util -- no debconf information ---End Message--- ---BeginMessage--- Source: kernel-image-2.6.8-sparc Source-Version: 2.6.8-16 We believe that the bug you reported is fixed in the latest version of kernel-image-2.6.8-sparc, which is due to be installed in the Debian FTP archive: kernel-build-2.6.8-4_2.6.8-16_sparc.deb to pool/main/k/kernel-image-2.6.8-sparc/kernel-build-2.6.8-4_2.6.8-16_sparc.deb kernel-headers-2.6.8-4-sparc32_2.6.8-16_sparc.deb to pool/main/k/kernel-image-2.6.8-sparc/kernel-headers-2.6.8-4-sparc32_2.6.8-16_sparc.deb kernel-headers-2.6.8-4-sparc64-smp_2.6.8-16_sparc.deb to pool/main/k/kernel-image-2.6.8-sparc/kernel-headers-2.6.8-4-sparc64-smp_2.6.8-16_sparc.deb kernel-headers-2.6.8-4-sparc64_2.6.8-16_sparc.deb to pool/main/k/kernel-image-2.6.8-sparc/kernel-headers-2.6.8-4-sparc64_2.6.8-16_sparc.deb kernel-headers-2.6.8-4_2.6.8-16_sparc.deb to pool/main/k/kernel-image-2.6.8-sparc/kernel-headers-2.6.8-4_2.6.8-16_sparc.deb kernel-image-2.6.8-4-sparc32_2.6.8-16_sparc.deb to pool/main/k/kernel-image-2.6.8-sparc/kernel-image-2.6.8-4-sparc32_2.6.8-16_sparc.deb kernel-image-2.6.8-4-sparc64-smp_2.6.8-16_sparc.deb to pool/main/k/kernel-image-2.6.8-sparc/kernel-image-2.6.8-4-sparc64-smp_2.6.8-16_sparc.deb kernel-image-2.6.8-4-sparc64_2.6.8-16_sparc.deb to pool/main/k/kernel-image-2.6.8-sparc/kernel-image-2.6.8-4-sparc64_2.6.8-16_sparc.deb kernel-image-2.6.8-sparc_2.6.8-16.dsc to pool/main/k/kernel-image-2.6.8-sparc/kernel-image-2.6.8-sparc_2.6.8-16.dsc kernel-image-2.6.8-sparc_2.6.8-16.tar.gz to pool/main/k/kernel-image-2.6.8-sparc/kernel-image-2.6.8-sparc_2.6.8-16.tar.gz A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the
Bug#317286: marked as done (Please backport support for Promise SATAII TX2/TX4 cards (from 2.6.11))
Your message dated Mon, 28 May 2007 23:06:22 + with message-id [EMAIL PROTECTED] and subject line Bug#317286: fixed in kernel-image-2.6.8-i386 2.6.8-17 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: kernel-source Version: 2.6.8-16 This version of the kernel does not support Promise SATAII TX2/TX4 cards. (Note SATAII, Not to be confused with regular Promise SATA TX2/4 cards). Support for these cards was added to kernel 2.6.11. From the Changelog (http://www.kernel.org/pub/linux/kernel/v2.6/ChangeLog-2.6.11): [EMAIL PROTECTED] [libata sata_promise] support Promise SATAII TX2/TX4 cards Originally from Peter Smith, with testing and additional contributions from Jens Axboe. I politely request that someone back port the Promise support to Debian's 2.6.8 kernel. Thank You ---End Message--- ---BeginMessage--- Source: kernel-image-2.6.8-i386 Source-Version: 2.6.8-17 We believe that the bug you reported is fixed in the latest version of kernel-image-2.6.8-i386, which is due to be installed in the Debian FTP archive: kernel-headers-2.6.8-4-386_2.6.8-17_i386.deb to pool/main/k/kernel-image-2.6.8-i386/kernel-headers-2.6.8-4-386_2.6.8-17_i386.deb kernel-headers-2.6.8-4-686-smp_2.6.8-17_i386.deb to pool/main/k/kernel-image-2.6.8-i386/kernel-headers-2.6.8-4-686-smp_2.6.8-17_i386.deb kernel-headers-2.6.8-4-686_2.6.8-17_i386.deb to pool/main/k/kernel-image-2.6.8-i386/kernel-headers-2.6.8-4-686_2.6.8-17_i386.deb kernel-headers-2.6.8-4-k7-smp_2.6.8-17_i386.deb to pool/main/k/kernel-image-2.6.8-i386/kernel-headers-2.6.8-4-k7-smp_2.6.8-17_i386.deb kernel-headers-2.6.8-4-k7_2.6.8-17_i386.deb to pool/main/k/kernel-image-2.6.8-i386/kernel-headers-2.6.8-4-k7_2.6.8-17_i386.deb kernel-headers-2.6.8-4_2.6.8-17_i386.deb to pool/main/k/kernel-image-2.6.8-i386/kernel-headers-2.6.8-4_2.6.8-17_i386.deb kernel-image-2.6.8-4-386_2.6.8-17_i386.deb to pool/main/k/kernel-image-2.6.8-i386/kernel-image-2.6.8-4-386_2.6.8-17_i386.deb kernel-image-2.6.8-4-686-smp_2.6.8-17_i386.deb to pool/main/k/kernel-image-2.6.8-i386/kernel-image-2.6.8-4-686-smp_2.6.8-17_i386.deb kernel-image-2.6.8-4-686_2.6.8-17_i386.deb to pool/main/k/kernel-image-2.6.8-i386/kernel-image-2.6.8-4-686_2.6.8-17_i386.deb kernel-image-2.6.8-4-k7-smp_2.6.8-17_i386.deb to pool/main/k/kernel-image-2.6.8-i386/kernel-image-2.6.8-4-k7-smp_2.6.8-17_i386.deb kernel-image-2.6.8-4-k7_2.6.8-17_i386.deb to pool/main/k/kernel-image-2.6.8-i386/kernel-image-2.6.8-4-k7_2.6.8-17_i386.deb kernel-image-2.6.8-i386_2.6.8-17.dsc to pool/main/k/kernel-image-2.6.8-i386/kernel-image-2.6.8-i386_2.6.8-17.dsc kernel-image-2.6.8-i386_2.6.8-17.tar.gz to pool/main/k/kernel-image-2.6.8-i386/kernel-image-2.6.8-i386_2.6.8-17.tar.gz A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. dann frazier [EMAIL PROTECTED] (supplier of updated kernel-image-2.6.8-i386 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 26 May 2007 03:59:02 -0600 Source: kernel-image-2.6.8-i386 Binary: kernel-headers-2.6.8-4-686-smp kernel-headers-2.6.8-4-686 kernel-headers-2.6.8-4-386 kernel-image-2.6.8-4-386 kernel-image-2.6.8-4-k7 kernel-image-2.6.8-4-686-smp kernel-headers-2.6.8-4 kernel-image-2.6.8-4-686 kernel-headers-2.6.8-4-k7-smp kernel-image-2.6.8-4-k7-smp kernel-headers-2.6.8-4-k7 Architecture: source i386 Version: 2.6.8-17 Distribution: oldstable Urgency: high Maintainer: Debian kernel team debian-kernel@lists.debian.org Changed-By: dann frazier [EMAIL PROTECTED] Description: kernel-headers-2.6.8-4 - Header files related to Linux kernel version 2.6.8 kernel-headers-2.6.8-4-386 - Linux kernel headers 2.6.8 on 386 kernel-headers-2.6.8-4-686 - Linux kernel headers 2.6.8 on PPro/Celeron/PII/PIII/P4 kernel-headers-2.6.8-4-686-smp - Linux kernel headers 2.6.8 on PPro/Celeron/PII/PIII/P4 SMP kernel-headers-2.6.8-4-k7 - Linux kernel headers 2.6.8 on AMD K7 kernel-headers-2.6.8-4-k7-smp - Linux kernel headers 2.6.8 on AMD K7 SMP kernel-image-2.6.8-4-386 - Linux kernel image
Bug#354493: marked as done (kernel-source-2.6.8: can't install grub on cciss device)
Your message dated Mon, 28 May 2007 23:06:22 +
with message-id [EMAIL PROTECTED]
and subject line Bug#354493: fixed in kernel-image-2.6.8-i386 2.6.8-17
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
---BeginMessage---
Package: kernel-source-2.6.8
Version: 2.6.8-16sarge2
Severity: normal
Tags: patch
In kernel.org 2.6.8, the block layer (drivers/block/ioctl.c) has:
case BLKFLSBUF:
if (!capable(CAP_SYS_ADMIN))
return -EACCES;
if (disk-fops-ioctl) {
ret = disk-fops-ioctl(inode, file, cmd, arg);
if (ret != -EINVAL)
return ret;
}
fsync_bdev(bdev);
invalidate_bdev(bdev, 0);
return 0;
So, fsync_bdev()/invalidate_bdev() are only called if ret == -EINVAL.
In pristine 2.6.8, cciss returned -EBADRQC, so these functions were never
called.
In 2.6.9, the block layer was modified to also accept -ENOTTY:
http://www.kernel.org/git/?p=linux/kernel/git/torvalds/old-2.6-bkcvs.git;a=commitdiff;h=b295216702a8fb86ef8e3951df9d7118746e35c7
So, in 2.6.10-rc4, the only fix needed was to make cciss return -ENOTTY, which
is what Mike submitted.
http://www.kernel.org/git/?p=linux/kernel/git/torvalds/old-2.6-bkcvs.git;a=commitdiff;h=d28d721eb3f7df904fb1533d314879da33f9b50a
Since 2.6.8 didn't accept -ENOTTY, simply backporting this fix wasn't enough to
fix the bug in 2.6.8, we also need the block layer changeset.
-- System Information:
Debian Release: 3.1
Architecture: ia64
Kernel: Linux 2.6.8-2-mckinley-smp
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages kernel-source-2.6.8 depends on:
ii binutils 2.15-6 The GNU assembler, linker and bina
ii bzip2 1.0.2-7high-quality block-sorting file co
ii coreutils [fileutils] 5.2.1-2The GNU core utilities
-- no debconf information
---End Message---
---BeginMessage---
Source: kernel-image-2.6.8-i386
Source-Version: 2.6.8-17
We believe that the bug you reported is fixed in the latest version of
kernel-image-2.6.8-i386, which is due to be installed in the Debian FTP archive:
kernel-headers-2.6.8-4-386_2.6.8-17_i386.deb
to
pool/main/k/kernel-image-2.6.8-i386/kernel-headers-2.6.8-4-386_2.6.8-17_i386.deb
kernel-headers-2.6.8-4-686-smp_2.6.8-17_i386.deb
to
pool/main/k/kernel-image-2.6.8-i386/kernel-headers-2.6.8-4-686-smp_2.6.8-17_i386.deb
kernel-headers-2.6.8-4-686_2.6.8-17_i386.deb
to
pool/main/k/kernel-image-2.6.8-i386/kernel-headers-2.6.8-4-686_2.6.8-17_i386.deb
kernel-headers-2.6.8-4-k7-smp_2.6.8-17_i386.deb
to
pool/main/k/kernel-image-2.6.8-i386/kernel-headers-2.6.8-4-k7-smp_2.6.8-17_i386.deb
kernel-headers-2.6.8-4-k7_2.6.8-17_i386.deb
to
pool/main/k/kernel-image-2.6.8-i386/kernel-headers-2.6.8-4-k7_2.6.8-17_i386.deb
kernel-headers-2.6.8-4_2.6.8-17_i386.deb
to
pool/main/k/kernel-image-2.6.8-i386/kernel-headers-2.6.8-4_2.6.8-17_i386.deb
kernel-image-2.6.8-4-386_2.6.8-17_i386.deb
to
pool/main/k/kernel-image-2.6.8-i386/kernel-image-2.6.8-4-386_2.6.8-17_i386.deb
kernel-image-2.6.8-4-686-smp_2.6.8-17_i386.deb
to
pool/main/k/kernel-image-2.6.8-i386/kernel-image-2.6.8-4-686-smp_2.6.8-17_i386.deb
kernel-image-2.6.8-4-686_2.6.8-17_i386.deb
to
pool/main/k/kernel-image-2.6.8-i386/kernel-image-2.6.8-4-686_2.6.8-17_i386.deb
kernel-image-2.6.8-4-k7-smp_2.6.8-17_i386.deb
to
pool/main/k/kernel-image-2.6.8-i386/kernel-image-2.6.8-4-k7-smp_2.6.8-17_i386.deb
kernel-image-2.6.8-4-k7_2.6.8-17_i386.deb
to
pool/main/k/kernel-image-2.6.8-i386/kernel-image-2.6.8-4-k7_2.6.8-17_i386.deb
kernel-image-2.6.8-i386_2.6.8-17.dsc
to pool/main/k/kernel-image-2.6.8-i386/kernel-image-2.6.8-i386_2.6.8-17.dsc
kernel-image-2.6.8-i386_2.6.8-17.tar.gz
to pool/main/k/kernel-image-2.6.8-i386/kernel-image-2.6.8-i386_2.6.8-17.tar.gz
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
dann frazier [EMAIL PROTECTED] (supplier of updated kernel-image-2.6.8-i386
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])
-BEGIN PGP SIGNED
Bug#336153: marked as done (kernel-image-2.6.8-2-386: Filesystem errors while writing to DM disk)
Your message dated Mon, 28 May 2007 23:06:34 + with message-id [EMAIL PROTECTED] and subject line Bug#336153: fixed in kernel-patch-powerpc-2.6.8 2.6.8-13 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: kernel-image-2.6.8-2-386 Severity: critical Justification: causes serious data loss Szenario: While copying some GBs to the filesystem under heavy load the filesystem gets corrupted. The SMART Status of all disks is passed, they are all new. The hardware components of the server should work fine too, used this server (cpu, motherboard, etc) before, just exchanged the harddisks. Error Message: Oct 27 23:36:34 localhost kernel: init_special_inode: bogus i_mode (4152) Oct 27 23:36:34 localhost kernel: init_special_inode: bogus i_mode (117230) Oct 27 23:36:45 localhost kernel: attempt to access beyond end of device Oct 27 23:36:45 localhost kernel: dm-0: rw=0, want=20177444552, limit=962598144 (last 2 lines repeating nonstop) Versions: - Unmodified Debian Sarge Kernel 2.6.8-2-386 - Debian Sarge utils last updated 27.10.05 Filesystem Layout: - ext2 (was ext3, but removed the journal with tune2fs) on top of - dmcrypt (aes-plain) /dev/mapper/croot on top of - RAID5 /dev/md2 on top of - 4x 160GB IDE /dev/hd[abcd]3 blacksheep:~# fdisk -l /dev/hd[abcd] Disk /dev/hda: 164.6 GB, 16469620 bytes 255 heads, 63 sectors/track, 20023 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/hda1 * 1 13 104391 fd Linux raid autodetect /dev/hda2 14 50 297202+ fd Linux raid autodetect /dev/hda3 51 20023 160433122+ fd Linux raid autodetect Disk /dev/hdb: 164.6 GB, 16469620 bytes 255 heads, 63 sectors/track, 20023 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/hdb1 * 1 13 104391 fd Linux raid autodetect /dev/hdb2 14 50 297202+ fd Linux raid autodetect /dev/hdb3 51 20023 160433122+ fd Linux raid autodetect Disk /dev/hdc: 164.6 GB, 16469620 bytes 255 heads, 63 sectors/track, 20023 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/hdc1 * 1 13 104391 fd Linux raid autodetect /dev/hdc2 14 50 297202+ fd Linux raid autodetect /dev/hdc3 51 20023 160433122+ fd Linux raid autodetect Disk /dev/hdd: 164.6 GB, 16469620 bytes 255 heads, 63 sectors/track, 20023 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/hdd1 * 1 13 104391 fd Linux raid autodetect /dev/hdd2 14 50 297202+ fd Linux raid autodetect /dev/hdd3 51 20023 160433122+ fd Linux raid autodetect blacksheep:~# cat /proc/mdstat Personalities : [raid1] [raid5] md0 : active raid1 hdd1[3] hda1[0] hdc1[2] hdb1[1] 104320 blocks [4/4] [] md1 : active raid5 hdd2[3] hda2[0] hdc2[2] hdb2[1] 891264 blocks level 5, 64k chunk, algorithm 2 [4/4] [] md2 : active raid5 hdd3[4] hda3[0] hdc3[2] hdb3[1] 481299072 blocks level 5, 64k chunk, algorithm 2 [4/3] [UUU_] [] recovery = 20.6% (33203840/160433024) finish=339.4min speed=6246K/sec unused devices: none blacksheep:~# dmsetup info croot Name: croot State: ACTIVE Tables present:LIVE Open count:1 Event number: 0 Major, minor: 254, 0 Number of targets: 1 blacksheep:~# dmsetup status croot 0 962598144 crypt blacksheep:~# dmsetup table croot 0 962598144 crypt aes-plain perhapsthatsmysecretkeyidontknow 0 9:2 0 blacksheep:~# cat /etc/crypttab # target device source device key file options cswap /dev/md1/dev/random swap croot /dev/md2nonecipher=aes-plain blacksheep:~# cat /etc/fstab # /etc/fstab: static file system information. # # file system mount point type options dump pass proc/proc procdefaults0 0 /dev/mapper/cswap none swapsw 0 0 /dev/mapper/croot /
Bug#336153: marked as done (kernel-image-2.6.8-2-386: Filesystem errors while writing to DM disk)
Your message dated Mon, 28 May 2007 23:06:09 + with message-id [EMAIL PROTECTED] and subject line Bug#336153: fixed in kernel-image-2.6.8-amd64 2.6.8-17 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: kernel-image-2.6.8-2-386 Severity: critical Justification: causes serious data loss Szenario: While copying some GBs to the filesystem under heavy load the filesystem gets corrupted. The SMART Status of all disks is passed, they are all new. The hardware components of the server should work fine too, used this server (cpu, motherboard, etc) before, just exchanged the harddisks. Error Message: Oct 27 23:36:34 localhost kernel: init_special_inode: bogus i_mode (4152) Oct 27 23:36:34 localhost kernel: init_special_inode: bogus i_mode (117230) Oct 27 23:36:45 localhost kernel: attempt to access beyond end of device Oct 27 23:36:45 localhost kernel: dm-0: rw=0, want=20177444552, limit=962598144 (last 2 lines repeating nonstop) Versions: - Unmodified Debian Sarge Kernel 2.6.8-2-386 - Debian Sarge utils last updated 27.10.05 Filesystem Layout: - ext2 (was ext3, but removed the journal with tune2fs) on top of - dmcrypt (aes-plain) /dev/mapper/croot on top of - RAID5 /dev/md2 on top of - 4x 160GB IDE /dev/hd[abcd]3 blacksheep:~# fdisk -l /dev/hd[abcd] Disk /dev/hda: 164.6 GB, 16469620 bytes 255 heads, 63 sectors/track, 20023 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/hda1 * 1 13 104391 fd Linux raid autodetect /dev/hda2 14 50 297202+ fd Linux raid autodetect /dev/hda3 51 20023 160433122+ fd Linux raid autodetect Disk /dev/hdb: 164.6 GB, 16469620 bytes 255 heads, 63 sectors/track, 20023 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/hdb1 * 1 13 104391 fd Linux raid autodetect /dev/hdb2 14 50 297202+ fd Linux raid autodetect /dev/hdb3 51 20023 160433122+ fd Linux raid autodetect Disk /dev/hdc: 164.6 GB, 16469620 bytes 255 heads, 63 sectors/track, 20023 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/hdc1 * 1 13 104391 fd Linux raid autodetect /dev/hdc2 14 50 297202+ fd Linux raid autodetect /dev/hdc3 51 20023 160433122+ fd Linux raid autodetect Disk /dev/hdd: 164.6 GB, 16469620 bytes 255 heads, 63 sectors/track, 20023 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/hdd1 * 1 13 104391 fd Linux raid autodetect /dev/hdd2 14 50 297202+ fd Linux raid autodetect /dev/hdd3 51 20023 160433122+ fd Linux raid autodetect blacksheep:~# cat /proc/mdstat Personalities : [raid1] [raid5] md0 : active raid1 hdd1[3] hda1[0] hdc1[2] hdb1[1] 104320 blocks [4/4] [] md1 : active raid5 hdd2[3] hda2[0] hdc2[2] hdb2[1] 891264 blocks level 5, 64k chunk, algorithm 2 [4/4] [] md2 : active raid5 hdd3[4] hda3[0] hdc3[2] hdb3[1] 481299072 blocks level 5, 64k chunk, algorithm 2 [4/3] [UUU_] [] recovery = 20.6% (33203840/160433024) finish=339.4min speed=6246K/sec unused devices: none blacksheep:~# dmsetup info croot Name: croot State: ACTIVE Tables present:LIVE Open count:1 Event number: 0 Major, minor: 254, 0 Number of targets: 1 blacksheep:~# dmsetup status croot 0 962598144 crypt blacksheep:~# dmsetup table croot 0 962598144 crypt aes-plain perhapsthatsmysecretkeyidontknow 0 9:2 0 blacksheep:~# cat /etc/crypttab # target device source device key file options cswap /dev/md1/dev/random swap croot /dev/md2nonecipher=aes-plain blacksheep:~# cat /etc/fstab # /etc/fstab: static file system information. # # file system mount point type options dump pass proc/proc procdefaults0 0 /dev/mapper/cswap none swapsw 0 0 /dev/mapper/croot /
Bug#354493: marked as done (kernel-source-2.6.8: can't install grub on cciss device)
Your message dated Mon, 28 May 2007 23:06:26 +
with message-id [EMAIL PROTECTED]
and subject line Bug#354493: fixed in kernel-image-2.6.8-ia64 2.6.8-15
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
---BeginMessage---
Package: kernel-source-2.6.8
Version: 2.6.8-16sarge2
Severity: normal
Tags: patch
In kernel.org 2.6.8, the block layer (drivers/block/ioctl.c) has:
case BLKFLSBUF:
if (!capable(CAP_SYS_ADMIN))
return -EACCES;
if (disk-fops-ioctl) {
ret = disk-fops-ioctl(inode, file, cmd, arg);
if (ret != -EINVAL)
return ret;
}
fsync_bdev(bdev);
invalidate_bdev(bdev, 0);
return 0;
So, fsync_bdev()/invalidate_bdev() are only called if ret == -EINVAL.
In pristine 2.6.8, cciss returned -EBADRQC, so these functions were never
called.
In 2.6.9, the block layer was modified to also accept -ENOTTY:
http://www.kernel.org/git/?p=linux/kernel/git/torvalds/old-2.6-bkcvs.git;a=commitdiff;h=b295216702a8fb86ef8e3951df9d7118746e35c7
So, in 2.6.10-rc4, the only fix needed was to make cciss return -ENOTTY, which
is what Mike submitted.
http://www.kernel.org/git/?p=linux/kernel/git/torvalds/old-2.6-bkcvs.git;a=commitdiff;h=d28d721eb3f7df904fb1533d314879da33f9b50a
Since 2.6.8 didn't accept -ENOTTY, simply backporting this fix wasn't enough to
fix the bug in 2.6.8, we also need the block layer changeset.
-- System Information:
Debian Release: 3.1
Architecture: ia64
Kernel: Linux 2.6.8-2-mckinley-smp
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages kernel-source-2.6.8 depends on:
ii binutils 2.15-6 The GNU assembler, linker and bina
ii bzip2 1.0.2-7high-quality block-sorting file co
ii coreutils [fileutils] 5.2.1-2The GNU core utilities
-- no debconf information
---End Message---
---BeginMessage---
Source: kernel-image-2.6.8-ia64
Source-Version: 2.6.8-15
We believe that the bug you reported is fixed in the latest version of
kernel-image-2.6.8-ia64, which is due to be installed in the Debian FTP archive:
kernel-headers-2.6-itanium-smp_2.6.8-15_ia64.deb
to
pool/main/k/kernel-image-2.6.8-ia64/kernel-headers-2.6-itanium-smp_2.6.8-15_ia64.deb
kernel-headers-2.6-itanium_2.6.8-15_ia64.deb
to
pool/main/k/kernel-image-2.6.8-ia64/kernel-headers-2.6-itanium_2.6.8-15_ia64.deb
kernel-headers-2.6-mckinley-smp_2.6.8-15_ia64.deb
to
pool/main/k/kernel-image-2.6.8-ia64/kernel-headers-2.6-mckinley-smp_2.6.8-15_ia64.deb
kernel-headers-2.6-mckinley_2.6.8-15_ia64.deb
to
pool/main/k/kernel-image-2.6.8-ia64/kernel-headers-2.6-mckinley_2.6.8-15_ia64.deb
kernel-headers-2.6.8-4-itanium-smp_2.6.8-15_ia64.deb
to
pool/main/k/kernel-image-2.6.8-ia64/kernel-headers-2.6.8-4-itanium-smp_2.6.8-15_ia64.deb
kernel-headers-2.6.8-4-itanium_2.6.8-15_ia64.deb
to
pool/main/k/kernel-image-2.6.8-ia64/kernel-headers-2.6.8-4-itanium_2.6.8-15_ia64.deb
kernel-headers-2.6.8-4-mckinley-smp_2.6.8-15_ia64.deb
to
pool/main/k/kernel-image-2.6.8-ia64/kernel-headers-2.6.8-4-mckinley-smp_2.6.8-15_ia64.deb
kernel-headers-2.6.8-4-mckinley_2.6.8-15_ia64.deb
to
pool/main/k/kernel-image-2.6.8-ia64/kernel-headers-2.6.8-4-mckinley_2.6.8-15_ia64.deb
kernel-headers-2.6.8-4_2.6.8-15_ia64.deb
to
pool/main/k/kernel-image-2.6.8-ia64/kernel-headers-2.6.8-4_2.6.8-15_ia64.deb
kernel-image-2.6-itanium-smp_2.6.8-15_ia64.deb
to
pool/main/k/kernel-image-2.6.8-ia64/kernel-image-2.6-itanium-smp_2.6.8-15_ia64.deb
kernel-image-2.6-itanium_2.6.8-15_ia64.deb
to
pool/main/k/kernel-image-2.6.8-ia64/kernel-image-2.6-itanium_2.6.8-15_ia64.deb
kernel-image-2.6-mckinley-smp_2.6.8-15_ia64.deb
to
pool/main/k/kernel-image-2.6.8-ia64/kernel-image-2.6-mckinley-smp_2.6.8-15_ia64.deb
kernel-image-2.6-mckinley_2.6.8-15_ia64.deb
to
pool/main/k/kernel-image-2.6.8-ia64/kernel-image-2.6-mckinley_2.6.8-15_ia64.deb
kernel-image-2.6.8-4-itanium-smp_2.6.8-15_ia64.deb
to
pool/main/k/kernel-image-2.6.8-ia64/kernel-image-2.6.8-4-itanium-smp_2.6.8-15_ia64.deb
kernel-image-2.6.8-4-itanium_2.6.8-15_ia64.deb
to
pool/main/k/kernel-image-2.6.8-ia64/kernel-image-2.6.8-4-itanium_2.6.8-15_ia64.deb
kernel-image-2.6.8-4-mckinley-smp_2.6.8-15_ia64.deb
to
pool/main/k/kernel-image-2.6.8-ia64/kernel-image-2.6.8-4-mckinley-smp_2.6.8-15_ia64.deb
kernel-image-2.6.8-4-mckinley_2.6.8-15_ia64.deb
to
Bug#372621: marked as done (old bug in ipt_ULOG (error during NLMSG_PUT))
Your message dated Mon, 28 May 2007 23:06:04 + with message-id [EMAIL PROTECTED] and subject line Bug#372621: fixed in kernel-image-2.6.8-alpha 2.6.8-17 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: kernel-source-2.6.8 Version: 2.6.8-16sarge2 When I used fprobe-ulog kernel printed sometimes: ipt_ULOG: error during NLMSG_PUT I google'd that this problem (actually bug) was solved in 2.6.10 by Harald Welte [EMAIL PROTECTED]. See: http://oss.sgi.com/archives/netdev/2004-10/msg01026.html (there is a small patch) http://www.kernel.org/pub/linux/kernel/v2.6/ChangeLog-2.6.10 It seems both 2.6 and 2.4 debian kernels affected. I use Debian GNU/Linux 3.1r2 (with last updates), kernel 2.6.8-2-686-smp. ---End Message--- ---BeginMessage--- Source: kernel-image-2.6.8-alpha Source-Version: 2.6.8-17 We believe that the bug you reported is fixed in the latest version of kernel-image-2.6.8-alpha, which is due to be installed in the Debian FTP archive: kernel-headers-2.6.8-4-generic_2.6.8-17_alpha.deb to pool/main/k/kernel-image-2.6.8-alpha/kernel-headers-2.6.8-4-generic_2.6.8-17_alpha.deb kernel-headers-2.6.8-4-smp_2.6.8-17_alpha.deb to pool/main/k/kernel-image-2.6.8-alpha/kernel-headers-2.6.8-4-smp_2.6.8-17_alpha.deb kernel-headers-2.6.8-4_2.6.8-17_alpha.deb to pool/main/k/kernel-image-2.6.8-alpha/kernel-headers-2.6.8-4_2.6.8-17_alpha.deb kernel-image-2.6.8-4-generic_2.6.8-17_alpha.deb to pool/main/k/kernel-image-2.6.8-alpha/kernel-image-2.6.8-4-generic_2.6.8-17_alpha.deb kernel-image-2.6.8-4-smp_2.6.8-17_alpha.deb to pool/main/k/kernel-image-2.6.8-alpha/kernel-image-2.6.8-4-smp_2.6.8-17_alpha.deb kernel-image-2.6.8-alpha_2.6.8-17.dsc to pool/main/k/kernel-image-2.6.8-alpha/kernel-image-2.6.8-alpha_2.6.8-17.dsc kernel-image-2.6.8-alpha_2.6.8-17.tar.gz to pool/main/k/kernel-image-2.6.8-alpha/kernel-image-2.6.8-alpha_2.6.8-17.tar.gz A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. dann frazier [EMAIL PROTECTED] (supplier of updated kernel-image-2.6.8-alpha package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 26 May 2007 03:54:13 -0600 Source: kernel-image-2.6.8-alpha Binary: kernel-headers-2.6.8-4 kernel-image-2.6.8-4-smp kernel-headers-2.6.8-4-smp kernel-image-2.6.8-4-generic kernel-headers-2.6.8-4-generic Architecture: source alpha Version: 2.6.8-17 Distribution: oldstable Urgency: high Maintainer: Debian Kernel Team debian-kernel@lists.debian.org Changed-By: dann frazier [EMAIL PROTECTED] Description: kernel-headers-2.6.8-4 - Header files related to Linux kernel version 2.6.8 kernel-headers-2.6.8-4-generic - Linux kernel headers 2.6.8 on Alpha kernel-headers-2.6.8-4-smp - Linux kernel headers 2.6.8 on Alpha SMP kernel-image-2.6.8-4-generic - Linux kernel image for version 2.6.8 on Alpha. kernel-image-2.6.8-4-smp - Linux kernel image for version 2.6.8 on Alpha SMP. Closes: 311357 317286 321442 323557 336153 349774 354493 372621 Changes: kernel-image-2.6.8-alpha (2.6.8-17) oldstable; urgency=high . * Rebuild against kernel-tree-2.6.8-17 [ Simon Horman ] * drivers-net-via-rhine-wol-oops.dpatch (removed): This patch breaks the via-rhine driver and 2.6.8 and is completely bogus for this version of the kernel (closes: #311357) . * drivers-media-vidio-bttv-vc100xp-detect.dpatch Allow Leadtek WinFast VC100 XP cards to work. . * fs-jbd-checkpoint-assertion.dpatch Fix possible false assertion failure in log_do_checkpoint(). We might fail to detect that we actually made a progress when cleaning up the checkpoint lists if we don't retry after writing something to disk. . * mm-rmap-out-of-bounds-pte.dpatch Stop try_to_unmap_cluster() passing out-of-bounds pte to pte_unmap() . * net-ipv4-netfilter-ip_queue-deadlock.dpatch Fix deadlock with ip_queue and tcp local input path. . * asm-i386-mem-clobber.dpatch: Make sure gcc doesn't reorder memory accesses in strncmp and friends on i386. . *
Bug#354493: marked as done (kernel-source-2.6.8: can't install grub on cciss device)
Your message dated Mon, 28 May 2007 23:06:34 +
with message-id [EMAIL PROTECTED]
and subject line Bug#354493: fixed in kernel-patch-powerpc-2.6.8 2.6.8-13
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
---BeginMessage---
Package: kernel-source-2.6.8
Version: 2.6.8-16sarge2
Severity: normal
Tags: patch
In kernel.org 2.6.8, the block layer (drivers/block/ioctl.c) has:
case BLKFLSBUF:
if (!capable(CAP_SYS_ADMIN))
return -EACCES;
if (disk-fops-ioctl) {
ret = disk-fops-ioctl(inode, file, cmd, arg);
if (ret != -EINVAL)
return ret;
}
fsync_bdev(bdev);
invalidate_bdev(bdev, 0);
return 0;
So, fsync_bdev()/invalidate_bdev() are only called if ret == -EINVAL.
In pristine 2.6.8, cciss returned -EBADRQC, so these functions were never
called.
In 2.6.9, the block layer was modified to also accept -ENOTTY:
http://www.kernel.org/git/?p=linux/kernel/git/torvalds/old-2.6-bkcvs.git;a=commitdiff;h=b295216702a8fb86ef8e3951df9d7118746e35c7
So, in 2.6.10-rc4, the only fix needed was to make cciss return -ENOTTY, which
is what Mike submitted.
http://www.kernel.org/git/?p=linux/kernel/git/torvalds/old-2.6-bkcvs.git;a=commitdiff;h=d28d721eb3f7df904fb1533d314879da33f9b50a
Since 2.6.8 didn't accept -ENOTTY, simply backporting this fix wasn't enough to
fix the bug in 2.6.8, we also need the block layer changeset.
-- System Information:
Debian Release: 3.1
Architecture: ia64
Kernel: Linux 2.6.8-2-mckinley-smp
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages kernel-source-2.6.8 depends on:
ii binutils 2.15-6 The GNU assembler, linker and bina
ii bzip2 1.0.2-7high-quality block-sorting file co
ii coreutils [fileutils] 5.2.1-2The GNU core utilities
-- no debconf information
---End Message---
---BeginMessage---
Source: kernel-patch-powerpc-2.6.8
Source-Version: 2.6.8-13
We believe that the bug you reported is fixed in the latest version of
kernel-patch-powerpc-2.6.8, which is due to be installed in the Debian FTP
archive:
kernel-build-2.6.8-4-power3-smp_2.6.8-13_powerpc.deb
to
pool/main/k/kernel-patch-powerpc-2.6.8/kernel-build-2.6.8-4-power3-smp_2.6.8-13_powerpc.deb
kernel-build-2.6.8-4-power3_2.6.8-13_powerpc.deb
to
pool/main/k/kernel-patch-powerpc-2.6.8/kernel-build-2.6.8-4-power3_2.6.8-13_powerpc.deb
kernel-build-2.6.8-4-power4-smp_2.6.8-13_powerpc.deb
to
pool/main/k/kernel-patch-powerpc-2.6.8/kernel-build-2.6.8-4-power4-smp_2.6.8-13_powerpc.deb
kernel-build-2.6.8-4-power4_2.6.8-13_powerpc.deb
to
pool/main/k/kernel-patch-powerpc-2.6.8/kernel-build-2.6.8-4-power4_2.6.8-13_powerpc.deb
kernel-build-2.6.8-4-powerpc-smp_2.6.8-13_powerpc.deb
to
pool/main/k/kernel-patch-powerpc-2.6.8/kernel-build-2.6.8-4-powerpc-smp_2.6.8-13_powerpc.deb
kernel-build-2.6.8-4-powerpc_2.6.8-13_powerpc.deb
to
pool/main/k/kernel-patch-powerpc-2.6.8/kernel-build-2.6.8-4-powerpc_2.6.8-13_powerpc.deb
kernel-headers-2.6.8-4_2.6.8-13_powerpc.deb
to
pool/main/k/kernel-patch-powerpc-2.6.8/kernel-headers-2.6.8-4_2.6.8-13_powerpc.deb
kernel-image-2.6.8-4-power3-smp_2.6.8-13_powerpc.deb
to
pool/main/k/kernel-patch-powerpc-2.6.8/kernel-image-2.6.8-4-power3-smp_2.6.8-13_powerpc.deb
kernel-image-2.6.8-4-power3_2.6.8-13_powerpc.deb
to
pool/main/k/kernel-patch-powerpc-2.6.8/kernel-image-2.6.8-4-power3_2.6.8-13_powerpc.deb
kernel-image-2.6.8-4-power4-smp_2.6.8-13_powerpc.deb
to
pool/main/k/kernel-patch-powerpc-2.6.8/kernel-image-2.6.8-4-power4-smp_2.6.8-13_powerpc.deb
kernel-image-2.6.8-4-power4_2.6.8-13_powerpc.deb
to
pool/main/k/kernel-patch-powerpc-2.6.8/kernel-image-2.6.8-4-power4_2.6.8-13_powerpc.deb
kernel-image-2.6.8-4-powerpc-smp_2.6.8-13_powerpc.deb
to
pool/main/k/kernel-patch-powerpc-2.6.8/kernel-image-2.6.8-4-powerpc-smp_2.6.8-13_powerpc.deb
kernel-image-2.6.8-4-powerpc_2.6.8-13_powerpc.deb
to
pool/main/k/kernel-patch-powerpc-2.6.8/kernel-image-2.6.8-4-powerpc_2.6.8-13_powerpc.deb
kernel-patch-powerpc-2.6.8_2.6.8-13.dsc
to
pool/main/k/kernel-patch-powerpc-2.6.8/kernel-patch-powerpc-2.6.8_2.6.8-13.dsc
kernel-patch-powerpc-2.6.8_2.6.8-13.tar.gz
to
pool/main/k/kernel-patch-powerpc-2.6.8/kernel-patch-powerpc-2.6.8_2.6.8-13.tar.gz
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will
Bug#321442: marked as done (kernel-source-2.6.8: fails to compile on powerpc (drivers/ide/ppc/pmac.c))
Your message dated Mon, 28 May 2007 23:06:12 + with message-id [EMAIL PROTECTED] and subject line Bug#321442: fixed in kernel-image-2.6.8-hppa 2.6.8-7 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: kernel-source-2.6.8 Version: 2.6.8-16 Severity: normal The kernel-source-2.6.8 sources fail to compile on powerpc (PowerMac 4400). ___ CC drivers/ide/ide.o CC drivers/ide/ide-default.o CC drivers/ide/ide-io.o CC drivers/ide/ide-iops.o CC drivers/ide/ide-lib.o CC drivers/ide/ide-probe.o CC drivers/ide/ide-taskfile.o CC drivers/ide/ide-dma.o CC drivers/ide/ide-proc.o CC drivers/ide/ppc/pmac.o drivers/ide/ppc/pmac.c: Dans la fonction « pmac_ide_dma_read »: drivers/ide/ppc/pmac.c:1951: error: `ide_dma_intr' undeclared (first use in this function) drivers/ide/ppc/pmac.c:1951: error: (Each undeclared identifier is reported only once drivers/ide/ppc/pmac.c:1951: error: for each function it appears in.) drivers/ide/ppc/pmac.c: Dans la fonction « pmac_ide_dma_write »: drivers/ide/ppc/pmac.c:1982: error: `ide_dma_intr' undeclared (first use in this function) drivers/ide/ppc/pmac.c: Dans la fonction « pmac_ide_setup_dma »: drivers/ide/ppc/pmac.c:2157: error: `__ide_dma_off_quietly' undeclared (first use in this function) drivers/ide/ppc/pmac.c:2158: error: `__ide_dma_on' undeclared (first use in this function) drivers/ide/ppc/pmac.c:2167: error: `__ide_dma_verbose' undeclared (first use in this function) drivers/ide/ppc/pmac.c:2168: error: `__ide_dma_timeout' undeclared (first use in this function) make[3]: *** [drivers/ide/ppc/pmac.o] Error 1 make[2]: *** [drivers/ide] Error 2 make[1]: *** [drivers] Error 2 ___ -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: powerpc (ppc) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.4.26-ltp Locale: LANG=fr_FR, LC_CTYPE=fr_FR (charmap=UTF-8) (ignored: LC_ALL set to fr_FR.UTF-8) Versions of packages kernel-source-2.6.8 depends on: ii binutils 2.16.1-2 The GNU assembler, linker and bina ii bzip2 1.0.2-8high-quality block-sorting file co ii coreutils [fileutils] 5.2.1-2The GNU core utilities ii fileutils 5.2.1-2The GNU file management utilities Versions of packages kernel-source-2.6.8 recommends: ii gcc 4:3.3.5-3The GNU C compiler ii libc6-dev [libc-dev]2.3.2.ds1-22 GNU C Library: Development Librari ii make3.80-9 The GNU version of the make util -- no debconf information ---End Message--- ---BeginMessage--- Source: kernel-image-2.6.8-hppa Source-Version: 2.6.8-7 We believe that the bug you reported is fixed in the latest version of kernel-image-2.6.8-hppa, which is due to be installed in the Debian FTP archive: kernel-headers-2.6.8-4-32-smp_2.6.8-7_hppa.deb to pool/main/k/kernel-image-2.6.8-hppa/kernel-headers-2.6.8-4-32-smp_2.6.8-7_hppa.deb kernel-headers-2.6.8-4-32_2.6.8-7_hppa.deb to pool/main/k/kernel-image-2.6.8-hppa/kernel-headers-2.6.8-4-32_2.6.8-7_hppa.deb kernel-headers-2.6.8-4-64-smp_2.6.8-7_hppa.deb to pool/main/k/kernel-image-2.6.8-hppa/kernel-headers-2.6.8-4-64-smp_2.6.8-7_hppa.deb kernel-headers-2.6.8-4-64_2.6.8-7_hppa.deb to pool/main/k/kernel-image-2.6.8-hppa/kernel-headers-2.6.8-4-64_2.6.8-7_hppa.deb kernel-headers-2.6.8-4_2.6.8-7_hppa.deb to pool/main/k/kernel-image-2.6.8-hppa/kernel-headers-2.6.8-4_2.6.8-7_hppa.deb kernel-image-2.6.8-4-32-smp_2.6.8-7_hppa.deb to pool/main/k/kernel-image-2.6.8-hppa/kernel-image-2.6.8-4-32-smp_2.6.8-7_hppa.deb kernel-image-2.6.8-4-32_2.6.8-7_hppa.deb to pool/main/k/kernel-image-2.6.8-hppa/kernel-image-2.6.8-4-32_2.6.8-7_hppa.deb kernel-image-2.6.8-4-64-smp_2.6.8-7_hppa.deb to pool/main/k/kernel-image-2.6.8-hppa/kernel-image-2.6.8-4-64-smp_2.6.8-7_hppa.deb kernel-image-2.6.8-4-64_2.6.8-7_hppa.deb to pool/main/k/kernel-image-2.6.8-hppa/kernel-image-2.6.8-4-64_2.6.8-7_hppa.deb kernel-image-2.6.8-hppa_2.6.8-7.dsc to pool/main/k/kernel-image-2.6.8-hppa/kernel-image-2.6.8-hppa_2.6.8-7.dsc kernel-image-2.6.8-hppa_2.6.8-7.tar.gz to pool/main/k/kernel-image-2.6.8-hppa/kernel-image-2.6.8-hppa_2.6.8-7.tar.gz A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address
Bug#336153: marked as done (kernel-image-2.6.8-2-386: Filesystem errors while writing to DM disk)
Your message dated Mon, 28 May 2007 23:06:22 + with message-id [EMAIL PROTECTED] and subject line Bug#336153: fixed in kernel-image-2.6.8-i386 2.6.8-17 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: kernel-image-2.6.8-2-386 Severity: critical Justification: causes serious data loss Szenario: While copying some GBs to the filesystem under heavy load the filesystem gets corrupted. The SMART Status of all disks is passed, they are all new. The hardware components of the server should work fine too, used this server (cpu, motherboard, etc) before, just exchanged the harddisks. Error Message: Oct 27 23:36:34 localhost kernel: init_special_inode: bogus i_mode (4152) Oct 27 23:36:34 localhost kernel: init_special_inode: bogus i_mode (117230) Oct 27 23:36:45 localhost kernel: attempt to access beyond end of device Oct 27 23:36:45 localhost kernel: dm-0: rw=0, want=20177444552, limit=962598144 (last 2 lines repeating nonstop) Versions: - Unmodified Debian Sarge Kernel 2.6.8-2-386 - Debian Sarge utils last updated 27.10.05 Filesystem Layout: - ext2 (was ext3, but removed the journal with tune2fs) on top of - dmcrypt (aes-plain) /dev/mapper/croot on top of - RAID5 /dev/md2 on top of - 4x 160GB IDE /dev/hd[abcd]3 blacksheep:~# fdisk -l /dev/hd[abcd] Disk /dev/hda: 164.6 GB, 16469620 bytes 255 heads, 63 sectors/track, 20023 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/hda1 * 1 13 104391 fd Linux raid autodetect /dev/hda2 14 50 297202+ fd Linux raid autodetect /dev/hda3 51 20023 160433122+ fd Linux raid autodetect Disk /dev/hdb: 164.6 GB, 16469620 bytes 255 heads, 63 sectors/track, 20023 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/hdb1 * 1 13 104391 fd Linux raid autodetect /dev/hdb2 14 50 297202+ fd Linux raid autodetect /dev/hdb3 51 20023 160433122+ fd Linux raid autodetect Disk /dev/hdc: 164.6 GB, 16469620 bytes 255 heads, 63 sectors/track, 20023 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/hdc1 * 1 13 104391 fd Linux raid autodetect /dev/hdc2 14 50 297202+ fd Linux raid autodetect /dev/hdc3 51 20023 160433122+ fd Linux raid autodetect Disk /dev/hdd: 164.6 GB, 16469620 bytes 255 heads, 63 sectors/track, 20023 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/hdd1 * 1 13 104391 fd Linux raid autodetect /dev/hdd2 14 50 297202+ fd Linux raid autodetect /dev/hdd3 51 20023 160433122+ fd Linux raid autodetect blacksheep:~# cat /proc/mdstat Personalities : [raid1] [raid5] md0 : active raid1 hdd1[3] hda1[0] hdc1[2] hdb1[1] 104320 blocks [4/4] [] md1 : active raid5 hdd2[3] hda2[0] hdc2[2] hdb2[1] 891264 blocks level 5, 64k chunk, algorithm 2 [4/4] [] md2 : active raid5 hdd3[4] hda3[0] hdc3[2] hdb3[1] 481299072 blocks level 5, 64k chunk, algorithm 2 [4/3] [UUU_] [] recovery = 20.6% (33203840/160433024) finish=339.4min speed=6246K/sec unused devices: none blacksheep:~# dmsetup info croot Name: croot State: ACTIVE Tables present:LIVE Open count:1 Event number: 0 Major, minor: 254, 0 Number of targets: 1 blacksheep:~# dmsetup status croot 0 962598144 crypt blacksheep:~# dmsetup table croot 0 962598144 crypt aes-plain perhapsthatsmysecretkeyidontknow 0 9:2 0 blacksheep:~# cat /etc/crypttab # target device source device key file options cswap /dev/md1/dev/random swap croot /dev/md2nonecipher=aes-plain blacksheep:~# cat /etc/fstab # /etc/fstab: static file system information. # # file system mount point type options dump pass proc/proc procdefaults0 0 /dev/mapper/cswap none swapsw 0 0 /dev/mapper/croot /
Bug#317286: marked as done (Please backport support for Promise SATAII TX2/TX4 cards (from 2.6.11))
Your message dated Mon, 28 May 2007 23:06:26 + with message-id [EMAIL PROTECTED] and subject line Bug#317286: fixed in kernel-image-2.6.8-ia64 2.6.8-15 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: kernel-source Version: 2.6.8-16 This version of the kernel does not support Promise SATAII TX2/TX4 cards. (Note SATAII, Not to be confused with regular Promise SATA TX2/4 cards). Support for these cards was added to kernel 2.6.11. From the Changelog (http://www.kernel.org/pub/linux/kernel/v2.6/ChangeLog-2.6.11): [EMAIL PROTECTED] [libata sata_promise] support Promise SATAII TX2/TX4 cards Originally from Peter Smith, with testing and additional contributions from Jens Axboe. I politely request that someone back port the Promise support to Debian's 2.6.8 kernel. Thank You ---End Message--- ---BeginMessage--- Source: kernel-image-2.6.8-ia64 Source-Version: 2.6.8-15 We believe that the bug you reported is fixed in the latest version of kernel-image-2.6.8-ia64, which is due to be installed in the Debian FTP archive: kernel-headers-2.6-itanium-smp_2.6.8-15_ia64.deb to pool/main/k/kernel-image-2.6.8-ia64/kernel-headers-2.6-itanium-smp_2.6.8-15_ia64.deb kernel-headers-2.6-itanium_2.6.8-15_ia64.deb to pool/main/k/kernel-image-2.6.8-ia64/kernel-headers-2.6-itanium_2.6.8-15_ia64.deb kernel-headers-2.6-mckinley-smp_2.6.8-15_ia64.deb to pool/main/k/kernel-image-2.6.8-ia64/kernel-headers-2.6-mckinley-smp_2.6.8-15_ia64.deb kernel-headers-2.6-mckinley_2.6.8-15_ia64.deb to pool/main/k/kernel-image-2.6.8-ia64/kernel-headers-2.6-mckinley_2.6.8-15_ia64.deb kernel-headers-2.6.8-4-itanium-smp_2.6.8-15_ia64.deb to pool/main/k/kernel-image-2.6.8-ia64/kernel-headers-2.6.8-4-itanium-smp_2.6.8-15_ia64.deb kernel-headers-2.6.8-4-itanium_2.6.8-15_ia64.deb to pool/main/k/kernel-image-2.6.8-ia64/kernel-headers-2.6.8-4-itanium_2.6.8-15_ia64.deb kernel-headers-2.6.8-4-mckinley-smp_2.6.8-15_ia64.deb to pool/main/k/kernel-image-2.6.8-ia64/kernel-headers-2.6.8-4-mckinley-smp_2.6.8-15_ia64.deb kernel-headers-2.6.8-4-mckinley_2.6.8-15_ia64.deb to pool/main/k/kernel-image-2.6.8-ia64/kernel-headers-2.6.8-4-mckinley_2.6.8-15_ia64.deb kernel-headers-2.6.8-4_2.6.8-15_ia64.deb to pool/main/k/kernel-image-2.6.8-ia64/kernel-headers-2.6.8-4_2.6.8-15_ia64.deb kernel-image-2.6-itanium-smp_2.6.8-15_ia64.deb to pool/main/k/kernel-image-2.6.8-ia64/kernel-image-2.6-itanium-smp_2.6.8-15_ia64.deb kernel-image-2.6-itanium_2.6.8-15_ia64.deb to pool/main/k/kernel-image-2.6.8-ia64/kernel-image-2.6-itanium_2.6.8-15_ia64.deb kernel-image-2.6-mckinley-smp_2.6.8-15_ia64.deb to pool/main/k/kernel-image-2.6.8-ia64/kernel-image-2.6-mckinley-smp_2.6.8-15_ia64.deb kernel-image-2.6-mckinley_2.6.8-15_ia64.deb to pool/main/k/kernel-image-2.6.8-ia64/kernel-image-2.6-mckinley_2.6.8-15_ia64.deb kernel-image-2.6.8-4-itanium-smp_2.6.8-15_ia64.deb to pool/main/k/kernel-image-2.6.8-ia64/kernel-image-2.6.8-4-itanium-smp_2.6.8-15_ia64.deb kernel-image-2.6.8-4-itanium_2.6.8-15_ia64.deb to pool/main/k/kernel-image-2.6.8-ia64/kernel-image-2.6.8-4-itanium_2.6.8-15_ia64.deb kernel-image-2.6.8-4-mckinley-smp_2.6.8-15_ia64.deb to pool/main/k/kernel-image-2.6.8-ia64/kernel-image-2.6.8-4-mckinley-smp_2.6.8-15_ia64.deb kernel-image-2.6.8-4-mckinley_2.6.8-15_ia64.deb to pool/main/k/kernel-image-2.6.8-ia64/kernel-image-2.6.8-4-mckinley_2.6.8-15_ia64.deb kernel-image-2.6.8-ia64_2.6.8-15.dsc to pool/main/k/kernel-image-2.6.8-ia64/kernel-image-2.6.8-ia64_2.6.8-15.dsc kernel-image-2.6.8-ia64_2.6.8-15.tar.gz to pool/main/k/kernel-image-2.6.8-ia64/kernel-image-2.6.8-ia64_2.6.8-15.tar.gz A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. dann frazier [EMAIL PROTECTED] (supplier of updated kernel-image-2.6.8-ia64 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 26 May 2007 04:04:02 -0600 Source: kernel-image-2.6.8-ia64 Binary: kernel-headers-2.6-itanium kernel-image-2.6.8-4-mckinley kernel-headers-2.6-mckinley-smp
Bug#336153: marked as done (kernel-image-2.6.8-2-386: Filesystem errors while writing to DM disk)
Your message dated Mon, 28 May 2007 23:06:13 + with message-id [EMAIL PROTECTED] and subject line Bug#336153: fixed in kernel-image-2.6.8-hppa 2.6.8-7 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: kernel-image-2.6.8-2-386 Severity: critical Justification: causes serious data loss Szenario: While copying some GBs to the filesystem under heavy load the filesystem gets corrupted. The SMART Status of all disks is passed, they are all new. The hardware components of the server should work fine too, used this server (cpu, motherboard, etc) before, just exchanged the harddisks. Error Message: Oct 27 23:36:34 localhost kernel: init_special_inode: bogus i_mode (4152) Oct 27 23:36:34 localhost kernel: init_special_inode: bogus i_mode (117230) Oct 27 23:36:45 localhost kernel: attempt to access beyond end of device Oct 27 23:36:45 localhost kernel: dm-0: rw=0, want=20177444552, limit=962598144 (last 2 lines repeating nonstop) Versions: - Unmodified Debian Sarge Kernel 2.6.8-2-386 - Debian Sarge utils last updated 27.10.05 Filesystem Layout: - ext2 (was ext3, but removed the journal with tune2fs) on top of - dmcrypt (aes-plain) /dev/mapper/croot on top of - RAID5 /dev/md2 on top of - 4x 160GB IDE /dev/hd[abcd]3 blacksheep:~# fdisk -l /dev/hd[abcd] Disk /dev/hda: 164.6 GB, 16469620 bytes 255 heads, 63 sectors/track, 20023 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/hda1 * 1 13 104391 fd Linux raid autodetect /dev/hda2 14 50 297202+ fd Linux raid autodetect /dev/hda3 51 20023 160433122+ fd Linux raid autodetect Disk /dev/hdb: 164.6 GB, 16469620 bytes 255 heads, 63 sectors/track, 20023 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/hdb1 * 1 13 104391 fd Linux raid autodetect /dev/hdb2 14 50 297202+ fd Linux raid autodetect /dev/hdb3 51 20023 160433122+ fd Linux raid autodetect Disk /dev/hdc: 164.6 GB, 16469620 bytes 255 heads, 63 sectors/track, 20023 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/hdc1 * 1 13 104391 fd Linux raid autodetect /dev/hdc2 14 50 297202+ fd Linux raid autodetect /dev/hdc3 51 20023 160433122+ fd Linux raid autodetect Disk /dev/hdd: 164.6 GB, 16469620 bytes 255 heads, 63 sectors/track, 20023 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/hdd1 * 1 13 104391 fd Linux raid autodetect /dev/hdd2 14 50 297202+ fd Linux raid autodetect /dev/hdd3 51 20023 160433122+ fd Linux raid autodetect blacksheep:~# cat /proc/mdstat Personalities : [raid1] [raid5] md0 : active raid1 hdd1[3] hda1[0] hdc1[2] hdb1[1] 104320 blocks [4/4] [] md1 : active raid5 hdd2[3] hda2[0] hdc2[2] hdb2[1] 891264 blocks level 5, 64k chunk, algorithm 2 [4/4] [] md2 : active raid5 hdd3[4] hda3[0] hdc3[2] hdb3[1] 481299072 blocks level 5, 64k chunk, algorithm 2 [4/3] [UUU_] [] recovery = 20.6% (33203840/160433024) finish=339.4min speed=6246K/sec unused devices: none blacksheep:~# dmsetup info croot Name: croot State: ACTIVE Tables present:LIVE Open count:1 Event number: 0 Major, minor: 254, 0 Number of targets: 1 blacksheep:~# dmsetup status croot 0 962598144 crypt blacksheep:~# dmsetup table croot 0 962598144 crypt aes-plain perhapsthatsmysecretkeyidontknow 0 9:2 0 blacksheep:~# cat /etc/crypttab # target device source device key file options cswap /dev/md1/dev/random swap croot /dev/md2nonecipher=aes-plain blacksheep:~# cat /etc/fstab # /etc/fstab: static file system information. # # file system mount point type options dump pass proc/proc procdefaults0 0 /dev/mapper/cswap none swapsw 0 0 /dev/mapper/croot /
Bug#372621: marked as done (old bug in ipt_ULOG (error during NLMSG_PUT))
Your message dated Mon, 28 May 2007 23:06:34 + with message-id [EMAIL PROTECTED] and subject line Bug#372621: fixed in kernel-patch-powerpc-2.6.8 2.6.8-13 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: kernel-source-2.6.8 Version: 2.6.8-16sarge2 When I used fprobe-ulog kernel printed sometimes: ipt_ULOG: error during NLMSG_PUT I google'd that this problem (actually bug) was solved in 2.6.10 by Harald Welte [EMAIL PROTECTED]. See: http://oss.sgi.com/archives/netdev/2004-10/msg01026.html (there is a small patch) http://www.kernel.org/pub/linux/kernel/v2.6/ChangeLog-2.6.10 It seems both 2.6 and 2.4 debian kernels affected. I use Debian GNU/Linux 3.1r2 (with last updates), kernel 2.6.8-2-686-smp. ---End Message--- ---BeginMessage--- Source: kernel-patch-powerpc-2.6.8 Source-Version: 2.6.8-13 We believe that the bug you reported is fixed in the latest version of kernel-patch-powerpc-2.6.8, which is due to be installed in the Debian FTP archive: kernel-build-2.6.8-4-power3-smp_2.6.8-13_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-build-2.6.8-4-power3-smp_2.6.8-13_powerpc.deb kernel-build-2.6.8-4-power3_2.6.8-13_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-build-2.6.8-4-power3_2.6.8-13_powerpc.deb kernel-build-2.6.8-4-power4-smp_2.6.8-13_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-build-2.6.8-4-power4-smp_2.6.8-13_powerpc.deb kernel-build-2.6.8-4-power4_2.6.8-13_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-build-2.6.8-4-power4_2.6.8-13_powerpc.deb kernel-build-2.6.8-4-powerpc-smp_2.6.8-13_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-build-2.6.8-4-powerpc-smp_2.6.8-13_powerpc.deb kernel-build-2.6.8-4-powerpc_2.6.8-13_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-build-2.6.8-4-powerpc_2.6.8-13_powerpc.deb kernel-headers-2.6.8-4_2.6.8-13_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-headers-2.6.8-4_2.6.8-13_powerpc.deb kernel-image-2.6.8-4-power3-smp_2.6.8-13_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-image-2.6.8-4-power3-smp_2.6.8-13_powerpc.deb kernel-image-2.6.8-4-power3_2.6.8-13_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-image-2.6.8-4-power3_2.6.8-13_powerpc.deb kernel-image-2.6.8-4-power4-smp_2.6.8-13_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-image-2.6.8-4-power4-smp_2.6.8-13_powerpc.deb kernel-image-2.6.8-4-power4_2.6.8-13_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-image-2.6.8-4-power4_2.6.8-13_powerpc.deb kernel-image-2.6.8-4-powerpc-smp_2.6.8-13_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-image-2.6.8-4-powerpc-smp_2.6.8-13_powerpc.deb kernel-image-2.6.8-4-powerpc_2.6.8-13_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-image-2.6.8-4-powerpc_2.6.8-13_powerpc.deb kernel-patch-powerpc-2.6.8_2.6.8-13.dsc to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-patch-powerpc-2.6.8_2.6.8-13.dsc kernel-patch-powerpc-2.6.8_2.6.8-13.tar.gz to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-patch-powerpc-2.6.8_2.6.8-13.tar.gz A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. dann frazier [EMAIL PROTECTED] (supplier of updated kernel-patch-powerpc-2.6.8 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 26 May 2007 04:08:06 -0600 Source: kernel-patch-powerpc-2.6.8 Binary: kernel-image-2.6.8-4-power4 kernel-build-2.6.8-4-power3-smp kernel-build-2.6.8-4-power4-smp kernel-build-2.6.8-4-powerpc-smp kernel-build-2.6.8-4-power3 kernel-image-2.6.8-4-power4-smp kernel-image-2.6.8-4-powerpc kernel-image-2.6.8-4-powerpc-smp kernel-build-2.6.8-4-power4 kernel-image-2.6.8-4-power3 kernel-headers-2.6.8-4 kernel-build-2.6.8-4-powerpc kernel-image-2.6.8-4-power3-smp Architecture: source powerpc Version: 2.6.8-13 Distribution: oldstable Urgency: high Maintainer: Debian Kernel Team debian-kernel@lists.debian.org Changed-By: dann frazier [EMAIL PROTECTED] Description: kernel-build-2.6.8-4-power3 - build
Bug#349774: marked as done ([Fwd: Re: stable kernel 2.6.8-2-686])
Your message dated Mon, 28 May 2007 23:06:26 + with message-id [EMAIL PROTECTED] and subject line Bug#349774: fixed in kernel-image-2.6.8-ia64 2.6.8-15 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: kernel-source-2.6.8 Version: 2.6.8-16sarge1 I'll file a bug for this usertag it dkt-pending-sarge-update. -- dann frazier [EMAIL PROTECTED] ---BeginMessage--- On Tue, 2006-01-17 at 16:23 -0700, dann frazier wrote: On Mon, 2006-01-16 at 23:07 +, Stuart T. R. Rowan wrote: Hi, The 3c59x kernel module doesn't work with vlan (802.1q) tagged packets. Apparently the fix was committed somewhere around 2.6.10, anyway we've upgraded our stable box to vanilla kernel 2.6.15.1 to work around this issue -- no discarded packets at all now. If there's gonna be an update to the stable kernel, a patch to make the 3c59x module work with vlans rather than silently failing might be a plan. hey Stu, got a link to the appropriate changeset(s)? Hey Dann, Yes! So the vlan patch turned up in patch-2.6.9.bz2. The changeset is on http://www.kernel.org/git/?p=linux/kernel/git/torvalds/old-2.6-bkcvs.git 3c59x.c has a history list here in case this builds on other non 2.6.8 patches: http://tinyurl.com/b8a95 On this you will clearly see the below commit listed: Title: [PATCH] VLAN support for 3c59x/3c90x commit 03e4b71f751da25d7b2d026ba6f4f904116e51e5 Body: This adds VLAN support to the 3c59x/90x series hardware. Stefan de Konink ported this code from the 2.4 VLAN patches and tested it extensively. I cleaned up the ifdefs and fixed a problem with bracketing that made older cards fail. I hope that helps? Thanks, Stu. (please keep me CC'd) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] ---End Message--- ---End Message--- ---BeginMessage--- Source: kernel-image-2.6.8-ia64 Source-Version: 2.6.8-15 We believe that the bug you reported is fixed in the latest version of kernel-image-2.6.8-ia64, which is due to be installed in the Debian FTP archive: kernel-headers-2.6-itanium-smp_2.6.8-15_ia64.deb to pool/main/k/kernel-image-2.6.8-ia64/kernel-headers-2.6-itanium-smp_2.6.8-15_ia64.deb kernel-headers-2.6-itanium_2.6.8-15_ia64.deb to pool/main/k/kernel-image-2.6.8-ia64/kernel-headers-2.6-itanium_2.6.8-15_ia64.deb kernel-headers-2.6-mckinley-smp_2.6.8-15_ia64.deb to pool/main/k/kernel-image-2.6.8-ia64/kernel-headers-2.6-mckinley-smp_2.6.8-15_ia64.deb kernel-headers-2.6-mckinley_2.6.8-15_ia64.deb to pool/main/k/kernel-image-2.6.8-ia64/kernel-headers-2.6-mckinley_2.6.8-15_ia64.deb kernel-headers-2.6.8-4-itanium-smp_2.6.8-15_ia64.deb to pool/main/k/kernel-image-2.6.8-ia64/kernel-headers-2.6.8-4-itanium-smp_2.6.8-15_ia64.deb kernel-headers-2.6.8-4-itanium_2.6.8-15_ia64.deb to pool/main/k/kernel-image-2.6.8-ia64/kernel-headers-2.6.8-4-itanium_2.6.8-15_ia64.deb kernel-headers-2.6.8-4-mckinley-smp_2.6.8-15_ia64.deb to pool/main/k/kernel-image-2.6.8-ia64/kernel-headers-2.6.8-4-mckinley-smp_2.6.8-15_ia64.deb kernel-headers-2.6.8-4-mckinley_2.6.8-15_ia64.deb to pool/main/k/kernel-image-2.6.8-ia64/kernel-headers-2.6.8-4-mckinley_2.6.8-15_ia64.deb kernel-headers-2.6.8-4_2.6.8-15_ia64.deb to pool/main/k/kernel-image-2.6.8-ia64/kernel-headers-2.6.8-4_2.6.8-15_ia64.deb kernel-image-2.6-itanium-smp_2.6.8-15_ia64.deb to pool/main/k/kernel-image-2.6.8-ia64/kernel-image-2.6-itanium-smp_2.6.8-15_ia64.deb kernel-image-2.6-itanium_2.6.8-15_ia64.deb to pool/main/k/kernel-image-2.6.8-ia64/kernel-image-2.6-itanium_2.6.8-15_ia64.deb kernel-image-2.6-mckinley-smp_2.6.8-15_ia64.deb to pool/main/k/kernel-image-2.6.8-ia64/kernel-image-2.6-mckinley-smp_2.6.8-15_ia64.deb kernel-image-2.6-mckinley_2.6.8-15_ia64.deb to pool/main/k/kernel-image-2.6.8-ia64/kernel-image-2.6-mckinley_2.6.8-15_ia64.deb kernel-image-2.6.8-4-itanium-smp_2.6.8-15_ia64.deb to pool/main/k/kernel-image-2.6.8-ia64/kernel-image-2.6.8-4-itanium-smp_2.6.8-15_ia64.deb kernel-image-2.6.8-4-itanium_2.6.8-15_ia64.deb to pool/main/k/kernel-image-2.6.8-ia64/kernel-image-2.6.8-4-itanium_2.6.8-15_ia64.deb kernel-image-2.6.8-4-mckinley-smp_2.6.8-15_ia64.deb to pool/main/k/kernel-image-2.6.8-ia64/kernel-image-2.6.8-4-mckinley-smp_2.6.8-15_ia64.deb kernel-image-2.6.8-4-mckinley_2.6.8-15_ia64.deb to pool/main/k/kernel-image-2.6.8-ia64/kernel-image-2.6.8-4-mckinley_2.6.8-15_ia64.deb kernel-image-2.6.8-ia64_2.6.8-15.dsc to
Bug#336153: marked as done (kernel-image-2.6.8-2-386: Filesystem errors while writing to DM disk)
Your message dated Mon, 28 May 2007 23:06:28 + with message-id [EMAIL PROTECTED] and subject line Bug#336153: fixed in kernel-image-2.6.8-s390 2.6.8-6 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: kernel-image-2.6.8-2-386 Severity: critical Justification: causes serious data loss Szenario: While copying some GBs to the filesystem under heavy load the filesystem gets corrupted. The SMART Status of all disks is passed, they are all new. The hardware components of the server should work fine too, used this server (cpu, motherboard, etc) before, just exchanged the harddisks. Error Message: Oct 27 23:36:34 localhost kernel: init_special_inode: bogus i_mode (4152) Oct 27 23:36:34 localhost kernel: init_special_inode: bogus i_mode (117230) Oct 27 23:36:45 localhost kernel: attempt to access beyond end of device Oct 27 23:36:45 localhost kernel: dm-0: rw=0, want=20177444552, limit=962598144 (last 2 lines repeating nonstop) Versions: - Unmodified Debian Sarge Kernel 2.6.8-2-386 - Debian Sarge utils last updated 27.10.05 Filesystem Layout: - ext2 (was ext3, but removed the journal with tune2fs) on top of - dmcrypt (aes-plain) /dev/mapper/croot on top of - RAID5 /dev/md2 on top of - 4x 160GB IDE /dev/hd[abcd]3 blacksheep:~# fdisk -l /dev/hd[abcd] Disk /dev/hda: 164.6 GB, 16469620 bytes 255 heads, 63 sectors/track, 20023 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/hda1 * 1 13 104391 fd Linux raid autodetect /dev/hda2 14 50 297202+ fd Linux raid autodetect /dev/hda3 51 20023 160433122+ fd Linux raid autodetect Disk /dev/hdb: 164.6 GB, 16469620 bytes 255 heads, 63 sectors/track, 20023 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/hdb1 * 1 13 104391 fd Linux raid autodetect /dev/hdb2 14 50 297202+ fd Linux raid autodetect /dev/hdb3 51 20023 160433122+ fd Linux raid autodetect Disk /dev/hdc: 164.6 GB, 16469620 bytes 255 heads, 63 sectors/track, 20023 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/hdc1 * 1 13 104391 fd Linux raid autodetect /dev/hdc2 14 50 297202+ fd Linux raid autodetect /dev/hdc3 51 20023 160433122+ fd Linux raid autodetect Disk /dev/hdd: 164.6 GB, 16469620 bytes 255 heads, 63 sectors/track, 20023 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/hdd1 * 1 13 104391 fd Linux raid autodetect /dev/hdd2 14 50 297202+ fd Linux raid autodetect /dev/hdd3 51 20023 160433122+ fd Linux raid autodetect blacksheep:~# cat /proc/mdstat Personalities : [raid1] [raid5] md0 : active raid1 hdd1[3] hda1[0] hdc1[2] hdb1[1] 104320 blocks [4/4] [] md1 : active raid5 hdd2[3] hda2[0] hdc2[2] hdb2[1] 891264 blocks level 5, 64k chunk, algorithm 2 [4/4] [] md2 : active raid5 hdd3[4] hda3[0] hdc3[2] hdb3[1] 481299072 blocks level 5, 64k chunk, algorithm 2 [4/3] [UUU_] [] recovery = 20.6% (33203840/160433024) finish=339.4min speed=6246K/sec unused devices: none blacksheep:~# dmsetup info croot Name: croot State: ACTIVE Tables present:LIVE Open count:1 Event number: 0 Major, minor: 254, 0 Number of targets: 1 blacksheep:~# dmsetup status croot 0 962598144 crypt blacksheep:~# dmsetup table croot 0 962598144 crypt aes-plain perhapsthatsmysecretkeyidontknow 0 9:2 0 blacksheep:~# cat /etc/crypttab # target device source device key file options cswap /dev/md1/dev/random swap croot /dev/md2nonecipher=aes-plain blacksheep:~# cat /etc/fstab # /etc/fstab: static file system information. # # file system mount point type options dump pass proc/proc procdefaults0 0 /dev/mapper/cswap none swapsw 0 0 /dev/mapper/croot /
Bug#354493: marked as done (kernel-source-2.6.8: can't install grub on cciss device)
Your message dated Mon, 28 May 2007 23:06:30 +
with message-id [EMAIL PROTECTED]
and subject line Bug#354493: fixed in kernel-image-2.6.8-sparc 2.6.8-16
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
---BeginMessage---
Package: kernel-source-2.6.8
Version: 2.6.8-16sarge2
Severity: normal
Tags: patch
In kernel.org 2.6.8, the block layer (drivers/block/ioctl.c) has:
case BLKFLSBUF:
if (!capable(CAP_SYS_ADMIN))
return -EACCES;
if (disk-fops-ioctl) {
ret = disk-fops-ioctl(inode, file, cmd, arg);
if (ret != -EINVAL)
return ret;
}
fsync_bdev(bdev);
invalidate_bdev(bdev, 0);
return 0;
So, fsync_bdev()/invalidate_bdev() are only called if ret == -EINVAL.
In pristine 2.6.8, cciss returned -EBADRQC, so these functions were never
called.
In 2.6.9, the block layer was modified to also accept -ENOTTY:
http://www.kernel.org/git/?p=linux/kernel/git/torvalds/old-2.6-bkcvs.git;a=commitdiff;h=b295216702a8fb86ef8e3951df9d7118746e35c7
So, in 2.6.10-rc4, the only fix needed was to make cciss return -ENOTTY, which
is what Mike submitted.
http://www.kernel.org/git/?p=linux/kernel/git/torvalds/old-2.6-bkcvs.git;a=commitdiff;h=d28d721eb3f7df904fb1533d314879da33f9b50a
Since 2.6.8 didn't accept -ENOTTY, simply backporting this fix wasn't enough to
fix the bug in 2.6.8, we also need the block layer changeset.
-- System Information:
Debian Release: 3.1
Architecture: ia64
Kernel: Linux 2.6.8-2-mckinley-smp
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages kernel-source-2.6.8 depends on:
ii binutils 2.15-6 The GNU assembler, linker and bina
ii bzip2 1.0.2-7high-quality block-sorting file co
ii coreutils [fileutils] 5.2.1-2The GNU core utilities
-- no debconf information
---End Message---
---BeginMessage---
Source: kernel-image-2.6.8-sparc
Source-Version: 2.6.8-16
We believe that the bug you reported is fixed in the latest version of
kernel-image-2.6.8-sparc, which is due to be installed in the Debian FTP
archive:
kernel-build-2.6.8-4_2.6.8-16_sparc.deb
to
pool/main/k/kernel-image-2.6.8-sparc/kernel-build-2.6.8-4_2.6.8-16_sparc.deb
kernel-headers-2.6.8-4-sparc32_2.6.8-16_sparc.deb
to
pool/main/k/kernel-image-2.6.8-sparc/kernel-headers-2.6.8-4-sparc32_2.6.8-16_sparc.deb
kernel-headers-2.6.8-4-sparc64-smp_2.6.8-16_sparc.deb
to
pool/main/k/kernel-image-2.6.8-sparc/kernel-headers-2.6.8-4-sparc64-smp_2.6.8-16_sparc.deb
kernel-headers-2.6.8-4-sparc64_2.6.8-16_sparc.deb
to
pool/main/k/kernel-image-2.6.8-sparc/kernel-headers-2.6.8-4-sparc64_2.6.8-16_sparc.deb
kernel-headers-2.6.8-4_2.6.8-16_sparc.deb
to
pool/main/k/kernel-image-2.6.8-sparc/kernel-headers-2.6.8-4_2.6.8-16_sparc.deb
kernel-image-2.6.8-4-sparc32_2.6.8-16_sparc.deb
to
pool/main/k/kernel-image-2.6.8-sparc/kernel-image-2.6.8-4-sparc32_2.6.8-16_sparc.deb
kernel-image-2.6.8-4-sparc64-smp_2.6.8-16_sparc.deb
to
pool/main/k/kernel-image-2.6.8-sparc/kernel-image-2.6.8-4-sparc64-smp_2.6.8-16_sparc.deb
kernel-image-2.6.8-4-sparc64_2.6.8-16_sparc.deb
to
pool/main/k/kernel-image-2.6.8-sparc/kernel-image-2.6.8-4-sparc64_2.6.8-16_sparc.deb
kernel-image-2.6.8-sparc_2.6.8-16.dsc
to pool/main/k/kernel-image-2.6.8-sparc/kernel-image-2.6.8-sparc_2.6.8-16.dsc
kernel-image-2.6.8-sparc_2.6.8-16.tar.gz
to
pool/main/k/kernel-image-2.6.8-sparc/kernel-image-2.6.8-sparc_2.6.8-16.tar.gz
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
dann frazier [EMAIL PROTECTED] (supplier of updated kernel-image-2.6.8-sparc
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Sat, 26 May 2007 04:09:38 -0600
Source: kernel-image-2.6.8-sparc
Binary: kernel-headers-2.6.8-4-sparc32 kernel-image-2.6.8-4-sparc64-smp
kernel-headers-2.6.8-4-sparc64 kernel-image-2.6.8-4-sparc32
kernel-build-2.6.8-4 kernel-headers-2.6.8-4 kernel-image-2.6.8-4-sparc64
Bug#372621: marked as done (old bug in ipt_ULOG (error during NLMSG_PUT))
Your message dated Mon, 28 May 2007 23:06:22 + with message-id [EMAIL PROTECTED] and subject line Bug#372621: fixed in kernel-image-2.6.8-i386 2.6.8-17 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: kernel-source-2.6.8 Version: 2.6.8-16sarge2 When I used fprobe-ulog kernel printed sometimes: ipt_ULOG: error during NLMSG_PUT I google'd that this problem (actually bug) was solved in 2.6.10 by Harald Welte [EMAIL PROTECTED]. See: http://oss.sgi.com/archives/netdev/2004-10/msg01026.html (there is a small patch) http://www.kernel.org/pub/linux/kernel/v2.6/ChangeLog-2.6.10 It seems both 2.6 and 2.4 debian kernels affected. I use Debian GNU/Linux 3.1r2 (with last updates), kernel 2.6.8-2-686-smp. ---End Message--- ---BeginMessage--- Source: kernel-image-2.6.8-i386 Source-Version: 2.6.8-17 We believe that the bug you reported is fixed in the latest version of kernel-image-2.6.8-i386, which is due to be installed in the Debian FTP archive: kernel-headers-2.6.8-4-386_2.6.8-17_i386.deb to pool/main/k/kernel-image-2.6.8-i386/kernel-headers-2.6.8-4-386_2.6.8-17_i386.deb kernel-headers-2.6.8-4-686-smp_2.6.8-17_i386.deb to pool/main/k/kernel-image-2.6.8-i386/kernel-headers-2.6.8-4-686-smp_2.6.8-17_i386.deb kernel-headers-2.6.8-4-686_2.6.8-17_i386.deb to pool/main/k/kernel-image-2.6.8-i386/kernel-headers-2.6.8-4-686_2.6.8-17_i386.deb kernel-headers-2.6.8-4-k7-smp_2.6.8-17_i386.deb to pool/main/k/kernel-image-2.6.8-i386/kernel-headers-2.6.8-4-k7-smp_2.6.8-17_i386.deb kernel-headers-2.6.8-4-k7_2.6.8-17_i386.deb to pool/main/k/kernel-image-2.6.8-i386/kernel-headers-2.6.8-4-k7_2.6.8-17_i386.deb kernel-headers-2.6.8-4_2.6.8-17_i386.deb to pool/main/k/kernel-image-2.6.8-i386/kernel-headers-2.6.8-4_2.6.8-17_i386.deb kernel-image-2.6.8-4-386_2.6.8-17_i386.deb to pool/main/k/kernel-image-2.6.8-i386/kernel-image-2.6.8-4-386_2.6.8-17_i386.deb kernel-image-2.6.8-4-686-smp_2.6.8-17_i386.deb to pool/main/k/kernel-image-2.6.8-i386/kernel-image-2.6.8-4-686-smp_2.6.8-17_i386.deb kernel-image-2.6.8-4-686_2.6.8-17_i386.deb to pool/main/k/kernel-image-2.6.8-i386/kernel-image-2.6.8-4-686_2.6.8-17_i386.deb kernel-image-2.6.8-4-k7-smp_2.6.8-17_i386.deb to pool/main/k/kernel-image-2.6.8-i386/kernel-image-2.6.8-4-k7-smp_2.6.8-17_i386.deb kernel-image-2.6.8-4-k7_2.6.8-17_i386.deb to pool/main/k/kernel-image-2.6.8-i386/kernel-image-2.6.8-4-k7_2.6.8-17_i386.deb kernel-image-2.6.8-i386_2.6.8-17.dsc to pool/main/k/kernel-image-2.6.8-i386/kernel-image-2.6.8-i386_2.6.8-17.dsc kernel-image-2.6.8-i386_2.6.8-17.tar.gz to pool/main/k/kernel-image-2.6.8-i386/kernel-image-2.6.8-i386_2.6.8-17.tar.gz A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. dann frazier [EMAIL PROTECTED] (supplier of updated kernel-image-2.6.8-i386 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 26 May 2007 03:59:02 -0600 Source: kernel-image-2.6.8-i386 Binary: kernel-headers-2.6.8-4-686-smp kernel-headers-2.6.8-4-686 kernel-headers-2.6.8-4-386 kernel-image-2.6.8-4-386 kernel-image-2.6.8-4-k7 kernel-image-2.6.8-4-686-smp kernel-headers-2.6.8-4 kernel-image-2.6.8-4-686 kernel-headers-2.6.8-4-k7-smp kernel-image-2.6.8-4-k7-smp kernel-headers-2.6.8-4-k7 Architecture: source i386 Version: 2.6.8-17 Distribution: oldstable Urgency: high Maintainer: Debian kernel team debian-kernel@lists.debian.org Changed-By: dann frazier [EMAIL PROTECTED] Description: kernel-headers-2.6.8-4 - Header files related to Linux kernel version 2.6.8 kernel-headers-2.6.8-4-386 - Linux kernel headers 2.6.8 on 386 kernel-headers-2.6.8-4-686 - Linux kernel headers 2.6.8 on PPro/Celeron/PII/PIII/P4 kernel-headers-2.6.8-4-686-smp - Linux kernel headers 2.6.8 on PPro/Celeron/PII/PIII/P4 SMP kernel-headers-2.6.8-4-k7 - Linux kernel headers 2.6.8 on AMD K7 kernel-headers-2.6.8-4-k7-smp - Linux kernel headers 2.6.8 on AMD K7 SMP kernel-image-2.6.8-4-386 - Linux kernel image for version 2.6.8 on 386. kernel-image-2.6.8-4-686 - Linux kernel image for version 2.6.8 on PPro/Celeron/PII/PIII/P4.
Bug#321442: marked as done (kernel-source-2.6.8: fails to compile on powerpc (drivers/ide/ppc/pmac.c))
Your message dated Mon, 28 May 2007 23:06:28 + with message-id [EMAIL PROTECTED] and subject line Bug#321442: fixed in kernel-image-2.6.8-s390 2.6.8-6 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: kernel-source-2.6.8 Version: 2.6.8-16 Severity: normal The kernel-source-2.6.8 sources fail to compile on powerpc (PowerMac 4400). ___ CC drivers/ide/ide.o CC drivers/ide/ide-default.o CC drivers/ide/ide-io.o CC drivers/ide/ide-iops.o CC drivers/ide/ide-lib.o CC drivers/ide/ide-probe.o CC drivers/ide/ide-taskfile.o CC drivers/ide/ide-dma.o CC drivers/ide/ide-proc.o CC drivers/ide/ppc/pmac.o drivers/ide/ppc/pmac.c: Dans la fonction « pmac_ide_dma_read »: drivers/ide/ppc/pmac.c:1951: error: `ide_dma_intr' undeclared (first use in this function) drivers/ide/ppc/pmac.c:1951: error: (Each undeclared identifier is reported only once drivers/ide/ppc/pmac.c:1951: error: for each function it appears in.) drivers/ide/ppc/pmac.c: Dans la fonction « pmac_ide_dma_write »: drivers/ide/ppc/pmac.c:1982: error: `ide_dma_intr' undeclared (first use in this function) drivers/ide/ppc/pmac.c: Dans la fonction « pmac_ide_setup_dma »: drivers/ide/ppc/pmac.c:2157: error: `__ide_dma_off_quietly' undeclared (first use in this function) drivers/ide/ppc/pmac.c:2158: error: `__ide_dma_on' undeclared (first use in this function) drivers/ide/ppc/pmac.c:2167: error: `__ide_dma_verbose' undeclared (first use in this function) drivers/ide/ppc/pmac.c:2168: error: `__ide_dma_timeout' undeclared (first use in this function) make[3]: *** [drivers/ide/ppc/pmac.o] Error 1 make[2]: *** [drivers/ide] Error 2 make[1]: *** [drivers] Error 2 ___ -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: powerpc (ppc) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.4.26-ltp Locale: LANG=fr_FR, LC_CTYPE=fr_FR (charmap=UTF-8) (ignored: LC_ALL set to fr_FR.UTF-8) Versions of packages kernel-source-2.6.8 depends on: ii binutils 2.16.1-2 The GNU assembler, linker and bina ii bzip2 1.0.2-8high-quality block-sorting file co ii coreutils [fileutils] 5.2.1-2The GNU core utilities ii fileutils 5.2.1-2The GNU file management utilities Versions of packages kernel-source-2.6.8 recommends: ii gcc 4:3.3.5-3The GNU C compiler ii libc6-dev [libc-dev]2.3.2.ds1-22 GNU C Library: Development Librari ii make3.80-9 The GNU version of the make util -- no debconf information ---End Message--- ---BeginMessage--- Source: kernel-image-2.6.8-s390 Source-Version: 2.6.8-6 We believe that the bug you reported is fixed in the latest version of kernel-image-2.6.8-s390, which is due to be installed in the Debian FTP archive: kernel-headers-2.6.8-4_2.6.8-6_s390.deb to pool/main/k/kernel-image-2.6.8-s390/kernel-headers-2.6.8-4_2.6.8-6_s390.deb kernel-image-2.6.8-4-s390-tape_2.6.8-6_s390.deb to pool/main/k/kernel-image-2.6.8-s390/kernel-image-2.6.8-4-s390-tape_2.6.8-6_s390.deb kernel-image-2.6.8-4-s390_2.6.8-6_s390.deb to pool/main/k/kernel-image-2.6.8-s390/kernel-image-2.6.8-4-s390_2.6.8-6_s390.deb kernel-image-2.6.8-4-s390x_2.6.8-6_s390.deb to pool/main/k/kernel-image-2.6.8-s390/kernel-image-2.6.8-4-s390x_2.6.8-6_s390.deb kernel-image-2.6.8-s390_2.6.8-6.dsc to pool/main/k/kernel-image-2.6.8-s390/kernel-image-2.6.8-s390_2.6.8-6.dsc kernel-image-2.6.8-s390_2.6.8-6.tar.gz to pool/main/k/kernel-image-2.6.8-s390/kernel-image-2.6.8-s390_2.6.8-6.tar.gz kernel-patch-2.6.8-s390_2.6.8-6_all.deb to pool/main/k/kernel-image-2.6.8-s390/kernel-patch-2.6.8-s390_2.6.8-6_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. dann frazier [EMAIL PROTECTED] (supplier of updated kernel-image-2.6.8-s390 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 26 May 2007 03:23:35 -0600 Source:
Bug#321442: marked as done (kernel-source-2.6.8: fails to compile on powerpc (drivers/ide/ppc/pmac.c))
Your message dated Mon, 28 May 2007 23:06:34 + with message-id [EMAIL PROTECTED] and subject line Bug#321442: fixed in kernel-patch-powerpc-2.6.8 2.6.8-13 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: kernel-source-2.6.8 Version: 2.6.8-16 Severity: normal The kernel-source-2.6.8 sources fail to compile on powerpc (PowerMac 4400). ___ CC drivers/ide/ide.o CC drivers/ide/ide-default.o CC drivers/ide/ide-io.o CC drivers/ide/ide-iops.o CC drivers/ide/ide-lib.o CC drivers/ide/ide-probe.o CC drivers/ide/ide-taskfile.o CC drivers/ide/ide-dma.o CC drivers/ide/ide-proc.o CC drivers/ide/ppc/pmac.o drivers/ide/ppc/pmac.c: Dans la fonction « pmac_ide_dma_read »: drivers/ide/ppc/pmac.c:1951: error: `ide_dma_intr' undeclared (first use in this function) drivers/ide/ppc/pmac.c:1951: error: (Each undeclared identifier is reported only once drivers/ide/ppc/pmac.c:1951: error: for each function it appears in.) drivers/ide/ppc/pmac.c: Dans la fonction « pmac_ide_dma_write »: drivers/ide/ppc/pmac.c:1982: error: `ide_dma_intr' undeclared (first use in this function) drivers/ide/ppc/pmac.c: Dans la fonction « pmac_ide_setup_dma »: drivers/ide/ppc/pmac.c:2157: error: `__ide_dma_off_quietly' undeclared (first use in this function) drivers/ide/ppc/pmac.c:2158: error: `__ide_dma_on' undeclared (first use in this function) drivers/ide/ppc/pmac.c:2167: error: `__ide_dma_verbose' undeclared (first use in this function) drivers/ide/ppc/pmac.c:2168: error: `__ide_dma_timeout' undeclared (first use in this function) make[3]: *** [drivers/ide/ppc/pmac.o] Error 1 make[2]: *** [drivers/ide] Error 2 make[1]: *** [drivers] Error 2 ___ -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: powerpc (ppc) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.4.26-ltp Locale: LANG=fr_FR, LC_CTYPE=fr_FR (charmap=UTF-8) (ignored: LC_ALL set to fr_FR.UTF-8) Versions of packages kernel-source-2.6.8 depends on: ii binutils 2.16.1-2 The GNU assembler, linker and bina ii bzip2 1.0.2-8high-quality block-sorting file co ii coreutils [fileutils] 5.2.1-2The GNU core utilities ii fileutils 5.2.1-2The GNU file management utilities Versions of packages kernel-source-2.6.8 recommends: ii gcc 4:3.3.5-3The GNU C compiler ii libc6-dev [libc-dev]2.3.2.ds1-22 GNU C Library: Development Librari ii make3.80-9 The GNU version of the make util -- no debconf information ---End Message--- ---BeginMessage--- Source: kernel-patch-powerpc-2.6.8 Source-Version: 2.6.8-13 We believe that the bug you reported is fixed in the latest version of kernel-patch-powerpc-2.6.8, which is due to be installed in the Debian FTP archive: kernel-build-2.6.8-4-power3-smp_2.6.8-13_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-build-2.6.8-4-power3-smp_2.6.8-13_powerpc.deb kernel-build-2.6.8-4-power3_2.6.8-13_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-build-2.6.8-4-power3_2.6.8-13_powerpc.deb kernel-build-2.6.8-4-power4-smp_2.6.8-13_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-build-2.6.8-4-power4-smp_2.6.8-13_powerpc.deb kernel-build-2.6.8-4-power4_2.6.8-13_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-build-2.6.8-4-power4_2.6.8-13_powerpc.deb kernel-build-2.6.8-4-powerpc-smp_2.6.8-13_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-build-2.6.8-4-powerpc-smp_2.6.8-13_powerpc.deb kernel-build-2.6.8-4-powerpc_2.6.8-13_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-build-2.6.8-4-powerpc_2.6.8-13_powerpc.deb kernel-headers-2.6.8-4_2.6.8-13_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-headers-2.6.8-4_2.6.8-13_powerpc.deb kernel-image-2.6.8-4-power3-smp_2.6.8-13_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-image-2.6.8-4-power3-smp_2.6.8-13_powerpc.deb kernel-image-2.6.8-4-power3_2.6.8-13_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-image-2.6.8-4-power3_2.6.8-13_powerpc.deb kernel-image-2.6.8-4-power4-smp_2.6.8-13_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-image-2.6.8-4-power4-smp_2.6.8-13_powerpc.deb kernel-image-2.6.8-4-power4_2.6.8-13_powerpc.deb to
Bug#317286: marked as done (Please backport support for Promise SATAII TX2/TX4 cards (from 2.6.11))
Your message dated Mon, 28 May 2007 23:06:30 + with message-id [EMAIL PROTECTED] and subject line Bug#317286: fixed in kernel-image-2.6.8-sparc 2.6.8-16 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: kernel-source Version: 2.6.8-16 This version of the kernel does not support Promise SATAII TX2/TX4 cards. (Note SATAII, Not to be confused with regular Promise SATA TX2/4 cards). Support for these cards was added to kernel 2.6.11. From the Changelog (http://www.kernel.org/pub/linux/kernel/v2.6/ChangeLog-2.6.11): [EMAIL PROTECTED] [libata sata_promise] support Promise SATAII TX2/TX4 cards Originally from Peter Smith, with testing and additional contributions from Jens Axboe. I politely request that someone back port the Promise support to Debian's 2.6.8 kernel. Thank You ---End Message--- ---BeginMessage--- Source: kernel-image-2.6.8-sparc Source-Version: 2.6.8-16 We believe that the bug you reported is fixed in the latest version of kernel-image-2.6.8-sparc, which is due to be installed in the Debian FTP archive: kernel-build-2.6.8-4_2.6.8-16_sparc.deb to pool/main/k/kernel-image-2.6.8-sparc/kernel-build-2.6.8-4_2.6.8-16_sparc.deb kernel-headers-2.6.8-4-sparc32_2.6.8-16_sparc.deb to pool/main/k/kernel-image-2.6.8-sparc/kernel-headers-2.6.8-4-sparc32_2.6.8-16_sparc.deb kernel-headers-2.6.8-4-sparc64-smp_2.6.8-16_sparc.deb to pool/main/k/kernel-image-2.6.8-sparc/kernel-headers-2.6.8-4-sparc64-smp_2.6.8-16_sparc.deb kernel-headers-2.6.8-4-sparc64_2.6.8-16_sparc.deb to pool/main/k/kernel-image-2.6.8-sparc/kernel-headers-2.6.8-4-sparc64_2.6.8-16_sparc.deb kernel-headers-2.6.8-4_2.6.8-16_sparc.deb to pool/main/k/kernel-image-2.6.8-sparc/kernel-headers-2.6.8-4_2.6.8-16_sparc.deb kernel-image-2.6.8-4-sparc32_2.6.8-16_sparc.deb to pool/main/k/kernel-image-2.6.8-sparc/kernel-image-2.6.8-4-sparc32_2.6.8-16_sparc.deb kernel-image-2.6.8-4-sparc64-smp_2.6.8-16_sparc.deb to pool/main/k/kernel-image-2.6.8-sparc/kernel-image-2.6.8-4-sparc64-smp_2.6.8-16_sparc.deb kernel-image-2.6.8-4-sparc64_2.6.8-16_sparc.deb to pool/main/k/kernel-image-2.6.8-sparc/kernel-image-2.6.8-4-sparc64_2.6.8-16_sparc.deb kernel-image-2.6.8-sparc_2.6.8-16.dsc to pool/main/k/kernel-image-2.6.8-sparc/kernel-image-2.6.8-sparc_2.6.8-16.dsc kernel-image-2.6.8-sparc_2.6.8-16.tar.gz to pool/main/k/kernel-image-2.6.8-sparc/kernel-image-2.6.8-sparc_2.6.8-16.tar.gz A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. dann frazier [EMAIL PROTECTED] (supplier of updated kernel-image-2.6.8-sparc package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 26 May 2007 04:09:38 -0600 Source: kernel-image-2.6.8-sparc Binary: kernel-headers-2.6.8-4-sparc32 kernel-image-2.6.8-4-sparc64-smp kernel-headers-2.6.8-4-sparc64 kernel-image-2.6.8-4-sparc32 kernel-build-2.6.8-4 kernel-headers-2.6.8-4 kernel-image-2.6.8-4-sparc64 kernel-headers-2.6.8-4-sparc64-smp Architecture: source sparc Version: 2.6.8-16 Distribution: oldstable Urgency: high Maintainer: Debian Kernel Team debian-kernel@lists.debian.org Changed-By: dann frazier [EMAIL PROTECTED] Description: kernel-build-2.6.8-4 - Headers for building modules for Linux 2.6.8 kernel-headers-2.6.8-4 - Header files related to Linux kernel version 2.6.8 kernel-headers-2.6.8-4-sparc32 - Header files for Linux kernel 2.6.8 on uniprocessor 32-bit SPARC kernel-headers-2.6.8-4-sparc64 - Header files for Linux kernel 2.6.8 on uniprocessor 64-bit SPARC kernel-headers-2.6.8-4-sparc64-smp - Header files for Linux kernel 2.6.8 on multiprocessor 64-bit SPAR kernel-image-2.6.8-4-sparc32 - Linux kernel binary image for Super/HyperSPARC (sparc32) systems kernel-image-2.6.8-4-sparc64 - Linux kernel binary image for UltraSPARC (sparc64) systems kernel-image-2.6.8-4-sparc64-smp - Linux kernel binary image for SMP UltraSPARC (sparc64) systems Closes: 311357 317286 321442 323557 336153 349774 354493 372621 Changes: kernel-image-2.6.8-sparc (2.6.8-16) oldstable; urgency=high . * Rebuild
Bug#323557: marked as done (kernel: nfs server intermitently claims ENOENT on existing files or directories)
Your message dated Mon, 28 May 2007 23:06:09 + with message-id [EMAIL PROTECTED] and subject line Bug#323557: fixed in kernel-image-2.6.8-amd64 2.6.8-17 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: kernel Severity: important Tags: patch The problem reported in https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=150759 (which also has a working patch) exists in Debian kernels as well. In short, the NFS server sometimes reports ENOENT to nfs clients when under high load. This makes it hard to use Maildir over NFS with Debian server as NFS server. -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.6.8-2-386 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) ---End Message--- ---BeginMessage--- Source: kernel-image-2.6.8-amd64 Source-Version: 2.6.8-17 We believe that the bug you reported is fixed in the latest version of kernel-image-2.6.8-amd64, which is due to be installed in the Debian FTP archive: kernel-headers-2.6.8-13-amd64-generic_2.6.8-17_i386.deb to pool/main/k/kernel-image-2.6.8-amd64/kernel-headers-2.6.8-13-amd64-generic_2.6.8-17_i386.deb kernel-headers-2.6.8-13-amd64-k8-smp_2.6.8-17_i386.deb to pool/main/k/kernel-image-2.6.8-amd64/kernel-headers-2.6.8-13-amd64-k8-smp_2.6.8-17_i386.deb kernel-headers-2.6.8-13-amd64-k8_2.6.8-17_i386.deb to pool/main/k/kernel-image-2.6.8-amd64/kernel-headers-2.6.8-13-amd64-k8_2.6.8-17_i386.deb kernel-headers-2.6.8-13-em64t-p4-smp_2.6.8-17_i386.deb to pool/main/k/kernel-image-2.6.8-amd64/kernel-headers-2.6.8-13-em64t-p4-smp_2.6.8-17_i386.deb kernel-headers-2.6.8-13-em64t-p4_2.6.8-17_i386.deb to pool/main/k/kernel-image-2.6.8-amd64/kernel-headers-2.6.8-13-em64t-p4_2.6.8-17_i386.deb kernel-headers-2.6.8-13_2.6.8-17_i386.deb to pool/main/k/kernel-image-2.6.8-amd64/kernel-headers-2.6.8-13_2.6.8-17_i386.deb kernel-image-2.6.8-13-amd64-generic_2.6.8-17_i386.deb to pool/main/k/kernel-image-2.6.8-amd64/kernel-image-2.6.8-13-amd64-generic_2.6.8-17_i386.deb kernel-image-2.6.8-13-amd64-k8-smp_2.6.8-17_i386.deb to pool/main/k/kernel-image-2.6.8-amd64/kernel-image-2.6.8-13-amd64-k8-smp_2.6.8-17_i386.deb kernel-image-2.6.8-13-amd64-k8_2.6.8-17_i386.deb to pool/main/k/kernel-image-2.6.8-amd64/kernel-image-2.6.8-13-amd64-k8_2.6.8-17_i386.deb kernel-image-2.6.8-13-em64t-p4-smp_2.6.8-17_i386.deb to pool/main/k/kernel-image-2.6.8-amd64/kernel-image-2.6.8-13-em64t-p4-smp_2.6.8-17_i386.deb kernel-image-2.6.8-13-em64t-p4_2.6.8-17_i386.deb to pool/main/k/kernel-image-2.6.8-amd64/kernel-image-2.6.8-13-em64t-p4_2.6.8-17_i386.deb kernel-image-2.6.8-amd64_2.6.8-17.dsc to pool/main/k/kernel-image-2.6.8-amd64/kernel-image-2.6.8-amd64_2.6.8-17.dsc kernel-image-2.6.8-amd64_2.6.8-17.tar.gz to pool/main/k/kernel-image-2.6.8-amd64/kernel-image-2.6.8-amd64_2.6.8-17.tar.gz A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. dann frazier [EMAIL PROTECTED] (supplier of updated kernel-image-2.6.8-amd64 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 26 May 2007 03:56:58 -0600 Source: kernel-image-2.6.8-amd64 Binary: kernel-headers-2.6.8-13-amd64-k8 kernel-image-2.6.8-13-em64t-p4-smp kernel-image-2.6.8-13-amd64-k8-smp kernel-headers-2.6.8-13 kernel-headers-2.6.8-13-amd64-generic kernel-image-2.6.8-13-amd64-k8 kernel-headers-2.6.8-13-em64t-p4 kernel-headers-2.6.8-13-amd64-k8-smp kernel-headers-2.6.8-13-em64t-p4-smp kernel-image-2.6.8-13-amd64-generic kernel-image-2.6.8-13-em64t-p4 Architecture: source i386 Version: 2.6.8-17 Distribution: oldstable Urgency: high Maintainer: Debian Kernel Team debian-kernel@lists.debian.org Changed-By: dann frazier [EMAIL PROTECTED] Description: kernel-headers-2.6.8-13 - Header files related to Linux kernel version 2.6.8 kernel-headers-2.6.8-13-amd64-generic - Linux kernel headers 2.6.8 for generic x86_64 systems kernel-headers-2.6.8-13-amd64-k8 - Linux kernel headers for version 2.6.8 on AMD64 systems kernel-headers-2.6.8-13-amd64-k8-smp - Linux kernel headers for version 2.6.8 on AMD64 SMP systems
Bug#349774: marked as done ([Fwd: Re: stable kernel 2.6.8-2-686])
Your message dated Mon, 28 May 2007 23:06:34 + with message-id [EMAIL PROTECTED] and subject line Bug#349774: fixed in kernel-patch-powerpc-2.6.8 2.6.8-13 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: kernel-source-2.6.8 Version: 2.6.8-16sarge1 I'll file a bug for this usertag it dkt-pending-sarge-update. -- dann frazier [EMAIL PROTECTED] ---BeginMessage--- On Tue, 2006-01-17 at 16:23 -0700, dann frazier wrote: On Mon, 2006-01-16 at 23:07 +, Stuart T. R. Rowan wrote: Hi, The 3c59x kernel module doesn't work with vlan (802.1q) tagged packets. Apparently the fix was committed somewhere around 2.6.10, anyway we've upgraded our stable box to vanilla kernel 2.6.15.1 to work around this issue -- no discarded packets at all now. If there's gonna be an update to the stable kernel, a patch to make the 3c59x module work with vlans rather than silently failing might be a plan. hey Stu, got a link to the appropriate changeset(s)? Hey Dann, Yes! So the vlan patch turned up in patch-2.6.9.bz2. The changeset is on http://www.kernel.org/git/?p=linux/kernel/git/torvalds/old-2.6-bkcvs.git 3c59x.c has a history list here in case this builds on other non 2.6.8 patches: http://tinyurl.com/b8a95 On this you will clearly see the below commit listed: Title: [PATCH] VLAN support for 3c59x/3c90x commit 03e4b71f751da25d7b2d026ba6f4f904116e51e5 Body: This adds VLAN support to the 3c59x/90x series hardware. Stefan de Konink ported this code from the 2.4 VLAN patches and tested it extensively. I cleaned up the ifdefs and fixed a problem with bracketing that made older cards fail. I hope that helps? Thanks, Stu. (please keep me CC'd) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] ---End Message--- ---End Message--- ---BeginMessage--- Source: kernel-patch-powerpc-2.6.8 Source-Version: 2.6.8-13 We believe that the bug you reported is fixed in the latest version of kernel-patch-powerpc-2.6.8, which is due to be installed in the Debian FTP archive: kernel-build-2.6.8-4-power3-smp_2.6.8-13_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-build-2.6.8-4-power3-smp_2.6.8-13_powerpc.deb kernel-build-2.6.8-4-power3_2.6.8-13_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-build-2.6.8-4-power3_2.6.8-13_powerpc.deb kernel-build-2.6.8-4-power4-smp_2.6.8-13_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-build-2.6.8-4-power4-smp_2.6.8-13_powerpc.deb kernel-build-2.6.8-4-power4_2.6.8-13_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-build-2.6.8-4-power4_2.6.8-13_powerpc.deb kernel-build-2.6.8-4-powerpc-smp_2.6.8-13_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-build-2.6.8-4-powerpc-smp_2.6.8-13_powerpc.deb kernel-build-2.6.8-4-powerpc_2.6.8-13_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-build-2.6.8-4-powerpc_2.6.8-13_powerpc.deb kernel-headers-2.6.8-4_2.6.8-13_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-headers-2.6.8-4_2.6.8-13_powerpc.deb kernel-image-2.6.8-4-power3-smp_2.6.8-13_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-image-2.6.8-4-power3-smp_2.6.8-13_powerpc.deb kernel-image-2.6.8-4-power3_2.6.8-13_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-image-2.6.8-4-power3_2.6.8-13_powerpc.deb kernel-image-2.6.8-4-power4-smp_2.6.8-13_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-image-2.6.8-4-power4-smp_2.6.8-13_powerpc.deb kernel-image-2.6.8-4-power4_2.6.8-13_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-image-2.6.8-4-power4_2.6.8-13_powerpc.deb kernel-image-2.6.8-4-powerpc-smp_2.6.8-13_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-image-2.6.8-4-powerpc-smp_2.6.8-13_powerpc.deb kernel-image-2.6.8-4-powerpc_2.6.8-13_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-image-2.6.8-4-powerpc_2.6.8-13_powerpc.deb kernel-patch-powerpc-2.6.8_2.6.8-13.dsc to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-patch-powerpc-2.6.8_2.6.8-13.dsc kernel-patch-powerpc-2.6.8_2.6.8-13.tar.gz to pool/main/k/kernel-patch-powerpc-2.6.8/kernel-patch-powerpc-2.6.8_2.6.8-13.tar.gz A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if
Bug#311357: marked as done (kernel-image-2.6.8-2: via-rhine fails to reserve I/O region, no networking available)
Your message dated Mon, 28 May 2007 23:06:03 + with message-id [EMAIL PROTECTED] and subject line Bug#311357: fixed in kernel-image-2.6.8-alpha 2.6.8-17 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: kernel-image-2.6.8-2-k7 Version: 2.6.8-16 Severity: important File: kernel-image-2.6.8-2 The via-rhine module no longer configures my network card correctly. This broke with the latest kernel upgrade. Below are the messages from the broken kernel and a working kernel. When loading the via-rhine module at boot (or by hand) with kernel 2.6.8-16 I get May 31 00:55:15 localhost kernel: via-rhine.c:v1.10-LK1.1.20-2.6 May-23-2004 Written by Donald Becker May 31 00:55:15 localhost kernel: PCI: Found IRQ 10 for device :00:06.0 May 31 00:55:15 localhost kernel: PCI: Sharing IRQ 10 with :00:04.4 May 31 00:55:15 localhost kernel: PCI: Unable to reserve I/O region #1:[EMAIL PROTECTED] for device :00:06.0 May 31 00:55:15 localhost kernel: via-rhine: probe of :00:06.0 failed with error -16 and networking is unavailable on the system. When loading the via-rhine module at boot (or by hand) with kernel 2.6.8-13 where it works I get May 31 01:53:00 localhost kernel: via-rhine.c:v1.10-LK1.1.20-2.6 May-23-2004 Written by Donald Becker May 31 01:53:00 localhost kernel: PCI: Found IRQ 10 for device :00:06.0 May 31 01:53:00 localhost kernel: PCI: Sharing IRQ 10 with :00:04.4 May 31 01:53:00 localhost kernel: eth0: VIA VT86C100A Rhine at 0xd800, 00:50:ba:c3:4f:50, IRQ 10. May 31 01:53:00 localhost kernel: eth0: MII PHY found at address 8, status 0x782d advertising 05e1 Link 45e1. lspci -v give :00:06.0 Ethernet controller: VIA Technologies, Inc. VT86C100A [Rhine] (rev 06) Subsystem: D-Link System Inc DFE-530TX rev A Flags: bus master, medium devsel, latency 64, IRQ 10 I/O ports at d800 [size=128] Memory at e680 (32-bit, non-prefetchable) [size=128] Expansion ROM at effd [disabled] [size=64K] -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.8-2-386 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages kernel-image-2.6.8-2-k7 depends on: ii coreutils [fileutils] 5.2.1-2The GNU core utilities ii initrd-tools 0.1.81.1 tools to create initrd image for p ii module-init-tools 3.2-pre1-2 tools for managing Linux kernel mo -- no debconf information ---End Message--- ---BeginMessage--- Source: kernel-image-2.6.8-alpha Source-Version: 2.6.8-17 We believe that the bug you reported is fixed in the latest version of kernel-image-2.6.8-alpha, which is due to be installed in the Debian FTP archive: kernel-headers-2.6.8-4-generic_2.6.8-17_alpha.deb to pool/main/k/kernel-image-2.6.8-alpha/kernel-headers-2.6.8-4-generic_2.6.8-17_alpha.deb kernel-headers-2.6.8-4-smp_2.6.8-17_alpha.deb to pool/main/k/kernel-image-2.6.8-alpha/kernel-headers-2.6.8-4-smp_2.6.8-17_alpha.deb kernel-headers-2.6.8-4_2.6.8-17_alpha.deb to pool/main/k/kernel-image-2.6.8-alpha/kernel-headers-2.6.8-4_2.6.8-17_alpha.deb kernel-image-2.6.8-4-generic_2.6.8-17_alpha.deb to pool/main/k/kernel-image-2.6.8-alpha/kernel-image-2.6.8-4-generic_2.6.8-17_alpha.deb kernel-image-2.6.8-4-smp_2.6.8-17_alpha.deb to pool/main/k/kernel-image-2.6.8-alpha/kernel-image-2.6.8-4-smp_2.6.8-17_alpha.deb kernel-image-2.6.8-alpha_2.6.8-17.dsc to pool/main/k/kernel-image-2.6.8-alpha/kernel-image-2.6.8-alpha_2.6.8-17.dsc kernel-image-2.6.8-alpha_2.6.8-17.tar.gz to pool/main/k/kernel-image-2.6.8-alpha/kernel-image-2.6.8-alpha_2.6.8-17.tar.gz A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. dann frazier [EMAIL PROTECTED] (supplier of updated kernel-image-2.6.8-alpha package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 26 May 2007 03:54:13 -0600 Source: kernel-image-2.6.8-alpha Binary: kernel-headers-2.6.8-4 kernel-image-2.6.8-4-smp kernel-headers-2.6.8-4-smp
Bug#321442: marked as done (kernel-source-2.6.8: fails to compile on powerpc (drivers/ide/ppc/pmac.c))
Your message dated Mon, 28 May 2007 23:06:26 + with message-id [EMAIL PROTECTED] and subject line Bug#321442: fixed in kernel-image-2.6.8-ia64 2.6.8-15 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: kernel-source-2.6.8 Version: 2.6.8-16 Severity: normal The kernel-source-2.6.8 sources fail to compile on powerpc (PowerMac 4400). ___ CC drivers/ide/ide.o CC drivers/ide/ide-default.o CC drivers/ide/ide-io.o CC drivers/ide/ide-iops.o CC drivers/ide/ide-lib.o CC drivers/ide/ide-probe.o CC drivers/ide/ide-taskfile.o CC drivers/ide/ide-dma.o CC drivers/ide/ide-proc.o CC drivers/ide/ppc/pmac.o drivers/ide/ppc/pmac.c: Dans la fonction « pmac_ide_dma_read »: drivers/ide/ppc/pmac.c:1951: error: `ide_dma_intr' undeclared (first use in this function) drivers/ide/ppc/pmac.c:1951: error: (Each undeclared identifier is reported only once drivers/ide/ppc/pmac.c:1951: error: for each function it appears in.) drivers/ide/ppc/pmac.c: Dans la fonction « pmac_ide_dma_write »: drivers/ide/ppc/pmac.c:1982: error: `ide_dma_intr' undeclared (first use in this function) drivers/ide/ppc/pmac.c: Dans la fonction « pmac_ide_setup_dma »: drivers/ide/ppc/pmac.c:2157: error: `__ide_dma_off_quietly' undeclared (first use in this function) drivers/ide/ppc/pmac.c:2158: error: `__ide_dma_on' undeclared (first use in this function) drivers/ide/ppc/pmac.c:2167: error: `__ide_dma_verbose' undeclared (first use in this function) drivers/ide/ppc/pmac.c:2168: error: `__ide_dma_timeout' undeclared (first use in this function) make[3]: *** [drivers/ide/ppc/pmac.o] Error 1 make[2]: *** [drivers/ide] Error 2 make[1]: *** [drivers] Error 2 ___ -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: powerpc (ppc) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.4.26-ltp Locale: LANG=fr_FR, LC_CTYPE=fr_FR (charmap=UTF-8) (ignored: LC_ALL set to fr_FR.UTF-8) Versions of packages kernel-source-2.6.8 depends on: ii binutils 2.16.1-2 The GNU assembler, linker and bina ii bzip2 1.0.2-8high-quality block-sorting file co ii coreutils [fileutils] 5.2.1-2The GNU core utilities ii fileutils 5.2.1-2The GNU file management utilities Versions of packages kernel-source-2.6.8 recommends: ii gcc 4:3.3.5-3The GNU C compiler ii libc6-dev [libc-dev]2.3.2.ds1-22 GNU C Library: Development Librari ii make3.80-9 The GNU version of the make util -- no debconf information ---End Message--- ---BeginMessage--- Source: kernel-image-2.6.8-ia64 Source-Version: 2.6.8-15 We believe that the bug you reported is fixed in the latest version of kernel-image-2.6.8-ia64, which is due to be installed in the Debian FTP archive: kernel-headers-2.6-itanium-smp_2.6.8-15_ia64.deb to pool/main/k/kernel-image-2.6.8-ia64/kernel-headers-2.6-itanium-smp_2.6.8-15_ia64.deb kernel-headers-2.6-itanium_2.6.8-15_ia64.deb to pool/main/k/kernel-image-2.6.8-ia64/kernel-headers-2.6-itanium_2.6.8-15_ia64.deb kernel-headers-2.6-mckinley-smp_2.6.8-15_ia64.deb to pool/main/k/kernel-image-2.6.8-ia64/kernel-headers-2.6-mckinley-smp_2.6.8-15_ia64.deb kernel-headers-2.6-mckinley_2.6.8-15_ia64.deb to pool/main/k/kernel-image-2.6.8-ia64/kernel-headers-2.6-mckinley_2.6.8-15_ia64.deb kernel-headers-2.6.8-4-itanium-smp_2.6.8-15_ia64.deb to pool/main/k/kernel-image-2.6.8-ia64/kernel-headers-2.6.8-4-itanium-smp_2.6.8-15_ia64.deb kernel-headers-2.6.8-4-itanium_2.6.8-15_ia64.deb to pool/main/k/kernel-image-2.6.8-ia64/kernel-headers-2.6.8-4-itanium_2.6.8-15_ia64.deb kernel-headers-2.6.8-4-mckinley-smp_2.6.8-15_ia64.deb to pool/main/k/kernel-image-2.6.8-ia64/kernel-headers-2.6.8-4-mckinley-smp_2.6.8-15_ia64.deb kernel-headers-2.6.8-4-mckinley_2.6.8-15_ia64.deb to pool/main/k/kernel-image-2.6.8-ia64/kernel-headers-2.6.8-4-mckinley_2.6.8-15_ia64.deb kernel-headers-2.6.8-4_2.6.8-15_ia64.deb to pool/main/k/kernel-image-2.6.8-ia64/kernel-headers-2.6.8-4_2.6.8-15_ia64.deb kernel-image-2.6-itanium-smp_2.6.8-15_ia64.deb to pool/main/k/kernel-image-2.6.8-ia64/kernel-image-2.6-itanium-smp_2.6.8-15_ia64.deb kernel-image-2.6-itanium_2.6.8-15_ia64.deb to pool/main/k/kernel-image-2.6.8-ia64/kernel-image-2.6-itanium_2.6.8-15_ia64.deb kernel-image-2.6-mckinley-smp_2.6.8-15_ia64.deb to
Bug#349774: marked as done ([Fwd: Re: stable kernel 2.6.8-2-686])
Your message dated Mon, 28 May 2007 23:06:13 + with message-id [EMAIL PROTECTED] and subject line Bug#349774: fixed in kernel-image-2.6.8-hppa 2.6.8-7 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: kernel-source-2.6.8 Version: 2.6.8-16sarge1 I'll file a bug for this usertag it dkt-pending-sarge-update. -- dann frazier [EMAIL PROTECTED] ---BeginMessage--- On Tue, 2006-01-17 at 16:23 -0700, dann frazier wrote: On Mon, 2006-01-16 at 23:07 +, Stuart T. R. Rowan wrote: Hi, The 3c59x kernel module doesn't work with vlan (802.1q) tagged packets. Apparently the fix was committed somewhere around 2.6.10, anyway we've upgraded our stable box to vanilla kernel 2.6.15.1 to work around this issue -- no discarded packets at all now. If there's gonna be an update to the stable kernel, a patch to make the 3c59x module work with vlans rather than silently failing might be a plan. hey Stu, got a link to the appropriate changeset(s)? Hey Dann, Yes! So the vlan patch turned up in patch-2.6.9.bz2. The changeset is on http://www.kernel.org/git/?p=linux/kernel/git/torvalds/old-2.6-bkcvs.git 3c59x.c has a history list here in case this builds on other non 2.6.8 patches: http://tinyurl.com/b8a95 On this you will clearly see the below commit listed: Title: [PATCH] VLAN support for 3c59x/3c90x commit 03e4b71f751da25d7b2d026ba6f4f904116e51e5 Body: This adds VLAN support to the 3c59x/90x series hardware. Stefan de Konink ported this code from the 2.4 VLAN patches and tested it extensively. I cleaned up the ifdefs and fixed a problem with bracketing that made older cards fail. I hope that helps? Thanks, Stu. (please keep me CC'd) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] ---End Message--- ---End Message--- ---BeginMessage--- Source: kernel-image-2.6.8-hppa Source-Version: 2.6.8-7 We believe that the bug you reported is fixed in the latest version of kernel-image-2.6.8-hppa, which is due to be installed in the Debian FTP archive: kernel-headers-2.6.8-4-32-smp_2.6.8-7_hppa.deb to pool/main/k/kernel-image-2.6.8-hppa/kernel-headers-2.6.8-4-32-smp_2.6.8-7_hppa.deb kernel-headers-2.6.8-4-32_2.6.8-7_hppa.deb to pool/main/k/kernel-image-2.6.8-hppa/kernel-headers-2.6.8-4-32_2.6.8-7_hppa.deb kernel-headers-2.6.8-4-64-smp_2.6.8-7_hppa.deb to pool/main/k/kernel-image-2.6.8-hppa/kernel-headers-2.6.8-4-64-smp_2.6.8-7_hppa.deb kernel-headers-2.6.8-4-64_2.6.8-7_hppa.deb to pool/main/k/kernel-image-2.6.8-hppa/kernel-headers-2.6.8-4-64_2.6.8-7_hppa.deb kernel-headers-2.6.8-4_2.6.8-7_hppa.deb to pool/main/k/kernel-image-2.6.8-hppa/kernel-headers-2.6.8-4_2.6.8-7_hppa.deb kernel-image-2.6.8-4-32-smp_2.6.8-7_hppa.deb to pool/main/k/kernel-image-2.6.8-hppa/kernel-image-2.6.8-4-32-smp_2.6.8-7_hppa.deb kernel-image-2.6.8-4-32_2.6.8-7_hppa.deb to pool/main/k/kernel-image-2.6.8-hppa/kernel-image-2.6.8-4-32_2.6.8-7_hppa.deb kernel-image-2.6.8-4-64-smp_2.6.8-7_hppa.deb to pool/main/k/kernel-image-2.6.8-hppa/kernel-image-2.6.8-4-64-smp_2.6.8-7_hppa.deb kernel-image-2.6.8-4-64_2.6.8-7_hppa.deb to pool/main/k/kernel-image-2.6.8-hppa/kernel-image-2.6.8-4-64_2.6.8-7_hppa.deb kernel-image-2.6.8-hppa_2.6.8-7.dsc to pool/main/k/kernel-image-2.6.8-hppa/kernel-image-2.6.8-hppa_2.6.8-7.dsc kernel-image-2.6.8-hppa_2.6.8-7.tar.gz to pool/main/k/kernel-image-2.6.8-hppa/kernel-image-2.6.8-hppa_2.6.8-7.tar.gz A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. dann frazier [EMAIL PROTECTED] (supplier of updated kernel-image-2.6.8-hppa package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 26 May 2007 04:01:59 -0600 Source: kernel-image-2.6.8-hppa Binary: kernel-image-2.6.8-4-64-smp kernel-headers-2.6.8-4-64-smp kernel-headers-2.6.8-4-32-smp kernel-headers-2.6.8-4 kernel-image-2.6.8-4-64 kernel-headers-2.6.8-4-32 kernel-headers-2.6.8-4-64 kernel-image-2.6.8-4-32-smp kernel-image-2.6.8-4-32 Architecture: source hppa Version: 2.6.8-7 Distribution: oldstable Urgency: high
Bug#349774: marked as done ([Fwd: Re: stable kernel 2.6.8-2-686])
Your message dated Mon, 28 May 2007 23:06:28 + with message-id [EMAIL PROTECTED] and subject line Bug#349774: fixed in kernel-image-2.6.8-s390 2.6.8-6 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: kernel-source-2.6.8 Version: 2.6.8-16sarge1 I'll file a bug for this usertag it dkt-pending-sarge-update. -- dann frazier [EMAIL PROTECTED] ---BeginMessage--- On Tue, 2006-01-17 at 16:23 -0700, dann frazier wrote: On Mon, 2006-01-16 at 23:07 +, Stuart T. R. Rowan wrote: Hi, The 3c59x kernel module doesn't work with vlan (802.1q) tagged packets. Apparently the fix was committed somewhere around 2.6.10, anyway we've upgraded our stable box to vanilla kernel 2.6.15.1 to work around this issue -- no discarded packets at all now. If there's gonna be an update to the stable kernel, a patch to make the 3c59x module work with vlans rather than silently failing might be a plan. hey Stu, got a link to the appropriate changeset(s)? Hey Dann, Yes! So the vlan patch turned up in patch-2.6.9.bz2. The changeset is on http://www.kernel.org/git/?p=linux/kernel/git/torvalds/old-2.6-bkcvs.git 3c59x.c has a history list here in case this builds on other non 2.6.8 patches: http://tinyurl.com/b8a95 On this you will clearly see the below commit listed: Title: [PATCH] VLAN support for 3c59x/3c90x commit 03e4b71f751da25d7b2d026ba6f4f904116e51e5 Body: This adds VLAN support to the 3c59x/90x series hardware. Stefan de Konink ported this code from the 2.4 VLAN patches and tested it extensively. I cleaned up the ifdefs and fixed a problem with bracketing that made older cards fail. I hope that helps? Thanks, Stu. (please keep me CC'd) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] ---End Message--- ---End Message--- ---BeginMessage--- Source: kernel-image-2.6.8-s390 Source-Version: 2.6.8-6 We believe that the bug you reported is fixed in the latest version of kernel-image-2.6.8-s390, which is due to be installed in the Debian FTP archive: kernel-headers-2.6.8-4_2.6.8-6_s390.deb to pool/main/k/kernel-image-2.6.8-s390/kernel-headers-2.6.8-4_2.6.8-6_s390.deb kernel-image-2.6.8-4-s390-tape_2.6.8-6_s390.deb to pool/main/k/kernel-image-2.6.8-s390/kernel-image-2.6.8-4-s390-tape_2.6.8-6_s390.deb kernel-image-2.6.8-4-s390_2.6.8-6_s390.deb to pool/main/k/kernel-image-2.6.8-s390/kernel-image-2.6.8-4-s390_2.6.8-6_s390.deb kernel-image-2.6.8-4-s390x_2.6.8-6_s390.deb to pool/main/k/kernel-image-2.6.8-s390/kernel-image-2.6.8-4-s390x_2.6.8-6_s390.deb kernel-image-2.6.8-s390_2.6.8-6.dsc to pool/main/k/kernel-image-2.6.8-s390/kernel-image-2.6.8-s390_2.6.8-6.dsc kernel-image-2.6.8-s390_2.6.8-6.tar.gz to pool/main/k/kernel-image-2.6.8-s390/kernel-image-2.6.8-s390_2.6.8-6.tar.gz kernel-patch-2.6.8-s390_2.6.8-6_all.deb to pool/main/k/kernel-image-2.6.8-s390/kernel-patch-2.6.8-s390_2.6.8-6_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. dann frazier [EMAIL PROTECTED] (supplier of updated kernel-image-2.6.8-s390 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 26 May 2007 03:23:35 -0600 Source: kernel-image-2.6.8-s390 Binary: kernel-headers-2.6.8-4 kernel-patch-2.6.8-s390 kernel-image-2.6.8-4-s390x kernel-image-2.6.8-4-s390-tape kernel-image-2.6.8-4-s390 Architecture: source s390 all Version: 2.6.8-6 Distribution: oldstable Urgency: high Maintainer: Debian kernel team debian-kernel@lists.debian.org Changed-By: dann frazier [EMAIL PROTECTED] Description: kernel-headers-2.6.8-4 - Header files related to Linux kernel version 2.6.8 on IBM S/390 kernel-image-2.6.8-4-s390 - Linux kernel image for kernel version 2.6.8 on IBM S/390 kernel-image-2.6.8-4-s390-tape - Linux kernel image for kernel version 2.6.8 on IBM S/390 kernel-image-2.6.8-4-s390x - Linux kernel image for kernel version 2.6.8 on IBM zSeries. kernel-patch-2.6.8-s390 - Diffs to the Linux kernel source 2.6.8 for IBM S/390 and zSeries Closes: 311357 317286 321442 323557 336153 349774 354493
Bug#321442: marked as done (kernel-source-2.6.8: fails to compile on powerpc (drivers/ide/ppc/pmac.c))
Your message dated Mon, 28 May 2007 23:06:22 + with message-id [EMAIL PROTECTED] and subject line Bug#321442: fixed in kernel-image-2.6.8-i386 2.6.8-17 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: kernel-source-2.6.8 Version: 2.6.8-16 Severity: normal The kernel-source-2.6.8 sources fail to compile on powerpc (PowerMac 4400). ___ CC drivers/ide/ide.o CC drivers/ide/ide-default.o CC drivers/ide/ide-io.o CC drivers/ide/ide-iops.o CC drivers/ide/ide-lib.o CC drivers/ide/ide-probe.o CC drivers/ide/ide-taskfile.o CC drivers/ide/ide-dma.o CC drivers/ide/ide-proc.o CC drivers/ide/ppc/pmac.o drivers/ide/ppc/pmac.c: Dans la fonction « pmac_ide_dma_read »: drivers/ide/ppc/pmac.c:1951: error: `ide_dma_intr' undeclared (first use in this function) drivers/ide/ppc/pmac.c:1951: error: (Each undeclared identifier is reported only once drivers/ide/ppc/pmac.c:1951: error: for each function it appears in.) drivers/ide/ppc/pmac.c: Dans la fonction « pmac_ide_dma_write »: drivers/ide/ppc/pmac.c:1982: error: `ide_dma_intr' undeclared (first use in this function) drivers/ide/ppc/pmac.c: Dans la fonction « pmac_ide_setup_dma »: drivers/ide/ppc/pmac.c:2157: error: `__ide_dma_off_quietly' undeclared (first use in this function) drivers/ide/ppc/pmac.c:2158: error: `__ide_dma_on' undeclared (first use in this function) drivers/ide/ppc/pmac.c:2167: error: `__ide_dma_verbose' undeclared (first use in this function) drivers/ide/ppc/pmac.c:2168: error: `__ide_dma_timeout' undeclared (first use in this function) make[3]: *** [drivers/ide/ppc/pmac.o] Error 1 make[2]: *** [drivers/ide] Error 2 make[1]: *** [drivers] Error 2 ___ -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: powerpc (ppc) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.4.26-ltp Locale: LANG=fr_FR, LC_CTYPE=fr_FR (charmap=UTF-8) (ignored: LC_ALL set to fr_FR.UTF-8) Versions of packages kernel-source-2.6.8 depends on: ii binutils 2.16.1-2 The GNU assembler, linker and bina ii bzip2 1.0.2-8high-quality block-sorting file co ii coreutils [fileutils] 5.2.1-2The GNU core utilities ii fileutils 5.2.1-2The GNU file management utilities Versions of packages kernel-source-2.6.8 recommends: ii gcc 4:3.3.5-3The GNU C compiler ii libc6-dev [libc-dev]2.3.2.ds1-22 GNU C Library: Development Librari ii make3.80-9 The GNU version of the make util -- no debconf information ---End Message--- ---BeginMessage--- Source: kernel-image-2.6.8-i386 Source-Version: 2.6.8-17 We believe that the bug you reported is fixed in the latest version of kernel-image-2.6.8-i386, which is due to be installed in the Debian FTP archive: kernel-headers-2.6.8-4-386_2.6.8-17_i386.deb to pool/main/k/kernel-image-2.6.8-i386/kernel-headers-2.6.8-4-386_2.6.8-17_i386.deb kernel-headers-2.6.8-4-686-smp_2.6.8-17_i386.deb to pool/main/k/kernel-image-2.6.8-i386/kernel-headers-2.6.8-4-686-smp_2.6.8-17_i386.deb kernel-headers-2.6.8-4-686_2.6.8-17_i386.deb to pool/main/k/kernel-image-2.6.8-i386/kernel-headers-2.6.8-4-686_2.6.8-17_i386.deb kernel-headers-2.6.8-4-k7-smp_2.6.8-17_i386.deb to pool/main/k/kernel-image-2.6.8-i386/kernel-headers-2.6.8-4-k7-smp_2.6.8-17_i386.deb kernel-headers-2.6.8-4-k7_2.6.8-17_i386.deb to pool/main/k/kernel-image-2.6.8-i386/kernel-headers-2.6.8-4-k7_2.6.8-17_i386.deb kernel-headers-2.6.8-4_2.6.8-17_i386.deb to pool/main/k/kernel-image-2.6.8-i386/kernel-headers-2.6.8-4_2.6.8-17_i386.deb kernel-image-2.6.8-4-386_2.6.8-17_i386.deb to pool/main/k/kernel-image-2.6.8-i386/kernel-image-2.6.8-4-386_2.6.8-17_i386.deb kernel-image-2.6.8-4-686-smp_2.6.8-17_i386.deb to pool/main/k/kernel-image-2.6.8-i386/kernel-image-2.6.8-4-686-smp_2.6.8-17_i386.deb kernel-image-2.6.8-4-686_2.6.8-17_i386.deb to pool/main/k/kernel-image-2.6.8-i386/kernel-image-2.6.8-4-686_2.6.8-17_i386.deb kernel-image-2.6.8-4-k7-smp_2.6.8-17_i386.deb to pool/main/k/kernel-image-2.6.8-i386/kernel-image-2.6.8-4-k7-smp_2.6.8-17_i386.deb kernel-image-2.6.8-4-k7_2.6.8-17_i386.deb to pool/main/k/kernel-image-2.6.8-i386/kernel-image-2.6.8-4-k7_2.6.8-17_i386.deb kernel-image-2.6.8-i386_2.6.8-17.dsc to pool/main/k/kernel-image-2.6.8-i386/kernel-image-2.6.8-i386_2.6.8-17.dsc
Bug#354493: marked as done (kernel-source-2.6.8: can't install grub on cciss device)
Your message dated Mon, 28 May 2007 23:06:09 +
with message-id [EMAIL PROTECTED]
and subject line Bug#354493: fixed in kernel-image-2.6.8-amd64 2.6.8-17
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
---BeginMessage---
Package: kernel-source-2.6.8
Version: 2.6.8-16sarge2
Severity: normal
Tags: patch
In kernel.org 2.6.8, the block layer (drivers/block/ioctl.c) has:
case BLKFLSBUF:
if (!capable(CAP_SYS_ADMIN))
return -EACCES;
if (disk-fops-ioctl) {
ret = disk-fops-ioctl(inode, file, cmd, arg);
if (ret != -EINVAL)
return ret;
}
fsync_bdev(bdev);
invalidate_bdev(bdev, 0);
return 0;
So, fsync_bdev()/invalidate_bdev() are only called if ret == -EINVAL.
In pristine 2.6.8, cciss returned -EBADRQC, so these functions were never
called.
In 2.6.9, the block layer was modified to also accept -ENOTTY:
http://www.kernel.org/git/?p=linux/kernel/git/torvalds/old-2.6-bkcvs.git;a=commitdiff;h=b295216702a8fb86ef8e3951df9d7118746e35c7
So, in 2.6.10-rc4, the only fix needed was to make cciss return -ENOTTY, which
is what Mike submitted.
http://www.kernel.org/git/?p=linux/kernel/git/torvalds/old-2.6-bkcvs.git;a=commitdiff;h=d28d721eb3f7df904fb1533d314879da33f9b50a
Since 2.6.8 didn't accept -ENOTTY, simply backporting this fix wasn't enough to
fix the bug in 2.6.8, we also need the block layer changeset.
-- System Information:
Debian Release: 3.1
Architecture: ia64
Kernel: Linux 2.6.8-2-mckinley-smp
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages kernel-source-2.6.8 depends on:
ii binutils 2.15-6 The GNU assembler, linker and bina
ii bzip2 1.0.2-7high-quality block-sorting file co
ii coreutils [fileutils] 5.2.1-2The GNU core utilities
-- no debconf information
---End Message---
---BeginMessage---
Source: kernel-image-2.6.8-amd64
Source-Version: 2.6.8-17
We believe that the bug you reported is fixed in the latest version of
kernel-image-2.6.8-amd64, which is due to be installed in the Debian FTP
archive:
kernel-headers-2.6.8-13-amd64-generic_2.6.8-17_i386.deb
to
pool/main/k/kernel-image-2.6.8-amd64/kernel-headers-2.6.8-13-amd64-generic_2.6.8-17_i386.deb
kernel-headers-2.6.8-13-amd64-k8-smp_2.6.8-17_i386.deb
to
pool/main/k/kernel-image-2.6.8-amd64/kernel-headers-2.6.8-13-amd64-k8-smp_2.6.8-17_i386.deb
kernel-headers-2.6.8-13-amd64-k8_2.6.8-17_i386.deb
to
pool/main/k/kernel-image-2.6.8-amd64/kernel-headers-2.6.8-13-amd64-k8_2.6.8-17_i386.deb
kernel-headers-2.6.8-13-em64t-p4-smp_2.6.8-17_i386.deb
to
pool/main/k/kernel-image-2.6.8-amd64/kernel-headers-2.6.8-13-em64t-p4-smp_2.6.8-17_i386.deb
kernel-headers-2.6.8-13-em64t-p4_2.6.8-17_i386.deb
to
pool/main/k/kernel-image-2.6.8-amd64/kernel-headers-2.6.8-13-em64t-p4_2.6.8-17_i386.deb
kernel-headers-2.6.8-13_2.6.8-17_i386.deb
to
pool/main/k/kernel-image-2.6.8-amd64/kernel-headers-2.6.8-13_2.6.8-17_i386.deb
kernel-image-2.6.8-13-amd64-generic_2.6.8-17_i386.deb
to
pool/main/k/kernel-image-2.6.8-amd64/kernel-image-2.6.8-13-amd64-generic_2.6.8-17_i386.deb
kernel-image-2.6.8-13-amd64-k8-smp_2.6.8-17_i386.deb
to
pool/main/k/kernel-image-2.6.8-amd64/kernel-image-2.6.8-13-amd64-k8-smp_2.6.8-17_i386.deb
kernel-image-2.6.8-13-amd64-k8_2.6.8-17_i386.deb
to
pool/main/k/kernel-image-2.6.8-amd64/kernel-image-2.6.8-13-amd64-k8_2.6.8-17_i386.deb
kernel-image-2.6.8-13-em64t-p4-smp_2.6.8-17_i386.deb
to
pool/main/k/kernel-image-2.6.8-amd64/kernel-image-2.6.8-13-em64t-p4-smp_2.6.8-17_i386.deb
kernel-image-2.6.8-13-em64t-p4_2.6.8-17_i386.deb
to
pool/main/k/kernel-image-2.6.8-amd64/kernel-image-2.6.8-13-em64t-p4_2.6.8-17_i386.deb
kernel-image-2.6.8-amd64_2.6.8-17.dsc
to pool/main/k/kernel-image-2.6.8-amd64/kernel-image-2.6.8-amd64_2.6.8-17.dsc
kernel-image-2.6.8-amd64_2.6.8-17.tar.gz
to
pool/main/k/kernel-image-2.6.8-amd64/kernel-image-2.6.8-amd64_2.6.8-17.tar.gz
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
dann frazier [EMAIL PROTECTED] (supplier of updated kernel-image-2.6.8-amd64
package)
(This message was generated
