On Fri, 21 Dec 2007, Paul Gear wrote:

> Hi kernel team,
>
> Just wondering if you have any thoughts on this bug yet. It is a high
> priority bug (as it prevents the system from booting), but i forgot to
> classify it as such.

can you install 2.6.23 from unstable, install just fine on stable.

thanks

--
maks



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

2.6.24rc6 has fared no better on my machine:

DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Process modprobe (pid: 2064, threadinfo ffff8102585c000, task
ffff81012779c040)
Stack: ffff810127678a40 ffff81012be8930 0000000000000282 ffff81000000ee00
ffffffff8026c617 0000000000000000 0000000000000000 ffff81012585ddc8
ffff81012585ddb8 ffff810001029660 ffffffff8026c66c ffff81012be8d930
Call trace:
[<ffffffff8026c617>] free_hot_cold_page+0x109/0x13d
[<ffffffff8026c66c>] __pagevec_free+0x21/0x2e
[<ffffffff8026fbfb>] release_pages+0x171/0x183
[<ffffffff80275ab7>] unmap_vmas+0x41f/0x744
[<ffffffff8027f115>] free_pages_and_swap_cache+0x73/0x8f
[<ffffffff802792b0>] unmap_region+0x110/0x126
[<ffffffff80279fa7>] do_munmap+0x1f9/0x276
[<ffffffff80408228>] __down_write_nested+0x12/0x9a
[<ffffffff8027a064>] sys_munmap+0x40/0x5a
[<ffffffff8020be2e>] system_call+0x7e/0x83


Code: 41 0f a3 0c 24 19 c0 48 89 f2 48 09 fa 85 c0 48 0f 45 f2 ff
RIP [<ffffffff8026b86f>] get_pageblock_flags_group+0x56/0x7f
RSP <ffff81012585dd40>
---[ end trace a186fe4770978f0c ]---
Kernel panic - not syncing: Aiee, killing interrupt handler!

This was with irqpoll removed from the command line.

[ kicked d-kernel cc, bug reports land anyway there ]

On Tue, Jan 15, 2008 at 10:08:43AM +1000, Paul Gear wrote:
> 2.6.24rc6 has fared no better on my machine:

rc7 is out.

your report are still a bit bizarre as if some lines were
cut out, please try rc7 and install kerneloops + let it
report to upstream.

thanks

--
maks



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Tue, Jan 15, 2008 at 10:10:15AM +1000, Paul Gear wrote:
> RIP free_pages_bulk
[...]
> RIP: kmem_cache_free
[...]
> RIP: refresh_cpu_vm_stats
> general protection fault: 0000 [2] SMP
> CPU 1

This looks like broken memory or other component.

Bastian

--
Actual war is a very messy business. Very, very messy business.
-- Kirk, "A Taste of Armageddon", stardate 3193.0



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Bastian Blank wrote:
> On Tue, Jan 15, 2008 at 10:10:15AM +1000, Paul Gear wrote:
>> RIP free_pages_bulk
> [...]
>> RIP: kmem_cache_free
> [...]
>> RIP: refresh_cpu_vm_stats
>> general protection fault: 0000 [2] SMP
>> CPU 1
>
> This looks like broken memory or other component.

That might be a good call, except that the system works perfectly
reliably (with uptime in the weeks, at least) on 2.6.18-4-amd64.

Could something have changed between 2.6.18-4 and 2.6.18-5 that would
somehow exercise a hardware fault that was there previously but never
encountered?

Paul

maximilian attems wrote:
> [ kicked d-kernel cc, bug reports land anyway there ]
>
> On Tue, Jan 15, 2008 at 10:08:43AM +1000, Paul Gear wrote:
>> 2.6.24rc6 has fared no better on my machine:
>
> rc7 is out.
>
> your report are still a bit bizarre as if some lines were
> cut out, please try rc7 and install kerneloops + let it
> report to upstream.

My report is bizarre to you because i am only typing out what is on the
screen manually. I have no experience in kernel debugging. I read
these pages:

http://kernel-handbook.alioth.debian.org/ch-bugs.html
http://wiki.debian.org/DebianKernelReportingBugs

They didn't seem to offer anything new about how to collect panic
information. If someone could point me to some more specific
documentation about what information you need to solve the problem, that
would be appreciated.

One thing the latter page did mention was that identifying the point at
which the bug was introduced is important. In my case, i can say for
sure that it was between
linux-image-2.6.18-4-amd64 version 2.6.18.dfsg.1-12etch2
and linux-image-2.6.18-5-amd64 version 2.6.18.dfsg.1-17.

Paul