Hi,
on recent Linus git, I regulary get the following backtrace (since 3.17 around
or so).
HW is Intel Corporation Wireless 7260 (rev 83)
[ 1774.340980] [ cut here ]
[ 1774.341003] WARNING: CPU: 2 PID: 2402 at
Hi,
on recent Linus git, I regulary get the following backtrace (since 3.17 around
or so).
HW is Intel Corporation Wireless 7260 (rev 83)
[ 1774.340980] [ cut here ]
[ 1774.341003] WARNING: CPU: 2 PID: 2402 at
Hi,
when changing the refresh rate of my laptop display with xrandr on 3.11.0-rc5,
like:
xrandr --output LVDS1 --rate 59.9 --mode 1920x1080
The following WARNING is generated:
[ 50.018055] [drm:intel_pipe_config_compare] *ERROR* mismatch in
adjusted_mode.flags (expected 1, found 0)
[
Hi,
when changing the refresh rate of my laptop display with xrandr on 3.11.0-rc5,
like:
xrandr --output LVDS1 --rate 59.9 --mode 1920x1080
The following WARNING is generated:
[ 50.018055] [drm:intel_pipe_config_compare] *ERROR* mismatch in
adjusted_mode.flags (expected 1, found 0)
[
87] ata5.00: configured for UDMA/100
Testing revealed no transfer issues.
Signed-off-by: Arnd Hannemann
---
drivers/ata/pata_atiixp.c | 16
1 file changed, 16 insertions(+)
diff --git a/drivers/ata/pata_atiixp.c b/drivers/ata/pata_atiixp.c
index 361c75c..24e5105 100644
--- a
Testing revealed no transfer issues.
Signed-off-by: Arnd Hannemann a...@arndnet.de
---
drivers/ata/pata_atiixp.c | 16
1 file changed, 16 insertions(+)
diff --git a/drivers/ata/pata_atiixp.c b/drivers/ata/pata_atiixp.c
index 361c75c..24e5105 100644
--- a/drivers/ata/pata_atiixp.c
J.C. Pizarro schrieb:
> 2008/2/25, Ady Wicaksono <[EMAIL PROTECTED]>:
>> I have 8 Gbytes RAM, but why I can allocate 2.8 Gbytes RAM for a single
>> process?
>> How to patch kernel so I have more than 2.8 Gbytes limitation?
>>
>> Kernel:
>> ---
>> Linux xxx.com
J.C. Pizarro schrieb:
2008/2/25, Ady Wicaksono [EMAIL PROTECTED]:
I have 8 Gbytes RAM, but why I can allocate 2.8 Gbytes RAM for a single
process?
How to patch kernel so I have more than 2.8 Gbytes limitation?
Kernel:
---
Linux xxx.com
Arnd Hannemann wrote:
> Jeremy Fitzhardinge wrote:
>> Arnd Hannemann wrote:
>>> This is with 2.6.24.2, but latest-git looks the same:
>>> I also tried with 2.6.23 which crashes instantly, without any output
>>> of the guest.
>>>
>> I'm n
Arnd Hannemann wrote:
Jeremy Fitzhardinge wrote:
Arnd Hannemann wrote:
This is with 2.6.24.2, but latest-git looks the same:
I also tried with 2.6.23 which crashes instantly, without any output
of the guest.
I'm not too surprised. Non-PAE Xen is a bit of a rarity, and it only
gets
Jeremy Fitzhardinge wrote:
> Arnd Hannemann wrote:
>> This is with 2.6.24.2, but latest-git looks the same:
>> I also tried with 2.6.23 which crashes instantly, without any output
>> of the guest.
>>
>
> I'm not too surprised. Non-PAE Xen is a bit of a rarity,
Jeremy Fitzhardinge schrieb:
> Arnd Hannemann wrote:
>> As paravirtualized xen guests won't work with !X86_PAE, change the
>> Kconfig
>> accordingly.
>>
>
> !PAE is supposed to work, but it is a rarely used configuration. How
> does it fail?
>
>J
Ian Campbell schrieb:
> On Fri, 2008-02-22 at 12:00 +0100, Arnd Hannemann wrote:
>> As paravirtualized xen guests won't work with !X86_PAE, change the Kconfig
>> accordingly.
>
> Really? Xen guests should work on non-PAE if you have a non-PAE
> hypervisor (which most dist
Hi,
As paravirtualized xen guests won't work with !X86_PAE, change the Kconfig
accordingly.
Signed-off-by: Arnd Hannemann <[EMAIL PROTECTED]>
diff --git a/arch/x86/xen/Kconfig b/arch/x86/xen/Kconfig
index 4d5f264..2035238 100644
--- a/arch/x86/xen/Kconfig
+++ b/arch/x86/xen/Kconfig
@@ -6,
Hi,
As paravirtualized xen guests won't work with !X86_PAE, change the Kconfig
accordingly.
Signed-off-by: Arnd Hannemann [EMAIL PROTECTED]
diff --git a/arch/x86/xen/Kconfig b/arch/x86/xen/Kconfig
index 4d5f264..2035238 100644
--- a/arch/x86/xen/Kconfig
+++ b/arch/x86/xen/Kconfig
@@ -6,7 +6,7
Ian Campbell schrieb:
On Fri, 2008-02-22 at 12:00 +0100, Arnd Hannemann wrote:
As paravirtualized xen guests won't work with !X86_PAE, change the Kconfig
accordingly.
Really? Xen guests should work on non-PAE if you have a non-PAE
hypervisor (which most distros don't ship but which does
Jeremy Fitzhardinge schrieb:
Arnd Hannemann wrote:
As paravirtualized xen guests won't work with !X86_PAE, change the
Kconfig
accordingly.
!PAE is supposed to work, but it is a rarely used configuration. How
does it fail?
J
This is with 2.6.24.2, but latest-git looks the same
Jeremy Fitzhardinge wrote:
Arnd Hannemann wrote:
This is with 2.6.24.2, but latest-git looks the same:
I also tried with 2.6.23 which crashes instantly, without any output
of the guest.
I'm not too surprised. Non-PAE Xen is a bit of a rarity, and it only
gets tested rarely. Chris
Iain Paton schrieb:
> Adrian Bunk wrote:
>> On Sun, Feb 17, 2008 at 03:46:01PM +0100, Arnd Hannemann wrote:
>>> Never tried to built it as a module.
>>> Probably there are issues with that. If I remember correctly I saw a
>>> patch in 2.6.25-rc which
>>>
Hi,
Iain Paton wrote:
> Arnd Hannemann wrote:
>
>> I can confirm that it is still working fine :-)
>
> Hi,
>
> Has anyone managed to build this as a module against the full 2.6.24
> release ?
>
> I am seeing the following error:
>
> CC [M] lib
Hi,
Iain Paton wrote:
Arnd Hannemann wrote:
I can confirm that it is still working fine :-)
Hi,
Has anyone managed to build this as a module against the full 2.6.24
release ?
I am seeing the following error:
CC [M] lib/zlib_inflate/infutil.o
CC [M] lib/zlib_inflate
Iain Paton schrieb:
Adrian Bunk wrote:
On Sun, Feb 17, 2008 at 03:46:01PM +0100, Arnd Hannemann wrote:
Never tried to built it as a module.
Probably there are issues with that. If I remember correctly I saw a
patch in 2.6.25-rc which
mentioned that using mfgpt in modules won't work. Does
cter which
is not a valid sysrq. (The probability to trigger another sysrq with random
data is much lower, but
did you find any other printout of an sysrq in your logs?)
Best regards,
Arnd Hannemann
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of
. (The probability to trigger another sysrq with random
data is much lower, but
did you find any other printout of an sysrq in your logs?)
Best regards,
Arnd Hannemann
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More
Hi,
Jordan Crouse schrieb:
> On 23/01/08 23:11 +0100, Willy Tarreau wrote:
>> Hi Peter,
>>
>> On Wed, Jan 23, 2008 at 01:59:32PM -0800, H. Peter Anvin wrote:
>>> Willy Tarreau wrote:
The GEODE MFGPT code assumed that 32kHz was 32000 Hz while the boards
run on a 32.768 kHz digital watch
Hi,
Jordan Crouse schrieb:
On 23/01/08 23:11 +0100, Willy Tarreau wrote:
Hi Peter,
On Wed, Jan 23, 2008 at 01:59:32PM -0800, H. Peter Anvin wrote:
Willy Tarreau wrote:
The GEODE MFGPT code assumed that 32kHz was 32000 Hz while the boards
run on a 32.768 kHz digital watch crystal. In
Hi,
Jordan Crouse schrieb:
>> Indeed.
>> Strange, it works at least with mfgpt_irq=8 (rtc) and mfgpt_irq=5 (audio):
>
> I have most excellent news. I was able to get tinyBIOS booting on my
> development platform. I looked at the problem with the debugger and
> I think I might have found
Hi Lars,
Lars Heete schrieb:
> Hello,
>
> On Tuesday 22 January 2008 10:03:08 am Arnd Hannemann wrote:
>> Jordan Crouse wrote:
>>> Okay - I've been exploring a little bit more. I talked to the TinyBIOS
>>> developer, and he verified that TinyBIOS shouldn't use a
Jordan Crouse wrote:
> Okay - I've been exploring a little bit more. I talked to the TinyBIOS
> developer, and he verified that TinyBIOS shouldn't use any MFGPT timers.
> He also told me that the mysterious "MFGPT workaround" was in fact the
> magic MFGPT erasing MSR that was in the old kernel
Jordan Crouse wrote:
Okay - I've been exploring a little bit more. I talked to the TinyBIOS
developer, and he verified that TinyBIOS shouldn't use any MFGPT timers.
He also told me that the mysterious MFGPT workaround was in fact the
magic MFGPT erasing MSR that was in the old kernel driver.
Hi Lars,
Lars Heete schrieb:
Hello,
On Tuesday 22 January 2008 10:03:08 am Arnd Hannemann wrote:
Jordan Crouse wrote:
Okay - I've been exploring a little bit more. I talked to the TinyBIOS
developer, and he verified that TinyBIOS shouldn't use any MFGPT timers.
He also told me
Hi,
Jordan Crouse schrieb:
Indeed.
Strange, it works at least with mfgpt_irq=8 (rtc) and mfgpt_irq=5 (audio):
I have most excellent news. I was able to get tinyBIOS booting on my
development platform. I looked at the problem with the debugger and
I think I might have found something. It
Jordan Crouse schrieb:
> On 20/01/08 14:22 +0100, Arnd Hannemann wrote:
>> Hi,
>>
>> Jordan Crouse wrote:
>>> On 17/01/08 23:52 +0100, Arnd Hannemann wrote:
>>>>>> Watchdog for the new API would be great :-)
>>>>> Coming soon.
&g
Jordan Crouse schrieb:
On 20/01/08 14:22 +0100, Arnd Hannemann wrote:
Hi,
Jordan Crouse wrote:
On 17/01/08 23:52 +0100, Arnd Hannemann wrote:
Watchdog for the new API would be great :-)
Coming soon.
As promised, a watchdog driver for the Geode GX/LX processors is attached.
I basically
ing CONFIG_GEODE_MFGPT_TIMER won't be enough to
boot 2.6.24-rc8 on a v0.98 bios or on a v0.99 bios with MFGPT workaround
turned on in the bios menu.
Otherwise the system will hang in arch/x86/kernel/mfgpt_32.c while
trying to detect MFGPT timers.
To clearify, for us the following works:
v0.99 bios, MF
Hi,
Jordan Crouse wrote:
> On 17/01/08 23:52 +0100, Arnd Hannemann wrote:
>>>> Watchdog for the new API would be great :-)
>>> Coming soon.
>
> As promised, a watchdog driver for the Geode GX/LX processors is attached.
> I basically just ported the previous pat
Hi,
Jordan Crouse wrote:
On 17/01/08 23:52 +0100, Arnd Hannemann wrote:
Watchdog for the new API would be great :-)
Coming soon.
As promised, a watchdog driver for the Geode GX/LX processors is attached.
I basically just ported the previous patch forward to 2.6.24.
Great work!
I also
and
CONFIG_GEODE_MFGPT_TIMER=n
--- snip ---
Best regards,
Arnd Hannemann
--
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/
Jordan Crouse schrieb:
> On 17/01/08 23:52 +0100, Arnd Hannemann wrote:
>
>
>
>>> Hmmm - not sure whats happening here. I wonder if we're stuck in an
>>> interrupt storm of some sort as soon as you register the interrupt handler.
>>> But I would think
Jordan Crouse wrote:
> On 17/01/08 22:50 +0100, Arnd Hannemann wrote:
>> Jordan Crouse schrieb:
>>> On 17/01/08 20:53 +0100, Arnd Hannemann wrote:
>>>> Andres Salomon schrieb:
>>>>> On Thu, 17 Jan 2008 10:54:30 +0100
>>>>> Arnd Hann
Jordan Crouse schrieb:
> On 17/01/08 20:53 +0100, Arnd Hannemann wrote:
>> Andres Salomon schrieb:
>>> On Thu, 17 Jan 2008 10:54:30 +0100
>>> Arnd Hannemann <[EMAIL PROTECTED]> wrote:
>>>
>>>> Andres Salomon schrieb:
>>>>> On W
Andres Salomon schrieb:
> On Thu, 17 Jan 2008 10:54:30 +0100
> Arnd Hannemann <[EMAIL PROTECTED]> wrote:
>
>> Andres Salomon schrieb:
>>> On Wed, 16 Jan 2008 16:19:12 -0500
>>> Andres Salomon <[EMAIL PROTECTED]> wrote:
>>>
>>>&
Andres Salomon schrieb:
> On Wed, 16 Jan 2008 16:19:12 -0500
> Andres Salomon <[EMAIL PROTECTED]> wrote:
>
>> On Wed, 16 Jan 2008 18:44:07 +0100
>> Arnd Hannemann <[EMAIL PROTECTED]> wrote:
>>
>>> Hi,
>>>
>>> I'm trying to boot 2.6
Andres Salomon schrieb:
On Thu, 17 Jan 2008 10:54:30 +0100
Arnd Hannemann [EMAIL PROTECTED] wrote:
Andres Salomon schrieb:
On Wed, 16 Jan 2008 16:19:12 -0500
Andres Salomon [EMAIL PROTECTED] wrote:
On Wed, 16 Jan 2008 18:44:07 +0100
Arnd Hannemann [EMAIL PROTECTED] wrote:
Hi,
I'm
Jordan Crouse schrieb:
On 17/01/08 20:53 +0100, Arnd Hannemann wrote:
Andres Salomon schrieb:
On Thu, 17 Jan 2008 10:54:30 +0100
Arnd Hannemann [EMAIL PROTECTED] wrote:
Andres Salomon schrieb:
On Wed, 16 Jan 2008 16:19:12 -0500
Andres Salomon [EMAIL PROTECTED] wrote:
On Wed, 16 Jan 2008
Jordan Crouse wrote:
On 17/01/08 22:50 +0100, Arnd Hannemann wrote:
Jordan Crouse schrieb:
On 17/01/08 20:53 +0100, Arnd Hannemann wrote:
Andres Salomon schrieb:
On Thu, 17 Jan 2008 10:54:30 +0100
Arnd Hannemann [EMAIL PROTECTED] wrote:
Andres Salomon schrieb:
On Wed, 16 Jan 2008 16:19:12
Jordan Crouse schrieb:
On 17/01/08 23:52 +0100, Arnd Hannemann wrote:
snip
Hmmm - not sure whats happening here. I wonder if we're stuck in an
interrupt storm of some sort as soon as you register the interrupt handler.
But I would think that whatever was causing the interrupt storm would
available here:
http://www.umic-mesh.net/~hannemann/config-2.6.24-rc8
Best regards,
Arnd Hannemann
[0.00] Linux version 2.6.24-rc8 ([EMAIL PROTECTED]) (gcc version 4.1.2
20060928 (prerelease) (Ubuntu 4.1.1-13ubuntu5)) #7 Wed Jan 16 17:47:15 CE8
[0.00] BIOS-provided physical RAM
available here:
http://www.umic-mesh.net/~hannemann/config-2.6.24-rc8
Best regards,
Arnd Hannemann
[0.00] Linux version 2.6.24-rc8 ([EMAIL PROTECTED]) (gcc version 4.1.2
20060928 (prerelease) (Ubuntu 4.1.1-13ubuntu5)) #7 Wed Jan 16 17:47:15 CE8
[0.00] BIOS-provided physical RAM
Hi,
Zurk Tech schrieb:
> i was trying to move my truecrypt container from my xp box to my
> debian etch box.
> on windows xp its just double click to mount it, no need to even
> install with the portable option.
> on linux i had to download the source of the kernel, compile it, add
> the
Hi,
Zurk Tech schrieb:
i was trying to move my truecrypt container from my xp box to my
debian etch box.
on windows xp its just double click to mount it, no need to even
install with the portable option.
on linux i had to download the source of the kernel, compile it, add
the truecrypt
Jan Engelhardt schrieb:
> On Jun 24 2007 23:27, Salvatore De Paolis wrote:
>> i built the kernel with a busybox initramfs which runs from a usb stick.
>> While
>> i boot i need to mount the real root and i'm using pivot_root.
>> Pivot_root . old-root return to me an "Invalid argument" error and
Jan Engelhardt schrieb:
On Jun 24 2007 23:27, Salvatore De Paolis wrote:
i built the kernel with a busybox initramfs which runs from a usb stick.
While
i boot i need to mount the real root and i'm using pivot_root.
Pivot_root . old-root return to me an Invalid argument error and googling i
53 matches
Mail list logo
