Menu
▾
▴
colinux-users — coLinux users mailing list
You can subscribe to this list here.
| 2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(100) |
Jun
(134) |
Jul
(149) |
Aug
(123) |
Sep
(185) |
Oct
(122) |
Nov
(59) |
Dec
(127) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2005 |
Jan
(128) |
Feb
(233) |
Mar
(210) |
Apr
(196) |
May
(85) |
Jun
(96) |
Jul
(76) |
Aug
(149) |
Sep
(65) |
Oct
(78) |
Nov
(121) |
Dec
(82) |
| 2006 |
Jan
(249) |
Feb
(181) |
Mar
(176) |
Apr
(156) |
May
(128) |
Jun
(102) |
Jul
(157) |
Aug
(80) |
Sep
(42) |
Oct
(49) |
Nov
(36) |
Dec
(42) |
| 2007 |
Jan
(64) |
Feb
(38) |
Mar
(45) |
Apr
(74) |
May
(26) |
Jun
(20) |
Jul
(17) |
Aug
(12) |
Sep
(40) |
Oct
(7) |
Nov
(14) |
Dec
(16) |
| 2008 |
Jan
(52) |
Feb
(49) |
Mar
(90) |
Apr
(80) |
May
(78) |
Jun
(82) |
Jul
(25) |
Aug
(8) |
Sep
(10) |
Oct
(11) |
Nov
(3) |
Dec
(17) |
| 2009 |
Jan
(12) |
Feb
(16) |
Mar
(20) |
Apr
(14) |
May
(17) |
Jun
(10) |
Jul
(13) |
Aug
(12) |
Sep
(21) |
Oct
(10) |
Nov
(30) |
Dec
(1) |
| 2010 |
Jan
(2) |
Feb
(7) |
Mar
(22) |
Apr
(6) |
May
(33) |
Jun
(5) |
Jul
(4) |
Aug
(38) |
Sep
(46) |
Oct
(23) |
Nov
(9) |
Dec
(5) |
| 2011 |
Jan
(21) |
Feb
(27) |
Mar
(1) |
Apr
(18) |
May
(12) |
Jun
(12) |
Jul
(10) |
Aug
(30) |
Sep
(4) |
Oct
|
Nov
(9) |
Dec
(19) |
| 2012 |
Jan
(26) |
Feb
(6) |
Mar
(8) |
Apr
(7) |
May
(3) |
Jun
|
Jul
(10) |
Aug
(1) |
Sep
(18) |
Oct
(5) |
Nov
|
Dec
(1) |
| 2013 |
Jan
(27) |
Feb
|
Mar
(11) |
Apr
(14) |
May
|
Jun
(1) |
Jul
|
Aug
(7) |
Sep
|
Oct
(1) |
Nov
(2) |
Dec
|
| 2014 |
Jan
|
Feb
|
Mar
|
Apr
(25) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2015 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
(1) |
Aug
|
Sep
(1) |
Oct
|
Nov
(2) |
Dec
|
| 2016 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
| 2017 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(2) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2024 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2025 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(2) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Mike F. <vap...@gm...> - 2008-06-22 21:12:37
|
On Sun, Jun 22, 2008 at 4:59 PM, Henry Nestler wrote: > Mike Frysinger wrote: >> On Sun, Jun 22, 2008 at 3:51 PM, Henry Nestler wrote: >>> Mike Frysinger wrote: >>>> On Sun, Jun 15, 2008 at 2:16 AM, Mike Frysinger wrote: >>>>> for some reason, the incoming packets from the tftp client as seen by >>>>> colinux have the gateway's ip (10.0.2.2) instead of the real ip >>>>> (192.168.0.17) ... any hints as to what's going wrong here ? >>>>> >>>>> taking a step back and just hitting colinux with netcat shows the same >>>>> behavior. connecting to a tcp forwarded port and things look good >>>>> (the source ip is the real client, not the gateway). connecting to a >>>>> udp forwarded port and things look bad (the source ip is the gateway >>>>> instead of the real client). >>>> i noticed that there's a standalone exe called >>>> 'colinux-slirp-net-daemon.exe', so on a hunch i copied the one from >>>> 0.7.1 to 0.7.3 and when i rebooted, the network communication for UDP >>>> forwarded ports started working again ... guess it's a bug in the >>>> slirp daemon ? >>> In Version 0.7.2 the builtin TFTP-server was disabled. This server was a >>> host only server and opens files on the Windows side. This should have >>> nothing to do with the redirections. I hope, that is not the problem here. >>> >>> I have build a slirp version with enabled builtin TFTP-server: >>> http://www.henrynestler.com/colinux/testing/stable-0.7.3/20080622-slirp/ >>> >>> Please test this. >> >> doesnt seem to make a difference :( > > OK. That is very nice. So, I know, that this change was not the problem. > > The difference for coLinux 0.7.1 and 0.7.3 are very small. Mostly are > fixups for compiler warnings. > > There exist an other interesting change between versions: > http://colinux.svn.sourceforge.net/viewvc/colinux?view=rev&revision=574 > > This sets the 10.0.2.2 as source for broardcasts. Perhaps somethin is > wrong there? I will check it with netcat and tcpdump next times. i'm building the devel branch now (./configure && make) so i can go back through the versions the easy test is to run `tcpdump` in colinux and then just connect with netcat from another machine: nc -u colinux 69 <<<"MOO" a broken system will show the packet coming from 10.0.2.x rather than the real host -mike |
|
From: Henry N. <hen...@ar...> - 2008-06-22 20:57:33
|
Mike Frysinger wrote: > On Sun, Jun 22, 2008 at 3:51 PM, Henry Nestler wrote: >> Mike Frysinger wrote: >>> On Sun, Jun 15, 2008 at 2:16 AM, Mike Frysinger wrote: >>>> for some reason, the incoming packets from the tftp client as seen by >>>> colinux have the gateway's ip (10.0.2.2) instead of the real ip >>>> (192.168.0.17) ... any hints as to what's going wrong here ? >>>> >>>> taking a step back and just hitting colinux with netcat shows the same >>>> behavior. connecting to a tcp forwarded port and things look good >>>> (the source ip is the real client, not the gateway). connecting to a >>>> udp forwarded port and things look bad (the source ip is the gateway >>>> instead of the real client). >>> i noticed that there's a standalone exe called >>> 'colinux-slirp-net-daemon.exe', so on a hunch i copied the one from >>> 0.7.1 to 0.7.3 and when i rebooted, the network communication for UDP >>> forwarded ports started working again ... guess it's a bug in the >>> slirp daemon ? >> In Version 0.7.2 the builtin TFTP-server was disabled. This server was a >> host only server and opens files on the Windows side. This should have >> nothing to do with the redirections. I hope, that is not the problem here. >> >> I have build a slirp version with enabled builtin TFTP-server: >> http://www.henrynestler.com/colinux/testing/stable-0.7.3/20080622-slirp/ >> >> Please test this. > > doesnt seem to make a difference :( OK. That is very nice. So, I know, that this change was not the problem. The difference for coLinux 0.7.1 and 0.7.3 are very small. Mostly are fixups for compiler warnings. There exist an other interesting change between versions: http://colinux.svn.sourceforge.net/viewvc/colinux?view=rev&revision=574 This sets the 10.0.2.2 as source for broardcasts. Perhaps somethin is wrong there? I will check it with netcat and tcpdump next times. -- Henry N. |
|
From: Mike F. <vap...@gm...> - 2008-06-22 20:23:29
|
On Sun, Jun 22, 2008 at 3:51 PM, Henry Nestler wrote: > Mike Frysinger wrote: >> On Sun, Jun 15, 2008 at 2:16 AM, Mike Frysinger wrote: >>> for some reason, the incoming packets from the tftp client as seen by >>> colinux have the gateway's ip (10.0.2.2) instead of the real ip >>> (192.168.0.17) ... any hints as to what's going wrong here ? >>> >>> taking a step back and just hitting colinux with netcat shows the same >>> behavior. connecting to a tcp forwarded port and things look good >>> (the source ip is the real client, not the gateway). connecting to a >>> udp forwarded port and things look bad (the source ip is the gateway >>> instead of the real client). >> >> i noticed that there's a standalone exe called >> 'colinux-slirp-net-daemon.exe', so on a hunch i copied the one from >> 0.7.1 to 0.7.3 and when i rebooted, the network communication for UDP >> forwarded ports started working again ... guess it's a bug in the >> slirp daemon ? > > In Version 0.7.2 the builtin TFTP-server was disabled. This server was a > host only server and opens files on the Windows side. This should have > nothing to do with the redirections. I hope, that is not the problem here. > > I have build a slirp version with enabled builtin TFTP-server: > http://www.henrynestler.com/colinux/testing/stable-0.7.3/20080622-slirp/ > > Please test this. doesnt seem to make a difference :( based on your comments, i also enabled port forwarding on 1234, but i saw the same misbehavior between 0.7.1 and 0.7.3 (and your test version) -mike |
|
From: Henry N. <hen...@ar...> - 2008-06-22 19:49:39
|
Mike Frysinger wrote: > On Sun, Jun 15, 2008 at 2:16 AM, Mike Frysinger wrote: >> for some reason, the incoming packets from the tftp client as seen by >> colinux have the gateway's ip (10.0.2.2) instead of the real ip >> (192.168.0.17) ... any hints as to what's going wrong here ? >> >> taking a step back and just hitting colinux with netcat shows the same >> behavior. connecting to a tcp forwarded port and things look good >> (the source ip is the real client, not the gateway). connecting to a >> udp forwarded port and things look bad (the source ip is the gateway >> instead of the real client). > > i noticed that there's a standalone exe called > 'colinux-slirp-net-daemon.exe', so on a hunch i copied the one from > 0.7.1 to 0.7.3 and when i rebooted, the network communication for UDP > forwarded ports started working again ... guess it's a bug in the > slirp daemon ? Thank for your comments. In Version 0.7.2 the builtin TFTP-server was disabled. This server was a host only server and opens files on the Windows side. This should have nothing to do with the redirections. I hope, that is not the problem here. I have build a slirp version with enabled builtin TFTP-server: http://www.henrynestler.com/colinux/testing/stable-0.7.3/20080622-slirp/ Please test this. -- Henry N. |
|
From: Michelangelo B. <mic...@gm...> - 2008-06-21 16:16:45
|
On 6/20/08, Paolo Minazzi <pao...@gm...> wrote:
>
> Hi Jonathan,
> can you do an other simple test ?
>
> Run colinux on vista.
> ************************
> Then digit :
>
> # n1=$(cat /proc/interrupts | grep "0:" | awk '{ print $2 }')
>
> wait <n> seconds on you hand-clock (Don't use sleep command ! we are
> studying the PC timer taht seems broken! ). Then exec a new command
>
> # n2=$(cat /proc/interrupts | grep "0:" | awk '{ print $2 }')
>
> Now digit
> # echo $(expr $n2 - $n1)
>
> Get the value and divide it by <n>.
>
> You should have a value very closed to 100. Is it ?
>
>
> Run an other linux distribution that works
> ***********************************************
> Use the same procedure written above.
>
> You should have 100 or 1000 (or 250) .... Depends on the HZ defined
> into kernel ....
> What is the value you see ?
>
> Bye,
>
> Paolo
>
>
> -------------------------------------------------------------------------
I've got a Athlon64 x2 with same bios problem (which it had not before last
bios update). I can confirm Ubuntu 7.10 did not pass booting without
acpi=off parameter.
Should this help debugging I can send more data|run some test.
My 2 c
Michelangelo
|
|
From: Paolo M. <pao...@gm...> - 2008-06-20 07:17:50
|
Hi Jonathan,
can you do an other simple test ?
Run colinux on vista.
************************
Then digit :
# n1=$(cat /proc/interrupts | grep "0:" | awk '{ print $2 }')
wait <n> seconds on you hand-clock (Don't use sleep command ! we are
studying the PC timer taht seems broken! ). Then exec a new command
# n2=$(cat /proc/interrupts | grep "0:" | awk '{ print $2 }')
Now digit
# echo $(expr $n2 - $n1)
Get the value and divide it by <n>.
You should have a value very closed to 100. Is it ?
Run an other linux distribution that works
***********************************************
Use the same procedure written above.
You should have 100 or 1000 (or 250) .... Depends on the HZ defined
into kernel ....
What is the value you see ?
Bye,
Paolo
|
|
From: Jonathan D. <tz...@sp...> - 2008-06-20 02:08:06
|
s used for memmap
Normal zone: 223520 pages, LIFO batch:31
HighMem zone: 4095 pages used for memmap
HighMem zone: 520113 pages, LIFO batch:31
Movable zone: 0 pages used for memmap
DMI 2.4 present.
ACPI: RSDP 000FE0B0, 0024 (r2 HP )
ACPI: XSDT B7FC81B8, 005C (r1 HPQOEM SLIC-MPC 1 HP 1)
ACPI: FACP B7FC8084, 00F4 (r4 HP 0944 3 HP 1)
ACPI Error (tbfadt-0453): 32/64X address mismatch in "Pm2ControlBlock": [00008800] [0000000000008100], using 64X [20070126]
ACPI: DSDT B7FC8498, 1193C (r1 HP SB400 10000 MSFT 3000001)
ACPI: FACS B7FE7D80, 0040
ACPI: SLIC B7FC8214, 0176 (r1 HPQOEM SLIC-MPC 1 HP 1)
ACPI: EPTH B7FC838C, 0038 (r1 HP 0944 1 HP 1)
ACPI: APIC B7FC83C4, 0062 (r1 HP 0944 1 HP 1)
ACPI: MCFG B7FC8428, 003C (r1 HP 0944 1 HP 1)
ACPI: TCPA B7FC8464, 0032 (r2 HP 0944 1 HP 1)
ACPI: SSDT B7FD9DD4, 0206 (r1 HP PSSTBLID 1 HP 1)
ACPI: DMI detected: Hewlett-Packard
ATI board detected. Disabling timer routing over 8254.
ACPI: PM-Timer IO Port: 0x8008
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
Processor #0 15:8 APIC version 16
ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
Processor #1 15:8 APIC version 16
ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
IOAPIC[0]: apic_id 2, version 33, address 0xfec00000, 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 c2000000 (gap: c0000000:20000000)
swsusp: Registered nosave memory region: 000000000009f000 - 00000000000a0000
swsusp: Registered nosave memory region: 00000000000a0000 - 00000000000e0000
swsusp: Registered nosave memory region: 00000000000e0000 - 0000000000100000
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 747697
Kernel command line: ramdisk_size=100000 init=/etc/init lang=us apm=power-off vga=791 initrd=minirt.gz nomce highres=off loglevel=0 libata.atapi_enabled=1 quiet SELINUX_INIT=NO nmi_watchdog=0 BOOT_IMAGE=knoppix BOOT_IMAGE=linux
mapped APIC to ffffb000 (fee00000)
mapped IOAPIC to ffffa000 (fec00000)
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
PID hash table entries: 4096 (order: 12, 16384 bytes)
Detected 1995.340 MHz processor.
Console: colour dummy device 80x25
console [tty0] enabled
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Memory: 2981344k/3014336k available (3742k kernel code, 31664k reserved, 1262k data, 420k init, 2096832k highmem)
virtual kernel memory layout:
fixmap : 0xffe13000 - 0xfffff000 (1968 kB)
pkmap : 0xff800000 - 0xffc00000 (4096 kB)
vmalloc : 0xf8800000 - 0xff7fe000 ( 111 MB)
lowmem : 0xc0000000 - 0xf8000000 ( 896 MB)
.init : 0xc05ea000 - 0xc0653000 ( 420 kB)
.data : 0xc04a78c8 - 0xc05e327c (1262 kB)
.text : 0xc0100000 - 0xc04a78c8 (3742 kB)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay using timer specific routine.. 3998.26 BogoMIPS (lpj=6661217)
Security Framework initialized
SELinux: Initializing.
SELinux: Starting in permissive mode
selinux_register_security: Registering secondary module capability
Capability LSM initialized as secondary
Mount-cache hash table entries: 512
CPU: After generic identify, caps: 178bfbff ebd3fbff 00000000 00000000 00002001 00000000 0000011f 00000000
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 512K (64 bytes/line)
CPU 0(2) -> Core 0
CPU: After all inits, caps: 178bfbff ebd3fbff 00000000 00000410 00002001 00000000 0000011f 00000000
Compat vDSO mapped to ffffe000.
Checking 'hlt' instruction... OK.
Checking for popad bug... OK.
SMP alternatives: switching to UP code
ACPI: Core revision 20070126
CPU0: AMD Turion(tm) 64 X2 Mobile Technology TL-60 stepping 02
SMP alternatives: switching to SMP code
Booting processor 1/1 eip 3000
Initializing CPU#1
Calibrating delay using timer specific routine.. 3991.02 BogoMIPS (lpj=6649635)
CPU: After generic identify, caps: 178bfbff ebd3fbff 00000000 00000000 00002001 00000000 0000011f 00000000
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 512K (64 bytes/line)
CPU 1(2) -> Core 1
AMD C1E detected late. Force timer broadcast.
CPU: After all inits, caps: 178bfbff ebd3fbff 00000000 00000410 00002001 00000000 0000011f 00000000
CPU1: AMD Turion(tm) 64 X2 Mobile Technology TL-60 stepping 02
Total of 2 processors activated (7989.28 BogoMIPS).
ENABLING IO-APIC IRQs
..TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1
..MP-BIOS bug: 8254 timer not connected to IO-APIC
...trying to set up timer (IRQ0) through the 8259A ... failed.
...trying to set up timer as Virtual Wire IRQ... works.
Brought up 2 CPUs
net_namespace: 64 bytes
HP Compaq Laptop series board detected. Selecting BIOS-method for reboots.
Booting paravirtualized kernel on bare hardware
NET: Registered protocol family 16
EISA bus registered
ACPI: bus type pci registered
PCI: Using MMCONFIG
Setting up standard PCI resources
ACPI: EC: Look up EC in DSDT
ACPI: EC: non-query interrupt received, switching to interrupt mode
ACPI: Interpreter enabled
ACPI: (supports S0 S3 S4 S5)
ACPI: Using IOAPIC for interrupt routing
ACPI: EC: GPE = 0x11, I/O: command/status = 0x66, data = 0x62
ACPI: EC: driver started in interrupt mode
ACPI: PCI Root Bridge [C08B] (0000:00)
PCI: Transparent bridge - 0000:00:14.4
ACPI: PCI Interrupt Routing Table [\_SB_.C08B._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.C08B.C08C._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.C08B.C0FC._PRT]
ACPI: PCI Interrupt Link [C145] (IRQs 10 11) *0, disabled.
ACPI: PCI Interrupt Link [C146] (IRQs 10 11) *0, disabled.
ACPI: PCI Interrupt Link [C147] (IRQs 10 11) *0, disabled.
ACPI: PCI Interrupt Link [C148] (IRQs 10 11) *0, disabled.
ACPI: PCI Interrupt Link [C149] (IRQs 10 11) *0, disabled.
ACPI: PCI Interrupt Link [C14A] (IRQs 9) *0, disabled.
ACPI: PCI Interrupt Link [C14B] (IRQs 10 11) *0, disabled.
ACPI: PCI Interrupt Link [C14C] (IRQs 10 11) *0, disabled.
ACPI: Power Resource [C171] (off)
ACPI: Power Resource [C231] (off)
ACPI: Power Resource [C24D] (on)
ACPI: Power Resource [C397] (off)
ACPI: Power Resource [C398] (off)
ACPI: Power Resource [C399] (off)
ACPI: Power Resource [C39A] (off)
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI init
ACPI: bus type pnp registered
pnp: PnP ACPI: found 14 devices
ACPI: ACPI bus type pnp unregistered
PnPBIOS: Disabled by ACPI PNP
SCSI subsystem initialized
libata version 3.00 loaded.
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
PCI: Using ACPI for IRQ routing
PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report
PCI: Cannot allocate resource region 0 of device 0000:00:14.2
ACPI: RTC can wake from S4
system 00:00: iomem range 0x0-0x9ffff could not be reserved
system 00:00: iomem range 0xe0000-0xfffff could not be reserved
system 00:00: iomem range 0x100000-0xffffffff could not be reserved
system 00:0a: ioport range 0x40b-0x40b has been reserved
system 00:0a: ioport range 0x4d0-0x4d1 has been reserved
system 00:0a: ioport range 0x4d6-0x4d6 has been reserved
system 00:0a: ioport range 0x500-0x51f has been reserved
system 00:0a: ioport range 0xc00-0xc01 has been reserved
system 00:0a: ioport range 0xc14-0xc14 has been reserved
system 00:0a: ioport range 0xc50-0xc51 has been reserved
system 00:0a: ioport range 0xc52-0xc52 has been reserved
system 00:0a: ioport range 0xc6c-0xc6c has been reserved
system 00:0a: ioport range 0xc6f-0xc6f has been reserved
system 00:0a: ioport range 0xcd0-0xcdf has been reserved
system 00:0a: iomem range 0xffb00000-0xffbfffff could not be reserved
system 00:0a: iomem range 0xfff00000-0xffffffff could not be reserved
system 00:0c: ioport range 0x8000-0x802f has been reserved
system 00:0c: ioport range 0x8100-0x811f has been reserved
system 00:0c: iomem range 0xe0000000-0xefffffff could not be reserved
system 00:0c: iomem range 0xfec00000-0xfec000ff could not be reserved
system 00:0c: iomem range 0xfed45000-0xfed8ffff has been reserved
system 00:0d: iomem range 0xcd400-0xcffff has been reserved
system 00:0d: iomem range 0x0-0x7ffffff could not be reserved
system 00:0d: iomem range 0xfee00000-0xfee00fff has been reserved
PCI: Bridge: 0000:00:01.0
IO window: 4000-4fff
MEM window: d0400000-d05fffff
PREFETCH window: c0000000-c7ffffff
PCI: Bridge: 0000:00:04.0
IO window: disabled.
MEM window: d0000000-d00fffff
PREFETCH window: disabled.
PCI: Bridge: 0000:00:05.0
IO window: 2000-3fff
MEM window: cc000000-cfffffff
PREFETCH window: disabled.
PCI: Bridge: 0000:00:06.0
IO window: disabled.
MEM window: c8000000-c80fffff
PREFETCH window: disabled.
PCI: Bus 3, cardbus bridge: 0000:02:04.0
IO window: 00001000-000010ff
IO window: 00001400-000014ff
PREFETCH window: d4000000-d7ffffff
MEM window: d8000000-dbffffff
PCI: Bridge: 0000:00:14.4
IO window: disabled.
MEM window: d0100000-d03fffff
PREFETCH window: disabled.
PCI: Setting latency timer of device 0000:00:04.0 to 64
PCI: Setting latency timer of device 0000:00:05.0 to 64
PCI: Setting latency timer of device 0000:00:06.0 to 64
ACPI: PCI Interrupt 0000:02:04.0[A] -> GSI 20 (level, low) -> IRQ 16
NET: Registered protocol family 2
Time: acpi_pm clocksource has been installed.
IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
TCP bind hash table entries: 65536 (order: 7, 786432 bytes)
TCP: Hash tables configured (established 131072 bind 65536)
TCP reno registered
checking if image is initramfs... it is
Freeing initrd memory: 1441k freed
audit: initializing netlink socket (disabled)
audit(1213912143.766:1): initialized
highmem bounce pool size: 64 pages
Total HugeTLB memory allocated, 0
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
fuse init (API version 7.9)
SELinux: Registering netfilter hooks
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 254)
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered (default)
io scheduler cfq registered
Boot video device is 0000:01:05.0
PCI: Setting latency timer of device 0000:00:04.0 to 64
assign_interrupt_mode Found MSI capability
Allocate Port Service[0000:00:04.0:pcie00]
Allocate Port Service[0000:00:04.0:pcie03]
PCI: Setting latency timer of device 0000:00:05.0 to 64
assign_interrupt_mode Found MSI capability
Allocate Port Service[0000:00:05.0:pcie00]
Allocate Port Service[0000:00:05.0:pcie03]
PCI: Setting latency timer of device 0000:00:06.0 to 64
assign_interrupt_mode Found MSI capability
Allocate Port Service[0000:00:06.0:pcie00]
Allocate Port Service[0000:00:06.0:pcie03]
ALI M7101 PMU not found.
vesafb: framebuffer at 0xc0000000, mapped to 0xf8880000, using 3072k, total 16384k
vesafb: mode is 1024x768x16, linelength=2048, pages=9
vesafb: protected mode interface info at c000:9f3c
vesafb: pmi: set display start = c00c9fc6, set palette = c00ca084
vesafb: scrolling: redraw
vesafb: Truecolor: size=0:5:6:5, shift=0:11:5:0
Console: switching to colour frame buffer device 128x48
fb0: VESA VGA frame buffer device
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
Real Time Clock Driver v1.12ac
Linux agpgart interface v0.102
intelfb: Framebuffer driver for Intel(R) 830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM chipsets
intelfb: Version 0.9.4
Floppy drive(s): fd0 is 1.44M
floppy0: no floppy controllers found
RAMDISK driver initialized: 16 RAM disks of 100000K size 1024 blocksize
input: Macintosh mouse button emulation as /class/input/input0
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
SB600_PATA: IDE controller (0x1002:0x438c rev 0x00) at PCI slot 0000:00:14.1
ACPI: PCI Interrupt 0000:00:14.1[A] -> GSI 16 (level, low) -> IRQ 17
SB600_PATA: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0x5040-0x5047, BIOS settings: hda:DMA, hdb:pio
Probing IDE interface ide0...
hda: Optiarc CDRWDVD CRX890A, ATAPI CD/DVD-ROM drive
hda: host max PIO4 wanted PIO255(auto-tune) selected PIO4
hda: MWDMA2 mode selected
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Probing IDE interface ide1...
hda: ATAPI 24X DVD-ROM CD-R/RW drive, 2048kB Cache
Uniform CD-ROM driver Revision: 3.20
Loading iSCSI transport class v2.0-724.
3ware Storage Controller device driver for Linux v1.26.02.002.
3ware 9000 Storage Controller device driver for Linux v2.26.02.010.
Driver 'sd' needs updating - please use bus_type methods
Driver 'sr' needs updating - please use bus_type methods
ahci 0000:00:12.0: version 3.0
ACPI: PCI Interrupt 0000:00:12.0[A] -> GSI 16 (level, low) -> IRQ 17
ahci 0000:00:12.0: controller can't do 64bit DMA, forcing 32bit
ahci 0000:00:12.0: controller can't do PMP, turning off CAP_PMP
ahci 0000:00:12.0: nr_ports (4) and implemented port map (0x1) don't match, using nr_ports
ahci 0000:00:12.0: forcing PORTS_IMPL to 0xf
ahci 0000:00:12.0: AHCI 0001.0100 32 slots 4 ports 3 Gbps 0xf impl SATA mode
ahci 0000:00:12.0: flags: ncq sntf ilck pm led clo pio slum part
scsi0 : ahci
scsi1 : ahci
scsi2 : ahci
scsi3 : ahci
ata1: SATA max UDMA/133 abar m1024@0xd0609000 port 0xd0609100 irq 17
ata2: SATA max UDMA/133 abar m1024@0xd0609000 port 0xd0609180 irq 17
ata3: SATA max UDMA/133 abar m1024@0xd0609000 port 0xd0609200 irq 17
ata4: SATA max UDMA/133 abar m1024@0xd0609000 port 0xd0609280 irq 17
ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata1.00: ATA-8: TOSHIBA MK1246GSX, LB214C, max UDMA/100
ata1.00: 234441648 sectors, multi 16: LBA48 NCQ (depth 31/32)
ata1.00: configured for UDMA/100
ata2: SATA link down (SStatus 0 SControl 0)
ata3: SATA link down (SStatus 0 SControl 0)
ata4: SATA link down (SStatus 0 SControl 0)
scsi 0:0:0:0: Direct-Access ATA TOSHIBA MK1246GS LB21 PQ: 0 ANSI: 5
sd 0:0:0:0: [sda] 234441648 512-byte hardware sectors (120034 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 0:0:0:0: [sda] 234441648 512-byte hardware sectors (120034 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sda: sda1 sda2
sd 0:0:0:0: [sda] Attached SCSI disk
ACPI: PCI Interrupt 0000:00:13.5[D] -> GSI 23 (level, low) -> IRQ 18
ehci_hcd 0000:00:13.5: EHCI Host Controller
ehci_hcd 0000:00:13.5: new USB bus registered, assigned bus number 1
ehci_hcd 0000:00:13.5: debug port 1
ehci_hcd 0000:00:13.5: irq 18, io mem 0xd0606000
ehci_hcd 0000:00:13.5: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 10 ports detected
116x: driver isp116x-hcd, 03 Nov 2005
ohci_hcd: 2006 August 04 USB 1.1 'Open' Host Controller (OHCI) Driver
ACPI: PCI Interrupt 0000:00:13.0[A] -> GSI 23 (level, low) -> IRQ 18
ohci_hcd 0000:00:13.0: OHCI Host Controller
ohci_hcd 0000:00:13.0: new USB bus registered, assigned bus number 2
ohci_hcd 0000:00:13.0: irq 18, io mem 0xd0601000
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
ACPI: PCI Interrupt 0000:00:13.1[B] -> GSI 17 (level, low) -> IRQ 19
ohci_hcd 0000:00:13.1: OHCI Host Controller
ohci_hcd 0000:00:13.1: new USB bus registered, assigned bus number 3
ohci_hcd 0000:00:13.1: irq 19, io mem 0xd0602000
usb usb3: configuration #1 chosen from 1 choice
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
ACPI: PCI Interrupt 0000:00:13.2[C] -> GSI 17 (level, low) -> IRQ 19
ohci_hcd 0000:00:13.2: OHCI Host Controller
ohci_hcd 0000:00:13.2: new USB bus registered, assigned bus number 4
ohci_hcd 0000:00:13.2: irq 19, io mem 0xd0603000
usb usb4: configuration #1 chosen from 1 choice
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 2 ports detected
ACPI: PCI Interrupt 0000:00:13.3[B] -> GSI 17 (level, low) -> IRQ 19
ohci_hcd 0000:00:13.3: OHCI Host Controller
ohci_hcd 0000:00:13.3: new USB bus registered, assigned bus number 5
ohci_hcd 0000:00:13.3: irq 19, io mem 0xd0604000
usb usb5: configuration #1 chosen from 1 choice
hub 5-0:1.0: USB hub found
hub 5-0:1.0: 2 ports detected
ACPI: PCI Interrupt 0000:00:13.4[C] -> GSI 17 (level, low) -> IRQ 19
ohci_hcd 0000:00:13.4: OHCI Host Controller
ohci_hcd 0000:00:13.4: new USB bus registered, assigned bus number 6
ohci_hcd 0000:00:13.4: irq 19, io mem 0xd0605000
usb usb6: configuration #1 chosen from 1 choice
hub 6-0:1.0: USB hub found
hub 6-0:1.0: 2 ports detected
USB Universal Host Controller Interface driver v3.0
sl811: driver sl811-hcd, 19 May 2005
drivers/usb/host/r8a66597-hcd.c: driver r8a66597_hcd, 29 May 2007
Initializing USB Mass Storage driver...
usb 4-1: new full speed USB device using ohci_hcd and address 2
usb 4-1: configuration #1 chosen from 1 choice
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usbcore: registered new interface driver libusual
PNP: PS/2 Controller [PNP0303:C24A,PNP0f13:C24B] at 0x60,0x64 irq 1,12
i8042.c: Detected active multiplexing controller, rev 1.1.
serio: i8042 KBD port at 0x60,0x64 irq 1
serio: i8042 AUX0 port at 0x60,0x64 irq 12
serio: i8042 AUX1 port at 0x60,0x64 irq 12
serio: i8042 AUX2 port at 0x60,0x64 irq 12
serio: i8042 AUX3 port at 0x60,0x64 irq 12
mice: PS/2 mouse device common for all mice
input: AT Translated Set 2 keyboard as /class/input/input1
Synaptics Touchpad, model: 1, fw: 6.2, id: 0x2580b1, caps: 0xa04793/0x300000
serio: Synaptics pass-through port at isa0060/serio4/input0
input: SynPS/2 Synaptics TouchPad as /class/input/input2
EDAC MC: Ver: 2.1.0 Mar 25 2008
EISA: Probing bus 0 at eisa.0
Cannot allocate resource for EISA slot 1
Cannot allocate resource for EISA slot 2
Cannot allocate resource for EISA slot 3
Cannot allocate resource for EISA slot 4
Cannot allocate resource for EISA slot 5
Cannot allocate resource for EISA slot 8
EISA: Detected 0 cards.
cpuidle: using governor ladder
usbcore: registered new interface driver hiddev
usbcore: registered new interface driver usbhid
drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver
Advanced Linux Sound Architecture Driver Version 1.0.15 (Tue Nov 20 19:16:42 2007 UTC).
ALSA device list:
No soundcards found.
Initializing XFRM netlink socket
NET: Registered protocol family 1
NET: Registered protocol family 17
NET: Registered protocol family 15
Using IPI No-Shortcut mode
Freeing unused kernel memory: 420k freed
Failed initialization of WD-7000 SCSI card!
ACPI: PCI Interrupt 0000:02:04.1[B] -> GSI 21 (level, low) -> IRQ 20
ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[20] MMIO=[d0101000-d01017ff] Max Packet=[2048] IR/IT contexts=[4/4]
ieee1394: Host added: ID:BUS[0-00:1023] GUID[00023f9929a52210]
hda: MWDMA2 mode selected
ISO 9660 Extensions: Microsoft Joliet Level 3
ISO 9660 Extensions: RRIP_1991A
cloop: Initializing cloop v2.624
cloop: loaded (max 8 devices)
cloop: /cdrom/KNOPPIX/KNOPPIX: 60323 blocks, 131072 bytes/block, largest block is 131118 bytes.
cloop: loaded 128 blocks into cache.
ISO 9660 Extensions: RRIP_1991A
cloop: losetup_file: 27172 blocks, 131072 bytes/block, largest block is 131118 bytes.
cloop: loaded 128 blocks into cache.
ISO 9660 Extensions: RRIP_1991A
aufs 20080324
ACPI: AC Adapter [C1EB] (on-line)
ACPI: Battery Slot [C1ED] (battery present)
ACPI: Battery Slot [C1EC] (battery absent)
No dock devices found.
input: Power Button (FF) as /class/input/input3
ACPI: Power Button (FF) [PWRF]
input: Sleep Button (CM) as /class/input/input4
ACPI: Sleep Button (CM) [C28D]
input: Lid Switch as /class/input/input5
ACPI: Lid Switch [C1F0]
ACPI: Transitioning device [C39B] to D3
ACPI: Transitioning device [C39B] to D3
ACPI: Fan [C39B] (off)
ACPI: Transitioning device [C39C] to D3
ACPI: Transitioning device [C39C] to D3
ACPI: Fan [C39C] (off)
ACPI: Transitioning device [C39D] to D3
ACPI: Transitioning device [C39D] to D3
ACPI: Fan [C39D] (off)
ACPI: Transitioning device [C39E] to D3
ACPI: Transitioning device [C39E] to D3
ACPI: Fan [C39E] (off)
ACPI: Processor [C000] (supports 8 throttling states)
ACPI: Processor [C001] (supports 8 throttling states)
ACPI: Thermal Zone [TZ1] (44 C)
input: Video Bus as /class/input/input6
ACPI: Video Device [C08D] (multi-head: yes rom: no post: no)
cpufreq: No nForce2 chipset.
powernow: This module only works with AMD K7 CPUs
powernow-k8: Found 1 AMD Turion(tm) 64 X2 Mobile Technology TL-60 processors (2 cpu cores) (version 2.20.00)
powernow-k8: 0 : fid 0xc (2000 MHz), vid 0x11
powernow-k8: 1 : fid 0xa (1800 MHz), vid 0x12
powernow-k8: 2 : fid 0x8 (1600 MHz), vid 0x13
powernow-k8: 3 : fid 0x0 (800 MHz), vid 0x1e
Yenta: CardBus bridge found at 0000:02:04.0 [103c:30c2]
Yenta: ISA IRQ mask 0x0cb8, PCI irq 16
Socket status: 30000006
Yenta: Raising subordinate bus# of parent bus (#02) from #03 to #06
pcmcia: parent PCI bridge Memory window: 0xd0100000 - 0xd03fffff
Clocksource tsc unstable (delta = -275903675 ns)
tg3.c:v3.86 (November 9, 2007)
ACPI: PCI Interrupt 0000:10:00.0[A] -> GSI 16 (level, low) -> IRQ 17
PCI: Setting latency timer of device 0000:10:00.0 to 64
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
eth0: Tigon3 [partno(none) rev b002 PHY(5787)] (PCI Express) 10/100/1000Base-T Ethernet 00:1f:29:8f:67:d8
eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] WireSpeed[1] TSOcap[1]
eth0: dma_rwctrl[76180000] dma_mask[64-bit]
ACPI: PCI Interrupt 0000:30:00.0[A] -> GSI 18 (level, low) -> IRQ 21
PCI: Setting latency timer of device 0000:30:00.0 to 64
WARNING: at drivers/ssb/main.c:883 ssb_tmslow_reject_bitmask()
Pid: 3073, comm: modprobe Not tainted 2.6.24.4 #2
[<faf748ab>] ssb_tmslow_reject_bitmask+0x4b/0x60 [ssb]
[<faf75201>] ssb_device_is_enabled+0x11/0x40 [ssb]
[<faf77839>] ssb_pcicore_init+0x19/0x60 [ssb]
[<faf746a3>] ssb_attach_queued_buses+0xd3/0x290 [ssb]
[<faf767ef>] ssb_pci_xtal+0x17f/0x230 [ssb]
[<faf74c73>] ssb_bus_register+0x163/0x1e0 [ssb]
[<faf76050>] ssb_pci_get_invariants+0x0/0x2c0 [ssb]
[<faf74dba>] ssb_bus_pcibus_register+0x2a/0x60 [ssb]
[<c0284de4>] pci_set_master+0x54/0x60
[<faf76a0c>] ssb_pcihost_probe+0x6c/0xa0 [ssb]
[<c0286e06>] pci_device_probe+0x56/0x80
[<c02f30f8>] driver_probe_device+0x88/0x190
[<c04a44bf>] klist_next+0x5f/0xc0
[<c02f3350>] __driver_attach+0x80/0x90
[<c02f249b>] bus_for_each_dev+0x3b/0x60
[<c02f2f66>] driver_attach+0x16/0x20
[<c02f32d0>] __driver_attach+0x0/0x90
[<c02f287a>] bus_add_driver+0x8a/0x1e0
[<c0286fc0>] __pci_register_driver+0x60/0xa0
[<faf1f04a>] ssb_modinit+0x4a/0x80 [ssb]
[<c0144817>] blocking_notifier_call_chain+0x17/0x20
[<c014de46>] sys_init_module+0x126/0x1ae0
[<c02758ff>] prio_tree_insert+0x1f/0x240
[<faf67000>] snd_hwdep_search+0x0/0x50 [snd_hwdep]
[<c02f2a70>] bus_register+0x0/0x230
[<c0104a5e>] syscall_call+0x7/0xb
=======================
ssb: Sonics Silicon Backplane found on PCI device 0000:30:00.0
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
ACPI: PCI Interrupt 0000:00:14.2[A] -> GSI 16 (level, low) -> IRQ 17
ieee80211_crypt: registered algorithm 'NULL'
ieee80211: 802.11 data/management/control stack, git-1.1.13
ieee80211: Copyright (C) 2004-2005 Intel Corporation <jke...@li...>
parport_pc 00:02: activated
parport_pc 00:02: reported by Plug and Play ACPI
parport_pc 00:02: disabled
tpm_inf_pnp 00:03: Found C232 with ID IFX0102
tpm_inf_pnp 00:03: TPM found: config base 0x520, data base 0x530, chip version 0x000b, vendor id 0x15d1 (Infineon), product id 0x000b (SLB 9635 TT 1.2)
bcm43xx driver
si3054: cannot initialize. EXT MID = 0000
piix4_smbus 0000:00:14.0: Found 0000:00:14.0 device
b43-phy0: Broadcom 4311 WLAN found
WARNING: at drivers/ssb/main.c:883 ssb_tmslow_reject_bitmask()
Pid: 3367, comm: modprobe Not tainted 2.6.24.4 #2
[<faf748ab>] ssb_tmslow_reject_bitmask+0x4b/0x60 [ssb]
[<faf749b7>] ssb_device_disable+0x47/0xf0 [ssb]
[<faf7523c>] ssb_device_enable+0xc/0xb0 [ssb]
[<fb141357>] b43_wireless_core_reset+0x17/0xe0 [b43]
[<fb14460b>] b43_probe+0x56b/0x8f0 [b43]
[<c01cff4b>] sysfs_addrm_finish+0x4b/0x220
[<c01d0b04>] sysfs_create_link+0x14/0x120
[<c044382b>] netlink_broadcast+0x21b/0x310
[<faf75137>] ssb_device_probe+0x37/0x80 [ssb]
[<c02f30f8>] driver_probe_device+0x88/0x190
[<c04a44bf>] klist_next+0x5f/0xc0
[<c02f21a0>] klist_devices_put+0x0/0x10
[<c02f3350>] __driver_attach+0x80/0x90
[<c02f249b>] bus_for_each_dev+0x3b/0x60
[<c02f2f66>] driver_attach+0x16/0x20
[<c02f32d0>] __driver_attach+0x0/0x90
[<c02f287a>] bus_add_driver+0x8a/0x1e0
[<f887d01f>] b43_init+0x1f/0x2e [b43]
[<c014de46>] sys_init_module+0x126/0x1ae0
[<c02758ff>] prio_tree_insert+0x1f/0x240
[<faf5d520>] pcmcia_request_irq+0x0/0x200 [pcmcia]
[<c0104a5e>] syscall_call+0x7/0xb
=======================
WARNING: at drivers/ssb/main.c:883 ssb_tmslow_reject_bitmask()
Pid: 3367, comm: modprobe Not tainted 2.6.24.4 #2
[<faf748ab>] ssb_tmslow_reject_bitmask+0x4b/0x60 [ssb]
[<faf749b7>] ssb_device_disable+0x47/0xf0 [ssb]
[<fb144894>] b43_probe+0x7f4/0x8f0 [b43]
[<c01cff4b>] sysfs_addrm_finish+0x4b/0x220
[<c01d0b04>] sysfs_create_link+0x14/0x120
[<c044382b>] netlink_broadcast+0x21b/0x310
[<faf75137>] ssb_device_probe+0x37/0x80 [ssb]
[<c02f30f8>] driver_probe_device+0x88/0x190
[<c04a44bf>] klist_next+0x5f/0xc0
[<c02f21a0>] klist_devices_put+0x0/0x10
[<c02f3350>] __driver_attach+0x80/0x90
[<c02f249b>] bus_for_each_dev+0x3b/0x60
[<c02f2f66>] driver_attach+0x16/0x20
[<c02f32d0>] __driver_attach+0x0/0x90
[<c02f287a>] bus_add_driver+0x8a/0x1e0
[<f887d01f>] b43_init+0x1f/0x2e [b43]
[<c014de46>] sys_init_module+0x126/0x1ae0
[<c02758ff>] prio_tree_insert+0x1f/0x240
[<faf5d520>] pcmcia_request_irq+0x0/0x200 [pcmcia]
[<c0104a5e>] syscall_call+0x7/0xb
=======================
phy0: Selected rate control algorithm 'simple'
input: b43-phy0 as /class/input/input7
WARNING: at drivers/ssb/main.c:883 ssb_tmslow_reject_bitmask()
Pid: 3469, comm: ifconfig Not tainted 2.6.24.4 #2
[<faf748ab>] ssb_tmslow_reject_bitmask+0x4b/0x60 [ssb]
[<faf75201>] ssb_device_is_enabled+0x11/0x40 [ssb]
[<fb1424d5>] b43_wireless_core_init+0x35/0x6d0 [b43]
[<fb151e39>] b43_rfkill_init+0x149/0x180 [b43]
[<fb143279>] b43_start+0x99/0xb0 [b43]
[<fb11faa7>] ieee80211_open+0x1a7/0x460 [mac80211]
[<c024e4bd>] task_has_capability+0x5d/0x80
[<c042c2d0>] dev_open+0x50/0x80
[<c042ae51>] dev_change_flags+0x81/0x190
[<c0429404>] __dev_get_by_name+0x74/0x90
[<c0476b1a>] devinet_ioctl+0x51a/0x6c0
[<c024e832>] inode_has_perm+0x52/0x90
[<c041da95>] sock_ioctl+0xb5/0x220
[<c041d9e0>] sock_ioctl+0x0/0x220
[<c01966ab>] do_ioctl+0x2b/0x90
[<c0196971>] vfs_ioctl+0x261/0x2d0
[<c0196a36>] sys_ioctl+0x56/0x70
[<c0104a5e>] syscall_call+0x7/0xb
=======================
b43-phy0 ERROR: Firmware file "b43/ucode13.fw" not found or load failed.
b43-phy0 ERROR: You must go to http://linuxwireless.org/en/users/Drivers/b43#devicefirmware and download the correct firmware (version 4).
warning: process `hwsetup' used the deprecated sysctl system call with 1.23.
pcmcia: Detected deprecated PCMCIA ioctl usage from process: hwsetup.
pcmcia: This interface will soon be removed from the kernel; please expect breakage unless you upgrade to new tools.
pcmcia: see http://www.kernel.org/pub/linux/utils/kernel/pcmcia/pcmcia.html for details.
cs: IO port probe 0xc00-0xcff: clean.
cs: IO port probe 0x100-0x4ff: clean.
cs: IO port probe 0xa00-0xaff: clean.
warning: process `hwsetup' used the deprecated sysctl system call with 1.49.
warning: process `hwsetup' used the deprecated sysctl system call with 1.49.
device-mapper: ioctl: 4.12.0-ioctl (2007-10-02) initialised: dm-...@re...
input: b43-phy0 as /class/input/input8
WARNING: at drivers/ssb/main.c:883 ssb_tmslow_reject_bitmask()
Pid: 3957, comm: ifconfig Not tainted 2.6.24.4 #2
[<faf748ab>] ssb_tmslow_reject_bitmask+0x4b/0x60 [ssb]
[<faf75201>] ssb_device_is_enabled+0x11/0x40 [ssb]
[<fb1424d5>] b43_wireless_core_init+0x35/0x6d0 [b43]
[<fb151e39>] b43_rfkill_init+0x149/0x180 [b43]
[<fb143279>] b43_start+0x99/0xb0 [b43]
[<fb11faa7>] ieee80211_open+0x1a7/0x460 [mac80211]
[<c024e4bd>] task_has_capability+0x5d/0x80
[<c042c2d0>] dev_open+0x50/0x80
[<c042ae51>] dev_change_flags+0x81/0x190
[<c0429404>] __dev_get_by_name+0x74/0x90
[<c0476b1a>] devinet_ioctl+0x51a/0x6c0
[<c024e832>] inode_has_perm+0x52/0x90
[<c041da95>] sock_ioctl+0xb5/0x220
[<c041d9e0>] sock_ioctl+0x0/0x220
[<c01966ab>] do_ioctl+0x2b/0x90
[<c0196971>] vfs_ioctl+0x261/0x2d0
[<c0196a36>] sys_ioctl+0x56/0x70
[<c0104a5e>] syscall_call+0x7/0xb
=======================
b43-phy0 ERROR: Firmware file "b43/ucode13.fw" not found or load failed.
b43-phy0 ERROR: You must go to http://linuxwireless.org/en/users/Drivers/b43#devicefirmware and download the correct firmware (version 4).
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
ADDRCONF(NETDEV_UP): eth0: link is not ready
[drm] Initialized drm 1.1.0 20060810
input: b43-phy0 as /class/input/input9
WARNING: at drivers/ssb/main.c:883 ssb_tmslow_reject_bitmask()
Pid: 3484, comm: pump Not tainted 2.6.24.4 #2
[<faf748ab>] ssb_tmslow_reject_bitmask+0x4b/0x60 [ssb]
[<faf75201>] ssb_device_is_enabled+0x11/0x40 [ssb]
[<fb1424d5>] b43_wireless_core_init+0x35/0x6d0 [b43]
[<fb151e39>] b43_rfkill_init+0x149/0x180 [b43]
[<fb143279>] b43_start+0x99/0xb0 [b43]
[<fb11faa7>] ieee80211_open+0x1a7/0x460 [mac80211]
[<c024e4bd>] task_has_capability+0x5d/0x80
[<c042c2d0>] dev_open+0x50/0x80
[<c042ae51>] dev_change_flags+0x81/0x190
[<c0429404>] __dev_get_by_name+0x74/0x90
[<c0476b1a>] devinet_ioctl+0x51a/0x6c0
[<c0499b70>] packet_ioctl+0x30/0x130
[<c041da95>] sock_ioctl+0xb5/0x220
[<c041d9e0>] sock_ioctl+0x0/0x220
[<c01966ab>] do_ioctl+0x2b/0x90
[<c0196971>] vfs_ioctl+0x261/0x2d0
[<c0196a36>] sys_ioctl+0x56/0x70
[<c0104a5e>] syscall_call+0x7/0xb
=======================
b43-phy0 ERROR: Firmware file "b43/ucode13.fw" not found or load failed.
b43-phy0 ERROR: You must go to http://linuxwireless.org/en/users/Drivers/b43#devicefirmware and download the correct firmware (version 4).
hda-intel: Invalid position buffer, using LPIB read method instead.
|
|
From: Jonathan D. <tz...@sp...> - 2008-06-20 00:31:57
|
Here you go:
CPU0
0: 57713 local-APIC-edge-fasteoi timer
1: 141 IO-APIC-edge i8042
8: 1 IO-APIC-edge rtc
9: 26 IO-APIC-fasteoi acpi
12: 151 IO-APIC-edge i8042
14: 1215 IO-APIC-edge ide0
16: 0 IO-APIC-fasteoi yenta
17: 122 IO-APIC-fasteoi ahci
18: 2 IO-APIC-fasteoi ohci_hcd:usb1, ehci_hcd:usb6
19: 29 IO-APIC-fasteoi ohci_hcd:usb2, ohci_hcd:usb3,
ohci_hcd:usb4, ohci_hcd:usb5
NMI: 0
LOC: 0
ERR: 0
MIS: 0
00000000-0009fbff : System RAM
00000000-00000000 : Crash kernel
0009fc00-0009ffff : reserved
000a0000-000bffff : Video RAM area
000c0000-000cd3ff : Video ROM
000cd400-000cffff : pnp 00:0d
000f0000-000fffff : System ROM
00100000-b7faffff : System RAM
00100000-0029ecda : Kernel code
0029ecdb-00340cc3 : Kernel data
b7fb0000-b7fc7fff : reserved
b7fc8000-b7fe7fb7 : ACPI Non-volatile Storage
b7fe7fb8-bfffffff : reserved
c0000000-c7ffffff : PCI Bus #01
c0000000-c7ffffff : 0000:01:05.0
c0000000-c0ffffff : vesafb
c8000000-c80fffff : PCI Bus #30
c8000000-c8003fff : 0000:30:00.0
c8100000-c8103fff : 0000:00:14.2
cc000000-cfffffff : PCI Bus #20
d0000000-d00fffff : PCI Bus #10
d0000000-d000ffff : 0000:10:00.0
d0100000-d03fffff : PCI Bus #02
d0100000-d0100fff : 0000:02:04.0
d0100000-d0100fff : yenta_socket
d0101000-d01017ff : 0000:02:04.1
d0400000-d05fffff : PCI Bus #01
d0400000-d040ffff : 0000:01:05.0
d0500000-d05fffff : 0000:01:05.0
d0601000-d0601fff : 0000:00:13.0
d0601000-d0601fff : ohci_hcd
d0602000-d0602fff : 0000:00:13.1
d0602000-d0602fff : ohci_hcd
d0603000-d0603fff : 0000:00:13.2
d0603000-d0603fff : ohci_hcd
d0604000-d0604fff : 0000:00:13.3
d0604000-d0604fff : ohci_hcd
d0605000-d0605fff : 0000:00:13.4
d0605000-d0605fff : ohci_hcd
d0606000-d06060ff : 0000:00:13.5
d0606000-d06060ff : ehci_hcd
d0609000-d06093ff : 0000:00:12.0
d0609000-d06093ff : ahci
d4000000-d7ffffff : PCI Bus #02
d4000000-d7ffffff : PCI CardBus #03
d8000000-dbffffff : PCI CardBus #03
e0000000-efffffff : reserved
fec00000-fec01fff : reserved
fed45000-fed8ffff : pnp 00:0c
fee00000-fee00fff : pnp 00:0d
ffbc0000-ffcbffff : reserved
fff00000-ffffffff : reserved
0000-001f : dma1
0020-0021 : pic1
0040-0043 : timer0
0050-0053 : timer1
0060-006f : keyboard
0070-0077 : rtc
0080-008f : dma page reg
00a0-00a1 : pic2
00c0-00df : dma2
00f0-00ff : fpu
0170-0177 : 0000:00:14.1
01f0-01f7 : 0000:00:14.1
01f0-01f7 : ide0
0376-0376 : 0000:00:14.1
03c0-03df : vesafb
03f6-03f6 : 0000:00:14.1
03f6-03f6 : ide0
040b-040b : pnp 00:0a
04d0-04d1 : pnp 00:0a
0cf8-0cff : PCI conf1
1000-1fff : PCI Bus #02
1000-10ff : PCI CardBus #03
1400-14ff : PCI CardBus #03
2000-3fff : PCI Bus #20
4000-4fff : PCI Bus #01
4000-40ff : 0000:01:05.0
5018-501b : 0000:00:12.0
5020-502f : 0000:00:12.0
5040-504f : 0000:00:14.1
5040-5047 : ide0
8000-802f : pnp 00:0c
8000-8003 : ACPI PM1a_EVT_BLK
8004-8005 : ACPI PM1a_CNT_BLK
8008-800b : ACPI PM_TMR
8020-8027 : ACPI GPE0_BLK
8100-811f : pnp 00:0c
8100-8100 : ACPI PM2_CNT_BLK
8104-8107 : ACPI PM1b_EVT_BLK
8200-820f : 0000:00:14.0
8200-8207 : piix4_smbus
9000-9007 : 0000:00:12.0
9008-900b : 0000:00:12.0
9010-9017 : 0000:00:12.0
Henry Nestler wrote:
> Henry Nestler wrote:
>
>> Thanks. As I suggest last mail :-),
>> You have a buggy timer chip, found in Gparted log:
>>
>> """
>> ..MP-BIOS bug: 8254 timer not connected to IO-APIC
>> ...trying to set up timer (IRQ0) through the 8259A ... failed.
>> """
>>
>> Some more I see: Why the BogoMIPS under coLinux are faster as in native.
>> Typicaly it is reverse.
>>
>> Your Debian in coLinux:
>> Calibrating delay loop... 15151.92 BogoMIPS (lpj=75759616)
>>
>> Your Gparted native live cd:
>> Calibrating delay using timer specific routine.. 3993.27 BogoMIPS
>> (lpj=7986550)
>>
>> Try to boot with manualy set of the delay, run coLinux with additional
>> kernel parameter:
>> lpj=1234567
>>
>>
>
> http://gentoo-wiki.com/HOWTO_Fix_Common_ACPI_Problems
>
> The problem is more clear now. But I can currently no find ideas for
> virtualisation. It is not Vista, or Vista has reprogrammed the DSDT?
> You would perhaps find many more Linux distributions that not works on
> this PC.
>
> The timer does not exist on IRQ0. That is truely very bad. The IRQ0 is
> the main timer for all events in Linux. coLinux kernel assumed, that
> IRQ0 is the timer.
>
> Jonathan, from the Gparted give me more informations please:
> cat /proc/interrupts
> cat /proc/iomem
> cat /proc/ioports
>
>
|
|
From: Jonathan D. <tz...@sp...> - 2008-06-19 23:23:34
|
"lpj=1234567" has no effect whatsoever on the problem. - Jonathan Henry Nestler wrote: > Thanks. As I suggest last mail :-), > You have a buggy timer chip, found in Gparted log: > > """ > ..MP-BIOS bug: 8254 timer not connected to IO-APIC > ...trying to set up timer (IRQ0) through the 8259A ... failed. > """ > > Some more I see: Why the BogoMIPS under coLinux are faster as in native. > Typicaly it is reverse. > > Your Debian in coLinux: > Calibrating delay loop... 15151.92 BogoMIPS (lpj=75759616) > > Your Gparted native live cd: > Calibrating delay using timer specific routine.. 3993.27 BogoMIPS > (lpj=7986550) > > Try to boot with manualy set of the delay, run coLinux with additional > kernel parameter: > lpj=1234567 > > |
|
From: Henry N. <hen...@ar...> - 2008-06-19 22:49:52
|
Henry Nestler wrote: > Thanks. As I suggest last mail :-), > You have a buggy timer chip, found in Gparted log: > > """ > ..MP-BIOS bug: 8254 timer not connected to IO-APIC > ...trying to set up timer (IRQ0) through the 8259A ... failed. > """ > > Some more I see: Why the BogoMIPS under coLinux are faster as in native. > Typicaly it is reverse. > > Your Debian in coLinux: > Calibrating delay loop... 15151.92 BogoMIPS (lpj=75759616) > > Your Gparted native live cd: > Calibrating delay using timer specific routine.. 3993.27 BogoMIPS > (lpj=7986550) > > Try to boot with manualy set of the delay, run coLinux with additional > kernel parameter: > lpj=1234567 > http://gentoo-wiki.com/HOWTO_Fix_Common_ACPI_Problems The problem is more clear now. But I can currently no find ideas for virtualisation. It is not Vista, or Vista has reprogrammed the DSDT? You would perhaps find many more Linux distributions that not works on this PC. The timer does not exist on IRQ0. That is truely very bad. The IRQ0 is the main timer for all events in Linux. coLinux kernel assumed, that IRQ0 is the timer. Jonathan, from the Gparted give me more informations please: cat /proc/interrupts cat /proc/iomem cat /proc/ioports -- Henry N. |
|
From: Henry N. <hen...@ar...> - 2008-06-19 22:22:31
|
Thanks. As I suggest last mail :-), You have a buggy timer chip, found in Gparted log: """ ..MP-BIOS bug: 8254 timer not connected to IO-APIC ...trying to set up timer (IRQ0) through the 8259A ... failed. """ Some more I see: Why the BogoMIPS under coLinux are faster as in native. Typicaly it is reverse. Your Debian in coLinux: Calibrating delay loop... 15151.92 BogoMIPS (lpj=75759616) Your Gparted native live cd: Calibrating delay using timer specific routine.. 3993.27 BogoMIPS (lpj=7986550) Try to boot with manualy set of the delay, run coLinux with additional kernel parameter: lpj=1234567 -- Henry Jonathan Deitch wrote: > I finally got the "main" setup to run long enough to capture a dmesg > trace; it's attached. > > thanks! > > - Jonathan > > Henry Nestler wrote: >> http://gparted.sourceforge.net/livecd.php >> >> is a very small live cdrom with USB mount support and a console and very >> recent kernel 2.6.22. I use it with VESA mode for mostly all PC. >> >> Henry >> >> Jonathan Deitch wrote: >> >>> Henry - >>> >>> capturing dmesg from knoppix will have to wait a bit ... I didn't >>> realize the distro had moved from CD to DVD, hence the download is >>> taking a bit longer. >>> >>> - Jonathan >>> >>> Henry Nestler wrote: >>> >>>> Jonathan Deitch wrote: >>>> >>>> >>>>> I'll run these tests tonight ... >>>>> >>>>> However - and this is the puzzling part - when the system goes into the >>>>> slow-mode, there is no abnormal CPU load. Yep, that's right ... no high >>>>> CPU in either task manager, or top. >>>>> >>>>> Both colinux and Vista are still usable - they're just very very slow >>>>> with a 4-5 second leg between any action and system response. >>>>> >>>>> >>>> Than I have an idea: The cpu has a buggy or a special timer chip? I have >>>> read some about buggy TSC, and Windows has shipped an update for such >>>> chips in a service pack. >>>> >>>> You says, the taskman shows na normal cpu load? Than the sytesm timer >>>> was falling down into slow mode? Currently I don't know why coLinux >>>> would reprogrammed the timer. Colinux does no change the timer >>>> intervall. Not directly, but perhaps the new kernel has some hocks for >>>> special cpu's? I will grep for it. >>>> >>>> The mouse is slow. ok. What is with a keyboard resonse time, for example >>>> in a notepad, or in a command prompt? >>>> >>>> Please boot a knoppix, or from a distribution you have in a rescure mode >>>> with text console. Somethere you can cat the native kernel boot messages >>>> (dmesg) into a file and send me, please. I will grep for special >>>> messages about your cpu. You also can send me the kernel messages from >>>> coLinux-daemon.exe, as you can do it via mouse "copy all text" from >>>> screen into clipboard and paste it into notepad. Or run >>>> "colinux-daemon.exe ... > file.log" >>>> >>>> >> |
|
From: Jonathan D. <tz...@sp...> - 2008-06-19 21:59:31
|
Linux version 2.6.22.18-co-0.7.3 (hn@coLinux) (gcc version 4.1.2) #1 PREEMPT Sat May 24 22:27:30 UTC 2008
768MB LOWMEM available.
initrd enabled: start: 0xeff9a000 size: 0x00065881
Entering add_active_range(0, 0, 196608) 0 entries of 256 used
Zone PFN ranges:
DMA 0 -> 0
Normal 0 -> 196608
early_node_map[1] active PFN ranges
0: 0 -> 196608
On node 0 totalpages: 196608
DMA zone: 0 pages used for memmap
Normal zone: 1536 pages used for memmap
Normal zone: 195072 pages, LIFO batch:31
Built 1 zonelists. Total pages: 195072
Kernel command line: root=/dev/cobd0 fastboot 3
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
Setting proxy interrupt vectors
PID hash table entries: 4096 (order: 12, 16384 bytes)
Console: colour CoCON 80x25
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Memory: 775168k/786432k available (1705k kernel code, 0k reserved, 470k data, 128k init, 0k highmem)
virtual kernel memory layout:
fixmap : 0xffffc000 - 0xfffff000 ( 12 kB)
vmalloc : 0xf0800000 - 0xffffa000 ( 247 MB)
lowmem : 0xc0000000 - 0xf0000000 ( 768 MB)
.init : 0xc0322000 - 0xc0342000 ( 128 kB)
.data : 0xc02aa638 - 0xc031ffe4 ( 470 kB)
.text : 0xc0100000 - 0xc02aa638 (1705 kB)
Calibrating delay loop... 14680.06 BogoMIPS (lpj=73400320)
Mount-cache hash table entries: 512
CPU: After generic identify, caps: 178bfbff ebd3fbff 00000000 00000000 00002001 00000000 0000011f
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 512K (64 bytes/line)
CPU: After all inits, caps: 178bf3ff ebd3fbff 00000000 00000410 00002001 00000000 0000011f
Compat vDSO mapped to ffffe000.
CPU: AMD Turion(tm) 64 X2 Mobile Technology TL-60 stepping 02
Checking 'hlt' instruction... OK.
NET: Registered protocol family 16
NET: Registered protocol family 2
IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
TCP bind hash table entries: 65536 (order: 6, 262144 bytes)
TCP: Hash tables configured (established 131072 bind 65536)
TCP reno registered
checking if image is initramfs...it isn't (no cpio magic); looks like an initrd
Freeing initrd memory: 406k freed
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
cofuse init 0.1 (API version 2.2)
io scheduler noop registered
io scheduler anticipatory registered (default)
io scheduler deadline registered
io scheduler cfq registered
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
cobd: loaded (max 32 devices)
alias for cobd2 is hdc
cobd alias cobd2 -> hdc created
loop: module loaded
conet: loaded (max 16 devices)
conet0: initialized
conet1: initialized
serio: cokbd at irq 1
mice: PS/2 mouse device common for all mice
input: AT Translated Set 2 keyboard as /class/input/input0
TCP cubic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
Using IPI Shortcut mode
RAMDISK: Compressed image found at block 0
VFS: Mounted root (ext2 filesystem).
ReiserFS: cobd0: warning: sh-2021: reiserfs_fill_super: can not find reiserfs on cobd0
EXT3-fs: INFO: recovery required on readonly filesystem.
EXT3-fs: write access will be enabled during recovery.
kjournald starting. Commit interval 5 seconds
EXT3-fs: cobd0: orphan cleanup on readonly fs
ext3_orphan_cleanup: deleting unreferenced inode 125371
EXT3-fs: cobd0: 1 orphan inode deleted
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS on cobd0, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem).
Trying to move old root to /initrd ... okay
Freeing unused kernel memory: 128k freed
device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised: dm-...@re...
kjournald starting. Commit interval 5 seconds
EXT3 FS on cobd1, internal journal
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.
fuse_read_super: connection already mounted
ip_tables: (C) 2000-2006 Netfilter Core Team
ip_tables: (C) 2000-2006 Netfilter Core Team
ip_tables: (C) 2000-2006 Netfilter Core Team
fuse_read_super: connection already mounted
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
eth1: duplicate address detected!
eth0: no IPv6 routers present
fuse_read_super: connection already mounted
fuse_read_super: connection already mounted
fuse_read_super: connection already mounted
|
|
From: Henry N. <hen...@ar...> - 2008-06-19 20:19:16
|
Can you run "colinux-daemon --status-driver" ? Perhaps we can check it by forcing parameter errors. Please run the follow tests by step and check your mouse after every step. We need to know on what step the problems begins. Abnormal exist of colinux-daemom are ok in that testings. "colinux-daemon mem=32 kernel=missing.file" Lets only driver init, no loading kernel. "colinux-daemon -v 3 mem=32 kernel=missing.file" The same with more debugs. "colinux-daemon -v 3 -d mem=32 kernel=vmlinux root=/dev/dummy" Loads and starts the kernel. Exits before mount filesystem. No console. "colinux-daemon -v 3 -t nt mem=32 kernel=vmlinux root=/dev/dummy" The same with NT console. "colinux-daemon -v 3 mem=32 kernel=vmlinux root=/dev/dummy" The same with FLTK console. "colinux-daemon -v 3 -d mem=32 kernel=vmlinux initrd=initrd.gz root=/dev/ram0 init=/sbin/halt" Starts RAMdisk and shuting down Linux automaticly, without console. "colinux-daemon -v 3 mem=32 kernel=vmlinux initrd=initrd.gz root=/dev/ram0 init=/sbin/halt" The same with FLTK console. "colinux-daemon mem=32 kernel=vmlinux initrd=initrd.gz root=/dev/ram0 init=/sbin/halt" The same with less error checks. -- Henry Jonathan Deitch wrote: > Ok, > > Still no go. I cannot get a dump from colinux; when I try and run the > debug setup, the system goes blackscreen and reboots. No bluescreen. > > I tried completely disabling the page file, same behavior. > > When the problem occurs, I do not see ANY runaway (or abnormal) cpu or > memory usage. > > Anyone got any other ideas? I'm rapidly reaching the point where I'm > going to be given no choice by my employer but to abandon colinux as > vista incompatible and find another solution. > > - Jonathan > > Jason Alonso wrote: >> On Wed, Jun 18, 2008 at 7:07 PM, Henry Nestler wrote: >> >>> Jonathan Deitch wrote: >>> >>>> However - and this is the puzzling part - when the system goes into the >>>> slow-mode, there is no abnormal CPU load. Yep, that's right ... no high >>>> CPU in either task manager, or top. >>>> >>>> Both colinux and Vista are still usable - they're just very very slow >>>> with a 4-5 second leg between any action and system response. >>>> >> Sounds familiar... >> >> >>> Than I have an idea: The cpu has a buggy or a special timer chip? I have >>> read some about buggy TSC, and Windows has shipped an update for such >>> chips in a service pack. >>> >> How about an alternative theory? Is your page file usage changing? >> If so, you can configure your taskman process list to show you memory >> usage and/or VM size. If something spirals out of control (and it >> will take a little while to do so), your system will start swapping >> memory with disk until it's painfully slow. coLinux, however, should >> not be torturing you with memory leaks. >> >> It's not as esoteric a theory as buggy system timer handling, but it's >> a simple test. >> >> Cheers, >> Jason >> |
|
From: Henry N. <hen...@ar...> - 2008-06-19 19:50:49
|
http://gparted.sourceforge.net/livecd.php is a very small live cdrom with USB mount support and a console and very recent kernel 2.6.22. I use it with VESA mode for mostly all PC. Henry Jonathan Deitch wrote: > Henry - > > capturing dmesg from knoppix will have to wait a bit ... I didn't > realize the distro had moved from CD to DVD, hence the download is > taking a bit longer. > > - Jonathan > > Henry Nestler wrote: >> Jonathan Deitch wrote: >> >>> I'll run these tests tonight ... >>> >>> However - and this is the puzzling part - when the system goes into the >>> slow-mode, there is no abnormal CPU load. Yep, that's right ... no high >>> CPU in either task manager, or top. >>> >>> Both colinux and Vista are still usable - they're just very very slow >>> with a 4-5 second leg between any action and system response. >>> >> Than I have an idea: The cpu has a buggy or a special timer chip? I have >> read some about buggy TSC, and Windows has shipped an update for such >> chips in a service pack. >> >> You says, the taskman shows na normal cpu load? Than the sytesm timer >> was falling down into slow mode? Currently I don't know why coLinux >> would reprogrammed the timer. Colinux does no change the timer >> intervall. Not directly, but perhaps the new kernel has some hocks for >> special cpu's? I will grep for it. >> >> The mouse is slow. ok. What is with a keyboard resonse time, for example >> in a notepad, or in a command prompt? >> >> Please boot a knoppix, or from a distribution you have in a rescure mode >> with text console. Somethere you can cat the native kernel boot messages >> (dmesg) into a file and send me, please. I will grep for special >> messages about your cpu. You also can send me the kernel messages from >> coLinux-daemon.exe, as you can do it via mouse "copy all text" from >> screen into clipboard and paste it into notepad. Or run >> "colinux-daemon.exe ... > file.log" >> |
|
From: Henry N. <hen...@ar...> - 2008-06-19 19:42:44
|
Paolo Minazzi wrote: > A simple question for all colinux users .... > If you use console-nt, does BLOCKNUM work ? > If I press BLOCKNUM and I use the the keys > > 0-9 * - + - ENTER . > > of numeric keypad, it does not work. Colinux does not change the BLOCKNUM state- > I use a keyboard with italian layout. > > I need only to know if it is only my problem or is generic problem. On German Windows does not woorking. NUMLOCK on or off does not sense, all I get on Linux prompt for keys 0-9 is: ^[[2~^[[4~^[[B^[[6~^[[D^[[G^[[C^[[1~^[[A^[[5~ You are right the NUMLOCK is always seen as "off" for coLinux. I have opened mc Midnight Commander and I can move the cursor with keys NUM-8 and NUM-2 up and down. Key NUM-Lock toggles the NUM-lock LED, but has no effect for key bindings. Cursor goes up and down in both states of NUN-LED on and off. -- Henry N. |
|
From: Jonathan D. <tz...@sp...> - 2008-06-19 16:29:37
|
Henry - capturing dmesg from knoppix will have to wait a bit ... I didn't realize the distro had moved from CD to DVD, hence the download is taking a bit longer. - Jonathan Henry Nestler wrote: > Jonathan Deitch wrote: > >> I'll run these tests tonight ... >> >> However - and this is the puzzling part - when the system goes into the >> slow-mode, there is no abnormal CPU load. Yep, that's right ... no high >> CPU in either task manager, or top. >> >> Both colinux and Vista are still usable - they're just very very slow >> with a 4-5 second leg between any action and system response. >> > > Than I have an idea: The cpu has a buggy or a special timer chip? I have > read some about buggy TSC, and Windows has shipped an update for such > chips in a service pack. > > You says, the taskman shows na normal cpu load? Than the sytesm timer > was falling down into slow mode? Currently I don't know why coLinux > would reprogrammed the timer. Colinux does no change the timer > intervall. Not directly, but perhaps the new kernel has some hocks for > special cpu's? I will grep for it. > > The mouse is slow. ok. What is with a keyboard resonse time, for example > in a notepad, or in a command prompt? > > Please boot a knoppix, or from a distribution you have in a rescure mode > with text console. Somethere you can cat the native kernel boot messages > (dmesg) into a file and send me, please. I will grep for special > messages about your cpu. You also can send me the kernel messages from > coLinux-daemon.exe, as you can do it via mouse "copy all text" from > screen into clipboard and paste it into notepad. Or run > "colinux-daemon.exe ... > file.log" > > |
|
From: Jonathan D. <tz...@sp...> - 2008-06-19 15:48:17
|
Ok, Still no go. I cannot get a dump from colinux; when I try and run the debug setup, the system goes blackscreen and reboots. No bluescreen. I tried completely disabling the page file, same behavior. When the problem occurs, I do not see ANY runaway (or abnormal) cpu or memory usage. Anyone got any other ideas? I'm rapidly reaching the point where I'm going to be given no choice by my employer but to abandon colinux as vista incompatible and find another solution. - Jonathan Jason Alonso wrote: > On Wed, Jun 18, 2008 at 7:07 PM, Henry Nestler wrote: > >> Jonathan Deitch wrote: >> >>> However - and this is the puzzling part - when the system goes into the >>> slow-mode, there is no abnormal CPU load. Yep, that's right ... no high >>> CPU in either task manager, or top. >>> >>> Both colinux and Vista are still usable - they're just very very slow >>> with a 4-5 second leg between any action and system response. >>> > > Sounds familiar... > > >> Than I have an idea: The cpu has a buggy or a special timer chip? I have >> read some about buggy TSC, and Windows has shipped an update for such >> chips in a service pack. >> > > How about an alternative theory? Is your page file usage changing? > If so, you can configure your taskman process list to show you memory > usage and/or VM size. If something spirals out of control (and it > will take a little while to do so), your system will start swapping > memory with disk until it's painfully slow. coLinux, however, should > not be torturing you with memory leaks. > > It's not as esoteric a theory as buggy system timer handling, but it's > a simple test. > > Cheers, > Jason > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://sourceforge.net/services/buy/index.php > _______________________________________________ > coLinux-users mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-users > |
|
From: Paolo M. <pao...@gm...> - 2008-06-19 08:15:43
|
I have changed a line into colinux code to manage BLOCKNUM . Doing so, for me works. It seems a bug of windows console API. Let me know if it is only my problem or generic, so we can patch it. Thanks. Paolo On Thu, Jun 19, 2008 at 10:06 AM, Paolo Minazzi <pao...@gm...> wrote: > A simple question for all colinux users .... > If you use console-nt, does BLOCKNUM work ? > If I press BLOCKNUM and I use the the keys > > 0-9 * - + - ENTER . > > of numeric keypad, it does not work. Colinux does not change the BLOCKNUM state- > I use a keyboard with italian layout. > > I need only to know if it is only my problem or is generic problem. > > Thanks for reply > > Paolo > |
|
From: Paolo M. <pao...@gm...> - 2008-06-19 08:07:02
|
A simple question for all colinux users .... If you use console-nt, does BLOCKNUM work ? If I press BLOCKNUM and I use the the keys 0-9 * - + - ENTER . of numeric keypad, it does not work. Colinux does not change the BLOCKNUM state- I use a keyboard with italian layout. I need only to know if it is only my problem or is generic problem. Thanks for reply Paolo |
|
From: Jason A. <ja...@ha...> - 2008-06-18 23:44:37
|
On Wed, Jun 18, 2008 at 7:07 PM, Henry Nestler wrote: > Jonathan Deitch wrote: >> However - and this is the puzzling part - when the system goes into the >> slow-mode, there is no abnormal CPU load. Yep, that's right ... no high >> CPU in either task manager, or top. >> >> Both colinux and Vista are still usable - they're just very very slow >> with a 4-5 second leg between any action and system response. Sounds familiar... > > Than I have an idea: The cpu has a buggy or a special timer chip? I have > read some about buggy TSC, and Windows has shipped an update for such > chips in a service pack. How about an alternative theory? Is your page file usage changing? If so, you can configure your taskman process list to show you memory usage and/or VM size. If something spirals out of control (and it will take a little while to do so), your system will start swapping memory with disk until it's painfully slow. coLinux, however, should not be torturing you with memory leaks. It's not as esoteric a theory as buggy system timer handling, but it's a simple test. Cheers, Jason |
|
From: Jonathan D. <tz...@sp...> - 2008-06-18 23:31:20
|
I can get you a knoppix dmesg dump no problem. I can also get you a dump from colinux, more than likely ... while the system does slow down, if you're patient it's still usable ... All functions slow down - mouse, keyboard, heck even the clock on the desktop. Everything starts slowing down, and actions happen only in spurts every 4-5 seconds ... ie: you click something, 4-5 seconds later it happens. You type, 4-5 seconds later it appears. etc. - Jonathan Henry Nestler wrote: > Jonathan Deitch wrote: > >> I'll run these tests tonight ... >> >> However - and this is the puzzling part - when the system goes into the >> slow-mode, there is no abnormal CPU load. Yep, that's right ... no high >> CPU in either task manager, or top. >> >> Both colinux and Vista are still usable - they're just very very slow >> with a 4-5 second leg between any action and system response. >> > > Than I have an idea: The cpu has a buggy or a special timer chip? I have > read some about buggy TSC, and Windows has shipped an update for such > chips in a service pack. > > You says, the taskman shows na normal cpu load? Than the sytesm timer > was falling down into slow mode? Currently I don't know why coLinux > would reprogrammed the timer. Colinux does no change the timer > intervall. Not directly, but perhaps the new kernel has some hocks for > special cpu's? I will grep for it. > > The mouse is slow. ok. What is with a keyboard resonse time, for example > in a notepad, or in a command prompt? > > Please boot a knoppix, or from a distribution you have in a rescure mode > with text console. Somethere you can cat the native kernel boot messages > (dmesg) into a file and send me, please. I will grep for special > messages about your cpu. You also can send me the kernel messages from > coLinux-daemon.exe, as you can do it via mouse "copy all text" from > screen into clipboard and paste it into notepad. Or run > "colinux-daemon.exe ... > file.log" > > |
|
From: Henry N. <hen...@ar...> - 2008-06-18 23:06:09
|
Jonathan Deitch wrote: > I'll run these tests tonight ... > > However - and this is the puzzling part - when the system goes into the > slow-mode, there is no abnormal CPU load. Yep, that's right ... no high > CPU in either task manager, or top. > > Both colinux and Vista are still usable - they're just very very slow > with a 4-5 second leg between any action and system response. Than I have an idea: The cpu has a buggy or a special timer chip? I have read some about buggy TSC, and Windows has shipped an update for such chips in a service pack. You says, the taskman shows na normal cpu load? Than the sytesm timer was falling down into slow mode? Currently I don't know why coLinux would reprogrammed the timer. Colinux does no change the timer intervall. Not directly, but perhaps the new kernel has some hocks for special cpu's? I will grep for it. The mouse is slow. ok. What is with a keyboard resonse time, for example in a notepad, or in a command prompt? Please boot a knoppix, or from a distribution you have in a rescure mode with text console. Somethere you can cat the native kernel boot messages (dmesg) into a file and send me, please. I will grep for special messages about your cpu. You also can send me the kernel messages from coLinux-daemon.exe, as you can do it via mouse "copy all text" from screen into clipboard and paste it into notepad. Or run "colinux-daemon.exe ... > file.log" -- Henry N. |
|
From: Jonathan D. <tz...@sp...> - 2008-06-18 21:08:23
|
I'll run these tests tonight ... However - and this is the puzzling part - when the system goes into the slow-mode, there is no abnormal CPU load. Yep, that's right ... no high CPU in either task manager, or top. Both colinux and Vista are still usable - they're just very very slow with a 4-5 second leg between any action and system response. - Jonathan Henry Nestler wrote: > Hello, > > Josep Maria Antolín Segura schrieb: > >> commandline: >> colinux-daemon.exe -t nt @D:\Colinux\debian\ramdisk-mode.txt >> >> ramdisk-mode.txt: >> kernel=vmlinux >> initrd=initrd.gz >> root=/dev/ram0 >> >> colinux version: >> Linux (none) 2.6.22.18-co-0.7.3 #1 PREEMPT Sat May 24 22:27:30 UTC 2008 i686 unk >> nown >> >> >> I don't know if it may be related to being Vista Business, or the AMD chip. I >> believe you'll have to work that out with the developers via debug builds. >> >> > > thanks, Josep. > > The version 0.8.0 with kernel 2.6.17 is a non official build, please use > this not as reference. > > The version 20080511-ntconsoleflood is a special build with some more > add ons, and have more debugging inside. So, this version would run > slower. You have seen it as a longer time before problems starts. > > Jonathan, debugging is available, if you would try some steps. First > lets configure the simplest start. Perhaps Josep can check, that the > same variant is running without probmlems. > > 0. All the colinux programs, please run from a CMD.EXE you have opened > as Admin. Please don't use "start.exe" and not a tool "runas.exe". > Please don't think you are an user with admin rights. That is not the > same. Check your admin status with "whoamy /all" or so. > > 1. You should have installed 0.7.3 final version. We need to verify > exactly the same version. Check the installed driver: > C:\coLinux> colinux-daemon --status-driver > Cooperative Linux Daemon, 0.7.3 > Daemon compiled on Sat May 24 22:36:07 2008 > > checking if the driver is installed > current state: 4 (fully initialized) > current number of monitors: 0 > current linux api version: 10 > current periphery api version: 20 > Driver compiled on: Sat May 24 22:36:07 2008 > > The installed path can differ. Any different output would make problems. > > 2. Open your Windows task manager and watch the performance graph. > Splitte the cpu into 2 diagrams to see, if one core is hanging. > > Some times later as you sayed, the first cpu core (the left diagram) > would go into 100% of load after coLinux runs somethere in an endless > loop. We need to find the position in Linux kernel boot steps. > > 3. Read file debugging.txt from your installation, or get it from > http://colinux.svn.sourceforge.net/svnroot/colinux/branches/devel/doc/debugging > > 4. Open a command prompt, change into colinux directory and run: > C:\coLinux> mode con lines=600 cols=120 > C:\coLinux> colinux-debug-daemon.exe -p -d -s prints=31,misc=31 > Adjust the font size from sys-menu of this window to see most lines as > you can. Don't worry about XML output needs only to see the text messages. > > 5. Watch the taskmanager performance graph. This command should not > incrace the cpu load. > > 6. Run the minimal coLinux ramdisk with special parameters: > colinux-daemon mem=64 kernel=vmlinux initrd=initrd.gz root=/dev/ram0 > rootdelay=10 > > Any signifikant changes in the memory or performance? 10 to 20% more cpu > load is normal after kernel boot, 5-10 MB more memory is normal. > > 7. Wait for prompt. Do nothing, do not press ENTER before 10 minutes you > have seen not your problem. The colinux-debug output should stop on this > step. > > 8. Press ENTER and run "halt" to shutdown coLinux. The debugger should > stop with text "string" lines like this: > <string>prints "colinux: halted, exiting." > <string>shutting down</string> > ... > <string>Pipe broken, exiting</string> > <string>done freeing</string> > <string>after free: 0 blocks</string> > <string>daemon cleanup</string> > <string>rc=00424400 exit=0</string> > > Please copy and send your last lines, if you have more or others. > > In every step: > Watch also for NT kernel memory usage after every step, and what the > physical free memory. Would it incrace permanently after one of the steps? > > Plese give some coments for the steps. We can rune more debugs later. > > |
|
From: Henry N. <hen...@ar...> - 2008-06-18 20:46:41
|
Hello, Josep Maria Antolín Segura schrieb: > commandline: > colinux-daemon.exe -t nt @D:\Colinux\debian\ramdisk-mode.txt > > ramdisk-mode.txt: > kernel=vmlinux > initrd=initrd.gz > root=/dev/ram0 > > colinux version: > Linux (none) 2.6.22.18-co-0.7.3 #1 PREEMPT Sat May 24 22:27:30 UTC 2008 i686 unk > nown > > > I don't know if it may be related to being Vista Business, or the AMD chip. I > believe you'll have to work that out with the developers via debug builds. > thanks, Josep. The version 0.8.0 with kernel 2.6.17 is a non official build, please use this not as reference. The version 20080511-ntconsoleflood is a special build with some more add ons, and have more debugging inside. So, this version would run slower. You have seen it as a longer time before problems starts. Jonathan, debugging is available, if you would try some steps. First lets configure the simplest start. Perhaps Josep can check, that the same variant is running without probmlems. 0. All the colinux programs, please run from a CMD.EXE you have opened as Admin. Please don't use "start.exe" and not a tool "runas.exe". Please don't think you are an user with admin rights. That is not the same. Check your admin status with "whoamy /all" or so. 1. You should have installed 0.7.3 final version. We need to verify exactly the same version. Check the installed driver: C:\coLinux> colinux-daemon --status-driver Cooperative Linux Daemon, 0.7.3 Daemon compiled on Sat May 24 22:36:07 2008 checking if the driver is installed current state: 4 (fully initialized) current number of monitors: 0 current linux api version: 10 current periphery api version: 20 Driver compiled on: Sat May 24 22:36:07 2008 The installed path can differ. Any different output would make problems. 2. Open your Windows task manager and watch the performance graph. Splitte the cpu into 2 diagrams to see, if one core is hanging. Some times later as you sayed, the first cpu core (the left diagram) would go into 100% of load after coLinux runs somethere in an endless loop. We need to find the position in Linux kernel boot steps. 3. Read file debugging.txt from your installation, or get it from http://colinux.svn.sourceforge.net/svnroot/colinux/branches/devel/doc/debugging 4. Open a command prompt, change into colinux directory and run: C:\coLinux> mode con lines=600 cols=120 C:\coLinux> colinux-debug-daemon.exe -p -d -s prints=31,misc=31 Adjust the font size from sys-menu of this window to see most lines as you can. Don't worry about XML output needs only to see the text messages. 5. Watch the taskmanager performance graph. This command should not incrace the cpu load. 6. Run the minimal coLinux ramdisk with special parameters: colinux-daemon mem=64 kernel=vmlinux initrd=initrd.gz root=/dev/ram0 rootdelay=10 Any signifikant changes in the memory or performance? 10 to 20% more cpu load is normal after kernel boot, 5-10 MB more memory is normal. 7. Wait for prompt. Do nothing, do not press ENTER before 10 minutes you have seen not your problem. The colinux-debug output should stop on this step. 8. Press ENTER and run "halt" to shutdown coLinux. The debugger should stop with text "string" lines like this: <string>prints "colinux: halted, exiting." <string>shutting down</string> ... <string>Pipe broken, exiting</string> <string>done freeing</string> <string>after free: 0 blocks</string> <string>daemon cleanup</string> <string>rc=00424400 exit=0</string> Please copy and send your last lines, if you have more or others. In every step: Watch also for NT kernel memory usage after every step, and what the physical free memory. Would it incrace permanently after one of the steps? Plese give some coments for the steps. We can rune more debugs later. -- Henry N. |
|
From: Jonathan D. <tz...@sp...> - 2008-06-18 19:54:55
|
Tried this in both normal and service mode. In both cases it fails .. runs for a minute or so, then both colinux and vista are very very slow. There are no errors. After that, the machine's screwed. You have to reboot. Debugging is impossible; I tried to set it up, and the second it tries to actually write debugging information, the entire system goes black and reboots; no bluescreen. So still no go. - Jonathan Josep Maria Antolín Segura wrote: > commandline: > colinux-daemon.exe -t nt @D:\Colinux\debian\ramdisk-mode.txt > > ramdisk-mode.txt: > kernel=vmlinux > initrd=initrd.gz > root=/dev/ram0 > > colinux version: > Linux (none) 2.6.22.18-co-0.7.3 #1 PREEMPT Sat May 24 22:27:30 UTC 2008 i686 unk > nown > > > I don't know if it may be related to being Vista Business, or the AMD chip. I > believe you'll have to work that out with the developers via debug builds. > > |
119 messages has been excluded from this view by a project administrator.
