* printouts about removable disk in the kernel log
@ 2015-04-28 15:49 Alexey Orishko
2015-04-30 9:49 ` Tim Small
0 siblings, 1 reply; 3+ messages in thread
From: Alexey Orishko @ 2015-04-28 15:49 UTC (permalink / raw)
To: linux-ide
Hi guys,
Sorry, if I'm off topic/wrong email list..
I'm using kernel 3.18.11 kernel with log level 3 and I wonder what module/driver
spamming kernel log with messages like:
...
[333670.400456] sdc: sdc1
[333681.164482] sdc: sdc1
[333703.092187] sdc: sdc1
[333735.383544] sdc: sdc1
[333745.723305] sdc: sdc1
[333767.222874] sdc: sdc1
[333777.664778] sdc: sdc1
...
[334196.922476] sdc: sdc1
[334203.111184] sdc: detected capacity change from 80022167552 to 0
[334203.113963] ata4: exception Emask 0x10 SAct 0x0 SErr 0x4010000
action 0xe frozen
[334203.113965] ata4: irq_stat 0x00400040, connection status changed
[334203.113968] ata4: SError: { PHYRdyChg DevExch }
[334203.113976] ata4: hard resetting link
[334203.836637] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
..
When a removable disk is connected, kernel log is overwhelmed with
messages about
disk and its partition like in example above. Messages in the kernel
log stop after disk
was removed (ejected). The messages are not really informative and I
wonder if they can be
switched off.
It is difficult to find this message in the kernel code, since based
on the the look it is
most likely containing only arguments to print function.
Does anyone know the origin of such messages so they can be removed?
Regards,
Alexey
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: printouts about removable disk in the kernel log
2015-04-28 15:49 printouts about removable disk in the kernel log Alexey Orishko
@ 2015-04-30 9:49 ` Tim Small
2015-05-01 17:00 ` Alexey Orishko
0 siblings, 1 reply; 3+ messages in thread
From: Tim Small @ 2015-04-30 9:49 UTC (permalink / raw)
To: Alexey Orishko, linux-ide
On 28/04/15 16:49, Alexey Orishko wrote:
> [334203.113976] ata4: hard resetting link
> [334203.836637] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
> ..
>
> When a removable disk is connected, kernel log is overwhelmed with
> messages about
> disk and its partition like in example above. Messages in the kernel
> log stop after disk
> was removed (ejected). The messages are not really informative and I
> wonder if they can be
> switched off.
Doing something like:
echo 1 > /sys/block/sdc/device/delete
prior to unplugging the drive will reduce messages on unplug (and will
also spin down the disk etc.). On some kernel versions it will also
stop the kernel speed limiting the interface (if that's a concern).
Personally I use something like "logcheck" to handle this sort of thing,
and add exclusion patterns for stuff I don't want to hear about.
Tim.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: printouts about removable disk in the kernel log
2015-04-30 9:49 ` Tim Small
@ 2015-05-01 17:00 ` Alexey Orishko
0 siblings, 0 replies; 3+ messages in thread
From: Alexey Orishko @ 2015-05-01 17:00 UTC (permalink / raw)
To: Tim Small; +Cc: linux-ide
On Thu, Apr 30, 2015 at 11:49 AM, Tim Small <tim@seoss.co.uk> wrote:
> Doing something like:
>
> echo 1 > /sys/block/sdc/device/delete
>
> prior to unplugging the drive will reduce messages on unplug (and will
> also spin down the disk etc.). On some kernel versions it will also
> stop the kernel speed limiting the interface (if that's a concern).
Well... it will kill that block device completely. If you are removing
hard disk connected to sata controller directly, it would do. However
in case of dock with a disk cartridge, dock becomes nonoperational due
to missing driver.
/alexey
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2015-05-01 17:00 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-04-28 15:49 printouts about removable disk in the kernel log Alexey Orishko
2015-04-30 9:49 ` Tim Small
2015-05-01 17:00 ` Alexey Orishko
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).