From: Frank Scheiner <frank.scheiner@web.de>
To: Anatoly Pugachev <matorola@gmail.com>
Cc: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
Christoph Hellwig <hch@lst.de>, Jan Engelhardt <jengelh@inai.de>,
Sparc kernel list <sparclinux@vger.kernel.org>,
debian-sparc <debian-sparc@lists.debian.org>
Subject: Re: Regression in 028abd92 for Sun UltraSPARC T1
Date: Wed, 24 Mar 2021 14:29:29 +0100 [thread overview]
Message-ID: <234666e6-b0bb-0dbf-19e6-9f3483469dad@web.de> (raw)
In-Reply-To: <CADxRZqy0qZYs3442zyHfcw1Q0qfx_Quor+1OH2UMv43nz_HkJA@mail.gmail.com>
On 24.03.21 14:24, Anatoly Pugachev wrote:
> On Wed, Mar 24, 2021 at 4:19 PM Frank Scheiner <frank.scheiner@web.de> wrote:
>> On 24.03.21 14:16, John Paul Adrian Glaubitz wrote:
>>> On 3/24/21 2:09 PM, Frank Scheiner wrote:> Kernel sources are not available on the T1000.
>>>>
>>>> If need be, where do they need to exist and how should the directory be
>>>> named - `/usr/src/[...]`?
>>>
>>> Try installing "linux-source" and the "-dbg" package for your Debian kernel.
>>
>> But don't I need the source for the kernel at 028abd92? I figured, I
>> need the sources in `/usr/src/linux-source-5.9.0-rc1+` because
>> "5.9.0-rc1+" is the version the corresponding modules are installed -
>> could that be correct?
>
> Frank,
>
> i'm using gdb from kernel sources directory (from which kernel is
> installed), like:
>
> $ uname -a
> Linux ttip 5.12.0-rc4 #203 SMP Wed Mar 24 15:50:29 MSK 2021 sparc64 GNU/Linux
> $ cd linux-2.6
> linux-2.6$ git describe
> v5.12-rc4
> linux-2.6$ gdb -q vmlinux
> Reading symbols from vmlinux...
> (gdb) l *(sys_mount+0x114/0x1e0)
> 0x6dd7c0 is in __se_sys_mount (fs/namespace.c:3431).
> 3426 /* ... and return the root of (sub)tree on it */
> 3427 return path.dentry;
> 3428 }
> 3429 EXPORT_SYMBOL(mount_subtree);
> 3430
> 3431 SYSCALL_DEFINE5(mount, char __user *, dev_name, char __user *, dir_name,
> 3432 char __user *, type, unsigned long, flags,
> void __user *, data)
> 3433 {
> 3434 int ret;
> 3435 char *kernel_type;
> (gdb)
>
Ok, will try that approach. I'm currently `tar`ing the kernel sources
@028abd92 on the cross-compiling host and will move them over to the T1000.
Cheers,
Frank
next prev parent reply other threads:[~2021-03-24 13:30 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-22 21:30 Regression in 028abd92 for Sun UltraSPARC T1 Frank Scheiner
2021-03-22 21:48 ` John Paul Adrian Glaubitz
2021-03-22 21:55 ` Frank Scheiner
2021-03-23 16:50 ` Jan Engelhardt
2021-03-23 16:57 ` Christoph Hellwig
2021-03-23 17:39 ` Frank Scheiner
2021-03-23 22:17 ` Frank Scheiner
2021-03-24 8:28 ` Christoph Hellwig
2021-03-24 12:30 ` Frank Scheiner
2021-03-24 12:42 ` Anatoly Pugachev
2021-03-24 12:48 ` Frank Scheiner
2021-03-24 12:49 ` John Paul Adrian Glaubitz
2021-03-24 13:09 ` Frank Scheiner
2021-03-24 13:16 ` John Paul Adrian Glaubitz
2021-03-24 13:19 ` Frank Scheiner
2021-03-24 13:24 ` Anatoly Pugachev
2021-03-24 13:29 ` Frank Scheiner [this message]
2021-03-24 13:57 ` Frank Scheiner
2021-03-24 15:22 ` Jan Engelhardt
2021-03-24 15:58 ` Frank Scheiner
2021-03-24 16:10 ` Christoph Hellwig
2021-03-24 16:33 ` Frank Scheiner
2021-03-24 16:37 ` Frank Scheiner
2021-03-25 7:50 ` Christoph Hellwig
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=234666e6-b0bb-0dbf-19e6-9f3483469dad@web.de \
--to=frank.scheiner@web.de \
--cc=debian-sparc@lists.debian.org \
--cc=glaubitz@physik.fu-berlin.de \
--cc=hch@lst.de \
--cc=jengelh@inai.de \
--cc=matorola@gmail.com \
--cc=sparclinux@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).