LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Software > Linux - Kernel
User Name
Password
Linux - Kernel This forum is for all discussion relating to the Linux kernel.

Notices

Reply
 
Search this Thread
Old 02-26-2012, 03:32 AM   #1
mah454
Member
 
Registered: Oct 2009
Location: Iran
Distribution: Debian , Ubuntu , RHEL , CentOS , NetBill
Posts: 132

Rep: Reputation: 15
Kernel Crash (Debian)


Hello
I use Debian testing (wheezy) on Laptop vostro 3350
Code:
uname -r
Linux skynet 3.2.0-1-amd64 #1 SMP Sun Feb 5 15:17:15 UTC 2012 x86_64 GNU/Linux
kernel error log :
Code:
Feb 26 12:43:28 skynet kernel: [14045.981431] sd 6:0:0:0: [sdb] Asking for cache data failed
Feb 26 12:43:28 skynet kernel: [14045.981441] sd 6:0:0:0: [sdb] Assuming drive cache: write through
Feb 26 12:44:20 skynet kernel: [14097.951632] sd 6:0:0:0: [sdb] Test WP failed, assume Write Enabled
Feb 26 12:44:20 skynet kernel: [14097.954709] sd 6:0:0:0: [sdb] Asking for cache data failed
Feb 26 12:44:20 skynet kernel: [14097.954719] sd 6:0:0:0: [sdb] Assuming drive cache: write through
Feb 26 12:45:12 skynet kernel: [14149.925534] sd 6:0:0:0: [sdb] Test WP failed, assume Write Enabled
Feb 26 12:45:12 skynet kernel: [14149.928615] sd 6:0:0:0: [sdb] Asking for cache data failed
Feb 26 12:45:12 skynet kernel: [14149.928625] sd 6:0:0:0: [sdb] Assuming drive cache: write through
Feb 26 12:46:04 skynet kernel: [14201.899293] sd 6:0:0:0: [sdb] Test WP failed, assume Write Enabled
Feb 26 12:46:04 skynet kernel: [14201.902334] sd 6:0:0:0: [sdb] Asking for cache data failed
Feb 26 12:46:04 skynet kernel: [14201.902344] sd 6:0:0:0: [sdb] Assuming drive cache: write through
Feb 26 12:46:56 skynet kernel: [14253.873412] sd 6:0:0:0: [sdb] Test WP failed, assume Write Enabled
Feb 26 12:46:56 skynet kernel: [14253.876454] sd 6:0:0:0: [sdb] Asking for cache data failed
Feb 26 12:46:56 skynet kernel: [14253.876464] sd 6:0:0:0: [sdb] Assuming drive cache: write through
Feb 26 12:47:48 skynet kernel: [14305.845470] sd 6:0:0:0: [sdb] Test WP failed, assume Write Enabled
Feb 26 12:47:48 skynet kernel: [14305.848675] sd 6:0:0:0: [sdb] Asking for cache data failed
Feb 26 12:47:48 skynet kernel: [14305.848685] sd 6:0:0:0: [sdb] Assuming drive cache: write through
Feb 26 12:48:40 skynet kernel: [14357.819153] sd 6:0:0:0: [sdb] Test WP failed, assume Write Enabled
Feb 26 12:48:40 skynet kernel: [14357.822269] sd 6:0:0:0: [sdb] Asking for cache data failed
Feb 26 12:48:40 skynet kernel: [14357.822279] sd 6:0:0:0: [sdb] Assuming drive cache: write through
Feb 26 12:49:20 skynet kernel: [14397.723768] r8169 0000:05:00.0: PME# enabled
Feb 26 12:49:20 skynet kernel: [14397.949458] r8169 0000:05:00.0: PME# disabled
Feb 26 12:49:20 skynet kernel: [14397.968855] r8169 0000:05:00.0: eth0: link down
Feb 26 12:49:20 skynet kernel: [14397.968874] r8169 0000:05:00.0: eth0: link down
Feb 26 12:49:20 skynet kernel: [14397.970032] ADDRCONF(NETDEV_UP): eth0: link is not ready
Feb 26 12:49:22 skynet kernel: [14399.509225] r8169 0000:05:00.0: eth0: link up
Feb 26 12:49:22 skynet kernel: [14399.510045] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Feb 26 12:49:32 skynet kernel: [14409.792273] sd 6:0:0:0: [sdb] Test WP failed, assume Write Enabled
Feb 26 12:49:32 skynet kernel: [14409.795204] sd 6:0:0:0: [sdb] Asking for cache data failed
Feb 26 12:49:32 skynet kernel: [14409.795217] sd 6:0:0:0: [sdb] Assuming drive cache: write through
Feb 26 12:49:32 skynet kernel: [14410.230898] eth0: no IPv6 routers present
Feb 26 12:49:51 skynet kernel: [14429.373099] eth0: no IPv6 routers present
Feb 26 12:50:24 skynet kernel: [14461.765426] sd 6:0:0:0: [sdb] Test WP failed, assume Write Enabled
Feb 26 12:50:24 skynet kernel: [14461.768449] sd 6:0:0:0: [sdb] Asking for cache data failed
Feb 26 12:50:24 skynet kernel: [14461.768453] sd 6:0:0:0: [sdb] Assuming drive cache: write through
Feb 26 12:50:57 skynet kernel: [14495.228212] BUG: unable to handle kernel NULL pointer dereference at 0000000000000050
Feb 26 12:50:57 skynet kernel: [14495.228261] IP: [<ffffffff81044104>] atomic_inc+0x4/0x4
Feb 26 12:50:57 skynet kernel: [14495.228293] PGD 119805067 PUD 11871b067 PMD 0 
Feb 26 12:50:57 skynet kernel: [14495.228321] Oops: 0002 [#1] SMP 
Feb 26 12:50:57 skynet kernel: [14495.228342] CPU 0 
Feb 26 12:50:57 skynet kernel: [14495.228354] Modules linked in: snd_seq_dummy nls_utf8 isofs udf crc_itu_t pci_stub vboxpci(O) vboxnetadp(O) vboxnetflt(O) vboxdrv(O) acpi_cpufreq mperf cpufreq_userspace cpufreq_powersave cpufreq_conservative cpufreq_stats ip6table_filter ip6_tables iptable_filter ip_tables ebtable_nat ebtables x_tables rfcomm bnep fuse nfsd nfs lockd fscache auth_rpcgss nfs_acl sunrpc coretemp loop snd_hda_codec_hdmi snd_hda_codec_idt joydev arc4 snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_seq snd_timer snd_seq_device iwlwifi mac80211 psmouse cfg80211 snd iTCO_wdt i915 uvcvideo drm_kms_helper videodev drm media soundcore ac dell_wmi dell_laptop i2c_algo_bit v4l2_compat_ioctl32 btusb bluetooth battery i2c_i801 power_supply dcdbas iTCO_vendor_support i2c_core video rfkill sparse_keymap evdev serio_raw pcspkr snd_page_alloc wmi processor button ext4 mbcache jbd2 crc16 dm_mod ums_realtek usb_storage uas sr_mod sd_mod cdrom crc_t10dif xhci_hcd ahci libahci r8169 mii ehci_hcd libata scsi_mod us
Feb 26 12:50:57 skynet kernel: bcore usb_common thermal thermal_sys [last unloaded: scsi_wait_scan]
Feb 26 12:50:57 skynet kernel: [14495.228964] 
Feb 26 12:50:57 skynet kernel: [14495.228974] Pid: 12783, comm: cpio Tainted: G           O 3.2.0-1-amd64 #1 Dell Inc. Vostro 3350/0M516T
Feb 26 12:50:57 skynet kernel: [14495.229025] RIP: 0010:[<ffffffff81044104>]  [<ffffffff81044104>] atomic_inc+0x4/0x4
Feb 26 12:50:57 skynet kernel: [14495.229065] RSP: 0018:ffff880129bd3ed0  EFLAGS: 00010246
Feb 26 12:50:57 skynet kernel: [14495.229092] RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000
Feb 26 12:50:57 skynet kernel: [14495.229127] RDX: 0000000000000000 RSI: ffff8801123b16c0 RDI: 0000000000000050
Feb 26 12:50:57 skynet kernel: [14495.229162] RBP: 0000000000000010 R08: 0000000000000000 R09: 0000000000000000
Feb 26 12:50:57 skynet kernel: [14495.229197] R10: 0000000000000246 R11: 0000000000000246 R12: ffff88004df14aa8
Feb 26 12:50:57 skynet kernel: [14495.229233] R13: ffff88004df14aa8 R14: ffff88004df13a40 R15: ffff8801123b16d0
Feb 26 12:50:57 skynet kernel: [14495.229270] FS:  00007fddffe52700(0000) GS:ffff88012fa00000(0000) knlGS:0000000000000000
Feb 26 12:50:57 skynet kernel: [14495.229311] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Feb 26 12:50:57 skynet kernel: [14495.229339] CR2: 0000000000000050 CR3: 00000001121d1000 CR4: 00000000000406f0
Feb 26 12:50:57 skynet kernel: [14495.229375] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Feb 26 12:50:57 skynet kernel: [14495.229410] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Feb 26 12:50:57 skynet kernel: [14495.229447] Process cpio (pid: 12783, threadinfo ffff880129bd2000, task ffff88012930b140)
Feb 26 12:50:57 skynet kernel: [14495.229487] Stack:
Feb 26 12:50:57 skynet kernel: [14495.229499]  ffffffff8104469e ffff8801123b16c0 ffffffff8113dff8 ffffffff8113dfeb
Feb 26 12:50:57 skynet kernel: [14495.229541]  ffffffff810f9941 00000000008ef4d0 ffff880127f3c680 0000000000000004
Feb 26 12:50:57 skynet kernel: [14495.229583]  ffff8801123b16c0 ffff88012aeac080 0000000000000000 00007fff7ac8d790
Feb 26 12:50:57 skynet kernel: [14495.229625] Call Trace:
Feb 26 12:50:57 skynet kernel: [14495.229642]  [<ffffffff8104469e>] ? mmput+0x12/0xf8
Feb 26 12:50:57 skynet kernel: [14495.229671]  [<ffffffff8113dff8>] ? mem_release+0xd/0x11
Feb 26 12:50:57 skynet kernel: [14495.229701]  [<ffffffff8113dfeb>] ? proc_base_instantiate+0xef/0xef
Feb 26 12:50:57 skynet kernel: [14495.229736]  [<ffffffff810f9941>] ? fput+0xf9/0x1a1
Feb 26 12:50:57 skynet kernel: [14495.229762]  [<ffffffff810f769a>] ? filp_close+0x62/0x6a
Feb 26 12:50:57 skynet kernel: [14495.229792]  [<ffffffff810f7730>] ? sys_close+0x8e/0xcb
Feb 26 12:50:57 skynet kernel: [14495.229823]  [<ffffffff81345712>] ? system_call_fastpath+0x16/0x1b
Feb 26 12:50:57 skynet kernel: [14495.229855] Code: 89 2d 35 1e 5d 00 48 c7 c7 b0 70 61 81 89 44 24 18 e8 4b ba 2f 00 8b 44 24 18 48 83 c4 20 5b 5d 41 5c 41 5d 41 5e c3 f0 ff 07 c3 <f0> ff 0f 0f 94 c0 84 c0 0f 95 c0 0f b6 c0 c3 f0 48 ff 07 c3 55 
Feb 26 12:50:57 skynet kernel: [14495.230044] RIP  [<ffffffff81044104>] atomic_inc+0x4/0x4
Feb 26 12:50:57 skynet kernel: [14495.230075]  RSP <ffff880129bd3ed0>
Feb 26 12:50:57 skynet kernel: [14495.230093] CR2: 0000000000000050
Feb 26 12:50:57 skynet kernel: [14495.300811] ---[ end trace 45844b9cc5fe9ec7 ]---
Feb 26 12:51:16 skynet kernel: [14513.738487] sd 6:0:0:0: [sdb] Test WP failed, assume Write Enabled
Feb 26 12:51:16 skynet kernel: [14513.741446] sd 6:0:0:0: [sdb] Asking for cache data failed
Feb 26 12:51:16 skynet kernel: [14513.741456] sd 6:0:0:0: [sdb] Assuming drive cache: write through
Feb 26 12:52:08 skynet kernel: [14565.713107] sd 6:0:0:0: [sdb] Test WP failed, assume Write Enabled
Feb 26 12:52:08 skynet kernel: [14565.716180] sd 6:0:0:0: [sdb] Asking for cache data failed
Feb 26 12:52:08 skynet kernel: [14565.716190] sd 6:0:0:0: [sdb] Assuming drive cache: write through
what is problem ?
and other question :
I receive this message in /var/log/message :
Code:
Feb 26 12:28:44 skynet kernel: [13162.434981] sd 6:0:0:0: [sdb] Test WP failed, assume Write Enabled
Feb 26 12:29:36 skynet kernel: [13214.406147] sd 6:0:0:0: [sdb] Test WP failed, assume Write Enabled
Feb 26 12:30:28 skynet kernel: [13266.378363] sd 6:0:0:0: [sdb] Test WP failed, assume Write Enabled
Feb 26 12:31:20 skynet kernel: [13318.351860] sd 6:0:0:0: [sdb] Test WP failed, assume Write Enabled
Feb 26 12:32:12 skynet kernel: [13370.325201] sd 6:0:0:0: [sdb] Test WP failed, assume Write Enabled
Feb 26 12:33:04 skynet kernel: [13422.297948] sd 6:0:0:0: [sdb] Test WP failed, assume Write Enabled
Feb 26 12:33:56 skynet kernel: [13474.276089] sd 6:0:0:0: [sdb] Test WP failed, assume Write Enabled
Feb 26 12:34:48 skynet kernel: [13526.246294] sd 6:0:0:0: [sdb] Test WP failed, assume Write Enabled
Feb 26 12:35:40 skynet kernel: [13578.218055] sd 6:0:0:0: [sdb] Test WP failed, assume Write Enabled
Feb 26 12:36:32 skynet kernel: [13630.192317] sd 6:0:0:0: [sdb] Test WP failed, assume Write Enabled
Feb 26 12:37:24 skynet kernel: [13682.164815] sd 6:0:0:0: [sdb] Test WP failed, assume Write Enabled
Feb 26 12:38:16 skynet kernel: [13734.137903] sd 6:0:0:0: [sdb] Test WP failed, assume Write Enabled
Feb 26 12:39:08 skynet kernel: [13786.111544] sd 6:0:0:0: [sdb] Test WP failed, assume Write Enabled
Feb 26 12:40:00 skynet kernel: [13838.084967] sd 6:0:0:0: [sdb] Test WP failed, assume Write Enabled
Feb 26 12:40:52 skynet kernel: [13890.058361] sd 6:0:0:0: [sdb] Test WP failed, assume Write Enabled
Feb 26 12:41:44 skynet kernel: [13942.031415] sd 6:0:0:0: [sdb] Test WP failed, assume Write Enabled
Feb 26 12:42:36 skynet kernel: [13994.000583] sd 6:0:0:0: [sdb] Test WP failed, assume Write Enabled
Feb 26 12:43:28 skynet kernel: [14045.978277] sd 6:0:0:0: [sdb] Test WP failed, assume Write Enabled
What is this message and how can disable/fix this ?
 
Old 03-01-2012, 02:34 PM   #2
nini09
Member
 
Registered: Apr 2009
Posts: 978

Rep: Reputation: 67
It look like Debian doesn't like your harddisk. Are you sure harddisk is good?
 
Old 03-04-2012, 04:22 AM   #3
mah454
Member
 
Registered: Oct 2009
Location: Iran
Distribution: Debian , Ubuntu , RHEL , CentOS , NetBill
Posts: 132

Original Poster
Rep: Reputation: 15
sorry !
i have not sdb hard disk !
I use debian in Laptop Vostro 3350
 
Old 03-05-2012, 02:37 PM   #4
nini09
Member
 
Registered: Apr 2009
Posts: 978

Rep: Reputation: 67
Does sdb come out during installation? Or do you turn on more than one hard disk in BIOS?
 
Old 04-15-2012, 04:41 AM   #5
WizadNoNext
Member
 
Registered: Nov 2009
Posts: 125

Rep: Reputation: 9
nini09: What does installation have to do with kernel saying about non-existing device. Most hardware is dynamically detected and drivers bound to them as needed - there's nothing static! When I was installing my OS I did it on VirtualBox and now I am running on bare hardware! I have no problems at all and there's not trace of it in any kernel messages after booting on bare hardware.

mah454: can you give us logs from time when HDDs are detected? It look like that:
Code:
[    1.637479] Uniform Multi-Platform E-IDE driver
[    1.650603] amd74xx 0000:00:06.0: UDMA133 controller
[    1.650712] amd74xx 0000:00:06.0: IDE controller (0x10de:0x0759 rev 0xa1)
[    1.650838] amd74xx 0000:00:06.0: IDE port disabled
[    1.650948] amd74xx 0000:00:06.0: BIOS didn't set cable bits correctly. Enabling workaround.
[    1.652744] amd74xx 0000:00:06.0: not 100% native mode: will probe irqs later
[    1.652851]     ide0: BM-DMA at 0xffa0-0xffa7
[    1.652956] Probing IDE interface ide0...
[    1.689914] it821x 0000:01:06.0: IDE controller (0x1283:0x8212 rev 0x13)
[    1.693446] usbcore: registered new interface driver usbfs
[    1.693601] usbcore: registered new interface driver hub
[    1.697077] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
[    1.697996] usbcore: registered new device driver usb
[    1.699292] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    1.707735] SCSI subsystem initialized
[    1.709338] ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 16
[    1.709482] ITE821x IDE 0000:01:06.0: PCI INT A -> Link[LNKA] -> GSI 16 (level, low) -> IRQ 16
[    1.709677] it821x 0000:01:06.0: forcing bypass mode
[    1.709783] it821x 0000:01:06.0: controller in pass through mode
[    1.709882] it821x 0000:01:06.0: 100% native mode on irq 16
[    1.709986]     ide1: BM-DMA at 0xc400-0xc407
[    1.710132]     ide2: BM-DMA at 0xc408-0xc40f
[    1.710234] Probing IDE interface ide1...
[    1.722679] r8169 0000:04:00.0: PCI INT A -> Link[LN2A] -> GSI 18 (level, low) -> IRQ 18
[    1.722896] r8169 0000:04:00.0: setting latency timer to 64
[    1.722978] r8169 0000:04:00.0: irq 40 for MSI/MSI-X
[    1.723490] r8169 0000:04:00.0: eth0: RTL8168b/8111b at 0xffffc9000000a000, f8:d1:11:00:77:36, XID 18000000 IRQ 40
[    1.723658] r8169 0000:04:00.0: eth0: jumbo features [frames: 4080 bytes, tx checksumming: ko]
[    1.728898] libata version 3.00 loaded.
[    1.739012] firewire_ohci 0000:05:00.0: PCI INT A -> Link[LN3A] -> GSI 17 (level, low) -> IRQ 17
[    1.739184] firewire_ohci 0000:05:00.0: setting latency timer to 64
[    1.810365] firewire_ohci 0000:05:00.0: irq 41 for MSI/MSI-X
[    1.810430] firewire_ohci: Added fw-ohci device 0000:05:00.0, OHCI v1.10, 4 IR + 4 IT contexts, quirks 0x0
[    1.960142] hda: ST320011A, ATA DISK drive
[    2.010251] hdc: ST380011A, ATA DISK drive
[    2.370033] hdd: HDS722516VLAT20, ATA DISK drive
[    2.370217] hdc: host max PIO4 wanted PIO255(auto-tune) selected PIO4
[    2.370501] hdc: UDMA/100 mode selected
[    2.370912] hdd: host max PIO4 wanted PIO255(auto-tune) selected PIO4
[    2.371205] hdd: UDMA/100 mode selected
[    2.371593] Probing IDE interface ide2...
[    2.680259] hde: MAXTOR STM3320820A, ATA DISK drive
[    2.690090] hda: host max PIO5 wanted PIO255(auto-tune) selected PIO4
[    2.690200] hda: UDMA/100 mode selected
[    2.690409] ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
[    2.722615] forcedeth: Reverse Engineered nForce ethernet driver. Version 0.64.
[    2.723252] ACPI: PCI Interrupt Link [LMAC] enabled at IRQ 23
[    2.723359] forcedeth 0000:00:0a.0: PCI INT A -> Link[LMAC] -> GSI 23 (level, low) -> IRQ 23
[    2.723522] forcedeth 0000:00:0a.0: setting latency timer to 64
[    2.727231] ide-gd driver 1.18
[    2.727401] hda: max request size: 128KiB
[    2.727762] hda: 39102336 sectors (20020 MB) w/2048KiB Cache, CHS=38792/16/63
[    2.727929] hda: cache flushes not supported
[    2.787239]  hda: hda1 hda2 hda3 hda4 < hda5 hda6 hda7 hda8 >
[    2.801342] forcedeth 0000:00:0a.0: ifname eth1, PHY OUI 0x732 @ 3, addr 00:24:8c:41:74:4c
[    2.801510] forcedeth 0000:00:0a.0: highdma csum pwrctl mgmt gbit lnktim msi desc-v3
[    2.801736] ehci_hcd 0000:00:02.1: PCI INT B -> Link[LUB2] -> GSI 22 (level, low) -> IRQ 22
[    2.801947] ehci_hcd 0000:00:02.1: setting latency timer to 64
[    2.801954] ehci_hcd 0000:00:02.1: EHCI Host Controller
[    2.802114] ehci_hcd 0000:00:02.1: new USB bus registered, assigned bus number 1
[    2.802315] ehci_hcd 0000:00:02.1: debug port 1
[    2.802422] ehci_hcd 0000:00:02.1: cache line size of 64 is not supported
[    2.802460] ehci_hcd 0000:00:02.1: irq 22, io mem 0xfce7fc00
[    2.820053] ehci_hcd 0000:00:02.1: USB 2.0 started, EHCI 1.00
[    2.820208] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    2.820310] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.820466] usb usb1: Product: EHCI Host Controller
[    2.820562] usb usb1: Manufacturer: Linux 3.2.14 ehci_hcd
[    2.820659] usb usb1: SerialNumber: 0000:00:02.1
[    2.821024] hub 1-0:1.0: USB hub found
[    2.821126] hub 1-0:1.0: 6 ports detected
[    2.821444] ehci_hcd 0000:00:04.1: PCI INT B -> Link[UB12] -> GSI 20 (level, low) -> IRQ 20
[    2.821623] ehci_hcd 0000:00:04.1: setting latency timer to 64
[    2.821628] ehci_hcd 0000:00:04.1: EHCI Host Controller
[    2.821738] ehci_hcd 0000:00:04.1: new USB bus registered, assigned bus number 2
[    2.821922] ehci_hcd 0000:00:04.1: debug port 1
[    2.822024] ehci_hcd 0000:00:04.1: cache line size of 64 is not supported
[    2.822055] ehci_hcd 0000:00:04.1: irq 20, io mem 0xfce7f800
[    2.840031] ehci_hcd 0000:00:04.1: USB 2.0 started, EHCI 1.00
[    2.840172] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
[    2.840273] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.840428] usb usb2: Product: EHCI Host Controller
[    2.840524] usb usb2: Manufacturer: Linux 3.2.14 ehci_hcd
[    2.840622] usb usb2: SerialNumber: 0000:00:04.1
[    2.840928] hub 2-0:1.0: USB hub found
[    2.841027] hub 2-0:1.0: 6 ports detected
[    2.841343] ahci 0000:00:09.0: version 3.0
[    2.841820] ACPI: PCI Interrupt Link [LSA0] enabled at IRQ 22
[    2.841928] ahci 0000:00:09.0: PCI INT A -> Link[LSA0] -> GSI 22 (level, low) -> IRQ 22
[    2.842179] ahci 0000:00:09.0: irq 42 for MSI/MSI-X
[    2.842189] ahci 0000:00:09.0: controller can't do PMP, turning off CAP_PMP
[    2.842413] ahci 0000:00:09.0: AHCI 0001.0200 32 slots 6 ports 3 Gbps 0x3f impl SATA mode
[    2.842575] ahci 0000:00:09.0: flags: 64bit ncq sntf led clo pio boh 
[    2.842680] ahci 0000:00:09.0: setting latency timer to 64
[    2.842710] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[    2.844886] scsi0 : ahci
[    2.845238] scsi1 : ahci
[    2.845556] scsi2 : ahci
[    2.845841] scsi3 : ahci
[    2.846109] scsi4 : ahci
[    2.846381] scsi5 : ahci
[    2.846783] ata1: SATA max UDMA/133 abar m8192@0xfce76000 port 0xfce76100 irq 42
[    2.846942] ata2: SATA max UDMA/133 abar m8192@0xfce76000 port 0xfce76180 irq 42
[    2.847101] ata3: SATA max UDMA/133 abar m8192@0xfce76000 port 0xfce76200 irq 42
[    2.847259] ata4: SATA max UDMA/133 abar m8192@0xfce76000 port 0xfce76280 irq 42
[    2.847418] ata5: SATA max UDMA/133 abar m8192@0xfce76000 port 0xfce76300 irq 42
[    2.847577] ata6: SATA max UDMA/133 abar m8192@0xfce76000 port 0xfce76380 irq 42
[    2.848257] ohci_hcd 0000:00:02.0: PCI INT A -> Link[LUB0] -> GSI 23 (level, low) -> IRQ 23
[    2.848453] ohci_hcd 0000:00:02.0: setting latency timer to 64
[    2.848460] ohci_hcd 0000:00:02.0: OHCI Host Controller
[    2.848581] ohci_hcd 0000:00:02.0: new USB bus registered, assigned bus number 3
[    2.848786] ohci_hcd 0000:00:02.0: irq 23, io mem 0xfce7e000
[    2.902147] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001
[    2.902256] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.902414] usb usb3: Product: OHCI Host Controller
[    2.902524] usb usb3: Manufacturer: Linux 3.2.14 ohci_hcd
[    2.902623] usb usb3: SerialNumber: 0000:00:02.0
[    2.902989] hub 3-0:1.0: USB hub found
[    2.903093] hub 3-0:1.0: 6 ports detected
[    2.903430] ohci_hcd 0000:00:04.0: PCI INT A -> Link[UB11] -> GSI 21 (level, low) -> IRQ 21
[    2.903624] ohci_hcd 0000:00:04.0: setting latency timer to 64
[    2.903630] ohci_hcd 0000:00:04.0: OHCI Host Controller
[    2.903743] ohci_hcd 0000:00:04.0: new USB bus registered, assigned bus number 4
[    2.903947] ohci_hcd 0000:00:04.0: irq 21, io mem 0xfce7d000
[    2.962060] usb usb4: New USB device found, idVendor=1d6b, idProduct=0001
[    2.962163] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.962320] usb usb4: Product: OHCI Host Controller
[    2.962417] usb usb4: Manufacturer: Linux 3.2.14 ohci_hcd
[    2.962514] usb usb4: SerialNumber: 0000:00:04.0
[    2.962823] hub 4-0:1.0: USB hub found
[    2.962924] hub 4-0:1.0: 6 ports detected
[    3.040110] hdf: Hitachi HDP725050GLAT80, ATA DISK drive
[    3.040307] hde: host max PIO4 wanted PIO255(auto-tune) selected PIO4
[    3.040491] hde: UDMA/100 mode selected
[    3.040797] hdf: host max PIO4 wanted PIO255(auto-tune) selected PIO4
[    3.040967] hdf: UDMA/133 mode selected
[    3.041282] ide1 at 0xcc00-0xcc07,0xc882 on irq 16
[    3.041517] ide2 at 0xc800-0xc807,0xc482 on irq 16
[    3.041831] hdc: max request size: 512KiB
[    3.070365] hdc: 156250000 sectors (80000 MB) w/2048KiB Cache, CHS=16383/255/63
[    3.070760] hdc: cache flushes supported
[    3.088372]  hdc: hdc1 hdc2 hdc3
[    3.088990] hdd: max request size: 512KiB
[    3.160074] usb 2-3: new high-speed USB device number 2 using ehci_hcd
[    3.180301] hdd: 321672960 sectors (164696 MB) w/1794KiB Cache, CHS=20023/255/63
[    3.180843] hdd: cache flushes supported
[    3.188933]  hdd: hdd1 hdd2 hdd3
[    3.189725] hde: max request size: 512KiB
[    3.190053] ata5: SATA link down (SStatus 0 SControl 300)
[    3.190180] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[    3.190303] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[    3.190420] ata4: SATA link down (SStatus 0 SControl 300)
[    3.190564] ata3: SATA link down (SStatus 0 SControl 300)
[    3.191839] ata2.00: ATA-8: ST31000340AS, SD81, max UDMA/133
[    3.191941] ata2.00: 1953525168 sectors, multi 0: LBA48 NCQ (depth 31/32)
[    3.193999] ata2.00: configured for UDMA/133
[    3.200059] ata6: SATA link down (SStatus 0 SControl 300)
[    3.234871] ata1.00: ATA-7: ST3400633AS, 3.AAE, max UDMA/133
[    3.234979] ata1.00: 781422768 sectors, multi 0: LBA48 NCQ (depth 31/32)
[    3.252811] hde: 625142448 sectors (320072 MB) w/8192KiB Cache, CHS=38913/255/63
[    3.277209] hde: cache flushes supported
[    3.300743]  hde: hde1 hde2 hde3
[    3.301309] hdf: max request size: 512KiB
[    3.301603] ata1.00: configured for UDMA/133
[    3.301908] scsi 0:0:0:0: Direct-Access     ATA      ST3400633AS      3.AA PQ: 0 ANSI: 5
[    3.302562] scsi 1:0:0:0: Direct-Access     ATA      ST31000340AS     SD81 PQ: 0 ANSI: 5
[    3.316100] sd 0:0:0:0: [sda] 781422768 512-byte logical blocks: (400 GB/372 GiB)
[    3.316358] sd 0:0:0:0: [sda] Write Protect is off
[    3.316394] sd 1:0:0:0: [sdb] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
[    3.316479] sd 1:0:0:0: [sdb] Write Protect is off
[    3.316485] sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
[    3.316523] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    3.318533] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[    3.318581] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    3.321892]  sdb: sdb1
[    3.322408] sd 1:0:0:0: [sdb] Attached SCSI disk
[    3.327556] usb 2-3: New USB device found, idVendor=148f, idProduct=3070
[    3.327663] usb 2-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    3.327765] usb 2-3: Product: 802.11 n WLAN
[    3.327862] usb 2-3: Manufacturer: Ralink
[    3.327958] usb 2-3: SerialNumber: 1.0
[    3.349666]  sda: sda1 sda2 sda3
[    3.350540] sd 0:0:0:0: [sda] Attached SCSI disk
[    3.480226] hdf: 976773168 sectors (500107 MB) w/7174KiB Cache, CHS=60801/255/63
[    3.480599] hdf: cache flushes supported
[    3.489609]  hdf: hdf1
I suspect, that this is some usb-storage (pendrive, card-reader).
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] Netlink sockets in kernel and ethernet driver. Kernel crash. Squier Programming 2 05-08-2011 12:57 PM
growisofs cause system crash on Debian sarge, kernel 2.6.8 begemotv2718 Linux - Software 4 05-29-2007 01:23 PM
New Kernel + bootsplash cause my Debian crash wshefeng Linux - Kernel 0 06-09-2006 04:40 PM
Debian KDE crash JJX Debian 1 06-08-2005 12:09 PM
Server crash in Debian Culbert Linux - Distributions 6 04-11-2003 05:48 AM


All times are GMT -5. The time now is 03:43 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration