[PATCH v2 1/7] ARM: dts: omap3-gta04: Add ti,omap36xx to compatible property to avoid problems with booting
Without that change booting leads to crash with more warnings like below:
[0.284454] omap_hwmod: uart4: cannot clk_get main_clk uart4_fck
[0.284484] omap_hwmod: uart4: cannot _init_clocks
[0.284484] [ cut here ]
[0.284545] WARNING: CPU: 0 PID: 1 at arch/arm/mach-omap2/omap_hwmod.c:2543
_init+0x300/0x3e4()
[0.284545] omap_hwmod: uart4: couldn't init clocks
[0.284576] Modules linked in:
[0.284606] CPU: 0 PID: 1 Comm: swapper/0 Not tainted
3.13.0-next-20140124-00020-gd2aefec-dirty #26
[0.284637] [] (unwind_backtrace) from []
(show_stack+0x10/0x14)
[0.284667] [] (show_stack) from []
(dump_stack+0x7c/0x94)
[0.284729] [] (dump_stack) from []
(warn_slowpath_common+0x6c/0x90)
[0.284729] [] (warn_slowpath_common) from []
(warn_slowpath_fmt+0x30/0x40)
[0.284759] [] (warn_slowpath_fmt) from []
(_init+0x300/0x3e4)
[0.284790] [] (_init) from []
(__omap_hwmod_setup_all+0x40/0x8c)
[0.284820] [] (__omap_hwmod_setup_all) from []
(do_one_initcall+0xe8/0x14c)
[0.284851] [] (do_one_initcall) from []
(kernel_init_freeable+0x104/0x1c8)
[0.284881] [] (kernel_init_freeable) from []
(kernel_init+0x8/0x118)
[0.284912] [] (kernel_init) from []
(ret_from_fork+0x14/0x2c)
[0.285064] ---[ end trace 63de210ad43b627d ]---
Reference:
https://lkml.org/lkml/2013/10/8/553
Signed-off-by: Marek Belisko
---
arch/arm/boot/dts/omap3-gta04.dts | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/omap3-gta04.dts
b/arch/arm/boot/dts/omap3-gta04.dts
index c551e4a..d3b253b 100644
--- a/arch/arm/boot/dts/omap3-gta04.dts
+++ b/arch/arm/boot/dts/omap3-gta04.dts
@@ -13,7 +13,7 @@
/ {
model = "OMAP3 GTA04";
- compatible = "ti,omap3-gta04", "ti,omap3";
+ compatible = "ti,omap3-gta04", "ti,omap36xx", "ti,omap3";
cpus {
cpu@0 {
--
1.8.3.2
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[PATCH v2 1/7] ARM: dts: omap3-gta04: Add ti,omap36xx to compatible property to avoid problems with booting
Without that change booting leads to crash with more warnings like below:
[0.284454] omap_hwmod: uart4: cannot clk_get main_clk uart4_fck
[0.284484] omap_hwmod: uart4: cannot _init_clocks
[0.284484] [ cut here ]
[0.284545] WARNING: CPU: 0 PID: 1 at arch/arm/mach-omap2/omap_hwmod.c:2543
_init+0x300/0x3e4()
[0.284545] omap_hwmod: uart4: couldn't init clocks
[0.284576] Modules linked in:
[0.284606] CPU: 0 PID: 1 Comm: swapper/0 Not tainted
3.13.0-next-20140124-00020-gd2aefec-dirty #26
[0.284637] [c00151c0] (unwind_backtrace) from [c0011e20]
(show_stack+0x10/0x14)
[0.284667] [c0011e20] (show_stack) from [c0568544]
(dump_stack+0x7c/0x94)
[0.284729] [c0568544] (dump_stack) from [c003ff94]
(warn_slowpath_common+0x6c/0x90)
[0.284729] [c003ff94] (warn_slowpath_common) from [c003ffe8]
(warn_slowpath_fmt+0x30/0x40)
[0.284759] [c003ffe8] (warn_slowpath_fmt) from [c07d1be8]
(_init+0x300/0x3e4)
[0.284790] [c07d1be8] (_init) from [c07d217c]
(__omap_hwmod_setup_all+0x40/0x8c)
[0.284820] [c07d217c] (__omap_hwmod_setup_all) from [c0008918]
(do_one_initcall+0xe8/0x14c)
[0.284851] [c0008918] (do_one_initcall) from [c07c5c18]
(kernel_init_freeable+0x104/0x1c8)
[0.284881] [c07c5c18] (kernel_init_freeable) from [c0563524]
(kernel_init+0x8/0x118)
[0.284912] [c0563524] (kernel_init) from [c000e368]
(ret_from_fork+0x14/0x2c)
[0.285064] ---[ end trace 63de210ad43b627d ]---
Reference:
https://lkml.org/lkml/2013/10/8/553
Signed-off-by: Marek Belisko ma...@goldelico.com
---
arch/arm/boot/dts/omap3-gta04.dts | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/omap3-gta04.dts
b/arch/arm/boot/dts/omap3-gta04.dts
index c551e4a..d3b253b 100644
--- a/arch/arm/boot/dts/omap3-gta04.dts
+++ b/arch/arm/boot/dts/omap3-gta04.dts
@@ -13,7 +13,7 @@
/ {
model = OMAP3 GTA04;
- compatible = ti,omap3-gta04, ti,omap3;
+ compatible = ti,omap3-gta04, ti,omap36xx, ti,omap3;
cpus {
cpu@0 {
--
1.8.3.2
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[PATCH 9/9] ARM: dts: omap3-gta04: Add ti,omap36xx to compatible property to avoid problems with booting.
Without that change booting leads to crash with more warnings like below:
[0.284454] omap_hwmod: uart4: cannot clk_get main_clk uart4_fck
[0.284484] omap_hwmod: uart4: cannot _init_clocks
[0.284484] [ cut here ]
[0.284545] WARNING: CPU: 0 PID: 1 at arch/arm/mach-omap2/omap_hwmod.c:2543
_init+0x300/0x3e4()
[0.284545] omap_hwmod: uart4: couldn't init clocks
[0.284576] Modules linked in:
[0.284606] CPU: 0 PID: 1 Comm: swapper/0 Not tainted
3.13.0-next-20140124-00020-gd2aefec-dirty #26
[0.284637] [] (unwind_backtrace) from []
(show_stack+0x10/0x14)
[0.284667] [] (show_stack) from []
(dump_stack+0x7c/0x94)
[0.284729] [] (dump_stack) from []
(warn_slowpath_common+0x6c/0x90)
[0.284729] [] (warn_slowpath_common) from []
(warn_slowpath_fmt+0x30/0x40)
[0.284759] [] (warn_slowpath_fmt) from []
(_init+0x300/0x3e4)
[0.284790] [] (_init) from []
(__omap_hwmod_setup_all+0x40/0x8c)
[0.284820] [] (__omap_hwmod_setup_all) from []
(do_one_initcall+0xe8/0x14c)
[0.284851] [] (do_one_initcall) from []
(kernel_init_freeable+0x104/0x1c8)
[0.284881] [] (kernel_init_freeable) from []
(kernel_init+0x8/0x118)
[0.284912] [] (kernel_init) from []
(ret_from_fork+0x14/0x2c)
[0.285064] ---[ end trace 63de210ad43b627d ]---
Reference:
https://lkml.org/lkml/2013/10/8/553
Signed-off-by: Marek Belisko
---
arch/arm/boot/dts/omap3-gta04.dts | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/omap3-gta04.dts
b/arch/arm/boot/dts/omap3-gta04.dts
index ea1b94d..998fe1e 100644
--- a/arch/arm/boot/dts/omap3-gta04.dts
+++ b/arch/arm/boot/dts/omap3-gta04.dts
@@ -13,7 +13,7 @@
/ {
model = "OMAP3 GTA04";
- compatible = "ti,omap3-gta04", "ti,omap3";
+ compatible = "ti,omap3-gta04", "ti,omap36xx", "ti,omap3";
cpus {
cpu@0 {
--
1.8.3.2
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[PATCH 9/9] ARM: dts: omap3-gta04: Add ti,omap36xx to compatible property to avoid problems with booting.
Without that change booting leads to crash with more warnings like below:
[0.284454] omap_hwmod: uart4: cannot clk_get main_clk uart4_fck
[0.284484] omap_hwmod: uart4: cannot _init_clocks
[0.284484] [ cut here ]
[0.284545] WARNING: CPU: 0 PID: 1 at arch/arm/mach-omap2/omap_hwmod.c:2543
_init+0x300/0x3e4()
[0.284545] omap_hwmod: uart4: couldn't init clocks
[0.284576] Modules linked in:
[0.284606] CPU: 0 PID: 1 Comm: swapper/0 Not tainted
3.13.0-next-20140124-00020-gd2aefec-dirty #26
[0.284637] [c00151c0] (unwind_backtrace) from [c0011e20]
(show_stack+0x10/0x14)
[0.284667] [c0011e20] (show_stack) from [c0568544]
(dump_stack+0x7c/0x94)
[0.284729] [c0568544] (dump_stack) from [c003ff94]
(warn_slowpath_common+0x6c/0x90)
[0.284729] [c003ff94] (warn_slowpath_common) from [c003ffe8]
(warn_slowpath_fmt+0x30/0x40)
[0.284759] [c003ffe8] (warn_slowpath_fmt) from [c07d1be8]
(_init+0x300/0x3e4)
[0.284790] [c07d1be8] (_init) from [c07d217c]
(__omap_hwmod_setup_all+0x40/0x8c)
[0.284820] [c07d217c] (__omap_hwmod_setup_all) from [c0008918]
(do_one_initcall+0xe8/0x14c)
[0.284851] [c0008918] (do_one_initcall) from [c07c5c18]
(kernel_init_freeable+0x104/0x1c8)
[0.284881] [c07c5c18] (kernel_init_freeable) from [c0563524]
(kernel_init+0x8/0x118)
[0.284912] [c0563524] (kernel_init) from [c000e368]
(ret_from_fork+0x14/0x2c)
[0.285064] ---[ end trace 63de210ad43b627d ]---
Reference:
https://lkml.org/lkml/2013/10/8/553
Signed-off-by: Marek Belisko ma...@goldelico.com
---
arch/arm/boot/dts/omap3-gta04.dts | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/omap3-gta04.dts
b/arch/arm/boot/dts/omap3-gta04.dts
index ea1b94d..998fe1e 100644
--- a/arch/arm/boot/dts/omap3-gta04.dts
+++ b/arch/arm/boot/dts/omap3-gta04.dts
@@ -13,7 +13,7 @@
/ {
model = OMAP3 GTA04;
- compatible = ti,omap3-gta04, ti,omap3;
+ compatible = ti,omap3-gta04, ti,omap36xx, ti,omap3;
cpus {
cpu@0 {
--
1.8.3.2
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: Problems on booting
On Saturday, 22 of December 2007, werner wrote: > There seems to have two regressions between the kernels from yesterday and > before-yesterday > On the kernel -git7 what didnt happened on -git6 > > 1) My hard disk is /dev/hda, but when I have an usb key sticked in /dev/sba, I guess you mean /dev/sda? > and run lilo then, then it dont boot but give L99 99 99 99 ... error. When I > remove the usb stick from /dev/sba , and run then #lilo , then the result > boots. This problem was not present at the -git6 kernel > > 2) The boot stops / hangs on hardware detection of SCSI. I have an Initio > INI-9X00U/UW. The last messages during boot are, that it's verifying i91u > scsi2 , then the boot hangs. When I put the pci=off kernel option, then the > boot process continues (but with this, by other reasons, my computer works > only half, so that this is unpracticable). This problem also didnt > happens with the -git6 kernelThis problem happens only on one of my two > computers, because the other has no SCSI card inside, that computer boots > normally. I have opened a bugzilla entry at http://bugzilla.kernel.org/show_bug.cgi?id=9621 and added it to the list of reported regressions. Thanks, Rafael -- 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/
Problems on booting
There seems to have two regressions between the kernels from yesterday and before-yesterday On the kernel -git7 what didnt happened on -git6 1) My hard disk is /dev/hda, but when I have an usb key sticked in /dev/sba, and run lilo then, then it dont boot but give L99 99 99 99 ... error. When I remove the usb stick from /dev/sba , and run then #lilo , then the result boots. This problem was not present at the -git6 kernel 2) The boot stops / hangs on hardware detection of SCSI. I have an Initio INI-9X00U/UW. The last messages during boot are, that it's verifying i91u scsi2 , then the boot hangs. When I put the pci=off kernel option, then the boot process continues (but with this, by other reasons, my computer works only half, so that this is unpracticable). This problem also didnt happens with the -git6 kernelThis problem happens only on one of my two computers, because the other has no SCSI card inside, that computer boots normally. [EMAIL PROTECTED] == *** www.copaya.yi.org / www.monkey.is-a-geek.net *** O único servidor comunitário na Guiana-Francesa. Situado no local, rápido, imuno contra guerras / desastres na Europa. Serviço não-comercial e gratuito de: http (forum, página web), irc (chat), ftp (download), name (subdomain) .
Problems on booting
There seems to have two regressions between the kernels from yesterday and before-yesterday On the kernel -git7 what didnt happened on -git6 1) My hard disk is /dev/hda, but when I have an usb key sticked in /dev/sba, and run lilo then, then it dont boot but give L99 99 99 99 ... error. When I remove the usb stick from /dev/sba , and run then #lilo , then the result boots. This problem was not present at the -git6 kernel 2) The boot stops / hangs on hardware detection of SCSI. I have an Initio INI-9X00U/UW. The last messages during boot are, that it's verifying i91u scsi2 , then the boot hangs. When I put the pci=off kernel option, then the boot process continues (but with this, by other reasons, my computer works only half, so that this is unpracticable). This problem also didnt happens with the -git6 kernelThis problem happens only on one of my two computers, because the other has no SCSI card inside, that computer boots normally. [EMAIL PROTECTED] == *** www.copaya.yi.org / www.monkey.is-a-geek.net *** O único servidor comunitário na Guiana-Francesa. Situado no local, rápido, imuno contra guerras / desastres na Europa. Serviço não-comercial e gratuito de: http (forum, página web), irc (chat), ftp (download), name (subdomain) .
Re: Problems on booting
On Saturday, 22 of December 2007, werner wrote: There seems to have two regressions between the kernels from yesterday and before-yesterday On the kernel -git7 what didnt happened on -git6 1) My hard disk is /dev/hda, but when I have an usb key sticked in /dev/sba, I guess you mean /dev/sda? and run lilo then, then it dont boot but give L99 99 99 99 ... error. When I remove the usb stick from /dev/sba , and run then #lilo , then the result boots. This problem was not present at the -git6 kernel 2) The boot stops / hangs on hardware detection of SCSI. I have an Initio INI-9X00U/UW. The last messages during boot are, that it's verifying i91u scsi2 , then the boot hangs. When I put the pci=off kernel option, then the boot process continues (but with this, by other reasons, my computer works only half, so that this is unpracticable). This problem also didnt happens with the -git6 kernelThis problem happens only on one of my two computers, because the other has no SCSI card inside, that computer boots normally. I have opened a bugzilla entry at http://bugzilla.kernel.org/show_bug.cgi?id=9621 and added it to the list of reported regressions. Thanks, Rafael -- 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/
