Re: 2.6.23-rt1 lockup after loading HAL deamon
Hi Good news (I hope). With kernel option maxcpus=1, I can not get a lock, so the system is stable and running. Where could be a problem? Best regards, Rok Ingo Molnar wrote: >> Hi >> >> I have recompiled kernel with OPROFILE disabled. I am sending in >> attachment /proc/interrupts (i ran it 3 times with 2 sec delay) and >> netconsole log. Lockup in the lock is software made with ./lockup. The >> kernel still locks 4-5minutes after boot without any further messages >> (waited more than 2 minutes). Any ideas? > > no good ideas :-( I suspect this one: > > [ 185.600900] hdc: lost interrupt > > was a side-effect of lockup.c too? > > does the lockup go away if you boot with maxcpus=1? > > Ingo > > - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.23-rt1 lockup after loading HAL deamon
Hi I have recompiled kernel with OPROFILE disabled. I am sending in attachment /proc/interrupts (i ran it 3 times with 2 sec delay) and netconsole log. Lockup in the lock is software made with ./lockup. The kernel still locks 4-5minutes after boot without any further messages (waited more than 2 minutes). Any ideas? Rok Ingo Molnar wrote: > could you disable CONFIG_OPROFILE? Maybe it interferes with the NMI > watchdog? > > how does /proc/interrupts look like shortly after bootup? Does a simple > "intentional lockup" piece of code, which provokes a hard lockup from > user-space, get properly zapped by the NMI watchdog (within a minute or > so): > > the NMI watchdog should produce a console message similar to: > > BUG: NMI Watchdog detected LOCKUP on CPU0, eip bff12345, registers: > ... > > ( if you test ./lockup and get the message properly then i'd suggest a > new reboot - i think we inhibit further console output after an NMI > printout. ) > > Ingo > > CPU0 CPU1 0:151 0 IO-APIC-edge timer 1:206 0 IO-APIC-edge i8042 5: 0 0 IO-APIC-edge parport0 6: 3 0 IO-APIC-edge floppy 8: 1 0 IO-APIC-edge rtc 9: 0 0 IO-APIC-fasteoi acpi 12:102 0 IO-APIC-edge i8042 15: 24 84 IO-APIC-edge ide1 19: 3 0 IO-APIC-fasteoi bttv0 20: 8873 0 IO-APIC-fasteoi sata_via 21: 11741 0 IO-APIC-fasteoi uhci_hcd:usb1, uhci_hcd:usb2, uhci_hcd:usb3, uhci_hcd:usb4, ehci_hcd:usb5 22: 0 0 IO-APIC-fasteoi VIA8237 23:380 0 IO-APIC-fasteoi eth0 NMI:253194 LOC: 61512 64324 ERR: 0 CPU0 CPU1 0:151 0 IO-APIC-edge timer 1:286 0 IO-APIC-edge i8042 5: 0 0 IO-APIC-edge parport0 6: 3 0 IO-APIC-edge floppy 8: 1 0 IO-APIC-edge rtc 9: 0 0 IO-APIC-fasteoi acpi 12:102 0 IO-APIC-edge i8042 15: 24120 IO-APIC-edge ide1 19: 5 0 IO-APIC-fasteoi bttv0 20: 8879 0 IO-APIC-fasteoi sata_via 21: 12641 0 IO-APIC-fasteoi uhci_hcd:usb1, uhci_hcd:usb2, uhci_hcd:usb3, uhci_hcd:usb4, ehci_hcd:usb5 22: 0 0 IO-APIC-fasteoi VIA8237 23:380 0 IO-APIC-fasteoi eth0 NMI:255196 LOC: 61993 64918 ERR: 0 CPU0 CPU1 0:151 0 IO-APIC-edge timer 1:292 0 IO-APIC-edge i8042 5: 0 0 IO-APIC-edge parport0 6: 3 0 IO-APIC-edge floppy 8: 1 0 IO-APIC-edge rtc 9: 0 0 IO-APIC-fasteoi acpi 12:102 0 IO-APIC-edge i8042 15: 24144 IO-APIC-edge ide1 19: 15 0 IO-APIC-fasteoi bttv0 20: 8879 0 IO-APIC-fasteoi sata_via 21: 13169 0 IO-APIC-fasteoi uhci_hcd:usb1, uhci_hcd:usb2, uhci_hcd:usb3, uhci_hcd:usb4, ehci_hcd:usb5 22: 0 0 IO-APIC-fasteoi VIA8237 23:380 0 IO-APIC-fasteoi eth0 NMI:255196 LOC: 62237 65219 ERR: 0 [ 177.078312] [ 190.712608] ide-cd: cmd 0x1e timed out [ 190.731121] hdc: lost interrupt [0.00] Linux version 2.6.23-rt1 ([EMAIL PROTECTED]) (gcc version 4.1.2 20070925 (Red Hat 4.1.2-27)) #5 SMP PREEMPT RT Sat Oct 13 09:36:19 CEST 2007 [0.00] Command line: ro root=/dev/VolGroup00/LogVol01 [EMAIL PROTECTED]/eth0,[EMAIL PROTECTED]/ nmi_watchdog=2 [0.00] BIOS-provided physical RAM map: [0.00] BIOS-e820: - 0009fc00 (usable) [0.00] BIOS-e820: 0009fc00 - 000a (reserved) [0.00] BIOS-e820: 000e6000 - 0010 (reserved) [0.00] BIOS-e820: 0010 - 3ffb (usable) [0.00] BIOS-e820: 3ffb - 3ffc (ACPI data) [0.00] BIOS-e820: 3ffc - 3fff (ACPI NVS) [0.00] BIOS-e820: 3fff - 4000 (reserved) [0.00] BIOS-e820: fee0 - fee01000 (reserved) [0.00] BIOS-e820: ff78 - 0001 (reserved) [0.00] end_pfn_map = 1048576 [0.00] DMI 2.3 present. [0.00] ACPI: RSDP 000F7C80, 0014 (r0 ACPIAM) [0.00] ACPI: RSDT 3FFB, 0034 (r1 A M I OEMRSDT 12000521 MSFT 97) [0.00] ACPI: FACP 3FFB0200, 0084 (r2 A M I OEMFACP 12000521 MSFT 97) [0.00] ACPI: DSDT
Re: 2.6.23-rt1 lockup after loading HAL deamon
Hi I have recompiled kernel with OPROFILE disabled. I am sending in attachment /proc/interrupts (i ran it 3 times with 2 sec delay) and netconsole log. Lockup in the lock is software made with ./lockup. The kernel still locks 4-5minutes after boot without any further messages (waited more than 2 minutes). Any ideas? Rok Ingo Molnar wrote: could you disable CONFIG_OPROFILE? Maybe it interferes with the NMI watchdog? how does /proc/interrupts look like shortly after bootup? Does a simple intentional lockup piece of code, which provokes a hard lockup from user-space, get properly zapped by the NMI watchdog (within a minute or so): the NMI watchdog should produce a console message similar to: BUG: NMI Watchdog detected LOCKUP on CPU0, eip bff12345, registers: ... ( if you test ./lockup and get the message properly then i'd suggest a new reboot - i think we inhibit further console output after an NMI printout. ) Ingo CPU0 CPU1 0:151 0 IO-APIC-edge timer 1:206 0 IO-APIC-edge i8042 5: 0 0 IO-APIC-edge parport0 6: 3 0 IO-APIC-edge floppy 8: 1 0 IO-APIC-edge rtc 9: 0 0 IO-APIC-fasteoi acpi 12:102 0 IO-APIC-edge i8042 15: 24 84 IO-APIC-edge ide1 19: 3 0 IO-APIC-fasteoi bttv0 20: 8873 0 IO-APIC-fasteoi sata_via 21: 11741 0 IO-APIC-fasteoi uhci_hcd:usb1, uhci_hcd:usb2, uhci_hcd:usb3, uhci_hcd:usb4, ehci_hcd:usb5 22: 0 0 IO-APIC-fasteoi VIA8237 23:380 0 IO-APIC-fasteoi eth0 NMI:253194 LOC: 61512 64324 ERR: 0 CPU0 CPU1 0:151 0 IO-APIC-edge timer 1:286 0 IO-APIC-edge i8042 5: 0 0 IO-APIC-edge parport0 6: 3 0 IO-APIC-edge floppy 8: 1 0 IO-APIC-edge rtc 9: 0 0 IO-APIC-fasteoi acpi 12:102 0 IO-APIC-edge i8042 15: 24120 IO-APIC-edge ide1 19: 5 0 IO-APIC-fasteoi bttv0 20: 8879 0 IO-APIC-fasteoi sata_via 21: 12641 0 IO-APIC-fasteoi uhci_hcd:usb1, uhci_hcd:usb2, uhci_hcd:usb3, uhci_hcd:usb4, ehci_hcd:usb5 22: 0 0 IO-APIC-fasteoi VIA8237 23:380 0 IO-APIC-fasteoi eth0 NMI:255196 LOC: 61993 64918 ERR: 0 CPU0 CPU1 0:151 0 IO-APIC-edge timer 1:292 0 IO-APIC-edge i8042 5: 0 0 IO-APIC-edge parport0 6: 3 0 IO-APIC-edge floppy 8: 1 0 IO-APIC-edge rtc 9: 0 0 IO-APIC-fasteoi acpi 12:102 0 IO-APIC-edge i8042 15: 24144 IO-APIC-edge ide1 19: 15 0 IO-APIC-fasteoi bttv0 20: 8879 0 IO-APIC-fasteoi sata_via 21: 13169 0 IO-APIC-fasteoi uhci_hcd:usb1, uhci_hcd:usb2, uhci_hcd:usb3, uhci_hcd:usb4, ehci_hcd:usb5 22: 0 0 IO-APIC-fasteoi VIA8237 23:380 0 IO-APIC-fasteoi eth0 NMI:255196 LOC: 62237 65219 ERR: 0 [ 177.078312] [ 190.712608] ide-cd: cmd 0x1e timed out [ 190.731121] hdc: lost interrupt [0.00] Linux version 2.6.23-rt1 ([EMAIL PROTECTED]) (gcc version 4.1.2 20070925 (Red Hat 4.1.2-27)) #5 SMP PREEMPT RT Sat Oct 13 09:36:19 CEST 2007 [0.00] Command line: ro root=/dev/VolGroup00/LogVol01 [EMAIL PROTECTED]/eth0,[EMAIL PROTECTED]/ nmi_watchdog=2 [0.00] BIOS-provided physical RAM map: [0.00] BIOS-e820: - 0009fc00 (usable) [0.00] BIOS-e820: 0009fc00 - 000a (reserved) [0.00] BIOS-e820: 000e6000 - 0010 (reserved) [0.00] BIOS-e820: 0010 - 3ffb (usable) [0.00] BIOS-e820: 3ffb - 3ffc (ACPI data) [0.00] BIOS-e820: 3ffc - 3fff (ACPI NVS) [0.00] BIOS-e820: 3fff - 4000 (reserved) [0.00] BIOS-e820: fee0 - fee01000 (reserved) [0.00] BIOS-e820: ff78 - 0001 (reserved) [0.00] end_pfn_map = 1048576 [0.00] DMI 2.3 present. [0.00] ACPI: RSDP 000F7C80, 0014 (r0 ACPIAM) [0.00] ACPI: RSDT 3FFB, 0034 (r1 A M I OEMRSDT 12000521 MSFT 97) [0.00] ACPI: FACP 3FFB0200, 0084 (r2 A M I OEMFACP 12000521 MSFT 97) [0.00] ACPI: DSDT 3FFB0450, 3CF4 (r1
Re: 2.6.23-rt1 lockup after loading HAL deamon
Hi Good news (I hope). With kernel option maxcpus=1, I can not get a lock, so the system is stable and running. Where could be a problem? Best regards, Rok Ingo Molnar wrote: Hi I have recompiled kernel with OPROFILE disabled. I am sending in attachment /proc/interrupts (i ran it 3 times with 2 sec delay) and netconsole log. Lockup in the lock is software made with ./lockup. The kernel still locks 4-5minutes after boot without any further messages (waited more than 2 minutes). Any ideas? no good ideas :-( I suspect this one: [ 185.600900] hdc: lost interrupt was a side-effect of lockup.c too? does the lockup go away if you boot with maxcpus=1? Ingo - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.23-rt1 lockup after loading HAL deamon
I forgot attachment. Rok Rok Markovic wrote: > Hi > > I enabled netconsole but I am affraid that it won't help. In attachment > I am sending complete log over netconsole. While I was trying to make > everything, I got a lockup on linux-2.6.23-rc8, but I am not sure into > this. But all lockups happend in VGA console mode. Any ideas. > > Rok > > > Ingo Molnar wrote: >>> I tried to recompile with those options enabled, kernel and linux >>> boots and loads fine, but after few minutes (if i try to recompile >>> kernel in console) the system locks completely (hard reset) without >>> any messages. Is there anything I can do, maybe console on serial >>> port? My new config is atached. >> yes, serial console (or netconsole) output would be useful, if you can >> solve that. Another way would be to boot with nmi_watchdog=2, do the >> kernel recompile in a VGA text console, and wait for the lockup to >> occur. Either you get some crash message to the text console >> immediately, or you should get the NMI watchdog print something within a >> minute or so. If neither happens you just get a blank hard lockup then >> the wedge is very deep ... >> >> (also make sure that the NMI counter in /proc/interrupts is increasing >> on all CPUs properly, with nmi_watchdog=2. If not all CPUs/cores are >> increasing their NMI counters once per second then the NMI watchdog wont >> be able to print out a stackdump.) >> >> Ingo [ 859.950668] sd 2:0:0:1: [sdc] 494080 512-byte hardware sectors (253 MB) [ 859.951294] sd 2:0:0:1: [sdc] Write Protect is off [ 859.951313] sd 2:0:0:1: [sdc] Assuming drive cache: write through [ 860.618633] sd 2:0:0:1: [sdc] 494080 512-byte hardware sectors (253 MB) [ 860.619414] sd 2:0:0:1: [sdc] Write Protect is off [ 860.619433] sd 2:0:0:1: [sdc] Assuming drive cache: write through [ 1007.878314] nfsd: last server has exited [ 1007.926075] nfsd: unexporting all filesystems [ 1324.899757] nfsd: last server has exited [ 1324.952596] nfsd: unexporting all filesystems [0.00] Linux version 2.6.23-rt1 ([EMAIL PROTECTED]) (gcc version 4.1.2 20070925 (Red Hat 4.1.2-27)) #4 SMP PREEMPT RT Fri Oct 12 22:07:05 CEST 2007 [0.00] Command line: ro root=/dev/VolGroup00/LogVol01 [EMAIL PROTECTED]/eth0,[EMAIL PROTECTED]/ nmi_watchdog=2 [0.00] BIOS-provided physical RAM map: [0.00] BIOS-e820: - 0009fc00 (usable) [0.00] BIOS-e820: 0009fc00 - 000a (reserved) [0.00] BIOS-e820: 000e6000 - 0010 (reserved) [0.00] BIOS-e820: 0010 - 3ffb (usable) [0.00] BIOS-e820: 3ffb - 3ffc (ACPI data) [0.00] BIOS-e820: 3ffc - 3fff (ACPI NVS) [0.00] BIOS-e820: 3fff - 4000 (reserved) [0.00] BIOS-e820: fee0 - fee01000 (reserved) [0.00] BIOS-e820: ff78 - 0001 (reserved) [0.00] end_pfn_map = 1048576 [0.00] DMI 2.3 present. [0.00] ACPI: RSDP 000F7C80, 0014 (r0 ACPIAM) [0.00] ACPI: RSDT 3FFB, 0034 (r1 A M I OEMRSDT 12000521 MSFT 97) [0.00] ACPI: FACP 3FFB0200, 0084 (r2 A M I OEMFACP 12000521 MSFT 97) [0.00] ACPI: DSDT 3FFB0450, 3CF4 (r1 75D8P 75D8P0044 INTL 2002026) [0.00] ACPI: FACS 3FFC, 0040 [0.00] ACPI: APIC 3FFB0390, 0078 (r1 A M I OEMAPIC 12000521 MSFT 97) [0.00] ACPI: MCFG 3FFB0410, 003C (r1 A M I OEMMCFG 12000521 MSFT 97) [0.00] ACPI: OEMB 3FFC0040, 0046 (r1 A M I AMI_OEM 12000521 MSFT 97) [0.00] Zone PFN ranges: [0.00] DMA 0 -> 4096 [0.00] DMA324096 -> 1048576 [0.00] Normal1048576 -> 1048576 [0.00] Movable zone start PFN for each node [0.00] early_node_map[2] active PFN ranges [0.00] 0:0 -> 159 [0.00] 0: 256 -> 262064 [0.00] ACPI: PM-Timer IO Port: 0x808 [0.00] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) [0.00] Processor #0 (Bootup-CPU) [0.00] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled) [0.00] Processor #1 [0.00] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x82] disabled) [0.00] ACPI: LAPIC (acpi_id[0x04] lapic_id[0x83] disabled) [0.00] ACPI: IOAPIC (id[0x02] address[0xfec0] gsi_base[0]) [0.00] IOAPIC[0]: apic_id 2, address 0xfec0, GSI 0-23 [0.00] ACPI: IOAPIC (id[0x03] address[0xfecc] gsi_base[24]) [0.00] IOAPIC[1]: apic_id 3, address 0xfecc, GSI 24-47 [0.00] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) [0.00] ACPI: INT_SRC_OVR (bus
Re: 2.6.23-rt1 lockup after loading HAL deamon
Hi I enabled netconsole but I am affraid that it won't help. In attachment I am sending complete log over netconsole. While I was trying to make everything, I got a lockup on linux-2.6.23-rc8, but I am not sure into this. But all lockups happend in VGA console mode. Any ideas. Rok Ingo Molnar wrote: >> I tried to recompile with those options enabled, kernel and linux >> boots and loads fine, but after few minutes (if i try to recompile >> kernel in console) the system locks completely (hard reset) without >> any messages. Is there anything I can do, maybe console on serial >> port? My new config is atached. > > yes, serial console (or netconsole) output would be useful, if you can > solve that. Another way would be to boot with nmi_watchdog=2, do the > kernel recompile in a VGA text console, and wait for the lockup to > occur. Either you get some crash message to the text console > immediately, or you should get the NMI watchdog print something within a > minute or so. If neither happens you just get a blank hard lockup then > the wedge is very deep ... > > (also make sure that the NMI counter in /proc/interrupts is increasing > on all CPUs properly, with nmi_watchdog=2. If not all CPUs/cores are > increasing their NMI counters once per second then the NMI watchdog wont > be able to print out a stackdump.) > > Ingo - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.23-rt1 lockup after loading HAL deamon
Hi again! I tried to boot into VGA mode with NMI watchdog=2. System loads OK, nmi counter is increasing on both CPUs (procesor is HT), but when I start to load the CPU (compiling kernel), system locks without any message. Even blinking cursor disapears. I will try to do netconsole loging, but I can't promise any results for today. Rok Ingo Molnar wrote: >> I tried to recompile with those options enabled, kernel and linux >> boots and loads fine, but after few minutes (if i try to recompile >> kernel in console) the system locks completely (hard reset) without >> any messages. Is there anything I can do, maybe console on serial >> port? My new config is atached. > > yes, serial console (or netconsole) output would be useful, if you can > solve that. Another way would be to boot with nmi_watchdog=2, do the > kernel recompile in a VGA text console, and wait for the lockup to > occur. Either you get some crash message to the text console > immediately, or you should get the NMI watchdog print something within a > minute or so. If neither happens you just get a blank hard lockup then > the wedge is very deep ... > > (also make sure that the NMI counter in /proc/interrupts is increasing > on all CPUs properly, with nmi_watchdog=2. If not all CPUs/cores are > increasing their NMI counters once per second then the NMI watchdog wont > be able to print out a stackdump.) > > Ingo - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.23-rt1 lockup after loading HAL deamon
Hi again! I tried to boot into VGA mode with NMI watchdog=2. System loads OK, nmi counter is increasing on both CPUs (procesor is HT), but when I start to load the CPU (compiling kernel), system locks without any message. Even blinking cursor disapears. I will try to do netconsole loging, but I can't promise any results for today. Rok Ingo Molnar wrote: I tried to recompile with those options enabled, kernel and linux boots and loads fine, but after few minutes (if i try to recompile kernel in console) the system locks completely (hard reset) without any messages. Is there anything I can do, maybe console on serial port? My new config is atached. yes, serial console (or netconsole) output would be useful, if you can solve that. Another way would be to boot with nmi_watchdog=2, do the kernel recompile in a VGA text console, and wait for the lockup to occur. Either you get some crash message to the text console immediately, or you should get the NMI watchdog print something within a minute or so. If neither happens you just get a blank hard lockup then the wedge is very deep ... (also make sure that the NMI counter in /proc/interrupts is increasing on all CPUs properly, with nmi_watchdog=2. If not all CPUs/cores are increasing their NMI counters once per second then the NMI watchdog wont be able to print out a stackdump.) Ingo - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.23-rt1 lockup after loading HAL deamon
I forgot attachment. Rok Rok Markovic wrote: Hi I enabled netconsole but I am affraid that it won't help. In attachment I am sending complete log over netconsole. While I was trying to make everything, I got a lockup on linux-2.6.23-rc8, but I am not sure into this. But all lockups happend in VGA console mode. Any ideas. Rok Ingo Molnar wrote: I tried to recompile with those options enabled, kernel and linux boots and loads fine, but after few minutes (if i try to recompile kernel in console) the system locks completely (hard reset) without any messages. Is there anything I can do, maybe console on serial port? My new config is atached. yes, serial console (or netconsole) output would be useful, if you can solve that. Another way would be to boot with nmi_watchdog=2, do the kernel recompile in a VGA text console, and wait for the lockup to occur. Either you get some crash message to the text console immediately, or you should get the NMI watchdog print something within a minute or so. If neither happens you just get a blank hard lockup then the wedge is very deep ... (also make sure that the NMI counter in /proc/interrupts is increasing on all CPUs properly, with nmi_watchdog=2. If not all CPUs/cores are increasing their NMI counters once per second then the NMI watchdog wont be able to print out a stackdump.) Ingo [ 859.950668] sd 2:0:0:1: [sdc] 494080 512-byte hardware sectors (253 MB) [ 859.951294] sd 2:0:0:1: [sdc] Write Protect is off [ 859.951313] sd 2:0:0:1: [sdc] Assuming drive cache: write through [ 860.618633] sd 2:0:0:1: [sdc] 494080 512-byte hardware sectors (253 MB) [ 860.619414] sd 2:0:0:1: [sdc] Write Protect is off [ 860.619433] sd 2:0:0:1: [sdc] Assuming drive cache: write through [ 1007.878314] nfsd: last server has exited [ 1007.926075] nfsd: unexporting all filesystems [ 1324.899757] nfsd: last server has exited [ 1324.952596] nfsd: unexporting all filesystems [0.00] Linux version 2.6.23-rt1 ([EMAIL PROTECTED]) (gcc version 4.1.2 20070925 (Red Hat 4.1.2-27)) #4 SMP PREEMPT RT Fri Oct 12 22:07:05 CEST 2007 [0.00] Command line: ro root=/dev/VolGroup00/LogVol01 [EMAIL PROTECTED]/eth0,[EMAIL PROTECTED]/ nmi_watchdog=2 [0.00] BIOS-provided physical RAM map: [0.00] BIOS-e820: - 0009fc00 (usable) [0.00] BIOS-e820: 0009fc00 - 000a (reserved) [0.00] BIOS-e820: 000e6000 - 0010 (reserved) [0.00] BIOS-e820: 0010 - 3ffb (usable) [0.00] BIOS-e820: 3ffb - 3ffc (ACPI data) [0.00] BIOS-e820: 3ffc - 3fff (ACPI NVS) [0.00] BIOS-e820: 3fff - 4000 (reserved) [0.00] BIOS-e820: fee0 - fee01000 (reserved) [0.00] BIOS-e820: ff78 - 0001 (reserved) [0.00] end_pfn_map = 1048576 [0.00] DMI 2.3 present. [0.00] ACPI: RSDP 000F7C80, 0014 (r0 ACPIAM) [0.00] ACPI: RSDT 3FFB, 0034 (r1 A M I OEMRSDT 12000521 MSFT 97) [0.00] ACPI: FACP 3FFB0200, 0084 (r2 A M I OEMFACP 12000521 MSFT 97) [0.00] ACPI: DSDT 3FFB0450, 3CF4 (r1 75D8P 75D8P0044 INTL 2002026) [0.00] ACPI: FACS 3FFC, 0040 [0.00] ACPI: APIC 3FFB0390, 0078 (r1 A M I OEMAPIC 12000521 MSFT 97) [0.00] ACPI: MCFG 3FFB0410, 003C (r1 A M I OEMMCFG 12000521 MSFT 97) [0.00] ACPI: OEMB 3FFC0040, 0046 (r1 A M I AMI_OEM 12000521 MSFT 97) [0.00] Zone PFN ranges: [0.00] DMA 0 - 4096 [0.00] DMA324096 - 1048576 [0.00] Normal1048576 - 1048576 [0.00] Movable zone start PFN for each node [0.00] early_node_map[2] active PFN ranges [0.00] 0:0 - 159 [0.00] 0: 256 - 262064 [0.00] ACPI: PM-Timer IO Port: 0x808 [0.00] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) [0.00] Processor #0 (Bootup-CPU) [0.00] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled) [0.00] Processor #1 [0.00] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x82] disabled) [0.00] ACPI: LAPIC (acpi_id[0x04] lapic_id[0x83] disabled) [0.00] ACPI: IOAPIC (id[0x02] address[0xfec0] gsi_base[0]) [0.00] IOAPIC[0]: apic_id 2, address 0xfec0, GSI 0-23 [0.00] ACPI: IOAPIC (id[0x03] address[0xfecc] gsi_base[24]) [0.00] IOAPIC[1]: apic_id 3, address 0xfecc, GSI 24-47 [0.00] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) [0.00] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level) [0.00] Setting APIC routing to flat [0.00] Using ACPI (MADT) for SMP configuration information [0.00] Allocating PCI resources starting at 5000 (gap: 4000:bee0
Re: 2.6.23-rt1 lockup after loading HAL deamon
Hi I enabled netconsole but I am affraid that it won't help. In attachment I am sending complete log over netconsole. While I was trying to make everything, I got a lockup on linux-2.6.23-rc8, but I am not sure into this. But all lockups happend in VGA console mode. Any ideas. Rok Ingo Molnar wrote: I tried to recompile with those options enabled, kernel and linux boots and loads fine, but after few minutes (if i try to recompile kernel in console) the system locks completely (hard reset) without any messages. Is there anything I can do, maybe console on serial port? My new config is atached. yes, serial console (or netconsole) output would be useful, if you can solve that. Another way would be to boot with nmi_watchdog=2, do the kernel recompile in a VGA text console, and wait for the lockup to occur. Either you get some crash message to the text console immediately, or you should get the NMI watchdog print something within a minute or so. If neither happens you just get a blank hard lockup then the wedge is very deep ... (also make sure that the NMI counter in /proc/interrupts is increasing on all CPUs properly, with nmi_watchdog=2. If not all CPUs/cores are increasing their NMI counters once per second then the NMI watchdog wont be able to print out a stackdump.) Ingo - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Oops on arm pxa270 2.6.22
Mike Rapoport wrote: I think you have conflict between PXA serial and 8250 drivers. Make sure you use only one of them. If you need to use PCMCIA serial cards, please see http://lists.arm.linux.org.uk/pipermail/linux-arm-kernel/2007-July/040604.html Thanks, I already fixed my problem. You are right it was serial port problem. I had wrong MAJOR and MINOR numbers in serial/pxa.c Now kerel boots and works fine with -ck patch. My I ask you if you (compulab) have any plans of merging machine cm-x270 patches into mainline kernel. Thanks again, Rok Markovic - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Oops on arm pxa270 2.6.22
Hi I would like to ask what could be a problem or how could I start debuging it. My board is cm-x270 from compulab and it successfully boot until it should start init from busysbox. I get the folowing report. environment: pxa270 128Mb RAM network boot gcc 3.4.5 softfloat Linux image detected in memory at 0xA010, booting... Kernel parameters: root=/dev/nfs ip=:eth0: console=ttySA1,38400N1 bpp=16 nfsroot=192.168.10.124:/cm-x270 KERNEL_PARAMS: 0xA100 Linux version 2.6.22-cm-x270 ([EMAIL PROTECTED]) (gcc version 3.4.5) #2 Thu Jul 19 09:54:50 CEST 2007 CPU: XScale-PXA270 [69054117] revision 7 (ARMv5TE), cr=397f Machine: Compulab CM-x270 ATAG_INITRD is deprecated; please update your bootloader. Memory policy: ECC disabled, Data cache writeback Run Mode clock: 208.00MHz (*16) Turbo Mode clock: 520.00MHz (*2.5, active) Memory clock: 208.00MHz (/2) System bus clock: 208.00MHz CPU0: D VIVT undefined 5 cache CPU0: I cache: 32768 bytes, associativity 32, 32 byte lines, 32 sets CPU0: D cache: 32768 bytes, associativity 32, 32 byte lines, 32 sets Built 1 zonelists. Total pages: 32512 Kernel command line: root=/dev/nfs ip=:eth0: console=ttySA1,38400N1 bpp=16 nfsroot=192.168.10.124:/cm-x270 PID hash table entries: 512 (order: 9, 2048 bytes) Console: colour dummy device 80x30 Dentry cache hash table entries: 16384 (order: 4, 65536 bytes) Inode-cache hash table entries: 8192 (order: 3, 32768 bytes) Memory: 128MB = 128MB total Memory: 126848KB available (2492K code, 371K data, 108K init) SLUB: Genslabs=22, HWalign=32, Order=0-1, MinObjects=4, CPUs=1, Nodes=1 Mount-cache hash table entries: 512 CPU: Testing write buffer coherency: ok NET: Registered protocol family 16 SCSI subsystem initialized usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb Time: pxa_timer clocksource has been installed. NET: Registered protocol family 2 IP route cache hash table entries: 1024 (order: 0, 4096 bytes) TCP established hash table entries: 4096 (order: 3, 32768 bytes) TCP bind hash table entries: 4096 (order: 2, 16384 bytes) TCP: Hash tables configured (established 4096 bind 4096) TCP reno registered NetWinder Floating Point Emulator V0.97 (double precision) io scheduler noop registered io scheduler cfq registered (default) pxa2xx-fb pxa2xx-fb: Invalid resolution or bit depth pxa2xx-fb: probe of pxa2xx-fb failed with error -22 Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled RAMDISK driver initialized: 4 RAM disks of 4096K size 1024 blocksize loop: module loaded dm9000 Ethernet Driver eth0: dm9000 at c8802000,c8804008 IRQ 42 MAC: 00:01:c0:02:45:9a NAND device: Manufacturer ID: 0x2c, Chip ID: 0xdc (Micron NAND 512MiB 3,3V 8-bit) Scanning device for bad blocks Bad eraseblock 299 at 0x0256 Bad eraseblock 2236 at 0x1178 Using static partition definition Creating 1 MTD partitions on "NAND 512MiB 3,3V 8-bit": 0x-0x2000 : "cmx270-0" usbmon: debugfs is not available pxa27x-ohci pxa27x-ohci: PXA27x OHCI pxa27x-ohci pxa27x-ohci: new USB bus registered, assigned bus number 1 pxa27x-ohci pxa27x-ohci: irq 3, io mem 0x4c00 usb usb1: configuration #1 chosen from 1 choice hub 1-0:1.0: USB hub found hub 1-0:1.0: 3 ports detected Initializing USB Mass Storage driver... usbcore: registered new interface driver usb-storage USB Mass Storage support registered. mice: PS/2 mouse device common for all mice usbcore: registered new interface driver usbhid drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver TCP cubic registered NET: Registered protocol family 1 NET: Registered protocol family 17 XScale iWMMXt coprocessor detected. eth0: link up, 100Mbps, full-duplex, lpa 0x45E1 Sending DHCP requests ., OK IP-Config: Got DHCP answer from 0.0.0.0, my address is 192.168.10.76 IP-Config: Complete: device=eth0, addr=192.168.10.76, mask=255.255.255.0, gw=192.168.10.1, host=192.168.10.76, domain=spina.si, nis-domain=(none), bootserver=0.0.0.0, rootserver=192.168.10.124, rootpath= Looking up port of RPC 13/2 on 192.168.10.124 Looking up port of RPC 15/1 on 192.168.10.124 VFS: Mounted root (nfs filesystem). Freeing init memory: 108K Unable to handle kernel NULL pointer dereference at virtual address 0004 pgd = c0004000 [0004] *pgd= Internal error: Oops: f5 [#1] Modules linked in: CPU: 0Not tainted (2.6.22-cm-x270 #2) PC is at init_dev+0x38/0x5b8 LR is at tty_open+0xf8/0x33c pc : []lr : []psr: 6013 sp : c0423dec ip : c0423e38 fp : c0423e34 r10: r9 : r8 : 0002 r7 : 0001 r6 : c04e2200 r5 : c04e0d20 r4 : c02e5c3c r3 : r2 : c0423df0 r1 : c0423e08 r0 : c04e2200 Flags: nZCv IRQs on FIQs on Mode SVC_32 Segment kernel Control: 397f Table: a0004000 DAC: 0017 Process swapper (pid: 1, stack limit = 0xc0422260) Stack: (0xc0423dec to 0xc0424000) 3de0:c003ab44 c0423e3c c04e2200
Oops on arm pxa270 2.6.22
Hi I would like to ask what could be a problem or how could I start debuging it. My board is cm-x270 from compulab and it successfully boot until it should start init from busysbox. I get the folowing report. environment: pxa270 128Mb RAM network boot gcc 3.4.5 softfloat Linux image detected in memory at 0xA010, booting... Kernel parameters: root=/dev/nfs ip=:eth0: console=ttySA1,38400N1 bpp=16 nfsroot=192.168.10.124:/cm-x270 KERNEL_PARAMS: 0xA100 Linux version 2.6.22-cm-x270 ([EMAIL PROTECTED]) (gcc version 3.4.5) #2 Thu Jul 19 09:54:50 CEST 2007 CPU: XScale-PXA270 [69054117] revision 7 (ARMv5TE), cr=397f Machine: Compulab CM-x270 ATAG_INITRD is deprecated; please update your bootloader. Memory policy: ECC disabled, Data cache writeback Run Mode clock: 208.00MHz (*16) Turbo Mode clock: 520.00MHz (*2.5, active) Memory clock: 208.00MHz (/2) System bus clock: 208.00MHz CPU0: D VIVT undefined 5 cache CPU0: I cache: 32768 bytes, associativity 32, 32 byte lines, 32 sets CPU0: D cache: 32768 bytes, associativity 32, 32 byte lines, 32 sets Built 1 zonelists. Total pages: 32512 Kernel command line: root=/dev/nfs ip=:eth0: console=ttySA1,38400N1 bpp=16 nfsroot=192.168.10.124:/cm-x270 PID hash table entries: 512 (order: 9, 2048 bytes) Console: colour dummy device 80x30 Dentry cache hash table entries: 16384 (order: 4, 65536 bytes) Inode-cache hash table entries: 8192 (order: 3, 32768 bytes) Memory: 128MB = 128MB total Memory: 126848KB available (2492K code, 371K data, 108K init) SLUB: Genslabs=22, HWalign=32, Order=0-1, MinObjects=4, CPUs=1, Nodes=1 Mount-cache hash table entries: 512 CPU: Testing write buffer coherency: ok NET: Registered protocol family 16 SCSI subsystem initialized usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb Time: pxa_timer clocksource has been installed. NET: Registered protocol family 2 IP route cache hash table entries: 1024 (order: 0, 4096 bytes) TCP established hash table entries: 4096 (order: 3, 32768 bytes) TCP bind hash table entries: 4096 (order: 2, 16384 bytes) TCP: Hash tables configured (established 4096 bind 4096) TCP reno registered NetWinder Floating Point Emulator V0.97 (double precision) io scheduler noop registered io scheduler cfq registered (default) pxa2xx-fb pxa2xx-fb: Invalid resolution or bit depth pxa2xx-fb: probe of pxa2xx-fb failed with error -22 Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled RAMDISK driver initialized: 4 RAM disks of 4096K size 1024 blocksize loop: module loaded dm9000 Ethernet Driver eth0: dm9000 at c8802000,c8804008 IRQ 42 MAC: 00:01:c0:02:45:9a NAND device: Manufacturer ID: 0x2c, Chip ID: 0xdc (Micron NAND 512MiB 3,3V 8-bit) Scanning device for bad blocks Bad eraseblock 299 at 0x0256 Bad eraseblock 2236 at 0x1178 Using static partition definition Creating 1 MTD partitions on "NAND 512MiB 3,3V 8-bit": 0x-0x2000 : "cmx270-0" usbmon: debugfs is not available pxa27x-ohci pxa27x-ohci: PXA27x OHCI pxa27x-ohci pxa27x-ohci: new USB bus registered, assigned bus number 1 pxa27x-ohci pxa27x-ohci: irq 3, io mem 0x4c00 usb usb1: configuration #1 chosen from 1 choice hub 1-0:1.0: USB hub found hub 1-0:1.0: 3 ports detected Initializing USB Mass Storage driver... usbcore: registered new interface driver usb-storage USB Mass Storage support registered. mice: PS/2 mouse device common for all mice usbcore: registered new interface driver usbhid drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver TCP cubic registered NET: Registered protocol family 1 NET: Registered protocol family 17 XScale iWMMXt coprocessor detected. eth0: link up, 100Mbps, full-duplex, lpa 0x45E1 Sending DHCP requests ., OK IP-Config: Got DHCP answer from 0.0.0.0, my address is 192.168.10.76 IP-Config: Complete: device=eth0, addr=192.168.10.76, mask=255.255.255.0, gw=192.168.10.1, host=192.168.10.76, domain=spina.si, nis-domain=(none), bootserver=0.0.0.0, rootserver=192.168.10.124, rootpath= Looking up port of RPC 13/2 on 192.168.10.124 Looking up port of RPC 15/1 on 192.168.10.124 VFS: Mounted root (nfs filesystem). Freeing init memory: 108K Unable to handle kernel NULL pointer dereference at virtual address 0004 pgd = c0004000 [0004] *pgd= Internal error: Oops: f5 [#1] Modules linked in: CPU: 0Not tainted (2.6.22-cm-x270 #2) PC is at init_dev+0x38/0x5b8 LR is at tty_open+0xf8/0x33c pc : []lr : []psr: 6013 sp : c0423dec ip : c0423e38 fp : c0423e34 r10: r9 : r8 : 0002 r7 : 0001 r6 : c04e2200 r5 : c04e0d20 r4 : c02e5c3c r3 : r2 : c0423df0 r1 : c0423e08 r0 : c04e2200 Flags: nZCv IRQs on FIQs on Mode SVC_32 Segment kernel Control: 397f Table: a0004000 DAC: 0017 Process swapper (pid: 1, stack limit = 0xc0422260) Stack: (0xc0423dec to 0xc0424000) 3de0:c003ab44 c0423e3c c04e2200
Oops on arm pxa270 2.6.22
Hi I would like to ask what could be a problem or how could I start debuging it. My board is cm-x270 from compulab and it successfully boot until it should start init from busysbox. I get the folowing report. environment: pxa270 128Mb RAM network boot gcc 3.4.5 softfloat Linux image detected in memory at 0xA010, booting... Kernel parameters: root=/dev/nfs ip=:eth0: console=ttySA1,38400N1 bpp=16 nfsroot=192.168.10.124:/cm-x270 KERNEL_PARAMS: 0xA100 Linux version 2.6.22-cm-x270 ([EMAIL PROTECTED]) (gcc version 3.4.5) #2 Thu Jul 19 09:54:50 CEST 2007 CPU: XScale-PXA270 [69054117] revision 7 (ARMv5TE), cr=397f Machine: Compulab CM-x270 ATAG_INITRD is deprecated; please update your bootloader. Memory policy: ECC disabled, Data cache writeback Run Mode clock: 208.00MHz (*16) Turbo Mode clock: 520.00MHz (*2.5, active) Memory clock: 208.00MHz (/2) System bus clock: 208.00MHz CPU0: D VIVT undefined 5 cache CPU0: I cache: 32768 bytes, associativity 32, 32 byte lines, 32 sets CPU0: D cache: 32768 bytes, associativity 32, 32 byte lines, 32 sets Built 1 zonelists. Total pages: 32512 Kernel command line: root=/dev/nfs ip=:eth0: console=ttySA1,38400N1 bpp=16 nfsroot=192.168.10.124:/cm-x270 PID hash table entries: 512 (order: 9, 2048 bytes) Console: colour dummy device 80x30 Dentry cache hash table entries: 16384 (order: 4, 65536 bytes) Inode-cache hash table entries: 8192 (order: 3, 32768 bytes) Memory: 128MB = 128MB total Memory: 126848KB available (2492K code, 371K data, 108K init) SLUB: Genslabs=22, HWalign=32, Order=0-1, MinObjects=4, CPUs=1, Nodes=1 Mount-cache hash table entries: 512 CPU: Testing write buffer coherency: ok NET: Registered protocol family 16 SCSI subsystem initialized usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb Time: pxa_timer clocksource has been installed. NET: Registered protocol family 2 IP route cache hash table entries: 1024 (order: 0, 4096 bytes) TCP established hash table entries: 4096 (order: 3, 32768 bytes) TCP bind hash table entries: 4096 (order: 2, 16384 bytes) TCP: Hash tables configured (established 4096 bind 4096) TCP reno registered NetWinder Floating Point Emulator V0.97 (double precision) io scheduler noop registered io scheduler cfq registered (default) pxa2xx-fb pxa2xx-fb: Invalid resolution or bit depth pxa2xx-fb: probe of pxa2xx-fb failed with error -22 Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled RAMDISK driver initialized: 4 RAM disks of 4096K size 1024 blocksize loop: module loaded dm9000 Ethernet Driver eth0: dm9000 at c8802000,c8804008 IRQ 42 MAC: 00:01:c0:02:45:9a NAND device: Manufacturer ID: 0x2c, Chip ID: 0xdc (Micron NAND 512MiB 3,3V 8-bit) Scanning device for bad blocks Bad eraseblock 299 at 0x0256 Bad eraseblock 2236 at 0x1178 Using static partition definition Creating 1 MTD partitions on NAND 512MiB 3,3V 8-bit: 0x-0x2000 : cmx270-0 usbmon: debugfs is not available pxa27x-ohci pxa27x-ohci: PXA27x OHCI pxa27x-ohci pxa27x-ohci: new USB bus registered, assigned bus number 1 pxa27x-ohci pxa27x-ohci: irq 3, io mem 0x4c00 usb usb1: configuration #1 chosen from 1 choice hub 1-0:1.0: USB hub found hub 1-0:1.0: 3 ports detected Initializing USB Mass Storage driver... usbcore: registered new interface driver usb-storage USB Mass Storage support registered. mice: PS/2 mouse device common for all mice usbcore: registered new interface driver usbhid drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver TCP cubic registered NET: Registered protocol family 1 NET: Registered protocol family 17 XScale iWMMXt coprocessor detected. eth0: link up, 100Mbps, full-duplex, lpa 0x45E1 Sending DHCP requests ., OK IP-Config: Got DHCP answer from 0.0.0.0, my address is 192.168.10.76 IP-Config: Complete: device=eth0, addr=192.168.10.76, mask=255.255.255.0, gw=192.168.10.1, host=192.168.10.76, domain=spina.si, nis-domain=(none), bootserver=0.0.0.0, rootserver=192.168.10.124, rootpath= Looking up port of RPC 13/2 on 192.168.10.124 Looking up port of RPC 15/1 on 192.168.10.124 VFS: Mounted root (nfs filesystem). Freeing init memory: 108K Unable to handle kernel NULL pointer dereference at virtual address 0004 pgd = c0004000 [0004] *pgd= Internal error: Oops: f5 [#1] Modules linked in: CPU: 0Not tainted (2.6.22-cm-x270 #2) PC is at init_dev+0x38/0x5b8 LR is at tty_open+0xf8/0x33c pc : [c0135dd8]lr : [c0136450]psr: 6013 sp : c0423dec ip : c0423e38 fp : c0423e34 r10: r9 : r8 : 0002 r7 : 0001 r6 : c04e2200 r5 : c04e0d20 r4 : c02e5c3c r3 : r2 : c0423df0 r1 : c0423e08 r0 : c04e2200 Flags: nZCv IRQs on FIQs on Mode SVC_32 Segment kernel Control: 397f Table: a0004000 DAC: 0017 Process swapper (pid: 1, stack limit = 0xc0422260) Stack: (0xc0423dec to 0xc0424000) 3de0:c003ab44 c0423e3c
Oops on arm pxa270 2.6.22
Hi I would like to ask what could be a problem or how could I start debuging it. My board is cm-x270 from compulab and it successfully boot until it should start init from busysbox. I get the folowing report. environment: pxa270 128Mb RAM network boot gcc 3.4.5 softfloat Linux image detected in memory at 0xA010, booting... Kernel parameters: root=/dev/nfs ip=:eth0: console=ttySA1,38400N1 bpp=16 nfsroot=192.168.10.124:/cm-x270 KERNEL_PARAMS: 0xA100 Linux version 2.6.22-cm-x270 ([EMAIL PROTECTED]) (gcc version 3.4.5) #2 Thu Jul 19 09:54:50 CEST 2007 CPU: XScale-PXA270 [69054117] revision 7 (ARMv5TE), cr=397f Machine: Compulab CM-x270 ATAG_INITRD is deprecated; please update your bootloader. Memory policy: ECC disabled, Data cache writeback Run Mode clock: 208.00MHz (*16) Turbo Mode clock: 520.00MHz (*2.5, active) Memory clock: 208.00MHz (/2) System bus clock: 208.00MHz CPU0: D VIVT undefined 5 cache CPU0: I cache: 32768 bytes, associativity 32, 32 byte lines, 32 sets CPU0: D cache: 32768 bytes, associativity 32, 32 byte lines, 32 sets Built 1 zonelists. Total pages: 32512 Kernel command line: root=/dev/nfs ip=:eth0: console=ttySA1,38400N1 bpp=16 nfsroot=192.168.10.124:/cm-x270 PID hash table entries: 512 (order: 9, 2048 bytes) Console: colour dummy device 80x30 Dentry cache hash table entries: 16384 (order: 4, 65536 bytes) Inode-cache hash table entries: 8192 (order: 3, 32768 bytes) Memory: 128MB = 128MB total Memory: 126848KB available (2492K code, 371K data, 108K init) SLUB: Genslabs=22, HWalign=32, Order=0-1, MinObjects=4, CPUs=1, Nodes=1 Mount-cache hash table entries: 512 CPU: Testing write buffer coherency: ok NET: Registered protocol family 16 SCSI subsystem initialized usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb Time: pxa_timer clocksource has been installed. NET: Registered protocol family 2 IP route cache hash table entries: 1024 (order: 0, 4096 bytes) TCP established hash table entries: 4096 (order: 3, 32768 bytes) TCP bind hash table entries: 4096 (order: 2, 16384 bytes) TCP: Hash tables configured (established 4096 bind 4096) TCP reno registered NetWinder Floating Point Emulator V0.97 (double precision) io scheduler noop registered io scheduler cfq registered (default) pxa2xx-fb pxa2xx-fb: Invalid resolution or bit depth pxa2xx-fb: probe of pxa2xx-fb failed with error -22 Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled RAMDISK driver initialized: 4 RAM disks of 4096K size 1024 blocksize loop: module loaded dm9000 Ethernet Driver eth0: dm9000 at c8802000,c8804008 IRQ 42 MAC: 00:01:c0:02:45:9a NAND device: Manufacturer ID: 0x2c, Chip ID: 0xdc (Micron NAND 512MiB 3,3V 8-bit) Scanning device for bad blocks Bad eraseblock 299 at 0x0256 Bad eraseblock 2236 at 0x1178 Using static partition definition Creating 1 MTD partitions on NAND 512MiB 3,3V 8-bit: 0x-0x2000 : cmx270-0 usbmon: debugfs is not available pxa27x-ohci pxa27x-ohci: PXA27x OHCI pxa27x-ohci pxa27x-ohci: new USB bus registered, assigned bus number 1 pxa27x-ohci pxa27x-ohci: irq 3, io mem 0x4c00 usb usb1: configuration #1 chosen from 1 choice hub 1-0:1.0: USB hub found hub 1-0:1.0: 3 ports detected Initializing USB Mass Storage driver... usbcore: registered new interface driver usb-storage USB Mass Storage support registered. mice: PS/2 mouse device common for all mice usbcore: registered new interface driver usbhid drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver TCP cubic registered NET: Registered protocol family 1 NET: Registered protocol family 17 XScale iWMMXt coprocessor detected. eth0: link up, 100Mbps, full-duplex, lpa 0x45E1 Sending DHCP requests ., OK IP-Config: Got DHCP answer from 0.0.0.0, my address is 192.168.10.76 IP-Config: Complete: device=eth0, addr=192.168.10.76, mask=255.255.255.0, gw=192.168.10.1, host=192.168.10.76, domain=spina.si, nis-domain=(none), bootserver=0.0.0.0, rootserver=192.168.10.124, rootpath= Looking up port of RPC 13/2 on 192.168.10.124 Looking up port of RPC 15/1 on 192.168.10.124 VFS: Mounted root (nfs filesystem). Freeing init memory: 108K Unable to handle kernel NULL pointer dereference at virtual address 0004 pgd = c0004000 [0004] *pgd= Internal error: Oops: f5 [#1] Modules linked in: CPU: 0Not tainted (2.6.22-cm-x270 #2) PC is at init_dev+0x38/0x5b8 LR is at tty_open+0xf8/0x33c pc : [c0135dd8]lr : [c0136450]psr: 6013 sp : c0423dec ip : c0423e38 fp : c0423e34 r10: r9 : r8 : 0002 r7 : 0001 r6 : c04e2200 r5 : c04e0d20 r4 : c02e5c3c r3 : r2 : c0423df0 r1 : c0423e08 r0 : c04e2200 Flags: nZCv IRQs on FIQs on Mode SVC_32 Segment kernel Control: 397f Table: a0004000 DAC: 0017 Process swapper (pid: 1, stack limit = 0xc0422260) Stack: (0xc0423dec to 0xc0424000) 3de0:c003ab44 c0423e3c
Re: Oops on arm pxa270 2.6.22
Mike Rapoport wrote: I think you have conflict between PXA serial and 8250 drivers. Make sure you use only one of them. If you need to use PCMCIA serial cards, please see http://lists.arm.linux.org.uk/pipermail/linux-arm-kernel/2007-July/040604.html Thanks, I already fixed my problem. You are right it was serial port problem. I had wrong MAJOR and MINOR numbers in serial/pxa.c Now kerel boots and works fine with -ck patch. My I ask you if you (compulab) have any plans of merging machine cm-x270 patches into mainline kernel. Thanks again, Rok Markovic - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Accelerated driver for linux 2.6
Trent Waddington wrote: On 1/9/07, Rok Markovic <[EMAIL PROTECTED]> wrote: Oh, I am not sure if I can? but It is Marathon (2700G3) from intel which has core licenced from PowerVR. So I get this strange feeling that you're not going to be writing an open source accelerated driver? Trent I want to write open source driver. BUT I don't know if i am allowed to do this. Our company is small, just a few researchers, and most of software written is published under GPL licence (not all, but that is firmware for uC), all of the communication protocols are public and API is well documented, because we all agreed that we are selling hardware not software. Some lawyer should review licence, and then I could tell you more. Rok - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Accelerated driver for linux 2.6
Trent Waddington wrote: On 1/9/07, Rok Markovic [EMAIL PROTECTED] wrote: Oh, I am not sure if I can? but It is Marathon (2700G3) from intel which has core licenced from PowerVR. So I get this strange feeling that you're not going to be writing an open source accelerated driver? Trent I want to write open source driver. BUT I don't know if i am allowed to do this. Our company is small, just a few researchers, and most of software written is published under GPL licence (not all, but that is firmware for uC), all of the communication protocols are public and API is well documented, because we all agreed that we are selling hardware not software. Some lawyer should review licence, and then I could tell you more. Rok - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Accelerated driver for linux 2.6
Trent Waddington wrote: You don't even say what the hardware is that you're writing a driver for... Oh, I am not sure if I can? but It is Marathon (2700G3) from intel which has core licenced from PowerVR. Rok - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Accelerated driver for linux 2.6
Hi! I would like to ask how can I start writing accelerated driver on linux. Right now I am realy confused, because there is no real documentation about it (or I can't find one). We get the documentation which is describing hardware (sort of?!) from manufactorer, and that's it. Target platform for this driver is linux 2.6 runing Qtopia application - without X server. This message could be a bit confusing, but that is how I feel at the moment. I am not planing to implement whole 3D accelerating (for now), but only implement 2D blit and multisampling. Cheers, Rok Markovic - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Accelerated driver for linux 2.6
Hi! I would like to ask how can I start writing accelerated driver on linux. Right now I am realy confused, because there is no real documentation about it (or I can't find one). We get the documentation which is describing hardware (sort of?!) from manufactorer, and that's it. Target platform for this driver is linux 2.6 runing Qtopia application - without X server. This message could be a bit confusing, but that is how I feel at the moment. I am not planing to implement whole 3D accelerating (for now), but only implement 2D blit and multisampling. Cheers, Rok Markovic - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Accelerated driver for linux 2.6
Trent Waddington wrote: You don't even say what the hardware is that you're writing a driver for... Oh, I am not sure if I can? but It is Marathon (2700G3) from intel which has core licenced from PowerVR. Rok - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Binary Drivers
Do we have a right to reverse engineer hardware, or they are protected by patents or something similar that would prevent you from publishing results adn/or drivers (open source). Are there any restrictions in how you obtain information - signal analyser, disassembly of windows driver, etc. Rok Markovic - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Binary Drivers
Do we have a right to reverse engineer hardware, or they are protected by patents or something similar that would prevent you from publishing results adn/or drivers (open source). Are there any restrictions in how you obtain information - signal analyser, disassembly of windows driver, etc. Rok Markovic - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Binary Drivers
It seems that debate around cars and drivers has gone too far (IMHO). I do not think that there is a question if we have any right to demand details about hardware from manufactorers -> we are NOT. But I think that we have right to know how to use it. I will translate this to CAR language - We have to know how to drive the car but not all the details how is this done, so we can drive a car without the "driver". We do not need an exact knowledge about engine, ECU, suspension,... Now the real question: Why are manufatorers afraid to give us this information? and Who can benefit from this? Let's that our manufactorer is not bound on licenced part of hardware. If we would know the answers on those questions we could start thinking how can we convince Them to give us information we need to develop our own drivers. Cheers Rok Markovic - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Binary Drivers
It seems that debate around cars and drivers has gone too far (IMHO). I do not think that there is a question if we have any right to demand details about hardware from manufactorers - we are NOT. But I think that we have right to know how to use it. I will translate this to CAR language - We have to know how to drive the car but not all the details how is this done, so we can drive a car without the driver. We do not need an exact knowledge about engine, ECU, suspension,... Now the real question: Why are manufatorers afraid to give us this information? and Who can benefit from this? Let's that our manufactorer is not bound on licenced part of hardware. If we would know the answers on those questions we could start thinking how can we convince Them to give us information we need to develop our own drivers. Cheers Rok Markovic - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Binary Drivers
Hi! Maybe this does not belong to this thread, but I am wondering why manufactorers doesn't want to release specifications about drivers. They have decided to develop some hardware for, let say 3D accelaration. Now they are selling hardware and users are buying hardware. Users are not buying hardware because they want to run mighty drivers, they want to use hardware. 1. Why they do not reveal spec. if user allready bought hardware, though they give driver for free but not specs. 2. Who can contribute if they reveal specifications (how to use hardware) ? Can anyone answer does questions? PS: I am not talking about NVIDIA and ATI, but let's say intel and 2700G multimedia accelerator IC. They sell IC without specifications how to use it!? Cheers, Rok Markovic - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Binary Drivers
Hi! Maybe this does not belong to this thread, but I am wondering why manufactorers doesn't want to release specifications about drivers. They have decided to develop some hardware for, let say 3D accelaration. Now they are selling hardware and users are buying hardware. Users are not buying hardware because they want to run mighty drivers, they want to use hardware. 1. Why they do not reveal spec. if user allready bought hardware, though they give driver for free but not specs. 2. Who can contribute if they reveal specifications (how to use hardware) ? Can anyone answer does questions? PS: I am not talking about NVIDIA and ATI, but let's say intel and 2700G multimedia accelerator IC. They sell IC without specifications how to use it!? Cheers, Rok Markovic - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
