Bug#402253: linux-image-2.6.18-3-alpha-smp: i2c-elektor incorrectly marked as BROKEN_ON_SMP
Package: linux-image-2.6.18-3-alpha-smp Version: 2.6.18-7 Severity: normal Tags: patch Back around the release of 2.6, i2c-elektor was marked as BROKEN_ON_SMP for use of cli/sti: http://lkml.org/lkml/2003/8/26/239 At some point since then, the drive has been fixed, but it's still marked as broken. As this is the i2c chip for UP2000+ dual Alpha systems, it would be nice if it were enabled. Thanks, James Andrewartha --- linux-2.6/drivers/i2c/busses/Kconfig.orig 2006-05-31 10:31:44.0 +1000 +++ linux-2.6/drivers/i2c/busses/Kconfig2006-12-05 00:55:54.0 +1100 @@ -86,7 +86,7 @@ config I2C_AU1550 config I2C_ELEKTOR tristate "Elektor ISA card" - depends on I2C && ISA && BROKEN_ON_SMP + depends on I2C && ISA select I2C_ALGOPCF help This supports the PCF8584 ISA bus I2C adapter. Say Y if you own -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: alpha Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-3-alpha-smp Locale: LANG=en_AU, LC_CTYPE=en_AU (charmap=ISO-8859-1) Versions of packages linux-image-2.6.18-3-alpha-smp depends on: ii coreutils 5.97-5 The GNU core utilities ii debconf [debconf-2.0] 1.5.8 Debian configuration management sy ii initramfs-tools [linux-initra 0.85b tools for generating an initramfs ii module-init-tools 3.3-pre3-1 tools for managing Linux kernel mo ii yaird [linux-initramfs-tool] 0.0.12-18 Yet Another mkInitRD linux-image-2.6.18-3-alpha-smp recommends no packages. -- debconf information excluded -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#402094: marked as done (kernel-source-2.6.8: Intel drivers (net/e100.c, net/e1000/e1000_main.c))
Your message dated Fri, 8 Dec 2006 23:10:09 +0100 with message-id <[EMAIL PROTECTED]> and subject line This is not a vulnerability 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) --- Begin Message --- Package: kernel-source-2.6.8 Version: 2.6.8-16sarge5 Severity: critical Justification: root security hole Noticed: Intel LAN Driver Buffer Overflow Local Privilege Escalation http://support.intel.com/support/network/sb/CS-023726.htm The Intel blurb says Linux, and specifically Debian, is affected also: Product Family OS Affected Driver Versions Corrected Driver Versions Intel PRO 10/100 Adapters Linux* 3.5.14 or previous3.5.17 or later Intel PRO/1000 AdaptersLinux 7.2.7 or previous 7.3.15 or later and it seems that: kernel-source-2.6.8/drivers/net/e100.c #define DRV_NAME"e100" #define DRV_VERSION "3.0.18" #define DRV_DESCRIPTION "Intel(R) PRO/100 Network Driver" #define DRV_COPYRIGHT "Copyright(c) 1999-2004 Intel Corporation" kernel-source-2.6.8/drivers/net/e1000/e1000_main.c char e1000_driver_name[] = "e1000"; char e1000_driver_string[] = "Intel(R) PRO/1000 Network Driver"; char e1000_driver_version[] = "5.2.52-k4"; char e1000_copyright[] = "Copyright (c) 1999-2004 Intel Corporation."; are quite old (so seem to be affected). Cheers, Paul Szabo [EMAIL PROTECTED] http://www.maths.usyd.edu.au/u/psz/ School of Mathematics and Statistics University of SydneyAustralia -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.6.8-spm1.6 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages kernel-source-2.6.8 depends on: ii binutils 2.15-6 The GNU assembler, linker and bina ii bzip2 1.0.2-7high-quality block-sorting file co ii coreutils [fileutils] 5.2.1-2The GNU core utilities ii fileutils 5.2.1-2The GNU file management utilities --- End Message --- --- Begin Message --- This vulnerability does not affect GNU/Linux. The security information vendor providing this information refers to git commit 0eb5a34cdf34ad07b6db2df1e523aaf6574601b4 However, the overflow cannot be triggered by unprivileged users, so the whole issue is bogus. This information is confirmed by Intel people. Cheers, Moritz --- End Message ---
Bug#401979: DISCARD --> It works with 2.6.19
Hello again! It's NOT working now with 2.6.19. Perhaps something more is affecting cpufreq. I will try to isolate the cause after my exams. Best regards. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#401556: marked as done (DVD Burn Fails with strange behavior)
Your message dated Tue, 5 Dec 2006 15:32:34 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#401556: DVD Burn Fails with strange behavior 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) --- Begin Message --- package: linux-image version: 2.6-k7 severity: critical package: linux-image version: 2.6.16 severity: critical I'm not sure where to file this bug; it seems to be a problem with kernel drivers in the Etch kernels. This is the behavior: When burning dvd's, the first attempt fails with "irq interrupt", and the second attempt freezes the entire system with what appears to be a kernel panic. Restarting the system shows filesystem corruption on RAID5 devices requiring something like 6 - 18 hours of resyncing, although this is unclear whether it's a direct result of the bug in question, merely a byproduct of the system crash, or a combination of both. At the same time, numerous messages and boot problems emerge with dma interrupt requests and an unresponsive /dev/hdb causing subsequent boot attempts to fail; these seem to appear after attempting a burn (not positive, but pretty sure). The hdb drive is a Maxtor 250G only some 7 weeks old and otherwise works fine, showing no other problems or errors whatsoever. In all dummy/dry-run instances (multiple tests with guaranteed blank discs), wodim returns the error message "Cannot get next writable address for 'invisible' track. This means we are checking recorded media." Growisofs returns only "Excuting built-in dd...". I've checked lspci; all controllers are listed, and i've tried rearranging their boot order so that the ide controllers boot before the device controllers, but no difference. I've done lsmod; all necessary drivers are loaded. I've tried using automated programs like k3burner and gnomebaker; same effect or worse. I've checked and switched the cables with new ones; no difference. I've played with hdparm; dma on/off, -c and -u on/off. No changes in behavior. DVD Play and cd writing all work fine. The same system worked fine with sarge and the old cdrecord. The only conclusion i can come to is that this is a kernel-space bug in the drivers somewhere, and this seems reinforced by the fact that both growisofs and wodim freeze. I've googled this now for two weeks and come up with virtually nothing, although there seems to have been a flurry of questions similar to mine these last few weeks, and questions surrounding the 2.6.17kernels for a while now (1+ years?). I'm using an ASUS DRW-1608P: ATAPI CD-ROM, with removable media Model Number: ASUSDRW-1608P Serial Number: 55DM071946 Firmware Revision: 1.40 Standards: Likely used CD-ROM ATAPI-1 Configuration: DRQ response: 50us. Packet size: 12 bytes Capabilities: LBA, IORDY(can be disabled) Buffer size: 64.0kB DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 *udma4 Cycle time: min=120ns recommended=120ns PIO: pio0 pio1 pio2 pio3 pio4 Cycle time: no flow control=240ns IORDY flow control=120ns Commands/features: Enabled Supported: *Power Management feature set *PACKET command feature set *DEVICE_RESET command HW reset results: CBLID- above Vih Device num = 0 determined by the jumper lspci: 00:00.0 Host bridge: Advanced Micro Devices [AMD] AMD-760 [IGD4-1P] System Controller (rev 14) 00:01.0 PCI bridge: Advanced Micro Devices [AMD] AMD-760 [IGD4-1P] AGP Bridge 00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] (rev 40) 00:07.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) 00:07.2 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1Controller (rev 1a) 00:07.3 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1Controller (rev 1a) 00:07.4 SMBus: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev 40) 00:07.5 Multimedia audio controller: VIA Technologies, Inc. VT82C686 AC97 Audio Controller (rev 50) 00:0c.0 Ethernet controller: ADMtek NC100 Network Everywhere Fast Ethernet 10/100 (rev 11) 01:05.0 VGA compatible controller: nVidia Corporation NV11 [GeForce2 MX/MX 400] (rev b2) agora:/var/log# lsmod Module Size Used by snd_usb_audio 69472 1 snd_usb_lib14912 1 snd_usb_audio snd_hwdep 8964 1 snd_usb_audio binfmt_misc11272 1 ppdev 8772 0 lp 11108
Processed: reassign 400783 to linux-2.6, forcibly merging 389803 400783
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.9.26 > reassign 400783 linux-2.6 Bug#400783: Dom0 crashes with xen-linux-system-2.6.17-2-xen-686=2.6.17-9 Bug reassigned from package `linux-image-2.6.17-2-xen-686' to `linux-2.6'. > forcemerge 389803 400783 Bug#389803: linux-image-2.6.17-2-xen-686 - crashs with 4 guest domains Bug#400783: Dom0 crashes with xen-linux-system-2.6.17-2-xen-686=2.6.17-9 Bug#391448: xen-hypervisor-3.0-unstable-1-i386: dom0 crashes when starting the 3rd domU Bug#393451: linux-image-2.6.17-2-xen-k7: Kernel panic - not syncing: Fatal exception in interrupt && reboot Bug#399467: linux-image-2.6.17-2-xen-686: cannot boot more than one DomU OS with Xen 3.0-i386 / Debian GNU/Linux, kernel 2.6.17-2-xen-686 Forcibly Merged 389803 391448 393451 399467 400783. > 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#400783: Furthermore
Hi, One more thing! The crash appear for me "sometimes" during the first DomU creation. But now (why, I do not know), when I start the first DomU, it is ok. This is when I start the second DomU that I normaly have the crash. At start, I was thinking of and RAM issue. So I've put "dom0_mem=256M" parameter on kernel. Still cashes. So during the night, I've pass memtest86+ and no errors this morning. But the strange thing is that yesterday, the 2 DomU started correctly, but they where a crash when I've done a simple GET / on the webserver located on the second DomU. + -- Jean-luc Henry Systèmes, Veille, Rayonnement / Systems & FLOSS Advocate Techno Centre Logiciels Libres, http://www.tc2l.ca/ Téléphone : (418) 681-2929 #115
Bug#379090: preparation for 2.6.18-6 kernel upload on monday 20th of november 2006.
* Goswin von Brederlow ([EMAIL PROTECTED]) [061120 10:47]: > Bastian Blank <[EMAIL PROTECTED]> wrote: > > On Sat, Nov 18, 2006 at 07:12:49AM +0100, Goswin von Brederlow wrote: > > The patch breaks crosscompilation and other things. > > > | diff -u linux-2.6.16-2.6.16/debian/arch/i386/xen-vserver/defines > > linux-2.6.16-2.6.16/debian/arch/i386/xen-vserver/defines > > | --- linux-2.6.16-2.6.16/debian/arch/i386/xen-vserver/defines > > | +++ linux-2.6.16-2.6.16/debian/arch/i386/xen-vserver/defines > > | @@ -12 +12,9 @@ > > | +kernel-arch: i386 > > | > > | +[amd64] > > | +class: AMD64 / EM64T SMP > > | +longclass: 64bit multi-processor AMD Athlon64/Opteron / Intel EM64T > > models > > | +KPKG-ARCH: amd64 > > | +recommends: libc6-i686 > > | +kpkg-arch: amd64 > > > kpkg always gets the debian arch of the system it compiles for. > > Overwriting this is not allowed. > See also man make-kpkg: > > | The value should be whatever DEB_HOST_ARCH_CPU contains when > | dpkg-architecture is run on the target machine, or it can be an other > | architecture in a multi-arch set (like i386/amd64). > > Which is what we do here. Sounds sane. > Anyway, leave the xen stuff disabled if that makes problems for > you. As said in this bugreport before we probably don't need it. Good. > > | diff -u linux-2.6.16-2.6.16/debian/rules.real > > linux-2.6.16-2.6.16/debian/rules.real > > | --- linux-2.6.16-2.6.16/debian/rules.real > > | +++ linux-2.6.16-2.6.16/debian/rules.real > > | @@ -35,7 +35,11 @@ > > | # replaced by the flavour for which the command is run. > > | # > > | kpkg_image := make-kpkg > > | -kpkg_image += --arch '$(ARCH)' > > | +ifdef KPKG_ARCH > > | + kpkg_image += --arch '$(KPKG_ARCH)' --cross-compile='-' > > | +else > > | + kpkg_image += --arch '$(ARCH)' > > | +endif > > | kpkg_image += --stem linux > > | ifneq ($(INITRAMFS),False) > > |kpkg_image += --initrd > > > No. The cross compilation stuff is set intern and must not be overwriten > > by the rules. > > Yes it must. > > We are building for a multi-arch set here and the synatx for that is > to set the architecture but not to cross-compile. --cross-compile='-' > does that. The man page tells: --cross-compile foo This is useful for setting the target string when you are cross compiling. Use the dummy target "-" if you are building for other arches of a multiarch set, like i386/amd64. The supports Goswins view. There is however one negative side-effect: You cannot crosscompile i386-kernel-package anymore. It might be better to set --cross-compile to the right value for i386 - but that shouldn't block application of this patch. Goswin, I expect you actually tested this patch on an i386, and it returned proper kernels (i.e. you tried at least one of them). If so, I think this patch is now in a state where it can be applied. Cheers, Andi -- http://home.arcor.de/andreas-barth/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#400783: Bug confirmation
Hi, I'm confirming having this bug too! Using Xen on IBM x345 (4Gb RAM), Debian Etch default installation. # dpkg -l |grep -i xen ii libc6-xen 2.3.6.ds1-8 ii linux-image-2.6-xen-686 2.6.17+2 ii linux-image-2.6.17-2-xen-686 2.6.17-9 ii linux-image-xen-686 2.6.17+2 ii linux-modules-2.6.17-2-xen-6862.6.17-9 ii xen-hypervisor-3.0.3-1-i386 3.0.3-0-2 ii xen-tools 2.8-2 ii xen-utils-3.0.3-1 3.0.3-0-2 ii xen-utils-common 3.0.3-0-2 Grub: title Xen 3.0.3-1-i386 / Debian GNU/Linux, kernel 2.6.17-2-xen-686 root(hd0,0) kernel /xen-3.0.3-1-i386.gz dom0_mem=256M noreboot module /vmlinuz-2.6.17-2-xen-686 root=/dev/mapper/internet-root ro console=tty0 module /initrd.img-2.6.17-2-xen-686 savedefault Example of configuration # cat /etc/xen/vs-svrInternet.conf kernel = '/boot/vmlinuz-2.6.17-2-xen-686' ramdisk = '/boot/initrd.img-2.6.17-2-xen-686' memory = 1024 name = 'svrinternet' #vif = [ 'ip=10.0.0.101' ] disk = [ 'file:/srv/data/xen/xen_internet_sys_domU.img,sda1,w', 'file:/srv/data/xen/xen_internet_srv_domU.img,sda2,w', 'file:/srv/data/xen/xen_internet_swap_domU.img,sda3,w' ] root = '/dev/sda1 ro' Any idea are welcome as the system need to be in production next week...? A+ -- Jean-luc Henry Systèmes, Veille, Rayonnement / Systems & FLOSS Advocate Techno Centre Logiciels Libres, http://www.tc2l.ca/ Téléphone : (418) 681-2929 #115
System freeze with linux-image-2.6.18-3-686 (version 2.6.18-7)
Hi, On a Debian GNU/Linux system with packages from the 'testing' distribution and 'linux-image-2.6' from 'unstable' I get the system freeze after 10-20 minutes when the screen saver 'Pop art squares' on Gnome is started. I cannot see anything in the system log regarding this problem. How can I found the problem and offer more information? Thanks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#401865: marked as done (linux-image-2.6.18-3-686: post-removal script returns error exit status 128)
Your message dated Fri, 8 Dec 2006 11:58:35 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#401865: linux-image-2.6.18-3-686: post-removal script
returns error exit status 128
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)
--- Begin Message ---
Package: linux-image-2.6.18-3-686
Version: 2.6.18-7
Severity: normal
I tried to completely remove the package (with --purge option) but the
configuration files remain. This problem is found on builds 6 and 7.
MICU:~# aptitude purge linux-image-2.6.18-3-686
Reading package lists... Done
Building dependency tree... Done
Reading extended state information
Initializing package states... Done
Reading task descriptions... Done
Building tag database... Done
The following packages will be REMOVED:
linux-image-2.6.18-3-686{p}
0 packages upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
Need to get 0B of archives. After unpacking 50.8MB will be freed.
Do you want to continue? [Y/n/?]
Writing extended state information... Done
(Reading database ... 117949 files and directories currently installed.)
Removing linux-image-2.6.18-3-686 ...
Running postrm hook script /sbin/update-grub.
Searching for GRUB installation directory ... found: /boot/grub
Testing for an existing GRUB menu.lst file ... found:
/boot/grub/menu.lst
Searching for splash image ... none found, skipping ...
Found kernel: /boot/vmlinuz-2.6.17-2-686
Updating /boot/grub/menu.lst ... done
The link /vmlinuz is a damaged link
Removing symbolic link vmlinuz
Unless you used the optional flag in lilo,
you may need to re-run your boot loader[lilo]
The link /initrd.img is a damaged link
Removing symbolic link initrd.img
Unless you used the optional flag in lilo,
you may need to re-run your boot loader[lilo]
Purging configuration files for linux-image-2.6.18-3-686 ...
Running postrm hook script /sbin/update-grub.
Searching for GRUB installation directory ... found: /boot/grub
Testing for an existing GRUB menu.lst file ... found:
/boot/grub/menu.lst
Searching for splash image ... none found, skipping ...
Found kernel: /boot/vmlinuz-2.6.17-2-686
Updating /boot/grub/menu.lst ... done
dpkg: error processing linux-image-2.6.18-3-686 (--purge):
subprocess post-removal script returned error exit status 128
Errors were encountered while processing:
linux-image-2.6.18-3-686
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install. Trying to recover:
-- System Information:
Debian Release: 4.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-2-686
Locale: LANG=ro_RO.UTF-8, LC_CTYPE=ro_RO.UTF-8 (charmap=UTF-8)
Versions of packages linux-image-2.6.18-3-686 depends on:
ii coreutils 5.97-5 The GNU core utilities
ii debconf [debconf-2.0] 1.5.8 Debian configuration management sy
ii initramfs-tools [linux-initra 0.85b tools for generating an initramfs
ii module-init-tools 3.3-pre3-1 tools for managing Linux kernel mo
Versions of packages linux-image-2.6.18-3-686 recommends:
ii libc6-i686 2.3.6.ds1-8 GNU C Library: Shared libraries [i
-- debconf information:
shared/kernel-image/really-run-bootloader: true
linux-image-2.6.18-3-686/postinst/bootloader-error-2.6.18-3-686:
linux-image-2.6.18-3-686/postinst/old-dir-initrd-link-2.6.18-3-686: true
linux-image-2.6.18-3-686/postinst/kimage-is-a-directory:
linux-image-2.6.18-3-686/preinst/elilo-initrd-2.6.18-3-686: true
linux-image-2.6.18-3-686/postinst/old-system-map-link-2.6.18-3-686: true
linux-image-2.6.18-3-686/preinst/lilo-initrd-2.6.18-3-686: true
linux-image-2.6.18-3-686/postinst/depmod-error-initrd-2.6.18-3-686: false
linux-image-2.6.18-3-686/preinst/bootloader-initrd-2.6.18-3-686: true
linux-image-2.6.18-3-686/prerm/removing-running-kernel-2.6.18-3-686: true
linux-image-2.6.18-3-686/postinst/create-kimage-link-2.6.18-3-686: true
linux-image-2.6.18-3-686/prerm/would-invalidate-boot-loader-2.6.18-3-686: true
linux-image-2.6.18-3-686/preinst/abort-install-2.6.18-3-686:
linux-image-2.6.18-3-686/preinst/overwriting-modules-2.6.18-3-686: true
linux-image-2.6.18-3-686/preinst/initrd-2.6.18-3-686:
linux-image-2.6.18-3-686/preinst/lilo-has-ramdisk:
linux-image-2.6.18-3-686/preinst/already-running-this-2.6.18-3-686:
linux-image-2.6.18-3-686/postinst/bootloader-test-error-2.6.18-3-686:
linux-image-2.6.18-3-686/preinst/abort-overwrite-2.6.18-3-686:
linux-image-2.6.18-3-686/postinst/
Scheduling 2.6.18-8
Hi folks I intend to schedule 2.6.18-8 for sunday. It includes the updates 2.6.18.4 and 2.6.18.5 and fixes the generated dependencies for the upgrade path. Bastian -- It is a human characteristic to love little animals, especially if they're attractive in some way. -- McCoy, "The Trouble with Tribbles", stardate 4525.6 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#398948: intel console framebuffer (i810fb or intelfb) does not work
Hi Maximilian, I have exactly the same problems. > this is old use 2.6.18 from sid, > will just install fine on testing. What do you mean? I have the most current linux image on Etch here, same problem. dmesg output is below. Olaf Linux version 2.6.17-2-686 (Debian 2.6.17-9) ([EMAIL PROTECTED]) (gcc version 4.1.2 20060901 (prerelease) (Debian 4.1.1-13)) #1 SMP Wed Sep 13 16:34:10 UTC 2006 BIOS-provided physical RAM map: BIOS-e820: - 000a (usable) BIOS-e820: 000f - 0010 (reserved) BIOS-e820: 0010 - 1f688c00 (usable) BIOS-e820: 1f688c00 - 1f68ac00 (ACPI NVS) BIOS-e820: 1f68ac00 - 1f68cc00 (ACPI data) BIOS-e820: 1f68cc00 - 2000 (reserved) BIOS-e820: e000 - f000 (reserved) BIOS-e820: fec0 - fed00400 (reserved) BIOS-e820: fed2 - feda (reserved) BIOS-e820: fee0 - fef0 (reserved) BIOS-e820: ffb0 - 0001 (reserved) 0MB HIGHMEM available. 502MB LOWMEM available. found SMP MP-table at 000fe710 On node 0 totalpages: 128648 DMA zone: 4096 pages, LIFO batch:0 Normal zone: 124552 pages, LIFO batch:31 DMI 2.3 present. ACPI: RSDP (v000 DELL ) @ 0x000fec00 ACPI: RSDT (v001 DELLDV051 0x0007 ASL 0x0061) @ 0x000fcc50 ACPI: FADT (v001 DELLDV051 0x0007 ASL 0x0061) @ 0x000fcc8c ACPI: SSDT (v001 DELLst_ex 0x1000 MSFT 0x010d) @ 0xfffc858f ACPI: MADT (v001 DELLDV051 0x0007 ASL 0x0061) @ 0x000fcd00 ACPI: BOOT (v001 DELLDV051 0x0007 ASL 0x0061) @ 0x000fcd92 ACPI: MCFG (v001 DELLDV051 0x0007 ASL 0x0061) @ 0x000fcdba ACPI: HPET (v001 DELLDV051 0x0007 ASL 0x0061) @ 0x000fcdf8 ACPI: DSDT (v001 DELLdt_ex 0x1000 MSFT 0x010d) @ 0x ACPI: PM-Timer IO Port: 0x808 ACPI: Local APIC address 0xfee0 ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) Processor #0 15:4 APIC version 20 ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] disabled) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x06] disabled) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x02] disabled) ACPI: LAPIC (acpi_id[0x05] lapic_id[0x04] disabled) ACPI: LAPIC (acpi_id[0x06] lapic_id[0x07] disabled) ACPI: LAPIC (acpi_id[0x07] lapic_id[0x03] disabled) ACPI: LAPIC (acpi_id[0x08] lapic_id[0x05] disabled) ACPI: LAPIC_NMI (acpi_id[0xff] high level lint[0x1]) ACPI: IOAPIC (id[0x08] address[0xfec0] gsi_base[0]) IOAPIC[0]: apic_id 8, version 32, 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 high 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 ACPI: HPET id: 0x8086a201 base: 0xfed0 Using ACPI (MADT) for SMP configuration information Allocating PCI resources starting at 3000 (gap: 2000:c000) Built 1 zonelists Kernel command line: BOOT_IMAGE=Linux ro root=803 reboot=warm video=intelfb:[EMAIL PROTECTED] splash=silent 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: 2048 (order: 11, 8192 bytes) Console: colour VGA+ 80x25 Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) Memory: 502816k/514592k available (1482k kernel code, 11356k reserved, 544k data, 196k init, 0k highmem) Checking if this processor honours the WP bit even in supervisor mode... Ok. hpet0: at MMIO 0xfed0 (virtual 0xd000), IRQs 2, 8, 0 hpet0: 3 64-bit timers, 14318180 Hz Using HPET for base-timer Using HPET for gettimeofday Detected 3059.102 MHz processor. Using hpet for high-res timesource Calibrating delay using timer specific routine.. 6123.76 BogoMIPS (lpj=12247536) Security Framework v1.0.0 initialized SELinux: Disabled at boot. Capability LSM initialized Mount-cache hash table entries: 512 CPU: After generic identify, caps: bfebfbff 2010 651d 0001 CPU: After vendor identify, caps: bfebfbff 2010 651d 0001 monitor/mwait feature present. using mwait in idle threads. CPU: Trace cache: 12K uops, L1 D cache: 16K CPU: L2 cache: 256K CPU: Hyper-Threading is disabled CPU: After all inits, caps: bfebfbff 2010 0180 651d 0001 Intel machine check architecture supported. Intel machine check reporting enabled on CPU#0. CPU0: Intel P4/Xeon Extended MCE MSRs (24) available CPU0: Thermal monitoring enabled Checking 'hlt' instruction... OK. SMP alternatives: switching to UP code Freeing SMP alternatives: 16k freed CPU0: Intel(R) Celeron(R) CPU 3.06GHz stepping 09 Total of 1 processors acti
