Bug#445611: conflicting types for 'mode_t'
Package: libc6-dev, linux-libc-dev Severity: important Hi, When building proftpd-dfsg on amd64 I get the following error: In file included from /usr/include/asm/types.h:5, from /usr/include/asm-x86_64/sigcontext.h:4, from /usr/include/asm/sigcontext.h:5, from /usr/include/bits/sigcontext.h:28, from /usr/include/signal.h:333, from /usr/include/sys/wait.h:31, from ../include/conf.h:95, from pr_fnmatch.c:38: /usr/include/asm-x86_64/types.h:6: error: conflicting types for 'mode_t' /usr/include/sys/types.h:72: error: previous declaration of 'mode_t' was here Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#445615: linux-image-2.6.22-2-686: package broke my grub menu.lst file
Package: linux-image-2.6.22-2-686 Version: 2.6.22-4 Severity: grave Justification: renders package unusable I had a custom built kernel (2.6.20.10). This was the conf in the menu.lst file: title Debian GNU/Linux, kernel 2.6.20.10 root(hd0,1) kernel /boot/vmlinuz-2.6.20.10 root=/dev/hda2 ro savedefault After installing the stock kernel (linux-image-2.6.22-2-686) this configuration was changed to: title Debian GNU/Linux, kernel 2.6.20.10 root(hd0,2) kernel /boot/vmlinuz-2.6.20.10 root=/dev/hda3 ro savedefault And of course the system could not boot since it is installed in the second partition (/dev/hda2). The configuration which the stock kernel package generated for it self was also wrong (it pointed to /dev/hda3, instead of the correct /dev/hda2). So, I had to manually edit /boot/grub/menu.lst in order to change all (hd0,2) back to (hd0,1) and all hda3 back to hda2. I can't really guess why it thought that the system is installed on /dev/hda3... -- Package-specific info: ** Version: Linux version 2.6.22-2-686 (Debian 2.6.22-4) ([EMAIL PROTECTED]) (gcc version 4.1.3 20070812 (prerelease) (Debian 4.1.2-15)) #1 SMP Fri Aug 31 00:24:01 UTC 2007 ** Tainted: PFSRMB ** Kernel log: nsc-ircc, Found chip at base=0x02e nsc-ircc, Wrong chip version ff nsc-ircc, Found chip at base=0x02e nsc-ircc, Wrong chip version ff nsc-ircc, chip-init nsc-ircc, Found chip at base=0x02e nsc-ircc, Wrong chip version ff nsc-ircc, Found chip at base=0x02e nsc-ircc, Wrong chip version ff pnp: Device 00:08 disabled. intel_rng: FWH not detected Adding 586332k swap on /dev/hda5. Priority:-1 extents:1 across:586332k EXT3 FS on hda2, internal journal loop: module loaded device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised: [EMAIL PROTECTED] fuse init (API version 7.8) NTFS driver 2.1.28 [Flags: R/W MODULE]. NTFS volume version 3.1. kjournald starting. Commit interval 5 seconds EXT3 FS on hda3, internal journal EXT3-fs: mounted filesystem with ordered data mode. NET: Registered protocol family 10 lo: Disabled Privacy Extensions ACPI: Battery Slot [BAT0] (battery present) ACPI: AC Adapter [ADP0] (on-line) input: Power Button (FF) as /class/input/input5 ACPI: Power Button (FF) [PWRF] input: Power Button (CM) as /class/input/input6 ACPI: Power Button (CM) [PWRB] input: Lid Switch as /class/input/input7 ACPI: Lid Switch [LID0] input: Sleep Button (CM) as /class/input/input8 ACPI: Sleep Button (CM) [SLPB] vmmon: module license 'unspecified' taints kernel. /dev/vmmon[3043]: Module vmmon: registered with major=10 minor=165 /dev/vmmon[3043]: Module vmmon: initialized /dev/vmnet: open called by PID 3076 (vmnet-bridge) /dev/vmnet: hub 0 does not exist, allocating memory. /dev/vmnet: port on hub 0 successfully opened bridge-eth2: peer interface eth2 not found, will wait for it to come up bridge-eth2: attached /dev/vmnet: open called by PID 3085 (vmnet-natd) /dev/vmnet: hub 8 does not exist, allocating memory. /dev/vmnet: port on hub 8 successfully opened /dev/vmnet: open called by PID 3086 (vmnet-netifup) /dev/vmnet: port on hub 8 successfully opened /dev/vmnet: open called by PID 3110 (vmnet-dhcpd) /dev/vmnet: port on hub 8 successfully opened [fglrx] Maximum main memory to use for locked dma buffers: 929 MBytes. [fglrx] USWC is disabled in module parameters [fglrx] PAT is disabled! [fglrx] module loaded - fglrx 8.40.4 [Jul 31 2007] on minor 0 ACPI: PCI Interrupt :01:00.0[A] - GSI 16 (level, low) - IRQ 16 [fglrx] total GART = 130023424 [fglrx] free GART = 114032640 [fglrx] max single GART = 114032640 [fglrx] total LFB = 134086656 [fglrx] free LFB = 84529152 [fglrx] max single LFB = 84529152 [fglrx] total Inv = 134217728 [fglrx] free Inv = 134217728 [fglrx] max single Inv = 134217728 [fglrx] total TIM = 0 vmnet8: no IPv6 routers present bridge-eth2: enabling the bridge bridge-eth2: up ieee80211_crypt: registered algorithm 'TKIP' bridge-eth2: disabling the bridge bridge-eth2: down bridge-eth2: enabling the bridge bridge-eth2: up tun: Universal TUN/TAP device driver, 1.6 tun: (C) 1999-2004 Max Krasnyansky [EMAIL PROTECTED] eth2: no IPv6 routers present usb 4-1: new high speed USB device using ehci_hcd and address 4 usb 4-1: configuration #1 chosen from 1 choice Initializing USB Mass Storage driver... scsi4 : SCSI emulation for USB Mass Storage devices usbcore: registered new interface driver usb-storage USB Mass Storage support registered. usb-storage: device found at 4 usb-storage: waiting for device to settle before scanning usb-storage: device scan complete scsi 4:0:0:0: Direct-Access WDC WD32 00JB-00KFA0 PQ: 0 ANSI: 0 sd 4:0:0:0: [sda] 625142448 512-byte hardware sectors (320073 MB) sd 4:0:0:0: [sda] Write Protect is off sd 4:0:0:0: [sda] Mode Sense: 27 00 00 00 sd 4:0:0:0: [sda] Assuming drive cache: write through sd 4:0:0:0: [sda] 625142448 512-byte hardware sectors (320073 MB) sd 4:0:0:0: [sda]
Bug#445615: marked as done (linux-image-2.6.22-2-686: package broke my grub menu.lst file)
Your message dated Sun, 7 Oct 2007 12:04:30 +0200 with message-id [EMAIL PROTECTED] and subject line Bug#445615: linux-image-2.6.22-2-686: package broke my grub menu.lst file 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-image-2.6.22-2-686 Version: 2.6.22-4 Severity: grave Justification: renders package unusable I had a custom built kernel (2.6.20.10). This was the conf in the menu.lst file: title Debian GNU/Linux, kernel 2.6.20.10 root(hd0,1) kernel /boot/vmlinuz-2.6.20.10 root=/dev/hda2 ro savedefault After installing the stock kernel (linux-image-2.6.22-2-686) this configuration was changed to: title Debian GNU/Linux, kernel 2.6.20.10 root(hd0,2) kernel /boot/vmlinuz-2.6.20.10 root=/dev/hda3 ro savedefault And of course the system could not boot since it is installed in the second partition (/dev/hda2). The configuration which the stock kernel package generated for it self was also wrong (it pointed to /dev/hda3, instead of the correct /dev/hda2). So, I had to manually edit /boot/grub/menu.lst in order to change all (hd0,2) back to (hd0,1) and all hda3 back to hda2. I can't really guess why it thought that the system is installed on /dev/hda3... -- Package-specific info: ** Version: Linux version 2.6.22-2-686 (Debian 2.6.22-4) ([EMAIL PROTECTED]) (gcc version 4.1.3 20070812 (prerelease) (Debian 4.1.2-15)) #1 SMP Fri Aug 31 00:24:01 UTC 2007 ** Tainted: PFSRMB ** Kernel log: nsc-ircc, Found chip at base=0x02e nsc-ircc, Wrong chip version ff nsc-ircc, Found chip at base=0x02e nsc-ircc, Wrong chip version ff nsc-ircc, chip-init nsc-ircc, Found chip at base=0x02e nsc-ircc, Wrong chip version ff nsc-ircc, Found chip at base=0x02e nsc-ircc, Wrong chip version ff pnp: Device 00:08 disabled. intel_rng: FWH not detected Adding 586332k swap on /dev/hda5. Priority:-1 extents:1 across:586332k EXT3 FS on hda2, internal journal loop: module loaded device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised: [EMAIL PROTECTED] fuse init (API version 7.8) NTFS driver 2.1.28 [Flags: R/W MODULE]. NTFS volume version 3.1. kjournald starting. Commit interval 5 seconds EXT3 FS on hda3, internal journal EXT3-fs: mounted filesystem with ordered data mode. NET: Registered protocol family 10 lo: Disabled Privacy Extensions ACPI: Battery Slot [BAT0] (battery present) ACPI: AC Adapter [ADP0] (on-line) input: Power Button (FF) as /class/input/input5 ACPI: Power Button (FF) [PWRF] input: Power Button (CM) as /class/input/input6 ACPI: Power Button (CM) [PWRB] input: Lid Switch as /class/input/input7 ACPI: Lid Switch [LID0] input: Sleep Button (CM) as /class/input/input8 ACPI: Sleep Button (CM) [SLPB] vmmon: module license 'unspecified' taints kernel. /dev/vmmon[3043]: Module vmmon: registered with major=10 minor=165 /dev/vmmon[3043]: Module vmmon: initialized /dev/vmnet: open called by PID 3076 (vmnet-bridge) /dev/vmnet: hub 0 does not exist, allocating memory. /dev/vmnet: port on hub 0 successfully opened bridge-eth2: peer interface eth2 not found, will wait for it to come up bridge-eth2: attached /dev/vmnet: open called by PID 3085 (vmnet-natd) /dev/vmnet: hub 8 does not exist, allocating memory. /dev/vmnet: port on hub 8 successfully opened /dev/vmnet: open called by PID 3086 (vmnet-netifup) /dev/vmnet: port on hub 8 successfully opened /dev/vmnet: open called by PID 3110 (vmnet-dhcpd) /dev/vmnet: port on hub 8 successfully opened [fglrx] Maximum main memory to use for locked dma buffers: 929 MBytes. [fglrx] USWC is disabled in module parameters [fglrx] PAT is disabled! [fglrx] module loaded - fglrx 8.40.4 [Jul 31 2007] on minor 0 ACPI: PCI Interrupt :01:00.0[A] - GSI 16 (level, low) - IRQ 16 [fglrx] total GART = 130023424 [fglrx] free GART = 114032640 [fglrx] max single GART = 114032640 [fglrx] total LFB = 134086656 [fglrx] free LFB = 84529152 [fglrx] max single LFB = 84529152 [fglrx] total Inv = 134217728 [fglrx] free Inv = 134217728 [fglrx] max single Inv = 134217728 [fglrx] total TIM = 0 vmnet8: no IPv6 routers present bridge-eth2: enabling the bridge bridge-eth2: up ieee80211_crypt: registered algorithm 'TKIP' bridge-eth2: disabling the bridge bridge-eth2: down bridge-eth2: enabling the bridge bridge-eth2: up tun: Universal TUN/TAP device driver, 1.6 tun: (C) 1999-2004 Max Krasnyansky [EMAIL PROTECTED] eth2: no IPv6 routers present usb 4-1: new high speed USB device using ehci_hcd and address 4 usb 4-1:
Bug#445611: conflicting types for 'mode_t'
On Sun, Oct 07, 2007 at 11:38:18AM +0200, Kurt Roeckx wrote: When building proftpd-dfsg on amd64 I get the following error: In file included from /usr/include/asm/types.h:5, from /usr/include/asm-x86_64/sigcontext.h:4, from /usr/include/asm/sigcontext.h:5, from /usr/include/bits/sigcontext.h:28, from /usr/include/signal.h:333, from /usr/include/sys/wait.h:31, from ../include/conf.h:95, from pr_fnmatch.c:38: /usr/include/asm-x86_64/types.h:6: error: conflicting types for 'mode_t' There is no mode_t defined in asm-x86_64/types.h. Bastian -- We have phasers, I vote we blast 'em! -- Bailey, The Corbomite Maneuver, stardate 1514.2
Bug#445611: conflicting types for 'mode_t'
On Sun, Oct 07, 2007 at 12:09:51PM +0200, Bastian Blank wrote: On Sun, Oct 07, 2007 at 11:38:18AM +0200, Kurt Roeckx wrote: When building proftpd-dfsg on amd64 I get the following error: In file included from /usr/include/asm/types.h:5, from /usr/include/asm-x86_64/sigcontext.h:4, from /usr/include/asm/sigcontext.h:5, from /usr/include/bits/sigcontext.h:28, from /usr/include/signal.h:333, from /usr/include/sys/wait.h:31, from ../include/conf.h:95, from pr_fnmatch.c:38: /usr/include/asm-x86_64/types.h:6: error: conflicting types for 'mode_t' There is no mode_t defined in asm-x86_64/types.h. Line 6 has umode_t on it: typedef unsigned short umode_t; While /usr/include/sys/types.h line 72 has: typedef __mode_t mode_t; proftpd's configure.in has: AC_CHECK_TYPE(umode_t, mode_t) And config.h.in has: /* Define to `mode_t' if sys/types.h doesn't define. */ #undef umode_t During configure we see: checking for umode_t... no The config.log contains: configure:29869: checking for umode_t configure:29894: gcc -c -O2 -Wall -I/usr/include/postgresql conftest.c 5 conftest.c:122: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'ac__type_new_' conftest.c: In function 'main': conftest.c:126: error: 'ac__type_new_' undeclared (first use in this function) conftest.c:126: error: (Each undeclared identifier is reported only once conftest.c:126: error: for each function it appears in.) conftest.c:126: error: expected expression before ')' token So it seems to me that proftpd's configure script is broken somehow. Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: reassign 445611 to proftpd-dfsg
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.8 reassign 445611 proftpd-dfsg 1.3.0-25 Bug#445611: conflicting types for 'mode_t' Bug reassigned from package `libc6-dev, linux-libc-dev' to `proftpd-dfsg'. End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Re: initramfs-tools / cryptoroot
Hi holler if you get to some limits or bugs :) *hollering*, new bugs coming right up...ehm..new release. This time as .deb as promised. Hadn't time to fiddle around with the copy_exec and ltrace stuff yet, had to write man pages first. Available here: http://www.itamservices.de/linux http://www.itamservices.de/linux/downloads/cryptroot-remoteunlock_0.1_i386.deb Ciao, Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#445615: linux-image-2.6.22-2-686: package broke my grub menu.lst file
On 10/7/07, Giorgos D. Pallas [EMAIL PROTECTED] wrote: Package: linux-image-2.6.22-2-686 Version: 2.6.22-4 Severity: grave Justification: renders package unusable I had a custom built kernel (2.6.20.10). This was the conf in the menu.lst file: title Debian GNU/Linux, kernel 2.6.20.10 root(hd0,1) kernel /boot/vmlinuz-2.6.20.10 root=/dev/hda2 ro savedefault After installing the stock kernel (linux-image-2.6.22-2-686) this configuration was changed to: title Debian GNU/Linux, kernel 2.6.20.10 root(hd0,2) kernel /boot/vmlinuz-2.6.20.10 root=/dev/hda3 ro savedefault And of course the system could not boot since it is installed in the second partition (/dev/hda2). The configuration which the stock kernel package generated for it self was also wrong (it pointed to /dev/hda3, instead of the correct /dev/hda2). So, I had to manually edit /boot/grub/menu.lst in order to change all (hd0,2) back to (hd0,1) and all hda3 back to hda2. I can't really guess why it thought that the system is installed on /dev/hda3... Search this paragraph in /boot/grub/menu.lst: ## ## Start Default Options ## ## default kernel options ## default kernel options for automagic boot options ## If you want special options for specific kernels use kopt_x_y_z ## where x.y.z is kernel version. Minor versions can be omitted. ## e.g. kopt=root=/dev/hda1 ro ## kopt_2_6_8=root=/dev/hdc1 ro ## kopt_2_6_8_2_686=root=/dev/hdc2 ro # kopt=root= Show us the last line you from the above paragraph. This has nothing to do with the 'linux-image', but with the 'update-grub' tool. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#445314: linux-image-2.6.22-2-amd64: Kernel hang with ASUS P5KC mobo apparently fixed with Linux 2.6.23-rc9
Now, after reboot the device special files are fine. ? I tried both cold and warm booting, with both a usb and a ps2 keyboard attached (just in case). The device special files came up right each time. However, once when using the 'halt' command the machine crashed and I got this on the console: It would not respond to the reset button and required a cold boot. [80237782] do_exit+0x28e/0x7e6 [8022346f] do_page_fault+0x6cb/0x7a4 [8026e121] zone_statistics+0x3f/0x60 [802ff8be] number+0x10e/0x1f9 [803178e6] vgacon_scroll+0x1a0/0x1c0 [804005bd] error_exit+0x0/0x84 [80231dfc] dup_fd+0x185/0x239 [80231db5] dup_fd+0x13e/0x239 [802689ac] __alloc_pages+0x59/0x2bb [80231ef7] copy_files+0x47/0x63 [80232822] copy_process+0x50f/0x1426 [80244005] alloc_pid+0x209/0x29c [80233897] do_fork+0xb1/0x1fc [80286421] fd_install+0x25/0x59 [8023d30b] recalc_sigpending+0xe/0x25 [8020bdee] system_call+0x7e/0x83 [8020c107] ptregscall_common+0x67/0xb0 Code: 83 7f 28 00 48 89 fb 75 13 48 c7 c7 10 69 47 80 31 c0 45 31 RIP [8028645c] filp_close+0x7/0x65 RSP 81011f843b68 CR2: 2be8 Fixing recursive fault but reboot is needed! Karl [EMAIL PROTECTED] Free Software: You don't pay back, you pay forward. -- Robert A. Heinlein
Bug#445314: linux-image-2.6.22-2-amd64: Kernel hang with ASUS P5KC mobo apparently fixed with Linux 2.6.23-rc9
You can forget all about the messing up of the device special files. The problem is me mis-using the mdadm command and forgetting to put a name after the --create. So, it uses the first device name it finds, which is the name of one of the devices I want to make array out of, and messes up that device special file by turning it into a md device. Sorry for the trouble. However, the box did crash again, this time on the reboot command. This time it responded to the reset button. The console output was different, it crashed in a different way. It's is quite a pain to transcribe the console output so please let me know if you want these in the future. It may be that mucking up the device special file is what's causing the crash on halt/reboot. I suspect so. Regards, Karl [EMAIL PROTECTED] Free Software: You don't pay back, you pay forward. -- Robert A. Heinlein
Bug#445615: linux-image-2.6.22-2-686: package broke my grub menu.lst file
CC: [EMAIL PROTECTED] Do NOT remove the bug e-mail address from a reply if you want to be fixed. It's the only way to keep track. On 10/7/07, Giorgos Pallas [EMAIL PROTECTED] wrote: Teodor wrote: On 10/7/07, Giorgos D. Pallas [EMAIL PROTECTED] wrote: Package: linux-image-2.6.22-2-686 Version: 2.6.22-4 Severity: grave Justification: renders package unusable I had a custom built kernel (2.6.20.10). This was the conf in the menu.lst file: title Debian GNU/Linux, kernel 2.6.20.10 root(hd0,1) kernel /boot/vmlinuz-2.6.20.10 root=/dev/hda2 ro savedefault After installing the stock kernel (linux-image-2.6.22-2-686) this configuration was changed to: title Debian GNU/Linux, kernel 2.6.20.10 root(hd0,2) kernel /boot/vmlinuz-2.6.20.10 root=/dev/hda3 ro savedefault And of course the system could not boot since it is installed in the second partition (/dev/hda2). The configuration which the stock kernel package generated for it self was also wrong (it pointed to /dev/hda3, instead of the correct /dev/hda2). So, I had to manually edit /boot/grub/menu.lst in order to change all (hd0,2) back to (hd0,1) and all hda3 back to hda2. I can't really guess why it thought that the system is installed on /dev/hda3... Search this paragraph in /boot/grub/menu.lst: ## ## Start Default Options ## ## default kernel options ## default kernel options for automagic boot options ## If you want special options for specific kernels use kopt_x_y_z ## where x.y.z is kernel version. Minor versions can be omitted. ## e.g. kopt=root=/dev/hda1 ro ## kopt_2_6_8=root=/dev/hdc1 ro ## kopt_2_6_8_2_686=root=/dev/hdc2 ro # kopt=root= Show us the last line you from the above paragraph. This has nothing to do with the 'linux-image', but with the 'update-grub' tool. Guys, sorry to have bothered you with my eh, inability to understand how the update-grub tool works... Indeed, the menu.lst file had # kopt=root=/dev/hda3 ro # groot=(hd0,2) and that's why my system became unbootable. You must admit though that an option which is commented out, taking active part in the behaviour of a tool, is rather unusual... Again sorry! In this case the bug #445615 should be closed? Can anyone do this? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
PCI:BIOS BUG: MCFG area at f0000000 is not E820-reserved
Hi I also send a email about this problem to the linux.debian.user list but it seems there is nobody who can answer my question. After i downloaded a new daily-build netisntall cd to install a SID system, i was happy that the install went quiet smoothly. But after the reboot i was greeted with this message: PCI:BIOS BUG: MCFG area at f000 is not E820-reserved PCI: Not using MMCONFIG PCI: Failed to allocate mem resource #6:[EMAIL PROTECTED] for :01:00 Loading , please wait ide0: I/O resource 0x3F6-0x3F6 not free. ide0: ports already in use, skipping probe ide1: I/O resource 0x376-0x376 not free. ide1: ports already in use, skipping probe and then the boot process completely hangs. The only thing which i did change before i wanted to install debian again was replace my ATA dvd writer with an SATA dvd writer and used this freed ATA connector to put another ATA disk in my system. Is the kernel which is used by the debian-installer different as the kernel which gets installed on the disk? The version on the disk is now linux-image-2.6.22-2-686 My hardware is: Intel DP965LT mainboard Intel Core 2 Duo E6600 CPU 2 GB Adata DDR2-800 Memory Winfast Nvidia 7600GT (256mb) graphics card Liteon SATA DVD writer Seagate SATA HD (250 GB) Seagate ATA HD (200 GB) Seagate ATA HD (320 GB) The strange thing is that Kubuntu (Gutsy Gibbon) and Opensuse 10.3 (which both also work with the 2.6.22 kernel) ... no problem seem to have with this hardware configuration Does this look familiar to some people? ... Is there a workaround? Thanks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#445615: linux-image-2.6.22-2-686: package broke my grub menu.lst file
Teodor wrote: Guys, sorry to have bothered you with my eh, inability to understand how the update-grub tool works... Indeed, the menu.lst file had # kopt=root=/dev/hda3 ro # groot=(hd0,2) and that's why my system became unbootable. You must admit though that an option which is commented out, taking active part in the behaviour of a tool, is rather unusual... Again sorry! In this case the bug #445615 should be closed? Can anyone do this? I thought it was already closed by Waldi... G. smime.p7s Description: S/MIME Cryptographic Signature
Bug#432555: 2.6.22-4 - Lenny - Update
Hi, Frantically download 2.6.22-4 which rolled into testing in the past couple of days to hope this is fixed and it's still producing the same error. I'm stuck on 2.6.18 and uber-gutted :( -- Regards, Sheridan Hutchinson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: tagging 430984
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.8 tags 430984 + lenny sid Bug#430984: pthreads issue with libc6 There were no tags set. Bug#433187: linux-2.6 - [sparc64-smp] produces unkillable processes Tags added: lenny, sid End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#432555: 2.6.22-4 - Lenny - Update
Processing commands for [EMAIL PROTECTED]: reassign 432555 linux-2.6 Bug#432555: ipw2200: Unknown parameter `rtap_iface' Warning: Unknown package 'linux-image-2.6.21-2-686' Bug reassigned from package `linux-image-2.6.21-2-686' to `linux-2.6'. -- 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#445684: linux-headers-2.6.22-2-amd64: Invalid UTS_RELEASE value in utsrelease.h
Package: linux-headers-2.6.22-2-amd64 Version: 2.6.22-4 Severity: important The file include/linux/utsrelease.h from the package linux-headers-2.6.22-2-amd64 contains an invalid UTS_RELEASE value. It is set as 2.6.222.6.22-2-amd64 , when it should be 2.6.22-2-amd64 -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.22-2-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages linux-headers-2.6.22-2-amd64 depends on: ii gcc-4.1 4.1.2-16 The GNU C compiler ii linux-headers-2.6.22-22.6.22-4 Common header files for Linux 2.6. ii linux-kbuild-2.6.22 2.6.22-1 Kbuild infrastructure for Linux 2. linux-headers-2.6.22-2-amd64 recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#445684: marked as done (linux-headers-2.6.22-2-amd64: Invalid UTS_RELEASE value in utsrelease.h)
Your message dated Sun, 7 Oct 2007 21:22:32 +0200 with message-id [EMAIL PROTECTED] and subject line Bug#445684: linux-headers-2.6.22-2-amd64: Invalid UTS_RELEASE value in utsrelease.h 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-headers-2.6.22-2-amd64 Version: 2.6.22-4 Severity: important The file include/linux/utsrelease.h from the package linux-headers-2.6.22-2-amd64 contains an invalid UTS_RELEASE value. It is set as 2.6.222.6.22-2-amd64 , when it should be 2.6.22-2-amd64 -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.22-2-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages linux-headers-2.6.22-2-amd64 depends on: ii gcc-4.1 4.1.2-16 The GNU C compiler ii linux-headers-2.6.22-22.6.22-4 Common header files for Linux 2.6. ii linux-kbuild-2.6.22 2.6.22-1 Kbuild infrastructure for Linux 2. linux-headers-2.6.22-2-amd64 recommends no packages. -- no debconf information ---End Message--- ---BeginMessage--- On Sun, Oct 07, 2007 at 07:33:26PM +0100, Bernard Bith wrote: The file include/linux/utsrelease.h from the package linux-headers-2.6.22-2-amd64 contains an invalid UTS_RELEASE value. It is set as 2.6.222.6.22-2-amd64 , when it should be 2.6.22-2-amd64 Not in all the files I checked: | #define UTS_RELEASE 2.6.22-2-amd64 Bastian -- She won' go Warp 7, Cap'n! The batteries are dead! ---End Message---
Bug#445688: initramfs-tools: creates broken initramfs image
Package: initramfs-tools Version: 0.90a Severity: critical Justification: breaks the whole system The initramfs image generated by update-initramfs stalls at a waiting for root filesystem... message. After roughly 5 minutes, it drops to a shell saying the filesystem doesn't exist. Other initramfs images(yaird) work with same kernel, same bug on all kernals. This is critical because this command is used to generate the original initramfs when the kernel is installed. -- Package-specific info: -- /proc/cmdline root=UUID=b507a249-f4b4-4502-8a6b-9fc0f3b39e05 ro quiet splash vga=769 -- /proc/filesystems reiserfs ext3 cramfs fuseblk -- lsmod Module Size Used by rfcomm 65432 0 l2cap 49792 5 rfcomm bluetooth 81124 4 rfcomm,l2cap capability 17672 0 commoncap 20096 1 capability ppdev 22020 0 ac 17796 0 battery22532 0 ipv6 333600 18 af_packet 47624 2 rt73 227328 0 dm_snapshot30760 0 dm_mirror 35732 0 dm_mod 72524 2 dm_snapshot,dm_mirror vesafb 20996 1 psmouse50824 0 lp 24324 0 parport49480 2 ppdev,lp ide_cd 8 0 cdrom 49440 1 ide_cd ide_disk 28928 4 ata_generic20996 0 libata137880 1 ata_generic scsi_mod 155148 1 libata generic17028 0 [permanent] uhci_hcd 37520 0 usbcore 147464 3 rt73,uhci_hcd piix 22660 0 [permanent] 8139too39680 0 8139cp 37376 0 mii18432 2 8139too,8139cp thermal26760 0 processor 44664 1 thermal -- /etc/kernel-img.conf do_symlinks = yes relative_links = yes do_bootloader = no do_bootfloppy = no do_initrd = yes link_in_boot = no postinst_hook = update-grub postrm_hook = update-grub -- /etc/initramfs-tools/initramfs.conf MODULES=most BUSYBOX=y KEYMAP=n BOOT=local DEVICE=eth0 NFSROOT=auto -- System Information: Debian Release: BeejexLinux APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.20.3-ubuntu1BeejexLinux (SMP w/1 CPU core; PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages initramfs-tools depends on: ii busybox 1:1.1.3-5Tiny utilities for small and embed ii busybox-initramfs 1:1.1.3-3ubuntu3 Standalone shell setup for initram ii cpio2.9-3GNU cpio -- a program to manage ar ii klibc-utils 1.5-4small statically-linked utilities ii module-init-tools 3.3-pre11-4 tools for managing Linux kernel mo ii udev108-0ubuntu4 rule-based device node and kernel initramfs-tools recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: [bts-link] source package linux-2.6
Processing commands for [EMAIL PROTECTED]: # # bts-link upstream status pull for source package linux-2.6 # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user [EMAIL PROTECTED] Setting user to [EMAIL PROTECTED] (was [EMAIL PROTECTED]). # remote status report for #438663 # * http://bugzilla.kernel.org/show_bug.cgi?id=9073 # * remote status changed: NEW - CLOSED # * remote resolution changed: (?) - CODE-FIX # * closed upstream tags 438663 + fixed-upstream Bug#438663: linux-image-2.6.22-1-amd64: Ethernet not functioning on Nvidia MCP51 There were no tags set. Tags added: fixed-upstream usertags 438663 - status-NEW Bug#438663: linux-image-2.6.22-1-amd64: Ethernet not functioning on Nvidia MCP51 Usertags were: status-NEW. Usertags are now: . usertags 438663 + status-CLOSED resolution-CODE-FIX Bug#438663: linux-image-2.6.22-1-amd64: Ethernet not functioning on Nvidia MCP51 There were no usertags set. Usertags are now: resolution-CODE-FIX status-CLOSED. 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]
[bts-link] source package linux-2.6
# # bts-link upstream status pull for source package linux-2.6 # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user [EMAIL PROTECTED] # remote status report for #438663 # * http://bugzilla.kernel.org/show_bug.cgi?id=9073 # * remote status changed: NEW - CLOSED # * remote resolution changed: (?) - CODE-FIX # * closed upstream tags 438663 + fixed-upstream usertags 438663 - status-NEW usertags 438663 + status-CLOSED resolution-CODE-FIX thanks
Bug#421015: openafs - module not buildable against 2.6.18-5 s390x
As with with the original report in this bug, I cannot get the OpenAFS module to build with 2.6.18-5 on s390x. All packages, except openafs-modules-source (see following) are stock Etch. Compiling Etch's openafs-modules-source fails with (abridged) s390x not supported. Compiling openafs-modules-source-1.4.4.dfsg1-7 (fetched from testing) fails with the following: ... /usr/src/modules/openafs/src/afs/afs_prototypes.h:1042: warning: function declaration isn't a prototype /usr/src/modules/openafs/src/libafs/MODLOAD-2.6.18-5-s390x-MP/afs_vnop_flock.c:36: warning: 'struct flock64' declared inside par ameter list /usr/src/modules/openafs/src/libafs/MODLOAD-2.6.18-5-s390x-MP/afs_vnop_flock.c:40: warning: 'struct flock64' declared inside par ameter list /usr/src/modules/openafs/src/libafs/MODLOAD-2.6.18-5-s390x-MP/afs_vnop_flock.c:45: warning: 'struct flock64' declared inside par ameter list /usr/src/modules/openafs/src/libafs/MODLOAD-2.6.18-5-s390x-MP/afs_vnop_flock.c:46: error: conflicting types for 'lockIdSet' /usr/src/modules/openafs/src/afs/afs_prototypes.h:940: error: previous declaration of 'lockIdSet' was here /usr/src/modules/openafs/src/libafs/MODLOAD-2.6.18-5-s390x-MP/afs_vnop_flock.c: In function 'lockIdSet': /usr/src/modules/openafs/src/libafs/MODLOAD-2.6.18-5-s390x-MP/afs_vnop_flock.c:133: error: dereferencing pointer to incomplete t ype /usr/src/modules/openafs/src/libafs/MODLOAD-2.6.18-5-s390x-MP/afs_vnop_flock.c: At top level: /usr/src/modules/openafs/src/libafs/MODLOAD-2.6.18-5-s390x-MP/afs_vnop_flock.c:157: warning: 'struct flock64' declared inside pa rameter list /usr/src/modules/openafs/src/libafs/MODLOAD-2.6.18-5-s390x-MP/afs_vnop_flock.c:158: error: conflicting types for 'lockIdcmp2' /usr/src/modules/openafs/src/libafs/MODLOAD-2.6.18-5-s390x-MP/afs_vnop_flock.c:40: error: previous declaration of 'lockIdcmp2' w as here /usr/src/modules/openafs/src/libafs/MODLOAD-2.6.18-5-s390x-MP/afs_vnop_flock.c: In function 'lockIdcmp2': /usr/src/modules/openafs/src/libafs/MODLOAD-2.6.18-5-s390x-MP/afs_vnop_flock.c:178: error: dereferencing pointer to incomplete t ype /usr/src/modules/openafs/src/libafs/MODLOAD-2.6.18-5-s390x-MP/afs_vnop_flock.c:180: error: dereferencing pointer to incomplete t ype /usr/src/modules/openafs/src/libafs/MODLOAD-2.6.18-5-s390x-MP/afs_vnop_flock.c:201: error: dereferencing pointer to incomplete t ype /usr/src/modules/openafs/src/libafs/MODLOAD-2.6.18-5-s390x-MP/afs_vnop_flock.c: In function 'HandleFlock': /usr/src/modules/openafs/src/libafs/MODLOAD-2.6.18-5-s390x-MP/afs_vnop_flock.c:233: error: storage size of 'flock' isn't known ... Entire build log from m-a build openafs can be included upon request. Is there a supported openafs module for s390x on Etch? I apologize if this should be a separate bug report -- the initial post in this bug seems to match my issue. Thank you, -Matt Smith [EMAIL PROTECTED]
Bug#445735: image creation fails with a non-modular kernel
Package: initramfs-tools Version: 0.91b I compiled a kernel using kernel-package, with CONFIG_MODULES not set since this machine is not going to need to load any modules. When trying to install the generated .deb, I get the following error: Setting up linux-image-2.6.22.9 (3:2.6.22.9.anomie1) ... Finding valid ramdisk creators. Using mkinitramfs-kpkg to build the ramdisk. mkinitramfs-kpkg failed to create initrd image. Failed to create initrd image. Executing update-initramfs with the -v option gives more information: # update-initramfs -c -v -k linux-image-2.6.22.9 update-initramfs: Generating /boot/initrd.img-linux-image-2.6.22.9 Cannot find /lib/modules/linux-image-2.6.22.9 update-initramfs: failed for /boot/initrd.img-linux-image-2.6.22.9 Unless I'm mistaken, an initramfs is still required if / is on an LVM2 logical volume. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
