All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Oliver Pitzeier" <o.pitzeier@uptime.at>
To: "'Jan-Benedict Glaw'" <jbglaw@lug-owl.de>,
	<linux-kernel@vger.kernel.org>, <axp-kernel-list@redhat.com>
Cc: "'Ivan Kokshaysky'" <ink@jurassic.park.msu.ru>
Subject: RE: kernel 2.5.20 on alpha (RE: [patch] Re: kernel 2.5.18 on alpha)
Date: Tue, 4 Jun 2002 17:13:08 +0200	[thread overview]
Message-ID: <001b01c20bda$58cea930$010b10ac@sbp.uptime.at> (raw)
In-Reply-To: <20020604142207.GN20788@lug-owl.de>

Jan-Benedict Glaw wrote:
> That's a known problem. Please look for my mail with Subject 
> "[2.5.19] Oops during PCI scan on Alpha". One follow-up had a 
> working (but
> hackish) fix.
[ ... ]

OK. Next error. I give up for today. :o)
[ ... ]
Freeing unused kernel memory: 360k freed
Kernel bug at ll_rw_blk.c:1602
swapper(1): Kernel Bug 1
pc = [<fffffc000040b850>]  ra = [<fffffc000040ba44>]  ps = 0000    Not
tainted
v0 = 0000000000000000  t0 = 0000000000000060  t1 = 0000000000000001
t2 = fffffc000fd84740  t3 = 0000000000000000  t4 = 0000000000000060
t5 = 0000000000000001  t6 = fffffc000fcfabf0  t7 = fffffc00008a8000
a0 = fffffc000fee08c0  a1 = fffffc000fee08c0  a2 = fffffc00008ab4e0
a3 = fffffc00008ab4f0  a4 = fffffc00008ab554  a5 = 0000000000000001
t8 = 0000000000000000  t9 = 0000000000000001  t10= 0000000000000000
t11= 0000000000000278  pv = fffffc000040b9a0  at = fffffc00005acc90
gp = fffffc00005eece8  sp = fffffc00008ab530
Trace:fffffc000040ba44 fffffc0000382e00 fffffc00003831f4
fffffc0000383354 fffffc00003b2280 fffffc00003d630c fffffc00003464ac
fffffc00003b2280 fffffc00003b280c fffffc0000359c10 fffffc0000359e14
fffffc0000347204 fffffc0000347928 fffffc00003477d0 fffffc0000368b58
fffffc0000369a00 fffffc000031078c fffffc00003101cc fffffc0000310708
fffffc0000310bf8 fffffc000032ed58 fffffc000031008c fffffc00003100b0
fffffc00003106f0 
Code: 4821f621  48213681  48407622  404103a2  e4400005  00000081
<00000642> 0057c095 
Kernel panic: Attempted to kill init!



  reply	other threads:[~2002-06-04 15:13 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-04 10:11 kernel 2.5.20 on alpha (RE: [patch] Re: kernel 2.5.18 on alpha) Oliver Pitzeier
2002-06-04 12:45 ` Oliver Pitzeier
2002-06-04 14:06   ` Oliver Pitzeier
2002-06-04 14:22     ` Jan-Benedict Glaw
2002-06-04 15:13       ` Oliver Pitzeier [this message]
2002-06-04 15:47       ` Oliver Pitzeier
2002-06-04 14:40     ` Oliver Pitzeier
2002-06-04 15:19       ` Patrick Mochel
2002-06-04 15:33         ` Oliver Pitzeier
2002-06-04 20:23         ` Michal Jaegermann
2002-06-04 20:36           ` Jeff Garzik
2002-06-04 22:00         ` Paul Mackerras
2002-06-04 22:07           ` kernel 2.5.20 on alpha David S. Miller
2002-06-04 16:24     ` kernel 2.5.20 on alpha (RE: [patch] Re: kernel 2.5.18 on alpha) Thunder from the hill
2002-06-04 20:04 ` David Mosberger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='001b01c20bda$58cea930$010b10ac@sbp.uptime.at' \
    --to=o.pitzeier@uptime.at \
    --cc=axp-kernel-list@redhat.com \
    --cc=ink@jurassic.park.msu.ru \
    --cc=jbglaw@lug-owl.de \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.