Re: error in apt-get upgrade process
On Sat, Dec 04, 2004 at 01:46:26PM -0800, nhrosen wrote: Why is apt-get -f u upgrade asking me now to upgrade to kernel-image-2.4.27-1-k7? This box is on unstable * kernel-image-2.6.9-1-k7. Likely you have both kernel-image-2.4.27-1-k7 and kernel-image-2.6.9-1-k7. installed on the machine. Several times over the past several weeks already upgraded kernel-images have been upgraded to the SAME image. There have been at least two releases of kernel-image-2.4.27-1-k7 over the past few weeks (sorry about that, we all make mistakes). Are you sure you aren't seeing successive updates of the same package. During those upgrades the initrd.img link has been invariably removed with nothing left in place. A new link had to be created manually for the lilo boot process to work. Fun for an ancient FORTUNE SYSTEMS and ALTOS ATT UNIX tech support guy, but time consuming. That is bit of a problem, though I think this is the first time it has been reported against 2.4.27 (as opposed to 2.6.8/9). There is at least one bug in the BTS for this. -- Horms
Processed: Re: Bug#284567: Unable to handle kernel paging request
Processing commands for [EMAIL PROTECTED]: reassign 284567 kernel-source-2.4.27 Bug#284567: Unable to handle kernel paging request Bug reassigned from package `kernel' to `kernel-source-2.4.27'. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Bug#284567: Unable to handle kernel paging request
reassign 284567 kernel-source-2.4.27
thanks
On Tue, Dec 07, 2004 at 01:22:24AM -0800, Tzvetan Mikov wrote:
Package: kernel
Severity: normal
The problem occured while running tar, causing it to segfault. It was
reproducible until a reboot.
I am copying the info from syslog below. I did a search about this kind of
problem and found many complaints about it, but no satisfactory explanation
or resolution.
memtest86 found no memory problems.
Did any of these discussions included (proposed) patches or fixes?
If so do you have any links handy?
Dec 6 21:05:23 localhost kernel: Unable to handle kernel paging request at
virtual address 1050f2a3
Dec 6 21:05:23 localhost kernel: printing eip:
Dec 6 21:05:23 localhost kernel: c013747d
Dec 6 21:05:23 localhost kernel: *pde =
Dec 6 21:05:23 localhost kernel: Oops:
Dec 6 21:05:23 localhost kernel: CPU:0
Dec 6 21:05:23 localhost kernel: EIP:0010:[sys_lstat64+42/99]Not
tainted
Dec 6 21:05:23 localhost kernel: EFLAGS: 00010206
Dec 6 21:05:23 localhost kernel: eax: 1050f26f ebx: ecx:
edx: ce1139e0
Dec 6 21:05:23 localhost kernel: esi: 401600e8 edi: ba10 ebp:
b968 esp: ce6c5f9c
Dec 6 21:05:23 localhost kernel: ds: 0018 es: 0018 ss: 0018
Dec 6 21:05:23 localhost kernel: Process tar (pid: 3811, stackpage=ce6c5000)
Dec 6 21:05:23 localhost kernel: Stack: ce1139e0 c12c6310 cc42f350 080ab840
0005 0008 0001 c7f21240
Dec 6 21:05:23 localhost kernel:ce6c4000 c01081fb 080ab840 ba10
4015d620 401600e8 ba10 b968
Dec 6 21:05:23 localhost kernel:00c4 002b 002b 00c4
400f7168 0023 0246 b904
Dec 6 21:05:23 localhost kernel: Call Trace:[system_call+51/56]
Dec 6 21:05:23 localhost kernel:
Dec 6 21:05:23 localhost kernel: Code: 83 78 34 00 74 07 52 ff 50 34 59 eb
02 31 c0 85 c0 89 c3 75
Is it possible to run this through ksymoops?
-- System Information:
Debian Release: 3.1
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.4.27-1-386
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Did this kernel come from kernel-image-2.4.27-1-386 and if
so which version? And if it is not the latest (-6) could you try that?
--
Horms
Bug#285430: Wrong module listed for INI-A100U2W
Package: initrd-tools Version: 0.1.74 The mkinitrd script has the wrong module listed for the Initio INI-A100U2W SCSI card. It attempts to probe for a nonexistent module called inia100, when it should be looking fof the module a100u2w. On line 518 of mkinitrd it says: s/^INIA100$/inia100/; t This should be changed to: s/^INIA100$/a100u2w/; t -- Seth ninja monkey Mattinen [EMAIL PROTECTED]
Bug#270376: Still a problem in 2.6.9
reassign 27037 kernel-image-2.6.8-1-386,kernel-image-2.6.9-1-386 Thanks I've upgraded to 2.6.9 to see if the problem still exists and it does. I am still unable to use my PCMCIA cards under any 2.6 kernel. Thanks Jefferson Cowart [EMAIL PROTECTED]
Processed: Still a problem in 2.6.9
Processing commands for [EMAIL PROTECTED]: reassign 270376 kernel-image-2.6.8-1-386,kernel-image-2.6.9-1-386 Bug#270376: kernel-image-2.6.8-1-386: PCMCIA Nic stops working after upgradin g to 2.6.6/7/8 Bug reassigned from package `kernel-image-2.6.8-1-386' to `kernel-image-2.6.8-1-386,kernel-image-2.6.9-1-386'. Thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Re: input core
On Wed, Dec 08, 2004 at 06:29:34PM +, Matthew Wilcox wrote: On Wed, Dec 08, 2004 at 07:26:40PM +0100, Paul Akkermans wrote: Hello everyone, HEY! RETARD!! This is the third time this week you've posted to debian-kernel. This is the third time I'm telling you to fuck off. I was polite before. But now you've made me angry. GO AWAY. I notice this time he CCed kernelnewbies, which is a better fourum. Telling him that is probably more useful than shouting at the poor guy. -- Horms
Bug#284680: slower xine since 2.6.8-2.6.9 ?
On Wed, Dec 08, 2004 at 08:17:23AM +0900, Junichi Uekawa wrote: Package: kernel-source-2.6.9 Version: 2.6.9-1 Using ALSA from kernel-source-2.6.9 is much slower than it was with kernel-source-2.6.8, when using xine. It can be worked around with xine using OSS device (which is alsa-oss device) This is on iBook G4 12. Thanks for the feedback. * 2.6.8 is the kernel for sarge, 2.6.9 is for testing. Feedback is very welcome, but 2.6.8 is the focus for now. -- Horms
Bug#279666: marked as done (kernel-image-2.6.8-1-k7: Runs out of network buffers)
Your message dated Mon, 13 Dec 2004 16:36:51 +0900 with message-id [EMAIL PROTECTED] and subject line Bug#279666: kernel-image-2.6.8-1-k7: Runs out of network buffers 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) -- Received: (at submit) by bugs.debian.org; 4 Nov 2004 14:29:27 + From [EMAIL PROTECTED] Thu Nov 04 06:29:27 2004 Return-path: [EMAIL PROTECTED] Received: from lsorense.tor.istop.com (athlon.lan) [66.11.182.144] (Debian-exim) by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1CPicA-000157-00; Thu, 04 Nov 2004 06:29:27 -0800 Received: from root by athlon.lan with local (Exim 4.34) id 1CPic2-0001oO-Mx; Thu, 04 Nov 2004 09:29:18 -0500 Content-Type: text/plain; charset=us-ascii MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: Len Sorensen [EMAIL PROTECTED] To: Debian Bug Tracking System [EMAIL PROTECTED] Subject: kernel-image-2.6.8-1-k7: Runs out of network buffers X-Mailer: reportbug 3.1 Date: Thu, 04 Nov 2004 09:29:18 -0500 Message-Id: [EMAIL PROTECTED] Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2004_03_25 X-Spam-Level: Package: kernel-image-2.6.8-1-k7 Version: 2.6.8-4 Severity: important For the last week or so, I have had to reboot my machine to get network access back. After a couple of days of doing the usually work (webbrowsing, bittornado, email, irssi, and such) it stops being able to establish network connections. It also shows an enourmous amount of memory in use, even though nothing in top or ps has any indication of using that memory. Basically about 250M of ram seems to have just disappeared somewhere. The kernel outputs this whenever I try to do something on the network: kernel: dst cache overflow While trying to run links or other programs with network connections get: connect: No buffer space available I have never seen this under 2.6.7 or earlier, and I am not sure if it started happening after going to 2.6.8, or just after the latest 2.6.8 update (although I believe it was only after the latest update or two). I hope there is some explanation for this behavior in the current kernel, since the machine load is the same as was working fine under prior kernels, and I would hate to see this behaviour in the kernel that would ship with sarge. Any suggestions for things to make note of or log the next time it happens (It probably will), I would be happy to try out. Note: I am running with a set of drivers added to run a Sangoma ADSL PCI card (www.sangoma.com) although I have been using those for a while with no problems. I may try removing them to see if they are part of the problem or not. -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.8-1-k7 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages kernel-image-2.6.8-1-k7 depends on: ii coreutils [fileutils] 5.2.1-2The GNU core utilities ii fileutils 5.2.1-2The GNU file management utilities ii initrd-tools 0.1.74 tools to create initrd image for p ii module-init-tools 3.1-pre6-1 tools for managing Linux kernel mo -- no debconf information --- Received: (at 279666-done) by bugs.debian.org; 13 Dec 2004 07:37:05 + From [EMAIL PROTECTED] Sun Dec 12 23:37:05 2004 Return-path: [EMAIL PROTECTED] Received: from koto.vergenet.net [210.128.90.7] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1CdklU-0005dX-00; Sun, 12 Dec 2004 23:37:04 -0800 Received: by koto.vergenet.net (Postfix, from userid 7100) id 34385345AD; Mon, 13 Dec 2004 16:20:24 +0900 (JST) Date: Mon, 13 Dec 2004 16:36:51 +0900 From: Horms [EMAIL PROTECTED] To: Lennart Sorensen [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: Bug#279666: kernel-image-2.6.8-1-k7: Runs out of network buffers Message-ID: [EMAIL PROTECTED] References: [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: [EMAIL PROTECTED] X-Cluestick: seven User-Agent: Mutt/1.5.6+20040907i Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin
Bug#284567: Unable to handle kernel paging request
Horms wrote: Did any of these discussions included (proposed) patches or fixes? If so do you have any links handy? So far there have been no discussions. There was a somewhat similar problem reported years ago, which I don't think was fully investigated: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=172250archive=yes Is it possible to run this through ksymoops? I am afraid not anymore (because of my own stupidity, no less). I will run it as soon as I reproduce the problem. So far in a week it hasn't happened again. -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.4.27-1-386 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Did this kernel come from kernel-image-2.4.27-1-386 and if so which version? And if it is not the latest (-6) could you try that? It is kernel-image-2.4.27-1-386_2.4.27-2_i386.deb Since I haven't reproduced it yet, I will probably wait a couple of more days without rebooting and see if it happens with -2. Then I will try -6. I will post more info if I get it with either version. (BTW, for this purpose should I be running the generic 386 or the 686 kernel ?) regards, Tzvetan
Re: Bug#281439: xserver-xfree86: lockup with linux 2.6.9 using mplayer
reassign 281439 kernel-source-2.6.9 retitle 281439 kernel: 2.6.9 has a regression from 2.6.8.1 in the i830 DRM module thanks On Fri, Dec 10, 2004 at 01:21:23PM -0500, Branden Robinson wrote: retitle 281439 kernel: 2.6.9 has a regression from 2.6.8.1 in the i830 DRM module reassign 281439 kernel thanks On Mon, Nov 15, 2004 at 10:04:22PM +0100, Marton Illes wrote: Package: xserver-xfree86 Version: 4.3.0.dfsg.1-8 Severity: important Using linux 2.6.9 with mplayer_1.0cvs the X server locks up, and refuses to restart. A reboot helps. It works like a charm with 2.6.8.1. Could be a bit more specific so we can isolate the offending (upstream) patch more easily? The error says: Error in I830WaitLpRing(), now is 6205, start is 4204 pgetbl_ctl: 0x2ffe0001 pgetbl_err: 0x0 ipeir: 0 iphdr: 181 LP ring tail: 6770 head: 0 len: 1f001 start 0 eir: 0 esr: 0 emr: instdone: ffc0 instpm: 0 memmode: 108 instps: 0 hwstam: ier: 0 imr: iir: 0 space: 104584 wanted 131064 FatalError re-entered, aborting lockup This sounds like a regression in the Linux kernel. Reassigning. -- Horms
Processed: Re: Bug#281439: xserver-xfree86: lockup with linux 2.6.9 using mplayer
Processing commands for [EMAIL PROTECTED]: reassign 281439 kernel-source-2.6.9 Bug#281439: xserver-xfree86: lockup with linux 2.6.9 using mplayer Bug reassigned from package `xserver-xfree86' to `kernel-source-2.6.9'. retitle 281439 kernel: 2.6.9 has a regression from 2.6.8.1 in the i830 DRM module Bug#281439: xserver-xfree86: lockup with linux 2.6.9 using mplayer Changed Bug title. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Processed: Re: Bug#285301: initrd-tools: typo in mkinitrd
Processing commands for [EMAIL PROTECTED]: tag 285301 +pending Bug#285301: initrd-tools: typo in mkinitrd There were no tags set. Tags added: pending thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Bug#283115: marked as done (kernel oops ins xfs_acl_get_attr with kernel-image-2.4.27-1-686-smp)
Your message dated Mon, 13 Dec 2004 17:58:44 +0900 with message-id [EMAIL PROTECTED] and subject line Bug#283115: kernel oops ins xfs_acl_get_attr with kernel-image-2.4.27-1-686-smp 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) -- Received: (at submit) by bugs.debian.org; 26 Nov 2004 16:13:19 + From [EMAIL PROTECTED] Fri Nov 26 08:13:18 2004 Return-path: [EMAIL PROTECTED] Received: from iterfw.rzg.mpg.de (virusw1.dmz.itereu.de) [130.183.3.2] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1CXiik-0001US-00; Fri, 26 Nov 2004 08:13:18 -0800 Received: from merlin (virusw1 [127.0.0.1]) by virusw1.dmz.itereu.de (8.11.6/8.11.6) with ESMTP id iAQAATf27308 for [EMAIL PROTECTED]; Fri, 26 Nov 2004 11:10:29 +0100 Received: from [194.59.170.134] (pcbecks.itereu.de [:::194.59.170.134]) (AUTH: PLAIN becks, SSL: TLSv1/SSLv3,256bits,AES256-SHA) by merlin with esmtp; Fri, 26 Nov 2004 11:10:29 +0100 id F5CC.41A70115.6075 Message-ID: [EMAIL PROTECTED] Date: Fri, 26 Nov 2004 11:10:29 +0100 From: Stefan Beck [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20041007 Debian/1.7.3-5 X-Accept-Language: en MIME-Version: 1.0 To: [EMAIL PROTECTED] Subject: kernel oops ins xfs_acl_get_attr with kernel-image-2.4.27-1-686-smp Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2004_03_25 X-Spam-Level: Package: kernel-image-2.4.27-1-686-smp Version: 2.4.27-2 Severity: important Hello, after somedays of uptime on our fileserver (nfs,samba,netatalk) we get an kerneloops (see below). After rebooting, we have to repair the xfs filesystem to get rid of the oops. We had that problem with previous kernels 2.4.2[456]-1-686-smp, too. thank you Stefan ksymoops 2.4.9 on i686 2.4.27-1-686-smp. Options used -V (default) -k /proc/ksyms (default) -l /proc/modules (default) -o /lib/modules/2.4.27-1-686-smp/ (default) -m /boot/System.map-2.4.27-1-686-smp (default) Warning: You did not tell me where to find symbol information. I will assume that the log matches the kernel and modules that are running right now and I'll use the default options above for symbol resolution. If the current kernel and/or modules do not match the log, you can get more accurate output by telling me the kernel version and where to find map, modules, ksyms etc. ksymoops -h explains the options. Warning (expand_objects): object /lib/modules/2.4.27-1-686-smp/kernel/fs/ext3/ext3.o for module ext3 has changed since load Warning (expand_objects): object /lib/modules/2.4.27-1-686-smp/kernel/fs/jbd/jbd.o for module jbd has changed since load Warning (expand_objects): object /lib/modules/2.4.27-1-686-smp/kernel/drivers/scsi/sd_mod.o for module sd_mod has changed si nce load Warning (expand_objects): object /lib/modules/2.4.27-1-686-smp/kernel/drivers/scsi/aic7xxx/aic79xx.o for module aic79xx has changed since load Warning (expand_objects): object /lib/modules/2.4.27-1-686-smp/kernel/drivers/scsi/scsi_mod.o for module scsi_mod has change d since load Warning (expand_objects): object /lib/modules/2.4.27-1-686-smp/kernel/net/unix/unix.o for module unix has changed since load 1Unable to handle kernel NULL pointer dereference at virtual address 0008 e1a20d39 *pde = Oops: CPU:1 EIP:0010:[e1a20d39]Not tainted Using defaults from ksymoops -t elf32-i386 -a i386 EFLAGS: 00010246 eax: e1aa3070 ebx: 2000 ecx: edx: e1a98d1c esi: 2002 edi: ebp: d4bc8060 esp: d4ff3d58 ds: 0018 es: 0018 ss: 0018 Process ls (pid: 28666, stackpage=d4ff3000) Stack: d89a5a60 da2c7c00 e1aa2b20 c015f014 d89a5a8c c027cda0 0130 2000 2100 e1a20334 d4bc8060 0001 2000 d4ff3d98 003d 0669fbf8 d4ff3e30 d6bad8d0 Call Trace:[e1aa2b20] [c015f014] [e1a20334] [e1aa1ee0] [e1a2ae76] [e1aa1f40] [e1a87c03] [c01640db] [c012c6b3] [e1a60d88] [e1a5bd3e] [e1a7b48f] [c015bbc1] [c0151fac] [c01527ec] [c01641d7] [c0108f67] Code: 8b 59 08 89 44 24 14 8d 44 24 18 89 44 24 0c
Bug#283115: kernel oops ins xfs_acl_get_attr with kernel-image-2.4.27-1-686-smp
Horms wrote: On Mon, Nov 29, 2004 at 08:48:09PM +0100, Stefan Beck wrote: Horms wrote: On Fri, Nov 26, 2004 at 11:10:29AM +0100, Stefan Beck wrote: Package: kernel-image-2.4.27-1-686-smp Version: 2.4.27-2 Severity: important Does this kernel exhibit the same behaviour? http://debian.vergenet.net/pending/kernel-image-2.4.27-i386-2.4.27/ Unfortunately I can't test this before friday 2004/12/03, since this will take some downtime. I'll let you know on saturday. Thanks, I am actually going to be on holidays next week, so I will probably upload the new images to Debian.Org before that. In any case, please let me know how you go. After increasing swapspace (which caused other problems) everything seems to run perfectly stable so far. Thanks. regards Stefan
Bug#283919: initrd-tools: Should warn if root device is not found
On Monday 13 of December 2004 03:34, Horms wrote: On Thu, Dec 02, 2004 at 11:11:42AM +0100, Piotr Roszatycki wrote: Package: initrd-tools Version: 0.1.74 Severity: wishlist I'd like to see some warning, if /proc/sys/kernel/real-root-dev is equal 0. That means no root device was found and the message would be very helpful. I've spend an hour trying to reboot the kernel 2.6 with root=/dev/ida/c0d0p2 parameter. I didn't know the kernel doesn't understand such parameter and I've found the real reason by my own inspection in initrd's mini-shell. That sounds reasonable, though I am not sure where you would want the warning to go. Perhaps a patch would help illustrate the idea. My proposition: --- init.orig 2004-08-27 20:43:34 +0200 +++ init2004-12-13 10:19:29 +0100 @@ -412,7 +412,10 @@ rootdev=$(cat proc/sys/kernel/real-root-dev) cmdline=$(cat /proc/cmdline) umount -n proc -if [ $rootdev != 256 ]; then +if [ $rootdev = 0 ]; then +echo Kernel can not convert a name into device number. Check the 'root=' argument +fi +if [ $rootdev != 256 ] [ $rootdev != 0 ]; then mount_root cd mnt [ $DEVFS ] mount -nt devfs devfs dev -- .''`.Piotr Roszatycki, Netia SA : :' :mailto:[EMAIL PROTECTED] `. `' mailto:[EMAIL PROTECTED] `-
Bug#284567: Unable to handle kernel paging request
On Mon, Dec 13, 2004 at 12:23:58AM -0800, Tzvetan Mikov wrote: Horms wrote: Did any of these discussions included (proposed) patches or fixes? If so do you have any links handy? So far there have been no discussions. There was a somewhat similar problem reported years ago, which I don't think was fully investigated: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=172250archive=yes Is it possible to run this through ksymoops? I am afraid not anymore (because of my own stupidity, no less). I will run it as soon as I reproduce the problem. So far in a week it hasn't happened again. -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.4.27-1-386 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Did this kernel come from kernel-image-2.4.27-1-386 and if so which version? And if it is not the latest (-6) could you try that? It is kernel-image-2.4.27-1-386_2.4.27-2_i386.deb Since I haven't reproduced it yet, I will probably wait a couple of more days without rebooting and see if it happens with -2. Then I will try -6. I will post more info if I get it with either version. (BTW, for this purpose should I be running the generic 386 or the 686 kernel ?) Whichever you were using when you saw the problem initially. That is assuming you aren't doing something silly like trying to run a 686 kernel on a 486. -- Horms
Bug#285301: initrd-tools: typo in mkinitrd
tag 285301 +pending thanks On Sun, Dec 12, 2004 at 01:12:02PM +0100, Harald Dunkel wrote: Package: initrd-tools Version: 0.1.75 See attached patch. Harri Thanks, Josh Kwan has added this to SVN and it should appear in the next release. -- Horms
Bug#278887: initrd-tools: Caused by megaraid2 module using /proc/scsi/megaraid
On Mon, Dec 13, 2004 at 06:38:57AM +0100, Harald Dunkel wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Philipp Niemann wrote: | | In the script /usr/sbin/mkinitrd, Line 497, is a find which seems to | search /proc/scsi for modules needed to mount the root device. If one | has the megaraid2 module loaded, there will be a directory called | megaraid in /proc/scsi. | Do you get the same misnamed module directory in /proc/scsi for kernel 2.6.x? There's no megaraid2 driver in 2.6. Megaraid 2.0.x is megaraid.ko, the newer 2.2.x driver is split into two modules, megaraid_mbox.ko and megaraid_mm.ko. In any case mkinitrd shouldn't rely on /proc/scsi at all.
Bug#283133: Please close - problem resolved
I am sorry. As it turns out, this is now resolved, and I suspect that eth1394 never was the culprit. I am not sure what was the real fix. I am tracking debian sid, and updates to discover (I think) made the problem go away. So you may close this report (I would have done it myself if I had known how). I am happy to say that the issue is gone. -- Håvard Dahle
Re: Bug#283133: Please close - problem resolved
On Mon, Dec 13, 2004 at 03:04:34PM +, Håvard Dahle wrote: I am sorry. As it turns out, this is now resolved, and I suspect that eth1394 never was the culprit. I am not sure what was the real fix. I am tracking debian sid, and updates to discover (I think) made the problem go away. So you may close this report (I would have done it myself if I had known how). I am happy to say that the issue is gone. You can close bugs yourself by sending mail to NN-done, as I'm doing with this mail. Thanks. -- Next the statesmen will invent cheap lies, putting the blame upon the nation that is attacked, and every man will be glad of those conscience-soothing falsities, and will diligently study them, and refuse to examine any refutations of them; and thus he will by and by convince himself that the war is just, and will thank God for the better sleep he enjoys after this process of grotesque self-deception. -- Mark Twain
Bug#283133: marked as done (kernel-image-2.6.9-1-k7: kernel oops on module eth1394 on nVidia nForce chipset)
Your message dated Mon, 13 Dec 2004 14:48:30 + with message-id [EMAIL PROTECTED] and subject line Bug#283133: Please close - problem resolved 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) -- Received: (at submit) by bugs.debian.org; 26 Nov 2004 18:55:56 + From [EMAIL PROTECTED] Fri Nov 26 10:55:55 2004 Return-path: [EMAIL PROTECTED] Received: from mail.broadpark.no [217.13.4.2] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1CXlG7-0004xj-00; Fri, 26 Nov 2004 10:55:55 -0800 Received: from [127.0.0.1] (179.80-202-92.nextgentel.com [80.202.92.179]) by mail.broadpark.no (Postfix) with ESMTP id 006AB1B91; Fri, 26 Nov 2004 19:55:22 +0100 (MET) Content-Type: multipart/mixed; boundary1843605238== MIME-Version: 1.0 From: =?iso-8859-15?q?H=C3=A5vard_Dahle?= [EMAIL PROTECTED] To: Debian Bug Tracking System [EMAIL PROTECTED] Subject: kernel-image-2.6.9-1-k7: kernel oops on module eth1394 on nVidia nForce chipset X-Mailer: reportbug 3.2 Date: Fri, 26 Nov 2004 19:56:20 + Message-Id: [EMAIL PROTECTED] Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2004_03_25 X-Spam-Level: This is a multi-part MIME message sent by reportbug. --===1843605238== Content-Type: text/plain; charset=us-ascii MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Package: kernel-image-2.6.9-1-k7 Version: 2.6.9-3 Severity: critical Justification: breaks the whole system Problem: After installing hotplug, the eth1394 is automatically loaded at boot time. This makes the kernel oops. Solution: Add eth1394 to /etc/hotplug/blacklist Since I cannot capture the output, I am not including it with this report. But, if it may help, I will certainly write it down and submit it. I am attaching the output of lspci -v, hoping that at least that may prove useful. -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.9-1-k7 Locale: LANG=no_NO, LC_CTYPE=no_NO (charmap=ISO-8859-15) (ignored: LC_ALL set to en_US.ISO-8859-15) Versions of packages kernel-image-2.6.9-1-k7 depends on: ii coreutils [fileutils] 5.2.1-2The GNU core utilities ii initrd-tools 0.1.74 tools to create initrd image for p ii module-init-tools 3.1-rel-2 tools for managing Linux kernel mo -- no debconf information --===1843605238== Content-Type: text/plain; charset=us-ascii MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=lspci :00:00.0 Host bridge: nVidia Corporation nForce2 AGP (different version?) (rev a2) Flags: bus master, 66MHz, fast devsel, latency 0 Memory at d000 (32-bit, prefetchable) [size=64M] Capabilities: [40] AGP version 2.0 Capabilities: [60] #08 [2001] :00:00.1 RAM memory: nVidia Corporation nForce2 Memory Controller 1 (rev a2) Subsystem: Micro-Star International Co., Ltd.: Unknown device 7960 Flags: 66MHz, fast devsel :00:00.2 RAM memory: nVidia Corporation nForce2 Memory Controller 4 (rev a2) Subsystem: Micro-Star International Co., Ltd.: Unknown device 7960 Flags: 66MHz, fast devsel :00:00.3 RAM memory: nVidia Corporation nForce2 Memory Controller 3 (rev a2) Subsystem: Micro-Star International Co., Ltd.: Unknown device 7960 Flags: 66MHz, fast devsel :00:00.4 RAM memory: nVidia Corporation nForce2 Memory Controller 2 (rev a2) Subsystem: Micro-Star International Co., Ltd.: Unknown device 7960 Flags: 66MHz, fast devsel :00:00.5 RAM memory: nVidia Corporation nForce2 Memory Controller 5 (rev a2) Subsystem: Micro-Star International Co., Ltd.: Unknown device 7960 Flags: 66MHz, fast devsel :00:01.0 ISA bridge: nVidia Corporation nForce2 ISA Bridge (rev a4) Subsystem: Micro-Star International Co., Ltd.: Unknown device 7960 Flags: bus master, 66MHz, fast devsel, latency 0 Capabilities: [48] #08 [01e1] :00:01.1 SMBus: nVidia Corporation nForce2 SMBus (MCP) (rev a2) Subsystem: Micro-Star International Co., Ltd.: Unknown device 7960 Flags: 66MHz, fast devsel, IRQ 169
Bug#284356: New release changed symbols thus rendering modules unloadable
On Mon, 13 Dec 2004 21:46:56 +0900, Horms wrote: [...] Hi, I think that I have discovered the cause of the problem. It seems to be caused by the 093_tty_lockup.diff patch which was applied to resolve CAN-2004-081, a security bug relating to race conditions in the TTY subsystem. The patch was sourced from Jason Baron from Red Hat. I have attached it for reference. In testing I found that the problem lies in the following change in include/linux/tty.h -extern struct tty_ldisc ldiscs[]; +extern struct tty_ldisc tty_ldiscs[]; Backing out this change then runing something along the lines of make mrproper cp some_path/some_config .config make oldconfig make dep yields the same symbols. (This test was done using the 686-smp config from kernel-image-i386-2.4.27 -6 and examining the proc_mkdir symbol which is found in include/linux/modules/root.ver) Of course this does not compile because my change is bogus, but I think it does establish the cause of the symbol problem. I believe that there are serveral different fixes for this problem, and in particular the one that was incoporated in 2.6 is somewhat different
Bug#284221: acenic firmware situation summary
The current owner of alteon is nortel. http://web.archive.org/web/20040117112911/www.alteonwebsystems.com/ascii/
Re: acenic firmware situation summary
On Mon, Dec 13, 2004 at 12:15:57PM -0500, Christopher Priest wrote: Is this helpful http://web.archive.org/web/2711071330/sanjose.alteon.com/license-agree.shtml This license doesn't let us distribute the software. This is pretty clearly stated in the first two sentences of the first two numbered paragraphs. And, the third numbered paragraph makes it clear that if we have ever distributed the software we're not allowed to even use it under this license. -- Raul
Re: Bug#284116: kernel-image-* should include vmlinux
On Mon, Dec 13, 2004 at 12:11:47PM +0900, Horms wrote: reassign 284116 kernel-package Package kernel-package already has an option to include vmlinux in the images (install_vmlinux, which fixed Bug#243927), so I still think the problem is in the kernel-image packages... Could you be a little more explicit about what sort of debugging you are refering to? Being able to inspect the kernel variables and the kernel content with: # gdb /boot/vmlinux /proc/kcore Thanks, -- .+'''+. .+'''+. .+'''+. .+'''+. .+'' Juan Cespedes / \ / \ [EMAIL PROTECTED] .+' `+...+' `+...+' `+...+' `+...+'
Re: status of getting security fixes into sarge
[Cc'ing debian-kernel for clarification] Joey Hess wrote: Here are the ones the testing security team is currently tracking that are fixed in unstable but don't yet have a fix in sarge, plus a few others of interest: It seems as if the local DoS in the a.out loader (only exploitable when VM memory overcommitment is turned on) is still unfixed in kernel-source- 2.6.8: The changelog for 2.6.8-9 mentions another unrelated elf/a.out vulnarability, but I can't find the proposed patch by Chris Wright in the diff.gz, so maybe this has slipped through until now or fixed in a different way, I don't know: http://marc.theaimsgroup.com/?l=linux-kernelm=110023019006886w=2 Cheers, Moritz
kernel-patch-powerpc-2.6.9_2.6.9-2_powerpc.changes UNACCEPT
Rejected: Rejected: kernel-image-power3-smp_2.6.9-2_powerpc.deb: old version (100) in unstable = new version (2.6.9-2) targeted at unstable. Rejected: Rejected: kernel-patch-powerpc-2.6.9_2.6.9-2_all.deb: old version (2.6.9-3) in unstable = new version (2.6.9-2) targeted at unstable. Rejected: Rejected: kernel-patch-powerpc-2.6.9_2.6.9-2.dsc: old version (2.6.9-3) in unstable = new version (2.6.9-2) targeted at unstable. Rejected: Rejected: kernel-build-2.6.9-powerpc-smp_2.6.9-2_powerpc.deb: old version (2.6.9-3) in unstable = new version (2.6.9-2) targeted at unstable. Rejected: Rejected: kernel-build-2.6.9-power3-smp_2.6.9-2_powerpc.deb: old version (2.6.9-3) in unstable = new version (2.6.9-2) targeted at unstable. Rejected: Rejected: kernel-build-2.6.9-power3_2.6.9-2_powerpc.deb: old version (2.6.9-3) in unstable = new version (2.6.9-2) targeted at unstable. Rejected: Rejected: kernel-image-power3_2.6.9-2_powerpc.deb: old version (100) in unstable = new version (2.6.9-2) targeted at unstable. Rejected: Rejected: kernel-image-2.6.9-powerpc_2.6.9-2_powerpc.deb: old version (2.6.9-3) in unstable = new version (2.6.9-2) targeted at unstable. Rejected: Rejected: kernel-image-2.6.9-power3-smp_2.6.9-2_powerpc.deb: old version (2.6.9-3) in unstable = new version (2.6.9-2) targeted at unstable. Rejected: Rejected: kernel-image-powerpc_2.6.9-2_powerpc.deb: old version (100) in unstable = new version (2.6.9-2) targeted at unstable. Rejected: Rejected: kernel-image-2.6.9-power3_2.6.9-2_powerpc.deb: old version (2.6.9-3) in unstable = new version (2.6.9-2) targeted at unstable. Rejected: Rejected: kernel-image-power4-smp_2.6.9-2_powerpc.deb: old version (100) in unstable = new version (2.6.9-2) targeted at unstable. Rejected: Rejected: kernel-build-2.6.9-powerpc_2.6.9-2_powerpc.deb: old version (2.6.9-3) in unstable = new version (2.6.9-2) targeted at unstable. Rejected: Rejected: kernel-image-2.6.9-power4_2.6.9-2_powerpc.deb: old version (2.6.9-3) in unstable = new version (2.6.9-2) targeted at unstable. Rejected: Rejected: kernel-image-2.6.9-powerpc-smp_2.6.9-2_powerpc.deb: old version (2.6.9-3) in unstable = new version (2.6.9-2) targeted at unstable. Rejected: Rejected: kernel-image-power4_2.6.9-2_powerpc.deb: old version (100) in unstable = new version (2.6.9-2) targeted at unstable. Rejected: Rejected: kernel-build-2.6.9-power4_2.6.9-2_powerpc.deb: old version (2.6.9-3) in unstable = new version (2.6.9-2) targeted at unstable. Rejected: Rejected: kernel-build-2.6.9-power4-smp_2.6.9-2_powerpc.deb: old version (2.6.9-3) in unstable = new version (2.6.9-2) targeted at unstable. Rejected: Rejected: kernel-image-2.6.9-power4-smp_2.6.9-2_powerpc.deb: old version (2.6.9-3) in unstable = new version (2.6.9-2) targeted at unstable. Rejected: Rejected: kernel-image-powerpc-smp_2.6.9-2_powerpc.deb: old version (100) in unstable = new version (2.6.9-2) targeted at unstable. Rejected: Rejected: kernel-headers-2.6.9_2.6.9-2_powerpc.deb: old version (2.6.9-3) in unstable = new version (2.6.9-2) targeted at unstable. === Despite being ACCEPTed, this package failed the database sanity checks at the time of install. This should only happen rarely and in corner-cases (a binary upload of a package which has since been melanie'd for example), so no code to do the necessary unaccept actions has been written. These actions (e.g. bug reopening, announcement rescinding, etc.) will have to be done by hand. Also, the files have been left in the accepted directory; please deal with them as well.
Re: kernel-patch-powerpc-2.6.9_2.6.9-2_powerpc.changes UNACCEPT
On Mon, Dec 13, 2004 at 02:53:02PM -0500, Debian Installer wrote: Rejected: Rejected: kernel-image-power3-smp_2.6.9-2_powerpc.deb: old version (100) in unstable = new version (2.6.9-2) targeted at unstable. Rejected: Rejected: kernel-patch-powerpc-2.6.9_2.6.9-2_all.deb: old version (2.6.9-3) in unstable = new version (2.6.9-2) targeted at unstable. Rejected: Rejected: kernel-patch-powerpc-2.6.9_2.6.9-2.dsc: old version (2.6.9-3) in unstable = new version (2.6.9-2) targeted at unstable. Rejected: Rejected: kernel-build-2.6.9-powerpc-smp_2.6.9-2_powerpc.deb: old version (2.6.9-3) in unstable = new version (2.6.9-2) targeted at unstable. Rejected: Rejected: kernel-build-2.6.9-power3-smp_2.6.9-2_powerpc.deb: old version (2.6.9-3) in unstable = new version (2.6.9-2) targeted at unstable. Rejected: Rejected: kernel-build-2.6.9-power3_2.6.9-2_powerpc.deb: old version (2.6.9-3) in unstable = new version (2.6.9-2) targeted at unstable. Rejected: Rejected: kernel-image-power3_2.6.9-2_powerpc.deb: old version (100) in unstable = new version (2.6.9-2) targeted at unstable. Rejected: Rejected: kernel-image-2.6.9-powerpc_2.6.9-2_powerpc.deb: old version (2.6.9-3) in unstable = new version (2.6.9-2) targeted at unstable. Rejected: Rejected: kernel-image-2.6.9-power3-smp_2.6.9-2_powerpc.deb: old version (2.6.9-3) in unstable = new version (2.6.9-2) targeted at unstable. Rejected: Rejected: kernel-image-powerpc_2.6.9-2_powerpc.deb: old version (100) in unstable = new version (2.6.9-2) targeted at unstable. Rejected: Rejected: kernel-image-2.6.9-power3_2.6.9-2_powerpc.deb: old version (2.6.9-3) in unstable = new version (2.6.9-2) targeted at unstable. Rejected: Rejected: kernel-image-power4-smp_2.6.9-2_powerpc.deb: old version (100) in unstable = new version (2.6.9-2) targeted at unstable. Rejected: Rejected: kernel-build-2.6.9-powerpc_2.6.9-2_powerpc.deb: old version (2.6.9-3) in unstable = new version (2.6.9-2) targeted at unstable. Rejected: Rejected: kernel-image-2.6.9-power4_2.6.9-2_powerpc.deb: old version (2.6.9-3) in unstable = new version (2.6.9-2) targeted at unstable. Rejected: Rejected: kernel-image-2.6.9-powerpc-smp_2.6.9-2_powerpc.deb: old version (2.6.9-3) in unstable = new version (2.6.9-2) targeted at unstable. Rejected: Rejected: kernel-image-power4_2.6.9-2_powerpc.deb: old version (100) in unstable = new version (2.6.9-2) targeted at unstable. Rejected: Rejected: kernel-build-2.6.9-power4_2.6.9-2_powerpc.deb: old version (2.6.9-3) in unstable = new version (2.6.9-2) targeted at unstable. Rejected: Rejected: kernel-build-2.6.9-power4-smp_2.6.9-2_powerpc.deb: old version (2.6.9-3) in unstable = new version (2.6.9-2) targeted at unstable. Rejected: Rejected: kernel-image-2.6.9-power4-smp_2.6.9-2_powerpc.deb: old version (2.6.9-3) in unstable = new version (2.6.9-2) targeted at unstable. Rejected: Rejected: kernel-image-powerpc-smp_2.6.9-2_powerpc.deb: old version (100) in unstable = new version (2.6.9-2) targeted at unstable. Rejected: Rejected: kernel-headers-2.6.9_2.6.9-2_powerpc.deb: old version (2.6.9-3) in unstable = new version (2.6.9-2) targeted at unstable. === Despite being ACCEPTed, this package failed the database sanity checks at the time of install. This should only happen rarely and in corner-cases (a binary upload of a package which has since been melanie'd for example), so no code to do the necessary unaccept actions has been written. These actions (e.g. bug reopening, announcement rescinding, etc.) will have to be done by hand. Also, the files have been left in the accepted directory; please deal with them as well. Well, 2.6.9-3 is now in the archive and fixes this, so i suppose that some ftp-master needs to look at the incoming queue and remove those files. Friendly, Sven Luther
Bug#285521: kernel-image-2.4.27-1: kernel-image-2.4.27-1 v6: thinkpad does not suspend upon lid closing
Package: kernel-image-2.4.27-1-686 Version: 2.4.27-6 Severity: normal File: kernel-image-2.4.27-1 APM does not see or react upon closing the lid of my IBM thinkpad X22 Version 2.4.27-2, and earlier kernels are fine. With v2, closing the lid shows Dec 13 21:46:25 oliebij apmd[1064]: Suspending now in the log. Nothing appears with 2.4.27-6. -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.4.27-1-686 Locale: LANG=nl_NL, LC_CTYPE=nl_NL (charmap=ISO-8859-1) Versions of packages kernel-image-2.4.27-1-686 depends on: ii coreutils [fileutils] 5.2.1-2The GNU core utilities ii fileutils 5.2.1-2The GNU file management utilities ii initrd-tools 0.1.75 tools to create initrd image for p ii modutils 2.4.27-0.1 Linux module utilities -- no debconf information
Bug#284015: kernel-image-2.6.9-1-686: DMA timeout error
On Mon, 13 Dec 2004 12:00:05 +0900, Horms [EMAIL PROTECTED] wrote: when I see errors like that it is usually just before I have to go to the store and get a new hard drive because the old one has failed. Are you seeing the same problem with other kernel's too? Hey, I get the same errors with 2.6.8 although I'd be more inclined to think it was a defective hard drive except it's a brand new laptop and smartmontools seems to be happy with it. Maybe the problem is the fact it's so new, I'm no expert by any means but could the failed opcode was: unknown message indicate this?
