All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Brubeck Unhammer <unhammer@fsfe.org>
To: Tejun Heo <tj@kernel.org>
Cc: "Navin P.S" <navinp1912@gmail.com>, linux-ide@vger.kernel.org
Subject: Re: Lenovo A740 gave up waiting for root device with kernels >= 4.3
Date: Wed, 15 Jun 2016 10:26:20 +0200	[thread overview]
Message-ID: <87eg7yluxf.fsf@mm.st> (raw)
In-Reply-To: <20160607141142.GV31708@htj.duckdns.org> (Tejun Heo's message of "Tue, 7 Jun 2016 09:11:42 -0500")

[-- Attachment #1: Type: text/plain, Size: 2117 bytes --]

Tejun Heo <tj@kernel.org> čálii:

> On Mon, Jun 06, 2016 at 04:03:57PM +0200, Kevin Brubeck Unhammer wrote:
>> dmesg from 4.2 is attached; from 4.6 I'm not sure how to get it …
>> 
>> perhaps I could mount a USB-stick through a
>> /etc/initramfs-tools/scripts/init-premount/ script, I'll try this later
>> (I'm travelling this week, so might be a bit delayed).
>
> You can also use serial or netconsole.
>
> Thanks.

I'm still working on getting the full dmesg text :-/

There's no /dev/sd[abcd] when I have a USB-stick in there, so I don't
know how I would mount that (and from 4.7 initramfs script a
"dmesg|grep /dev/sd[abcd]" gives nothing).


I got netconsole working from the booted 4.2, but when I try from the
4.7 initramfs script it can't find eth0 even though I have r8169 in modules.

It seems r8169 is the right driver since 4.2 shows 

$ grep DRIVER /sys/class/net/*/device/uevent
/sys/class/net/eth0/device/uevent:DRIVER=r8169
/sys/class/net/wlan0/device/uevent:DRIVER=rtl8723au


I tried

/etc/initramfs-tools/modules:
r8169
ahci
libahci
uhci_hcd
ehci_hcd
usb_storage
configfs
netconsole

/etc/initramfs-tools/scripts/init-premount/kbu-blkid:
echo 'cat /proc/scsi/scsi # gives:'
      cat /proc/scsi/scsi
echo 'dmesg | grep -i libata # gives:'
      dmesg | grep -i libata
echo 'grep -i ahci /proc/modules # gives:'
      grep -i ahci /proc/modules 
echo 'modprobe ahci # gives:'
      modprobe ahci
echo 'grep -i ahci /proc/modules # gives:'
      grep -i ahci /proc/modules 
dmesg |grep -i eth
mount none -t configfs /sys/kernel/config
mkdir /sys/kernel/config/netconsole/target1
cd /sys/kernel/config/netconsole/target1
echo 0 >enabled
echo 192.168.1.117 > local_ip
echo 192.168.1.2 >remote_ip
echo eth0 >dev_name
echo 68:05:CA:29:E4:7F >remote_mac
echo 6666 > remote_port
echo 1 >enabled
echo kbu-testing >/dev/kmsg
echo 'dmesg | tail'
      dmesg | tail
echo "/KBU"

and got

http://bildr.no/image/dXFjbkEw.jpeg
http://bildr.no/image/MUpqLzZx.jpeg


I guess I'll have to start shopping for (two) USB-to-serial cables.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]

  reply	other threads:[~2016-06-15  8:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-06  7:31 Lenovo A740 gave up waiting for root device with kernels >= 4.3 Kevin Brubeck Unhammer
2016-06-06 11:26 ` Navin P.S
2016-06-06 13:54   ` Tejun Heo
2016-06-06 14:03     ` Kevin Brubeck Unhammer
2016-06-07 14:11       ` Tejun Heo
2016-06-15  8:26         ` Kevin Brubeck Unhammer [this message]
2016-07-04 15:25   ` Kevin Brubeck Unhammer
2016-07-05  5:31     ` Navin P.S
2016-07-13 17:24       ` Tejun Heo
  -- strict thread matches above, loose matches on Subject: below --
2016-05-11 10:35 Kevin Brubeck Unhammer

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=87eg7yluxf.fsf@mm.st \
    --to=unhammer@fsfe.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=navinp1912@gmail.com \
    --cc=tj@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.