Bug#471495: linux-2.6: please add Vcs-* fields/headers to debian/control file
On Tue, Mar 18, 2008 at 02:52:19PM +, Jon Dowland wrote: Patch attached. The patch is wrong. trunk != sid. And no, I don't know a way to determine that automatic. Bastian -- Vulcans believe peace should not depend on force. -- Amanda, Journey to Babel, stardate 3842.3 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Enable some debug options
On Wed, Mar 19, 2008 at 12:37:38AM +, Thiemo Seufer wrote: Bastian Blank wrote: - PRINTK_TIME Is this one useful for non-esoteric cases? Sure. You never had the problem that the kernel log is full of disk errors and you can't determine the timing? Bastian -- No one wants war. -- Kirk, Errand of Mercy, stardate 3201.7 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Changes for 2.6.25
* Bastian Blank [EMAIL PROTECTED] [2008-02-14 19:43]: - Deprecate kernel-package method. It is still used for alpha, arm, armel, hppa, ia64, mips, mipsel, sparc. It will be removed after the 2.6.25 release to make it possible to use features like out-of-tree builds. Can you please elaborate on this some more? What do the arches that still use kernel-package have to do in order to move to the new system? Is there any documentation on this? -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Changes for 2.6.25
On Wed, Mar 19, 2008 at 03:06:47PM +0100, Martin Michlmayr wrote: * Bastian Blank [EMAIL PROTECTED] [2008-02-14 19:43]: - Deprecate kernel-package method. It is still used for alpha, arm, armel, hppa, ia64, mips, mipsel, sparc. It will be removed after the 2.6.25 release to make it possible to use features like out-of-tree builds. Can you please elaborate on this some more? What do the arches that still use kernel-package have to do in order to move to the new system? Is there any documentation on this? Sure. The documentation is the source, at least m68k managed to get it working. It needs two things in debian/rules.real: - A target which installs the image. Example: | install-image_s390_$(FEATURESET)_$(FLAVOUR)_plain_image | install -m644 '$(DIR)/arch/s390/boot/image' $(INSTALL_DIR)/vmlinuz-$(REAL_VERSION) - Maybe a definition for template overrides. The type currently uses a copy of the kpkg templates which needs some additional information. Examples: | install-image_powerpc_$(FEATURESET)_$(FLAVOUR)_plain_templates: ARG_KIMAGE = vmlinux | install-image_s390_$(FEATURESET)_$(FLAVOUR)_plain_templates: ARG_BOOTLOADER = zipl Bastian -- Murder is contrary to the laws of man and God. -- M-5 Computer, The Ultimate Computer, stardate 4731.3 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#466933: marked as done (Debian-arm: kernel BUG at fs/inode.c:250!)
Your message dated Wed, 19 Mar 2008 15:53:52 +0100 with message-id [EMAIL PROTECTED] and subject line Re: Bug#466933: Debian-arm: kernel BUG at fs/inode.c:250! has caused the Debian Bug report #466933, regarding Debian-arm: kernel BUG at fs/inode.c:250! to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 466933: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=466933 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: kernel Version: 2.6.18-6-ixp4xx Severity: Important I'm running the latest version of Debian on a Linksys NSLU2 with a 2GB USB stick as mass storage and a pl2303 based USB-to-serial adapter attached. The box crashes at least once a day, and I find messages like this in kern.log: Feb 19 21:50:35 slug kernel: kernel BUG at fs/inode.c:250! Feb 19 21:50:35 slug kernel: Unable to handle kernel NULL pointer dereference at virtual address Feb 19 21:50:35 slug kernel: pgd = c1778000 Feb 19 21:50:35 slug kernel: [] *pgd=017b0031, *pte=, *ppte= Feb 19 21:50:35 slug kernel: Internal error: Oops: 817 [#1] Feb 19 21:50:35 slug kernel: Modules linked in: ledtrig_heartbeat dm_snapshot dm_mirror dm_mod rtc_dev ixp4xx_mac evdev ixp4 xx_npe ixp4xx_qmgr firmware_class pl2303 usbserial ixp4xx_beeper ext3 jbd mbcache sd_mod usb_storage scsi_mod ehci_hcd ohci_ hcd usbcore Feb 19 21:50:35 slug kernel: CPU: 0 Feb 19 21:50:35 slug kernel: PC is at __bug+0x44/0x58 Feb 19 21:50:35 slug kernel: LR is at 0x1 Feb 19 21:50:35 slug kernel: pc : [c00238a0]lr : [0001]Not tainted Feb 19 21:50:35 slug kernel: sp : c1845e9c ip : 6093 fp : c1845ea8 Feb 19 21:50:35 slug kernel: r10: 40184000 r9 : c1844000 r8 : c02d31a0 Feb 19 21:50:35 slug kernel: r7 : c08aac38 r6 : r5 : c02e258c r4 : Feb 19 21:50:35 slug kernel: r3 : r2 : r1 : 1e7d r0 : 0001 Feb 19 21:50:35 slug kernel: Flags: nZCv IRQs on FIQs on Mode SVC_32 Segment user Feb 19 21:50:35 slug kernel: Control: 397F Table: 01778000 DAC: 0015 Feb 19 21:50:35 slug kernel: Process sh (pid: 10528, stack limit = 0xc1844250) Feb 19 21:50:35 slug kernel: Stack: (0xc1845e9c to 0xc1846000) Feb 19 21:50:35 slug kernel: 5e80: c1845ebc Feb 19 21:50:35 slug kernel: 5ea0: c1845eac c00931a8 c0023868 c0303500 c1845ed4 c1845ec0 c00ad0b0 c0093170 Feb 19 21:50:35 slug kernel: 5ec0: c02e258c c00ad030 c1845eec c1845ed8 c0093378 c00ad03c c02e258c c02e258c Feb 19 21:50:35 slug kernel: 5ee0: c1845f00 c1845ef0 c0092d18 c0093298 c08aac38 c1845f1c c1845f04 c0090f4c Feb 19 21:50:35 slug kernel: 5f00: c0092c94 c08aac38 c1845f34 c1845f20 c0091aa4 c0090eb8 Feb 19 21:50:35 slug kernel: 5f20: 00bf c1845f5c c1845f38 c0079aac c0091954 c1d67760 Feb 19 21:50:35 slug kernel: 5f40: c130e240 0006 c001ff24 c1845f6c c1845f60 c0079b04 c0079928 Feb 19 21:50:35 slug kernel: 5f60: c1845f88 c1845f70 c00766fc c0079adc c130e240 c1d67760 c1845fa4 Feb 19 21:50:35 slug kernel: 5f80: c1845f8c c0077dc0 c0076694 0006 0006 0003 c1845fa8 Feb 19 21:50:35 slug kernel: 5fa0: c001fd80 c0077d48 0006 0006 0003 be911aac 001f 2c94 Feb 19 21:50:35 slug kernel: 5fc0: 0006 0006 0003 0003 be911aac be911ba0 40184000 000b6ed0 Feb 19 21:50:35 slug kernel: 5fe0: 400fc6fc be911aac 0006e9b4 400fcb78 0010 0003 0002 0003 Feb 19 21:50:35 slug kernel: Backtrace: Feb 19 21:50:35 slug kernel: [c002385c] (__bug+0x0/0x58) from [c00931a8] (clear_inode+0x44/0x128) Feb 19 21:50:35 slug kernel: [c0093164] (clear_inode+0x0/0x128) from [c00ad0b0] (proc_delete_inode+0x80/0x84) Feb 19 21:50:35 slug kernel: r4 = C0303500 Feb 19 21:50:35 slug kernel: [c00ad030] (proc_delete_inode+0x0/0x84) from [c0093378] (generic_delete_inode+0xec/0x174) Feb 19 21:50:35 slug kernel: r5 = C00AD030 r4 = C02E258C Feb 19 21:50:35 slug kernel: [c009328c] (generic_delete_inode+0x0/0x174) from [c0092d18] (iput+0x90/0xa4) Feb 19 21:50:35 slug kernel: r5 = C02E258C r4 = C02E258C Feb 19 21:50:35 slug kernel: [c0092c88] (iput+0x0/0xa4) from [c0090f4c] (dentry_iput+0xa0/0xa4) Feb 19 21:50:35 slug kernel: r4 = C08AAC38 Feb 19 21:50:35 slug kernel: [c0090eac] (dentry_iput+0x0/0xa4) from [c0091aa4] (dput+0x15c/0x18c) Feb 19 21:50:35 slug kernel: r5 = r4 = C08AAC38 Feb 19 21:50:35 slug kernel: [c0091948] (dput+0x0/0x18c) from [c0079aac] (__fput+0x190/0x1b4) Feb 19 21:50:35 slug kernel: r5 = r4 = 00BF Feb 19 21:50:35 slug kernel: [c007991c]
Processed: found 266875 in 2.6.22-4
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.18.1 found 266875 2.6.22-4 Bug#266875: uid= doesn't work on udf filesystems with rock ridge attributes Bug marked as found in version 2.6.22-4. 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]
DEFAULT_MMAP_MIN_ADDR change breaks ssh on arm
The following change r10769 | maks | 2008-03-10 17:03:03 +0100 (Mon, 10 Mar 2008) | 8 lines security: set DEFAULT_MMAP_MIN_ADDR to 65536 Low address space to protect from user allocation, see a5ecbcb8c13ea8a822d243bf782d0dc9525b4f84, runtime tunable on /proc/sys/vm/mmap_min_addr. let's see if we get any fallout. double checked after Kconfig recommendation that fedora uses that recommendation too. breaks ssh on arm. While root can still log in via ssh, normal users cannot. ssh almost manages to log in but when it comes to starting a shell the connection simply closes. Changing DEFAULT_MMAP_MIN_ADDR back to 0 fixes this. maks, should I simply set DEFAULT_MMAP_MIN_ADDR to 0 on ARM or should I report this to the SE Linux folks or someone else? I've no idea how SE Linux works, so any help is welcome. -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: DEFAULT_MMAP_MIN_ADDR change breaks ssh on arm
[ adding relevant cc peoples to your message, no more insight ] On Wed, Mar 19, 2008 at 06:46:37PM +0100, Martin Michlmayr wrote: The following change r10769 | maks | 2008-03-10 17:03:03 +0100 (Mon, 10 Mar 2008) | 8 lines security: set DEFAULT_MMAP_MIN_ADDR to 65536 Low address space to protect from user allocation, see a5ecbcb8c13ea8a822d243bf782d0dc9525b4f84, runtime tunable on /proc/sys/vm/mmap_min_addr. let's see if we get any fallout. double checked after Kconfig recommendation that fedora uses that recommendation too. breaks ssh on arm. While root can still log in via ssh, normal users cannot. ssh almost manages to log in but when it comes to starting a shell the connection simply closes. Changing DEFAULT_MMAP_MIN_ADDR back to 0 fixes this. maks, should I simply set DEFAULT_MMAP_MIN_ADDR to 0 on ARM or should I report this to the SE Linux folks or someone else? I've no idea how SE Linux works, so any help is welcome. -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Changes for 2.6.25
On Wed, Mar 19, 2008 at 03:47:21PM +0100, Bastian Blank wrote: Sure. The documentation is the source, Am I the only one finding this unacceptable? Greetings Marc -- - Marc Haber | I don't trust Computers. They | Mailadresse im Header Mannheim, Germany | lose things.Winona Ryder | Fon: *49 621 72739834 Nordisch by Nature | How to make an American Quilt | Fax: *49 3221 2323190 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: DEFAULT_MMAP_MIN_ADDR change breaks ssh on arm
breaks ssh on arm. While root can still log in via ssh, normal users cannot. ssh almost manages to log in but when it comes to starting a shell the connection simply closes. Changing DEFAULT_MMAP_MIN_ADDR back to 0 fixes this. ... I should mention that it's not a ssh problem per se, but one with PAM. Logging in on the serial console also fails in the same way (see below). I believe Gordon Farquharson, who originally found this problem, has some more debugging information. Transcript: debian login: tbm Password: Last login: Wed Mar 19 17:57:46 CET 2008 from 192.168.1.22 on pts/0 Linux debian 2.6.25-rc6-iop32x #9 Wed Mar 19 17:38:35 UTC 2008 armv5tel The programs included with the Debian GNU/Linux system are free software; the exact distribution terms for each program are described in the individual files in /usr/share/doc/*/copyright. Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. Debian GNU/Linux lenny/sid debian ttyS0 debian login: -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: DEFAULT_MMAP_MIN_ADDR change breaks ssh on arm
Hi All On Wed, Mar 19, 2008 at 12:45 PM, Martin Michlmayr [EMAIL PROTECTED] wrote: I believe Gordon Farquharson, who originally found this problem, has some more debugging information. I'll send this information when I get home this evening. Essentially, it is the output from 'sshd -d -d -d' when I try to connect with a non-root user. In the meantime, here is a page that may (or may not) provide some more information. http://inz.fi/blog/2008/01/17/scratchbox-on-hardy/ I should note that 'su' and 'login' also fail for non-root users. Martin, did you say that you don't see this problem on the Thecus N2100 (iop32x)? I've seen it on the Linksys NSLU2 (ixp4xx) and the GLAN Tank (iop32x). Gordon -- Gordon Farquharson GnuPG Key ID: 32D6D676 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: DEFAULT_MMAP_MIN_ADDR change breaks ssh on arm
* Gordon Farquharson [EMAIL PROTECTED] [2008-03-19 13:09]: Martin, did you say that you don't see this problem on the Thecus N2100 (iop32x)? No, I see it there as well. -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#368399: marked as done (netbase: Wake-on-LAN doesn't work after shutdown)
Your message dated Wed, 19 Mar 2008 20:51:40 +0100 with message-id [EMAIL PROTECTED] and subject line Fixed in current kernel versions has caused the Debian Bug report #368399, regarding netbase: Wake-on-LAN doesn't work after shutdown to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 368399: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=368399 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: netbase Version: 4.25 Severity: normal I'm using an Intel desktop gigabit card (e1000 driver). WoL works once when I turn the system off right after power on, e. g. when it's sitting at the grub screen. However, after a shutdown -h or similar, the machine will refuse to wake up, because the NIC was apparently shut down with the system (LED is off). There're various explanations floating arout for this: - WoL ia not turned on via ethtool (it is) - the interface is being brought down prior to shutdown (commenting out the relevant part of init.d/networking didn't help) - the driver module is unloaded prior to shutdown (no way to check) Something shuts dows the card completely, even when it should stay on in soft-off state. Feel free to move this to kernel-image-2.6-k7, but I don't think it's a kernel bug, really - my other machines with different NICs and kernels behave the same. Thanks, C. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15-1-k7 Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8) Versions of packages netbase depends on: ii debconf [debconf-2.0] 1.5.0Debian configuration management sy ii ifupdown0.6.7high level tools to configure netw ii iputils-ping [ping] 3:20020927-3 Tools to test the reachability of ii lsb-base3.1-5Linux Standard Base 3.1 init scrip ii netkit-inetd0.10-10.3The Internet Superserver ii tcpd7.6.dbs-9Wietse Venema's TCP wrapper utilit netbase recommends no packages. -- debconf information: netbase/upgrade-note/etc-network-interfaces-pre-3.17-1: netbase/upgrade-note/init.d-split-pre-3.16-1: netbase/upgrade-note/radius-ports-pre-3.05: netbase/upgrade-note/portmap-restart-pre-3.11-2: ---End Message--- ---BeginMessage--- The stock Debian testing kernel has for some months now included an e1000 driver version that does not exhibit the problem. Sorry for not closing the bug earlier. Cheers, C. ---End Message---
Bug#365475: marked as done (hdparm: disk sent to sleep with -Y does not wake up again)
Your message dated Wed, 19 Mar 2008 20:59:20 +0100
with message-id [EMAIL PROTECTED]
and subject line Problem has become irrelevant
has caused the Debian Bug report #365475,
regarding hdparm: disk sent to sleep with -Y does not wake up again
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
365475: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=365475
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
---BeginMessage---
Package: hdparm
Version: 6.3-3
Severity: normal
I have a Maxtor 7V300F0 (MaxLine III 300GB SATA) that I use
only for daily backups and thus would like to turn off when
no backup is running.
The hdparm -Y command succeeds in turning off the drive, but
after that it refuses to wake up at all. While an access should
probably reset the channel and spin up the disk, all I get is:
ata2: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00
ata2: status=0x51 { DriveReady SeekComplete Error }
ata2: error=0x04 { DriveStatusError }
ata2: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00
ata2: status=0x51 { DriveReady SeekComplete Error }
ata2: error=0x04 { DriveStatusError }
ata2: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00
ata2: status=0x51 { DriveReady SeekComplete Error }
ata2: error=0x04 { DriveStatusError }
ata2: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00
ata2: status=0x51 { DriveReady SeekComplete Error }
ata2: error=0x04 { DriveStatusError }
ata2: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00
ata2: status=0x51 { DriveReady SeekComplete Error }
ata2: error=0x04 { DriveStatusError }
ata2: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00
ata2: status=0x51 { DriveReady SeekComplete Error }
ata2: error=0x04 { DriveStatusError }
ata2: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00
ata2: status=0x51 { DriveReady SeekComplete Error }
ata2: error=0x04 { DriveStatusError }
ata2: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00
ata2: status=0x51 { DriveReady SeekComplete Error }
ata2: error=0x04 { DriveStatusError }
ata2: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00
ata2: status=0x51 { DriveReady SeekComplete Error }
ata2: error=0x04 { DriveStatusError }
ata2: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00
ata2: status=0x51 { DriveReady SeekComplete Error }
ata2: error=0x04 { DriveStatusError }
ata2: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00
ata2: status=0x51 { DriveReady SeekComplete Error }
ata2: error=0x04 { DriveStatusError }
ata2: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00
ata2: status=0x51 { DriveReady SeekComplete Error }
ata2: error=0x04 { DriveStatusError }
Basically, a reboot is required to revive the drive. The controller is a:
:00:0e.1 Mass storage controller: ALi Corporation ULi 5289 SATA (rev 10)
Complete dmesg is attached
Thanks,
C.
available.
On node 0 totalpages: 524208
DMA zone: 4096 pages, LIFO batch:0
DMA32 zone: 0 pages, LIFO batch:0
Normal zone: 290816 pages, LIFO batch:31
HighMem zone: 229296 pages, LIFO batch:31
DMI 2.3 present.
ACPI: RSDP (v000 ACPIAM) @ 0x000f9b10
ACPI: RSDT (v001 A M I OEMRSDT 0x03000620 MSFT 0x0097) @ 0x7ffb
ACPI: FADT (v001 A M I OEMFACP 0x03000620 MSFT 0x0097) @ 0x7ffb0200
ACPI: MADT (v001 A M I OEMAPIC 0x03000620 MSFT 0x0097) @ 0x7ffb0390
ACPI: OEMB (v001 A M I AMI_OEM 0x03000620 MSFT 0x0097) @ 0x7ffc0040
ACPI: DSDT (v001 939A8 939A8202 0x0202 INTL 0x02002026) @ 0x
ACPI: PM-Timer IO Port: 0x808
ACPI: Local APIC address 0xfee0
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
Processor #0 15:15 APIC version 16
ACPI: LAPIC (acpi_id[0x02] lapic_id[0x81] disabled)
ACPI: IOAPIC (id[0x01] address[0xfec0] gsi_base[0])
IOAPIC[0]: apic_id 1, version 17, address 0xfec0, GSI 0-23
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level)
ACPI: IRQ0 used by override.
ACPI: IRQ2 used by override.
ACPI: IRQ9 used by override.
Enabling APIC mode: Flat. Using 1 I/O APICs
Using ACPI (MADT) for SMP configuration information
Allocating PCI resources starting at 8800 (gap: 8000:7f7c)
Built 1 zonelists
Kernel command line: root=/dev/sda3 ro
mapped APIC to d000 (fee0)
mapped IOAPIC to c000 (fec0)
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
PID hash table entries: 4096 (order: 12, 65536 bytes)
Detected 2200.192 MHz processor.
Using pmtmr for
Bug#277391: call me
my room mate showed me you and im interested in talking with you add me on live messenger [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#278822: amazing bio
just saw your pic (its nice) if you care my messenger is [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#292747: hey muffin
my room mate showed me you and im interested in talking with you add me on live messenger [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: retitle 468343 to Page fault in nfs_complete_unlink
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.18.1 retitle 468343 Page fault in nfs_complete_unlink Bug#468343: linux-image-2.6.18-6-amd64: Feb 28 14:22:43 dove kernel: Modules linked in: button ac battery ipt_LOG xt_limit xt_state xt_tcpudp iptable_filter iptable_mangle iptable_nat ip_nat ip_conntrack nfnetlink ip_tables x_tables nfs lockd nfs_acl sunrpc bonding reiserfs dm_snapshot dm_mirror dm_mod loop joydev evdev pcspkr usbhid shpchp pci_hotplug i2c_i801 sg i2c_core sr_mod cdrom ext3 jbd mbcache generic ide_core sd_mod ata_piix bnx2 libata ehci_hcd e1000 uhci_hcd aacraid scsi_mod thermal processor fan Changed Bug title to `Page fault in nfs_complete_unlink' from `linux-image-2.6.18-6-amd64: Feb 28 14:22:43 dove kernel: Modules linked in: button ac battery ipt_LOG xt_limit xt_state xt_tcpudp iptable_filter iptable_mangle iptable_nat ip_nat ip_conntrack nfnetlink ip_tables x_tables nfs lockd nfs_acl sunrpc bonding reiserfs dm_snapshot dm_mirror dm_mod loop joydev evdev pcspkr usbhid shpchp pci_hotplug i2c_i801 sg i2c_core sr_mod cdrom ext3 jbd mbcache generic ide_core sd_mod ata_piix bnx2 libata ehci_hcd e1000 uhci_hcd aacraid scsi_mod thermal processor fan'. End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#348613: listing of you
my room mate showed me you and im interested in talking with you add me on live messenger [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#468343: Page fault in nfs_complete_unlink
These oops messages seem incomplete but I'm assuming a page fault. The
traceback shows the fault at offset 0x10 in nfs_complete_unlink. The
top of this function is:
void
nfs_complete_unlink(struct dentry *dentry)
{
struct nfs_unlinkdata *data;
for(data = nfs_deletes; data != NULL; data = data-next) {
if (dentry == data-dentry)
break;
}
Offset 0x10 in the compiled code corresponds to the line if (dentry ==
data-dentry) with data in register rbx. In the register dump we see
rbx is 0x00050006, so the nfs_deletes list is corrupt.
The first comment in fs/nfs/unlink.c says:
* NOTE: we rely on holding the BKL for list manipulation protection.
So I looked at which functions manipulate the nfs_deletes list and
found:
- nfs_async_unlink
- called by nfs_sillyrename
- called by nfs_unlink, holding BKL
- called by nfs_rename, holding BKL
- nfs_complete_unlink
- called by nfs_dentry_iput, holding BKL
- nfs_detach_unlinkdata
- called by nfs_put_unlinkdata
- called by nfs_complete_unlink
- called by nfs_dentry_iput, holding BKL
- called by nfs_async_unlink_release
- called through rpc_call_ops::rpc_release
- NOT called with BKL!
The locking was revised and probably fixed by patch
e4eff1a622edd6ab7b73acd5d8763aa2fa3fee49 which went into Linux 2.6.23.
It looks like this will apply to 2.6.18 with a tiny bit of fudging, but
it changes ABI.
Ben.
--
Ben Hutchings
The generation of random numbers is too important to be left to chance.
- Robert Coveyou
signature.asc
Description: This is a digitally signed message part
Re: DEFAULT_MMAP_MIN_ADDR change breaks ssh on arm
Hi All On Wed, Mar 19, 2008 at 1:09 PM, Gordon Farquharson [EMAIL PROTECTED] wrote: On Wed, Mar 19, 2008 at 12:45 PM, Martin Michlmayr [EMAIL PROTECTED] wrote: I believe Gordon Farquharson, who originally found this problem, has some more debugging information. I'll send this information when I get home this evening. Essentially, it is the output from 'sshd -d -d -d' when I try to connect with a non-root user. Here is the debug information from sshd with -d -d -d. Restarting OpenBSD Secure Shell server: sshddebug2: load_server_config: filename /etc/ssh/sshd_config debug2: load_server_config: done config len = 660 debug2: parse_server_config: config /etc/ssh/sshd_config len 660 debug3: /etc/ssh/sshd_config:5 setting Port 22 debug3: /etc/ssh/sshd_config:8 setting ListenAddress 0.0.0.0 debug3: /etc/ssh/sshd_config:9 setting Protocol 2 debug3: /etc/ssh/sshd_config:11 setting HostKey /etc/ssh/ssh_host_rsa_key debug3: /etc/ssh/sshd_config:12 setting HostKey /etc/ssh/ssh_host_dsa_key debug3: /etc/ssh/sshd_config:14 setting UsePrivilegeSeparation yes debug3: /etc/ssh/sshd_config:17 setting KeyRegenerationInterval 3600 debug3: /etc/ssh/sshd_config:18 setting ServerKeyBits 768 debug3: /etc/ssh/sshd_config:21 setting SyslogFacility AUTH debug3: /etc/ssh/sshd_config:22 setting LogLevel DEBUG debug3: /etc/ssh/sshd_config:25 setting LoginGraceTime 120 debug3: /etc/ssh/sshd_config:26 setting PermitRootLogin yes debug3: /etc/ssh/sshd_config:27 setting StrictModes yes debug3: /etc/ssh/sshd_config:29 setting RSAAuthentication yes debug3: /etc/ssh/sshd_config:30 setting PubkeyAuthentication yes debug3: /etc/ssh/sshd_config:34 setting IgnoreRhosts yes debug3: /etc/ssh/sshd_config:36 setting RhostsRSAAuthentication no debug3: /etc/ssh/sshd_config:38 setting HostbasedAuthentication no debug3: /etc/ssh/sshd_config:43 setting PermitEmptyPasswords no debug3: /etc/ssh/sshd_config:47 setting ChallengeResponseAuthentication no debug3: /etc/ssh/sshd_config:62 setting X11Forwarding yes debug3: /etc/ssh/sshd_config:63 setting X11DisplayOffset 10 debug3: /etc/ssh/sshd_config:64 setting PrintMotd no debug3: /etc/ssh/sshd_config:65 setting PrintLastLog yes debug3: /etc/ssh/sshd_config:66 setting TCPKeepAlive yes debug3: /etc/ssh/sshd_config:73 setting AcceptEnv LANG LC_* debug3: /etc/ssh/sshd_config:75 setting Subsystem sftp /usr/lib/openssh/sftp-server debug3: /etc/ssh/sshd_config:77 setting UsePAM yes debug1: sshd version OpenSSH_4.7p1 Debian-2 debug3: Not a RSA1 key file /etc/ssh/ssh_host_rsa_key. debug1: read PEM private key done: type RSA debug1: private host key: #0 type 1 RSA debug3: Not a RSA1 key file /etc/ssh/ssh_host_dsa_key. debug1: read PEM private key done: type DSA debug1: private host key: #1 type 2 DSA debug1: rexec_argv[0]='/usr/sbin/sshd' debug1: rexec_argv[1]='-d' debug1: rexec_argv[2]='-d' debug1: rexec_argv[3]='-d' debug2: fd 3 setting O_NONBLOCK debug1: Bind to port 22 on 0.0.0.0. Server listening on 0.0.0.0 port 22. debug3: fd 4 is not O_NONBLOCK debug1: Server will not fork when running in debugging mode. debug3: send_rexec_state: entering fd = 7 config len 660 debug3: ssh_msg_send: type 0 debug3: send_rexec_state: done debug1: rexec start in 4 out 4 newsock 4 pipe -1 sock 7 debug1: inetd sockets after dupping: 3, 3 Connection from 192.168.1.65 port 36502 debug1: Client protocol version 2.0; client software version OpenSSH_4.3p2 Debian-9 debug1: match: OpenSSH_4.3p2 Debian-9 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_4.7p1 Debian-2 debug2: fd 3 setting O_NONBLOCK debug3: privsep user:group 100:65534 debug1: permanently_set_uid: 100/65534 debug1: list_hostkey_types: ssh-rsa,ssh-dss debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug2: kex_parse_kexinit: diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1 debug2: kex_parse_kexinit: ssh-rsa,ssh-dss debug2: kex_parse_kexinit: aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour128,arcfour256,arcfour,aes192-cbc,aes256-cbc,[EMAIL PROTECTED],aes128-ctr,aes192-ctr,aes256-ctr debug2: kex_parse_kexinit: aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour128,arcfour256,arcfour,aes192-cbc,aes256-cbc,[EMAIL PROTECTED],aes128-ctr,aes192-ctr,aes256-ctr debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,[EMAIL PROTECTED],hmac-ripemd160,[EMAIL PROTECTED],hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,[EMAIL PROTECTED],hmac-ripemd160,[EMAIL PROTECTED],hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: none,[EMAIL PROTECTED] debug2: kex_parse_kexinit: none,[EMAIL PROTECTED] debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: first_kex_follows 0 debug2: kex_parse_kexinit: reserved 0 debug2: kex_parse_kexinit: diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1 debug2: kex_parse_kexinit: ssh-rsa,ssh-dss debug2:
Re: DEFAULT_MMAP_MIN_ADDR change breaks ssh on arm
Hi Martin On Wed, Mar 19, 2008 at 11:46 AM, Martin Michlmayr [EMAIL PROTECTED] wrote: The following change r10769 | maks | 2008-03-10 17:03:03 +0100 (Mon, 10 Mar 2008) | 8 lines security: set DEFAULT_MMAP_MIN_ADDR to 65536 Low address space to protect from user allocation, see a5ecbcb8c13ea8a822d243bf782d0dc9525b4f84, runtime tunable on /proc/sys/vm/mmap_min_addr. let's see if we get any fallout. double checked after Kconfig recommendation that fedora uses that recommendation too. breaks ssh on arm. While root can still log in via ssh, normal users cannot. ssh almost manages to log in but when it comes to starting a shell the connection simply closes. Changing DEFAULT_MMAP_MIN_ADDR back to 0 fixes this. maks, should I simply set DEFAULT_MMAP_MIN_ADDR to 0 on ARM or should I report this to the SE Linux folks or someone else? I've no idea how SE Linux works, so any help is welcome. On the GLAN Tank, values larger than 32768 cause ssh to fail, whereas 32768 and lower allow ssh to work. However, it appears that the exploit CVE-2008-0600 is fixed in kernel versions 2.6.22.18 and above, 2.6.23.16 and above, 2.6.24.2 and above, and all 2.6.25 versions [1], so why can't we set DEFAULT_MMAP_MIN_ADDR to 0 for all architectures? Gordon [1] http://kerneltrap.org/Linux/Patching_CVE-2008-0600_Local_Root_Exploit -- Gordon Farquharson GnuPG Key ID: 32D6D676 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#471062: ixp4xx: stalls and I/O errors when reading and writing via NFS
Hi Martin On Tue, Mar 18, 2008 at 2:57 PM, Martin Michlmayr [EMAIL PROTECTED] wrote: OK, I can reproduce this with 2.6.24 on arm on a NSLU2. However, I don't see it with 2.6.25-rc6. Gordon, any idea how many changes there were between 2.6.24 and 2.6.25? I'll have to check. I'll try to look into this before the weekend. I should update the the network drive patch in 2.6.24 anyway to keep it in sync with Krzysztof's tree. Gordon -- Gordon Farquharson GnuPG Key ID: 32D6D676 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
