[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#804351: Kirkwood / Qnap HS-210, kernel 3.16->4.2/ udev 215->227 upgrade issue



On Tue, 2015-11-10 at 01:08 +0000, Ben Hutchings wrote:
> On Mon, 2015-11-09 at 14:18 -0800, Martin Michlmayr wrote:
> > * Ian Campbell <ijc@debian.org> [2015-11-09 08:37]:
> > > It might be the same issue as this recent installation report:
> > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804351
> > > 
> > > I've not had a chance to dig into what is going on there. Often
> this
> > > kind of thing turns out to be an upstream change to the modules
> > > (different config options, splitting modules into more fine
> grained
> > > parts) which requires tweaks to the kernel config, or initramfs
> -tools
> > > or to the kernel udebs for the installer.
> > 
> > There was a report on the QNAP forum about a QNAP no longer booting
> > after an update.  The logs says:
> > 
> > [    8.697480]  sdb: sdb1
> > [    8.702144]  sda: sda1 sda2 sda3
> > [    8.705613] sd 1:0:0:0: [sdb] Attached SCSI disk
> > [    8.713159] sd 0:0:0:0: [sda] Attached SCSI disk
> > Begin: Loading essential drivers ... modprobe: module
> of:NocpTCsimple-bus not found in modules.dep
> > modprobe: module of:NgpioT<NULL>Cmarvell,orion-gpio not found in
> modules.dep
> > modprobe: module of:NocpT<NULL>Csimple-bus not found in modules.dep
> > modprobe: module of:NgpioTCmarvell,orion-gpio not found in
> modules.dep
> > modprobe: module of:NocpT<NULL>Csimple-bus not found in modules.dep
> > modprobe: module of:Nsata-phyT<NULL>Cmarvell,mvebu-sata-phy not
> found in modules.dep
> > modprobe: module of:NocpTCsimple-bus not found in modules.dep
> > modprobe: module of:Nsata-phyTCmarvell,mvebu-sata-phy not found in
> modules.dep
> > modprobe: module of:NocpTCsimple-bus not found in modules.dep
> > modprobe: module platform:reg-dummy not found in modules.dep
> > done.
> > Begin: Running /scripts/init-premount ... done.
> > ...
> > [ and then the UUID is not found ]
> > 
> > Any idea what these messages about modules.dep are about?
> 
> All those modaliases correspond to devices whose drivers are built-in.
> So it's not surprising that they're not found in modules.dep, and I
> don't think this has anything to do with the failure.

Indeed, I've been seeing them for a while and I don't believe they are
anything more than a cosmetic issue.

Ian.


Reply to: