All of lore.kernel.org
 help / color / mirror / Atom feed
From: Helge Deller <deller@gmx.de>
To: petkovbb@gmail.com
Cc: Linus <torvalds@linux-foundation.org>,
	Borislav Petkov <petkovbb@googlemail.com>,
	Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
	Kyle McMartin <kyle@mcmartin.ca>,
	linux-parisc <linux-parisc@vger.kernel.org>,
	"Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: [PATCH] ide-cd: fix kernel crash on hppa regression
Date: Fri, 17 Apr 2009 09:15:27 +0200	[thread overview]
Message-ID: <49E82C8F.5060202@gmx.de> (raw)
In-Reply-To: <20090417065344.GC6806@liondog.tnic>

Borislav Petkov wrote:
> Hi,
> 
> On Thu, Apr 16, 2009 at 10:26:06PM +0200, Helge Deller wrote:
> 
> [..]
> 
>> I tried to build a kernel with CONFIG_DEBUG_INFO.
>> There are two problem with that, because I'm cross-compiling:
>> a) I don't have a cross-gdb (but I could use addr2line instead though)
>> b) the resulting kernel is becoming too big and won't link/boot:ina
>> ...
>>   SYSMAP  System.map
>>   SYSMAP  .tmp_System.map
>> /sbin/palo -f /mnt/sda4/home/cvs/parisc/git-kernel/linus-linux-2.6-32bit/palo.conf
>> palo version 1.14 deller@p100 Fri Jul 28 22:55:11 CEST 2006
>> ELF32 executable
>> ipl: addr 2048 size 36864 entry 0x0
>>  ko 0x0 ksz 0 k64o 0x0 k64sz 0 rdo 0 rdsz 0
>> <>
>> Your 32-bit-kernel is too big for your F0 partition
>> make[3]: *** [palo] Error 2
>>
>> I could now just try to look into the assembly by hand and try
>> to find which line produces the problem. But reading hppa assembly code
>> for such a big function is not very easy though.
> 
> Thanks a lot for trying, I appreciate it. However, I think I have an easier idea
> I could try here first and maybe we won't need the hppa assembly exercise :).

Great, thanks!
If you want me to test something, just let me know.

>> BTW, even with my patch ATAPI CDROM accesses don't work with the current kernel...
> 
> What do you mean by that, please elaborate?

I meant:
a) Without my patch the kernel did crash (see backtrace in original mail)
b) with my patch the kernel booted to login prompt, but I got those messages on the console:
 hda: command error: status=0x51 { DriveReady SeekComplete Error }
 hda: command error: error=0x54 <3>{ AbortedCommand LastFailedSense=0x05 }
 ide: failed opcode was: unknown
Nevertheless, mounting a cdrom in the drive didn't suceeded with same/similiar messages, but
this could even be because of the parisc superio driver...

Helge

  reply	other threads:[~2009-04-17  7:15 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-15 22:45 [PATCH] ide-cd: fix kernel crash on hppa regression Helge Deller
2009-04-16  6:37 ` Borislav Petkov
2009-04-16 20:26   ` Helge Deller
2009-04-17  6:53     ` Borislav Petkov
2009-04-17  7:15       ` Helge Deller [this message]
2009-04-22  6:12         ` Borislav Petkov
2009-04-22 21:13           ` Helge Deller
2009-04-23 21:34             ` Bartlomiej Zolnierkiewicz
2009-04-25 11:19               ` Helge Deller
2009-04-25 14:32                 ` Bartlomiej Zolnierkiewicz
2009-04-25 22:51                   ` Helge Deller
2009-04-26  6:33                     ` Borislav Petkov
2009-04-26  9:52                       ` Bartlomiej Zolnierkiewicz
2009-04-22  6:10 ` Borislav Petkov
2009-04-22 18:27   ` Bartlomiej Zolnierkiewicz

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=49E82C8F.5060202@gmx.de \
    --to=deller@gmx.de \
    --cc=bzolnier@gmail.com \
    --cc=kyle@mcmartin.ca \
    --cc=linux-parisc@vger.kernel.org \
    --cc=petkovbb@gmail.com \
    --cc=petkovbb@googlemail.com \
    --cc=rjw@sisk.pl \
    --cc=torvalds@linux-foundation.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.